Send data to Google Ads

Google Ads appear within the Google advertising network to web users. Advertisers pay to display brief advertisements, service offerings, product listings, and so on.

Note

This destination uses the Google Ads 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:

  1. The name of the custom audience to which Amperity will send data. Amperity will create the custom audience name if it does not already exist.

  2. The membership duration for the custom audience. Membership duration defines for how long a name stays in the custom audience list. When the duration expires, the name is removed from the list. The default is 30 days. The maximum is 540 days.

  3. The upload key type. The upload key type must be one of the following: “Contact Info”, “User ID”, or “Mobile ID”.

    If the upload key type is “Mobile ID”, add the ID for the iOS or Android application from which the data will be collected.

    Caution

    A list can be uploaded with only one type of data–contact info, mobile device ID, or user ID–and once uploaded will not accept any other list ID types.

  4. Authorize Amperity to send data to the customer’s Google Ads account.

Configure OAuth

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

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 data to Google Ads using the Google Ads API.

Warning

Amperity must be authorized to send data to the customer’s Google Ads account prior to configuring the destination.

To add a destination

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

  2. Enter the name of the destination and a description. For example: “Google Ads” and “This sends customer data to Google Ads”.

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

  4. From the Credentials drop-down, select the “the OAuth credential you created for your Google Ads account” credential type. Select the OAuth credential you created for your Google Ads account, after which configuration settings are added automatically.

  5. Under Google Ads Settings, enter the customer ID.

  6. Select Allow business users to use this destination.

    This allows users who have been assigned to the Amp360 User and/or AmpIQ User policies to use this destination with orchestrations and/or campaigns.

  7. Select Allow business users with limited PII access to send data.

    This allows users who have been assigned to the Restrict PII Access policy option to use this destination with orchestrations and/or campaigns.

  8. Click Save.

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.

You have two options for setting up data templates for Google Ads:

  1. For use with campaigns

  2. For use with orchestrations

for campaigns

You can configure Amperity to send campaigns to Google Ads. These results are sent from the Campaigns tab. Results default to a list of email addresses, but you may configure a campaign to send additional attributes to Google Ads.

To add a data template for campaigns

  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.

  2. Enter the name of the data template and a description. For example: “Google Ads audiences” and “Send audiences to Google Ads.”

  3. Enable the Allow customers to use this data template option, and then enable the Make available to campaigns option. This allows users to send campaign results from Amperity to Google Ads.

  4. Verify all template settings and make any required updates.

  5. Click Save.

for orchestrations

You can configure Amperity to send query results to Google Ads. These results are sent using an orchestration.

To add a data template for orchestrations

  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.

  2. Enter the name of the data template and a description. For example: “Google Ads customer profiles” and “Send email addresses and customer profiles to Google Ads.”

  3. Enable the Allow customers to use this data template option. This allows users to build queries, and then configure orchestrations that send results from Amperity to a configured destination.

  4. Optional. Enable the Allow orchestrations from customers with limited PII access option. This allows users who have been assigned the Restrict PII Access policy option to send results from Amperity.

  5. Verify all template settings and make any required updates.

  6. Click Save.