Skip to main content

​
Overview

Add one closed age range to a get_products brief when a campaign must reach a specific adult audience. For example:
The storefront copies the two numbers from the brief. It does not ask a model to choose an age range, translate a generation label such as “Gen Z” into ages, or widen the request to fit a platform. This applies during product discovery and media-buy creation. It does not change targeting on an existing media buy. In chat, ask for ages 21-35; your agent uses this path automatically and does not guess when the platform cannot represent the range. No setup change is required for an existing brief that already contains one exact supported range.

​
Platform support

Each storefront must prove that it can execute the requested range exactly. ages 21-35 therefore works on Meta and Spotify. It returns no product from a bucket-only or unsupported adapter because approximating the request would change the audience.

​
Requests that need clarification

Product discovery returns no matching product when the age request cannot be executed without guessing or broadening. Rewrite the brief as one explicit, closed, supported adult range when it contains:
  • An open endpoint, such as ages 21+, under 35, or up to 35.
  • More than one or a disjoint range, such as ages 21-24 or 35-44.
  • An exclusion, such as exclude people ages 21-35.
  • A lower bound below 18.
  • Conflicting or ambiguous bounds.
  • A descriptive label without numbers, such as young adults or Gen Z.
This fail-closed response is expected. It prevents a storefront or model from silently choosing a different audience.

​
Unknown ages on Meta

Meta can deliver to people whose age is unknown. A constrained-age request excludes them unless the brief explicitly says to include them:
You can also state that they must be excluded. The choice is stored with the product, written to the Meta ad set, and checked on readback. Other platforms currently reject a request to include people whose age is unknown.

​
Read the applied targeting

A returned product with verified age targeting includes the applied range at:
Use the returned product for media-buy creation. The storefront checks the stored product declaration again before publishing it or writing provider state. On Meta, requested and provider controls also show whether unknown ages were included.
Age is currently carried by the selected product. It is not a targeting_overlay field, and adding age to an overlay does not activate this behavior.

​
Seller impact

Sellers using a built-in adapter do not need a new configuration field. A custom or upstream sales agent must return the exact ext.scope3_product_targeting.demographics.age declaration or its product is filtered from that brief. Products with a different range, an undeclared range, or a provider mapping that would broaden the request are not offered.