THE SHORT ANSWER
Marketing data is trustworthy enough for a decision when its definitions, collection, identity, transformations and reconciliation have been tested for the required use. Trust is proportional to the decision: directional exploration and financial allocation may need different controls.
Recognize common failure modes
| Failure | Possible symptom |
|---|---|
| Missing tracking | A journey step suddenly disappears |
| Duplicate events | Conversions exceed reconciled orders |
| Inconsistent naming | One campaign fragments across rows |
| Broken UTMs | Traffic becomes direct, unassigned or misclassified |
| Bot or internal traffic | Activity rises without business outcomes |
| Consent and identity gaps | Observed journeys change by environment |
| CRM mismatch | Leads, customers and status definitions disagree |
| Implementation change | A trend breaks on release day |
Run practical quality checks
- Reconcile key totals with order, CRM or finance records.
- Test events in a controlled journey and inspect parameters.
- Check missing, duplicate, impossible and delayed records.
- Monitor sudden changes by device, source and version.
- Validate campaign naming and channel rules.
- Annotate deployments, consent changes and definition revisions.
- Confirm time zone, currency and reporting date.
Evidence & context: Google Analytics Help
Disagreement does not always mean failure
Reports may use different scope, processing times, retention, thresholds or modeled data. Ad platforms, analytics, CRM and finance systems also observe different stages. Explain the expected reconciliation relationship rather than demanding identical totals.
Unexpected differences still deserve investigation. Preserve a tolerance, reason and owner for each important comparison.
Evidence & context: Google Analytics Help · Google Analytics Help
Match confidence to the decision
A directional content question may tolerate incomplete identity. A high-value budget reallocation or customer-level intervention may require reconciled outcomes, permission checks and reproducible logic.
Evidence & context: UK Information Commissioner's Office
Sources & further reading
- Monitor events in DebugView
Google Analytics Help. Official implementation-debugging guidance for inspecting collected events and user properties. Debugging one device does not replace production reconciliation and ongoing monitoring.
- Data differences between reports and explorations
Google Analytics Help. Official explanation of differences caused by supported fields, filtering, retention, thresholds, modeling and processing. It covers GA4 surfaces, not every cross-platform discrepancy.
- About modeled key events
Google Analytics Help. Official description of modeled key events under observation gaps. Modeled values remain estimates and may differ across reporting surfaces and processing times.
- How should we assess security and data minimisation in AI?
UK Information Commissioner's Office. UK regulatory guidance, checked 11 September 2026. Jurisdiction-specific context, not individual legal advice or permission for a particular use.
Examples and exercises are illustrative unless attributed to a source. No independent expert review is claimed.
A correction, a counterexample or an experience worth sharing?
Join the conversation ↗