Event reference

Every event collection Intempt provisions out of the box: 49 collections across six sources, carrying 979 documented fields.

Overview

When you connect a source, Intempt provisions a fixed set of event collections for it. Each collection is one event type with a defined set of fields. You do not create these and you cannot rename them: they exist so that an event from your website and an event from your Shopify store land in a shape the platform already understands.

This page lists the 49 collections in the shared events namespace and the 979 fields they carry between them. The mobile SDKs provision a further set of their own, listed below.

Events you define yourself are covered in Setting up custom events. This page is only the ones you get automatically.

📘 Collections are provisioned per source, not per project

Connecting a Shopify store provisions the nine shopify_* collections. Connecting a second Shopify store does not create a second set — both stores write into the same collections, distinguished by the source the event arrived from.

Collections by source

Web (JavaScript) — 7 collections

Collected automatically by the JavaScript SDK once the snippet is installed.

Collection	Fields	Source
`web_change_on`	6	Web (JavaScript)
`web_click_on`	6	Web (JavaScript)
`web_leave_page`	9	Web (JavaScript)
`web_session_end`	27	Web (JavaScript)
`web_session_start`	24	Web (JavaScript)
`web_submit_on`	6	Web (JavaScript)
`web_view_page`	8	Web (JavaScript)

iOS — 8 collections

Collected automatically by the iOS SDK. Screen and control names come from the view controller and the control itself.

Collection	Fields	Source
`ios_action`	13	iOS
`ios_edit_field`	13	iOS
`ios_launch`	13	iOS
`ios_leave_screen`	4	iOS
`ios_session_end`	24	iOS
`ios_session_start`	24	iOS
`ios_touch`	13	iOS
`ios_view_screen`	3	iOS

Shopify — 9 collections

Synced from a connected Shopify store.

Collection	Fields	Source
`shopify_abandoned_checkouts`	27	Shopify
`shopify_customers`	15	Shopify
`shopify_draft_orders`	31	Shopify
`shopify_order_cancelled`	33	Shopify
`shopify_order_fulfilled`	19	Shopify
`shopify_order_refunded`	2	Shopify
`shopify_placed_order`	34	Shopify
`shopify_product_ordered`	24	Shopify
`shopify_products`	1	Shopify

Stripe — 17 collections

Synced from a connected Stripe account.

Collection	Fields	Source
`stripe_cash_balance`	4	Stripe
`stripe_charges`	51	Stripe
`stripe_checkout_sessions`	50	Stripe
`stripe_customer_cash_balance_transactions`	16	Stripe
`stripe_customer_tax_ids`	9	Stripe
`stripe_customers`	30	Stripe
`stripe_discounts`	19	Stripe
`stripe_disputes`	12	Stripe
`stripe_early_fraud_warnings`	6	Stripe
`stripe_invoices`	60	Stripe
`stripe_payment_intents`	34	Stripe
`stripe_payment_methods`	30	Stripe
`stripe_products`	12	Stripe
`stripe_refunds`	13	Stripe
`stripe_reviews`	8	Stripe
`stripe_subscription_schedule`	19	Stripe
`stripe_subscriptions`	45	Stripe

HubSpot — 7 collections

Synced from a connected HubSpot portal.

Collection	Fields	Source
`hubspot_company_created`	29	HubSpot
`hubspot_company_updated`	29	HubSpot
`hubspot_contact_created`	27	HubSpot
`hubspot_contact_updated`	27	HubSpot
`hubspot_deal_created`	31	HubSpot
`hubspot_deal_updated`	31	HubSpot
`hubspot_owners`	4	HubSpot

Intempt system — 1 collections

Emitted by Intempt itself when a journey performs an action.

Collection	Fields	Source
`system_journey_action_event`	4	Intempt system

A worked example: `web_view_page`

Every field in every collection carries a title, a description and an example. web_view_page in full, so you can see the shape:

Field	Title	Description	Example
`previousPage`	Previous page	The previous page visited in this session	`/`
`url`	URL	Full page URL	`https://www.intempt.com/`
`domain`	Domain	Website domain including subdomain, e.g., app.intempt.com	`www.intempt.com`
`query`	Query	Query parameters of the URL, e.g., ?utm_id=1234 for intempt.com?utm_id=1234	`?utm_source=Google&utm_medium=CPC&utm_campaign=sell&utm_term=marketing&utm_content=`
`path`	Path	Path of the URL following the domain pointing to a specific page, e.g., /company for intempt.com/company	`/company`
`windowWidth`	Window width	Width of the user's screen in pixels	`1920`
`hash`	Hash	Hash route of the first page of the user's session	`#install for help.intempt.com/docs#install`
`title`	Title	Title of the page	`Intempt Technologies`

Mobile SDKs provision differently

Both mobile SDKs provision collections, and they do not provision the same ones. iOS creates 9, Android creates 13.

Collection	iOS	Android
Identify	✅	✅
Session start / Session end	✅	✅
View screen / Leave screen	✅	✅
App install / upgrade	✅	✅
Touch	✅ `Touch`	✅ `Touch event`
Action	✅	❌
Edit Field	✅	❌
Change event	❌	✅
Fragment transition	❌	✅
Added to cart	❌	✅
Removed from cart	❌	✅
Product ordered	❌	✅
Product viewed	❌	✅

Two differences matter when you build across both platforms:

Commerce is Android-only. An Android app autocaptures added-to-cart, removed-from-cart, product-ordered and product-viewed into provisioned collections. An iOS app has none of those, so the same four events have to be sent as custom events from iOS. A funnel built on the provisioned collections will show Android traffic only.

A control interaction is named differently. iOS splits it into Action for a button press and Edit Field for a value change; Android records both as Change event and Touch event. The same user gesture lands in differently named collections, so a cross-platform segment must include both names.

What is not provisioned

React Native, Node.js, PHP and Python send events through the same ingestion API but provision no collections of their own. Events from those SDKs land in collections you define. The same is true of the HTTP API and URI feed sources.

Use cases

Check which collection an incoming event will land in before you build a segment on it.
Confirm a field exists on a collection before referencing it in a journey condition.
Size an integration: the field counts show how much of a Stripe or HubSpot object Intempt actually carries.
Decide whether you need a custom event, or whether a provisioned collection already captures what you want.