Event Journey Evidence Workbench

How to use Event Journey Evidence Workbench

Prepare auditable journey summaries directly from a small event export. Trace each closed-funnel step to a real source record, or assemble returning-activity cohorts from each ID’s first observed month. The workbench makes chronology, repeat entries, duplicate handling and unobserved months explicit instead of accepting unexplained aggregate totals.

1. Paste event CSV and choose the three exact column names; use synthetic or appropriately minimized identifiers.
2. Choose funnel or cohort mode and set its chronology, duplicate and observation rules.
3. Run the tool, inspect source-record witnesses and download the JSON evidence report.

Good to know

• 1–2,000 CSV records, 200,000 source characters, 100 columns and 50,000 characters per cell. IDs/event names are exact nonblank strings up to 100 characters without controls. Timestamps must be exact Gregorian UTC whole seconds YYYY-MM-DDTHH:mm:ssZ, years 0001–9999; offsets, leap seconds, fractions and repaired impossible dates are refused.
• Funnel: 2–10 stages; repeated stage names are allowed but require distinct records. The inclusive entry window is 0–31,536,000 seconds or unlimited. At most 2,000,000 record comparisons and a 2 second computation budget; a budget failure returns no partial report. Source-order ties are an explicit input assumption.
• Cohorts: at most 120 source-to-cutoff calendar months and 1–24 periods including month 0. Events after the last fully observed month are refused. Periods after that cutoff are null; observed periods with no matching event are zero. A month beyond year 9999 has no representable month label and remains unobserved.
• Only the three selected columns define event identity and identical-triple deduplication; other columns are not included in this evidence report. No upload, tracking integration, automatic capture-gap detection, identity stitching, causal claim, actual acquisition guarantee or GA4 compatibility is provided.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.