Event taxonomy

Every attribute on every event collection Intempt provisions, by source, with the type each carries and an example value.

Overview

Event reference lists which collections exist. This section lists what is inside them: every attribute on every collection, the type it carries, an example value, and what it means.

One page per source. Pick the source you send from.

Source	Collections	What it covers
Web (JavaScript)	`web_*`	Page, session, click, form and change events from the site snippet
iOS	`ios_*`	Screen, session, touch and field-edit events from the iOS SDK
Android	SDK records	Screen, session, touch, cart and product events from the Android SDK
Shopify	`shopify_*`	Orders, checkouts, products and customers from a connected store
Stripe	`stripe_*`	Invoices, charges, subscriptions, disputes and balances
HubSpot	`hubspot_*`	Contact, company and deal create/update, plus owners
Intempt system	`system_*`	Written by the platform itself, not by a source you connect

How to read a table

Every page has one section per collection and one row per attribute.

Column	Means
Attribute	The key as it arrives on the event. A dotted key such as `attribute.user.id` is a nested path, not a literal dot in the name.
Title	The label the console shows for it.
Type	The wire type the platform stores: String, Integer, Decimal or Boolean.
Example	A real value, taken from the schema rather than invented.
Description	What the attribute means.

📘 The Android table has different columns, on purpose

Every source here except Android provisions collections in the shared events namespace, and those definitions carry a description and an example for each attribute. Android sends SDK records instead, and those carry names and types only. So the two tables differ by what their schema can support:

Source	Columns	Why
Web, iOS, Shopify, Stripe, HubSpot	Attribute, Type, Example, Description	The collection schema carries a description and an example for every attribute
Android	Attribute, Type, Required	The record schema carries neither, but does say whether a field can be absent

Neither table is missing anything its schema holds. Making them match would mean either inventing Android examples or dropping real ones from the other five.

📘 A hidden attribute still arrives

A title marked (hidden) means the attribute lands on the event but is not offered in the console attribute pickers, so you will not find it when building a segment. It is documented because it is on the wire and you may see it in an export or an API response.

Where these come from

These pages are generated from the same schema definitions the platform provisions collections from, so an attribute listed here is one the platform actually creates. If a collection gains an attribute, it appears here when the pages are regenerated.

What is not here

Source	Why
React Native, Node.js, PHP, Python	Identity records only, with no event payload to list. See Record taxonomy.
HTTP API	The schema is yours to define, so there is no fixed taxonomy to list.
Scheduled pull sources	These arrive with the upstream system's own schema rather than an Intempt-authored one. See Source taxonomy.

Where to go next

Event reference — which collections each source provisions
Source taxonomy — every source, and what it creates on connect
SDK record reference — the wire-level record shapes
System attribute reference — attributes on the profile rather than the event