Event reference

Every event collection Intempt provisions out of the box, by source, with the fields each one carries.

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 collections in the shared events namespace. 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

For the attributes inside each of these collections, with types and example values, see Event taxonomy.

Web (JavaScript)

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

Collection
`web_change_on`
`web_click_on`
`web_leave_page`
`web_session_end`
`web_session_start`
`web_submit_on`
`web_view_page`

iOS

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

Collection
`ios_action`
`ios_edit_field`
`ios_launch`
`ios_leave_screen`
`ios_session_end`
`ios_session_start`
`ios_touch`
`ios_view_screen`

Shopify

Synced from a connected Shopify store.

Collection
`shopify_abandoned_checkouts`
`shopify_customers`
`shopify_draft_orders`
`shopify_order_cancelled`
`shopify_order_fulfilled`
`shopify_order_refunded`
`shopify_placed_order`
`shopify_product_ordered`
`shopify_products`

Stripe

Synced from a connected Stripe account.

Collection
`stripe_cash_balance`
`stripe_charges`
`stripe_checkout_sessions`
`stripe_customer_cash_balance_transactions`
`stripe_customer_tax_ids`
`stripe_customers`
`stripe_discounts`
`stripe_disputes`
`stripe_early_fraud_warnings`
`stripe_invoices`
`stripe_payment_intents`
`stripe_payment_methods`
`stripe_products`
`stripe_refunds`
`stripe_reviews`
`stripe_subscription_schedule`
`stripe_subscriptions`

HubSpot

Synced from a connected HubSpot portal.

Collection
`hubspot_company_created`
`hubspot_company_updated`
`hubspot_contact_created`
`hubspot_contact_updated`
`hubspot_deal_created`
`hubspot_deal_updated`
`hubspot_owners`

Intempt system

Emitted by Intempt itself when a journey performs an action.

Collection
`system_journey_action_event`

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

The two mobile SDKs do not capture the same things, and they do not carry it the same way.

iOS provisions eight collections in the shared events namespace, the ios_* list above. Android provisions none: what an Android app sends arrives as SDK records instead. Its events are still documented, in Android event taxonomy for what each event carries, and Android record taxonomy for the full wire record. The Android tables have no example values, because those schemas carry names and types only.

The table below is what each SDK captures, not what each provisions as a collection. Identify is a record on both platforms rather than an event collection, for instance.

What the SDK captures	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. An iOS app has none of those, so the same four events have to be sent as custom events from iOS.

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 under different names, so a cross-platform segment must include both.

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.

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.