Google Ads enhanced conversions, server-side
Oriva sends your conversions to Google Ads from a server, with the Google click ID (gclid, gbraid or wbraid) and, when you have them, the buyer's hashed email and phone: these are enhanced conversions. The send goes through the Data Manager API, the route Google now recommends. It no longer needs a developer token, and you connect your Google account with one click: no Google Cloud project to create.
Why the Data Manager API?
Since June 15, 2026, Google Ads' old import method refuses projects that made no offline conversion upload between December 17, 2025 and that date. Google asks you to move to the Data Manager API. A new integration built on the old method therefore fails on its first send. Oriva uses the new one.
Since September 9, 2026, Google no longer issues developer tokens: access goes through a Google Cloud project. An older tutorial that has you request a token in the “API Center” is out of date.
Who is affected, how to check, and how to migrate: read our guide.
What does Oriva send to Google Ads?
- the Google click ID captured when the visitor arrived;
- the email and phone, in the format Google asks for (for a Gmail address, without the dots or the “+”), irreversibly hashed;
- the value, the currency, and a unique transaction reference;
- the visitor's consent, the way Google asks for it.
One Oriva destination = one Google Ads conversion action. If you track leads and purchases, you create two destinations, linked to two conversion actions. That is how Google Ads organizes its conversions.
How do I test?
The “Test this destination” button asks Google to validate the request without recording it: your credentials, your access to the account and the format are checked, nothing is counted. Google offers this validation mode, Meta and TikTok don't.
Why does Google Ads count differently?
Google ties a conversion to the day of the click, Oriva to the day of the sale. Google also warns that its figures often differ by up to 20% from third-party analytics such as Google Analytics or Shopify, because the attribution models differ, and its figures for the last two days are still moving.
What if a server-side GTM already sends to the same action?
If Stape or a server-side GTM container already sends your conversions to a Google Ads action, do not plug Oriva into the same action. Google only reliably matches two sends when they carry the same transaction reference: otherwise the same click counts twice, and your bidding is tuned on an inflated number.
There are three ways out: keep a single sender, give Oriva and your GTM the same event identifier, or send Oriva's events to a dedicated action, kept secondary so it does not enter bidding.
Setup, step by step
One connect button, two identifiers to copy from your Google Ads account, and two settings in that account. The Google Ads menus are quoted as they appear in English.
- In Google Ads, note two identifiers. The account's: click the profile icon at the top right, it appears under the account name. If the account is managed from a manager account, also note that account's identifier. Then the conversion action's: Goals → Conversions → Summary, open the action, and the identifier is the number after
ctId=in the address of its page (not the tag's “conversion ID”AW-…). The action must be an import-type action (offline conversions), not a tag-based action. No conversion action yet? Create one in four minutes. - Make two settings in your Google Ads account, under Goals → Conversions → Settings: accept the customer data terms, then turn on enhanced conversions for leads, with the “Google tag” method: nothing to install on your site. Google can take several hours to apply them: a test refused right afterwards is not a mistake on your side.
- In Oriva, connect your Google account. Add the Google Ads destination, click “Connect my Google Ads account” and choose the Google account that has access to Google Ads. Google describes the “Data Manager” permission in broad terms (see, edit, create, import or delete your customer data in Google Ads): Oriva only uses it to send your conversions and to read back the status of its own sends, and you can remove the access at any time at myaccount.google.com/permissions. Then come back to Oriva, paste the account identifier, the conversion action identifier and the manager account identifier if there is one, and save.
- Click “Test this destination”. Google validates the request without recording it.
Use your own Google Cloud project (advanced)
To skip the button, provide your own OAuth credentials. The Google Cloud console menus are quoted in English, the console's default language.
- Create a Google Cloud project (or reuse one) in the Google Cloud console. In APIs & Services → Library, search for Data Manager API and enable it. Not “Google Ads API”: that is the most common mistake.
- Give the Google account that will generate the token access to the Google Ads account, by inviting it like any other user.
- Create OAuth credentials. Google Auth Platform → Clients → Create client, application type Desktop app. Keep the Client ID and copy the Client Secret right away: Google shows it only once.
- Publish the consent screen to production (Google Auth Platform → Audience → Publishing status → Publish app, the status becomes In production) before you generate the token. In “Testing” mode, Google expires the token after 7 days, and your sends stop a week after setup.
- Generate the refresh token with Google's generate_user_credentials script, or with OAuth 2.0 Playground (gear icon → Use your own OAuth credentials). Authorize the scope
https://www.googleapis.com/auth/datamanager, not the oldadwordsscope: it would fail on the first send. (Google's sample script uses theadwordsscope by default: pass the Data Manager one.) Sign in with the Google account that has access to Google Ads. - Paste them into Oriva: in the destination form, open “Use my own Google Cloud project (advanced)”, paste the Client ID, the Client Secret and the refresh token, then click “Test this destination”.
Keep reading
- Create a Google Ads conversion action: The Oriva field cannot be filled without an import-type conversion action created in your account. How to create it in four minutes.
- Google Ads: developer token removed, what now?: Developer token removed, old import refused for new projects: who is affected, how to migrate to the Data Manager API.
- Zonscope: its Google Ads conversions, server-side: Nine days of measurement: Oriva finds 95% of a server tag's conversions on Google Ads, from −9% to +6% depending on the day, and what that does not prove.
Try Oriva for free.
14 days to connect your site and watch your sales reach your platforms.
Start free trial