Connect Reverse ETL Source to Google Ads Remarketing Lists
10 minute read
This guide takes you through the steps to connect a Reverse ETL source to your Google Ads Remarketing Lists destination.
RudderStack uses the Data Manager API to manage Customer Match for this integration.
Prerequisites: Account permissions
To use this integration, your Google Ads account must have Standard or Admin permissions. Otherwise, the API calls to Google Ads will fail.
Setup
- Set up and configure your Reverse ETL source.
- In the Overview tab of the source page, click Add destination > Create new destination. You can also select an already-configured destination here.
- From the list of destinations, select Google Ads Remarketing Lists and click Continue.
- Specify a unique name to identify this destination in RudderStack.
- In the Event delivery account section, click Select to choose an existing Google Ads account from the list, then skip to Step 7. To add a new account, click Add account and select any of the account types:
| Account type | Description |
|---|---|
| OAuth (Google Ads API) | If you choose this account type, RudderStack asks for the adwords OAuth scope during authentication |
| OAuth (Data Manager API) (Recommended) Beta | If you choose this account type, RudderStack asks for the dataManager OAuth scope during authentication |
- After selecting the account type, specify the following settings:
| Setting | Description |
|---|---|
| Account Name | Specify a unique account name |
| Connect account | Click Connect account, sign in with Google, and give RudderStack the required permissions to access your Google Ads account. |
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.
Click Continue to configure the mapping settings.
OAuth (Data Manager API) account type
The OAuth (Data Manager API) account type uses the Data Manager API. Creating this account grants RudderStack the datamanager scope on your Google account, which is used to manage your audience data.
Migrate from OAuth (Google Ads API) account type
If an existing destination uses the OAuth (Google Ads API) account type for authentication, follow these steps to migrate to OAuth (Data Manager API):
Go to the Configuration tab of the destination and click Switch account.
Click Add account and select OAuth (Data Manager API) as the account type.
Specify the Account name and click Connect account to sign in with Google and give RudderStack the required permissions.
After connecting the new 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.
Save the changes.
Mapping settings
This section lists the settings to correctly map data from your Reverse ETL source to the Google Ads Remarketing Lists destination.
Select user list
In this section, you can create a new user list or use an existing one.
- Create new list: Use this option to create a new list in Google Ads. You can specify the name and description of the new list.
- Use existing list: Use this option if you have an existing list in Google Ads. RudderStack automatically populates this field with the relevant lists based on your specified connection settings.
Sync mode
RudderStack supports only Mirror mode for this integration.
Select list type
If you select the Create new list option, you need to select the type of list where you want to sync the data. RudderStack provides three options:
| List type | Description |
|---|---|
| CONTACT_INFO | You can send email, phone number, and address information in this list |
| CRM_ID | You can send internal customer IDs in this list |
| MOBILE_ADVERTISING_ID | You can send mobile advertising IDs (IDFA/GAID) in this list Note: If selected, specify the App ID of the mobile app the data was collected from.
|
Map identifiers
In this section, you can map your warehouse columns to specific Google Ads fields that represent your audience’s identity.
The fields available for mapping depend on the list type you select.

Advanced settings
| Setting | Description |
|---|---|
| Automatically hash PII data | When set to Yes, RudderStack hash-encodes sensitive user data like email, phone, first name, and last name in the SHA-256 format. See Data hashing section for more information. |
| Specify user consent | Specify the consent type for the uploaded users for using their data in Google Ads. RudderStack provides four options for this setting:
|
| Specify ad personalization consent | Specify consent for uploaded users for personalizing ads. RudderStack provides four options for this setting:
|
Sync settings
RudderStack determines how and when to run a sync based on the sync schedule you set for your Reverse ETL connection.
| Schedule type | Description |
|---|---|
| Basic | Run syncs at a set interval, optionally starting from a specified time (UTC). If a start time is set, syncs run from that time until the end of that day. |
| CRON | Run syncs based on a specified CRON expression (in UTC). |
| Manual | Run syncs manually. |
Sync observability settings
| Setting | Description | ||||||
|---|---|---|---|---|---|---|---|
| Retain sync logs | This setting is toggled on by default and instructs RudderStack to store the sync logs in your warehouse. You can also configure the below settings:
| ||||||
| Retry failed records | This setting is toggled on by default and causes RudderStack to continually retry sending the failed records. | ||||||
| Retain and show failures | This setting is toggled off by default. Turn it on to have RudderStack write the error recorded for every failed record to a failed records table in your warehouse and show it in the sync’s failed records view. It applies from the next sync and can take up to a minute to reach your data plane.
|
Storing sync logs, snapshot tables, and failed records may incur additional warehouse costs.
Data normalization
By default, RudderStack automatically cleans and standardizes the data as prescribed by Google Ads.
After normalization, RudderStack validates each field before sending it to Google Ads:
- If a field is determined to be invalid, RudderStack does not send it to Google Ads.
- If all fields in a row are invalid, then the entire row is rejected and marked as failed
RudderStack first normalizes the data and then validates it, skipping any invalid rows. Then, it hashes the data before sending it to Google Ads.
Data hashing
The Automatically hash PII data setting lets you hash your user data before sending it to Google Ads. This setting is enabled by default.
- Configure the setting to Yes if your incoming data is not pre-hashed
- Configure this setting to No if your data is already hashed
Incorrect configuration of the Automatically hash PII data setting will result in failures.
- If the Automatically hash PII data setting is configured to Yes and your data is pre-hashed, the event will fail.
- If the Automatically hash PII data setting is configured to No and your data is not pre-hashed, the event will fail.
RudderStack rejects such events with a clear error message, for example:
Hashing is disabled but the value for field EMAIL appears to be unhashed. Either enable hashing or send pre-hashed data.You will also see errors in the Events tab for cases that were previously marked as successful, but were effectively resulting in no matches, helping you quickly identify and fix any data quality or configuration issues.
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.
What are the account permissions required for the Google Ads Remarketing Lists integration?
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.
Follow these steps to set the access level:
- Sign in to your Google Ads account and go to TOOLS AND SETTINGS > Access and security:

- Enter the email address of the account. From the list of permissions, select Standard or Administrative. Then, click SEND INVITATION:

The account will have the required access-level permissions once the user accepts the invitation.
How do I create a Google Ads customer list?
- Open your Google Ads account.
- Go to Tools and settings.
- Under Shared Library, go to Audience Manager.
- Click the + button and select Customer list.
- Under Segment name, assign a name to the list.
- From the dropdown, select the list type of data to upload.
- Upload the CSV containing the user data. You can also download the template and upload the data.
- Click UPLOAD AND CREATE.
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.
See About manager accounts 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 |
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, insufficient access, or API rate limits.
| Error | Notes |
|---|---|
USER_PERMISSION_DENIED | The authenticated Google account doesn’t have permission to act on the selected account, or you’re trying to modify a customer list created by a different account (only the owning account can edit a list). 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. |
RESOURCE_EXHAUSTED | Too many requests are sent in a short period — this is a quota/rate limit issue rather than a configuration error. Batch your operations and review Google’s API limits and quotas. |
For other Customer Match-specific errors, see Google’s Customer Match Troubleshooting Guide.
Why am I getting a 400 Bad Request error message while setting up the Google Ads Remarketing Lists 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.