Google AdWords Enhanced Conversions

Step-by-step guide to send event data from RudderStack to Google AdWords Enhanced Conversions.

Google Adwords Enhanced Conversions lets you improve your conversion measurement accuracy by securely sending first-party conversion data from your website to Google.

RudderStack supports Google Adwords Enhanced Conversions as a destination to which you can send your audience list.

To use this destination, you must set up Enhanced Conversions with the Google Ads API. For detailed instructions, refer to the Google Ads support page.

Getting started

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

Connection Mode	Web	Mobile	Server
Device mode	-	-	-
Cloud mode	Supported	Supported	Supported

To know more about the difference between cloud mode and device mode in RudderStack, refer to the RudderStack Connection Modes guide.

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

1. From your RudderStack dashboard, add the source. Then, from the list of destinations, select Google AdWords Enhanced Conversions.

2. Assign a name to your destination and click on Next.

Connection settings

To successfully configure Google AdWords Enhanced Conversions as a destination, follow the steps below:

1. Give RudderStack access to your Google Ads account by clicking on the Sign in with Google button under Create new account.

2. Then, you will need to 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.

For more information on obtaining the customer ID, refer to the Google Ads Help Center page.

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

For more information on subaccounts, refer to the Google Ads Help Center page.

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

This field is required only when you want to send data to a customer list of a 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.

For information on the track call, refer to the RudderStack API Specification guide.

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

RudderStack uses the ConversionAdjustment method to send these events to Google Ads.

RudderStack will discard any track call where orderId is not present. This is because orderId is a required field for enhancement.

Supported mapping

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

RudderStack field	Google AdWords 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 the 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.

FAQs

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 Adwords customer ID?

To get the customer ID associated with your Google Ads account, click on 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:

1. Enter the email address of the account and from the list of permissions, select Standard or Administrative. Then, click on 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.

Contact us

For queries on any of the sections covered in this guide, you can contact us or start a conversation in our Slack community.