Criteo
Enable Criteo with Branch to power your mobile attribution.
![RTB House + branch.png 1328](https://files.readme.io/6133e7f-Criteo_Branch_Logo.png)
Overview
Criteo helps advertisers, retailers, and publishers activate and monetize audiences everywhere shoppable moments happen.
Partner Capabilities
Capability | Details |
---|---|
Company Type | Contact support at Criteo for more information |
Deep Linking | Supported |
Attribution |
|
Ad Campaign Types |
|
Ad Formats |
|
Click Types |
|
Supported Platforms |
|
Link Wrapping | Supported |
Cost Ingestion Support | Supported |
Cost Ingestion Types |
|
Cost Time Zone | GMT |
Cost Data Scheduling |
|
Pricing Models |
|
Prerequisites
In order to enable Criteo, you need to have completed the following:
- Created a Branch Dashboard.
- Enabled Universal Ads for your Branch account.
- Contact your Branch account manager or visit https://branch.io/pricing
- Implemented the Branch SDK into your mobile app (iOS | Android)
- Running campaigns through Criteo.
Enable Criteo
1. Enable Criteo in Branch
In the Branch Dashboard under Ads > Partner Management, find/search for Criteo. If you're already logged into the Branch Dashboard, you can also click here to go there directly.
Click the Save & Enable button.
![RTB House enable.png](https://files.readme.io/9db0a28-Enable_Criteo.png)
2. Configure Postbacks
Enabling Criteo will automatically enable the following postbacks:
- INSTALL
- OPEN
- PURCHASE
![rtb house postbacks.png](https://files.readme.io/9e00a57-Criteo_Postbacks.png)
You can configure these postbacks or add more under the Postback Config tab.
Send All Events
Optionally, you can check the checkbox for a given postback for sending all events. When checked, all events will be sent regardless of attribution. Otherwise, the postback will only fire for events attributed to Criteo.
Adding Postbacks
Click the Add New Postback button at the bottom of the screen. A modal will appear that will allow you to select an event that you are tracking with the Branch SDKs (including Custom Events).
For more in-depth postback configurations, view our guides:
3. Configure Attribution Windows
After configuring your events, navigate to the Attribution Windows tab to set windows by attribution type.
Recommended Attribution Windows
Attribution Type | Window |
---|---|
click to session start | 90 days |
click to install | 30 days |
click to conversion event | 90 days |
impression to session start | 1 day |
impression to install | 1 day |
impression to conversion event. | 1 day |
4. Set up Cost Data
Beta for Non-SANs
Cost Data for Non-Self-Attributing Networks (Non-SANs) is a feature currently in Beta; be aware that there may be unexpected bugs/behaviors until the full release.
To set up cost ingestion for Criteo, you will need to authenticate using your User Name and Password. Please reach out to your Criteo account manager if you have trouble finding these values.
Enter your User Name and Password, and click Save Authentication
![](https://files.readme.io/6c21196-Criteo_Cost_Authentication.png)
5. Create Branch Ad Link
Next, you'll need to create a Branch Ad Link for your Criteo campaigns in order for Branch to properly attribute conversions.
The Branch Ad Link you create will be placed in your Criteo campaign.
6. Verify Data in Branch
After launching your Criteo campaigns, and conversions begin to happen, you'll want to verify data is being sent from Branch to Criteo. You can look at the Branch Dashboard's Liveview Webhook Records and apply the following filter:
Filter | Operator | Value |
---|---|---|
ad partner (3p) | equals | a_criteo |
Once applied, data should flow through the Liveview, and you can see the data being sent to Criteo from Branch.
Verifying Cost Data
To verify that cost data is flowing into Branch, you need to have the following:
- Completed all implementation steps above
- You need to already be live with campaigns running for the ad network
- Wait 24 hours for data to be pulled in
Updated 2 months ago