PathwAI's Google Ads integration uploads conversions from your flows to Google Ads through Google's Data Manager API. Each event you map is credited to a conversion action you choose, with the Google click ID from the visit and hashed contact details for matching. Events go out only for people who consented to ad tracking. PathwAI can also sync segments to Customer Match.
What data moves
- Click IDs: gclid, gbraid or wbraid from the flow URL, or from Google's own click cookies when the flow URL has none.
- Hashed email, phone, first and last name, with country and postal code.
- For purchases: value, currency and the order ID as the transaction ID, so a browser tag reporting the same order is not counted twice.
- For Customer Match: hashed email and phone of segment members who consented to ad tracking.
Where it is configured
Data → Destinations → Google Ads (Data Manager API) holds the Customer ID, an optional Login Customer ID for a manager account, and a Connect with Google sign-in. Conversion Action IDs are set on each event mapping.
Use cases
Credit campaigns for completed intakes
Map flow_completed to a conversion action so bidding learns from finished intakes.
Website-first visitors keep the click
A visitor who clicked an ad, browsed your site and then opened the flow keeps the click through Google's cookies.
Several conversion actions, one destination
Credit started intakes and purchases to different conversion actions from the same destination.
Enhanced conversions
Turn it on to send events without a click ID when a hashed email or phone is available.
How to set it up
- Open Data → Destinations and choose Google Ads (Data Manager API).
- Enter the Customer ID, plus the Login Customer ID if you sign in through a manager account.
- Click Connect with Google and grant access.
- In the Events tab, add a source event and set the numeric Conversion Action ID from Google Ads. Leave Send on.
- Turn the destination on in its header.
Good to know
- By default, an event without a Google click ID is skipped. Enhanced conversions, off by default, sends it when a hashed email or phone is present.
- A mapping with a missing or non-numeric Conversion Action ID is skipped.
- Events reach the ad platform only for people who consented to ad tracking, through a consent block marked for ad tracking or a call to window.pathwai.consent(). A run with no recorded consent counts as opted out.
Google Ads integration FAQ
Do I need a Google Ads developer token?
No. The Data Manager API connection uses Connect with Google, with no developer token and no pasted refresh token.
What if the visit has no click ID?
The event is skipped unless enhanced conversions is on, in which case it is sent when a hashed email or phone is available.
Are answers sent to Google Ads?
Not by default. Only fields a transformer allows are added to the click ID, hashed identifiers and purchase details.
Want to see Google Ads in a flow?
We can walk through where Google Ads fits in your funnel and exactly which data it would receive.