Who this is for
Teams whose path reports disagree across clients — different event names, missing parameters, or out-of-order sequences that make journey comparisons unreliable.
Result
A reconciled event path dictionary for one product surface, with rename recommendations, required parameters, and a short validation checklist for the next release train.
Included
Inventory of current events on the chosen path, cross-platform comparison, recommended canonical names, and a handover sheet for engineering.
Excluded
SDK installation, QA automation, and long-term taxonomy ownership. We hand you a clear dictionary; your team owns the merge.
Process & timeline
Day 1 intake, days 2–4 comparison work, day 5 review session, optional follow-up for questions within the same week.
Pricing basis
Fixed starting fee for one path (for example checkout or onboarding). Extra client platforms or nested sub-flows are quoted after intake.
Next step
Ask for an Event Path Review and attach your current event list if you have one.