PostHog integration

Connect PostHog to see which website visits lead to signups and other successful outcomes. Spronta Identity Bridge links the session; Spronta configures the event destination for you.

Connect your project

1. In your website’s Spronta workspace, open Connections → PostHog.
2. Choose EU Cloud or US Cloud, matching your PostHog account.
3. Click Connect PostHog and authorize Spronta.
4. Choose your PostHog project, then click Finish connection.

Spronta creates its event destination, stores the delivery credentials securely and keeps its event filters in sync with your goals. You do not need to copy API keys, webhook headers or JSON templates. PostHog may show an unverified application notice while publisher verification is pending.

Connect the website session

Keep Spronta’s website snippet and PostHog installed on your website. The snippet automatically detects the standard global PostHog browser instance and adds the current consented Spronta session to its events.

If you import PostHog into your application, or use a named instance, add this after initialization:

(window.sprontaIdentityBridge ||= []).push(['posthog', posthog]);

This works whether Spronta loads before or after your app. Continue calling posthog.identify(user.id) after login or signup, and posthog.reset() on logout. Existing event callbacks remain in place.

Server-side events need the same PostHog distinct ID and explicit analytics consent. A browser adapter cannot add properties to events sent only by your server. If the marketing site and app run on separate origins, keep their identity and consent handoff explicit.

Choose conversion goals

Spronta lists event names from your connected PostHog project. Choose a real signup, trial or purchase event, give it a name and save your goals. Property filters are optional and available under each goal’s advanced settings.

The destination forwards identity events, pageviews and your enabled goal events when spronta_consent is true. New rules apply to new deliveries. Previous conversions keep their original definition.

Check the connection

Visit your website and complete a tracked action, then click Check connection in Spronta. The page shows event delivery, Identity Bridge detection, conversion totals and linked visitor journeys. Missing session or identity links leave conversions unmatched rather than guessing a person from an email or IP address.

For tests, use spronta_test: true. Test deliveries are excluded from journeys and conversion totals.

Existing manual connections

Existing destinations continue working. Open Settings → Make this connection automatic, connect your account and select the same PostHog project. Spronta keeps your existing goals and imported journeys. The manual setup remains available for deployments that need it, including self-hosted PostHog.

Privacy and retention

Identity Bridge follows the Spronta snippet’s analytics permission, Do Not Track and Global Privacy Control. Provider user IDs are pseudonymized for storage. Imported events are retained for up to 90 days; reports cover at most the latest 2,000 eligible events in the selected period. No historical import runs during connection.

Disconnecting disables the destination managed by Spronta and removes this website’s imported events and identity links. Other PostHog data is managed in PostHog.

See Spronta Identity Bridge for Amplitude and Mixpanel browser connections.