Enabling the Google AdWords Integration

The Google AdWords integration in Attribution Analytics includes a simplified setup to notify AdWords of your app events. By adding your mobile app to the integration, the events you associate with that app automatically populate within the Google Adwords integration itself, and by enabling the appropriate postbacks, they are shared with AdWords (via postback URLs).

After your campaigns are active in AdWords, Attribution Analytics notifies AdWords’ real-time endpoint of conversions (i.e. installs and other in-app events). If responsible, AdWords then returns back to Attribution Analytics the corresponding conversion data which we use to attribute the install and any other in-app event you’ve enabled in your postback settings.

Note: Please make sure you enable “auto-tagging” in all of your Google AdWords accounts where you promote your app.

Setting up the Google AdWords integration with Attribution Analytics is streamlined and requires minimal manual setup.

  1. In Attribution Analytics, go to Partners > Integrated Partners from the main navigation
  2. Search for Google AdWords
  3. Click the Enable button on the far right

This article is part of our Common Integrations series.

Connecting Your Mobile Apps

Once you’ve enabled the Google AdWords integration, you’ll need to connect the mobile apps you’re running AdWords campaigns for to the integration. Doing so ensures that postbacks are sent to Adwords for the correct mobile apps.

  1. On the Google Adwords Details page, click Add Apps.
  2. Select your Mobile App from the drop-down.
  3. Provide the Google AdWords Link ID for your mobile app. NOTE: You can find your Google AdWords Link ID here.
  4. Repeat the steps above for all your mobile apps.

 

Note: Currently, Google AdWords has a 1-2 day turn-around time for whitelisting accounts to use the new UI. If you do not have access to the new UI being referenced in this document, please contact your AdWords account manager and ask to be whitelisted. If you’d prefer to move ahead using the legacy AdWords UI, follow these instructions instead.

Enabling App Conversion Postbacks

By default, we enable all of the app conversion event postbacks for which your mobile app already has events being measured.

Note: If you have the TUNE SDK implemented in your mobile app, TUNE will measure and attribute only those in-app events for which you’ve included event measurement code.

The Google AdWords Integration supports sending postbacks for the following TUNE pre-defined in-app events without additional configuration:

  • Install
  • Open
  • Update
  • Registration
  • Login
  • Purchase
  • Level Achieved
  • Added Payment Info
  • Add to Cart
  • Add to Wishlist
  • Tutorial Complete
  • Checkout Initiated
  • Rated
  • Content View
  • Achievement Unlocked
  • Spent Credits
  • Search
  • Reservation
  • Share
  • Invite

Importing Conversion Actions into AdWords

Once TUNE starts sending postbacks for the in-app conversions listed above, these conversion actions will be available in your AdWords account for import. To learn how to import conversion Actions, please do so here.

Note: TUNE cannot report on AdWords driven app conversions until you’ve imported all of the relevant conversion actions into your AdWords account.  Once imported, AdWords will begin to send TUNE conversion data for those conversion actions to be used for attribution.

Please make sure to import all your relevant conversion actions before launching your AdWords campaign. You cannot create AdWords campaigns that optimize on them without doing so.

Optional Custom Postbacks

While the integration includes the above-listed app event postbacks by default, you will need to create custom postbacks if:

  • You’re measuring a custom app event specific to your mobile app that’s not included in the list above.
  • You prefer not to send AdWords the revenue data (i.e. revenue & currency code) associated with your app’s events.

Sending Postbacks for Custom Events

If your mobile app includes custom in-app events you want to measure and attribute via this integration, you’ll need to create custom postbacks to ensure TUNE notifies AdWords of these custom app events.

Note: If you have the TUNE SDK implemented in your mobile app, TUNE will measure and attribute only those custom in-app events for which you’ve included custom event measurement code using the TuneEvent class.

To implement a custom event postback (including revenue data):

  1. On the Google Adwords Postback tab, click the Custom box.
  2. On the Custom Postbacks page, click Add Postback URL.
  3. On the Create Postback URL page, select the Custom Event w/ Revenue postback template from the drop-down.
  4. Make sure you make the following selections:
    1. Mobile App – select your mobile app.
    2. Event Name – select the appropriate custom in-app event.
  5. Click Save.

Sending Postbacks without Revenue Data

By default, all conversion postbacks sent to AdWords include revenue data if that conversion included revenue in its transaction (e.g. “add to cart” or “purchase”).  If you’d prefer to not pass your revenue data along to AdWords, you can implement a custom postback that omits this information (i.e. revenue & currency code).

To implement a custom postback that does not include revenue:

  1. On the Google Adwords Postback tab, click the Custom box.
  2. On the Custom Postbacks page, click Add Postback URL.
  3. On the Create Postback URL page, select the Custom Event postback template from the drop-down.
  4. Make sure you make the following selections:
    1. Mobile App – select your mobile app.
    2. Event Name – select the appropriate custom in-app event.
  5. Click Save.
  6. Disable the corresponding in-app conversion Template, by toggling it to Off.

2 Comments

Leave a reply
  • lily  •  June 14, 2017

    the message mentioned Providing the Google AdWords Link ID for your mobile app ,but if the Google AdWords is the old experience we're using not the new one ,there are conversion_id and label rather than link ID ,what should we do when setting the postback of google Adwords?

    • Grace  •  June 15, 2017

      Hello Lilly,

      Currently AdWords has a 1-2 day turn-around time for whitelisting the new AdWords UI. Please contact your AdWords account manager and ask them for access to the new UI. Alternately, if you'd like to move forward with the legacy AdWords integration, please follow these instructions instead.