Skip to main content
Pinterest Ads maps AdCP media buys to campaigns, packages to ad groups, and creative assignments to ads backed by Pins. Current code classifies seven product families as executable through deterministic contract coverage; this is not fresh provider eligibility. Catalog sales and Idea Pins remain explicitly blocked.
Review-ready, not provider-endorsed · last verified 2026-08-16. This is an Interchange compatibility review prepared for partner feedback. Pinterest has not reviewed, certified, or endorsed it. “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 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: Purchase/add-to-cart and lead/signup goals map to one exact conversion tag; optional CPA targets preserve micro-currency precision.
  • Event-source setup: Returns a buyer-instrumented Pinterest Tag snippet and installation instructions. It makes no Pinterest API call and emits no built-in provider event source.
  • Event ingestion: Activation is blocked: log_event is absent from public tools/list. A provider-authoritative guarded implementation remains internal until trusted selected-account/source bindings and signed live evidence are available.
  • Audiences: Audience synchronization and targeting are activation-blocked and are not claimed as publicly available while every governed lifecycle stage remains pending.

​
Known limits

  • Catalog Sales is blocked until the full catalog execution path is complete.
  • Idea Pins are blocked until creative upload, materialization, and reverse readback are complete.
  • Existing Pins remain hidden outside the governed canary path; that restriction is not evidence that a signed live run passed. Ordinary self-serve formats are standard image, video, and max-width video Pins.
  • Placement-group selection is not exposed; executable products currently use ALL.
  • Pinterest analytics can take up to 72 hours to stabilize, and supported attribution windows remain provider constrained.
  • The protected harness is ready, but canonical run 29671483671 skipped every Pinterest check because no dedicated staging account was configured; complete lifecycle, creative round-trip, and delivery remain ready_for_live.
  • sync_catalogs is partial: it registers feed URLs only and does not push inline catalog items.
  • get_account_financials is partial: campaign spend aggregation exists, while the v6 AccountStore variant returns UNSUPPORTED_FEATURE pending context threading.
  • Audience synchronization and include/exclude targeting are activation-blocked: every governed lifecycle stage remains pending and the audience canary is blocked.
  • log_event is absent from public tools/list. Its provider-authoritative guarded implementation remains internal until sync_event_sources publishes trusted selected-account/source bindings and a signed dedicated-account canary passes.

​
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 pinterest 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

​
Review questions

  • Does campaign → ad group → ad → Pin describe the provider hierarchy and ownership boundary accurately?
  • Are Standard, Video, and Max-width Video Pins the right ordinary self-serve creative scope, with existing Pins limited to governed canary proof?
  • Is placement_group ALL the correct current boundary when no per-placement AdCP selector is exposed?
  • Are the conversion-tag, audience, catalog, and reporting mappings accurate, including the analytics stabilization caveat?
  • Which market, account-permission, or product-eligibility distinctions should be added without implying that every account is eligible?