An OAuth connection requesting the ads scope with offline access so a refresh token is issued, stored encrypted against the account. The connect route is explicit that lead delivery itself needs no OAuth — the builder pastes a webhook URL and key into the lead form asset.
Also called: Google Ads · lead form extensions · campaign names · cost data
- 1An admin starts the connect flow from Settings.
- 2The dialog requests the ads scope with offline access and a forced consent prompt so a refresh token is always issued.
- 3The callback stores the encrypted tokens against the account.
- 4Campaign identifiers on incoming leads can then be resolved to readable names.
The route header draws the line clearly: 'IMPORTANT SPLIT: Google Ads LEAD FORM webhooks need NO OAuth at all — the builder pastes our webhook URL + key straight into the Lead Form asset and leads flow. This connection is the ENRICHMENT layer on top... Connecting is therefore optional today and gets more valuable over time — the UI says exactly that.'
- Lead attribution showed raw identifiers instead of campaign names.
- Requiring OAuth before leads could flow would have blocked the simple path.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →