Skip to main content

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
Use it when you need row-level evidence behind summary analytics cards.

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

StatusPractical meaning
pendingReceived but not yet finalized
approvedCounted as accepted business outcome
refunded/chargeback/cancelledReversal-impacting outcome
rejected/duplicate/fraudExcluded from trusted outcome totals

Conversion source interpretation

Conversion source labels can come from:
  • browser/client instrumentation
  • server-to-server submissions
  • integration-provider ingestion
If source appears blank or generic, verify upstream source metadata mapping.

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:
  1. Check whether customer email or external customer ID is sent.
  2. Check whether repeated events reuse identity fields consistently.
  3. Check whether source integrations map identity fields correctly.

Events-to-customers reconciliation workflow

  1. Start with Events for row-level evidence.
  2. Group by identity signals used in your setup.
  3. Confirm those identities appear in Customers.
  4. Reconcile totals with Conversions and analytics tabs using same filters.

Common discrepancy scenarios

ScenarioLikely causeFirst action
Conversions exist but no customersMissing identity fields in eventsValidate payload identity fields
Customer value looks lower than expectedStatus filters excluding pending/reversed eventsAlign status filter context
Source breakdown unclearUpstream source tags not mappedCheck integration or SDK source metadata
Different counts across pagesScope/date/timezone mismatchAlign filters before comparing
Related:
  • /user-guides/manual/data/conversions-customers
  • /user-guides/manual/data/conversion-methods-and-event-types-reference
  • /user-guides/manual/data/analytics-and-reporting