SegmentStream Cloud — managed measurement infrastructure

Add marketing analytics to your product — or run it for your clients

Attribution, incrementality testing and budget optimization — fully managed on SegmentStream Cloud. Under your brand, fed from any source, priced by what you process. Nothing to deploy.

See the SDK ↓

For SaaS platforms →For agencies & in-house teams →

segmentstream cloud

$ npm i -g @segmentstream/cli

$ segmentstream workspaces create acme --region eu

✓ workspace ready wk_acme · eu

$ segmentstream deploy

✓ segmentstream.yml deployed 4 sources · 2 models

$ segmentstream run --workflow refresh

✓ refresh complete identity graph + models updated

CLI preview — commands may change before GA.

REST + TypeScript SDK·MCP server per workspace·EU & US regions·workspace-per-client isolation·GDPR / DPA

Two products, one engine

Measuring your own brand's marketing? You're looking for the platform. This page is the infrastructure — the same engine, inside your product.

SegmentStream

The platform

Who it's for: Marketing teams and brands
What it does: Measures your own marketing
How it runs: Hosted dashboard and AI agent, run by us
Branding: SegmentStream
Pricing: Self-serve plans from $800/mo

Get started with the platform →

SegmentStream Cloud

The infrastructure

Who it's for: SaaS platforms and agencies
What it does: Measurement for your customers
How it runs: White-label module, SDK / API / MCP inside your product
Branding: Yours
Pricing: Platform fee + DPU / DQU usage

Same engine underneath — attribution, incrementality testing, budget optimization. The difference is whose brand is on the screen and whose customers are looking at it.

Two ways to run it

Two entry points into Cloud, metered the same way — pick yours by where your events come from.

Platform

For SaaS platforms

You already have a tracker — an adapter maps your existing events; clients never re-tag.

White-label Measurement module inside your app
TypeScript SDK and API to build your own surface
Your brand in front, our engine underneath

e.g. an ad-platform ships a white-label Measurement tab inside its own admin panel.

Agency

For agencies & in-house teams

No tracker needed — connect GA4 exports or warehouse SQL as event sources.

A workspace per client, the full engine in each
Adobe Analytics next — same adapter pattern
Nothing to deploy on the client's site

e.g. an agency runs 30 client workspaces off GA4 BigQuery exports.

Your product. Our engine.

Not an iframe — React components and a typed SDK. Build an admin panel in any layout and design system; SegmentStream appears nowhere your customers look. Switch the designs and see.

acme.example · Admin

▲ Acme Ads

Overview

Campaigns

Traffic

Measurement

Settings

Measurement

Predictive attribution · Last 30 days

ChannelSpendAttributed revenueROAS

Paid Search$48,210$193,8044.02

Paid Social$31,450$87,1202.77

Organic—$64,380—

Email$2,100$41,93019.97

+12.4% lift · significantGeo holdout · Paid Social · June

Three different products, one engine underneath — same data through the same SDK. Layout, navigation and design system are entirely yours.

Any source in. Any surface out.

Identity resolution, attribution models, incrementality and budget optimization run on managed SegmentStream infrastructure — deployed in the cloud region where your clients live.

Sources

SegmentStream SDK
First-party tracking, or your own tracker via an adapter
GA4 export
BigQuery event export, no re-tagging
Warehouse SQL
Any table you can query becomes an event source
Adobe Analytics
Next in line — same adapter pattern

Surfaces

White-label module
The full measurement UI inside your product, your brand
REST API & SDK
Every report and model output, programmatically
MCP for AI agents
Claude, Cursor or any agent queries the engine directly
Dashboards
Hosted workspaces when you don't want to build UI

Build your own admin panel

Everything the engine computes is reachable from a TypeScript SDK and REST API — query it, or drop the whole module into your UI.

Query the engine

typescript

const report = await ss.reports.attribution({
  workspace: "acme-retail",
  model: "predictive",
  date_range: {
    from: "2026-06-01",
    to: "2026-06-30",
  },
  group_by: ["channel"],
});

Response

json

{
  "rows": [
    { "channel": "Paid Search",
      "spend": 48210, "roas": 4.02 },
    { "channel": "Paid Social",
      "spend": 31450, "roas": 2.77 }
  ]
}

200 OK · 2.4 GB scanned · 2.4 DQU

Or embed the module

typescript

// server: mint a scoped embed token
const token = await ss.embedTokens.create({
  workspace: "acme-retail",
});

// client: render the white-label module
<MeasurementModule
  token={token}
  theme="dark"
/>

Or ask through MCP

text

> Why did ROAS drop for acme-retail
  last week?

⏺ segmentstream · get_report_table
⏺ segmentstream · get_conversions

Paid Social CPA rose 23% after the
June 12 creative swap. Search held.

API preview — final shapes may change before general availability. Every workspace ships with MCP access, so AI agents can query the engine directly.

Pay for what you process

A platform fee per plan, plus two meters. No per-seat pricing, no per-client surprises.

DPU

Data Processing Unit

Event ingestion, identity resolution and model refreshes — every unit of data the engine processes on your behalf.

DQU

Data Query Unit

Reports, API calls and AI-agent queries, metered by data scanned. One DQU is one gigabyte.

Each plan includes monthly DPU and DQU quotas — unit sizing and early-access pricing are shared with the waitlist first.

The engine behind measurement at

Join the waitlist

SegmentStream Cloud is rolling out to a small group of design partners. Tell us where to reach you.