Skip to content

Common failure modes

This page centralizes the most frequent “it looks broken” scenarios after checkout tracking changes.

GA4 Realtime shows 0

  • Wrong property or measurement ID

  • Event name mismatch (not purchase)

  • Consent denied, so identifiers are withheld

  • Reporting filters or missing DebugView settings

  • Ad blockers or browser privacy settings

DebugView is empty

  • Debug mode not enabled for the test session

  • Event is blocked before it reaches the ingest layer

  • Event is sent server-side only without debug flags

  • Incorrect stream or property

Meta shows “received” but not “attributed”

  • Missing or low-quality identifiers due to consent gating

  • Event is outside the attribution window

  • Validation warnings or dedup rules suppress the event

  • Reporting delays or delayed match quality updates

Duplicates after migration

  • Legacy Additional Scripts still firing

  • Pixel and server both send, but event_id is unstable

  • Multiple pixels or data sources are configured with overlapping events

  • Test events and live events are mixed without clear separation

Next steps

Canonical explainer

See https://ty-bridge.com/explainers/.