Google Ads enhanced conversions, server-side

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.

• 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.

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.

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.

This is the longest integration to set up, because Google requires OAuth credentials. The Google Cloud console menus are quoted in English, the console's default language.

1. 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.
2. 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.
3. Give the Google account that will generate the token access to the Google Ads account, by inviting it like any other user.
4. 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.
5. 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.
6. 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 old adwords scope: it would fail on the first send. (Google's sample script uses the adwords scope by default: pass the Data Manager one.) Sign in with the Google account that has access to Google Ads.
7. Paste everything into Oriva: the account identifier, the conversion action identifier, the manager account identifier if there is one, the Client ID, the Client Secret and the refresh token. Then click “Test this destination”.