Integrations / Analytics
PostHog
Server-side event tracking to PostHog via the capture API (/i/v0/e/). Maps Signal events to PostHog conventions ($pageview with $current_url/$referrer, person properties via $set/$set_once), uses a stable distinct_id (user_id with anonymous_id fallback), and forwards IP via $ip for GeoIP enrichment. PostHog stores raw person properties, so PII is sent in clear under $set; consent is enforced upstream by the pipeline's consent categories.
Datafly Signal delivers first-party events to PostHog server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload PostHog expects.
Why route PostHog through Datafly Signal
Your numbers stop depending on what the browser allows
Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so PostHog receives the complete event stream.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what PostHog needs to attribute the event to the right session.
One consent decision governs every destination
PostHog is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartbegin_checkoutloginpagepurchasesearchsign_upview_itemVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the PostHog documentation.
Frequently asked questions
Does Datafly Signal integrate with PostHog?
Yes. Datafly Signal delivers first-party events to PostHog server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload PostHog expects. The integration is included in every deployment at no additional cost.
How is server-side PostHog tracking different from the PostHog tag?
The PostHog tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to PostHog from your server, so delivery does not depend on browser conditions.
Which events can Signal send to PostHog?
The blueprint ships with mappings for add_to_cart, begin_checkout, login, page, purchase, search, sign_up, view_item. Any event in your schema can be mapped to PostHog through pipeline configuration without a code change.
Do I need to keep the PostHog tag on my site?
No. Signal delivers to PostHog from the server, so no client-side PostHog script is required on your site.
Other analytics integrations
Ready to move PostHog server-side?
See how Datafly Signal delivers first-party events to PostHog from infrastructure you control, with hashed identity and consent enforcement built in.