A comprehensive guide to navigating and interpreting your blog's analytics data
To track analytics data, the platform provides an endpoint (`POST /analytics/track`) that records various metrics about page views. When a page view is tracked, the following data can be recorded: `article_id`, `session_id`, `referrer`, `utm_source`, `utm_medium`, `utm_campaign`, `duration_seconds`, `scroll_depth_pct`, `device_type`, and `country_code`. The IP address of the viewer is hashed and stored for privacy. If a `referrer` is provided, the domain is extracted and stored. The `country_code` is determined by prioritizing CDN headers (Cloudflare, Vercel, AWS) and falls back to the request body if necessary. Note that certain country codes like 'XX' or '--' are filtered out as unknown.

The `GET /analytics/overview` endpoint provides a summary of your blog's performance over a specified period (default is 30 days, adjustable between 1 and 365 days). This overview includes:
For detailed analytics on a specific article, use the `GET /analytics/articles/{article_id}` endpoint. This provides:
You can export your analytics data using the `GET /analytics/export` endpoint. The data can be exported in CSV format for a specified period (default is 30 days, adjustable between 1 and 365 days). The exported data includes:
Now that you understand your blog's analytics, explore ways to improve engagement and reach. Consider using insights from top articles and referrers to guide content strategy.