Connect Google Ads

A Google destination uploads your conversions to Google Ads as click conversions, matched on gclid, wbraid/gbraid and hashed customer data. You need three values from Google: your Ads customer ID, a conversion action ID and a developer token.

Get your credentials from Google

1. Ads customer ID: the 10-digit ID shown in the top-right of Google Ads, formatted 123-456-7890.
2. Conversion action ID: in Google Ads, open Goals → Conversions. Create (or pick) the conversion action your purchases should land in, an “import”-type action, since the data arrives via API rather than a tag. The numeric ID is visible in the URL when the action is open (the ctId parameter).
3. Developer token: issued per manager (MCC) account under Tools → API Center. If you don't have a manager account, creating one is free and takes a few minutes; agencies typically already have one. Basic access is sufficient.

Create the destination

1. In RoasProof, go to Destinations and create a new one.
2. Pick the website, select Google as the platform, and name the destination.
3. Paste the Ads customer ID, conversion action ID and developer token, set the status to active, and save.

How matching works

Google attributes uploaded conversions primarily by click ID. The tracking script captures gclid (and wbraid/gbraid for iOS traffic) on the landing page and stores it first-party, so a purchase days later (long after the URL parameter is gone) still carries the click ID back to Google. Hashed email and phone are included for enhanced conversions, improving matches where the click ID alone is not enough.

Verify

Send a test conversion (through your site or the API) and check the event shows sent in Conversion events. In Google Ads, uploaded conversions appear in the conversion action's report. Allow up to a few hours for them to show. Two things to know:

• Conversions without any Google click identifier (organic or non-Google traffic) cannot be attributed by Google. They are simply not counted against your Ads campaigns. This is expected.
• If every event fails with an authorization error, the developer token and the customer ID usually belong to different account hierarchies. The token's manager account must have access to the Ads account you target. See troubleshooting.