Review-ready, not provider-endorsed · last verified 2026-08-16.
This is an Interchange compatibility review for technical feedback, not a Snap certification or endorsement. “Implemented” means a provider write/read path exists.
It does not mean fresh signed live evidence exists or that the selected account
is currently eligible.
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-country 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. Onlyexecutable 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: The executable conversion product maps purchase, add-to-cart, or signup to one exact Snap Pixel source.
- Event sources: Snap Pixels are discovered and readiness checked.
- Event ingestion: Conversions API events are supported through log_event.
- Audiences: Audience synchronization, readiness polling, and include/exclude targeting are implemented.
Known limits
- Catalog traffic, app installs, Story Ads, Collection Ads, lead generation, Sponsored Snaps, and Commercials remain blocked until creative round-trip coverage is complete.
- snap_existing_post is not an ordinarily executable format: the code-complete Public Profile path requires the protected canary gate and external provider allowlisting, and remains Yellow/ready_for_live.
- The protected Snap harness is ready, but no successful dated signed run currently supplies live-provider lifecycle evidence.
- The public AAO community mirror excludes snap_existing_post, so discovery metadata does not advertise it as ordinarily eligible.
- The AAO full-screen placement is a discovery umbrella; the ordinary executable path uses provider automatic placement.
- Account permissions and provider feature eligibility can narrow audience, pixel, catalog, and creative availability.
- A live canary result applies only to its exact account, fixture revision, product, and format.
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 snap is not asserted to be that record ID.