Meta Ads adapter compatibility

Meta Ads maps AdCP media buys to campaigns, packages to ad sets, and creative assignments to ads across the governed Facebook and Instagram placement catalog.

​

Coverage and execution-package model

​

Claim provenance gaps

Object-mapping and reporting rows have no exported, code-owned complete denominator on current main. They remain published because they are useful, but the contract marks the missing drift oracle instead of pretending a same-test literal prevents drift.

​

Evidence state

Static certification and live certification are different claims. Deterministic tests can prove code-owned catalog classifications and fail-closed behavior without contacting the provider. Object-mapping and reporting rows are validated for shape, presence, and uniqueness only; the provenance table above records that they are not compared with a complete code-owned denominator. Fresh live evidence must be dated, signed, bound to the exact account, product, resources, fixture revision, requested package, readback, no-spend result, and cleanup result. Live evidence is treated as stale after 30 days, and a newer failure overrides an older pass.

​

Markets

account_check_required. No global market allowlist is asserted by this public contract. This page publishes no global market allowlist. Authority: The selected account’s live provider eligibility and targeting reads are authoritative.

​

Object mapping

​

Operations

​

Wholesale products and exact execution bases

​

Creative formats

The format state is deliberately narrower than the provider format catalog. Only executable formats have the ordinary provider write and readback path; canary_only formats are restricted to governed proof, and catalog_declared formats are present in current code without a public ordinary-execution certification claim. declared_not_buyer_selectable formats are not sold through the adapter.

​

Placements

​

Targeting

​

Reporting

​

Conversion and audience support

• Optimization: Website, app, lead, message, call, and value goals are represented by explicit product mappings.
• Event sources: Pixels, apps, and supported built-in sources are discovered and validated.
• Event ingestion: Conversions API events are supported through log_event.
• Audiences: Custom Audience synchronization, readiness polling, inclusion, and exclusion are implemented.

​

Known limits

• Messenger Inbox, Messenger Stories, and Threads Feed remain canary candidates rather than public placements.
• Existing-post creative sync remains restricted to the signed paused canary.
• AdCP 3.2 budget and bidding replacement is not exposed as an atomic update; create a replacement media buy instead.
• Provider account permissions, Page/Instagram/WhatsApp ownership, and objective eligibility can narrow the catalog.

​

Public review endpoints

• AAO registry record
• Staging MCP/AdCP state: relationship_gated_storefront_id_required.
• Route template after a storefront relationship supplies its registered platform ID: https://api.staging.interchange.io/seller/{registered_storefront_platform_id}/mcp
• No provider-ID-derived URL is published. The shared MCP route requires the registered storefront platform ID assigned to the relationship; the adapter provider ID meta is not asserted to be that record ID.

The staging endpoint is connection-gated. Its presence here is not an invitation to send mutating requests without a jointly approved test account and canary window.

​

Provider references

• Meta Marketing API overview
• Meta Campaign reference
• Meta Ad Set reference
• Meta Insights API

​

Review questions

If a provider mapping is incomplete or has changed, send the exact product, format, targeting dimension, metric, market, or provider API field that differs. We update the governed contract and add code-owned drift checks where a denominator exists; otherwise the explicit non-enforced provenance gap remains.