Search specific term/phrase surrounded by double quotes. e.g. “deep linking”
Exclude records that contain a specific term prefixed with a minus. e.g. Android -Firebase


Enable Criteo with Branch to power your mobile attribution.



Criteo helps advertisers, retailers, and publishers activate and monetize audiences everywhere shoppable moments happen.

Partner Capabilities



Company Type

Contact support at Criteo for more information

Deep Linking



  • Click-Through Attribution
  • View-Through Attribution

Ad Campaign Types

  • Retargeting campaigns

Ad Formats

  • Banner
  • Video

Click Types

  • Server-side click

Supported Platforms

  • iOS
  • Android
  • Windows
  • Mac OS
  • Unix

Link Wrapping


Cost Ingestion Support


Cost Ingestion Types

  • via API (Beta)
  • via Branch Ad Link
Cost Time ZoneGMT
Cost Data Scheduling
  • 4 times/day for Days 0-2
  • 1 time/day for Days 3-7
  • 1 time/week for Days 8-30

Pricing Models

  • CPC
  • CPM
  • CPA


In order to enable Criteo, you need to have completed the following:

  1. Created a Branch Dashboard.
  2. Enabled Universal Ads for your Branch account.
  3. Implemented the Branch SDK into your mobile app (iOS | Android)
  4. 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.

2. Configure Postbacks

Enabling Criteo will automatically enable the following postbacks:

  • OPEN

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 TypeWindow
click to session start90 days
click to install30 days
click to conversion event90 days
impression to session start1 day
impression to install1 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

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:

ad partner (3p)equalsa_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