Google Lead Connector
When someone taps your Google ad and fills in the lead form attached to it, that person is a warm prospect — and the sooner they land in REDA, the sooner your team can follow up. The Google Lead Connector makes that automatic: once you connect a Google Ads account to REDA, every Google Lead Form submission arrives as a captured lead, complete with the campaign, form, and click details your marketing reports need. This article is written for the administrator who sets up the connection and for the agents who work the leads once they arrive. It covers what you need on the Google side, how to connect an account in REDA, where the lead and its attribution land, and where to go for closed-loop conversion reporting.
Access you'll need. Managing ad connections is administrator work. On OEM orgs, ask your administrator to assign the REDA - Ads Integration permission set, which grants the Ad Account tab, the record, and the Connect and Disconnect buttons. On ISV orgs there is no Ads permission set — assign REDA - Master Data - Admin instead, which grants the same Ad Account object access and tab. Agents who only work the leads need their normal read access to the lead record.
How it works
The connector links three things: your Google Ads account, the Lead Form running on your ads, and a REDA Ad Account record that ties them together. Once connected, the flow is hands-off:
The account only needs to be connected once. From then on new leads flow in on their own, and you work them in REDA exactly like any other lead.
What you need on the Google side
Before connecting, make sure the Google side is ready. These are things you manage in Google Ads, not in REDA:
| You'll need | Why |
|---|---|
| A Google Ads account | The account that runs your campaigns. You'll connect it to REDA and grant consent during the connect step, so sign in with a Google user that can administer it. |
| Your Google Customer ID | The account's identifier, shown in Google Ads in the form 390-649-0547. You'll record it on the Ad Account so REDA knows which account this record represents. |
| A Lead Form on your ads | The Google Lead Form asset that collects the prospect's details. Its submissions are what flow into REDA — no lead form, no leads. |
| Manager account ID (if you use one) | If your account sits under a Google manager (MCC) account, have that manager ID ready too — it's recorded on the Ad Account as the Manager / Business ID. |
If you're not sure whether your ads carry a Lead Form or which Customer ID to use, your Google Ads administrator or media agency can confirm both.
Setting up the Google side (in Google Ads)
Everything in this section happens in Google Ads — it's the work your marketing admin does on your own account so leads are ready to flow. None of it involves developer tools: REDA operates the shared connection service, so there is no Google Cloud project, API key, or app to register on your side.
390-649-0547); you'll record it on the Ad Account.Connecting a Google Ad Account
Connecting is done once per Google account, from a single Ad Account record. There is one connect button, shared by Google and Meta — you tell REDA which provider this record is for by setting the Advertising Platform field.
To end a connection, open the Ad Account and click Disconnect Ad Account. REDA releases the connection, clears the stored token, and sets Active to false. The button fails safe — if the release can't complete, the account stays connected and you're shown a LOG-#### support reference you can quote to support. Disconnecting is always safe to retry.
Turning capture on
One org-wide switch governs whether Google leads are ingested at all: Google Lead Form Enabled. It must be on for submissions to flow in, and it acts as a master pause — turn it off and REDA stops accepting Google leads across every connected account without you having to disconnect anything. Your administrator controls it; if leads aren't arriving even though an account shows Active, this switch is the first thing to check.
Where the lead and its attribution land
Each Google Lead Form submission becomes one lead record — an Inquiry on OEM orgs, a standard Lead on ISV orgs — with the prospect's answers filled in and a set of attribution fields stamped on so you can trace the lead back to the ad that produced it:
| Field | What it tells you |
|---|---|
| Ad Platform | The source — Google (or Google LSA for Local Services Ads). |
| Ad Account | A link to the Ad Account record that produced the lead. |
| Ad Campaign Id | The Google campaign the ad belonged to. |
| Ad Form Id | The Lead Form that was submitted. |
| Web gclid | The Google click ID — the key that lets a later conversion be matched back to this click. |
| Ext Lead Id | Google's own ID for the lead. REDA uses it to avoid creating the same lead twice. |
| Ad Unmapped Answers | Any custom-question answers from your lead form that don't have a dedicated field, kept together for reference. |
These fields are not on your page layout yet. A managed-package upgrade never places a field on a layout you own, so the connector can populate Ad Platform, Ad Account, Ad Campaign Id, Ad Form Id and Ext Lead Id on a record where you cannot see any of them. Verified on a captured lead: every one of them held a value while only Web gclid appeared on the layout. Add the ones you want visible — Setup → Object Manager → the lead object → Page Layouts → drag them into a section — before concluding the attribution did not arrive.
Campaign attribution. On OEM orgs, if the Ad Account has a Promotion set, that Promotion is stamped onto the new Inquiry so it rolls up to the right leasing promotion. On ISV orgs, the Ad Account carries a Campaign instead, and the connector links the new Lead to that Campaign as a member. Either way, the lead is tied to the marketing effort that earned it.
Reporting conversions back to Google
Capturing the lead is half the loop; the other half is telling Google when that lead turns into business, so Google can optimize toward the ads that actually produce customers. That closed-loop step — choosing a Google conversion action with Select Conversion Target, and letting REDA send the conversion back through Google's Data Manager API when a lead converts — is covered on its own page.
See Closed-loop Conversions & Conversion Target for the full walkthrough, including how the Web gclid captured here is what matches the conversion back to the original click.
Where to go next
- Ads Connector Overview — how the whole connector fits together, across Google and Meta.
- Ads Connector Setup — the one-time admin setup: permission set, page-layout fields, and delivery settings.
- Meta (Facebook & Instagram) Lead Connector — the same capture path for Meta Lead Ads.
- Closed-loop Conversions & Conversion Target — send conversions back to Google when a lead becomes business.
- Ads Connector Troubleshooting — when a lead doesn't arrive or a connection won't complete.
Frequently asked questions
One button — Connect Ad Account — on the Ad Account record. You choose Google in the Advertising Platform field first; the same button handles both Google and Meta.
No. The Google API project, OAuth client, and consent screen are all operated by REDA. On your side you supply a Google Ads account with a Lead Form and grant consent during Connect.
Check three things: the Ad Account shows Active, the Google Lead Form Enabled switch is on, and the Webhook Base URL and Page ID / Lead Webhook Key on the Ad Account match what your Lead Form delivery is configured with. See Ads Connector Troubleshooting.
On the captured lead — an Inquiry on OEM, a standard Lead on ISV — as Ad Platform, Ad Campaign Id, Ad Form Id, and the Web gclid. OEM orgs also stamp the Promotion from the Ad Account; ISV orgs link a Campaign member.
Was this article helpful?