Overview
A buyer property list is a buyer-owned include or exclude set of domains, apps, or CTV identifiers. On the seller side, the most important case is an include list attached to a campaign or media-buy package: the buyer is asking the seller to run on that set of properties if the seller can honor it. The property list reaches the seller as an ADCPPropertyListReference. Its
placement depends on the request:
For initial discovery, the buyer’s
get_products request can carry the
reference at the top level:
What the seller’s agent does
When your sales agent receives a property-list reference, it resolves the list from the buyer’s agent URL:cache_valid_until, then re-fetch
if the buy or update still needs it.
Large lists can be paginated. Pass max_results and follow
pagination.cursor while pagination.has_more is true. Cache each resolved
page until cache_valid_until.
What it means operationally
Today, Interchange forwards the property-list reference and provides the resolution endpoint. The seller decides how to honor it. Common seller-side outcomes:
Do not treat a buyer property list as automatic ad-server enforcement. If the
seller has not configured a way to execute that subset, the honest answer is
that the storefront can see the buyer’s requested properties but must decide
seller-side whether it can run against them.
How this relates to coverage
Coverage and buyer property lists answer different questions.
For network sellers,
publisher_properties usually comes from
adagents.json authorized coverage. A buyer property list is the buyer’s
requested subset inside or across seller coverage.
Related
Property lists
Buyer-side list creation, validation, and resolution.
Publisher properties and coverage
How buyers see the publisher domains a product covers.
Custom targeting and properties
How seller-managed GAM key-values relate to site lists.
Ad-server signal components
Browse GAM targeting and create signal components.