Analytics — PostHog

Connect PostHog to give 1mn read access to your website traffic — pageviews, sessions, visitors, sources, and top pages. This powers the business digest and feeds the growth loops with demand signals. The connection is read-only and the key is encrypted at rest.

Prerequisites

• A PostHog project that's already receiving traffic.
• Whether your project is on the US (us.posthog.com) or EU (eu.posthog.com) cloud — you'll select the matching region.

Connect PostHog

1. Open Integrations and find the Web analytics (PostHog) card.
2. Choose your Region — US — us.posthog.com or EU — eu.posthog.com.
3. Create a Personal API Key in PostHog: top-right avatar → Settings → Personal API keys → Create personal API key. Grant it exactly these scopes:
   • project:read
   • insight:read
   • query:read
4. Paste the key (it looks like phx_…) into Personal API Key.
5. Enter your Project ID — in PostHog go to Settings → Project and copy the Project ID. It's also the number after /project/ in your PostHog URL.
6. Click Connect PostHog. 1mn validates the key against your project before saving; an invalid key or wrong region is rejected immediately.

Example: what you get

Once connected, the Analytics tab and the daily business digest report week-over-week movement read straight from your project — for example:

Pageviews        12,480   ▲ 18% WoW
Unique visitors   4,120   ▲ 11% WoW
Top growing source   google / organic
Top declining source twitter / referral

The digest is recommend-only — it never changes a campaign on traffic alone.

Notes & limits

• Scopes are minimal and read-only. The three scopes above are all the agent needs; it cannot write to or modify your PostHog project.
• Region must match. A US key on the EU region (or vice-versa) fails validation — pick the cloud your project lives on.
• Disconnect any time from the card; the dashboard and digest stop reading traffic, and the stored key is removed.
• PostHog is today's analytics provider; the connection is built on a provider registry so other providers (e.g. GA4) can slot in later without changing how the loops consume traffic.