Tracking DoubleClick campaigns

AppMetrica detects DoubleClick advertising campaigns by using DoubleClick Floodlight.

This section explains the steps for setting up AppMetrica tracking to work with DoubleClick ad campaigns.

Step 1. General settings

1. In the AppMetrica interface, go to Tracking → Add tracker.

2. Enter the name of the tracker.

3. Select DoubleClick as the media source.

4. Specify Main as the tracker type.

5. Fill in the information:

   • src — The Advertiser ID. If you use DoubleClick Bid Manager, take the src value from the Floodlight tag settings. The value can be found in the Pixel setup screen.
   • type — The value that identifies the activity group, with which the Floodlight activity is associated.
   • token — The advertiser-specific string. It is transferred with each reqest to the DoubleClick Bid Manager server.
   • cat — The tag that used by Floodlight servers.

Step 2. (Optional) Configure attribution

This attribution type correctly detects the source that brought users to your app and accurately links app installs to ad interactions, whether they're a click or an impression.

For more information about attribution methods, see AppMetrica tracking technology and Impression attribution.

• Reattribution — Attribution of reinstalls by pre-existing users. This option is disabled by default. For more information, see Attributing app installs.

  For test devices, reattribution is always enabled (regardless of the option status). For more information about adding test devices, see Testing attribution.

• Setting up clicks

  Specify the attribution window: this is the period between the click and the install during which the action will be attributed to the campaign.

• Impression attribution, also known as post-view attribution or view-through attribution (VTA), accounts for cases where a user didn't navigate to the app store by clicking an ad but still installed your app shortly after viewing it. The option is enabled by default. For more information, see Impression attribution.

Step 3. (Optional) Configure postbacks

A postback is a request to the media source's server sent via a set link (postback URL). The request transmits data about a conversion that occurred in the app.

Postbacks are typically used when running CPI/CPA campaigns. You can add up to 10 postbacks per tracker.

If you have default postbacks configured for the selected media source, they're automatically added to the tracker. You can disable these postbacks, add templates that exist for the media source and are disabled by default, or create new ones.

For media source, postbacks for all sources can also be configured — they allow you to send event data to the media source regardless of whether the user was acquired through advertising or organically. Such postbacks are not linked to specific trackers. You can view them on the media source page.

1. Select the conversion for which you want to send a postback, then choose a sending method (POST or GET).

2. Generate a postback URL.

   To transmit additional information about the event to the media source, use macros when generating the URL.

   Some media sources can set a permanent Postback URL for their network. In this case, the postback is sent to the media source regardless of other settings. It can't be edited.

Step 4. (Optional) Configure anti-fraud

Enable FraudScore to check installs and events for fraud via FraudScore.

FraudScore is a paid option (Pricing plans) only available for legal entities registered in Russia.

Step 5. Save your changes

Click Save at the bottom of the page.

On the right, you can find the tracker's Tracking ID.

Learn more

• About Floodlight

If you didn't find the answer you were looking for, you can use the feedback form to submit your question. Please describe the problem in as much detail as possible. Attach a screenshot if possible.