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, then disable the legacy integration to prevent data duplication.
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.

Attribution data duplication

As long as both integrations are active in AppsFlyer, data duplication is expected.

To minimize data duplication, turn off the legacy integration promptly after validating initial data from the new 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.