Send data to Google Ads

Google Ads appear within the Google advertising network to web users. Use ads to promote your brand, help sell products or services, raise awareness, and increase traffic to your website or stores.

What is Google Customer Match?

Google Customer Match is a unified ad creation tool that you can use to create and publish search, display, and video ads across the Google-owned paid media ecosystem. For example:

Note

This destination uses the Google Audience Partner API .

Changes to audiences are not immediately available in Google Ads. Allow for up to 48 hours after the point at which Amperity has finished sending audience updates for them to be available.

This topic describes the steps that are required to send customer data to Google Ads from Amperity:

  1. Get details

  2. Authorize Amperity access to the customer’s account

  3. Add destination

  4. Add data template

Get details

The Google Ads destination requires the following configuration details:

Detail one.

Configuration details for Google Ads.

The name of the product to which Amperity will send data: “Google Ads”.

The customer ID associated with your Google Customer Match account, along with the customer ID associated with the “Google Ads” account.

Note

The customer ID must be 10 digits and may not contain dashes.

A refresh token that is generated from the OAuth process that authorizes Amperity to send data to the selected product. This must be a Google account with permission to access the configured customer ID and product within Google.

Important

OAuth for “Google Ads” must be completed within Google prior to configuring OAuth in Amperity.

Detail two.

The name of an audience in Google Ads. The description is optional. If the audience does not exist, Amperity will create it.

The membership duration defines the length of time (in days) at which individual audience members will belong to the segment. The membership duration must be between 0-540 (inclusive) or 10000 for an unlimited duration.

Tip

Set this value to “0” to remove all audience members.

The Upload key type must be set to one of Contact Info, User ID, or Mobile ID.

If the Upload key type is set to “Mobile ID”, use the Mobile app ID setting to provide the ID for the iOS or Android app from which the mobile ID was collected.

Configure OAuth

OAuth is an open standard for access delegation, commonly used to grant websites or applications access to information on other websites.

Important

OAuth for “Google Ads” must be completed within Google prior to configuring OAuth in Amperity.

To configure OAuth

  1. From the Destinations tab, click Add Destination. The Add Destination dialog box opens.

  2. From the Plugin drop-down, select Google Ads.

  3. From the Credential drop-down, select Create a new credential. This opens the Create New Credential dialog box.

  4. Generate an authorization link, and then visit the URL that was generated to complete the authorization process.

    Log in to Google Ads at the generated URL using the customer’s credentials to allow access to the customer’s instance of Google Ads.

    Tip

    Send the URL to an individual who can provide the customer’s credentials, and then ask them to log into Google Ads on your behalf.

  5. When complete, you will be redirected to the Credentials page in Amperity.

    Verify the credential is on the page, and then return to the Destinations tab.

Reauthorize Amperity

You may need to reauthorize access to Google Ads. This is necessary when an authorization token has expired or when it has been removed by someone with permission to manage access within Google Ads. To reauthorize access to Google Ads, follow the steps to configure OAuth and create a new credential.

Add destination

Configure Amperity to send customer data directly to Google Ads.

Warning

Amperity must be authorized to send data to your Google Ads account prior to configuring the destination.

To add a destination

Step 1.

Open the Destinations tab to configure a destination for Google Ads, and then click the Add Destination button to open the Destination dialog box.

Name, description, choose plugin.

Enter a name for this destination and provide a description. For example: “Google Ads” and “This sends audiences to Google Ads”.

From the Plugin drop-down, start typing “google” to filter the list, and then select Google Ads.

Step 2.

Credentials allow Amperity to connect to Google Ads.

The credential type is set automatically to google-customer-match. You may use an existing credential or you may add a new one.

Choose an existing credential or add credential.

Select an existing credential from the Credential drop-down.

– or –

Select Create a new credential from the Credential drop-down. This opens the Credential dialog box.

To create a new credential for Google Ads, generate an authorization link, and then use that link to log into your Google Ads account. After you have completed that process, you will be provided a refresh token. Add the value for the refresh token to the Refresh Token setting in Amperity.

Set the following credentials for Amazon Ads.

When finished, click Save.

Step 3.

Each destination has settings that define how Amperity will deliver data to Google Ads. These settings are listed under the Settings section of the Destination dialog box.

Settings for DV360: advertiser or partner?

Choose “Google Ads”.

Settings for Google Ads.
Step 4.

Business users are assigned to the Amp360 User and/or AmpIQ User policies. (Amp360 User allows access to queries and orchestrations and AmpIQ User allows access to segments and campaigns.) A business user cannot select a destination that is not visible to them.

Business users – including users assigned to the DataGrid Operator policy – may have restricted access to PII.

What is restricted access to PII?

Restricted PII access is enabled when the Restrict PII Access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow.

You can make this destination visible to orchestrations and allow users with restricted access to PII to use this destination by enabling one (or both) of the following options:

Allow business users access to this destination.

Note

To allow business users to use this destination with campaigns, you must enable the Make available to campaigns option within the data template. This allows users to send campaign results from Amperity to Google Ads.

The other two settings may be configured within the data template instead of the destination.

Step 5.

Review all settings, and then click Save.

Save the destination.

Important

You must configure a data template for this destination before you can send data to Google Ads.

Add data template

A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.

To add a data template

Step 1.

From the Destinations tab, open the menu for a destination that is configured for Google Ads, and then select Add data template.

This opens the Add Data Template dialog box.

Step 1

From the Destinations tab, open the menu for a destination that is configured for Google Ads, and then select Add data template.

This opens the Add Data Template dialog box.

Step 2.

Verify business user access to queries and orchestrations and access to segments and campaigns.

A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data.

Step 2.

If business user access was not configured as part of the destination, you may configure access from the data template.

Important

To allow business users to use this destination with campaigns, you must enable the Make available to campaigns option. This allows users to send campaign results from Amperity to Google Ads.

If you enable this option, the data extension settings require using campaign name and group name template variables to associate the name of the data extension to your campaign.

Step 3.

Verify all configuration settings.

Verify settings for the data template.

Note

When the customer ID setting was are not configured as part of the destination, you must configure it as part of the data template before making this destination available to campaigns.

Step 4.

Review all settings, and then click Save.

Save the data template.

After you have saved the data template, and depending on how you configured it, business users can send query results and/or send campaigns to Google Ads.