Snapchat pixel setup takes five steps: create the Snap Pixel in Ads Manager and share it with your ad accounts; install it directly, through Google Tag Manager or a store integration; map Snap’s standard events to real actions on the site; test with Test Events and the Snap Pixel Helper; then add the Conversions API with a shared deduplication ID so purchases aren’t counted twice.
- Create the pixel in the client’s organization, not the agency’s.
- Turn on Automated Matching when you set it up.
- PURCHASE fires once per order, with price, currency and transaction ID.
- Pixel and Conversions API events pair on the same ID within 48 hours.
Step 1: Create the pixel in the right place
In Ads Manager, open the menu and go to Pixels, then click Create Pixel. Share it with the ad accounts that will optimize to it, then open Set up Pixel to get the Pixel Code. Snap marks Automated Matching as recommended; turn it on so Snap can use hashed customer details from the page to match visitors.
Create the pixel in the client’s organization. A pixel built inside the agency’s organization works until the agency changes, and then the client’s tracking moves with someone else. If an agency needs it, share it from the client side under Business Details, then Shared. Roles are covered in Snapchat Ads Manager roles.
Step 2: Choose how to install it
Snap Pixel install routes
| How | Conversions API | Good for | |
|---|---|---|---|
| Pixel code on the site | Paste the base code and event calls into the site | A separate build | Custom sites with a developer |
| Google Tag Manager | Events Manager: New Event Source, Web, Snap Pixel, Partner Integration, Google Tag Manager; sign in and pick the container and workspace | A separate setup | Sites already tagged through GTM |
| Shopify | Snapchat Ads app | Installed automatically | Shopify stores |
| Zid | Zid integration | Installed automatically | Zid stores |
| Salla | Salla integration | A separate CAPI app | Salla stores |
| WooCommerce, Wix | Snap’s plugin or app | Creates a CAPI token and syncs the catalog | Stores on those platforms |
| BigCommerce | Script Manager | A separate setup | BigCommerce stores |
Pick one route per site. Two routes at once, such as a store app plus a GTM tag, is a common reason an account reports more purchases than the shop recorded, in the accounts we’ve audited. If you’re installing through GTM, the tag-side walkthrough is TikTok and Snap pixels in Google Tag Manager.
Step 3: Map standard events to real actions
Snap requires at least one standard event for attribution. Map each one to the moment it describes, not to the nearest page load:
Snap Pixel event map
| Snap event | Fire it when | Send with it | |
|---|---|---|---|
| Any page | PAGE_VIEW | A page loads | Nothing extra |
| Product page | VIEW_CONTENT | A product or key content page loads | Product ID matching your catalog |
| Add to cart | ADD_CART | The add-to-cart action succeeds, not when the cart page opens | Product ID, price, currency |
| Checkout | START_CHECKOUT | Checkout starts, not at a later step | Value, currency |
| Payment details | ADD_BILLING | Payment details are entered | Value, currency |
| Order confirmation | PURCHASE | Once per order, on the confirmation page | Price, currency, transaction ID |
| Lead or sign-up | SIGN_UP | The form submission succeeds | Hashed email or phone, if available |
| Search | SEARCH | A site search runs | The search term |
Snap also has SUBSCRIBE, START_TRIAL, ADD_TO_WISHLIST, SAVE, RESERVE, LIST_VIEW and others, plus five custom events. Price, currency and transaction ID on PURCHASE are what make ROAS reporting work. Customer details such as email, phone, name and location can only be passed when the pixel first loads, and Snap’s code hashes them.
Step 4: Test before you trust it
- In Events Manager, click Test Events, choose the pixel, enter your site URL and click Open Website. Events appear in near real time until you close or refresh the page.
- Install the Snap Pixel Helper Chrome extension and click through the funnel: product, add to cart, checkout, purchase.
- Place a real test order. Check that exactly one PURCHASE arrives, with the right value, currency and transaction ID.
- Check that staging and test domains don’t fire the production pixel.
- After a few days of traffic, check each event’s Event Quality Score in Events Manager: Good, Okay or Poor.
Step 5: Add the Conversions API without double counting
Browser pixels lose events to blockers and closed tabs, so Snap recommends adding the Conversions API, which sends the same events from a server. Setup routes include a direct integration, Snap’s listed partners (tag managers such as Google Tag Manager and Stape, commerce platforms and customer data platforms), and a Conversions API Gateway with Datahash that Snap is rolling out inside Ads Manager. Snap estimates 1 to 4 hours for a tag-manager setup and 2 to 4 weeks of developer time for a direct one.
When both send the same event, Snap needs to know they’re one event. This is what to ask your developer for:
- A deduplication ID: the same value in the pixel’s client_dedup_id and the Conversions API’s event_id. Snap matches the pair within 48 hours.
- The order ID on purchases: the pixel’s transaction_id and the server event’s order ID, matched for up to 30 days. If both IDs are present, the deduplication ID wins.
- The click ID: Snap adds ScCid to landing page URLs; pass it through to server events, because Snap uses it to match and attribute.
If you don’t set a deduplication ID, the pixel generates its own, which the server can never match. Snap also lists IDs that break deduplication: one hardcoded value for every event, IDs that are too short, and IDs built from timestamps. If GA4 shows duplicates too, see GA4 duplicate purchases.
Snapchat pixel setup checklist
Snap Pixel and Conversions API, ready for launch
- Pixel created in the client’s organization and shared with each ad account.
- Automated Matching turned on.
- One install route per site, with no duplicate tags or apps.
- Standard events fire on the right actions, not the nearest page load.
- PURCHASE fires once per order with price, currency and transaction ID.
- Product IDs on VIEW_CONTENT and ADD_CART match the catalog.
- Staging and test domains don’t fire the production pixel.
- Test Events and the Snap Pixel Helper show the full funnel.
- Conversions API live, sending the same events with a matching deduplication ID.
- Landing URLs keep the ScCid click ID through redirects.
- Event Quality Score Good or Okay on purchase and lead events.
Where this goes wrong
- Two installs. A store app plus a GTM tag doubles purchases. Pick one route.
- Events on the wrong trigger. Add to cart firing on a cart-page view, or checkout firing on a shipping step, both mislead bidding.
- Customer data in the wrong field. An internal user ID sent as an email or phone hurts matching. Send hashed email and phone in their own fields.
- Purchase on reload. Snap says pass PURCHASE only once per page; a refresh of the thank-you page shouldn’t count again.
- Dynamic Ads without a matching catalog. Snap can only match products when the catalog’s IDs are the ones the pixel sends.
To review an existing setup, use the tracking section of our Snapchat ads audit.
Do it faster with Whathead
Whathead is our product.
Through the Snapchat Ads MCP, Claude can read your pixels and their Event Quality Scores and validate a sample event against the Conversions API before you rely on it:
- “List the Snap Pixels on account [name] with the Event Quality Score for each event, and flag any rated Poor.”
- “Validate this sample PURCHASE event for pixel [ID], with value, currency and a deduplication ID. Validate only; don’t send a live event.”
Writes, including live events, come back as dry-run previews first. For server-side delivery, Whathead Signal sends website and lead events to Snapchat’s Conversions API, alongside Meta, TikTok and others, with an event ID on each event for deduplication. Signal is in private pilot, enabled per workspace on request.
Snapchat pixel setup: common questions
How do I set up the Snapchat pixel?
Create it in Ads Manager under Pixels, share it with your ad accounts, install the code directly, through Google Tag Manager or a store integration, map standard events such as PAGE_VIEW, ADD_CART and PURCHASE, and test with Test Events and the Snap Pixel Helper.
Do I need the Snapchat Conversions API as well as the pixel?
Snap recommends it, because server events recover conversions the browser misses. If you run both, send the same deduplication ID from each so Snap counts one event.
How do I test the Snap Pixel?
Use Test Events in Events Manager, which opens your site and shows events in near real time, and the Snap Pixel Helper Chrome extension. Then place a test order and check that one PURCHASE arrives with value and currency.
What is a good Event Quality Score on Snapchat?
Snap rates events Good, Okay or Poor. The score reflects which customer details arrive, deduplication and matching quality, and event volume. Aim for Good on purchase and lead events.
Can I install the Snap Pixel with Google Tag Manager?
Yes. Events Manager has a Google Tag Manager partner integration that signs in with Google and adds the tags to the container and workspace you choose.
Sources
- Snapchat Business Help: installing the pixel, pixel with Google Tag Manager, pixel events and parameters, Conversions API partners, comparing CAPI integrations, CAPI Gateway, pixel deduplication, Snap Pixel Helper, Test Events, viewing Event Quality Score, how EQS is calculated, click ID, WooCommerce, Wix, BigCommerce, sharing a pixel. Checked 19 Nov 2026.
- Snap for Business: Snap Pixel. Snap Marketing API: Conversions API overview, deduplication. Checked 19 Nov 2026.
Written by Ahmed Shahin, founder of Whathead. Last reviewed 19 November 2026.
Check Snap Pixel health from Claude
Read every Snap Pixel’s Event Quality Score and validate test events before your next launch.



