The LiveRamp Segment You Activate Through Your DSP Is Not the Same Segment Your Clean Room Measured
Audience segments measured inside a clean room and then exported for DSP activation resolve through different identity states, so the population you measured is not the population you buy.

When media buyers run audience analysis inside a data clean room and then push that same segment into a DSP for activation, the handoff looks seamless. The file moves, the DSP accepts it, and delivery begins. What does not move cleanly is identity resolution. The population your clean room counted and the population your DSP reaches are resolved through different systems at different moments, and those two things are almost never the same group of people.
Understanding why this happens requires a short look at how each environment handles identity.
How clean rooms resolve identity
A clean room counts audiences by joining your first-party data to a partner's data using a shared identity key, often a hashed email or a proprietary people-based identifier. That join happens inside the clean room's controlled environment at a specific moment in time, against a specific version of whatever graph or identity table the clean room operator maintains.
The count you see in your clean room report reflects that join. It tells you how many records overlapped under those conditions. It does not guarantee that those exact records are findable, reachable, or resolvable to the same identifiers your DSP uses when it goes to buy impressions.
How DSPs resolve identity at bid time
Your DSP does not receive a list of people. It receives a list of identifiers, typically cookie IDs, device IDs, or RampIDs, depending on your activation path. When your DSP bids on an impression, it checks whether the device or identifier on that impression matches something in the segment it was given.
That matching step uses the DSP's own identity logic, or the logic of the identity partner whose IDs were used to express the segment. If your clean room measured the audience in one identifier space and your DSP is bidding in a different identifier space, there is a translation step somewhere in between. That translation introduces population drift.
The size, composition, and demographic profile of the group you reach can shift meaningfully depending on how well those two identifier spaces correspond to each other.
Where the gap appears in practice
Consider a hypothetical example. A brand runs a clean room analysis to identify high-value existing customers who also visit a retail partner's properties. The clean room returns a match count and the brand exports that segment for activation. The export is expressed in hashed email format, which is then onboarded through a people-based identity graph to generate device-level IDs for DSP delivery.
Each step in that chain introduces a resolution question. How many of the clean room matches have a hashed email that the onboarding graph can find? Of those, how many resolve to an active device ID? Of those, how many are actually reachable in the inventory the DSP accesses?
By the time delivery begins, the active audience may represent a fraction of the clean room match count, and that fraction is not random. Customers who are harder to resolve through the onboarding graph tend to be systematically different from those who resolve easily. They may be older, less digitally active, concentrated in certain regions, or heavier users of environments that limit identifier availability. The audience that does get reached may skew toward a different profile than the audience you analyzed.
Why buyers often miss this
The gap is easy to miss because the reporting at each stage looks complete. The clean room shows a match count. The onboarding platform shows a reachability percentage. The DSP shows delivery numbers. None of those reports is wrong on its own terms. The problem is that they are each describing a different population, and the buyer is expected to understand that the numbers should not be compared directly.
Most campaign workflows do not include a step that audits whether the delivered population resembles the measured population. The clean room analysis is treated as proof of audience quality, and delivery is treated as proof that the audience was reached. The connection between the two is assumed rather than verified.
What a more durable workflow looks like
A few structural adjustments can reduce the gap without requiring entirely new infrastructure.
First, when possible, run your clean room analysis using the same identifier type your activation path will use. If your DSP activates on RampIDs, and your clean room can join on RampIDs, doing so reduces the translation step between measurement and delivery. The population you count is expressed in the same language your DSP speaks.
Second, treat the onboarding reachability report as a population filter, not just a scale report. When your onboarding partner returns a reachability number, ask for a breakdown by customer segment if that is available, or at minimum compare the reachable population back to your clean room criteria. If a large share of the customers who met your clean room criteria are not reachable, that is signal about which part of your intended audience you are actually funding.
Third, run a post-delivery identity audit on a sample basis if your measurement setup allows it. The goal is to check whether the identifiers your DSP reached can be traced back to the records your clean room analyzed. This does not have to be comprehensive to be useful. Even a rough comparison can reveal whether delivery drifted toward a structurally different group.
Finally, when you set performance expectations from a clean room analysis, apply a conservative adjustment to account for resolution loss between measurement and delivery. How large that adjustment should be depends on your specific activation path, but assuming the clean room population and the delivered population are equivalent is almost always an overstatement.
The durable principle underneath the mechanics
Clean rooms and DSPs are useful tools. The tension described here is not a reason to avoid either one. It is a reason to treat the handoff between them as a measurement event rather than an administrative step.
Every identity translation in your activation path is a moment where the population can shift. Buyers who account for that structurally, by choosing compatible identifier types, auditing reachability by segment, and building conservative expectations into planning, will get more accurate reads on what their campaigns actually accomplished and who their campaigns actually reached.