Installation Guide

Overview

When you implement Intempt, you add Intempt code to your website, app, or server. This code generates messages based on specific triggers you define.

In a basic implementation, the code can be a snippet of JavaScript that you paste into the HTML of a website to track page views. It can also be as complex as a custom event tracked via a server-side library.

The best way to understand how Intempt works is to see it in action.

Before you begin

Before starting your Intempt implementation, you need:

An Intempt account with an organization and project

Access to the code for a website or iOS app

Ability to install JavaScript or modify your codebase

Tip: If you don’t have an existing site or app, consider creating a simple GitHub Pages website to get started quickly.

Create separate development and production projects

Intempt strongly recommends creating separate dev and prod projects to avoid polluting production data.

Each project can be labeled by environment (e.g., "Production", "Development", "Staging") — this helps maintain clean data and isolate testing.

Step 1: Create your API key

The API key is a unique identifier for a source. It tells Intempt:

Which source the data comes from

Which organization the data belongs to

To create a write key:

Go to the API Keys section.

Click Create public key.

Copy the API key — you will need it in later steps.

⚠️ Attention

Save the API key securely. You will not be able to access it later.

Note

Cloud sources do not use write keys — they rely on a token from your connected service.

Step 2: Create a source & set up autocapture

Autocapture makes it easy to start collecting:

Page views

Clicks

Form submissions

Input changes

It automatically captures events without manual event coding. If you restructure your frontend, events continue to be collected without updating code.

To set up autocapture:

Go to Integrations → Sources

Click Create Source

Select Web

Under Installation, copy the JavaScript snippet (script tags + function)

Replace the API key

Replace "YOUR_API_KEY" with the API key created in Step 1.

Add the snippet to your website:

Paste the first block inside <head>

Paste the second block inside <body>

Add it to your base HTML template so it loads on all pages

Once added, autocapture begins tracking:

Clicks

Input changes

Form submissions

Typing in input/select/textarea fields

Label interactions

All events automatically flow into Intempt.

Autocapture limitations

Autocapture is extremely useful, but not enough for deep product analytics.

1. High volume = noisy tables

Autocapture collects every click, form change, etc.
In high-traffic environments, this can overwhelm your Live Events view.

2. Custom events provide richer insight

Autocapture is general-purpose.
To get the most value, you should send custom events for the behaviors that matter.

Examples:

Completing onboarding

Adding items to cart

Completing checkout

Searching for something

Viewing important pages

Server-side actions

Step 3: Set up custom events

Custom events let you capture meaningful actions anywhere in your codebase — frontend, backend, or mobile.

1. Install the Web tracker (from previous section)

Once installed, you can start logging custom events.

2. Add the tracking code to your codebase

You can log a custom event using the record function:

Example: Purchase event

Getting custom events right

Custom events require planning:

Start with your product goals
What events matter? (e.g., checkout, onboarding, subscription)

Ensure data is accessible
You may need helper functions or accessors.

Send clean, consistent event structures
So you can use them in reports, actions, analytics.

There are many places where you can refine event structure — naming, nesting, attributes, and consistency across pages and devices.

Step 4: Identify users

Autocaptured events automatically associate session-level identifiers.
Custom events require manual identification.

Example: Identify with email

To track users across:

browsers

devices

mobile apps

logged-out → logged-in states

Always set a unique identifier such as:

database user ID

phone number

Identification allows Intempt to merge anonymous + known sessions.

Step 5: Create events (Event Editor)

A single event might not describe a full behavior.

Example:
A signup may include:

Clicking "signup"

Filling fields

Submitting form

Completing verification

Defined events allow you to combine:

autocapture events

custom events

page views

into a single defined event for cleaner analytics.

Defined events also work retroactively, tagging past events automatically.

What’s next?

Now that you’ve set up:

Autocapture

High-quality custom events

User identification

Defined events

You will start seeing a stream of data in Intempt.

Next steps:

Create reports

Explore dashboards

Build journeys

Personalize experiences

Trigger messages

Analyze product behavior

Explore template reports for inspiration

This foundation now enables:

Behavioral analytics

Conversion funnels

Retention analysis

Segmentation

Personalization

Experimentation

Basic Intempt Installation

Installation Guide#

Overview#

Before you begin#

Create separate development and production projects#

Step 1: Create your API key#

To create a write key:#

⚠️ Attention#

Note#

Step 2: Create a source & set up autocapture#

To set up autocapture:#

Replace the API key#

Add the snippet to your website:#

Autocapture limitations#

1. High volume = noisy tables#

2. Custom events provide richer insight#

Step 3: Set up custom events#

1. Install the Web tracker (from previous section)#

2. Add the tracking code to your codebase#

Example: Purchase event#

Example: Signup event (frontend form data)#

Getting custom events right#

Step 4: Identify users#

Example: Identify with email#

Step 5: Create events (Event Editor)#

What’s next?#