Audience & Data Activation

An audience segment needs a documented source before it can be treated as an asset.

We log the source of each proposed segment, whether it uses first-party, contracted third-party or contextual data, and attach the client's documented consent or contractual basis. A privacy-designated reviewer approves the intended use before activation. After the segment reaches the DSP, we check its match rate, available reach and whether the live setup still fits the approved scope and consent window. You end up with a data-use register prepared for direct review by a privacy-designated owner. Your DSP already has audiences running that nobody can trace back to a signed data-use agreement.

A data-use register tracing an activated segment back to its consent basis and source

Some of the 500+ brands we've worked with

See all references
  • GAP
  • Yandex
  • HangiKredi
  • Teyit.org
  • Amazon
  • BMW
  • Shell
  • Hyundai
  • PepsiCo
  • Red Bull
  • Decathlon
  • MediaMarkt
  • Bayer
  • Sanofi
  • EY
  • KPMG
  • GE
  • 3M
  • Domino’s
  • Lexus
  • Trendyol
  • Hepsiburada
  • Pegasus Airlines
  • LC Waikiki

How the work runs

Follow each segment from source to retirement

One register holds the source, approved use, match-rate check and retirement date for each segment. AI may trace declared sources and flag missing consent records. It cannot approve a data source or activate a segment.

How we hold ourselves to it

  • Every segment's data source gets logged before anyone uses it
  • Review documented consent and use-rights before a segment reaches a DSP
  • Match rate and reach get checked after activation
  • Segments run on a refresh-or-retire schedule

  1. Register the segment's data source

    Document whether a proposed segment uses first-party, contracted third-party, or contextual data before it is considered for activation. A data owner confirms the source before the segment moves forward.

    Source register entry naming the segment's data origin before it is considered for activation.

  2. Check documented consent and use restrictions

    Check the segment against the consent basis and any contractual use restrictions, and flag anything that doesn't clearly cover this specific activation. A privacy-designated reviewer signs off before activation.

    Consent and contractual check flagging anything that does not clearly cover this activation.

  3. Activate in the DSP with defined scope

    Build the segment into the DSP with only the scope, geography, and duration the consent basis actually supports. The media lead confirms the activated scope matches the approval.

    DSP activation limited to the scope, geography and duration the consent basis supports.

  4. Verify match rate and reach

    Check how much of the segment actually matched and activated, and whether the reachable audience is close enough to the intended one to be worth running. The media lead decides whether a low match rate needs a different approach.

    Match-rate and reach report comparing the reachable audience with the intended one.

  5. Monitor for drift and unauthorized reuse

    Check periodically that a segment hasn't been copied into a different campaign or use case outside its original approval. The data owner investigates any flagged reuse.

    Drift check confirming no segment was reused outside its original approval.

  6. Refresh or retire on schedule

    Refresh a segment's underlying data on schedule, or retire it entirely once its consent window or campaign use has ended. The data owner approves the refresh or confirms retirement.

    Refresh and retirement log entry for each segment reaching its review date.

What lands with your team

You can trace every audience back to its source

Open the register and you can see the data source and documented basis behind each targeting name.

  • Segment source register

    Every active segment, its underlying data source, and the consent or contractual basis for its use.

  • Activation and scope record

    What scope, geography, and duration each segment was actually activated with in the DSP.

  • Match-rate and reach report

    How much of each segment matched and activated, and how close the reachable audience is to the intended one.

  • Refresh and retirement log

    When each segment was last refreshed, when it's due for review, and the record of any segment retired.

Before the work starts

When this work is the right next step

Audience activation depends on the permissions behind the data. A DSP may accept a segment without telling you where its data came from or whether the proposed use fits the original consent. Delivery and conversion reports won't expose that gap. It usually appears when a legal or privacy reviewer asks to see the permission behind the targeting name.

A good fit when

  • Every audience name is live in the DSP, but your team cannot trace each segment back to its first-party, third-party, or contextual source.
  • First-party records sit beside modeled or contextual DSP segments, so the boundary between your data and the platform's data needs a written record.
  • Segments keep running past their campaign or consent window, because nobody owns a dated refresh-or-retire schedule.
  • Segments get renamed and reused across campaigns, and nobody can trace the current one back to its original consent basis.
  • A "custom audience" gets built from a data source nobody on the current team remembers agreeing to.
  • Match rates get reported but nobody checks whether the activated segment is actually who it's supposed to be.
  • Old segments keep running in a DSP long after the campaign or consent window they were built for has ended.

Better handled as other work when

  • A proposed data source has no clear consent trail, so a privacy or legal review must establish permission before any activation work begins.
  • Targeting stays contextual and simple, while every segment already carries a documented source, match rate, and retirement date in your register.
  • The work depends on a third-party data type this method cannot source or verify, so its source and permission need a separate privacy review.

People who own a single channel

Paid Search, Paid Social, CRO, and Programmatic each run under a named owner at Zeo. The consultants below are matched to the channel this page is about, so you can see who you'd actually work with.

Tools we use

Tools behind this work

  • LiveRamp

    resolves the segment's identity, then activates it into the DSP through a governed connection

  • The Trade Desk

    the DSP where the activated segment’s delivery and scale are verified

Trace the data behind every segment

Check the source before the next activation

Show us the segments already in use. We'll trace each one to its source and documented consent basis before it runs again.
Map audience data

The questions we hear most

Where does the audience data actually come from?

The source depends on the campaign. It may be first-party data held by the client, a contracted third-party source, or contextual signals that do not rely on user-level data. We register the source of every activated segment. The record also carries the documented consent or contractual basis for its intended use.

Can you use any data source a client wants to try?

If a source doesn't have a clear consent basis or contractual right for the intended use, we flag it and don't activate it until that's resolved.

What happens to a segment when a campaign ends?

It goes onto the refresh-or-retire schedule. That stops a segment from running indefinitely after its campaign or consent window has ended.

Can AI decide which data sources are permissible?

The permission call stays with a data owner or privacy reviewer. AI may trace a segment to its declared source and flag a missing consent record.