Snapchat Conversions API

Datafly Signal delivers events to Snapchat server-to-server using the Snapchat Conversions API (CAPI). This provides reliable conversion tracking for Snapchat ad campaigns without depending on the Snap Pixel client-side script.

Why route Snapchat through Datafly Signal

• Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Snapchat optimises against are not filtered by the browser.
• Email and phone number are hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Snapchat receives match keys rather than raw personal data.
• Client IP and user agent are carried in the payload. Both are taken from the original visitor request rather than your server, which is what Snapchat needs to attribute the event to the right session.
• Click identifiers are captured and replayed. Signal stores sccid first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
• Delivery is batched, rate-limited, and retried. Signal buffers to Kafka, respects the Snapchat rate limit, and retries on 429 or transient failure rather than dropping the event.
• Presets for Retail and Lead Generation. The mapping starts from a working configuration for your vertical instead of a blank field map.
• One consent decision governs every destination. Snapchat is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
• No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Before configuring Snapchat Conversions API in Signal, you need a Snapchat Business account, a Snap Pixel, and an API access token. Follow the steps below to set everything up.

Configure in Signal

Now that you have your Pixel ID and access token, configure the integration in Signal.

Configuration Fields

Management UI Setup

1. Go to Integrations > Add Integration > Snapchat Conversions API.
2. Enter your pixel_id and access_token.
3. Optionally enter snap_app_id if tracking mobile app events.
4. Select consent categories (typically advertising).
5. Click Save.

Management API Setup

curl -X POST http://localhost:8084/v1/admin/integrations \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "source_id": "src_abc123",
    "vendor": "snapchat",
    "name": "Snapchat Conversions",
    "enabled": true,
    "config": {
      "pixel_id": "your_pixel_id",
      "access_token": "your_access_token"
    },
    "consent_categories": ["advertising"]
  }'

API Endpoint

POST https://tr.snapchat.com/v2/conversion

Events are sent as JSON with authentication via the Authorization: Bearer header.

Identity Signals

Snapchat uses multiple identity signals to match server events to Snapchat user profiles.

Automatic Signals

These are sent automatically by Signal — no configuration needed:

When a user clicks a Snapchat ad, the ScCid parameter is appended to the landing page URL:

https://example.com/landing?ScCid=abc123def456

Datafly.js automatically captures the ScCid from the URL and persists it as a first-party cookie for the duration of the attribution window.

User-Provided Signals (Hashed)

When user data is available via datafly.identify(), the following fields are SHA-256 hashed before sending to Snapchat:

Event Mapping

Retail preset

To customise or extend (e.g. additional verticals, custom events), edit the integration’s Field Mappings in the Management UI.

Example: Purchase Event

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  total: 129.99,
  currency: "USD",
  products: [
    { product_id: "SKU-A", name: "Widget", price: 49.99, quantity: 2 },
    { product_id: "SKU-B", name: "Gadget", price: 30.01, quantity: 1 }
  ]
});

Snapchat Conversions API payload sent by Signal:

{
  "pixel_id": "your_pixel_id",
  "event_type": "PURCHASE",
  "event_conversion_type": "WEB",
  "timestamp": 1706540000000,
  "event_tag": "evt_abc123def456",
  "page_url": "https://example.com/checkout/confirmation",
  "user_agent": "Mozilla/5.0 ...",
  "hashed_ip_address": "d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5",
  "hashed_email": "836f82db99121b3481011f16b49dfa5fbc714a0d1b1b9f784a1ebbbf5b39577f",
  "hashed_phone_number": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6abcd",
  "click_id": "ScCid_abc123",
  "price": 129.99,
  "currency": "USD",
  "transaction_id": "ORD-001",
  "number_items": 3,
  "item_ids": ["SKU-A", "SKU-B"]
}

Example: Page View

{
  "pixel_id": "your_pixel_id",
  "event_type": "PAGE_VIEW",
  "event_conversion_type": "WEB",
  "timestamp": 1706539000000,
  "event_tag": "evt_789ghi012jkl",
  "page_url": "https://example.com/products/widgets",
  "user_agent": "Mozilla/5.0 ...",
  "hashed_ip_address": "d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5",
  "hashed_sc_cookie": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}

Testing Your Integration

Step 1: Send Test Events

1. Enable the integration in Signal and trigger events on your website.
2. Check the Signal event debugger to confirm events are being delivered.
3. Verify the delivery status shows successful responses ({"status": "SUCCESS"}) from Snapchat.

Step 2: Verify in Events Manager

1. In Snapchat Ads Manager, go to Events Manager.
2. Select your Snap Pixel / event source.
3. Go to the Overview tab. You should see events arriving with the “Server” source indicator.
4. Click on individual events to inspect the payload and match quality.

Step 3: Check Event Match Quality

1. In Events Manager, review the Match Quality indicator for your event source.
2. Snapchat rates match quality based on the identity signals provided.
3. To improve match quality, add more user identity signals via datafly.identify().

Troubleshooting

Rate Limits