Bulletin: Google Marketing Platform (GMP) integration transition

What's new?

As part of preparations for enforcing the Digital Marketing Act (DMA), Google is updating its EU user consent policy. AppsFlyer is making the necessary changes to support Google’s policy requirements.

The following Google Marketing Platform (GMP) integrations are currently available:

During Q2 of 2024, Google and AppsFlyer will be deprecating the legacy doubleclick_int integration. If you're using this integration, you'll need to transition to the new DV360 integration to continue running campaigns and measuring them using GMP.

Action required

Transition to the new DV360 dv360_int integration as soon as possible, before the end of Q2 2024.

Steps to take

Make sure to configure both platforms, GMP and AppsFlyer:

Configure in GMP

  1. Log in to your CM360 or DV360 account.
    Note: Completing the steps in CM360 negates the need for completing them in DV360.
  2. Create or reuse your partner attribution link (Link ID) using these instructions

Configure in AppsFlyer

  1. Complete your DV360 integration in AppsFlyer using these instructions
    Note: To maintain data consistency, make sure the configuration is similar to the legacy integration (lookback windows, in-app event postbacks, etc).
  2. Test the new integration: 
    Wait for about a day to confirm the new integration data. You can then disable the legacy integration.

What you must know


Considerations Available options

Media source PID

After completing the migration, the DV360 media source PID changes from doubleclick_int to dv360_int.

If you're pulling raw data from AppsFlyer into your BI or any 3rd party analytics tool, consider the change in the media source name.

Out-of-store apps

Apps from unofficial app stores aren't supported in the DV360 integration. The integration relies on a link ID, which is generated for apps obtained through official app stores.

If your app is downloaded from sources outside official app stores, contact your CSM or hello@appsflyer.com.

Attribution data distribution

When both integrations are active and claim attribution for installs, attribution is randomly split between them, with one being the primary source and the other acting as a contributor. This ensures data isn't duplicated. For example, if DV360 is responsible for 100 installs, you might see 70 installs from the legacy integration and 30 from DV360, or 80 installs from DV360 and 20 installs from the legacy integration.
In-app events for installs/re-engagements attributed to the legacy integration remain credited accordingly.


Re-engagement attribution is supported in the DV360 integration.

Field discrepancies

Due to differences between available data fields in the legacy and updated APIs, you may see differences in some AppsFlyer fields, as seen below:

AppsFlyer field Legacy field (doubleclick_int) DV360 field (dv360_int)
Campaign name placement_id line_item_name
Campaign ID placement_id line_item_id
Adset name ad_id NA (not supported)
Adset ID ad_id NA (not supported)
Ad name creative_id NA (not supported)
Ad ID creative_id creative_id