# Send Mixpanel data to Sequential > Keep the Mixpanel JavaScript SDK and point it at Sequential: your Sequential Mixpanel ingest key as the project token, plus `api_host`. Sequential speaks Mixpanel’s ingestion protocol, so `track`, `identify`, `track_pageview` and autocapture keep working. Pick **one** of the three paths below. ## Already using Mixpanel Do not add a second copy. In the mixpanel.init(…) call you already have, replace the project token and add api_host so events go to Sequential instead of Mixpanel. ```js mixpanel.init('YOUR_MIXPANEL_INGEST_KEY', { api_host: 'https://api.usesequential.com' }); ``` Keep every other option you pass. If the init reads the token from an environment variable, change the variable instead of the code. ## New install: npm (bundled apps) Install the package, then initialise it once, in browser-only code. ```sh npm install mixpanel-browser ``` ```js import mixpanel from 'mixpanel-browser'; mixpanel.init('YOUR_MIXPANEL_INGEST_KEY', { api_host: 'https://api.usesequential.com' }); ``` ## New install: script tag (plain HTML, tag managers) Mixpanel's own loader plus the one line that points it at Sequential. Paste it once into your site's ``, or into a Google Tag Manager Custom HTML tag that fires on All Pages. Nothing else to change. The loader is Mixpanel’s own. The Mixpanel SDK refuses `init` without it, so keep it as is. It sets `track_pageview: true`, so a page view arrives as soon as it is pasted. Without it, Mixpanel sends nothing until your code calls `mixpanel.track(…)`. ```html ``` ## What is supported What Sequential does with Mixpanel traffic: | Capability | Support | Notes | |---|---|---| | Custom events | Partial | `mixpanel.track(name, props)`; properties whose names start with `$` are dropped (except element properties). | | Page / screen views | Yes | `track_pageview` / `$mp_web_page_view`. | | Autocaptured clicks & forms | Yes | Mixpanel's autocapture clicks, submits, rage and dead clicks. | | Identify (user id) | Yes | `mixpanel.identify(id)`. | | User properties | No | `mixpanel.people.set` from the browser SDK does not land today: its form-encoded `/engage` request is refused. Tracked as a known issue. | | Groups / accounts | No | Group profiles are not supported. A `/groups` update is stored as user properties on a user with no id. | | Errors | No | No error events; track them as custom events. | | Session replay | Partial | Mixpanel's own recording is not accepted (`/record` has no route). Add Sequential's recorder: it joins Mixpanel's session id automatically. | | DevTools: errors, console, network, performance | Yes | Captured by Sequential's recorder once the session-replay line is on the page. | | Feature flags, surveys, experiments | No | No `/decide` or flags route. | | Server-side SDKs | No | Browser and PostHog mobile SDKs only. Server-side SDK user agents are rejected as bots (403). | > **Known issue:** user profile updates from the browser SDK (`mixpanel.people.set` and the other `people.*` calls) are not stored today. Keep the calls, since they do no harm, but do not rely on user properties from Mixpanel in Sequential yet. Event properties whose names start with `$` are also dropped, apart from autocapture’s element properties, so give your own properties plain names. ## Add session replay (optional) Optional, one line. The recorder picks up Mixpanel's session and user ids on its own, so every event above lands on the replay timeline. Put it on every page you want to replay, after the SDK. What it records and masks is set per project in Sequential (Settings → Projects → Session replay), not in the page. See [Session replay](/docs/session-replay). ```html ``` ## Content-Security-Policy Only if the site sets a Content-Security-Policy. Add these origins to the directives it already has; do not replace them. ```text script-src https://api.usesequential.com https://cdn.mxpnl.com https://cdn.usesequential.com connect-src https://api.usesequential.com ``` ## Check it works 1. Load a page of the site in a normal browser (headless and automated browsers are rejected as bots) and open the network panel. 2. Look for requests to the Sequential API URL that answer 2xx. A **401** means the key is wrong, or belongs to another source (every key works with one SDK only). A **403** means the request looked like a bot. 3. In Sequential, Settings → Projects → Setup shows your source as "receiving" once its first event arrives. Until then, the Sequential SDK and session replay read "no events yet", and another source's line does not show. The page checks again every few seconds for 5 minutes after you open it. After that, reload it. The first event can take up to about a minute to appear. More in [Check your install](/docs/verify).