Set up Criteo B
Criteo B is an ad network integrated with Adjust. Our integration lets Criteo B receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with Criteo B for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Criteo B.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Criteo B parameters. Follow the guides linked below to use this feature.
iOS | Android | Windows | Unity | React Native | Flutter | Adobe Air | Cordova | Marmalade | Xamarin | Cocos2d-x | Titanium | Corona
Credentials
API_KEY
- For help finding your credentials, contact your Criteo B representative.
Select Criteo B and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Criteo B. Select Next to move to the next screen.
- In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with Criteo B.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Criteo B. To enable data sharing:
- Enter your API_KEY.
Once you enable data sharing with Criteo B, Adjust automatically sends Criteo B the following data, by default:
- install
- session
- event
- rejectedInstall
Set your data sharing options
If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:
- Separate data sharing options at the platform-level by selecting Use platform-specific settings.
- Set the same data sharing settings for multiple platforms by selecting Use global settings.
Now, under What will be shared by default?, review the activities that Adjust shares with Criteo B by default.
- install
- session
- event
- rejectedInstall
Send additional data
Choose the amount and type of data that you want to share with Criteo B through callbacks. Criteo B may use this information to optimize performance.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets Criteo B receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.
Map events
Map events that you want to share to the values that Criteo B can receive. Data for unmapped events is not shared with Criteo B.
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with Criteo B. This lets you:
- Set individual events to manage campaign strategies for each platform.
- Customize data sharing per platform.
Under Map events, follow these steps to choose the in-app events you want to directly send to Criteo B.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with Criteo B.
- Under Partner event, you need to select the Criteo B event that corresponds to the Adjust event.
- For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
- Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
- Select Use global mapping to map the same events for all platforms.
- In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
- For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
- Select Apply.
Now Criteo B will receive in-app event data for each of your linked events.
Map all events
If Criteo B supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now Criteo B will receive in-app event data for all your linked events.
Configure your link and settings
You have the option to set your:
Create your link and share it with Criteo B
In the Setup review screen, you can review your choices. You can also go back and make changes to:
- Your selected app
- Data sharing options
- Link structure parameters
- User destinations
- Attribution settings
Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with Criteo B.
Once you’ve created your link, share it with Criteo B for placement in campaigns.
List of all parameters forwarded to Criteo B
Criteo B requires Adjust to send the following parameters (data points) with your callbacks:
| Placeholder | Information |
{adid} | Adjust device ID (all platforms) |
{city} | Device city |
{click_attribution_window} | Attribution window settings for device matching (hours) |
{country} | Device two-character country code |
{currency} | Original ISO 4217 currency code sent from Adjust SDK |
{deeplink} | Deeplink URL appended to click URL |
{device_name} | Device model number |
{device_type} | Device type |
{environment} | Current Adjust SDK environment setting |
{event_name} | Event name, as set in the Dashboard |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{idfv} | Uppercase iOS ID for vendors |
{impression_attribution_window} | Attribution window settings for impression matching (hours) |
{ip_address} | Device IP address |
{is_reattributed} | 1 if user was reattributed at least once from an earlier source. 0 if user has never been reattributed |
{isp} | Device internet service provider |
{language} | Device two-character language code |
{lifetime_session_count} | Number of sessions recorded across entire user lifetime |
{match_type} | Attribution method |
{mcc} | Mobile country code: three-digit code identifying a device's country. Use with the mobile network code to identify a device's carrier. |
{mnc} | Mobile network code: two-digit code. Use with the mobile country code to identify a device's carrier. |
{os_name} | Device operating system |
{os_version} | Operating system version number |
{partner_parameters} | Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks |
{revenue_float} | Revenue, as sent from Adjust SDK, in whole currency units |
{revenue_usd} | Revenue, in US dollars |
{revenue} | Revenue, as sent from Adjust SDK in cents |
{sdk_version} | Adjust SDK version (per app) |
{tracking_enabled} | 1 if tracking is enabled, 0 if not |
{tracking_limited} | 1 if tracking is limited, 0 if not |
{user_agent} | Incoming raw user agent |
{win_udid} | Windows Phone unique device ID |
{activity_kind} | Type of user activity |
{adgroup_name} | Adgroup name, as taken from the tracker |
{app_id} | Store App ID or Google Play Store |
{app_name} | Name of the app |
{campaign_name} | Campaign name, as taken from the tracker |
{connection_type} | Internet connection type |
{cpu_type} | CPU type |
{creative_name} | Creative name, as taken from the tracker |
{device_manufacturer} | Device manufacturer name |
{hardware_name} | Hardware name |
{impression_based} | 1 if impression-based engagement, 0 if not |
{install_begin_time} | App download began timestamp (Android and Google Play Store only) |
{install_finish_time} | App download completion timestamp |
{installed_at} | Install (i.e., first app open) timestamp |
{is_organic} | 1 if organic traffic, 0 if non-organic |
{network_name} | Network name, as taken from the tracker |
{rejection_reason} | Reason for a rejected attribution |
{is_s2s} | 1 if server to server engagement, 0 if not |
{proxy_ip_address} | IP address of user's proxy |
{ad_mediation_platform} | Mediation platform name |