Destinations
PostHog Cloud
Your full event stream, forwarded server-side to your own PostHog project.
PostHog is product analytics, so unlike the ad platforms it receives the full event
stream - page views, clicks and custom events, not just conversions. PixelFox forwards
every ingested event server-side to your project's capture endpoint (/batch), keyed by
the same distinct id you see in PixelFox, so funnels and retention line up across both
tools.
Credentials
| Field | Where to find it |
|---|---|
| Project API key | PostHog → Project settings → Project API key (phc_…). This is the write-only ingestion key. |
| Ingestion host | https://us.i.posthog.com (default) or https://eu.i.posthog.com for the EU cloud. Self-hosted works too - paste your instance's ingestion URL. |
Paste them under Integrations → PostHog Cloud.
What you get
- Every event, server-side - ad blockers that stop
posthog-jsnever see this traffic, because it goes backend-to-backend. - Shared identity - events carry the PixelFox distinct id, and each one includes a
signals_event_idproperty (the same uuid used for Meta/TikTok dedup), so a conversion can be traced across every destination. - No extra browser weight - PixelFox does not load
posthog-js; if you want session replay or feature flags, add PostHog's own snippet alongside (events will not double, since PixelFox sends server-side under its own event names).
Verify
Events appear in PostHog's Activity view within seconds of traffic on your tagged site. The Integrations page's delivery status shows accepted/rejected counts per attempt.