Meta AI Ads

Meta does not document “Meta AI Ads” as a separate ad-buying product. Its first-party material describes AI interactions as a signal for ad recommendations, and describes a Meta AI business assistant inside existing advertiser tools. See AI recommendations, AI performance, and the business assistant announcement.

As of 2026-08-31, no first-party source checked here documents a standalone Meta AI Ads API, Meta AI-specific Conversions API, click ID, pixel, token, or self-serve signup. The checked sources are Meta’s AI recommendation announcement, Meta’s business assistant announcement, Meta’s Marketing API workspace, and Meta’s Business SDK. Do not create an adapter for those surfaces.

Use ad-conversion-hub for the canonical event envelope, consent gate, identity rules, retry policy, and adapter contract. Pair it with ad-experiments for one-audience tests, seed sizing, and PII-export authorization.

Account and access

For ordinary Meta inventory, Ads Manager is Meta’s documented starting point for running ads on Facebook, Instagram, Messenger, and Audience Network. It also provides campaign tracking. See Meta Blueprint’s Ads Manager guide.

Meta’s official Marketing API workspace documents campaign, ad set, ad, and insights operations for the broader Facebook Marketing API. It requires an ad account, an account ID, and an access token. See Meta’s official Marketing API workspace.

The official Meta AI business assistant route is in existing advertiser interfaces. Meta says its beta is expanding to advertisers and agencies, and lists Ads Manager, Meta Business Suite, and Business Support Home as interfaces. See Meta’s announcement.

There is no separate self-serve Meta AI Ads signup in the official sources checked. If the assistant is absent from the approved Meta interface, stop. See Meta’s business assistant announcement. Do not invent an enrollment URL, developer app, beta token, or account field.

Meta’s later Business Agent announcement is a different product. It describes a customer-facing agent, a selected-business rollout, and a waitlist. Do not treat that waitlist as Meta AI Ads access. See Meta Business Agent.

Client-side Meta Pixel

There is no Meta AI-specific browser tag or pixel documented in the sources checked. The sources describe AI recommendations and an assistant in existing tools, not a Meta AI browser tag. See Meta’s AI recommendation announcement and business assistant announcement. Do not add a Meta AI script, pixel ID, or browser event namespace.

For broader Meta inventory, use the approved Meta Pixel implementation in ../ads-meta/SKILL.md. Meta’s first-party Google Tag Manager template shows the Meta Pixel event path, consent control, advanced matching, and an Event ID input for events also sent server-side. See Meta’s Pixel template.

Keep the browser path disabled until the hub grants measurement consent. The Meta template states that the pixel sends no hits until consent is granted. See the consent setting in Meta’s template.

Rule setup and event mapping

Meta AI has no documented conversion rule, event catalog, or advertiser event mapping. Meta’s AI recommendation announcement describes how AI interactions can influence recommendations, not how advertisers register conversion events. See Meta’s AI recommendation announcement.

Keep the canonical event in the hub. Do not dispatch a hub event to a Meta-AI-specific destination. Record the first-party event in your system and use payment-provider truth for purchases and refunds.

If the campaign uses ordinary Meta inventory, map events through ../ads-meta/SKILL.md. Do not copy that mapping into this skill and label it Meta AI behavior.

Server-side conversions API

There is no verified Meta AI-specific Conversions API in the official sources checked. Meta does provide a broader Conversions API for web, app, and offline events. Meta’s official Node.js Business SDK documents ServerEvent, EventRequest, UserData, CustomData, and a Purchase example. See the official Meta Business SDK.

That broader CAPI route does not prove Meta AI attribution. Use it only for approved Meta inventory, through ../ads-meta/SKILL.md. Do not send a hub event to a guessed Meta AI endpoint.

The Meta SDK example uses an access token and pixel ID for the broader CAPI request. It does not document a Meta AI token or pixel. See the CAPI example.

Do not add an endpoint, Graph API version, parameter set, token scope, or response contract here. Meta’s official sources checked here do not provide those details for a Meta AI Ads product.

Identity and consent

The hub owns the measurement consent decision and identifier policy. Hash identifiers only after consent permits ad-user data. Keep normalized values temporary and keep secrets in the server secret store.

Meta’s official SDK says its Conversions API Parameter Builder can fill user_data.fbc, user_data.fbp, user_data.client_ip_address, event_source_url, and referrer_url from an incoming request. It also says that its Node.js customer-information parameters are normalized and SHA-256-hashed. See the SDK’s Parameter Builder documentation.

Those are broader Meta CAPI fields. They are not Meta AI-specific identity fields. Do not send chat content, assistant memory, inferred interests, or sensitive context as conversion identity or event data.

Meta says that conversations about religion, sexual orientation, politics, health, racial or ethnic origin, philosophical beliefs, and trade-union membership are not used to show people ads. Do not use that statement as permission to export such data. See Meta’s AI recommendation privacy description.

Click ID and first-party cookie

No Meta AI-specific click parameter, cookie name, attribution window, or reporting join key is documented in the official sources checked. The broader SDK’s request-context fields do not establish a Meta AI contract. See Meta’s AI recommendation announcement and Meta’s Business SDK. Do not invent a click parameter or promise a reporting window.

For broader Meta inventory, the official SDK documents the request fields fbc and fbp. Use them only through the approved Meta adapter and its current first-party documentation. See the SDK’s request-context fields and the Meta Ads skill.

Do not require a Meta click ID before recording a first-party signup, checkout, purchase, subscription, or refund in the hub.

Deduplication

Meta AI has no documented browser/server deduplication contract in the checked product sources. See Meta’s business assistant announcement. Do not add Meta AI-specific event IDs or deduplication rules.

For broader Meta inventory, Meta’s first-party Pixel template exposes an Event ID setting for an event also tracked server-side and says the ID can deduplicate the same event from multiple sources. Use the exact browser/server contract in ../ads-meta/SKILL.md. See Meta’s Pixel template.

Ads Manager settings that override code

Treat the approved Meta console state as authoritative. The Meta AI business assistant is described as a beta feature inside existing advertiser tools, and Meta says its availability is expanding. See Meta’s business assistant announcement.

No code setting can create a documented Meta AI Ads placement, conversion rule, or reporting breakdown. The checked Meta AI material describes recommendations and advertiser assistance, not those surfaces. See Meta’s AI recommendation announcement and business assistant announcement. A successful broader Meta Pixel or CAPI request proves only that broader Meta processing accepted the event path.

Meta also says that AI interactions can personalize content and ad recommendations in most regions, with user controls and regional variation. That is a recommendation and privacy behavior, not an advertiser conversion receipt. See Meta’s AI recommendation announcement.

Verification

Use three separate proofs:

1. Access proof: confirm that the approved Meta interface shows the business assistant or the ordinary Meta inventory account. Do not infer Meta AI access from a broader API credential.
2. First-party proof: record the consent decision, canonical event ID, and payment-provider or signup result in your own server logs.
3. Platform proof: verify broader Meta events in the Meta reporting surface configured for that campaign. Do not call that result Meta AI attribution unless Meta exposes a current, named AI placement and reporting join.

The official Ads Manager guide describes Ads Manager as the place to create, manage, and track ordinary Meta campaigns. See Meta Blueprint.

Common pitfalls and security

• Treating Meta AI recommendations or an advertiser assistant as ad inventory.
• Treating the Meta Business Agent waitlist as Meta AI Ads access.
• Creating a guessed Meta AI endpoint, token, pixel, parameter, or event name.
• Treating broader Meta CAPI receipt as Meta AI attribution.
• Sending raw email, phone, chat content, memory, or sensitive context to an undocumented ad destination.
• Letting missing Meta AI access fail checkout. Return skipped for this destination and preserve the first-party event. See ad-conversion-hub.
• Storing approved Meta tokens in browser code, URLs, logs, screenshots, or commits. Keep them in the server secret store.

Official sources checked (2026-08-31)

• AI recommendations · AI performance
• Meta AI business assistant · Meta Business Agent
• Ads Manager guide · Meta Marketing API workspace
• Meta Node.js Business SDK · Meta Pixel GTM template