Source Taxonomy
Every source Intempt reads from, the collections each one provisions on connect, and how many fields you get without writing a mapping.
Source Taxonomy
When you connect a source, Intempt provisions its collections with a schema already defined. You do not write a field mapping and you do not normalise the payload yourself.
Two numbers describe a source and they measure different things, so both are here:
| Column | Means |
|---|---|
| Collections | What gets created in your project when you connect the source |
| Fields | Total schema fields across those collections, including nested records |
Every source
| Source | Type key | Kind | Collections | Fields |
|---|---|---|---|---|
| Web (JavaScript) | web | SDK | 12 | 274 |
| iOS | ios | SDK | 9 | 206 |
| Android | android | SDK | 12 | 169 |
| React Native | react-native | SDK | 1 | 12 |
| Node.js | nodejs | Server SDK | 1 | 12 |
| PHP | php | Server SDK | 1 | 12 |
| Python | python | Server SDK | 1 | 12 |
| HTTP API | api | Direct | you define | you define |
| URI feed | uri_feed | Scheduled pull | you define | you define |
| Shopify | Shopify | Platform | 24 | 2170 |
| Stripe | Stripe | Platform | 17 | 738 |
| HubSpot | HubSpot | Platform | 7 | 237 |
A server SDK with one collection is not a limitation. Node, PHP, Python and
React Native send through the same ingestion endpoint as everything else. They
provision only Identify because their events are yours to define, not a shape
we can agree in advance.
Beyond the natively-schema'd sources
The sources above are the ones Intempt ships a schema for. Scheduled pull sources can additionally bring in a long tail of databases, warehouses and SaaS APIs.
Those arrive with the upstream system's own schema, not an Intempt-authored one, so the out-of-box taxonomy below does not apply to them. Availability depends on your plan, so ask us rather than assuming a given system is supported.
Shopify (24 collections, 2170 fields)
| Collection | Fields |
|---|---|
cancelled_orders | 433 |
placed_orders | 433 |
fulfilled_orders | 432 |
order_refunds | 145 |
product_ordered | 101 |
abandoned_checkouts | 100 |
draft_orders | 91 |
products | 91 |
fulfillments | 80 |
customers | 55 |
SessionEnd | 29 |
SessionStart | 26 |
collections | 22 |
smart_collections | 22 |
PageLeave | 15 |
SubmitOn | 15 |
PageView | 14 |
ClickOn | 13 |
ChangeOn | 12 |
inventory_levels | 10 |
Identify | 8 |
added_to_cart | 8 |
removed_from_cart | 8 |
product_viewed | 7 |
Stripe (17 collections, 738 fields)
| Collection | Fields |
|---|---|
invoices | 112 |
subscriptions | 79 |
charges | 75 |
checkout_sessions | 75 |
payment_intents | 53 |
subscription_schedule | 51 |
payment_methods | 44 |
customers | 42 |
discounts | 33 |
customer_cash_balance_transactions | 31 |
refunds | 26 |
disputes | 24 |
customer_tax_ids | 20 |
reviews | 20 |
early_fraud_warnings | 18 |
products | 18 |
cash_balance | 17 |
HubSpot (7 collections, 237 fields)
| Collection | Fields |
|---|---|
created_deals | 44 |
updated_deals | 44 |
created_companies | 34 |
created_contacts | 34 |
updated_companies | 34 |
updated_contacts | 34 |
owners | 13 |
What every collection shares
Whatever the source, each event carries the same envelope: eventId, profileId,
sessionId, timestamp, userId and a data record holding the payload. See
Data Enrichment.