Aggregation
Combining data to obscure individuals
- Term
- Aggregation
- Field
- Audience & Privacy
- Category
- Audience & Privacy
The short definition
Combining data to obscure individuals
Aggregation sits in Audience & Privacy; it is an audience or privacy concept. Define it once and the reporting holds together.
How it operates
Think of Aggregation as context-bound. A small shop reads it simply; an enterprise reads it with more nuance. That is normal -- Aggregation is shaped by audience and channel mix. Read Aggregation without care and the plan wobbles; be precise and the read holds.
The working rule is plain. Agree what Aggregation covers first, then act on it. Skip that order and Aggregation loses its shared meaning, and two teams end up measuring two different things. One idea, plainly put.
When teams use it
Use Aggregation when it changes an outcome. For audience & privacy teams, that tends to be three recurring moments. With no choice live, Aggregation is good to know, not to chase.
- Setting budget. Aggregation signals which line earns the marginal spend.
- Choosing a metric. Aggregation reveals if the metric measures real impact.
- Comparing options. Aggregation adjusts a compare so the gap is honest.
An example with real numbers
Take Nike. During a clean-room measurement setup, the team made Aggregation the deciding input, not an afterthought. They set a baseline first, agreed one definition of Aggregation, and only then read the result: cross-channel reach stayed within 5% of truth. The number matters less than the order.
| Stage | The step taken | Why it mattered |
|---|---|---|
| Baseline | Took a before reading on Aggregation. | Something concrete to compare to. |
| Define | Fixed one meaning of Aggregation for the test. | Two people, one meaning. |
| Act | A clean-room measurement setup — one variable. | Cause and effect, isolated. |
| Result | Cross-channel reach stayed within 5% of truth | An outcome you can trust. |
Figures for Aggregation here are illustrative and marked RGM analysis. Copy the method, not the exact numbers.
Common mistakes
- No segments. Treating Aggregation as one number for all. Break it out before you trust it.
- No context. Reporting Aggregation with no baseline. A bare number cannot be judged.
- Wrong target. Treating Aggregation as the goal. The goal is the outcome it predicts.
- Bad compares. Benchmarking Aggregation with no adjustment. Account for the model differences first.
Frequently asked questions
What does Aggregation mean?
Why does Aggregation matter?
Where does Aggregation get used?
Where do teams slip up on Aggregation?
- What does Aggregation mean?
- Combining data to obscure individuals Settle what Aggregation covers first; the strategy follows from there.
- Why does Aggregation matter?
- Aggregation shows up in budget reviews and channel reporting. Use it loosely and teams pull apart; use it precisely and the numbers line up.
- Where does Aggregation get used?
- Teams put Aggregation to work on a spend split, a metric, or a head-to-head call. See the Nike walk-through above.