Lesson 1

How Intempt receives your events

How Intempt receives events: auto-tracking, the browser SDK's custom event methods, and the server-side Track Data API.

Video comingThe video is being filmed. The steps below are the whole lesson.

In this lesson

  1. 1Decide your path: browser autocapture plus track() for web pages, or a server SDK or the Track Data API for anything with no browser.
Read the reference docs for this lesson

Setup checklist

The 18 steps to ship the SDK, from your first line of code to an identified event in Live. Tick them off as you go; your ticks stay in this browser.

Open the setup checklist (PDF)

0 of 18 ticked

You are done when

  • Your custom event appears on Events, Live in the console.
  • The event is attached to the identified user's profile, not an anonymous one.
  • Browser only: tested on a real domain, since tracking is blocked on localhost.
  • Server SDKs: flush or close ran so buffered events were sent before the process exited.

Your tech stack and tools

The core stack (everything you actually need)

Highly recommended optional upgrades that level up your work

Every SDK is free. Your first 100K events a month are included on every plan.