If you got a data quality notification for your Google Analytics connection, we can't use your Google Analytics data for attribution right now. Until you fix it, Criteo AI can't optimize your campaigns toward your Google Analytics data.

This guide is for advertisers and agencies using Criteo Commerce Growth with a connected Google Analytics account. Find the notification title you received in the table below, then go to its section for step-by-step fixes.

Find your issue

Notification title	What it means	What to do
Missing transaction ID	Your conversion tracking isn't sending a transaction ID.	Turn on transaction ID tracking in Google Analytics.
Transaction match rate too low	We can't match enough transactions between Google Analytics and Criteo.	Make sure both send the transaction ID in exactly the same format.
Too many null conversions	We're receiving too many conversions with a null value.	Keep an eye on it. If it doesn't go away, contact Criteo Support.
Invalid source medium	The source medium in your tracking code doesn't identify Criteo.	Set utm_source=criteo consistently on all ads and ad sets.
Incorrect event name	Your purchase event name isn't set up correctly.	Make sure the event is named exactly purchase.
Ad set ID missing	Ad set ID information is missing from your data.	Add utm_id={{adsetid}} to all Criteo ads and ad sets.

What to know before you fix anything

You can have more than one issue at once. Each check runs on its own, and each notification comes with its own reminder. Fix every issue you've been notified about.

Fixes aren't confirmed right away. After you make a change, it can take up to seven days for the check to pass, depending on which issue you fixed.

Your connection may show as Pending while this happens. The table below explains why.

Your connection shows Pending when…	What to do
You connected Google Analytics today	Nothing. Checks begin once we start receiving your data.
We didn't receive data on the first day of processing	Wait for the next update. If it stays Pending, contact Criteo Support.
We're receiving data, but there are data quality issues	Follow the steps in this guide for each notification you have.
You've fixed every issue, but the checks haven't passed yet	Wait up to seven days for the checks to update.

Missing transaction ID

Why it matters: The transaction ID is how we recognize the same purchase in Google Analytics and in Criteo. Without it, we can't use your Google Analytics data for attribution.

How to fix it:

Open your Google Analytics e-commerce tracking setup.

Confirm that transaction ID tracking is turned on for purchases.

If it isn't, set it up using Google's Ecommerce events guide.

Transaction match rate too low

Why it matters: We match each purchase by its transaction ID. If Google Analytics and Criteo send the ID in different formats, we can't pair the purchases, and too few transactions match for us to use your data.

How to fix it: Make sure the transaction ID has the same value and format in Google Analytics and in the Criteo OneTag.

Check for	Example of a mismatch
Prefixes	Criteo OneTag sends Transaction_1234, Google Analytics sends 1234
Suffixes	An extra character or string added to the end of the ID in one tag only
Formatting logic	Different formatting rules applied in each tag
Transformations	Any change made to the ID in either tag before it's sent

Too many null conversions

Why it matters: When too many conversions come in with a null value, we can't reliably use your Google Analytics data for attribution.

How to fix it:

Keep monitoring your connection. This ratio can go up and down over time, so the issue may resolve without any action.

If the issue keeps happening, contact Criteo Support so we can look into it with you.

Invalid source medium

Why it matters: Google Analytics uses the source medium to know which traffic came from Criteo. If the value is wrong or inconsistent, we can't attribute those conversions to your Criteo campaigns.

How to fix it: Set up Criteo tracking the same way in the click URL of every ad.

Parameter	Accepted values
utm_source	criteo or crto

Then:

Check that the source medium value Google Analytics receives identifies Criteo.
Review every active ad and ad set.
Look for ad-level tracking overrides. These can replace the tracking set at the ad set level.

Incorrect event name

Why it matters: We look for purchases under one standard event name. If your purchases are sent under a different name, we can't find them.

How to fix it:

Turn on Google Analytics e-commerce purchase tracking.

Make sure the event Criteo receives is named exactly purchase.

Check that purchases go through the standard Google Analytics e-commerce setup, not through a different custom event.

Ad set ID missing

Why it matters: The ad set ID lets us connect Google Analytics attribution to a specific Criteo ad set. Without it, we can't break down your Google Analytics data by ad set.

How to fix it: Add this parameter to the tracking settings for all your Criteo ads and ad sets.

Parameter	Value to add
utm_id	{{adsetid}}

Then:

Review your existing ads.
Review any ads you've created since.
Look for ad-level tracking overrides that could remove or replace the parameter.

Next step

Once you've made your changes, give the checks up to seven days to update. When all checks pass, your notifications stop, and we can use your Google Analytics data for attribution again. If an issue is still there after that, contact Criteo Support.

Conexões