/Integrations
v1.2PostHog
Validate PostHog project keys, script loading, and CSP readiness.
Integration
PostHog
Confirms analytics script loading and CSP compatibility.
Product analytics gaps at launch mean you fly blind on activation and conversion—often because the snippet never loaded, the project key is wrong, or Content Security Policy blocks capture requests. PreFlight checks script reachability, landing-page install, and CSP rules before you rely on PostHog dashboards on day one.
Requirements
- PostHog project API key
- PostHog host or reverse-proxy URL
- Public landing page URL where the snippet should be installed
What PreFlight checks
| Probe | What it proves |
|---|---|
| Script reachability | The PostHog script endpoint responds and is loadable. |
| Landing page install | The configured project key appears on the public landing page. |
| CSP compatibility | Content Security Policy allows PostHog in script-src and connect-src. |
| Host alignment | The host in your config matches what the snippet requests at runtime. |
Failure guidance
| Symptom | Fix |
|---|---|
| Script not found on page | Install the PostHog snippet on the public landing page with the correct project key. |
| CSP blocked | Allow the PostHog host in script-src and connect-src at your CDN or framework layer. |
| Wrong project key | Copy the key from PostHog → Project Settings and redeploy. |
| Reverse proxy mismatch | Confirm the proxy URL in PreFlight matches the api_host in your client init. |
Dashboard setup
- Go to Integrations → PostHog in your PreFlight project.
- Paste the project API key and PostHog host (or proxy URL).
- Enter the public landing page URL where analytics should be active.
- Run Pre-Flight Check and resolve any CSP or install warnings.