TikTok Pixel Installation: How to Install It, Configure Events, and Confirm It Is Active (2026)

Installing the TikTok Pixel means creating a web data connection in TikTok Events Manager, choosing a partner integration or manual setup, placing the base code on your site, configuring the events you care about, and then confirming the pixel is active. TikTok gives you three ways to confirm: Pixel Helper, Test Events, and the Diagnostics tab.

This guide follows TikTok's own Business Help Center articles on TikTok Pixel, setting up and verifying a web data connection, the Event Builder, standard events and parameters, web diagnostics and event deduplication, as published in September 2026. The pixel is one part of account setup rather than a later add-on; for the order everything else goes in, see our TikTok ads account setup guide.

What installing the TikTok Pixel actually involves

TikTok describes the pixel as a piece of code you place on your website that lets you share website events with TikTok. Once it is set up and verified, it reports when a visitor takes an action you have defined — viewing a product page, adding to cart, registering, purchasing.

Four things have to be true before the pixel is doing anything useful:

1. A web data connection exists in Events Manager and has a pixel attached to it.
2. The base code is present on the pages that matter, or a partner platform is sending the data for you.
3. The events you optimize for are configured, with the parameters those events need.
4. Events are actually arriving, which you have checked rather than assumed.

Most of the "my pixel is not working" cases are the third and fourth items. Installed code that never fires looks identical to healthy code when you only inspect the page source.

Step 1: Create the data connection in Events Manager

TikTok's setup article gives this path:

1. Log in to TikTok Ads Manager and go to Tools.
2. Open Events Manager. (TikTok's own articles label this entry point both as Events and as Events Manager; both lead to the same place.)
3. Click Connect Data Source.
4. Select Web.
5. Enter your URL.
6. Choose Partner Integration or Manual Setup as the connection method.

Two things are decided here. The URL you enter is the site this connection belongs to. The connection method decides whether you will be editing your site's code at all.

Step 2: Partner integration or manual setup

Partner integration. TikTok maintains a list of merchant, website and data platforms that can set up the pixel and the Events API for you, and says these integrations often require no edits to your site's code. The merchant and website platform list includes Shopify, WooCommerce, Wix, WordPress, BigCommerce, PrestaShop, OpenCart, Adobe Commerce, SHOPLINE, VTEX, Cafe24 and others; Google Tag Manager appears in the partner setup flow as well. Which products each partner supports differs — some carry Pixel only, some Pixel and Events API — so check the row for your platform before assuming server-side is included.

The flow is: pick your partner, create and name the pixel, then follow the partner's steps. TikTok recommends naming the pixel after your website or domain, with a maximum of 128 characters including spaces. That naming advice matters more than it sounds once an account holds several datasets.

Manual setup. Pick your manual connection method, create and name the pixel, install the base code on your website, manage the configuration settings, and then configure the events. TikTok's Event Builder exists for this last part: it analyzes your page's button text and elements, suggests standard events and parameters, and lets you add events by selecting buttons or URL keywords — without writing code. You can still set events in code if you prefer, and TikTok publishes developer documentation for that route.

Step 3: Configure the events you will optimize for

Events are the actions; parameters are the details attached to them. TikTok's standard events are predefined names it recognizes for reporting, conversion optimization and audience building, supported across both the pixel and the Events API. The list includes View Content, Add to Cart, Add to Wishlist, Add Payment Info, Initiate Checkout, Purchase, Complete Registration, Submit Form, Submit Application, Subscribe, Start Trial, Search, Contact, Schedule, Download, Find Location, Customize Product and Application Approval. Each maps to an event code, such as ViewContent, AddToCart or Purchase.

Parameters are where campaigns usually gain or lose ground. TikTok's parameter documentation marks several as conditionally required rather than optional:

• content_type, contents and content_ids are required for Video Shopping Ads.
• value is required for ROAS and value-based optimization; price is the price of a single item while value is the order total.
• currency is required for ROAS and must be an ISO currency code from TikTok's supported list.

An illustration of what an Add to Cart event carries, using field names exactly as TikTok documents them:

{
  "content_type": "product",
  "content_ids": ["SKU-1024"],
  "content_name": "Merino crew sweater",
  "quantity": 1,
  "price": 59.0,
  "value": 59.0,
  "currency": "USD"
}

TikTok recommends setting up events across the whole user journey rather than only the final conversion, because the earlier events are what the system uses to find the people likely to reach the later ones.

One constraint from TikTok's own documentation: avoid sending sensitive visitor data in events, and keep event labels compliant with TikTok's advertising policies, anti-discrimination policy, and housing, employment and credit policy. TikTok says non-compliant event names may be removed.

Step 4: Confirm the pixel is active

This is what most people mean by "activating" the pixel — not a switch you flip, but evidence that events are arriving. TikTok gives three checks:

Pixel Helper. A Chrome extension, available from the Chrome Web Store. TikTok recommends using it to view the data being sent, both to check for errors and to confirm you are not sending anything that data-sharing policies would treat as sensitive.

Test Events. A tab in Events Manager with a live test environment that mimics how your site appears in the TikTok app. You open your site in the browser directly — no QR code needed — take an action, and the test event activity section shows the events that action produced. You can filter between browser and server test events, which is how you tell which path a given event came in on.

Diagnostics. A tab in Events Manager, reachable from the home page for all pixels or from an individual pixel. Each diagnostic card shows the issue, its severity, the affected dataset and the ads impacted, with an action item to resolve it — for example, an issue saying first-party cookies are not enabled for a pixel comes with the button to enable them. Clicking Learn more gives impact details, fix instructions and sample data from recent affected events.

Alongside these, the Overview tab for a data connection carries the reading that answers "is this pixel live":

• Event Status — Active means an event was shared with TikTok in the last 7 days; No recent activity means it has not been in the last 7 days.
• Last Received — the most recent hour TikTok received the event. TikTok notes event data is not real-time and there can be latency between the trigger and the dashboard, so an event you just fired may not appear immediately.
• Connection Method — browser only, server only, or server and browser.
• EMQ Score — Event Match Quality, a weighted average of your match key coverage.

When the pixel is installed but nothing arrives

Work down this order rather than reinstalling:

1. Check Event Status and Last Received on the Overview tab. If the status flipped to No recent activity, the question is what changed on the site, not whether the pixel exists.
2. Trigger the event yourself and watch Test Events, filtered to the browser path. Nothing arriving here means the event is not firing on that page.
3. Read the Diagnostics tab before theorizing. Missing parameter data and missing content IDs are the examples TikTok names, and both are fixed in configuration rather than in code.
4. Allow for latency before concluding an event is missing.

A theme partner integration is worth confirming separately: the integration can be connected at the platform level while a specific template or a custom checkout never fires the event, and the platform side will still report the connection as healthy.

Pixel plus Events API, and why deduplication matters

TikTok recommends setting up the pixel and the Events API together, and says a pixel or Events API setup is a prerequisite for the Web Conversions objective in Ads Manager. The Events API sends events from your server, which recovers conversions the browser path loses to connectivity issues and browser behavior.

Running both means the same conversion can arrive twice, so deduplication becomes a requirement rather than a refinement:

• You must send event_id as a parameter on both paths. That shared ID is what lets TikTok recognize two copies of one conversion.
• Deduplication is only needed where the events overlap. Sending Add to Cart via the pixel and Purchase via the Events API needs no deduplication; sending Purchase on both does.
• The windows TikTok documents: duplicates within the pixel, and duplicates within the Events API, are deduplicated when the identical event and event_id arrive within 48 hours of the first. Across the pixel and the Events API, TikTok merges or deduplicates events with an identical event and event_id arriving after 5 minutes and within 48 hours of the first.

TikTok also asks that the events and parameters you share stay consistent across both paths, and that relevant match keys are passed back to improve match rates.

What not to do

Three patterns that circulate in advertiser groups and are worth naming as the wrong answer:

• Firing events that did not happen. Sending conversion events the visitor never triggered corrupts the optimization you are paying for, and TikTok treats submitting false or misleading information to get around review as prohibited conduct that can lead to enforcement on the account.
• Putting identifying or sensitive data into event parameters. TikTok's guidance is the opposite direction: avoid sending sensitive data about visitors, and use Pixel Helper to inspect what you are actually sending.
• Stacking duplicate pixels to work around a problem. Multiple datasets receiving the same traffic make the readings harder to interpret, and none of the three checks above will tell you which one your campaign is optimizing against. Fix the connection you have.

If the account itself is not approved yet, none of this is the blocker — see TikTok ads account requirements for what TikTok checks before approval. And because reporting and scheduling sync to the ad account's time zone, the timestamps you compare against your own analytics depend on it; ad account time zone covers what that setting controls.

Where AdBegin fits

Teams running several brands or markets end up with several datasets, several people who can edit them, and several environments those edits are made from. AdBegin is an ad workspace that keeps accounts, access and working environments organized as one set. It does not install pixels for you and has no role in what TikTok records or reports.

FAQ

How do I install the TikTok Pixel on my website?

In TikTok Ads Manager, go to Tools, open Events Manager, click Connect Data Source, select Web, enter your URL, and choose Partner Integration or Manual Setup. Partner integrations often need no code changes; manual setup means creating and naming the pixel, installing the base code on your site, and configuring the events.

How do I know if my TikTok Pixel is active?

Check Event Status on the data connection's Overview tab: Active means an event was shared with TikTok in the last 7 days. For a live check, trigger the event and watch the Test Events tab, or install Pixel Helper from the Chrome Web Store to see what is being sent.

Why is my TikTok Pixel installed but not receiving events?

Most often the events are not configured or are not firing on the pages you assumed, rather than the base code being absent. Use Test Events to see whether the action produces an event, and read the Diagnostics tab — TikTok names missing parameter data and missing content IDs as typical issues. Also allow for reporting latency.

Do I need the Events API as well as the pixel?

Not to start, but TikTok recommends both together for web conversions, and says a pixel or Events API setup is a prerequisite for the Web Conversions objective. If you run both and send the same events on both paths, you must pass event_id on each so TikTok can deduplicate them.

Can I set up TikTok Pixel events without writing code?

Yes. The Event Builder analyzes your page's button text and elements, suggests standard events and parameters, and lets you add events by selecting buttons or URL keywords. Partner integrations with platforms such as Shopify, WooCommerce and Wix also set events up without code edits.

The short version

Installing the TikTok Pixel is four steps: create the web data connection in Events Manager, choose partner integration or manual setup, configure the standard events and their required parameters, and verify. Verification is the step that decides whether any of it counts — use Pixel Helper, Test Events and Diagnostics, and read Event Status and Last Received on the Overview tab. Add the Events API alongside the pixel for web conversions, and pass event_id on both paths so the same conversion is counted once.