Event Log Usage

The Event Log provides a granular, chronological view of ingested tracking events to:

1. Accessing the Event Log

From navigation: Funnel → Event Log (or contextual link from a step analytics panel if available).

Filter	Purpose	Notes
Date Range	Limit noise to the analysis window	Match your funnel’s conversion window when validating
Event Name	Focus on a specific step trigger	Useful before redefining a step
User / Device ID	Trace individual journey	Diagnose multi-step abandonment
Segment	Compare attribute-qualified cohorts	Ensure segmentation matches funnel config
Property Key/Value	Narrow to specific metadata	Case-sensitive if raw key store is strict

Step	Action	Why
1	Filter by target event name	Isolate core signal
2	Spot-check recent entries	Confirm freshness & volume
3	Expand a row (if supported)	Inspect payload fields
4	Cross-check segment logic	Ensure user qualifies as expected
5	Compare timestamps across sequential events	Identify latency or missing transition

Symptom	Possible Cause	Next Step
Missing expected event	Tracking not fired	Reproduce user action & watch network
Sudden volume drop	Deployment regression	Correlate with release timeline
Segment empty	Filter too restrictive	Relax one condition to test presence
Duplicate events	Client double-fire	Add idempotency guard client-side
Property null increase	Upstream schema drift	Align SDK version / payload mapper

Insight	Adjustments
High noise baseline event	Tighten step to a more specific event or add property constraint
Users stall before final step	Insert interim step to measure micro-conversion
Long delay between steps	Investigate UX friction or async processing
Segment disparity	Tailor messaging or create segment-specific path

If export (CSV / JSON) is supported, pull a bounded sample (e.g. last 24h) for deeper analysis or anomaly detection scripting.

Practice	Benefit
Maintain event naming conventions	Reduces misconfiguration risk
Document required properties per key event	Faster onboarding & QA
Periodically archive deprecated events	Cleaner selection lists

Use the Event Log as the ground-truth layer before altering a production funnel—early validation prevents mis-attribution down the line.