Universal Pixel DebuggerNetworks · Snapchat
Snap Pixel (Snapchat) events and parameters
Updated 2026-09-27
The Snap Pixel is Snapchat's website tag. It reports events such as page views, add to cart and checkout to Snapchat Ads. Current versions of its script send events to tr.snapchat.com/p in JSON batches, where each entry in req[] carries one event in its t object.
Where the events go
| Endpoint | Method | What it carries |
|---|---|---|
tr.snapchat.com/p | POST | A JSON batch. Each tracking entry in req[].t has its own pixel ID (pid) and event name (ev), so one request can carry several events for different pixels. Diagnostics entries can share the batch. |
tr6.snapchat.com/p and other numbered hosts | POST | The same format on a numbered host; 6 of 45 live stores we checked used one. |
tr.snapchat.com/p (supporting) | POST | Batches with only diagnostics, or only SDK entries (i initialization with pixel IDs, log, md). They carry no event. |
Older formats send the same event fields directly as query or form fields on /p. The script loads from sc-static.net/scevent.min.js; a loaded script is setup evidence, not an event.
Event names as sent
The event name is in ev, in each batch entry. The event tag in et is a separate field, not the name. The occurrence ID is in e_client_dedup_id or cdid. The names seen live are upper case with underscores.
| Name as sent | Notes |
|---|---|
PAGE_VIEW | Page view. |
VIEW_CONTENT | Product or content view. Seen live with a value and currency. |
ADD_CART | Add to cart. |
SEARCH | Site search. The term is in e_ss. |
START_CHECKOUT | Checkout started. |
ADD_BILLING | Seen live on a checkout page, after START_CHECKOUT. |
PURCHASE | The standard purchase event (not yet confirmed on a live purchase: we don't place real orders). |
Value, currency, order ID and products
| Field | Key(s) | Notes |
|---|---|---|
| Event value | e_pr (current), e_prc (older) | The event amount. Must be a number. |
| Currency | e_cur (current), e_cr (older) | Kept exactly as sent. |
| Order ID | e_tid | Transaction ID. |
| Occurrence ID | e_client_dedup_id, cdid | Identifies this event, separate from the order ID. |
| Product IDs | e_iids | A JSON array of IDs; older scripts can send a single ID. |
| Number of items | e_ni | A total count, not a quantity per product. |
| Item category | e_ic | Kept separate from the product IDs. |
| Other content fields | e_desc, e_bds, e_cs, e_dm | Description, brands, customer status, delivery method. |
Values sent through Snap's server-side Conversions API do not appear in browser requests, so a browser check cannot see them.
Common problems
- Checking only one pair of keys. Current scripts send
e_prande_cur; older ones sende_prcande_cr. A check that looks for only one pair misses the other. - Missing requests on numbered hosts. 6 of the 45 live stores we checked sent events to
tr6.snapchat.com. A filter for exactlytr.snapchat.commisses them. - Several events in one request. A batch can hold several events and diagnostics entries, each with its own pixel ID. Counting requests is not counting events, and a batch with only diagnostics or SDK entries has no event.
- Variant IDs instead of product IDs. On a live store,
ADD_CARTsent a variant ID ine_iids, while TikTok and Pinterest on the same store sent the parent product ID. Product IDs will not match across networks by themselves. - Item count read as quantity.
e_niis a total for the event. It does not give a quantity for each product.
How to check it with Universal Pixel Debugger
- Open the site and click the Universal Pixel Debugger toolbar icon to open the side panel.
- Find the Snapchat lane on the signal board. It shows the event count and an amber
?for requests with no decoded event, such as diagnostics-only batches. Click the lane to show only Snapchat. - Click an event. Value and currency each show the key they came from, for example "from e_pr", or read Not observed or Invalid. Product IDs from
e_iidsare listed with no invented quantity. - Open the Snapchat parameters checklist: "N of M known fields sent", the sent fields by section, and a Not sent list. Anything else the entry carried is under Other sent fields.
- Check the issues: invalid numeric value or currency, a value, currency or product mismatch when events on several networks share an order ID, and data that differs between destinations.