How to Set Up Criteo Conversion Tracking with Google Tag Manager (Step-by-Step Guide 2026)

Criteo is one of the world’s largest commerce media and retargeting platforms. If you’re running an eCommerce store, proper Criteo tracking can dramatically improve your product retargeting campaigns—but only if it’s implemented correctly.
Most businesses simply install the Criteo app or use a basic integration.
Unfortunately…
That’s usually where the problems begin.
Product IDs don’t match.
Purchase events fail.
Dynamic ads don’t display the correct products.
Campaign performance suffers because Criteo isn’t receiving the data it needs.
In this guide, I’ll show you how to implement Criteo Conversion Tracking using Google Tag Manager the right way.
What is Criteo?
Criteo is an advertising platform built specifically for commerce.
Unlike traditional display advertising, Criteo focuses on showing personalized product ads to people who have already visited your website.
For example…
A visitor browses running shoes on your Shopify store.
They leave without buying.
Later, while browsing another website, they see the exact shoes they viewed.
That’s Criteo working.
To make this happen accurately, Criteo needs high-quality event data from your website.
Why Google Tag Manager Instead of Direct Integration?
Many merchants install Criteo through an app.
It’s quick.
But you lose control.
One of the biggest issues is Product ID mismatch.
If the Product ID sent from your website doesn’t match the Product ID inside your Criteo catalog…
Your dynamic ads won’t work correctly.
Google Tag Manager gives you complete control over:
- Product IDs
- Transaction IDs
- Currency
- Basket data
- Purchase values
- Event triggers
That’s why GTM is the preferred implementation for larger eCommerce stores.
Before You Start
You’ll need:
✅ Google Tag Manager
✅ Criteo Merchant Account
✅ Your Criteo Partner ID
✅ Product Catalog uploaded to Criteo
✅ Data Layer implementation (recommended)
Step 1 — Upload Your Product Catalog
Before implementing tracking…
Upload your product catalog inside Criteo.
Every product ID you send through GTM must exist inside this catalog.
Otherwise Criteo cannot match products correctly.
Step 2 — Add the Official Criteo Templates
Inside GTM:
Templates → Search Gallery
Search:
- Criteo Loader
- Criteo OneTag
Install both official templates.
Avoid legacy templates whenever possible.
Step 3 — Create Your Partner ID Variable
Your Partner ID identifies your Criteo account.
Create:
Variable → Constant
Paste your Partner ID.
Example:
Criteo Partner ID
If you manage multiple websites, use a Lookup Table based on Page Hostname instead.
Step 4 — Configure the Criteo OneTag
Create a new Tag.
Choose:
Criteo OneTag
Configure:
- Partner ID
- All Pages Trigger
This loads the Criteo base tag across your website.
Step 5 — Configure the Criteo Loader Tag
Create another tag:
Criteo Loader
Add your Partner ID.
No trigger is required.
Instead…
Use it as a Setup Tag inside the OneTag configuration.
This ensures the Loader executes before OneTag.
Step 6 — Create the Purchase Conversion Tag
Now create another:
Criteo OneTag
Event Type:
Conversion
This event sends purchase information back to Criteo.
Step 7 — Pass Purchase Data
The Conversion tag requires information like:
- Transaction ID
- Currency
- Basket Items
- Purchase Value
The best practice is using your website’s Data Layer.
Example variables include:
- ecommerce.transaction_id
- ecommerce.currency
- ecommerce.items
- ecommerce.value
Avoid scraping values directly from the thank-you page whenever possible.
Developers update page layouts frequently.
Data Layer remains much more stable.
Step 8 — Configure the Purchase Trigger
Create:
Custom Event Trigger
Event Name:
purchase
Attach this trigger to your Conversion Tag.
Now Criteo only receives purchase events after a successful transaction.
Step 9 — Preview & Test
Before publishing:
Use GTM Preview Mode.
Place a test order.
Verify:
✅ Purchase Trigger fires
✅ Transaction ID is correct
✅ Product IDs match your catalog
✅ Currency is correct
✅ Basket data is populated
Common Mistakes
Here are the issues I find most often during audits:
❌ Product ID mismatch
❌ Wrong transaction IDs
❌ Missing purchase value
❌ Missing currency
❌ Incorrect basket formatting
❌ Legacy Criteo templates
❌ Scraping page data instead of Data Layer
Best Practices
I recommend:
✔ Use Data Layer instead of DOM scraping
✔ Keep Product IDs identical across Shopify/WooCommerce and Criteo Catalog
✔ Test every event before publishing
✔ Audit implementation regularly
✔ Use GTM instead of plugin-based integrations whenever possible
Why Accurate Criteo Tracking Matters
Better tracking leads to:
✅ Better product recommendations
✅ Higher catalog match rates
✅ Better retargeting
✅ More accurate attribution
✅ Improved ROAS
Because Criteo’s machine learning performs best when it receives clean, structured data.
Need Help?
I help eCommerce brands, agencies, and DTC businesses implement advanced tracking solutions, including:
- Google Tag Manager (GTM)
- Criteo Conversion Tracking
- GA4 Setup & Audits
- Google Ads Conversion Tracking
- Meta Pixel & Conversions API
- Server-Side Tracking (sGTM)
- Enhanced Conversions
- Shopify & WooCommerce Tracking
If you’re struggling with Criteo tracking, product ID mismatches, or inaccurate conversion data, feel free to reach out. I’d be happy to help you build a clean, reliable tracking setup.
#Criteo #GoogleTagManager #GTM #ConversionTracking #GA4 #Ecommerce #Shopify #WooCommerce #PerformanceMarketing #DigitalAnalytics
Need this implemented, audited, or white-labeled?
Whether you are an eCommerce brand owner fixing signal loss or a digital marketing agency needing a senior analytics engineer under strict NDA, I deliver 24–48h SLA turnaround with 8.5+ EMQ match rates.



