GA4 and a CRM may record the same customer journey on different dates. Analytics can timestamp a browser event in the property’s time zone, while a CRM stores UTC or local time. Systems may also define “conversion” differently.
Write down both event definitions
Choose the exact GA4 event and CRM milestone being compared. A form submission, lead creation, sales acceptance, and opportunity creation are separate events; comparing different milestones creates a mismatch that timestamp changes cannot solve.
Record event time and ingestion time where available. If an integration processes a submission later, the event may belong to one day in analytics and a later day in the CRM.
Normalize clocks before comparing
Document the GA4 property time zone and CRM storage and display time zones. Preserve original timestamps and create a normalized UTC value for reconciliation. Check daylight-saving transitions and date-only fields that have lost time precision.
Aggregate only after normalization. A submission just before midnight in one time zone may appear on the next date in another, even when weekly or monthly totals eventually converge.
Separate event date from attribution date
Platforms may assign conversion credit to an earlier interaction or update modeled results after the event. A CRM usually records an operational milestone. These dates represent different concepts and should not be overwritten to force agreement.
Build a reconciliation table by event, system, time basis, and status. Include late arrivals, duplicates, and records without a join key so the report exposes the source of the difference.
Set a repeatable comparison window
Compare stable periods with an explicit data-maturity lag. Re-run recent days after integrations settle and mark them provisional. Investigate recurring boundary differences separately from real volume changes.
If the discrepancy remains, trace sample records from browser event through CRM creation and downstream status. See our event tracking plan for consistent event definitions.
Related reading: event tracking plan.
Practical checklist
- Name the decision and the evidence it requires.
- Record the definitions, assumptions, and ownership that affect interpretation.
- Revisit the method when the underlying process or data changes.
How did this article land?
Choose one reaction. You can change it anytime.