Goals, funnels, and journeys
Automate goals and funnels
Create saved definitions through workspace-scoped API keys.
Last updated August 20, 2026
Before you start
- A workspace API key
- A stable definition for each goal or funnel
How to do it
- 1
Create an API key from Settings > API keys and store it outside the repository.
- 2
Send the workspace-scoped goal or funnel definition using the Goals API or Funnels API contract.
- 3
List the saved definitions and open Conversions to verify the dashboard result.
- 4
Choose Attempts, configure the attempt ID property, and add up to 20 required steps. Send the same ID on each event and keep it across resumed sessions.
- 5
An attempt starts when the entire first required step is satisfied. That event starts the conversion window and supplies cohort properties. An unfinished first group is not a started attempt; use separate steps to measure losses within the group.
- 6
Use a finite conversion window. Compare pending attempts, confirmed drop-off, and per-step completion, then export all matching cohorts.
What to check
- The definition belongs only to the intended workspace
- Updates preserve stable identifiers and expected step order
- Two incomplete attempts cannot combine into one completion
- Completion, ordering, and coverage checks use retained events, not inferred missing history