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.

Getting started

Before configuring Google Ads Enhanced Conversions as a destination in RudderStack, verify if the source platform is supported by referring to the table below:

Once you have confirmed that the source platform supports sending events to Google Ads Enhanced Conversions, follow these steps:

1. From your RudderStack dashboard, add the source. Then, from the list of destinations, select Google Ads Enhanced Conversions.
2. Assign a name to your destination and click Next.

Google Ads Permissions

Actions undertaken via your RudderStack integration rely on the authorizing Google Ads user's underlying permissions and must be at least Standard or Admin.

If an integration is authorized by a user without at least Standard or Admin permissions, API calls will fail, and a "RudderStack Admin" user will disable the integration in your audit logs. If you encounter an entry in your audit logs from a Rudder Admin/admin@rudderstack.com user, this means that the integration was disabled by RudderStack on account of insufficient permissions by your Google Ads user.

To avoid this, ensure that the authorizing user has the Standard permissions, at minimum.

Connection settings

To successfully configure Google Ads Enhanced Conversions as a destination, first authenticate your account by following the below steps:

1. Click Create Account in the Account Settings section.
2. From the modal, click the Sign in with Google button.
3. Choose the required account and grant RudderStack the required permissions.
4. Click Save to use the specified account, as shown:

In case you have authenticated multiple accounts, you can click Edit Credentials to select or delete any other authenticated account, as shown:

RudderStack gives an error if you try to delete an account used by any other connection set up for the same destination.

Next, configure the following settings:

• Customer ID: Enter the ID associated with your Google Ads account. You can find it by clicking on the Help option in your dashboard.

• Subaccount: Enable this setting if you are using a Google Ads subaccount.

• Login Customer ID: Enter the customer ID of the manager account (associated with the subaccount).

Event settings

• List of Conversion: Enter the list of events on which you want to perform enhanced conversions. RudderStack will discard any events that are not specified in this list.

• Hashing Required: Enabled by default, this setting hash encrypts the user identifiers, such as email, phone number, first name, last name and street address.

Track

The track call lets you record and send the conversion events along with any properties associated with them.

A sample track call is shown below:

Copy
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",
    },
  ],
})

Supported mapping

The following table details the mapping of the fields specified in the RudderStack dashboard and Google Ads Enhanced Conversions, along with the relevant guidelines:

FAQ

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?

To get the customer ID associated with your Google Ads account, click the Help option in your Google Ads dashboard. You will find the customer ID in the resulting pop-up, as shown:

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:

1. Sign into to your Google Ads account and go to TOOLS AND SETTINGS > Access and security, as shown:

2. Enter the email address of the account and from the list of permissions, select Standard or Administrative. Then, click SEND INVITATION, as shown:

The account will have the access level permissions once they accept the invitation.

I am getting a 400 Bad Request error message. What should I do?

If you get a 400 Bad Request error while configuring the destination, make sure your customer account is allow-listed and configured to have Standard or Administrative access levels in Google Ads. Refer to the above FAQ for steps on setting the access level permissions for the account.