Guides / Connect Google Ads
Sign in with Google, approve access, pick the Ads account. Conversion actions set themselves up — no pixel, no tags, nothing to create in Google Ads.
⏱ About 2 minutesOpen the location in Pipeline Signals → Connections → the Google Ads card. The button opens a new tab with Google's sign-in (from inside your CRM this always opens a fresh tab — finish there and come back; the page catches up on its own).
Sign in with the Google account that can access the client's Ads account. Agency manager (MCC) logins work perfectly — your client accounts appear in the picker automatically.
Google asks to approve two permissions: one to see your Ads accounts and manage conversion actions, one to deliver your conversion events. Approve both — the app uses them for exactly that and nothing else.
Choose which Ads account receives this location's offline conversions (manager accounts are listed for context — pick the client account beneath them) and click Finish connecting. We validate access live before saving.
The first time a mapped event fires, a conversion action named after it — e.g. Pipeline Signals – Purchase — appears by itself in the account under Goals → Conversions. One per mapped event, created on demand, with sensible categories. Nothing to pre-create, ever.
Where do conversions show up? In Google Ads reporting on the conversion action, usually within a few hours of the event (Google's processing lag, not ours). Clicks stay creditable for 90 days — and our dashboard shows every delivery instantly, so you always know what was sent.
One prerequisite: the contact needs a gclid — which your capture script collects on every ad visit automatically. Contacts without a Google click are simply skipped for Google (and still report to Meta with their own keys).
Pipeline Signals · dedup, retries, expiry windows and consent flags handled automatically