Age and gender can now be set on each creative inside one ad set — this is not the v27 default-on device expansion
On 19 October 2026 Meta launched a Marketing API feature that lets advertisers set a specific audience on each ad creative: several ads can sit in one ad set, and each piece of media can have its own age range and gender. That is a creative-level cut, not the v27 default that turns on device expansion or Product showcase when you upgrade the API version. The official post names only age range and gender — not interests, locations, or custom audiences — and it does not publish field names in the post itself.
What launched on 19 October 2026
Meta for Developers published "Choose an Audience for Each Ad Creative" on 19 October 2026. The post says the feature launched that day, and describes it this way: "Choose an audience for each ad creative when toggled on allows you to create several ads within one ad set and select the age range and gender each media is best suited for." Two examples in the post: "Financial services might decide retirement-planning videos are best suited for people aged 50–65, and savings account videos are best suited for all ages." And: "Fashion retailers might decide images of women's sweaters are best suited for women, and images of men's sweaters are best suited for men." Those sentences are official examples, not a compliance rule or a performance promise.
Endpoints the post names; field names it does not
The official post lists these Marketing API endpoints and tells partners to see the API reference: POST /act_{ad-account-id}/adsets, POST /{adset-id}, GET /{adset-id}, POST /act_{ad-account-id}/ads, POST /{ad-id}, GET /{ad-id}, POST /act_{ad-account-id}/adcreatives, GET /{adcreative-id}. It also says: "Starting today, Marketing API partners will see this option available to them." The post encourages partners to review and test the feature. The official post does not itself publish field names.
Field names on the live API reference
The blog links to the Marketing API document "Creative audience pairing." A curl/8.14.1 fetch of that page on 2026-11-10 20:44 Asia/Singapore returned HTTP 200. The field names below come from that reference, not from the 19 October post; re-check the live reference before relying on them. The page says creative audience pairing "lets you set age and gender on the ad creative instead of the ad set." To opt in, set the creative_audience_pairing parameter within targeting_automation to 1; to opt out, set it to 0; "If you omit the creative_audience_pairing parameter, creative audience pairing remains off." The parameter "accepts only 0 or 1." The same page says: "Creative audience pairing takes two steps. Enable it on the ad set, then set a persona. Enabling it on its own has no effect, because without a persona there is nothing to pair." A single-media ad carries one persona on the ad as the top-level field creative_audience_pairing_persona. A multi-media ad carries one persona per media asset in media_sourcing_spec; when those per-asset personas are set, "any ad-level persona on the same ad is not used." Persona fields on that page are age_min (must be 18 or older and cannot be lower than the ad set's age_min), age_max (up to 65), and genders (1 for male and 2 for female; at most two values).
Official limits on the same reference — and a silence
The reference says you cannot combine creative audience pairing with Advantage+ audience, or with age and gender suggestions, which set age or gender to 1 within individual_setting. "The Graph API returns error code 100 when either conflict occurs." When pairing is enabled, the ad set's age_min may only be between 18 and 25, age_max must be 65, and the ad set must leave genders out or target all genders; targeting a single gender is not allowed, while passing both ([1,2]) "counts as all genders and is allowed." Error code 100 also applies if the ad set does not meet those requirements, or if a persona's age_min is lower than the ad set's. The official post and this reference do not discuss Special Ad Categories, and they do not say that per-creative age or gender loosens housing, employment, credit, or social-issues rules. Meta's Marketing API Special Ad Categories document (HTTP 200 on the same day) also does not mention creative audience pairing or personas. The official pages are silent on that interaction, so this article stops there and does not invent one.
What to check
If you currently split ad sets only so that different creatives can use different age or gender cuts, inventory those ad sets. Review and test the new option on the Marketing API endpoints listed in the official post, and confirm whether your tool writes the official creative_audience_pairing parameter and personas described in the API reference. Check the ad set's age and gender settings against the reference limits before turning the option on. This option is not a default that turns on when you upgrade the API version.
This is not the v27 defaults article
The live article Meta Marketing API v27.0: two defaults that switch on unless your tool opts out is about defaults that flip with the API version (device expansion and Product showcase), which is a different clock from this 19 October creative-level age and gender control.
This article summarises Meta for Developers pages. It is not official Meta guidance, and it is not legal advice. Follow the live blog post and API reference.
Sources
- Meta for Developers, "Choose an Audience for Each Ad Creative" (19 October 2026) (https://developers.facebook.com/blog/post/2026/10/19/choose-an-audience-for-each-ad-creative/)
- Marketing API, "Creative audience pairing" (https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/reference/targeting-expansion/creative-audience-pairing)
- Multi-media ads, on per-asset personas (https://developers.facebook.com/documentation/ads-commerce/marketing-api/ad-creative/multi-media-ads)
- Special Ad Categories (https://developers.facebook.com/documentation/ads-commerce/marketing-api/audiences/special-ad-category). Live curl/8.14.1 fetches on 2026-11-10 20:43–20:49 Asia/Singapore returned HTTP 200 for all four; a browser User-Agent received HTTP 400 on the same URLs.