Spronta Identity Bridge

Spronta Identity Bridge connects your existing analytics browser SDK to Spronta’s website sessions, so you can see which content and interactions lead to successful outcomes.

Supported connections

• PostHog: OAuth connection, automatic event destination and event-name discovery. Supports browser events and correctly identified, consented server events. Connect PostHog.
• Amplitude: Browser SDK 2 enrichment plugin. Connects browser events and explicit user/device IDs without setting up an Amplitude webhook.
• Mixpanel: JavaScript SDK with before_send_events hook support (v2.40.0 or later). Connects browser events and explicit user/device IDs without setting up a Mixpanel webhook.

Amplitude and Mixpanel connections currently observe browser events. They do not import server-only events, historical events, cohorts or saved provider reports.

Enable Amplitude or Mixpanel

1. Install your normal Spronta snippet and analytics browser SDK on the website.
2. Open the website’s Connections page in Spronta.
3. Choose Amplitude or Mixpanel, then enable its bridge.
4. Open your website and trigger a tracked action.
5. Return to Spronta, click Check connection, choose the real event as a goal and save.

Standard global SDK instances are detected automatically. No analytics API key is needed in Spronta.

SDKs imported into an application

Add the relevant line after initializing your SDK. Named instances should pass their specific initialized SDK object.

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

// Amplitude Browser SDK 2
(window.sprontaIdentityBridge ||= []).push(['amplitude', amplitude]);

// Mixpanel JavaScript SDK
(window.sprontaIdentityBridge ||= []).push(['mixpanel', mixpanel]);

The queue works before or after Spronta loads. Keep your existing identify calls after login and reset calls on logout. Spronta preserves existing event hooks and never replaces your analytics user ID.

Goals and visitor journeys

Only events you choose as goals count as conversions. Optional property filters use exact values. Spronta forwards only the properties those filters require; it does not copy every event property into visitor records. Other custom event names may appear as observed activity so you can choose them as goals.

Browser goals are observations from the visitor’s browser. For server-confirmed payments or backend actions, use an appropriate server event integration. Avoid configuring the same outcome through several sources unless you intend to count it more than once.

Consent and identity

The bridge runs when the Spronta snippet permits analytics. It reads the current session at capture time and removes stale bridge properties when permission is unavailable. It does not persist provider super-properties, guess identity from email or IP, or merge identities between providers.

Each website and provider has separate identity links. If a browser session contains different signed-in users, Spronta shows that ambiguity. Identifying a user does not overwrite an established different identity. Forgetting an imported identity also suppresses future deliveries for its known linked IDs.