Overview

Intempt doesn't have a one-click connector for Segment, Mixpanel, or Amplitude. Moving from one of them means three things: connecting an Intempt source for each platform you currently track (web, iOS, Android, or a server), re-implementing your identify, track, group, and alias calls against Intempt's SDK, and deciding what happens to your existing historical data.

This guide walks through all three, plus how to run Intempt alongside your current tool before you remove it.

How it works

Method mapping

Segment, Mixpanel, and Amplitude all use a similar vocabulary for identifying users and tracking events. Intempt's SDK covers the same actions, with the same method names across the JavaScript, iOS, and Android SDKs:

📘 Good to know

Intempt also ships purpose-built ecommerce methods your previous tool may have needed a custom event for: productAdd(), productOrdered(), and productView(). See the JavaScript SDK reference for their parameters.

Exact call syntax differs by platform. See the JavaScript SDK, iOS SDK, and Android SDK references for each method's full parameter table.

What auto-tracking replaces

Once an Intempt source is connected, the SDK automatically records page views, page exits, sessions, clicks, and form activity with no code required. If your current setup fires manual events for these (a page() call on every route, or a click handler that just logs a button name), you can drop them and rely on auto-tracking instead. Keep manual track()/record() calls only for events specific to your business, like a purchase or a plan upgrade.

Historical data

Intempt has no direct historical-data importer for Segment, Mixpanel, or Amplitude. Two options carry existing data over:

• CSV import, for historical users, accounts, or events. Drag a CSV into the Users, Accounts, or Events page and map its columns to Intempt attributes. See Data import for file requirements and the column-mapping flow.
• The Track Data API, for backfilling events from a server. Each event payload accepts an explicit timestamp field, so backfilled events keep their original time instead of being stamped with the import time. See Track Data for the request schema.

Getting started

Step 1: Connect an Intempt source

Connect a source for each platform you're currently tracking with Segment, Mixpanel, or Amplitude.

1. Go to Integrations and click Add Integration.
2. Under Sources, click Connect next to JavaScript, iOS, Android, or Node.js, depending on where your existing tracking lives.

📘 Media pending

Screenshot of the Add Integration sidebar hasn't been captured yet.

3. Follow the setup panel for that source type and copy its installation snippet.

📘 Media pending

Screenshot of the source configuration panel hasn't been captured yet.

See Creating a Source for the full panel-by-panel walkthrough, and Basic Intempt installation for the JavaScript source end to end, including creating the API key the snippet needs.

Step 2: Re-implement your tracking calls

Go through the calls your current implementation makes and swap each one for its Intempt equivalent from the mapping table above. A Segment or Mixpanel identify call, for example:

// Before (Segment)
analytics.identify('user123', { email: 'user@example.com', plan: 'premium' });

becomes:

// After (Intempt)
intempt.identify({
  userId: 'user123',
  userAttributes: { email: 'user@example.com', plan: 'premium' }
});

Do the same for your track, group, and alias calls. Leave out any page() calls your old tool needed. Intempt captures those automatically.

Step 3: Run both in parallel, then cut over

Keep your existing tool's tracking code in place while Intempt's snippet runs alongside it. Compare event volume and the attributes each tool captures for the same user actions. Once you've confirmed Intempt is receiving equivalent data, remove the old tool's snippet and API keys.

Step 4: Backfill historical data

If your reports need continuity across the cutover date, import what you need with a CSV (for user and account profiles, or a bulk event export) or the Track Data API (for server-side event backfills with their original timestamps). See the Historical data section above for which one fits.

Use cases

• Replacing Segment as your CDP while keeping the same identify/track/group vocabulary your team already writes code against.
• Consolidating Mixpanel funnels and Amplitude cohorts into Intempt's own analytics, instead of maintaining tracking code for two platforms.
• An ecommerce site swapping manual page and product events for Intempt's autocaptured page views and built-in productAdd/productOrdered/productView methods.
• A mobile team retiring Amplitude's iOS and Android SDKs in favor of Intempt's native iOS and Android sources.
• A backend service using Mixpanel's server-side library switching its event calls to the Track Data API.
• Merging an anonymous ID with a known user ID after login, using alias() in place of the old tool's own alias call.
• Backfilling last quarter's event history via CSV or the Track Data API so reports don't show a gap starting at the cutover date.

Where to go next

• JavaScript SDK for the full method reference, auto-tracking details, and error handling.
• iOS SDK and Android SDK for mobile method signatures.
• Event Tracking (SDK deep-dive) for when to use the browser SDK versus the Track Data API.
• Track Data for the server-side ingestion schema, including backfill timestamps.
• Creating a Source and Basic Intempt installation for connecting a new source.
• Data import for CSV-based historical backfills.