Matt Jones · 15 May 2026

Ads on Threads just grew up: what Meta's Marketing API update means for advertisers

Threads passed 400 million monthly users and Meta has shipped Marketing API updates to match: app ads went global, and advertisers can now moderate the replies under their ads. Matt Jones gives the practical paid-media read on whether Threads has earned a line on your media plan yet.

Ads on Threads just grew up: what Meta's Marketing API update means for advertisers

Threads quietly crossed 400 million monthly active users, and with that kind of scale the ad product was always going to get serious. Meta has now shipped a round of updates to the Threads Marketing API, and they matter more than the dry release note suggests. Two things changed: app ads went global, and advertisers can finally moderate the replies under their ads. Here is the practical read for anyone actually buying media, not just the headline.

First, why this is on our radar at all

For most of its life Threads was an organic-only land grab. Big reach, no real way to put paid budget behind it through the tools agencies live in. The platform sat in the "interesting, watch this space" pile rather than the media plan. An update to the Marketing API is the moment that changes, because it means we can build, launch and report on Threads campaigns the same way we already do for the rest of the Meta family, programmatically and at scale, rather than poking at a one-off interface.

Our take: the API support is the real news here, not the ad formats. A placement you can only buy by hand stays a side project. A placement that plugs into the same pipelines as Facebook and Instagram becomes part of the everyday plan. That is the line Threads has just crossed.

App ads, now global

App advertising is the headline addition. Through the Marketing API you can now run app campaigns on Threads worldwide, optimising for the objectives that matter: APP_INSTALLS, plus app-event optimisation against LINK_CLICKS or CONVERSIONS. The Threads feed becomes an extra placement, and, importantly, you do not need bespoke creative for it. Your existing images, videos and carousels work as they are.

Our take: "no new creative required" is the bit that gets this tested quickly. The friction in adding any new placement is usually the production cost, so when an extra surface opens up that runs your current assets, the sensible move is to let it into the campaign, measure the incremental installs, and keep it only if the numbers hold. For advertisers: if you are running app-install or app-event campaigns on Meta, Threads is now a low-effort expansion of reach rather than a separate build. Treat it as a new placement to validate, not a new channel to staff up for.

Reply moderation: the genuinely useful one

The second update is the one we are more interested in. Advertisers can now manage the conversation underneath their ads through the API: view the top-level replies on an ad, hide replies you do not want sitting under your brand, and post advertiser responses directly. Permissions split sensibly, the ads_read permission lets you see replies, while ads_management is required to hide them or respond.

Our take: open comments on a paid post are a brand-safety problem that has burned plenty of advertisers, and "just turn comments off" is a blunt instrument that also kills the social proof you paid for. Programmatic moderation is the grown-up answer: keep the conversation open, surface the replies that need a human, hide the genuinely toxic or spammy ones, and reply where it helps. The fact it is exposed through the API means it can be wired into a workflow and a tool, not left to someone refreshing the app. For advertisers: this is what makes spending real money on Threads defensible. You are not posting an ad into a comment section you cannot control. Agree the moderation rules up front (what gets hidden, who signs off on replies, how fast you respond) and the placement stops being a reputational gamble.

What we would do with this

Strip the announcement back and there are three concrete moves. First, add Threads as a test placement on existing app campaigns, since the creative cost is zero and the only question is whether the installs are incremental. Second, stand up a moderation workflow before the spend, not after, using the reply endpoints so the conversation under every ad is watched and handled by rule rather than by luck. Third, read it as an early-mover window: Threads ad inventory is younger and less crowded than Instagram or Facebook, which historically means cheaper attention for the advertisers who show up first and learn the placement properly.

The honest counterweight is the same one we apply to any shiny new placement: more reach is not the goal, profitable reach is. A new surface is only worth keeping if it earns its slice of budget against everything else you could spend it on, so we would hold Threads to the same efficiency bar as the rest of the account and cut it without sentiment if it does not clear it. And as ever, the placement only does the distribution, the creative and the offer still have to be worth scrolling for, which is the part the storytelling does.

If you are running paid social and want a clear-eyed view on whether Threads deserves a line on your media plan, that is exactly the kind of call we like to make with clients. Tell us about your goals and we will tell you straight whether it is worth your budget yet.