Ecommerce Tracking Audit Checklist for Meta Pixel, GTM, GA4 and Klaviyo
A practical ecommerce tracking audit checklist for Meta Pixel, Google Tag Manager, GA4, Klaviyo, UTM links, cookie banners and event quality.
Bad tracking is expensive because it makes every growth decision less reliable. Paid media teams optimize toward incomplete events. Lifecycle teams miss abandonment flows. Founders read dashboards that look precise but are quietly wrong.
An ecommerce tracking audit does not need to start with a complex data warehouse. Start with the public and platform-level signals that tell you whether the system is healthy enough to trust.
What To Check
| Area | What to verify | Why it matters |
|---|---|---|
| Meta Pixel | Base pixel, ViewContent, AddToCart, InitiateCheckout, Purchase | Paid social optimization and retargeting |
| GTM | Container ID, ownership, duplicate containers, dataLayer | Tag governance and event consistency |
| GA4 | Measurement ID, ecommerce events, DebugView | Reporting and attribution |
| Klaviyo | Onsite script, forms, product viewed, cart and purchase events | Email capture and lifecycle revenue |
| UTM links | Source, medium, campaign naming | Clean campaign reporting |
| Cookie banner | Consent behavior and CMP signal | Compliance readiness and tracking behavior |
| Server-side tracking | CAPI or server-side events when needed | Better event resilience |
Public Signals Are A Starting Point
Public HTML can reveal GTM IDs, GA4 IDs, Meta Pixel scripts, Klaviyo snippets and cookie management platforms. That is useful, but it is not a complete measurement audit.
Some stores load tracking after consent. Some inject scripts through tag managers. Some use server-side setups that are not visible from the storefront. Treat public checks as fast signal detection, then verify event quality inside each platform.
Common Tracking Problems
- Duplicate purchase events.
- Meta Pixel installed but core ecommerce events missing.
- GTM and hardcoded scripts firing the same tags.
- GA4 collecting pageviews but not ecommerce events.
- Klaviyo installed without reliable product viewed or cart events.
- UTM naming inconsistent across channels.
- Consent banner blocking scripts differently by market without documentation.
Recommended Workflow
Start with public checks for Meta Pixel, GTM and Klaviyo. Then use platform debug tools to verify events. Finally, document the event map so marketing, analytics and development teams know what each event means.
If tracking is not trustworthy, do not scale spend aggressively. Fix measurement first, then optimize.
