Skip to content

For developers

Built for the teams who ship it

SDKs for web, iOS, Android, Node.js and Laravel, plus an HTTP API. Install one, send a test event, and watch it arrive in the dashboard

Hands typing code on a laptop keyboard

What you build with

Every source sends the same event format, so web, app and server activity lands in one warehouse

SDKs for every surface

A JavaScript SDK from cdn.sfere.io or npm with React bindings, Swift and Android SDKs for apps, and Node.js and Laravel SDKs for your backend

HTTP API

One POST per event or batches of up to 100, authenticated with a source write key. Any language that can make a request can send events

Pipes and functions

Route each source to the Sfere Data Warehouse or another destination, and run JavaScript that filters, transforms or enriches events on the way

Fits the stack you already run

Add Sfere next to your existing analytics and tag manager. Each website, app or backend becomes its own source with its own keys and pipes

  • GA4 ecommerce event names (view_item, add_to_cart, purchase, refund) across web, app and server, so one instrumentation feeds analytics and ad-platform conversions
  • Browser keys are public and safe in page source. Server keys stay on your backend
  • Server SDKs forward the customer's IP, user agent and click IDs from the original request
  • Google Tag Manager or a single script in the page head: both load the same SDK

Start from the documentation

Step-by-step guides with copy-ready code for each platform, written against the SDKs as they are published

  • Quickstart: create a source, add the script, and see the first page view in Live events
  • Guides for websites, React and Next.js, iOS, Android, the HTTP API, Node.js and Laravel
  • Reference for event names, write keys, consent, pipes, functions and monitoring
Open the Quickstart

How the system fits together

Collect, resolve, store, activate, and prove, as one vendor-neutral architecture

Read the architecture

See Sfere on your own customer data

Book a walkthrough with our team: how your channels join into one profile per customer, and what we would run first