Meta today switched on a Marketing API option that lets advertisers attach a separate age range and gender to each creative inside a single ad set, according to a post on the Meta for Developers blog by Graham Mahon. The feature, called "Choose an audience for each ad creative," moves a targeting decision that has lived at ad set level down to the individual image or video - but only if the ad set around it stays broad.

In Short

Meta now lets advertisers tell its system which age group and gender each picture or video in a campaign is meant for, instead of setting one audience for all of them. This matters to brands that run several different messages at once, such as a bank with one video for retirees and another for younger savers. The catch is that the overall ad set has to stay open to everyone from their mid-twenties or younger up to 65, of all genders, and the option cannot be combined with Meta's fully automated audience setting.

What Meta published

The post is short. It opens with a dated sentence: "Today, Monday, October 19, we launched a new feature that lets advertisers choose a specific audience for each ad creative." The capture supplied to PPC Land, taken on the evening of October 19, shows the post timestamped "3 hours ago" and tagged Business Tools, Developer Tools and Ads.

According to Meta, the setting works 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," the post states.

Two illustrations follow. "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," Meta wrote. The second concerns apparel: "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."

The rest of the page is aimed at developers. Under the heading "What does this mean for Marketing API partners?" Meta says: "Starting today, Marketing API partners will see this option available to them." Under a second heading on what partners should do, a single bullet reads: "Today: We encourage partners to review and test this feature starting today to fully benefit from this update."

There are no performance figures, no test results and no rollout percentages in the post. Nor does it say whether the toggle also appears in Ads Manager, which markets it covers, or which campaign objectives and placements are eligible. The header image is a stock-style illustration rather than a product screenshot, so the capture shows nothing of the interface itself.

Eight endpoints

Meta lists the same eight Graph API calls twice on the page, once under the examples and once under "Affected API endpoints":

  • 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}

The spread matters. Three of the calls sit at ad set level, three at ad level and two at creative level, which means the change touches every layer a third-party buying tool writes to when it builds a Meta campaign. Read and update calls are included alongside creation, so tools that sync existing campaigns, not only those that launch new ones, have to handle the new fields.

What the API reference adds

The "API reference" link in the post points to a Marketing API documentation page titled "Creative audience pairing," filed under audiences and targeting expansion. That page, not the blog post, carries the mechanics, and it is considerably more restrictive than the two upbeat examples suggest.

According to that documentation, the feature has two parts. An ad set opts in through a field named creative_audience_pairing inside targeting_automation, set to 1 to enable or 0 to disable; leaving it out keeps the feature off. The audience for each creative is then described in a separate object, creative_audience_pairing_persona. Meta's reference is explicit that switching the ad set flag on without supplying a persona does nothing, because there is nothing to pair.

Where the persona goes depends on the ad. For an ad with a single image or video, it sits as a top-level field on the ad next to the creative. For ads that carry several media assets, it is set on each image or video inside media_sourcing_spec, and in that case any persona set at ad level is ignored. That second path is how one ad can hold, say, a retirement video and a savings video with different age bands.

The persona itself has three fields, according to the reference:

  • age_min: 18 or older, and never lower than the ad set's own minimum age. On creation it defaults to the ad set's effective minimum.
  • age_max: up to 65, defaulting to 65 on creation.
  • genders: an array of up to two values, 1 for male and 2 for female, defaulting to all genders.

On updates, omitted fields keep their current values. The example URLs on the page use Graph API v26.0.

The ad set has to stay wide

The restrictions bite at ad set level. While pairing is enabled, Meta's reference requires the ad set's minimum age to be between 18 and 25, its maximum age to be 65, and its gender setting to be either omitted or set to both values. Single-gender ad sets are not allowed.

Put differently, the feature does not let an advertiser build a narrow ad set and then narrow it further per creative. The container must be broad, and the creative-level personas carve segments out of it. An advertiser running the fashion example from Meta's post would need an ad set open to all genders before assigning the women's and men's sweater images to their respective groups.

Incompatible with Advantage+ audience

The reference lists two conflicts. Creative audience pairing cannot be combined with Advantage+ audience, and it cannot be combined with age and gender suggestions, which are switched on through an individual_setting object with age or gender set to 1. Requests that break any of these rules, including a persona minimum age below the ad set's minimum, return Graph API error code 100.

That exclusion is notable. Meta has pushed advertisers toward its automated audience setting since at least 2025, and here it has built a demographic control that only works when that automation is off.

What the documentation does not say

Neither the blog post nor the reference page says how the persona affects delivery. The post's phrasing - the age range and gender each piece of media is "best suited for" - could describe a hard restriction, where a creative is never shown outside its band, or a signal the delivery system weighs alongside others. The reference does not resolve the question, and it does not mention reporting breakdowns, placements, objectives or Ads Manager. Whether an age_max of 65 means 65 and over is also not stated.

The post also leaves a regulatory question open. Its first example uses financial services. PPC Land's explainer on the special ad category describes how ads in the housing, employment and financial products categories run with age fixed at 18 to 65+ and gender set to all. Meta's post does not say whether creative-level personas are available to campaigns in those categories, or how the retirement-planning example would apply to an advertiser required to declare one.

A demographic control in an automated system

The launch runs against the direction Meta's ads products have taken. Meta removed detailed targeting exclusions for new ad sets on January 21, 2025, citing internal tests in which campaigns without exclusions performed 22% better. In May 2025 it began collapsing its separate shopping and app campaign types into a unified Advantage+ structure built on three automation levers - budget, audience and placement - where any placement targeting disqualifies a campaign from Advantage+ status. On October 8, 2025, Marketing API v24.0 blocked creation of legacy Advantage Shopping and Advantage App campaigns, with v25.0 extending the block across all versions in the first quarter of 2026.

Demographic levers have nonetheless survived in other forms. Value rules, which Meta extended to all ad accounts and campaign objectives in August 2025, allow bid adjustments by age range, gender, operating system, location and placement, with up to 10 rules of two criteria each. Those rules change how much an advertiser bids for a group; they do not decide which creative that group sees. In August 2026, PPC Land reported that some advertisers were losing the manual placements control in Ads Manager, leaving value rules with a maximum 90% bid decrease as the nearest substitute. The same Meta update round included ad-level age and gender suggestions - the very feature today's reference page says cannot be used alongside creative audience pairing.

The new option also slots into Meta's push toward many creatives per ad set. Meta introduced a creative breakdown in Ads Manager on July 11, 2025, covering flexible format ads that can hold up to 10 images and videos. In September 2026, some accounts began seeing a message that Page-level ad limits no longer applied, with one account running 286 ads against a 250-ad ceiling; Meta had already dropped its recommendation of six creatives per ad set from its help pages in July 2025. More creatives in one container raises an obvious question for advertisers: which audience is each one for? Until today, Meta's answer was that its retrieval and ranking systems would work it out.

That answer has drawn scepticism. PPC Land's November 2025 analysis of advertiser reactions to Meta's AI automation cited one incrementality test in which Advantage+ produced 17% of the conversions Meta's attribution reported, set against Meta's claims of a 22% return on ad spend uplift from Advantage+ creative features. Meta's Andromeda retrieval engine, announced in December 2024, narrows tens of millions of ad candidates to thousands per request. Creative audience pairing gives advertisers a way to feed their own view of who a creative is for into that process - with the trade-off that the fully automated audience setting has to be switched off.

Who is affected first

The blog post addresses Marketing API partners: the agencies, buying platforms and in-house tools that create Meta campaigns programmatically. For them the practical scope is concrete. Ad set create and update calls now accept a new targeting_automation flag; ad and creative calls accept a persona object at one of two levels; and requests that combine the flag with Advantage+ audience, age and gender suggestions, single-gender ad sets or an ad set minimum age above 25 will fail with error 100.

The timing sits close to other API work. Graph API and Marketing API v26.0 took effect on July 29, 2026, and most of its restrictions extend to all remaining supported versions on October 27, 2026 - eight days from today. Meta's Ads CLI, published on April 29, 2026, lets developers and AI agents create campaigns, ad sets, ads and creatives from a command line; the blog post does not say whether the CLI supports personas.

For brands, the use case Meta describes is message segmentation inside one budget pool. A bank with a retirement product and a savings product, or a retailer with menswear and womenswear lines, could keep both in one ad set rather than splitting them into separate ad sets with their own targeting. Whether that consolidation helps or hurts results is something Meta has not addressed: the post contains no data, and the company has published no test of the feature.

Timeline

Summary

Who: Meta, through a Meta for Developers blog post by Graham Mahon, addressed to Marketing API partners and the advertisers that use their tools.

What: A feature called "Choose an audience for each ad creative" that, when toggled on, lets advertisers run several ads in one ad set and assign each image or video its own age range and gender. Meta's API reference, titled "Creative audience pairing," requires the ad set to have a minimum age of 18 to 25, a maximum age of 65 and all genders, and bars use with Advantage+ audience and age and gender suggestions. Eight ad set, ad and creative endpoints are affected.

When: Today, Monday, October 19, 2026, with the option available to Marketing API partners from the same day.

Where: Meta's Marketing API, across the ad set, ad and ad creative endpoints. The post does not say whether the option appears in Ads Manager or which markets, objectives and placements it covers.

Why: Meta's examples point to advertisers that run distinct messages for distinct demographics - retirement versus savings products, menswear versus womenswear - and want them in one ad set. The launch matters because it reintroduces a manual demographic control into a system Meta has spent recent years automating, while leaving open whether the persona restricts delivery or only informs it.