- The Criteo OneTag includes a set of safety and quality mechanisms to ensure that there will not be a negative impact on the user’s browsing behavior and that user's privacy is protected.
- This article explains how Criteo ensures that the OneTag is not affecting website performance and load time.
- We'll explain how Criteo ensures privacy and anonymity of the advertiser and customer.
Read more about the generic behavior of OneTag at Criteo OneTag HTTP/HTTPS calls explained
Compressed calls via HTTP-GZIP
All calls made to Criteo are HTTP-GZIP compressed to ensure a quick interaction between the user and Criteo’s data centers.
The OneTag has been designed to work in an asynchronous way to avoid any WAIT states which might interfere and slow down the user’s browsing experience.
The initial tracking-request will be made as soon as the Criteo request has been fulfilled. All possible further requests triggered by the OneTag will only be made after the Browser has successfully downloaded all primary resources including images, script files, CSS files, etc. from your website.
Example Criteo Calls – Inventory selection and Publisher calls are made after LOAD (red line)
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.
Loading Time Thresholds
Time limitations are put in place to make sure the entire loading time does not exceed a certain threshold. All requests triggered by Criteo will immediately stop once the threshold has been reached.
Smart Inventory Selection
We do 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 inventory selection if tests are not passed completely.
Device / Bandwidth Detection
The Criteo OneTag considers the current device of the user and the latency and bandwidth of the users connection. Depending on that, the thresholds and the potential number of requests will be more strict.
Loading & 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 5 data centers worldwide with exceptional availability (up time). In 2012, our availability average was 99.97% in the United States of America.
This request will be processed by our servers before they respond but the request is asynchronous so 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.
Similarly to 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 issue related to that please get in touch with your Criteo Account Strategist.