Property Governance Tasks
Property governance uses a stateful model where all evaluation happens through property list management. Create lists with filters and brand references, then resolve them to get compliant properties.Discovery
Use the protocol-level
get_adcp_capabilities task to discover what features a governance agent can evaluate. See the governance section for details on the property_features array.
Property List Management
See Property List Management for complete CRUD documentation.
Validation
See validate_property_delivery for post-campaign compliance validation.
Task Selection Guide
Creating a Property List
Usecreate_property_list with filters and brand reference:
countries_all restricts to properties with data in ALL listed countries, channels_any restricts to properties supporting ANY listed channel. Omitting a filter means no restriction on that dimension.
Base properties: An array of property sources to evaluate. Each entry is a discriminated union with selection_type:
publisher_tags:{ "selection_type": "publisher_tags", "publisher_domain": "...", "tags": [...] }publisher_ids:{ "selection_type": "publisher_ids", "publisher_domain": "...", "property_ids": [...] }identifiers:{ "selection_type": "identifiers", "identifiers": [...] }- Omitted: Query the agent’s entire property database
countries_all: Property must have feature data for ALL listed countrieschannels_any: Property must support ANY of the listed channelsfeature_requirements: Property must pass ALL requirements (AND)
countries_all, channels_any) plus feature_requirements which reference features the agent provides (discovered via get_adcp_capabilities). For quantitative features, use min_value/max_value. For binary or categorical features, use allowed_values.
Getting Resolved Properties
Useget_property_list to retrieve the list with resolved identifiers:
auth_token for sharing with sellers is returned at creation time (from create_property_list). Store it securely - it’s only returned once.