One audience stream.
Every media service in context.
One stream serves many business services. Process impressions, audience segments and content propensity scores together, and connect permitted context to your ad-serving, editorial and subscription systems as events arrive.
For publishers, subscription teams and audience operations, together with editorial, IT and privacy owners.
Audience & Subscriber Context
One network. Clear agreements for each participant.
Subscription status, newsletter choices and content interests often live in separate systems. Readers repeat their preferences while audience teams reconcile exports and exceptions. Streams can carry these changes into the services that need them under one approved processing definition.
Reader or subscriber
Chooses topics and channels, changes preferences and accesses subscribed content.
Editorial team
Defines content categories and editorial conditions for recommendations.
Subscription and customer service
Maintain access entitlements and resolve account or payment exceptions.
Website, app and newsletter services
Use the permitted context for the current interaction without each maintaining a separate interpretation of the rules.
Processes to connect
Bring processing to the data your services already use.
Keep the relevant personal context, purpose, rules and destinations in an approved definition. Connected operations use that definition as new events arrive.
Subscription change to access
Apply an accepted entitlement update to connected channels and route conflicting or missing information for review.
Reader choice to newsletter selection
Use declared topics and current channel permissions before preparing the next delivery.
Interaction to audience insight
Process permitted events into useful audience measures, applying field restrictions and retention rules at the configured collection and processing points.
Connected media operations
One stream serves many business services.
Run impression processing, audience segmentation and content propensity scoring in the same stream operation. Use its APIs and configured outputs to serve advertising, editorial, analytics and subscription services from current context, with the rules for each purpose applied before delivery.
Impression management
Define which reported impressions count, validate event fields and identifiers, handle duplicates and update the agreed counters. Keep served, rendered and viewable events distinct according to the measurement signals supplied by your sources.
Audience segmentation
Update membership as permitted content interactions, declared interests and subscription context change. Define membership conditions and expiry in the stream rather than repeatedly exporting audience lists between tools.
Content propensity scoring
Calculate an agreed score from permitted signals such as reading frequency, topic interest and recency. Make the score, its version and its meaning explicit so each service knows how it may use the result.
Real-time ad-serving context
Deliver the allowed segment, score or contextual signal through the stream API or a configured integration with your ad-serving system. Agree the delivery latency and freshness needed for the advertising decision.
Editorial and subscription services
Use purpose-appropriate outputs for content selection, subscription journeys and audience analysis. Each recipient receives the information authorised for its role and task.
One operation, multiple outputs
Reuse the accepted event and approved processing definitions across these services. Separate SaaS tools for the covered processing can be retired once their required behaviour and integrations are validated.
From one interaction to several permitted outcomes.
A permitted article interaction updates a topic segment and its engagement score. The next configured ad request can use the allowed context, while a separate output updates audience reporting and a subscription service receives its own permitted signal. An impression acknowledgement returns from the serving system to update the relevant counters. One stream supports these services without making every recipient a copy of the reader profile.
Rule-based scores are reproducible for the same input, context, time reference and approved scoring version. Where a predictive model is used, retain the model version and the output used in the decision; deterministic execution does not make a prediction certain. Define behaviour for stale context, late events and unavailable ad-serving endpoints, and verify enforcement when a permission changes.
Example operation
See how an agreement becomes an outcome.
The same input, relevant context and approved rule version produce the same rule-based result. Changed facts or agreements can change the next result, with the applied version recorded.
1. trigger
A subscriber turns off personalised newsletters while retaining a paid subscription.
2. context
Keep subscription entitlement, newsletter permission and topic preferences as distinct facts with their effective times.
3. rule
The newsletter operation checks the current permission before dispatch. Subscription access follows its own approved entitlement rule.
4. outcome
Exclude the reader from the next personalised newsletter operation while preserving valid content access. A queued message must pass the configured check before sending.
5. evidence
Record the preference event, purpose, rule version and suppressed action. Preserve only the evidence required by the agreed retention rules.
Validate late or duplicate events, unavailable destinations and rule changes before activation. Historical evidence explains the earlier decision; a new action must meet the conditions that apply when it is executed.
Rules in context · EU and Netherlands
Turn applicable requirements into explicit processing conditions.
The responsible organisation determines the applicable obligations and approves their translation into executable rules. These sources guide that work; they are not a certification of the solution.
Purpose-specific processing
Assess the basis for subscription fulfilment, audience measurement and marketing separately. Record a withdrawal where consent is used and reflect it in subsequent processing for that purpose.
EDPB: lawful processingTracking at collection
Assess cookie and tracking requirements before collecting events. An approved downstream rule does not remedy information collected without the required permission.
Dutch DPA: tracking cookiesPlatform duties depend on the service
Assess whether a service qualifies as an online platform and which DSA duties apply, including relevant recommender and advertising transparency rules. Publishing editorial content alone does not make every platform duty applicable.
European Commission: DSA questions and answersSource review: 20 September 2026. Confirm the applicable requirements for your service and jurisdiction when defining the operation.
Business value
Measure the work you can remove.
Build the business case from the integrations, manual work and evidence preparation this process actually replaces. Include platform fees, implementation, validation and remaining operating costs.
Preference reconciliation
Reduce repeated exports and list corrections. Track staff time and preference mismatches across channels.
Campaign and access maintenance
Reuse approved rules instead of duplicating them in each tool. Track change effort and access-related support cases.
Processing review
Keep the applied purpose and rule with the outcome. Measure the work needed to explain a selected audience or suppressed message.
Start small, then expand
Prove the value in one bounded process.
Start with one publication, one interaction source, one defined audience segment or content score and one ad-serving connection. Agree the impression definitions, permitted fields and acceptable context age. Test the same stream with a second output for audience reporting, including a permission change before delivery.
Keep editorial responsibility with the publisher. Confirm each channel's API, measurement signals and enforcement before dispatch. Your ad-serving system remains responsible for the advertising delivery it executes. Validate scoring quality and business impact; higher yield, conversion and retention are outcomes to measure.
Define your first processAgree the baseline and acceptance criteria
- Time from an accepted preference change to enforcement
- Time from accepted event to updated segment or score at the destination
- Duplicate impression handling and stale-context fallbacks
- Replaced SaaS costs, integration hours and audience reconciliation work
- Time to explain a sampled segment, score or delivery decision
Compare a representative period before and after. Expand only after the responsible owners accept the processing behaviour, evidence and measured value.