Events and Customers Operations Reference
Use this guide for day-to-day operations on the Events and Customers pages.Events page purpose
The Events page is the event-level timeline view for:- click-related events
- lead and sale events
- custom conversion events
- status transitions and ingestion diagnostics
Typical event fields operators review
- event type/class
- status
- source
- timestamp
- value and currency (when applicable)
- campaign/link/rule attribution context
- customer identity signals (if present)
Event status interpretation
Conversion source interpretation
Conversion source labels can come from:- browser/client instrumentation
- server-to-server submissions
- integration-provider ingestion
Customers page purpose
The Customers page is identity-centric. It helps answer:- who converted
- how often they converted
- what value they generated
- which channels/campaigns they came from
Customer stitching diagnostics
If customers seem sparse compared with conversions:- Check whether customer email or external customer ID is sent.
- Check whether repeated events reuse identity fields consistently.
- Check whether source integrations map identity fields correctly.
Events-to-customers reconciliation workflow
- Start with Events for row-level evidence.
- Group by identity signals used in your setup.
- Confirm those identities appear in Customers.
- Reconcile totals with Conversions and analytics tabs using same filters.
Common discrepancy scenarios
Related:
/user-guides/manual/data/conversions-customers/user-guides/manual/data/conversion-methods-and-event-types-reference/user-guides/manual/data/analytics-and-reporting