TL;DR
- Meta for Developers (Graham Mahon) announced on Monday 19 October 2026 that Marketing API partners can set an age range and gender for each creative in one ad set.
- The ad set opts in with creative_audience_pairing set to 1 inside targeting_automation; each ad, or each image or video in a multi-media ad, gets a persona with age_min, age_max and genders.
- While pairing is on, Meta's API reference requires the ad set minimum age to be 18 to 25, the maximum age 65, and all genders; single-gender ad sets return error code 100.
- The reference says pairing cannot be combined with Advantage+ audience or with age and gender suggestions.
- Meta published no performance data and did not say whether the toggle comes to Ads Manager or which markets, objectives and placements qualify.
Meta launched a Marketing API option on Monday 19 October 2026 that lets an advertiser give each ad creative its own age range and gender inside a single ad set. Meta announced it in a short post on the Meta for Developers blog titled "Choose an Audience for Each Ad Creative", written by Graham Mahon, and said Marketing API partners can use it from that day. The API reference behind the post, titled "Creative audience pairing", sets tight rules: while the option is on, the ad set itself has to stay open to all genders, with a minimum age between 18 and 25 and a maximum age of 65, and it cannot be combined with Advantage+ audience. Meta published no performance data and did not say whether the toggle is coming to Ads Manager.
This article sets out what Meta's post says, what the linked API reference adds, the limits that decide who can actually use it, and the questions neither document answers. RA has not covered this feature before; a title search of RA's news archive returned no earlier post on per-creative audiences.
What Meta announced on 19 October 2026
The post on the Meta for Developers blog is brief. Its opening sentence reads: "Today, Monday, October 19, we launched a new feature that lets advertisers choose a specific audience for each ad creative." Meta then describes the setting as a toggle: "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."
Meta gives two examples. In the first, a financial services advertiser "might decide retirement-planning videos are best suited for people aged" 50 to 65, and that "savings account videos are best suited for all ages." In the second, a fashion retailer "might decide images of women's sweaters are best suited for women, and images of men's sweaters are best suited for men."
The rest of the post is addressed to developers. Under the heading "What does this mean for Marketing API partners?", Meta writes: "Starting today, Marketing API partners will see this option available to them." Under the next heading, Meta encourages partners "to review and test this feature starting today." The full post is on the Meta for Developers blog.
The post lists eight affected Graph API endpoints, covering creation, update and read calls at three levels:
- Ad sets: POST /act_{ad-account-id}/adsets, POST /{adset-id} and GET /{adset-id}
- Ads: POST /act_{ad-account-id}/ads, POST /{ad-id} and GET /{ad-id}
- Ad creatives: POST /act_{ad-account-id}/adcreatives and GET /{adcreative-id}
Because read and update calls are on the list, a tool that only syncs existing campaigns, and does not create new ones, also has new fields to handle.
How creative audience pairing works in the API reference
The blog post links to a Marketing API reference page titled "Creative audience pairing". When RA read that page on 20 October 2026 it carried the label "Updated: Sep 4, 2026", so the documentation existed before the public announcement. The page describes the mechanics the blog post leaves out.
The reference says the feature "lets you set age and gender on the ad creative instead of the ad set." It takes two steps.
First, the ad set opts in. The advertiser sets a parameter called creative_audience_pairing to 1 inside targeting_automation in the ad set's targeting spec. Setting it to 0 opts out, and leaving it out keeps the feature off. The parameter accepts only 0 or 1.
Second, each ad gets a persona. The reference is explicit that enabling the ad set flag on its own does nothing, "because without a persona there is nothing to pair." The persona is an object named creative_audience_pairing_persona with three optional fields:
- age_min: 18 or older, and never lower than the ad set's own age_min. If left out when the persona is created, it takes the ad set's effective minimum age. The Graph API returns error code 100 if it is set lower than the ad set's minimum.
- age_max: up to 65. If left out on creation, it is set to 65.
- genders: an array where 1 means male and 2 means female, with at most two values. If left out on creation, the persona targets all genders.
When a persona is updated, any field left out keeps its current value.
Where the persona sits depends on the ad. For a single-media ad, it is a top-level field on the ad, next to the creative. For a multi-media ad, it is set on each image or video inside media_sourcing_spec. The reference adds that when personas are set per media asset, "only those per-asset personas apply" and any ad-level persona on the same ad is not used. That per-asset path is how one ad can carry, for example, a retirement video for older viewers and a savings video for everyone. The example requests on the page call Graph API v26.0.
The limits: the ad set has to stay broad
The "Limitations" section of the reference is where most of the practical constraints sit. According to Meta's reference page:
- Creative audience pairing cannot be combined with Advantage+ audience.
- It cannot be combined with age and gender suggestions, which are switched on by setting age or gender to 1 within individual_setting.
- While pairing is enabled, the ad set's age_min can only be between 18 and 25.
- The ad set's age_max must be 65.
- The ad set must target all genders. Leaving genders out, or passing both values [1,2], is allowed. Targeting a single gender, [1] or [2], is not.
The Graph API returns error code 100 when an ad set breaks any of these rules.
Put together, the design is a wide ad set with narrower creatives inside it. An advertiser cannot build an ad set aimed only at women aged 30 to 45 and then narrow it again per creative. The ad set has to stay open, and the personas pick segments out of it. Meta's own fashion example only works if the ad set covering both sweater images is open to all genders.
PPC Land, which covered the launch on 19 October 2026, read the same reference the same way and noted the trade-off with Meta's automation: the new demographic control only works when the fully automated Advantage+ audience setting is off.
Key facts at a glance
The table below lines up the main facts from Meta's blog post and its API reference, as read on 20 October 2026.
| Item | What Meta's documents say |
|---|---|
| Launch date | Monday 19 October 2026, for Marketing API partners |
| Ad set switch | creative_audience_pairing set to 1 inside targeting_automation |
| Per-creative persona | age_min (18+), age_max (up to 65), genders (1 male, 2 female) |
| Ad set age rules while on | Minimum age 18 to 25 only; maximum age must be 65 |
| Ad set gender rule while on | All genders; single-gender ad sets are rejected |
| Not compatible with | Advantage+ audience, and age and gender suggestions |
| Endpoints affected | Eight: three ad set, three ad and two ad creative calls |
What Meta did not say
Several points that matter for planning are missing from both the blog post and the reference page. They are listed here so nobody fills the gaps with guesses.
- No performance data. Meta's post contains no test results, no lift figures and no rollout percentages.
- No word on Ads Manager. The post addresses Marketing API partners only and does not say whether the toggle will appear in Ads Manager.
- No list of eligible markets, objectives or placements. The example request in the reference uses the United States as a geo target, but that is a code sample, not a statement of availability.
- No explanation of delivery behaviour. Meta's wording is that the advertiser picks the audience each piece of media is "best suited for". Neither document says whether a creative will never be shown outside its persona or whether the persona is one signal among others in delivery.
- No word on reporting. Neither document mentions breakdowns that show results per persona.
- No word on special ad categories. PPC Land pointed out that Meta's first example is financial services, while ads in special ad categories such as financial products run with fixed age and gender settings. Meta's post does not say whether personas are available to campaigns that have declared such a category.
- No statement on whether an age_max of 65 also covers people older than 65.
Why the feature matters for account structure
The following is RA's analysis, not something Meta said. Until now, an advertiser who wanted one message for older viewers and another for younger viewers usually split them into separate ad sets, each with its own age targeting and its own budget. Creative audience pairing offers a second option: keep both creatives in one ad set, with one budget, and attach the audience to the creative.
PPC Land's 19 October report places the launch against Meta's recent direction. It notes that Meta removed detailed targeting exclusions for new ad sets on 21 January 2025, and that Meta added a creative breakdown in Ads Manager on 11 July 2025 for flexible format ads that can hold up to 10 images and videos. A broad ad set with many creatives leaves Meta's systems to work out who should see which creative. Per-creative personas let the advertiser state that view directly, at the price of turning Advantage+ audience off for that ad set.
Whether consolidation helps or hurts results is an open question. Meta has published no data on it, and the honest answer for any account is that it has to be tested against the existing structure rather than assumed.
What this means for Thai marketers
Meta's post and reference say nothing about Thailand or any other market, so availability for Thai ad accounts is not confirmed by the source. What follows is practical analysis for advertisers in Thailand who might want to use it.
The use case fits advertisers who already split ad sets by age or gender because their creatives speak to different groups. In Thailand this could include banks and insurers with products aimed at different life stages, fashion and beauty brands with separate lines for women and men, and education or property brands that run separate messages for younger and older buyers. For them, the feature is a way to test one consolidated ad set against the current split.
Four checks are worth making before anyone plans around it:
- Ask the tool provider. The launch is for Marketing API partners. A team that buys Meta ads through a third-party platform or an in-house tool needs that tool to support the new targeting_automation flag and the persona object. A team that works only in Ads Manager has no confirmed access, because Meta has not said the toggle is coming there.
- Check age rules. While pairing is on, the ad set minimum age can be no higher than 25. A campaign that must keep its whole ad set above 25 cannot switch it on, and that includes any brand whose own policy or legal advice requires a higher age floor for the whole audience.
- Check the Advantage+ setting. Ad sets currently running Advantage+ audience, or age and gender suggestions, would have to give those up to use pairing.
- Check special ad category status. Banks and lenders running ads declared under a special ad category should not assume personas work for those campaigns until Meta says so.
For teams planning Facebook ads structure in the fourth quarter, the sensible step is a controlled test on one product line rather than a rebuild of the account. Advertisers who run campaigns across several platforms can compare it with how social ads on other networks handle creative-level targeting, and retailers with menswear and womenswear catalogues may want to fold it into their wider ecommerce marketing testing plan.
Frequently asked questions
What is Meta's "Choose an audience for each ad creative" feature?
It is a Marketing API option, launched by Meta on 19 October 2026, that lets an advertiser set an age range and gender for each creative inside one ad set. The ad set opts in with creative_audience_pairing set to 1, and each ad or media asset gets a persona with age_min, age_max and genders.
Can I use per-creative audiences in Ads Manager?
Meta has not said. The 19 October post states that Marketing API partners can use it from that day and says nothing about Ads Manager.
Is the feature available in Thailand?
Meta's documents do not say which markets are eligible. Neither the blog post nor the API reference mentions Thailand or any country restriction, so Thai advertisers should check with their API tool provider or test it in their own account.
Can I use it with Advantage+ audience?
No. Meta's API reference states that creative audience pairing cannot be combined with Advantage+ audience or with age and gender suggestions, and the Graph API returns error code 100 if an ad set tries to.
Does the persona stop a creative from showing to other age groups?
Meta has not said. Its post describes the persona as the audience each piece of media is "best suited for", and neither the post nor the reference explains whether that is a hard limit or a signal used in delivery.
Bottom line
Meta's 19 October 2026 launch moves age and gender choices from the ad set down to the creative for advertisers who build through the Marketing API. The catch is that the ad set around those creatives must stay open to all genders and to ages from 25 or younger up to 65, with Advantage+ audience switched off. Meta has offered no data on results, so the first job for any advertiser interested in it is a clean test against their current structure. RA's paid social team can help scope that test if needed.







