How to Measure Criteo Campaigns in Appsflyer

Introduction

This article is intended as a guide for advertisers who are working with AppsFlyer and Criteo.

When you complete the setup, we highly recommend that you test all the different types of retargeting in a testing environment, as well as in live production by following the steps outlined in this article.

Android

Step 1: SDK Configuration

AppsFlyer - Criteo integration is available for SDK version: 3.0 and above. The integration guide can be found here.

1.1  Support Deep Linking and Reporting Deep Link to AppsFlyer (Mandatory)

To run retargeting campaigns with Criteo you must support Deep Linking functionality - more information can be found here under the Deep Link section.

To report Deep Linking to AppsFlyer, follow the guidelines here, under the Reporting Deep Links for Retargeting Attribution.

 Note

If you already configured this in the past AppsFlyer automatically pulls the scheme from the Onelink configuration and append it to Criteo's tracking links.


1.2  Rich In-App Events Mapping

For the rich in-app events mapping to work follow specific guidelines per event.
Click here for more information.

 Important Note

If you do not follow the instructions for mapping rich in-app events to the respective Criteo attributed mapping, postbacks will fail.


1.3  Collecting User Emails 

For information on Collecting User Emails view the relevant section in this article.

Step 2:  Tracking + In-App Events Configuration 

Criteo tracking link redirect URLs must include the following parameters for AppsFlyer to be able to attribute conversions to Criteo:

Parameter Description
&pid=criteonew_int Pre-fixed to define that Criteo is the Deep Link source
&c={campaign.name} Variable
&af_reeengagement_window=30d As the default window is set up to 30 days by AppsFlyer even when the parameter does not appear on the URL
&is_retargeting=true

Value = True or False

These parameters are automatically added to the tracking links once the retargeting campaign checkbox is enabled.

For detailed information of how to set up the campaign with Criteoת follow the guidelines here.

iOS

Step 1:  SDK Configuration

AppsFlyer - Criteo integration is available for SDK version: 3.0 and above. The integration guide can be found here

1.1 Support Deep Linking and Reporting Deep Linking to AppsFlyer (Mandatory)

To run retargeting campaigns with Criteo you must support Deep Linking functionality - more information can be found here under the Deep Link section

To report Deep Linking to AppsFlyer, follow the guidelines here under the Reporting Deep Links for Retargeting Attribution.

 Note

If you already configured this in the past AppsFlyer automatically pulls the scheme from the Onelink configuration and append it to Criteo's tracking links.

1.2  Rich In-App Events Mapping

For the rich in-app events mapping to work follow specific guidelines per event.
Click here for more information.

 Note

If you do not follow the guide lines for mapping of rich in-app events to the respective Criteo attributed mapping, postbacks will fail.

1.3  Collecting User Emails

For information on Collecting User Emails view the relevant section in this article. 

Step 2:  Tracking + In-App Events Configuration

Criteo tracking link redirect URLs must include the following parameters for AppsFlyer to be able to attribute conversions to Criteo:

Parameter Description
&pid=criteonew_int Pre-fixed to define that Criteo is the Deep Link source
&c={campaign.name} Variable
&af_reeengagement_window=30d As the default window is set up to 30 days by AppsFlyer even when the parameter does not appear on the URL
&is_retargeting=true

Value = True or False

These parameters are automatically added to the tracking links once the retargeting campaign checkbox is enabled. For detailed information of how to set the campaign with Criteo please follow the guidelines here.

Was this article helpful?
0 out of 0 found this helpful