Stats endpoints

All are GET, take the ranges and filters and need a read key.

Endpoint	Returns
/v1/sites/{id}/stats/overview	Visitors, visits, page views, conversions, bounce rate, views per visit, engaged time; compare=true adds the previous period and the change
/v1/sites/{id}/stats/timeseries	Points per interval (hour or day; empty buckets filled)
/v1/sites/{id}/stats/pages	Pages by views, with visitors and engaged time
/v1/sites/{id}/stats/sources	Visits by by: channel, referrer, utm_source, utm_medium, utm_campaign, entry_page
/v1/sites/{id}/stats/geo	Visits by by: country, region, city
/v1/sites/{id}/stats/devices	Visits by by: device, browser, os, language
/v1/sites/{id}/stats/events	Custom events and conversions; name=<event> breaks one down by property
/v1/sites/{id}/stats/trust	The trust report
/v1/sites/{id}/stats/changes	What changed against the previous range
/v1/sites/{id}/stats/realtime	Visits active in the last 5 minutes, their pages, and the last 30 minutes
/v1/sites/{id}/stats/revenue	Revenue per currency
/v1/sites/{id}/stats/crawlers	Crawler reads
/v1/sites/{id}/heatmaps/pages	Pages by clicks, rage and dead clicks
/v1/sites/{id}/heatmaps?path=	One page’s heatmap

Every stats response starts with the range it covers (from, to, timezone).

Visitors are counted once per local day, so the visitors of a range are the sum of its daily counts.