> ## 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. # TikTok Ads pixel > Send your store's events to TikTok through the Events API with Referly Atlas. Find your TikTok Pixel ID and access token, add the pixel in Atlas, and verify that events arrive in TikTok Events Manager. Referly Atlas sends your store's events to TikTok from its servers, through TikTok's Events API. Page views, product views, carts, checkouts and purchases reach your TikTok pixel without depending on the visitor's browser, with customer details hashed before they leave. This guide walks you through finding the two values TikTok asks for, adding the pixel in Atlas, and checking that events arrive in Events Manager. ## 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 TikTok pixel in Events Manager.** Atlas sends to a pixel you already have, it does not create one. * **Access to that pixel's settings** in TikTok Ads Manager, so you can generate an Events API access token. 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 your data sources** In TikTok **Ads Manager**, go to **Tools**, then **Events**, then **Data sources**. **2. Open the pixel** Select the pixel you advertise with. **3. Copy the Pixel ID** Copy the **Pixel ID**. It is a string of letters and numbers like `CG7A7AAA77A77AA2AAA`. TikTok's own article: [How to create and access your TikTok Pixel ID](https://ads.tiktok.com/help/article/how-to-create-and-access-tiktok-pixel-id). 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 TikTok's article. ## Step 2: Create an access token The access token lets Atlas send events to your pixel through the Events API. **1. Open the pixel settings** In **Events Manager**, select your pixel, then **Settings**. **2. Go to the Events API section** Open **Events API**. **3. Generate the token** Select **Generate Access Token** and copy it. A token lapses after 90 days without use, so generate a fresh one if your pixel has been idle. TikTok's own article: [Events API](https://business-api.tiktok.com/portal/docs?id=1771100865818625). ## 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 TikTok** In the **Add your tracking pixel** dialog, select the **TikTok** 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 **Access token**. **Name (optional)** helps you tell pixels apart when a store sends to more than one TikTok 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 TikTok selected, showing the Pixel ID and Access token fields](https://mintcdn.com/pushlapgrowth/oT87nrz5crwfmm9Y/images/atlas/pixels/pixels-tiktok--add-pixel-dialog.png?fit=max\&auto=format\&n=oT87nrz5crwfmm9Y\&q=85\&s=fd4d7711568045fdc28354f0da00e5ce) 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 TikTok returned, or shows TikTok's own error message so you can correct the ID or token. ## Events Atlas sends to TikTok TikTok accepts every event Atlas tracks. Note that TikTok's name for a purchase is CompletePayment. | Atlas event | What TikTok calls it | | - | - | | Page view | Pageview | | View content | ViewContent | | Add to cart | AddToCart | | Initiate checkout | InitiateCheckout | | Add payment info | AddPaymentInfo | | Purchase | CompletePayment | | Search | Search | | Lead | Lead | | Sign up | CompleteRegistration | | Start trial | StartTrial | | Subscribe | Subscribe | 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 TikTok accepted the event, or shows TikTok's error. Test events time out after 10 seconds. 2. **Read the delivery line.** The line under the pixel reads how many events reached TikTok 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 TikTok's response. See [Live activity](/docs/help-center/atlas/reports/live-activity.md). 4. **Check Events Manager.** In TikTok's [Events Manager](https://ads.tiktok.com/i18n/events_manager), open your pixel and look for the events Atlas sent. ![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) ## Troubleshooting > **The test event fails** > > Atlas shows TikTok'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 TikTok row is on, then open **Live activity** and read the Status column: **Skipped** means no consent or no identifiers TikTok 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). > **Events were flowing, then every send started failing** > > A TikTok access token lapses after 90 days without use. Generate a new one under **Events API** in the pixel's settings, select **Edit** on the pixel row in Atlas, paste it into **Access token** and save. The row goes back to **Live** once the next event is accepted. ## 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. > **[UTM tagging](/docs/help-center/atlas/reports/utm-tagging.md)** > > The TikTok tracking template that fills Reporting. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.