Lesson 6
How to send your own custom events
Call track() or record() to capture the business actions autocapture can't see, with real-world examples for common use cases.
Video comingThe video is being filmed. The steps below are the whole lesson.
In this lesson
- 1Send one named business event with intempt.record({ eventTitle, userId, data }) from a handler, and confirm it lands in Live with the user attached. Use track only with a non-empty data object.
Setup checklist
The 16 steps to get your data flowing, from connecting a source to seeing a known person in Live. Tick them off as you go; your ticks stay in this browser.
Open the setup checklist (PDF)0 of 16 ticked
You are done when
- The JavaScript source shows Type Source and Status Active on the Connections tab.
- An event from your own page appears in Events, Live after a reload.
- Table shows Ingested, Created and System rows, and you built one Created event.
- A record() call arrives in Live carrying the user.
- The Event type dropdown header shows your provisioned collection count.
Your tech stack and tools
The core stack (everything you actually need)
- Intempt console: Integrations and Events (This is where you connect sources and watch events arrive live)
- JavaScript SDK (intemptjs) (This is the snippet that tracks your website. It captures clicks and page views for you)
- Public API key (This is what switches the snippet on. Without it, nothing arrives)
Highly recommended optional upgrades that level up your work
- Node.js SDK (This is how your backend sends events, like a signup or a payment)
- iOS SDK (This is how your iPhone app sends events)
- Android SDK (This is how your Android app sends events)
- Stripe (This is how your payments come in. It connects in one click)
- Live data feed guide (This is the full reference for watching events arrive)
Everything you need is free. Your first 100K events a month are included on every plan.