Connect a Reverse ETL Source to Google Ads Remarketing Lists (Customer List)

Configure a Reverse ETL source with your Google Ads Remarketing Lists destination.

  •   3 minute read  

This guide takes you through the steps to connect a Reverse ETL source to the Google Ads Remarketing Lists destination.

Set up the connection

warning

The Reverse ETL feature supports only source-driven pipeline configuration.

Make sure you have set up a RETL source and connected it to your Google Ads Remarketing Lists destination before following the below steps.

  1. Confirm the connection settings for Google Ads Remarketing Lists destination and click Continue.
  2. In the Where do you want to sync data to? section:
  • Select Create New audience to create a new list in the Google Ads Remarketing Lists destination. Specify the name and description of the list in the respective fields.
info
RudderStack creates a new list with the specified name for that particular list ID.
  • Select Use Existing Audience if you have an existing list in the Google Ads Remarketing Lists destination and specify the List ID.
  1. Set the Sync mode to specify how RudderStack should sync the data to Google Ads.
  2. Under Choose identifier, select the column that RudderStack uses to identify your records and specify the destination field to map it to.
  3. Map the warehouse columns with the Google Ads Remarketing Lists fields. Then, click Continue to set up the connection successfully.

If you have selected Create New audience option in Step 2, the new audience will be created in the destination with the same Audience ID as in the Schema tab of your Reverse ETL connection.

Schema mappings

The following table details the mapping of the schema fields specified in the RudderStack dashboard and Google Adwords Remarketing Lists:

RudderStack schema fieldGoogle Ads Remarketing Lists field
Guidelines
emailhashedEmailInclude a domain name for all email addresses. Remove any spaces in between the addresses.
phonehashedPhoneFormat the phone number using the E.164 format. Include the country code as well.
firstNamehashedFirstNameDo not include any prefixes, for example, Mrs..
lastNamehashedLastNameDo not include any suffixes, for example, Sr..
countrycountryCodeUse the ISO two-letter/three-letter country codes. Include the country code even if all your users belong to the same country.
postalCodepostalCodeBoth 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.
mobileIdmobileIdOnly include the mobile device ID. Google Ads does not accept any other data type.
thirdPartyUserIdthirdPartyUserIDDo not include any numbers. Google Ads accepts only a string for this field.

FAQ

Why can’t I add a Reverse ETL source from the destination page?

The Reverse ETL feature supports only source-driven pipeline configuration. It means that you must configure a Reverse ETL source in RudderStack and then connect it to a new or existing destination. Note that this destination should not be connected to any other source.

See Reverse ETL FAQ for more information.

Questions? Contact us by email or on Slack