Google Ads Enhanced Conversions (Cloud Mode)
11 minute read
Choose the right Google Ads destination
RudderStack offers two Google Ads destinations that can support enhanced conversions:
- Use this destination to send events in cloud mode (server-to-server integration) using the Google Ads API
- Use the Google Ads (gtag.js) destination if you’re sending events in web device mode and want to enable enhanced conversions for your setup
Google Ads Enhanced Conversions lets you improve your conversion measurement accuracy by securely sending first-party conversion data from your website to Google.
RudderStack supports Google Ads Enhanced Conversions as a destination to which you can send your audience list.
Key features
The Google Ads Enhanced Conversions destination integration supports the following features:
| Feature | Available | Description |
|---|---|---|
| Adjustment types | Yes | Supports enhancement and restatement adjustments |
| User identification | Yes | Supports email, phone, name, and address identifiers with SHA-256 hashing |
| Google Consent Mode | No | Google’s ConversionAdjustment resource has no consent field, so ad_user_data and ad_personalization values cannot be passed.See the FAQ for details. |
| User deletion | No | Google Ads Enhanced Conversions does not support user deletion |
Connection compatibility
| Destination Information | |||
|---|---|---|---|
| |||
Prerequisites
To use this destination correctly, you must:
Set up Enhanced Conversions with the Google Ads API.
Accept the Google Ads data terms to receive the enhanced conversions events successfully. To accept the terms:
- Log in to your Google Ads dashboard.
- Go to Conversions > Settings > Customer Data Terms.
- Carefully read and accept the customer data terms.

Google Ads permissions
This integration relies on the authorizing Google Ads user’s underlying permissions and must be at least Standard or Admin.
If you authorize the integration without the Standard or Admin permissions, the API calls will fail and a “RudderStack Admin” user will disable the integration. If you encounter an entry in your audit logs from a Rudder Admin/admin@rudderstack.com user, it means that RudderStack disabled the integration on account of insufficient user permissions.
To avoid this, ensure that the authorizing user has the Standard permissions, at minimum.
Setup
- In your RudderStack dashboard, set up a source.
- Go to the Overview tab of your source and select Add Destination > Create new destination.

- Select Google Ads Enhanced Conversions from the list of destinations. Then, click Continue.
Connection settings
| Setting | Description |
|---|---|
| Destination name | Assign a name to uniquely identify the destination. |
| Event delivery account | Click Select to choose an existing Google Ads account for authentication. To add a new account:
|
| Customer ID | After connecting a Google account under Event delivery account, select the Customer ID from the picker. The top level lists every Google Ads account the signed-in user can access directly, including standalone accounts. Each account’s enabled descendants are listed beneath it with their depth shown in the label. You can select a top-level account or any account beneath it, including a manager. RudderStack sets the login customer automatically from your selection. Only enabled accounts appear. If an account is missing, it is usually disabled in Google Ads or not accessible to the signed-in user. |
Configuration settings
| Setting | Description |
|---|---|
| List of Conversion | Select one or more enabled conversion actions from the selected Google Ads account in the multi-select. RudderStack discards events whose conversion names aren’t in this list. |
| Hashing Required | This setting is enabled by default and hash encrypts the user identifiers like email, phone number, first name, last name, and street address using the SHA256 encryption method. |
| Adjustment Type | Select the adjustment type for your conversions. The following options are available:
|
Other settings
| Setting | Description |
|---|---|
| Consent management settings | Configure the consent management settings for the specified source by choosing the Consent management provider from the dropdown and entering the relevant consent category IDs. See Consent Management in RudderStack for more information on this feature. |
Track
The track call lets you record and send the conversion events along with any properties associated with them. RudderStack uses the ConversionAdjustment method to send the track events to Google Ads.
Important considerations
- Create the conversion actions in Google Ads before sending the associated conversion events from RudderStack. Select their names in List of Conversion.
- RudderStack does not send user consent values for this destination. Google’s
ConversionAdjustmentresource has noconsentfield, so Google Consent Mode values cannot be passed — see the FAQ for details.
A sample track call is shown below:
rudderanalytics.track("Order Completed", {
checkout_id: "12345",
orderId: "123",
affiliation: "Apple Store",
gclid: "abcd1234",
conversionDateTime: "2019-01-01 12:32:45-08:00",
adjustedValue: 100,
currencyCode: "INR",
adjustmentDateTime: "2019-01-01 12:32:45-08:00",
total: 20,
revenue: 15.0,
shipping: 22,
tax: 1,
discount: 1.5,
coupon: "SAVE45",
currency: "USD",
products: [
{
product_id: "FS247",
sku: "G-32",
name: "Monopoly",
price: 14,
quantity: 1,
category: "Games",
url: "https://www.estore.com/product/funskool-monopoly",
},
],
})orderIdis a required field to send atrackcall successfully.
Important considerations
- If you set the Adjustment Type to Restatement, use the
adjustedValueandcurrencyCodefields to specify the corrected conversion value and currency.- RudderStack does not send user identifiers or the
userAgentfield for Restatement events — only the conversion adjustment data is included in the payload.See the Google Ads documentation for more information on uploading conversion adjustments.
Supported mappings
The following table details the mapping of the fields specified in the RudderStack dashboard and Google Ads Enhanced Conversions, along with the relevant guidelines:
| RudderStack field | Google Ads Enhanced Conversions field | Guidelines |
|---|---|---|
gclid | gclid | This is the Google click ID associated with the original conversion. |
conversionDateTime | conversionDateTime | The datetime at which the conversion for the adjustment occurred. You must specify the timezone in the format `yyyy-mm-dd hh:mm:ss+ |
adjustedValue | adjustedValue | The value of the conversion after restatement. To change the value of a conversion from 100 to 75, for example, you should report an adjusted value of 75. |
currencyCode | currencyCode | Use the ISO 4217 3-character currency code, e.g. USD/EUR. |
orderId | orderId | If a conversion was reported with a specific order ID, then that order ID must be used as the identifier. |
adjustmentDateTime | adjustmentDateTime | The datetime at which the adjustment occurred. You must specify the timezone in the format `yyyy-mm-dd hh:mm:ss+ |
userAgent | userAgent | User agent should only be specified in enhancements with the user identifiers and it should match the user agent of the request that sent the original conversion. This is so that the conversion and the enhancement both are either attributed as same or cross-device. |
email | hashedEmail | Include a domain name for all email addresses. Remove any spaces in between the addresses. |
phone | hashedPhone | Format the phone number using the E.164 format. Include the country code as well. |
firstName | hashedFirstName | Do not include any prefixes (e.g., Mrs.). |
lastName | hashedLastName | Do not include any suffixes (e.g., Sr.). |
city | city | This field accepts any string. |
state | state | This field accepts any string. |
country / countryCode | countryCode | Use the ISO two-letter/three-letter country codes. Include the country code even if all your users belong to the same country. |
postalCode | postalCode | Both the US and international zip and postal codes are allowed. For the US, 5 digit codes followed by 4 digit extensions are also allowed. For the rest of the countries, do not include the postal code extensions. |
FAQ
Can I send Google Consent Mode values (ad_user_data / ad_personalization) to Google Ads Enhanced Conversions?
No. Google’s ConversionAdjustment resource, which the Enhanced Conversions API (uploadConversionAdjustments) accepts, does not include a consent field — unlike ClickConversion used by Google Ads Offline Conversions. Because the field does not exist in Google’s API, consent values cannot be passed for this destination, including via a custom transformation.
Enhanced conversions for web supplement a conversion Google has already recorded: your Google tag sends the GCLID and order ID at conversion time, and the adjustment attaches hashed user data afterwards. Set consent on that original conversion instead — either with Consent Mode on your Google tag, or by using the Google Ads Offline Conversions destination, where RudderStack maps consent end-to-end.
What are the account permissions required for this integration?
For the integration to be successful, make sure the customer account used for OAuth verification adheres to Google’s Customer Match policy and has Standard or higher (Administrative) access level permissions. For more information on the access level permissions, refer to this Google Ads support page.
To set the access level, follow these steps:
- Log in to your Google Ads account.
- In the left navigation bar, click Admin > Access and security.
- Click the + symbol. Then, enter the email address of the account and from the list of permissions, select Standard or Administrative.

- Click Send invitation.
The account will have the access level permissions once the user accepts the invitation.
According to my audit logs, a “Rudder Admin” user updated my destination. Why is this?
This is a Google Ads permissions issue. See Google Ads Permissions for details.
Can I set up the Enhanced Conversions and Remarketing Lists destinations using the same Google Ads account?
Yes, you can. Both the integrations are the sub-features of Google Ads. Hence, you can use the same Google Ads account to configure both the destinations in RudderStack.
Where can I find my Google Ads customer ID?
After you connect a Google account under Event delivery account, the Customer ID picker lists the accounts it can access. Select the account there. You don’t need to look up its ID.
When do I need to provide a Login Customer ID?
You don’t enter Login Customer ID — the picker doesn’t show that field. Select the account itself for direct access. To access an account under a manager, select it beneath that manager. RudderStack derives the login customer from your selection: the top-level account for a descendant, or none when you select a top-level account itself. For cross-account conversion tracking, select the conversion-owning manager instead of the child.
See About manager accounts and Cross-account conversion tracking.
My account uses cross-account conversion tracking. What should I enter in the Customer ID field?
If your account uses cross-account conversion tracking, select the conversion-owning manager in the Customer ID picker rather than the child account. Select it at the top level if you can access it directly, or beneath its parent manager if you reach it through another manager. The conversion actions live on that manager.
Under cross-account conversion tracking, the conversion actions live on the manager account, and the Google Ads API requires conversion uploads to be sent to that manager.
Even though you may think of the child account as the destination for conversions, the attribution to the child happens automatically inside Google Ads — you don’t need to specify the child anywhere in the destination configuration
Selecting the child instead of the conversion-owning manager can cause INVALID_CUSTOMER_ID or CUSTOMER_NOT_ACCEPTED_CUSTOMER_DATA_TERMS. Selecting the top-level manager leaves Login Customer ID empty automatically.
To confirm which account owns conversion tracking for a given child, sign in to the child account in the Google Ads dashboard and go to Tools > Conversions. If a banner indicates conversions are managed by a manager, select that manager in the picker.
See Cross-account conversion tracking (Google Ads API) for more information.
How do I know which Customer ID and Login Customer ID combination applies to my setup?
| Setup | Select in the Customer ID picker | Automatic Login Customer ID |
|---|---|---|
| Direct-access account | The account itself (top-level) | Empty |
| Account under a manager | The account beneath its manager | Top-level manager |
| Child under cross-account conversion tracking | The conversion-owning manager — at the top level if you can access it directly, otherwise beneath its parent manager | Empty for a top-level selection, otherwise the top-level manager |
Why am I getting the USER_PERMISSION_DENIED, INVALID_CUSTOMER_ID, or CUSTOMER_NOT_ACCEPTED_CUSTOMER_DATA_TERMS errors?
These errors can indicate an incorrect account selection or insufficient access.
| Error | Notes |
|---|---|
USER_PERMISSION_DENIED | The authenticated Google account doesn’t have permission to act on the selected account. Check that the selected manager is linked to the child in Google Ads. |
INVALID_CUSTOMER_ID | The selected account or its manager might not be authorized. Under cross-account conversion tracking, select the conversion-owning manager instead of the child. |
CUSTOMER_NOT_ACCEPTED_CUSTOMER_DATA_TERMS | Customer data terms haven’t been accepted on the account that owns conversion tracking. If cross-account tracking is in use, the terms must be accepted on the manager account, not the child. |
Why am I getting a 400 Bad Request error message while configuring the destination?
If you get a 400 Bad Request error while configuring the destination, make sure your customer account is allowlisted and configured to have Standard or Administrative access levels in Google Ads.
See the above FAQ for steps on setting the access level permissions for the account.