Record taxonomy
Every field on every record each SDK and connected source sends, with the type it carries and whether it is required.
Overview
SDK record reference lists which records each source sends. This section lists the fields inside them, with the type each carries.
One page per source. Pick the one you send from.
SDKs
| SDK | Records | What it sends |
|---|---|---|
| Web (JavaScript) | 38 | Page, session, click, form, technology and referrer detail |
| iOS | 28 | Screen, session, touch, device and app detail |
| Android | 13 | Screen, session, touch, cart and product detail |
| React Native | 5 | Identity only |
| Node.js | 5 | Identity only |
| PHP | 5 | Identity only |
| Python | 5 | Identity only |
| Intempt system | 4 | Written by the platform itself |
Connected sources
| Source | Collections | What it provisions |
|---|---|---|
| Shopify | 24 | Orders, checkouts, products, customers, inventory |
| Stripe | 17 | Invoices, charges, subscriptions, disputes, balances |
| HubSpot | 7 | Contact, company and deal create/update, plus owners |
How to read a table
| Column | Means |
|---|---|
| Attribute | The field name as it arrives. A dotted path means the field sits inside a nested record: data.targetText is the targetText field carried on that record's data. |
| Type | The type the field carries. A value in backticks is another record in the same source, listed in its own section on that page. |
| Required | Whether the field always arrives. A field that may be absent shows No, and so does any field inside an optional parent. |
📘 Nested records are flattened, not summarised
Most records carry a data record holding the payload, defined inline rather than as a record of
its own. Those inner fields are listed here as dotted paths under their parent, so nothing is left
implied behind a type name.
📘 These schemas carry no examples
Unlike the event taxonomy, these definitions hold names and types only. There are no example values or per-field descriptions to show, so the tables list what the schema actually carries and nothing more. For an event collection with descriptions and real example values, use Event taxonomy instead.
A server SDK sending five records is not a limitation
React Native, Node.js, PHP and Python each send the same five identity records. A server has no page, no screen, no viewport and no referrer, so there is nothing for autocapture to collect. They send identity; you send the events.
Where to go next
- SDK record reference — which records each source sends
- Event taxonomy — event collection attributes, with descriptions and examples
- Event reference — which event collections each source provisions
- Source taxonomy — every source, and what it creates on connect