Get a conversion funnel
Ordered conversion funnel over 2 to 5 event names. Each returned step carries the visitors who completed every step up to and including it, in order, with all of them inside window_hours of the first step. Rates are given against step 1 and against the previous step.
Two limits are inherent to the source and are reported, not hidden. The funnel is VISITOR-grain: the source carries no person id, so one person on two devices counts as two visitors and cannot complete a single funnel. And the source retains 90 days: an earlier start_date is pulled forward to that floor and meta.from_clamped is true, while a range entirely behind the floor is a 400 rather than a funnel of zeros. A step taken after end_date is not counted even when it falls inside window_hours, so widen end_date to close that edge.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Comma-separated event names in funnel order, 2 to 5 of them. Empty names are rejected rather than dropped. Use /event-names to get the names this workspace tracks; an untracked name yields zero visitors, not an error.
Conversion window: every step must occur within this many hours of the first step. The maximum equals the source's 90-day retention.
1 <= x <= 2160Inclusive first event date, as YYYY-MM-DD or an ISO 8601 instant. Supply with end_date; omit both for the last 30 days. Clamped to 90 days ago.
Inclusive last event date, as YYYY-MM-DD or an ISO 8601 instant.
Response
Successful response. Visitor-grain, last 90 days only: a person on two devices is two visitors, and an earlier start is clamped with meta.from_clamped.