Skip to main content
Skip table of contents

Criteo Setup

This functionality is not available for trial customers

This guide helps you to connect fraud0 with your Criteo account.

1. Contact your Criteo Account Manager

Please request a Tag for Audience Exclusion from your Criteo account manager (the exclusion should be set globally for all campaigns).

Here is an example of what the tag could look like:

<script type="text/javascript">
window.criteo_q = window.criteo_q || [];
     { event: "setAccount", account: xxx },
     { event: "viewItem", item: "#ProductID#", userinfos:"frauduser" }

Please note

There are different tags from Criteo. Please use the one provided by your account manager.

2. Implement Tag in Google Tag Manager

  • Within the Tag Configuration section select Custom HTML. The Custom HTML Template will open next.

  • Give your tag a name (F0 Criteo) and paste your tracking code from the Microsoft UET tag into the HTML field. You will get the tracking code in the audience creation process described below.

  • In the Triggering section you need to assign the F0 Trigger you have created before.

Save the configuration

3. Add an exclusion for your already existing Criteo Tag

For your already existing Criteo Tag in Google Tag Manager, please add an exclusion for the fraud0 trigger – otherwise the exclusion will not work.

Please note

“All Pages” might not be the trigger you use for your Criteo tags – the following is just an example.

After 7 days, please double-check with your Criteo account manager whether events for Audience Exclusion are collected.

Next Steps

In the next steps, you can create Negative Audience lists for your other channels. Please have a look at our setup guides:

Google Ads Setup →

Facebook Business Manager Setup →

DV360 & Campaign Manager Setup →

Microsoft Ads / Bing Ads Setup →

Need support?

Do you still have questions or require further details? Contact our support team for assistance!

Send us an email →

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.