How Relay works

One traceable loop, from page context to settled revenue.

Every page view runs the same nine steps under one correlation id — so any decision on the network can be replayed end to end. Four services own the loop; a handful of invariants keep it honest.

01Page context

The page offers a slot; Relay classifies its topic, entities and brand safety — cached by content fingerprint.

Try it in Match Lab →
02Hard eligibility

Rights, geo and suspension filter the catalogue before ranking ever runs — never after. Within a 5s bound.

03Ranking

What survives is scored: a deterministic baseline, a learned layer, then a business-constraints clamp that can only lower a score.

04Match or NO_MATCH

The best fit serves only if it clears the relevance floor. Below it, nothing is served — a bad fit is never better than the house slate.

05Ad decision

For the opportunity, the ad server runs an auction — targeting, brand safety, pacing, pricing model — or returns the house slate.

Try it in Ad Lab →
06Playback

A viewability-gated autoplay mounts real HLS: the pre-roll creative, then the matched video. Never a dead frame.

07Billable event

Revenue is recognised at the qualifying view — a validated impression or the view threshold, not ad start.

08Allocation

Gross splits at the agreement effective when the event occurred — each publisher and content owner on its own terms.

09Reconciliation

A period closes idempotently over the event ledger: re-closing returns the stored statement, never a double count.

See real traces →
The four services

Each owns one part of the loop.

syndication-platform

Organizations, effective-dated agreements, rights and kill switches, tenancy, publisher destinations and tag keys.

content-intelligence

Page/context classification, candidate retrieval, the ranking layers, the NO_MATCH floor, anonymous visitor profiles.

ad-server

CSAI direct and VAST ad decisions, targeting, pacing, frequency, pricing models, billable-event validation.

analytics-revenue

The idempotent event ledger, the funnel, event-time allocation, period reconciliation, and the correlation-id trace.

A multi-sided network

Four parties, one marketplace.

Content owners
Distribute a catalogue once; it reaches every eligible destination, matched to the page — and earn a fixed share.
Publishers
One tag installs contextual video across their pages; real fill and RPM, their own editorial control.
Advertisers
Contextual reach on brand-safe inventory, priced how they buy — CPM, CPC or CPV — paced to deliver.
Network operator
Admits partners, enforces rights and tenancy, and settles the money — the managed layer in the middle.
The guarantees

Invariants the network holds.

Hard eligibility before ranking

Rights and safety are enforced on the candidate set first. Ranking can reorder, never re-admit.

Allocation at the event-time agreement

A later amendment never rewrites an earlier event. The split is the terms in force when it happened.

Billing at the qualifying view

CPV is a validated view, not an ad start. The billable event is the settlement anchor.

Idempotent settlement

A period close is keyed on recon:{period}:{version}. Re-running is a no-op; no impression double-counts.

Tenancy, enforced server-side

Every read and write is scoped by organization on the backend. The client is never trusted for scope.

Deterministic by seed

The whole world is reproducible from one seed — the same inputs always produce the same decision.

2,179 · 85.4% · 25%
licensed assets · ad fill · your share, from the first event
Watch the live feedDrive a decision