Advanced Tracking
Creating Complex Step Events
Track multi-step funnels such as signup, checkout, KYC, onboarding, and deposit journeys with consistent step events and completion outcomes.
What complex step events solve
Many important conversions are not single clicks. A user may open a form, finish step one, upload documents, confirm details, and only then complete registration or deposit. Complex step events make those journeys visible without collapsing every interaction into one vague action.
RetentionMaster stores each step as its own action-coded event. Reporting, User Journey, Lead Collection, Retention, and Data Explorer can then show where users advance, stall, or abandon.
Naming convention
Use a shared prefix plus explicit step names: signup_step_1_started, signup_step_1_completed, signup_step_2_completed, signup_completed. For checkout, use checkout_step_1_started through checkout_completed. For KYC, use kyc_started, kyc_documents_submitted, kyc_approved, and kyc_rejected.
Keep the final business outcome separate from progress events. For example, registration or signup_success should remain the conversion event, while signup_step_2_completed describes progress toward it.
Payload convention
Every step event should include a journey name, step number, step name, status, and stable identifiers when available: { journey: "signup", step: 2, step_name: "verify_email", status: "completed", user_id: "..." }.
For revenue or value events, include amount and currency using payload paths that can be mapped later. For experiments, include variant or campaign identifiers so step drop-off can be compared by audience.
Sequence analysis in practice
Use Data Explorer to verify every step event, Reporting to monitor action-code volume, User Journey to understand sessions and transitions, and Retention or Forecast to connect completed journeys to later value.
If steps trigger retention assets, bind campaigns to the relevant action or page context and keep cooldowns conservative so visitors are helped rather than interrupted repeatedly.
Frequently Asked Questions
Should missing steps be inferred?
Prefer explicit events for each important step. Inference is useful for analysis, but explicit step events make debugging and attribution much cleaner.
Can a step event trigger a retention asset?
Yes, if the runtime action configuration and campaign binding treat that action as eligible for a retention asset. Use cooldowns and page rules carefully.