PrestaShop Product Feed & Tracking Audit

Why Google rejects your products

Google Merchant Center rejects half the catalogue due to issues like incorrect GTINs, feed prices below storefront prices, missing structured data, and other discrepancies. These issues can lead to feed suspensions.

Why conversions may not match orders

Conversion numbers in your ad account may not match orders in your back office due to misaligned data between your feed and Google tracking, leading to potential discrepancies in performance metrics.

What the audit checks

• Reconciles your PrestaShop product feed with the data PrestaShop is serving to ensure accuracy.
• Walks through the full purchase sequence with tags live to capture every event, its value, and currency.
• Checks for duplicate tags and missing attributes to ensure proper tracking.
• Verifies structured data and consent state to ensure rich results and accurate data collection.

How the review is run

The audit is run against your live PrestaShop store, pulling your feed and comparing it with what the storefront actually serves. This ensures that issues are tied to specific products and pages.

How findings are ranked

Each issue is scored based on its monetary or measurement impact and the effort required to remediate it. This ensures that the most critical issues are addressed first.

What the findings actually look like

Examples include products disapproved due to empty GTINs, feed prices below storefront prices, and purchase tags that double-count revenue. Each finding is tied to the specific products and pages affected.

Who it is for

• Mercanting spending on Google Shopping, Google Ads, or Meta and TikTok who suspect the numbers are off.
• Agencies needing an independent technical read on a client's feed and measurement before scaling budget.

What you get

• A prioritized list of feed and tracking faults, each with its revenue or measurement impact and the concrete fix.
• The cause behind each Merchant Center error and warning, traced down to the specific products affected.
• A verdict on whether your GA4 and Google Ads conversion numbers can be trusted, with the evidence behind it.
• Pixel and structured-data checks run on your real product and checkout pages, with what each tag emitted.
• A remediation for every diagnosed fault, written so your own team or developer can implement it directly.

The line between the plumbing and your campaigns

This audit is the technical layer only: feed data quality, tracking integrity, structured data, and the data layer. It does not cover campaign management, bidding, budgets, creative, or keywords, and it carries no ROAS or ad-approval promise.

PrestaShop versions covered

• Audit covers PrestaShop 1.6, 1.7, 8, and 9, including multistore and multi-currency shops.
• Includes multistore feeds crossing currencies and languages, and tags injected by both theme and module that end up firing twice.

How every finding is written

Symptoms, the evidence they were drawn from, why they happen on PrestaShop, the fix, the effort, and how to confirm it worked are all detailed in a way a developer can act on without asking follow-up questions.