DestinationsAdvertisingSnapchat Conversions API

Snapchat Conversions API

Send server-side conversion events to Snapchat for attribution and ad optimization via the Conversions API (CAPI). Server-side events improve measurement accuracy by bypassing browser limitations and providing more reliable conversion data.

Prerequisites

  • A Snapchat Ads account
  • A Snap Pixel set up in Snapchat Ads Manager
  • Your Pixel ID (UUID format)
  • Access to the Snapchat Marketing API

Authentication

Snapchat Conversions API uses OAuth 2.0.

  1. Click Connect with OAuth in Zeotap
  2. Sign in with your Snapchat account
  3. Authorize the requested permissions

OAuth scope: snapchat-marketing-api.

Configuration

FieldTypeRequiredDescription
Pixel IDTextYesYour Snapchat Pixel ID for receiving conversion events. Example: abc123de-f456-7890-abcd-ef1234567890
Snap App IDTextNoOptional Snap App ID for app-based conversion tracking

Supported Operations

Sync Modes

ModeSupported
InsertYes
Update
Upsert
Mirror

Audience Sync Modes

ModeSupported
AddYes
Remove
Mirror
Upsert

Features

FeatureSupported
Field MappingYes
Schema IntrospectionNo

Required Mapping Fields

FieldDescription
event_typeSnapchat conversion event type (e.g., PURCHASE, ADD_CART, PAGE_VIEW)
email or hashed_emailUser email for PII matching. Provide either a raw email (auto-hashed by Zeotap) or a pre-hashed SHA256 email

Default Destination Fields

Event

FieldDescription
event_typeThe Snapchat conversion event type
event_conversion_typeConversion type. Options: WEB, MOBILE_APP, OFFLINE. Default: WEB

User Data (raw)

These fields are automatically normalized and hashed with SHA256 before being sent to Snapchat.

FieldDescription
emailUser email address
phonePhone number with country code

User Data (pre-hashed)

These fields are passed through to Snapchat without additional hashing. Values must be lowercase SHA256 hex strings.

FieldDescription
hashed_emailSHA256-hashed email address
hashed_phoneSHA256-hashed phone number

Additional Fields

FieldDescription
priceMonetary value of the event
currencyISO 4217 currency code (e.g., USD, EUR)
transaction_idYour unique transaction identifier
item_idsProduct or content identifiers

Supported Event Types

Snapchat recognizes the following standard conversion events:

  • PURCHASE
  • ADD_CART
  • ADD_BILLING
  • ADD_TO_WISHLIST
  • APP_INSTALL
  • APP_OPEN
  • COMPLETE_TUTORIAL
  • INVITE
  • LEVEL_COMPLETE
  • LIST_VIEW
  • LOGIN
  • PAGE_VIEW
  • RATE
  • RESERVE
  • SAVE
  • SEARCH
  • SHARE
  • SIGN_UP
  • SPENT_CREDITS
  • START_CHECKOUT
  • SUBSCRIBE
  • VIEW_CONTENT

Custom event names are also supported.

How It Works

Zeotap reads rows from your model query and applies field mapping to transform your data into Snapchat’s Conversions API format.

PII hashing: Raw user data fields (email, phone) are automatically normalized and hashed with SHA256 per Snapchat’s requirements. Pre-hashed fields (hashed_email, hashed_phone) are passed through without re-hashing.

Batching: Events are batched up to 500 per API call to the Snapchat Conversions API endpoint. For syncs with more than 500 events, Zeotap automatically splits them into multiple API calls.

Event conversion type: Defaults to WEB if not explicitly mapped. Map event_conversion_type to override for MOBILE_APP or OFFLINE events.

Rate Limits

  • 500 events per API call — Zeotap automatically batches events to stay within this limit
  • Snapchat Marketing API rate limits apply based on your app’s usage tier

Troubleshooting

Invalid Pixel ID

Verify your Pixel ID in Snapchat Ads Manager. Navigate to Events Manager and locate the Pixel ID in your Pixel settings. The ID uses UUID format.

Events not appearing in Events Manager

Check that your event_conversion_type matches the actual event origin. Events may take a few minutes to appear in Snapchat Ads Manager. Verify that the Pixel is active.

Authentication failed

Snapchat OAuth tokens expire periodically. Reconnect your Snapchat account in Zeotap to refresh the credentials.

Missing event data

Each event requires at minimum an event_type and at least one user data field for matching (e.g., email or hashed_email). Verify your field mapping includes these required fields.