> ## Documentation Index > Fetch the complete documentation index at: https://www.referly.so/docs/llms.txt > Use this file to discover all available pages before exploring further. # Snapchat Ads pixel > Send your store's events to Snapchat through the Conversions API with Referly Atlas. Find your Snap Pixel ID and API token, add the pixel in Atlas, and verify that events arrive. Includes the 24 hour wait for a new token. Referly Atlas sends your store's events to Snapchat from its servers, through Snapchat's Conversions API. Page views, product views, carts, checkouts and purchases reach your Snap Pixel without depending on the visitor's browser, with customer details hashed before they leave. This guide walks you through finding the two values Snapchat asks for, adding the pixel in Atlas, and checking that events arrive. ## Before you start You need: * **A store in Atlas that is set up and live.** Only stores that are Running or Awaiting data send events. See [Store statuses](/docs/help-center/atlas/statuses.md#store-statuses). * **A Snap Pixel in Events Manager.** Atlas sends to a pixel you already have, it does not create one. * **The Organization Admin role in Snapchat Ads Manager**, because only an Organization Admin can generate a Conversions API token. * **Up to 24 hours of patience for a brand new token.** Snapchat can answer **Invalid access token** for up to a day after a token is created, even when everything is right. Create the token first, then add the pixel. If this is your first pixel, read [Pixels and destinations](/docs/help-center/atlas/pixels.md) first: it explains what a pixel is in Atlas and what every pixel row shows. ## Step 1: Find your Pixel ID **1. Open Events Manager** In Snapchat **Ads Manager**, open the menu, then **Events Manager**. **2. Open your pixel** Select the pixel you advertise with. **3. Copy the Pixel ID** Copy the **Pixel ID** shown under the pixel's name. It is a UUID like `a72aa7aa-aa7a-7aa-aa7a-a7a7777777a7`. Snapchat's own article: [Conversions API](https://businesshelp.snapchat.com/s/article/conversions-api). The same steps sit in the **Where to find it** tooltip beside the field in Atlas, and the **How to find it** link under the field opens Snapchat's article. ## Step 2: Generate an API token **1. Open Business Details** In Snapchat **Ads Manager**, open the menu, then **Business Details**. **2. Go to Conversions API Tokens** Open **Conversions API Tokens**. **3. Generate the token** Select **Generate Token** (you need the Organization Admin role) and copy it. Snapchat's own article: [Conversions API: get started, access token](https://developers.snap.com/api/marketing-api/Conversions-API/GetStarted#access-token). ## Step 3: Add the pixel in Atlas **1. Open Pixels and destinations** In the left sidebar of Atlas, open **Pixels and destinations** for the store, then select **+ Add pixel**. **2. Choose Snapchat** In the **Add your tracking pixel** dialog, select the **Snapchat** chip. Leave **Method** on **Add a new pixel**. If another store of your business already sends to this pixel, choose **Use an existing pixel** instead and Atlas copies its ids and keys to this store. See [Use an existing pixel](/docs/help-center/atlas/pixels.md#use-an-existing-pixel). **3. Paste the two values** Fill in **Pixel ID** and **API token**. Under the token field Atlas repeats the notice that a new token can take up to 24 hours to start working. **Name (optional)** helps you tell pixels apart when a store sends to more than one Snap Pixel. **4. Choose the events to send** Under **Events sent**, keep or change the events Atlas pre-selected for your business type. Every event in the table below is available. See [Default events by business type](/docs/help-center/atlas/events.md#default-events-by-business-type). **5. Save** Select **Add pixel**. Atlas shows the **Pixel saved** screen with a **Data flowing** badge. ![Add pixel dialog with Snapchat selected, showing the Pixel ID and API token fields and the 24 hour token notice](https://mintcdn.com/pushlapgrowth/oT87nrz5crwfmm9Y/images/atlas/pixels/pixels-snapchat--add-pixel-dialog.png?fit=max\&auto=format\&n=oT87nrz5crwfmm9Y\&q=85\&s=f9d107281562153604f97cf91d0334c3) On the **Pixel saved** screen, use **You can verify that here** to send a test event straight away. Atlas answers **Test event accepted** with the HTTP status Snapchat returned, or shows Snapchat's own error message. With a token created in the last 24 hours, expect **Invalid access token** until Snapchat activates it. ## Events Atlas sends to Snapchat | Atlas event | What Snapchat calls it | | - | - | | Page view | PAGE\_VIEW | | View content | VIEW\_CONTENT | | Add to cart | ADD\_CART | | Initiate checkout | START\_CHECKOUT | | Add payment info | ADD\_BILLING | | Purchase | PURCHASE | | Search | SEARCH | | Sign up | SIGN\_UP | | Start trial | START\_TRIAL | | Subscribe | SUBSCRIBE | Snapchat has no standard lead event, so Lead is not sent to Snapchat. Sign ups, trials and subscriptions map one to one. Only the events ticked under **Events sent** are forwarded. Orders and conversions are always evaluated; the browser events (page views, product views, carts, checkouts, payment info, searches) are forwarded only when a pixel wants them. ## Verify that events arrive 1. **Send a test event.** On the pixel row, open the row's menu and choose **Send test event**. A toast confirms that Snapchat accepted the event, or shows Snapchat's error. Test events time out after 10 seconds. 2. **Read the delivery line.** The line under the pixel reads how many events reached Snapchat in the last 24 hours, for example **8 sent in 24 h**, or **8 sent, 2 failed in 24 h** when some were rejected. A green dot means **Live**: events are being sent. See [Pixel states](/docs/help-center/atlas/statuses.md#pixel-states). 3. **Watch Live activity.** Open **Live activity** in the left sidebar and filter by destination to see each event's status and Snapchat's response. See [Live activity](/docs/help-center/atlas/reports/live-activity.md). ![More pixel actions menu on a pixel row with Send test event and Event filters](https://mintcdn.com/pushlapgrowth/oT87nrz5crwfmm9Y/images/atlas/pixels/pixels--row-menu.png?fit=max\&auto=format\&n=oT87nrz5crwfmm9Y\&q=85\&s=95d7b2e4b5deb3b3c88c9e73b0ed6663) ## Snapchat settings in Atlas Snapchat pixels have no extra settings in Atlas. The one thing to plan for is the token: * **A new token can take up to 24 hours to start working.** Until then Snapchat answers **Invalid access token**, even when the token and the Pixel ID are right. Atlas keeps retrying failed sends (8 attempts, spaced out from 10 seconds), but events that fail all attempts in that window show as **Failed** and are not sent again. If you can, create the token a day before you add the pixel. * **Replace a token without losing anything else.** Select **Edit** on the pixel row and paste the new token into **API token**. A blank field keeps the saved token. ## Troubleshooting > **The test event fails** > > Atlas shows Snapchat's error next to the test. Check the Pixel ID first, then the token: Atlas never shows a saved token again, so select **Edit** on the row and paste a fresh one (a blank field keeps the saved value). Test events time out after 10 seconds, so a slow answer also counts as a failure: try once more. > **The row says No events in the last 24 h** > > Atlas sends only from stores that are Running or Awaiting data, only the events ticked under **Events sent**, and never test-mode orders. Check that the platform switch at the top of the Snapchat row is on, then open **Live activity** and read the Status column: **Skipped** means no consent or no identifiers Snapchat can match, **Filtered** means an event filter stopped it, **Deduped** means the same event was already sent within 48 hours. See [Delivery statuses](/docs/help-center/atlas/statuses.md#delivery-statuses). > **Snapchat answers Invalid access token** > > If you generated the token less than 24 hours ago, wait: Snapchat activates new tokens with a delay, and the token and Pixel ID are most likely fine. If it is older than a day, generate a new token under **Conversions API Tokens** in **Business Details** (Organization Admin role), select **Edit** on the pixel row and paste it in. ## Related > **[Pixels and destinations](/docs/help-center/atlas/pixels.md)** > > Add, edit, test and detach pixels on any store. > **[Events](/docs/help-center/atlas/events.md)** > > What each event means and which platform calls it what. > **[Consent and privacy](/docs/help-center/atlas/pixels/consent-and-privacy.md)** > > What is hashed before it leaves and what consent Atlas needs. > **[Live activity](/docs/help-center/atlas/reports/live-activity.md)** > > Watch every event and Snapchat's response as they happen. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.