DoubleClick Campaign Manager Integration

DoubleClick Campaign Manager can be thought of as an ad server or a different way to give creative tags to a publisher.  Some advertisers want to use DCM to “traffic” campaigns.  If they want to run network campaigns through DoubleClick Campaign Manager, they must ensure that the network’s macros are correctly expanded - the pid=network URLs are used and not pid=doubleclick_int.  This can be completed by mapping the macros (typically requires a DoubleClick rep) or by using a static URL and appending the AppsFlyer URL using a semicolon.  For example:

http://123.4567.89;www.appsflyer.com?pid=network&c=campaign&param={macro}

For details of how to configure DoubleClick Campaign Manager, refer to the article here.

Install Configuration

AppsFlyer automatically receives the below parameters from DoubleClick and you can see this information in the Install Postback Reports.  

NOTE:  These parameters apply to DCM only.  We do not support DBM parameters at this time. For example, Site ID refers to the network level site configured in DCM, not to the site where the impression is served in DBM.  

Integration Types

Two types of integration can be performed with DCM:

Integration 1: Directly through DCM/Publishers

Requires Floodlight set up & AppsFlyer URL

Integration 2: Through another network

Run a network tracking link - DoubleClick and AppsFlyer both perform attribution

Setting a Tracking URL for DoubleClick Campaign Manager

There are two methods for setting up a tracking URL.  

Step 1:  Generate the AppsFlyer Tracking URL

The tracking link should contain the real media source you use, and not DoubleClick. For example, if you are running through Rocketfuel, use “pid=rocketfuel_int” and not “pid=doubleclick_int” :

https://app.appsflyer.com/{app_id}?pid=rocketfuel_int&c=campaign&param={macro}

AppsFlyer receives the parameters from the DoubleClick tracking URL and this can be reviewed in the raw data install report.  

Step 2: Append the AppsFlyer Tracking URL to DoubleClick Tracking URL

There are two methods for setting up a tracking URL. An advertiser can choose to run with DoubleClick Static URLs and with DoubleClick Dynamic URLs. Please work with a DoubleClick representative on this.

Method 1: DoubleClick Static URLs

Please append AppsFlyer’s Tracking URL with exposed macros (generated from Step 1) to DoubleClick’s Static URL.

For example:  

https://www.dbcm.com/93827:89734:18974;https://app.appsflyer.com/{app_id}?pid=rocketfuel_int&c=campaign&param={macro}

Method 2: DoubleClick Dynamic URLs

DoubleClick supports redirecting to AppsFlyer tracking links and populates parameters through dynamic values. Dynamic values in DoubleClick tracking links are created with ‘%’ parameters, it will redirect to AppsFlyer tracking links with the associated ‘%’ parameters.

For example:

http://doubleclick.com/idfa=%E&clickid=%F

—> Redirects to

https://app.appsflyer.com/{app_id}?pid=rocketfuel_int&c=campaign&idfa={%E}&click_id={%F}

NOTES:  

  • It is highly recommended to work with a DoubleClick representative on this set-up.
  • Method 1 is the most popular and preferred method since Dynamic URL creates more discrepancies.
 

Android / iOS

u1=

af device id

u2=

customer user id

u3=

Android:  advertising id

iOS:  idfa

u4=

wifi

u5=

carrier

u6=

country code

u7=

region

u8=

city

u9=

device type

u10=

os version

u11=

sdk version

u12=

app version

u13=

install timestamp


If you want to see any of the above parameters in your DoubleClick dashboard simply map them in the DoubleClick UI.

Example:

If you want to see the device type, simply map it under u9 on the DoubleClick dashboard.

In-App Event Configuration

In DoubleClick, in-app events are also configured as activities. In the DoubleClick system, you can follow the same configuration steps as you would to create your install floodlight.

In the Appsflyer dashboard:

Map the in-app events you want to send to DoubleClick.

  1. Click Integrated Partners
  2. In the Integrated Partners Configuration page, search for and select DoubleClick as the partner
  3. Click the In-App Event tab
  4. When configuring the in-app event you must re-insert the following parameters under the appropriate In-App Events Mapping heading, taken from the DoubleClick dashboard:

    * Token
    * Src
    * Cat
    * Type

The format should be set as below:

token=DBM_tokenID&type=DBM_typeID&cat=DBM_catparam&src=DBM_srcID

NOTE: All parameters (token, type, src, cat)  are mandatory for each In App event.

  1. Click +Click to add in app event mapping and map the events you want to send to DoubleClick
  2. Click Save & close.

AppsFlyer only supports sending additional U parameters up to U26.  Since they are pre-mapped, no additional custom U parameters can be configured.  

For every in-app event AppsFlyer sends the following floodlights:

 

Android / iOS

u1=

af device id

u2=

customer user id

u3=

Android: Advertising id

iOS:  idfa

u4=

wifi

u5=

carrier

u6=

country code

u7=

Region

u8=

city

u9=

device type

u10=

os version

u11=

sdk version

u12=

app version

u13=

install timestamp

u14=

click time

u15=

impression time

u16=

campaign name*

u17=

campaign id

u18=

adset name*

u19=

adset id

u20=

ad name*

u21=

ad id

u22=

site id

u23=

event time

u24=

event name

u25=

event value**

u26=

currency

Example: If you want to see the country code in DoubleClick, simply map it under u6 on the DoubleClick dashboard.

*In such cases AppsFlyer does not receive the name and therefore populates the field with the corresponding ID (i.e. Adset name becomes adset ID).

If you want to see any of the above parameters in your DoubleClick dashboard simply map them in the DoubleClick dashboard.

** AppsFlyer only sends the eventValue=amount, but for many events the client may have configured a complete JSON body with attributes.  DoubleClick does not support us sending the whole JSON body for the eventValue, only the defined event value amount.

Example:

If you want to see the country code simply map it under u6 on the DoubleClick dashboard.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk