Skip to main content
This page compares the Snap Ads capabilities represented in the Apostra adapter with what Apostra currently makes available to buyers. It answers a practical question: what can I do through Apostra today, and what would still require another path?
Last reviewed 2026-08-20. This is Apostra’s description of its own adapter, based on the implementation and the linked provider documentation. Snap Ads has not reviewed or endorsed this page. Availability can still vary by account permissions, market, and provider access.

​
At a glance

​
How to read availability

  • 🟢 Available — Offered through Apostra now, subject to your ad account’s permissions and eligibility with the provider.
  • 🟡 Partial — Some of the workflow is available; the Comments column explains the boundary.
  • 🔵 Testing — Apostra is validating the workflow before offering it broadly.
  • ⚪ Planned — Not offered through Apostra yet. The provider may still support it directly; Comments explains why and links a roadmap reference.

​
Roadmap

The adapter roadmap is tracked in AI-1945 (a plain-text reference — Apostra’s internal issue tracker is not public). This roadmap tracks Snap adapter product completeness, provider access, and live readiness. Every row that is not currently available shows that reference or a more specific one in its References column, so customers and partners can quote a stable identifier when asking about a capability.

​
Connection, accounts, and identity

Snap Ads connects to Apostra through an OAuth grant. Connecting a Organization account gives Apostra access to each Ad account it can reach — you then map each one to your advertisers. The mapped account decides which Snap Ads tenant a buy runs on: a media buy for an unmapped advertiser fails closed with account_mapping_required rather than silently using another account. Connection, account-discovery, and revocation behavior is the same across ad platforms — see Platform accounts and advertiser mapping for the full model and the Snap Ads section of the connecting guide for Snap Ads-specific permissions.

​
Campaign products

​
Creative formats

These rows describe Apostra availability, not a claim that the ad platform itself prohibits an unavailable format.

​
What the adapter can do

​
Placement choices

​
Targeting

​
Reporting

Apostra reports Snap Ads delivery day by day (there is no hourly delivery breakdown), aggregated nightly from adapter-reported delivery, in the advertiser’s home currency using the booked or historical exchange rate — any cross-currency rollup is always labeled an estimate and is never used for billing. See Reporting overview for the full model. Apostra does not currently publish an attribution-finality window for Snap Ads; the table below lists every metric the adapter surfaces today.

​
Webhooks and async lifecycle

Snap Ads does not push status, delivery, or reporting events into Apostra — every campaign product declares supports_webhooks: false.
  • Status. Apostra does not currently poll Snap Ads in the background for creative or media-buy status changes; status reflects what the adapter returned on your last call.
  • Delivery. Apostra fetches delivery numbers (spend, impressions, clicks) live from Snap Ads on demand, only when you call get_media_buy_delivery directly. The /reporting/metrics endpoints never call the adapter either way — they read from a separately-populated store (see Reporting below), so a reporting request does not itself refresh provider delivery.
This is separate from Apostra’s own buyer webhook subscriptions — an unrelated account-level event feed (currently discovery.revision only), documented in Buyer webhooks.

​
Market and account availability

Apostra does not promise that every feature is enabled for every account or market. Availability is checked against your selected ad account rather than a global market list on this page.

​
Important limitations

  • Apostra implementation/testing. Snap preview requires an image or video creative already synchronized to the selected ad account; unsynchronized creatives and explicit placement selections cannot be previewed.
  • Apostra implementation/testing. Catalog traffic, app installs, Story Ads, Collection Ads, lead generation, Sponsored Snaps, and Commercials are not available through Apostra.
  • both Apostra’s implementation and the ad platform’s API or account eligibility. Promoting an existing Public Profile Snap is still being tested, and Snap must allow the selected profile to use it.
  • Apostra implementation/testing. Governed CRM audience activation remains protected until the dedicated consented fixture is certified.
  • Apostra implementation/testing. Apostra uses Snap’s automatic placement choice instead of exposing individual placements.
  • the ad platform’s API or your account’s eligibility. Account permissions and Snap feature access can narrow audience, Pixel, catalog, and creative availability.
  • Apostra implementation/testing. Apostra has not yet completed end-to-end account validation for the full Snap campaign lifecycle.
  • the ad platform’s API or your account’s eligibility. Web Conversions (and any other Pixel-optimized product) requires the selected Snap Pixel to have enough tracked conversion events. The conversion window is fixed by the product/optimization goal you choose, not something you select separately. When Apostra can complete its preflight check, a pixel below Snap’s eligibility threshold is refused up front with SNAP_PIXEL_INELIGIBLE. If that check itself fails (a transient Snap-side error), Apostra proceeds and Snap’s own validation is the backstop, so an ineligible pixel can occasionally still surface as a generic rejection after resources are created and rolled back.

​
Technical mapping

Engineering-level detail — raw provider objectives, billing enums, optimization codes, and object-field mappings. Not required reading to understand what Apostra can do with Snap Ads; see the tables above for that.

​
Provider documentation