Measurement
Part of What shopping feeds measurement means for multichannel reporting
When to audit shopping feeds measurement mistakes
Shopping feeds measurement mistakes in England, covering when to audit consent, platform issue logs and market context, plus a quarterly checklist.
What to take away
- Measurement mistakes usually show up as mismatched numbers, not missing numbers, so audit when your feed report and your analytics disagree.
- Platform issue logs now drive eligibility, so check the Merchant Centre issue details page before you blame the feed file.
- Consent rules under PECR affect what you can measure, and enforcement continues to focus on cookies and electronic marketing.
- ONS business changes data gives context for demand shifts, which helps separate seasonality from a broken tracking setup.
- Use the checklist below at least quarterly, or whenever you change channels, tags or feed software.
Why does timing matter for shopping feeds measurement mistakes?
Measurement problems rarely announce themselves. They surface when a finance report and a channel report disagree, or when a product that should be eligible stops serving. By then, budget has already moved.
Auditing on a schedule is cheaper than auditing after a bad quarter. A short, repeatable review beats a one-off clean-up because feeds, tags and consent states change whenever you add a channel or a market.
This list applies to England; rules that cover the whole UK or apply globally are labelled as such.
Which consent and tracking errors distort feed reporting?
The Information Commissioner's Office publishes a guide to the Privacy and Electronic Communications Regulations covering cookies, email and electronic marketing rules. If your tags fire before consent, your conversion counts include people who never agreed.
Consent and tracking errors
Error
- Tags before consent
- Includes non-agreers
- Banner clicks as engagement
- Counts clicks
- Modelled as observed
- Treats estimates
- Server and browser mixed
- Blends sources
What it shifts
- Tags before consent
- Inflates conversions
- Banner clicks as engagement
- Not consent
- Modelled as observed
- As real data
- Server and browser mixed
- Shifts denominator
Fix the definition first. Write down what a conversion means for each channel, then check that every report uses that definition. The wider shopping feeds measurement and reporting guide 2027 sets out how those definitions should flow into board reporting.
Are you reading platform issue logs before blaming the feed?
Google Merchant Centre provides an issue details page that explains how to review and resolve item issues. Teams that skip it often rewrite feed rules that were never the problem.
Diagnose platform issue logs
Is the issue item-level, account-level or a policy flag?
Check if same issue appears in your own catalogue data
Review the Merchant Centre issue details page
Check whether the issue is item-level, account-level or a policy flag. Then check whether the same issue appears in your own catalogue data. If it does, fix the source; if it does not, fix the submission.
Keep a dated log of issues and resolutions. That log becomes evidence when a channel manager asks why a product group underperformed.
How do you separate market shifts from tracking faults?
The Office for National Statistics publishes changes to business data covering business demography and related trends. Use it as context, not as a target.
If the market moved and your numbers moved with it, tracking may be fine. If the market moved and your numbers did not, investigate. If your numbers moved and the market did not, investigate harder.
Label every figure in your report by source and date. Mixing platform, analytics and survey data without labels misleads readers. For a structure that keeps those sources apart, see the shopping feeds reporting dashboard in England.
What belongs in a quarterly measurement checklist?
- Confirm consent states are recorded before tags fire, per the ICO guidance.
- Reconcile platform-reported conversions against analytics conversions for the same period.
- Review the Merchant Centre issue details page weekly and log resolutions.
- Check that feed attributes and catalogue attributes still match after any bulk edit.
- Verify currency, tax and shipping settings for each market you sell into.
- Note any ONS business changes release that could explain a demand shift.
- Confirm every report names its source, date and definition.
Run the checklist when you add a channel, change feed software, or enter a new market. Otherwise, quarterly is enough for most multichannel shops.
Common questions
How often should I audit feed measurement?
Quarterly for most shops, and immediately after any change to channels, tags or feed software. A change is the most common trigger for a measurement fault.
Does PECR apply to feed reporting?
PECR governs cookies and electronic marketing, so it affects what you can collect and measure. Reporting built on non-consented tracking will not be reliable.
What is the first thing to check when numbers disagree?
Check the definition of a conversion in each report. Most disagreements come from different definitions, not different data.
Can I fix measurement mistakes without new software?
Often yes. Clear definitions, a dated issue log and labelled sources resolve many problems before any purchase is needed.
