How data flows in and out: sources, destinations and syncs

In this lesson

1. 1Open Create event and the Event type dropdown; read the header count (All events · N) and the collection names your source provisioned. Close without saving.
2. 2Before connecting another source, check the source and destination reference for what it provisions.

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.

0 of 16 ticked

1. 1.Open Integrations and stay on the Connections tab; it lists no connections yet.
2. 2.Click Add integration and, under Sources, click JavaScript.
3. 3.Type a Connection name for the site (not 'JavaScript') and click Proceed. The source is created at that click and the snippet appears.
4. 4.Read the snippet's last line: it ends key={YOUR_API_KEY}, a placeholder.
5. 5.Go to Settings, API keys, click Create Key, choose Public, pick this project, click Create key and copy the key.
6. 6.Paste the key over {YOUR_API_KEY} and paste the snippet into your site's HTML on every page.
7. 7.On Connections, confirm the row shows Type Source, Status Active and a dash under Last Sync.
8. 8.Open Users, then Events, switch to the Live tab, reload your tracked page and watch the event arrive.
9. 9.In Live, click Pause, then use Create event on a row to build a definition with auto-mapped conditions.
10. 10.Back on Table, filter or sort by the Type column so Ingested, Created and System are all visible.
11. 11.Filter to Ingested, then create one Created event on top of an ingested one (Create event, Event type, Conditions, Save).
12. 12.For every event you add, write down the question it answers before you collect it.
13. 13.Open Create event and the Event type dropdown; read the header count (All events · N) and the collection names your source provisioned. Close without saving.
14. 14.Before connecting another source, check the source and destination reference for what it provisions.
15. 15.Call intempt.identify({ userId }) with a stable identifier (usually email) wherever a person signs up or logs in; autocaptured events identify for you.
16. 16.Send 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.

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.