Skip to content
Docs menu Get started

Core concepts

Sources collect events, pipes carry them, functions reshape them on the way, and destinations store or deliver them

On this page

How an event moves#

SOURCEPIPEDESTINATIONWebsiteMobile appServerZid storePipeFunctions run hereFilterTransformEnrichSfere Data WarehouseIncluded with every accountAnother connected toolOne pipe per destinationSOURCEWebsiteMobile appServerZid storePipeFunctions run hereFilterTransformEnrichSfere DataWarehouseAnotherconnected toolDESTINATION
Select any part of the flow to open its guideOpen

Every event enters through a source, travels through one pipe per destination, and lands in that destination. A source can feed several pipes, so the same event can reach more than one destination.

Sources#

A source is one place where customer activity happens: a website, a mobile app, your backend, or an online store. Two websites are two sources, even if they use the same SDK, so each can have its own keys and pipes.

Source type How events arrive Guide
Website JavaScript SDK in the page head or Google Tag Manager JavaScript SDK
Mobile app iOS or Android SDK iOS, Android
Your backend HTTP API, Node.js SDK or Laravel SDK HTTP API
Online store Zid, connected by authorizing Sfere in Zid Zid

Events#

Every event has a type:

pageA page view on a websitesfere.page()
screenA screen view in a mobile appsfere.screen("Product", …)
trackSomething the customer did, such as add_to_cart or purchasesfere.track("add_to_cart", …)
identifyLinking the current visitor to a known customer ID and traits such as emailsfere.identify("user_1234", …)
groupLinking the customer to an account or companysfere.group("company_42", …)
aliasMerging two IDs for the same customersfere.alias(…)

Event names follow the GA4 ecommerce vocabulary (view_item, add_to_cart, begin_checkout, purchase, refund, sign_up, login), so one set of events feeds analytics and ad-platform conversions. See Track events.

Pipes#

A pipe connects one source to one destination. It can be enabled or paused, and a source and destination pair can be joined only once. Connecting a website or a Zid store builds its pipe to the Sfere Data Warehouse for you; for other sources, add a pipe in Pipes. See Pipes.

Functions#

A function is JavaScript that runs on every event a pipe carries. It can transform an event, filter it out, or enrich it with extra fields before delivery. See Functions.

Destinations#

A destination is where events are stored or delivered. Every account includes a Sfere Data Warehouse, powered by ClickHouse, with no warehouse to buy or provision. See Destinations and warehouse.

Profiles#

Events that carry a user ID, email or phone are merged into one customer profile in Profiles. Call identify when a customer signs in so their events carry the ID the profile is built on.