Repository navigation
get_products: required_match_keys filter for cross-publisher cap planning #8450
Description
Follow-up to #8375 / #8446, open question 4.
A buyer planning a cross-publisher cap needs to find products whose identity_match keys are compatible with its own Identity Match provider at a given scope. Today the only way is to walk the whole catalog and read Product.identity.match_keys.
Proposal: a get_products filter required_match_keys: [{ uid_type, vendor?, scope, use }]. A product matches when it has a key with that use that is compatible at scope, under the compatibility rule in the media-buy spec. This parallels required_overlay_support and audience_activation_methods.
Deferred until WG review of #8375 settles the compatibility rule, because the filter's matching logic is that rule.
Activity
bokelley commentedon Oct 31, 2026
Not decided for 3.3, so per the WG rule ('anything not decided moves to 3.4') this moves to 3.4. Objections by Fri 2026-11-06.
No PR exists, and the #8375 consent round (#8375 (comment)) explicitly leaves this filter out of the 3.3 match-keys slice (#8446). This depends on that round passing. The milestone stays 3.3.0 for now; it will be moved after Nov 6.