track() calls, and errors), a chart of counts over time, and a per-event property drill-down. A dedicated Page titles list and its own filter-value autocomplete live here too, since both power the same explorer UI.
A site is addressed by {siteKey} (UUID or domain). All endpoints require Authorization: Bearer {token} and accept the shared range/from/to and filter query parameters described in Conventions.
List events
engagement beacons. Scroll-paginated with the standard data/meta/links envelope — see Conventions.
Query parameters
Filter dimensions (
path, country, browser, prop_key/prop_value, etc.) are also accepted — see Conventions.
Response — each item in data:
Status:
200 OK.
Events timeseries
engagement.
Query parameters
Filter dimensions are also accepted.
Response — flat object:
Status:
200 OK.
Event property breakdown
event_name within one event_type, ranked by unique visitors. There is no site-level property allow-list — any key the matching events actually carried is returned. Capped at 50 rows.
Query parameters
Filter dimensions are also accepted.
Response — flat object:
Status:
200 OK.
List page titles
data/meta/links envelope.
Query parameters
Filter dimensions are also accepted.
Response — each item in
data:
Status:
200 OK.
Page title timeseries
Filter dimensions are also accepted.
Response — flat object:
Status:
200 OK.
Filter value suggestions
Other filter dimensions (besides
dimension itself) are also accepted, to narrow suggestions.
Response — flat object:
Status:
200 OK.

