Skip to main content
Spotzee ships three first-party SDKs. They share the same wire shape, the same publishable-key auth, and the same pinned API version, so a customer running a website plus an iOS app plus an Android app sees one user record across all three.

​
Pick an SDK

JavaScript SDK

Install, identify users, track events, and register devices from a browser, Node app, or script tag.

iOS SDK

Install via SPM or CocoaPods, identify users, track events, register for APNs, render in-app notifications, unwrap Universal Links.

Android SDK

Install via JitPack, identify users, track events, register for FCM, render in-app dialogs, unwrap App Links.

​
What every SDK does

  • Identifies users. Anonymous IDs are minted on first use and persisted locally. Calling identify with an external_id aliases the anonymous record to the known one.
  • Tracks events. A single track call flows into journeys, segments, and campaign triggers.
  • Registers devices. APNs, FCM, or browser push tokens land on the user record so any push channel can target them.
  • Renders in-app notifications. Banner, alert, and HTML content types. iOS and Android render natively; the JavaScript SDK fetches and lets you render however you want.
  • Authenticates with publishable keys (pk_…). These are safe to ship in client builds. Read Manage API keys for the key model.
  • Pins an API version. Every SDK release sets Spotzee-Version to a known release date so a future API change does not break a shipped client.

​
Pick the right surface

​
Where the SDKs fit

Sync users from your backend

SDKs cover the client-side flows. For backend-driven user import, use the recipe.

Send events from your backend

Backend events can mix with SDK events on the same user record.

Configure push providers

Set up APN and FCM credentials before mobile SDKs can register tokens.

Subscription preferences

The preference centre lives on a web page, not inside the mobile SDKs.