GMP DV360/CM (DoubleClick)—CM360 and media source

At a glance: Set up and use the attribution link for CM360.

 Related reading

For a complete picture of working with Google Marketing Platform (GMP) in AppsFlyer, check out these articles:

 Important!

  • When setting up campaign management using CM360 and an AppsFlyer integrated partner, first complete the GMP Integration Guide and the partner's integration guide, before continuing with the instructions in this section.
  • If you are managing a DV360 campaign through CM360, ignore the instructions in this section. Switch back to the integration tab and follow the instructions there.
  • AppsFlyer does NOT recommend using the CM360 + media source scenario to report on SRN traffic if the relevant SRN partner integration is also enabled. This is in order to avoid conflicts when reporting conversions from the same partner via two different integrations. For example, if the Facebook SRN integration is enabled in AppsFlyer, but CM360 is also utilized to report on Facebook traffic (facebook_int) using the method described in this article in parallel, conversions might alternatively be reported by Facebook and CM360, with CM360 capturing some of the conversions that would have been claimed by the main Facebook integration.

Setting an attribution link for GMP campaign manager

To run and measure campaigns in CM360, you need an AppsFlyer attribution link. For data to be posted back to GMP and correctly logged in AppsFlyer, such data needs to be appended on the AppsFlyer link and not the CM360 link.

  1. Create a CM360 link.
    You must make sure you have a placeholder for the Device ID, the parameter dc_rdid, because AppsFlyer only receives mobile app conversion claims from the GMP integration, based on the presence of this parameter.
  2. Create an attribution link.

    • The attribution link should contain the actual media source that you intend to report on, which should be a third-party media source, not GMP. For example, if the third-party media source is Rocketfuel, use pid=rocketfuel_int and not pid=doubleclick_int.
    • For Retargeting campaigns make sure your network link contains is_retargeting=true. Learn more 

    Attribution link example:

    Android iOS
    https://app.appsflyer.com/com.example?pid=rocketfuel_int&c=campaign_name
    &advertising_id=13******-****-****-****-54**********
  3. Append the AppsFlyer attribution link to the CM360 link:
    Android iOS
    https://ad.doubleclick.net/ddm/trackclk/N736113.127733/B202683.204586115;
    dc_trk_aid=404426918;dc_trk_cid=92566356;dc_lat=;dc_rdid=13******-****-****-****-54**********
    ?https://app.appsflyer.com/com.example?pid=rocketfuel_int
    &c=campaign_name&advertising_id=13******-****-****-****-54**********

Using the attribution link

Once you have the attribution link, make sure it is used while running ads on your intended media source. When an install occurs, AppsFlyer attributes the install to the selected media source. AppsFlyer then lets CM360 know about the install via postback mechanism, using floodlight parameters used when configuring the integration.

The end result is an install that is attributed to the media source, and an install that is registered in DCM360.

CM360 token parameter

A fourth parameter called token is also required. A token is an advertiser-specific alphanumeric string that must be passed along with each server request to GMP Digital Marketing (DDM.) To retrieve this token, you must enable third-party mobile in-app conversion recording at the advertiser (Floodlight configuration) level:

  1. Go to the Floodlight configuration tab
  2. In the Server to server section, enable In-app attribution recording

    DCM_enable.png

  3. Click New Token to generate a token, then enter a name (i.e. App Install - AppsFlyer).
  4. Click Save.
  5. CM360 (DCM360) generates values for the new token.
  6. Use this token when integrating Google Marketing Platform with AppsFlyer.

Limitations

As per Google’s no-redirect policy, third-party solutions such as OneLink cannot be relied upon in the CM360 + media source scenario.

Was this article helpful?