Track app conversion with Floodlight and server to server (S2S)

If you choose not to use Google Tag Manager (GTM), you can implement direct Floodlight calls either within your advertiser's app or via a server-to-server call to report on conversion activities directly without the use of a tag management solution.

Instructions

1. Navigate to your advertiser, and go to Resources and click Floodlight group.
2. Under the "Floodlight activities" tab, click New Floodlight activity.
3. Configure your Floodlight activity, then click Save.
4. In your Floodlight activity’s page, click the Code tab.
5. Copy the "doubleclick.net" URL from your iframe tag, image tag, or event snippet (depending on your Floodlight activity’s tag format).
6. Share the URL with your advertiser's app developer or webmaster to implement as a server-side GET request.

Get a tag's code

To get a tag's code, navigate to your advertiser's Floodlight activity page, and click the Code tab inside your conversion tracking Floodlight activity.

Technical information

GET requests to Floodlight (from an app or server to server call) are made to the following URL:

https://ad.doubleclick.net/ddm/activity/src=1234567;cat=fghij456;type=abcde123;dc_rdid=38400000-8cf0-11bd-b23e-10b96e4ddddd;u1=[friendlyname1];ord=1312312312

where:

• dc_rdid is the IDFA or Android advertising ID which must be passed over SSL.

• src is the advertiser ID that is the source of the Floodlight activity.

• cat is the activity tag string, which Floodlight servers use to identify the activity group to which the activity belongs.

• type is the group tag string, which identifies the activity group with which the Floodlight activity is associated.

• ord is a random number that is used to make the Floodlight tag unique and prevent browser caching.

• u1, u2, ... (if available) are the custom Floodlight variable key-values.

• tag_for_child_directed_treatment=[0|1] (if available) is a flag (with a value of 1) indicating that this particular request may come from a user under the age of 13, under COPPA compliance.

• tfua=[0|1] (if available) is a flag (with a value of 1) indicating that this particular request may come from a user under the age of 16 (may differ by country), under compliance with the EU’s General Data Protection Regulation (GDPR).​

• npa=[0|1] (if available) is a flag (with a value of 1) indicating that this particular request may come from a user who wishes to opt-out of remarketing. If missing or unpopulated, this field will default to 0.

• dc_lat=[0|1] (if available) is a flag (with a value of 1) indicating if the user has enabled the "Limit Ad Tracking" option for IDFA or Android Advertising ID. If missing or unpopulated, this field will default to 0.

Be sure that the necessary values are passed to key-values at serve time, particularly the required dc_rdid= value.

Make sure that the HTTP header user agent is the same as that of the app where the conversion activity took place. This is especially important if you've implemented a server-to-server call to Floodlight.