Boost Your Criteo Campaign Performance: A Guide to Technical Setup and Troubleshooting

The success of your Criteo campaigns fundamentally depends on the quality and continuity of the data coming from your website. Criteo OneTag and the Product Catalog, the two main pillars of this ecosystem, enable your ads to show the right product to the right user.

Technical issues in the setup can result in low hit counts, data discrepancies, or incorrect matches, directly undermining your advertising performance. This article provides a step-by-step roadmap to help you perform your own checks and maintain campaign efficiency.

Criteo OneTag Check: Step-by-Step Manual Troubleshooting

Using the technical tools available in your browser can be highly useful for determining whether OneTag is working correctly.

Using the Network Panel

Go to your website and right-click on the page you want to inspect, then select “Inspect.”

Click the “Network” tab in the top menu and refresh the page.

Use Cmd+F (macOS) or Ctrl+F (Windows) to search.

Critical Checkpoints

ld.js (Loader): Type “criteo” into the search box. You should see ld.js, the Criteo loader, in the list. If it does not appear:

Direct Code Implementation: Check that the loader is placed at the beginning of the code and is not being blocked.

Google Tag Manager (GTM): Make sure the triggers are configured correctly and that the dataLayer contains the required information. More detailed information is available in this article.

E-commerce Platforms (Shopify, etc.): Check that your plugin is updated to the latest version. More detailed information is available in this article.

event?a= (Event Call): This is technically the most critical checkpoint. Even if the loader is working, the request beginning with event?a= is what confirms that data is actually reaching Criteo. If you cannot find this entry, the tag may be installed but is not being triggered.

Common Implementation Errors

Account ID Errors: The ID in the setAccount parameter must exactly match the partner ID assigned to you in the Criteo platform.

JavaScript Errors: Missing or incorrect parentheses (), curly brackets {}, or quotation marks ” can break the entire code structure. Errors are commonly concentrated around the criteo_q.push() function.

Events Tracking Panel and Status Analysis

The fastest and most reliable way to monitor the overall technical health of your Criteo OneTag integration is to use the Assets > Events Tracking menu directly in the Criteo platform. This panel provides the most reliable, visual, and easy-to-understand overview of the real-time status of your tags.

The Events Timeline by Type chart on this screen allows you to identify exactly when technical issues started and how long they have been ongoing.

This enables you to clearly analyze whether potential performance declines in your campaigns are linked to a technical interruption. The panel makes monitoring easier by classifying the health of your data transfer into three simple statuses:

Working: Everything is running as expected. Your setup is functioning properly, and your campaigns are receiving the data they need.

Optimization: Indicates areas where you can review your tag implementation and make improvements to further enhance campaign performance.

Issue: Indicates critical errors that may negatively affect campaign performance and should be resolved as soon as possible.

By clicking the download button in the Actions column next to the relevant event, you can download a comprehensive Criteo OneTag report. This report allows you to review event logs from the last 48 hours, URLs of pages generating errors, and missing parameters.

How to Read the OneTag Excel Report

To review the details of events with errors, use the download icon in the Actions column to download the .xlsx report.

Last Events Listing: Contains parameters such as URLs, product IDs, and site types for sample events recorded during the last 48 hours.

Top Non-Displayable Product IDs: Shows products that do not match the catalog. Important Tip: Make sure to check columns H and I in this tab. The specific reason for the issue—such as out-of-stock status, blacklisting, or missing information—is provided here.

Duplicated Transaction IDs: Lists transaction IDs that have been triggered more than once on the sales confirmation page.

Critical Thresholds

Ideally, the matching quality between the catalog and tracker should be above 80%. If this rate falls below 60%, campaign performance may decline significantly.

For this reason, make sure that the products tracked on your website by their IDs also exist in your catalog with exactly the same IDs.

Product Catalog Errors and Solutions

The product catalog can be created and imported in CSV, XML, or JSON format via HTTP, FTP, or SFTP protocols.

For the health of your campaigns, your product catalog must be transferred to Criteo without interruption. Errors encountered during this process generally fall into three main categories: Credentials, Downloads, and Parsing.

Understanding these three categories allows you to quickly identify and resolve bottlenecks in the data flow.

Credentials errors occur when Criteo cannot connect to your FTP, SFTP, or password-protected HTTP server due to an invalid username, insufficient permissions, or IP restrictions.

To resolve access issues, you may need to whitelist Criteo IP addresses on the server side.

Note: Criteo IP ranges are not publicly available. For whitelisting procedures, you should contact the Criteo support team and request the latest IP addresses.

Downloads errors occur when access permission is available but the file cannot be found on the server at the scheduled import time, the filename or file path is incorrect, or server latency causes timeout errors.

An incorrect file format or an invalid SSL certificate may also cause download interruptions.

To resolve these issues quickly, first make sure that your product feed file is available on the server with the correct filename before the scheduled import time.

If large file sizes cause response delays on your server, such as a 504 Gateway Timeout, you can split your feed file into multiple parts and enable the multipage feature using the {0} parameter to streamline the download process.

If the issue remains unresolved after following the steps above, clearly listing the troubleshooting steps you have already taken and specifying the exact point where the process failed when contacting the Criteo support team can significantly accelerate the resolution process.