Marketing by Raj

Meta API Update: AI Labels, Device Targeting Defaults

Meta has changed its Graph and Marketing APIs, letting apps add or remove AI self-disclosures, expanding device targeting by default and deprecating a video metric. Anyone running Meta ads through third-party tools should check their settings.

Rajesh Kumar · 6 Nov 2026 · 3 min read

Meta API Update: AI Labels, Device Targeting Defaults
Key takeaways
  • Graph API v27.0 apps can add or remove a post's AI-generated self-disclosure.
  • New sales ad sets with device or OS targeting now expand reach to other devices by default, though this can be turned off.
  • Meta may auto-enable product showcase on API-created ads; it can be switched off manually.
  • The total video consumption rate metric is being deprecated, following earlier deprecations of 3-second viewers and video reach.
  • Agencies and media buyers using third-party tools should audit defaults, reports and vendor readiness.

What happened

Meta has announced a set of changes to its Graph API and Marketing API. These are the connections that let third-party tools manage Facebook and Instagram content and ad campaigns without the advertiser logging into Meta's own Ads Manager. According to Social Media Today, the changes will affect how those tools handle publishing and campaign setup.

Here is what the report lists:

  • AI self-disclosure control. Apps using Graph API v27.0 can add or remove the AI-generated self-disclosure on a post.
  • Device targeting defaults. New sales ad sets that target specific mobile devices or operating systems will, by default, expand reach to people on other mobile devices. You can change this manually to keep strict device targeting.
  • Product showcase. Meta may automatically turn on product showcase for ads created through the API. This can also be switched off.
  • Legacy request features restricted. As of Nov. 4, new apps cannot use multi-ID requests, date/time formatting, HTTP method override, field aliases, JSONP callbacks or asynchronous batch requests. Existing apps cannot add new use cases for them. This applies across all Graph API versions.
  • Metric deprecation. The total video consumption rate metric is being deprecated. The 3-second video viewers and video reach metrics were already deprecated with Graph API v26.0.

Why it matters

Most Meta advertisers still work inside Ads Manager, so this will not touch everyone. But agencies, media buyers and larger ecommerce brands often run campaigns through API-connected tools, because they can manage many accounts and platforms in one place. For those teams, the risk is not the headline feature. It is the quiet defaults.

The device targeting change is the one I would watch most closely. If you built a sales campaign around a specific operating system or device type, perhaps because your app, checkout or creative suits one environment, a default that widens delivery can shift who sees your ads. It can be reversed, but only if someone notices.

The product showcase default works the same way. An ad you built one way may behave differently if the feature switches on automatically. That might help or hurt, depending on your catalog quality and creative approach.

The AI disclosure question

The ability to hide an AI-generated self-disclosure is the most talked-about item. Social Media Today calls it an odd change given ongoing questions about AI transparency. I agree it is awkward timing.

The practical point is that the option exists at the tool level. Your social management platform may eventually offer a toggle. Whether you use it is a brand decision, not a technical one. Audiences are increasingly wary of synthetic content, and being caught hiding AI use costs more trust than a small label does.

Reporting and tooling impact

The video metric deprecation matters if you have dashboards or client reports that pull video data through the API. Metrics that disappear can leave blank columns or broken calculations. The restrictions on older request methods mostly concern developers, but if your agency or software vendor relies on those methods, ask whether their integration is affected.

What to do now

  1. Audit device-targeted sales campaigns. Check any ad set created via API that uses device or OS targeting, and confirm whether expanded reach is on.
  2. Check product showcase status. Review newly created API ads and decide whether you want it on or off.
  3. Ask your tool vendor whether they support Graph API v27.0 and how they handle the new defaults.
  4. Review reporting templates. Remove or replace the deprecated video metrics so your reports stay accurate.
  5. Set an AI labeling policy. Decide in advance when AI-generated content gets disclosed, so the choice is not left to whoever is scheduling posts.
  6. Document your settings. Keep a simple checklist of the intended targeting and placement settings, and compare it with what actually launches.

The bottom line

None of these changes is dramatic on its own. Together they show a pattern: Meta keeps nudging advertisers toward broader delivery and more automation, and expects you to opt out if you disagree. If you rely on third-party tools, the job is to verify what actually goes live rather than assume your settings carried over.

Raj's take

The defaults worry me more than the AI label toggle. Meta keeps widening delivery unless you opt out, and teams using API tools can easily miss that. I would verify what actually launches in the account, and I would keep AI disclosure on unless there is a very good reason not to.

Get the Daily Signal: AI, SEO and social media news in five minutes.

Want this applied to your business?

Free, no login: SEO, speed and AI-visibility score in about 60 seconds. One audit per email.

Related