Skip to main content
GET
Get content analytics

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

Content ID

projectId
string
required

Project ID

Query Parameters

environmentId
string
required

Environment whose sessions to aggregate (content is project-level; pick the env).

startDate
string

ISO date, inclusive. Default: 30 days ago.

endDate
string

ISO date, inclusive. Default: today.

timezone
string

IANA timezone used for the per-day bucketing. Default: UTC.

Response

Content analytics — the shape follows the content type

object
enum<string>
required
Available options:
contentAnalytics
contentId
string
required
environmentId
string
required
startDate
string
required
endDate
string
required
timezone
string
required
contentType
enum<string>
required
Available options:
flow
uniqueStarts
integer
required

Distinct users who started it in the range.

Required range: 0 <= x <= 9007199254740991
totalStarts
integer
required

Runs started in the range — one per session, so a user who ran it twice counts twice.

Required range: 0 <= x <= 9007199254740991
uniqueCompletions
integer
required

Distinct users who reached the end of the flow (or an explicit completion step).

Required range: 0 <= x <= 9007199254740991
totalCompletions
integer
required

Runs completed in the range.

Required range: 0 <= x <= 9007199254740991
byDay
object[]
required

Per-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).

steps
object[]
required