Overview

A source connects an app or server to Intempt so it can send event data. Intempt supports four source types: JavaScript (web), Node.js, iOS, and Android. Create a separate source for each website, app, or server you want to track, so events from each one stay attributable to where they came from.

How it works

Sources live on the Integrations page, in the Connections tab, alongside platforms (HubSpot, Stripe, Shopify) and destinations (Gmail, Twilio, SendGrid, Slack, Amazon SES). See Integrations Overview for the full connectors table, platforms, destinations, and the Domains tab.

Each source type opens its own setup panel when you connect it:

• JavaScript asks you to enter a Connection Name, which Intempt checks against your existing connectors to prevent duplicates.

• Node.js, iOS, and Android create the source immediately under an auto-generated name (for example, "Untitled source-482"), which you can change afterward with Rename.

Every panel includes a copyable installation snippet for that source type. Once created, the source appears as a row in the Connected Integrations table, tagged Source.

Getting started

1. Go to Integrations in the left navigation.

2. On the Connections tab, click Add Integration.

📘 Media pending

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

3. Under Sources, click Connect next to the source type you want to add.

Connecting a JavaScript source

1. In the Configure JavaScript panel, enter a Connection Name (for example, "Marketing Website").

2. Copy the installation snippet (a script tag that loads intempt.min.js with your organization, project, and source IDs) and add it to your site.

3. Click Connect JavaScript.

📘 Media pending

Screenshot of the Configure JavaScript panel hasn't been captured yet.

Connecting a Node.js source

1. In the Configure Node JS panel, click Connect Node JS. Intempt creates the source right away, and the panel shows Source Type: Server.

2. Copy the Source ID that appears once the source is created.

3. Copy the installation snippet from the panel to install the Node.js SDK.

Connecting an iOS source

1. In the Configure iOS panel, copy the Swift Package Manager installation snippet.

2. Click Connect iOS.

Connecting an Android source

1. In the Configure Android panel, copy the Gradle installation snippet.

2. Click Connect Android.

📘 Media pending

Screenshot of the Connected Integrations table hasn't been captured yet.

After you connect

The new source appears as a row in the Connected Integrations table with a status of Active, Syncing, Error, or Disabled. Open the row's action menu to Rename or Delete the source.

📘 Good to know

Node.js, iOS, and Android sources are created with an auto-generated name, so use Rename right after connecting one to make it easy to identify later in the connectors table.

Use cases

• Tracking your website. Connect a JavaScript source to track events from a web application.

• Tracking a mobile app. Connect an iOS or Android source for mobile analytics from your app.

• Server-side tracking. Connect a Node.js source for server-side event tracking.

• Separating environments. Create one JavaScript source for production and another for staging, so their events don't mix in the same connector.

• Separating properties. Create a distinct source for each website or app you own, instead of sending all their events through a single shared source.

• Renaming a default source. Use Rename on a Node.js, iOS, or Android source to replace its auto-generated name with something identifiable.

Where to go next

• Integrations Overview for the full connectors table, platforms, destinations, and the Domains tab.

• Basic Intempt Installation for installing the JavaScript SDK end to end, including API keys.

• JavaScript SDK, iOS SDK, and Android SDK for the complete method reference for each SDK.

• REST API for sending events directly without an SDK.