Google Ads (Google AdWords) Partner Postbacks Configuration

Introduction

Advertisers can work with Google Ads Partners to optimize campaigns on Google Ads. When configured, AppsFlyer sends postbacks to the configured Google Ads partner.

 Important!

The configuration detailed below is not for attributing installs to a selected partner in AppsFlyer, but only for sending postbacks to a selected partner running Google Ads. For details of how to configure attributing installs, click here.

 Note

This is only relevant for the Google Ads new API.

Enabling Google Ads Attribution

Advertisers can follow the instructions here on how to enable attribution for Google Ads.

What Information is Accessible?

Once you have completed the configuration for Partner Postbacks, the following information can be received, depending on the partner integration that has been configured:

1. For details of all the macros available on AppsFlyer's Postbacks, click here.
2. All parameters available from Google response.  For a description of each parameter, click here:

Ad Events ID Campaign ID Campaign Name Campaign Type External Customer ID (CID) Network TYpe Network Sub Type Timestamp Video ID
Ad Group ID Creative ID Keywork Match Type Placement Ad Type Interaction Type Conversion Metric Location

 Note

The information available is based solely on the information sent by Google. If Google do not send the information, we do not have it to pass on.

Configuring the Google Ads Marketing Partner

1.  Click Integrated Partners from the left sidebar

Integrated_Partners_link.png

2.  Enter the name of the Google Ads Partner you would like to work with in the search box and click the logo.

 Tip

Enter "Google Ads" in the integrated partners field to receive the list of Google Ads marketing partners. 

3.  Click on the required partner for Google Ads to open their unique configuration window:

GA_msc_new_2.png

 Note

The Google Ads Customer ID must be entered without hyphens or spaces.

4.  From your Google Ads account, copy the Customer ID (without hypens) from the top left-hand corner and paste it to the AppsFlyer Ads Customer ID parameter as shown in the screenshots below.

5.  Enter the number in the Google Ads Customer ID field.

GA_msc_new_4.png

6.  In the In-App Events Postback section configure the in-app for sending postbacks.

7.  Click Save.

 Important Note

  • Disabling attribution for Google Ads prevents sending postbacks to Google Ads Partners.
  • You can configure multiple Ads accounts (CID) to send postbacks (step 5) by separating each CID with a comma.

Use Cases

Use Case 1

An advertiser is running Google Ads campaigns and wants the traffic from its Google Ads accounts to be sent to Partner X.

  1. Advertiser configures Google Ads
  2. Advertiser configures Partner X - Google Ads

The advertiser must enter all its CIDs (Ads Account IDs) in the Partner X - Google Ads configuration.

Use Case 2

An advertiser and an agency are both running Google Ads campaigns, the advertiser wants only its traffic to be sent to Partner X.

  1. Advertiser configures Google Ads
  2. Agency configures Google Ads (just for their traffic to be attributed to them as an agency)
  3. Advertiser configures Partner X - Google Ads

The advertiser must enter ONLY its CIDs in the Partner X - Google Ads configuration.

Use Case 3

An advertiser and agency are running Google Ads campaigns, the agency wants only its traffic to be sent to Partner X.

  1. Advertiser configures Google Ads
  2. Agency configures Google Ads
  3. Agency configures Partner X - Google Ads

The agency must enter ONLY their CIDs in the Partner X - Google Ads configuration

Use Case 4

An advertiser and agency are running Google Ads campaigns, Both the advertiser and agency want their traffic to be sent to Partner X.

  1. Advertiser configures Google Ads
  2. Agency configures Google Ads
  3. Advertiser configures Partner X - Google Ads for their CIDs
  4. Agency configures Partner X - Google Ads for their CIDs

Notice that these must be different CID's between the advertiser & agency.

Was this article helpful?
0 out of 0 found this helpful