On October 19, 2026, Meta added an option to its Marketing API called “Choose an audience for each ad creative.” Inside one ad set, every image or video can now carry its own age range and gender. Until now that choice lived only at the ad set level. For the moment, it is aimed at third-party platforms that build campaigns through the API.
What exactly changed?
Previously, age and gender were set once per ad set, and every creative inside competed for the same people. Now you can tell Meta who each image or video suits best. Meta’s own examples: a financial company pairing retirement-planning videos with ages 50 to 65, and a fashion retailer pairing women’s sweater photos with women and men’s sweaters with men.
Meta’s stated reason is to connect the right visual with the right promotion. Social Media Today notes that Meta’s systems may already infer some of this from product catalog data, and that explicit input could make delivery more relevant.
What are the rules and limits?
According to the API documentation as described by PPC Land, the feature comes with specific conditions:
- The ad set’s minimum age must be between 18 and 25, and the maximum must be 65.
- The ad set’s gender must stay open to everyone. Single-gender ad sets are not allowed.
- The ad set stays broad, and each creative’s audience narrows within it.
- It cannot be combined with Advantage+ audience or with age and gender suggestions.
- A creative’s minimum age cannot be lower than the ad set’s, and requests that break the rules return an error.
In plain terms: Meta is not handing back fine-grained targeting. It is letting you say which creative fits which profile inside a wide base.
Who can use it today?
The documentation and Meta’s announcement describe API access only. Neither mentions Ads Manager, specific markets, campaign objectives or placements. If you build campaigns in Ads Manager, there is no confirmation the option shows up there. If you use a third-party tool, ask the vendor whether it supports the feature yet.
What is still unknown?
Several gaps remain, and neither source closes them:
- Delivery: it is unclear whether a creative’s audience strictly limits who sees the ad or only guides the system. Meta’s phrase “best suited for” could mean either.
- Reporting: nothing is said about breakdowns by creative audience, and Meta published no performance tests.
- Special ad categories: it is unclear whether the option works for housing, employment or financial campaigns, which normally run with fixed age and gender.
- The age 65 cap: it is not clear whether the ceiling excludes people older than that.
Social Media Today also flags a side effect: people shopping for gifts outside the targeted group may see less relevant ads, something to watch this holiday season.
What does it change for sellers?
In our assessment, the gain is bigger for stores with a few very different creatives. Picture a clothing shop with one photo for women’s wear and another for men’s. Before, both sat in the same ad set and the system learned on its own which worked for whom. Now you can give it a head start.
If you sell a single product to a single audience, the change is irrelevant. And over-restricting is a real risk: if you pick a narrow band and Meta treats it as a suggestion, you may pay for delivery outside your profile and think the test was clean.
A careful way to test once your tool supports it:
- Pick two creatives with clearly different appeals, for example one for gifting and one for personal use.
- Run them with per-creative audiences in one ad set, and the same creatives without the option in another, with equal budgets.
- Compare cost per purchase, not clicks. If you have not worked out your break-even yet, see what ROAS is and how to find your minimum number.
- Wait several days before concluding anything, so you do not decide on a handful of sales.
If the open question is how much to put behind each test, how much to spend on Google Ads and Meta helps you size it.
When do more rules take effect?
PPC Land reports that most Graph API v26.0 restrictions extend to all remaining supported API versions on October 27, 2026. Whether Meta’s command-line tool supports the feature is not stated.
For now, treat this as a behind-the-scenes feature for people using partner tools, not something to rush after today.
