DoubleClick Integration

Using AppsFlyer to attribute conversions from your Google DoubleClick campaigns is simple and easy to use. When you view an ad for a mobile app and then click on it, DoubleClick records the ad click in their system. When the mobile app is installed, the AppsFlyer SDK queries DoubleClick at the first app open to determine if the install can be attributed to them.  

You can use the Appsflyer DoubleClick setup to report on campaigns run in both DoubleClick Campaign Manager and DoubleClick Bid Manager.  Make sure your DoubleClick campaign is set-up correctly for tracking in-app attributions. See the DoubleClick support pages for more information.  

NOTE:  These support pages require a login to the DoubleClick UI to access:

DoubleClick Campaign Manager

DoubleClick Bid Manager 

DoubleClick Configuration

To set-up a campaign and enable the integration between DoubleClick and AppsFlyer, follow these steps:

1. Click Integrated Partners on the left side of the screen.

 

2. In the Integrated Partners page, select DoubleClick as the partner, either by scrolling down the page to DoubleClick or entering DoubleClick in the search filter. 

3. Click the DoubleClick logo to open the DoubleClick Configuration window.

Doubleclick_new_1a.png  

4. Please disregard the campaign field as this is not used. 

5.  Set the Click-Through lookback period by moving the slider according to your preference. DoubleClick's default lookback click-through window is 30 days.  To minimize discrepancies, it is recommended to use this time period.

6.  Define the Integration Parameters

  • token is an advertiser-specific alphanumeric string that must be transferred with each server request to DBM
  • src is the advertiser ID that is the source of the Floodlight activity.
    NOTE
    : For DBM clients, this is the src= parameter in the floodlight tag you export from the ‘Pixel’ setup screen, not the DBM advertiser ID Added clarification for DBM clients
  • cat is the activity tag string, used by Floodlight servers to identify the activity group to which the activity belongs
  • type is the group tag string, it identifies the activity group with which the Floodlight activity is associated

7.  Select Enable to activate View-Through attribution.

8.  Move the slider according to your lookback time preference.  DoubleClick's default lookback view-through window is 14 days.  To minimize discrepancies, it is recommended to use seven days (the maximum available) on AppsFlyer.

9.  Copy both the Tracking Link and the View-Through Tracking Link and paste them into the designated place in DoubleClick's configuration page.

10.  Click Save & Close

NOTE: AppsFlyer is not using the click data when attributing installs to DoubleClick.   

Re-Targeting

If you are running re-targeting campaigns on DoubleClick click the DoubleClick Retargeting toggle to on.

Then define the scr, type, token and cat parameters specific to your re-targeting campaigns. 

NOTE:  Since AppsFlyer has server-to-server integration with DoubleClick, the is_retargeting=true parameter does not appear in the tracking link and there is no need to copy it.

Doubleclick_new_1a.png

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. 

Added clarification for FAQ

  • PlacementID becomes af_c_id, c
  • Ad ID becomes af_adset_id, af_adset
  • Creative ID becomes af_ad, af_ad_id
  • Site ID becomes af_siteid

Moreover, for every install, AppsFlyer sends the following floodlights:

 

Android

iOS

u1=

af device id

af device id

u2=

customer user id

customer user id

u3=

advertising id

idfa

u4=

wifi

wifi

u5=

carrier

carrier

u6=

country code

country code

u7=

region

region

u8=

city

city

u9=

device type

device type

u10=

os version

os version

u11=

sdk version

sdk version

u12=

app version

app version

u13=

install timestamp

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:

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.

5. Click +Click to add in app event mapping and map the events you want to send to DoubleClick

6. Click Save & close.

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

 

Android

iOS

u1=

af device id

af device id

u2=

customer user id

customer user id

u3=

advertising id

idfa

u4=

wifi

wifi

u5=

carrier

carrier

u6=

country code

country code

u7=

Region

Region

u8=

city

city

u9=

device type

device type

u10=

os version

os version

u11=

sdk version

sdk version

u12=

app version

app version

u13=

install timestamp

install timestamp

u14=

click time

click time

u15=

impression time

impression time

u16=

campaign name*

campaign name*

u17=

campaign id

campaign id

u18=

adset name*

adset name*

u19=

adset id

adset id

u20=

ad name*

ad name*

u21=

ad id

ad id

u22=

site id

site id

u23=

event time

event time

u24=

event name

event name

u25=

event value

event value

u26=

currency

currency

*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 UI.

Example:

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

General Advice

It is possible for some conversion events to be discarded from the DoubleClick system as invalid/spam activity after they have posted their attribution response to Appsflyer. In these cases, Appsflyer may report on these events, but DoubleClick will not. If you see high numbers of conversions reported in Appsflyer that are missing from DoubleClick, we recommend running a DoubleClick report on invalid activity to determine whether there is an issue with your inventory. 

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