Get content analytics
The response shape follows the content type (discriminated on contentType): flows report starts + completions and a per-step funnel with tooltip-target-missing counts; checklists starts + completions and per-task rows; launchers seen + activations; banners seen + dismissals; resource centers opens + block clicks; trackers users + occurrences of the tracked event. All with a per-day series. Defaults to the last 30 days, UTC.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Environment whose sessions to aggregate (content is project-level; pick the env).
ISO date, inclusive. Default: 30 days ago.
ISO date, inclusive. Default: today.
IANA timezone used for the per-day bucketing. Default: UTC.
Response
Content analytics — the shape follows the content type
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
contentAnalytics flow Distinct users who started it in the range.
0 <= x <= 9007199254740991Runs started in the range — one per session, so a user who ran it twice counts twice.
0 <= x <= 9007199254740991Distinct users who reached the end of the flow (or an explicit completion step).
0 <= x <= 9007199254740991Runs completed in the range.
0 <= x <= 9007199254740991Per-day activity: each row counts only that calendar day (increments, NOT a running total). Summing the total* rows reproduces the total* headline; a unique* row is distinct users WITHIN THAT DAY, so summing unique* rows over-counts a user active on several days — there is no daily series for range-wide unique users. Note the question-analytics nps/rating byDay uses the OPPOSITE convention (rolling-window cumulative).