You set up the Snapchat Pixel, launched campaigns, and conversions show zero. Or they showed up for a while and suddenly stopped. Here’s how to diagnose and fix it.
Step 1: Is the Pixel Actually on Your Site?
Check with Snap Pixel Helper
Install the Snap Pixel Helper Chrome extension. Visit your site — it should show a green checkmark and list detected events.
If it shows nothing: the pixel code isn’t on the page. Check your GTM container or hardcoded script.
Check with Browser DevTools
- Open Chrome DevTools → Network tab
- Filter by
sc-static.netortr.snapchat.com - Navigate your site
- You should see requests to Snapchat’s tracking domain
If no requests appear, the pixel JavaScript isn’t loading.
Step 2: Is It Firing the Right Events?
Snapchat recognizes these standard events:
| Event | When to Fire |
|---|---|
PAGE_VIEW | Every page load |
VIEW_CONTENT | Product page |
ADD_CART | Add to cart |
START_CHECKOUT | Checkout begins |
PURCHASE | Order confirmed |
SIGN_UP | Account created |
ADD_BILLING | Payment info submitted |
If you’re only sending PAGE_VIEW, Snapchat can’t optimize for purchases. You need at least PAGE_VIEW + PURCHASE for conversion campaigns.
Verify in Snap Events Manager
Snap Ads Manager → Events Manager → select your pixel
Check:
- Last event received (should be recent)
- Event breakdown (shows which events fired)
- Match rate (how many events matched to Snap users)
Step 3: Common Problems
Problem: Pixel Fires But Zero Conversions Reported
Cause 1: Attribution window mismatch. Snapchat’s default attribution is 28-day click, 1-day view. If users click your ad but convert after 28 days, the conversion isn’t attributed.
Cause 2: Domain not verified. Snap requires domain verification for iOS 14+ campaigns. Go to Events Manager → “Manage” button → verify your domain via DNS TXT record or meta tag.
Cause 3: Low match rate. If your pixel sends events without identity data (no email, no phone, no _scid cookie), Snap can’t match events to Snap users. Check your match rate in Events Manager.
Problem: Pixel Stopped Working After an Update
Cause 1: Consent banner blocking the pixel. If you recently added a CMP, the Snapchat pixel might be categorized as “marketing” and blocked until consent.
Cause 2: GTM container update removed the tag. Check GTM → Versions → compare recent publishes. See our GTM audit checklist for systematic verification.
Cause 3: Site redesign changed URLs. If your triggers fire on specific URL patterns (like /checkout/thank-you), a URL change breaks the trigger.
Problem: Duplicate Events
If you’re firing both the browser pixel AND Snapchat CAPI, make sure you’re sending the same event_id on both. Without dedup, Snap counts every conversion twice.
Step 4: Snapchat CAPI
Like Meta CAPI and Google Enhanced Conversions, Snapchat has a server-side Conversions API that sends events from your server:
Endpoint: https://tr.snapchat.com/v2/conversion
Required parameters:
pixel_id— your Snap Pixel IDsnap_app_idor access tokenevent_type—PURCHASE,ADD_CART, etc.hashed_email— SHA-256 hashed lowercase emailevent_conversion_type—WEBpriceandcurrency— for revenue tracking
Snapchat CAPI recovers conversions from users with ad blockers or iOS tracking restrictions.
Step 5: Verify End-to-End
- Open Snap Pixel Helper (or DevTools)
- Complete a test purchase on your site
- Verify
PURCHASEevent fires with correctpriceandcurrency - Wait 30 minutes → check Events Manager for the event
- If using CAPI: check that both browser and server events appear with the same
event_id
Still Broken?
If you’ve checked all steps and conversions aren’t recording:
- Verify your ad account and pixel are linked to the same organization
- Check if your Snap Pixel ID is correct (typos in the ID = events go nowhere)
- Contact Snap support with your pixel ID and event logs
Or run a free tracking scan — we check your Snapchat Pixel alongside GA4, Meta, and all other platforms automatically.