Turn your first-party data into a revenue stream
Register brand partners, control exactly what data they receive, and let them self-serve their own integrations. Data monetisation built into your server-side infrastructure.
$55B+
RMN market size by 2025
Retail media is the fastest-growing ad channel globally. Brand workspaces let you participate by monetising the first-party data you already collect.
10,000+
Brand accounts per retailer
Large retailers work with thousands of brand partners. Brand workspaces scale to any number of registered brands without additional infrastructure.
6 actions
Field-level privacy controls
Remove, hash (SHA-256), mask, truncate, generalise, or allow — applied per field, per brand, per event type. Default policies: pass-all or deny-all.
Zero
Additional infrastructure costs
Brand workspaces run on the same pipeline, the same Kafka cluster, and the same delivery workers. No new infrastructure to deploy or manage.
How brand workspaces work
Shopper events flow through your existing pipeline. The data monetisation layer filters events by brand, applies privacy controls, and delivers to each brand's own integrations.
Brand registry & data controls
Register brands, define what data they can access, and enforce privacy at the field level. You control the data — brands consume it on your terms.
Brand Registry
Register brand partners with metadata, logo, contact details, and brand keys that match your product catalogue. Each brand gets a unique workspace scoped to their data.
Data Access Rules
Per-brand, per-event-type control over which events flow to each brand. A sports brand sees only their product events — never a competitor's data.
Field-Level Privacy
Six actions per field: remove, hash (SHA-256), mask, truncate, generalise, or allow. Set a default policy of pass-all or deny-all, then override per field.
PII Presets
One-click presets for common scenarios: GDPR Safe, Hash All PII, Remove Emails, Analytics Only. Apply a preset, then fine-tune individual fields.
Brands manage their own integrations
Each brand logs in with their own credentials and sees only their own workspace. They can configure integrations, view delivery status, and monitor event volume — without seeing any other brand's data or configuration.
- Brand-scoped JWT tokens — brands can only access their own workspace
- Full integration catalog: Facebook CAPI, GA4, BigQuery, webhooks, and more
- Standard blueprint install flow, scoped to the brand's allowed events
- Real-time delivery status and event monitoring within their workspace
- Zero engineering effort from your team — brands self-serve entirely
# brand-workspace-nike.yaml — Brand-scoped delivery
name: brand_nike_purchase
brand: nike
brand_key: brand_id
trigger:
event: track
conditions:
- field: event
operator: equals
value: Order Completed
- field: properties.brand
operator: equals
value: Nike
privacy:
default_policy: deny-all
fields:
- field: email
action: hash # SHA-256
- field: phone
action: remove
- field: ip_address
action: mask # 123.45.67.0
- field: name
action: remove
- field: order_id
action: allow
- field: product_id
action: allow
- field: revenue
action: allow
pipelines:
# Brand manages their own integrations
- name: nike_meta_capi
vendor: meta_conversions_api
event_name: Purchase
managed_by: brand # Brand self-service
- name: nike_bigquery
vendor: bigquery
dataset: nike_signals
managed_by: brandDelivery conditions work with brand workspaces
Global delivery conditions and per-event filters apply before brand-level filtering. Consent enforcement, event validation, and schema checks happen once at the Org Data Layer — then brand workspaces receive only the events they're entitled to, already cleaned and validated.
Global Filters
Org-level delivery conditions filter events before they reach any brand workspace. Consent checks, bot filtering, and event validation happen once.
Per-Event Rules
Each brand workspace defines which event types it receives. A brand only sees Purchase and Add to Cart — never Page View or internal events.
Layered Enforcement
Global filters, brand data access rules, field-level privacy, and per-integration delivery conditions all compose together. Defence in depth for data governance.
Usage tracking & monetisation
Every event delivered to a brand workspace is counted and tracked. Export usage data for billing, set rate limits, and monitor consumption per brand.
Per-Brand Event Counts
Real-time and historical event counts per brand, per event type. Know exactly how much data each brand consumes.
Monthly Usage Tracking
Aggregated monthly usage per brand with trend data. Set up tiered pricing based on event volume.
CSV Export for Billing
Export usage reports as CSV for your finance team. Per-brand, per-month breakdowns ready for invoicing.
Rate Limiting per Brand
Set per-brand rate limits to prevent any single brand from consuming disproportionate pipeline capacity.
Monetise your first-party data with brand workspaces
See how Datafly Signal lets you register brand partners, enforce field-level privacy, and let brands self-serve their own integrations — all on your existing infrastructure.