Snapchat Ads

Datafly Signal delivers conversion events to Snapchat server-to-server, replacing the client-side Snap Pixel with lightweight server-side delivery. This provides reliable campaign attribution and ad performance measurement without loading vendor JavaScript.

Why route Snapchat Ads 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 Ads 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 Ads 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 Ads 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 Ads rate limit, and retries on 429 or transient failure rather than dropping the event.
• Presets for Retail and Travel. The mapping starts from a working configuration for your vertical instead of a blank field map.
• One consent decision governs every destination. Snapchat Ads 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 Ads in Signal, you need a Snapchat Business account with a Snap Pixel created and an API key generated.

Configure in Signal

Now that you have your Pixel ID and API key, configure the integration in Signal.

Configuration Fields

Vendor Click IDs

Signal automatically captures the following Snapchat click identifiers from URL parameters:

These are captured automatically by the Datafly.js collector and forwarded with conversion events.

Management UI Setup

1. Go to Integrations > Add Integration > Snapchat Ads.
2. Enter your pixel_id and api_key.
3. Select consent categories (typically advertising).
4. 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_ads",
    "name": "Snapchat Ads Production",
    "enabled": true,
    "config": {
      "pixel_id": "abc123de-f456-7890-gh12-ijkl34567890",
      "api_key": "ak_snap_abc123..."
    },
    "consent_categories": ["advertising"]
  }'

API endpoint

POST https://tr.snapchat.com/v3/{{pixel_id}}/events

Allow egress to tr.snapchat.com from the network your delivery workers run on.

Event Mapping

Retail preset

Travel preset

To customise, edit the integration’s Field Mappings in the Management UI.

Identity Signals

Automatic Signals

These are sent automatically by Signal — no configuration needed:

User-Provided Signals

When a user is identified via datafly.identify(), additional signals improve match quality:

Testing Your Integration

Step 1: Send a Test Event

1. Trigger a page view or conversion event on your website.
2. Check the Signal event debugger in the Management UI to confirm the event was captured and delivered.

Step 2: Verify in Snapchat Events Manager

1. In Snapchat Ads Manager, go to Events Manager > your Pixel.
2. Click on the Overview tab to see received events.
3. Events should appear within a few minutes.

Step 3: Validate Attribution

1. Create a test campaign with a small audience.
2. Confirm that conversion events are attributed correctly in campaign reports.
3. Check that sccid click IDs are being matched for click-through attribution.

Troubleshooting