Track customer data

Tracking is how you feed customer identity and behaviour into Binoban. Every downstream capability — building audiences, activating Engage messaging, serving Retail Media, reading Insights — runs on the profiles and events you send here. Get tracking right first; everything else builds on it.

What tracking is

The Binoban spec defines a small number of call types, each representing a distinct kind of semantic information about a customer, and all sharing a common set of fields. That's the whole model: identity (who a customer is) plus behaviour (what a customer did) is the foundation every downstream capability — audiences, Engage, Retail Media, Insights — runs on.

The two calls

• Identify — who the customer is. Associates the current person with your userId and any traits (email, plan, locale). Before you identify anyone, Binoban already tracks them under an automatically-assigned anonymousId; Identify links that anonymous history to a known user.
• Track — what they did. Records an action (product_added, order_completed) with properties describing it, in the shared event shape so events mean the same thing across every source.

That pair is the whole surface every SDK and API in this section supports. page, for pageviews, exists on the Web SDK only — it isn't part of the public surface on Native, React Native, or the Tracking REST API.

Choose your path

Send identity and events from wherever your customer is. Most integrations use more than one path — a client SDK for on-device behaviour plus the REST API for trusted server-side events.

Path	You use	Best for
Web SDK	JavaScript loaded in the browser	On-site behaviour, identity, and pageviews
Native SDK · Android	Kotlin, installed via Gradle (io.binoban.sdk:sdk-android), initialized in Application	A native Android app
Native SDK · iOS	Swift, installed via Swift Package Manager, initialized in AppDelegate	A native iOS app
React Native	A thin TurboModule bridge over the native outputs — not a standalone SDK	A React Native app
Tracking REST	HTTP POST straight from your backend	Trusted server-side state your backend owns — orders, payments, refunds

Android and iOS are one Kotlin Multiplatform SDK shipped as two outputs, sharing the same tracking model and method names. apiHost is mandatory on the Native SDK — there's no default.

Next steps

• Send your first event — the Quick Start walks the fastest path end to end.
• Model identity well — Identity strategy covers anonymousId → userId across sources.
• Standardize your events — the ecommerce catalogue defines the common events and their properties, and Limits & validation lists the field rules and value ranges Binoban enforces.
• Then activate — turn this data into outcomes with Engage or Retail Media.