All potential publisher calls are triggered as an image-request within an iFrame. This ensures that 3rd parties cannot place or read data on your website.
Smart inventory selection
We identify the most relevant publisher networks for the current users and also keep records of which publishers have already been informed of the current user. This way we make sure there are no redundant requests.
A user who interacted with Criteo in the past will see much less publisher tagging calls.
New users will see the maximum number of calls. Most monitoring and performance systems fall into the ‘new user’ category and because of that don’t reflect a realistic user browsing experience.
Publisher service monitoring
All publisher services are tested periodically and monitored 24/7 by Criteo around the globe. Loading times, response types, certificates, etc. are being monitored and checked constantly. Publishers are automatically removed from the inventory selection if tests are not passed completely.
Loading and uptime of datacenters
This request (down)loads a file hosted in our data centers, there is no processing time between the request and the response. We have five data centers worldwide with exceptional availability (uptime).
This request will be processed by our servers before they respond but the request is asynchronous. This means that the content of your website will continue to load as the browser waits for the response. Regardless, our average response time is only 25 milliseconds and our infrastructure team monitors latency 24/7 so that incidents are resolved within minutes.
Much like the Event, this request is asynchronous, and our average response time is only 50 milliseconds. Our servers’ latency is also monitored 24/7. Most importantly, we only begin to tag users for publishers once the onLoad event has been reached and the page is fully usable for your visitors. This means that our tags will not affect the perceived load time of pages on your site.
Can certain publisher calls be removed?
It is not possible to remove specific publisher calls, except if there are technical issues. This case will result in a global deactivation as explained above. In case of issues related to that please get in touch with your Criteo contact.
Criteo OneTag HTTP/HTTPS calls explained
The Criteo OneTag allows us to know who to retarget and what to recommend to them across our network of publishers. A smart algorithm evaluates where the user can be approached in the most efficient way. As a result, 3rd-party HTTP calls may be made. No personal or advertiser-related information is shared with other vendors.
What calls are triggered by the OneTag?
When our tag fires on one of your pages, it results in a call to our loader and three main HTTP requests: a request from the user's browser to our servers and HTTP requests to our publisher partner’s ad servers. All requests are asynchronous.
- The second call is the actual tracking event. This event sends the user-browsing information to our servers such as which products are currently being looked at
- The third call request is for inventory selection. This call builds a list of all relevant publishers from our server
- Depending on the result of the inventory selection call, publisher http-calls might be made. This is when publishers are informed that we would like to show ads to the current user whenever they browse the publisher’s network. These requests are made as image-requests and are therefore also called 3rd-party pixels
FLoC IDsProposed by Google as an audience targeting scenario for the Chrome web browser, FLoC, or “Federated Learning of Cohorts” creates lookalike audiences based on machine learning. Google began testing FLoC as a replacement for third-party cookies in March 2021.
Criteo will be collecting FLoC IDs on a portion of the traffic in eligible countries (Australia, Brazil, Canada, India, Indonesia, Japan, Mexico, New Zealand, Philippines, and the U.S.) during the trial period set by Google.
For more information on FLoC, visit https://web.dev/floc/