Sign in

Welcome to our Support Center

Get help with integration and live campaigns

Welcome to our Support Center. Get help with integration and live campaigns

Very low number of hits or no hits

Overview

Every time the Criteo OneTag is fired, Criteo receives an event with all the parameters passed in the tag; this is called a hit. If no hits are received by Criteo, it means there is an issue with the implementation of the Criteo OneTag.
The number of hits per page recorded by the Criteo OneTag on your site (Homepage, Search Listing, Product, Basket and Sales Confirmation pages) must match the number of hits/page views as recorded by Google Analytics or similar. If there is a discrepancy  it means that not all page views are being recorded correctly and you will need to perform the following troubleshooting steps.

Troubleshooting

Ensure that the Criteo OneTag is implemented in a live environment because test environments do not generate enough hits for accurate analysis.
Browse your site's pages where the Criteo OneTag has been implemented (Homepage, Search Listing, Product, Basket and Sales Confirmation pages), particularly those where no, or a low number of hits are reported, then do the following checks:

Is the Criteo loader being executed?

Without the loader Criteo OneTag cannot be fired, so you must check that the loader is executed correctly:

1. Open the Network panel.
If you are using Google Chrome, Mozilla Firefox or Internet Explorer, press F12 on the keyboard, reload the page (F5), and then click on Network on the pop-up as shown in the image below.

2. Look for Criteo related network activity.
Click on the Network panel and press Ctrl+F to open the search bar

3. Search "criteo" and try to find a network activity entry like the one below showing ld.js

4. If you don't find this entry, reload the page and try again.

5. If you still can't find the ld.js entry you must double check:

  • If you are implementing the Criteo OneTag directly into the source code of your website you must check that the JavaScript loader (see the below code) is included at the beginning of the Criteo OneTag and that it's not being blocked by any other element of the code.
    Criteo Loader:
     <script type="text/javascript" src="//static.criteo.net/js/ld/ld.js" async="true"></script>
  • If you are implementing the Criteo OneTag via Google Tag Manager, please ensure your triggers are correctly defined and the Google Tag Manager dataLayer contains the required information used in those Triggers.

Is the Criteo OneTag being fired correctly?

After verifying that the loader is executing correctly, you will need to perform a similar check to confirm that there is an event call being made to Criteo.

1. Using the network panel, search for an entry starting with "event?a=" as shown in the image below.

2. If you don't find this entry, reload the page and repeat the search.

3. If you still can't find the entry starting with "event?a=" it means that the Criteo OneTag is not being executed and you will need to review the implementation of the Criteo OneTag. Detailed information on how to set-up the Criteo OneTag correctly can be found here.

Common issues when implementing the Criteo OneTag:

  • Account parameter has been modified
    Double check that the account parameter is exactly the same as the one that you get from the Integrate platform.
    Account ID declaration:
     { event: "setAccount", account: YOUR UNIQUE ACCOUND ID },
  • Missing brackets, parentheses, square brackets or quotes
    If brackets, parentheses, square brackets or quotes are not opened or closed correctly, the Criteo OneTag code will be broken, generating JavaScript errors. Please ensure that all parentheses "(" , brackets "{" and square brackets "[" and quotes are entered exactly as shown in the Criteo OneTag code that you get from Integrate platform.
Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk