Audience Targeting and Data Strategy
Domain 3: Audience Targeting and Data Strategy
This domain tests how to select, onboard, and combine first-party, second-party, and third-party data without breaking identity, privacy, or scale. Expect questions on UID2, Data Marketplace segments, exclusions, and overlap.
Core rules and concepts
- First-party data (CRM, site pixel, app events) is usually the highest-quality seed; onboard it with consent and match keys such as hashed email, then activate through UID2 where supported.
- Third-party segments come from the Data Marketplace; check recency, country coverage, and whether the segment is modeled or deterministic.
- Apply exclusions before launch: existing purchasers, employees, and recent converters should not inflate prospecting.
- Audience size is not the same as reachable size; overlap, frequency, and identity match rates reduce usable scale.
Worked example
A retailer targets a lookalike from past purchasers plus an in-market apparel segment and excludes buyers from the last 30 days. If the third-party segment overlaps heavily with the first-party seed, incremental reach is small. Reasoning: measure unique reach and overlap; add a prospecting segment or broaden geo rather than raising bids.
Traps that cost marks
- Assuming all Data Marketplace segments are deterministic.
- Forgetting exclusions, so prospecting reports include recent buyers.
- Using a CRM list without consent or match-key hygiene.
- Confusing audience size with addressable, on-target reach.