First, check the pixel helper, test events and the network request
Open the page where the missing event should happen in a clean browser with no content blockers, accept the consent banner, and run three checks side by side. The pixel helper extension shows whether a pixel loaded, which pixel code it carries and which events fired. The test events view in Events Manager, opened for the pixel you expect, shows whether those events reached TikTok from your session. The network log in the browser's developer tools shows the actual requests to TikTok, with their pixel code and event name. If the site uses Tag Manager (GTMTag management system.), run the same journey in preview mode as well, following the debugging and preview tutorial, and note which tags fired at each step.
Read the three results together. No request at all points to the base code, consent or timing. A request with an unexpected pixel code, or a request that arrives in test events but never in the ad account you work in, points to ownership and sharing. A page view that arrives while a specific event does not points to how that event was built or when it fires. This page fixes events that are absent; when events arrive more often than they should, the page on TikTok conversions higher than orders takes over.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Helper finds no pixel on some templates, such as checkout or a subdomain | Helper and network log on each template; live container version | Base code missing from templates, or the container unpublished | Load the base code on every template and publish the container |
| Events reach test events but the ad group cannot select them | Business Center that owns the pixel; ad accounts it is shared to | Pixel created in a personal account and not shared | Move or recreate the pixel in Business Center and share it |
| Page views arrive, value-bearing events never do or carry no value | Pixel setup mode; how each event was defined | Event built in standard mode that cannot read the page | Rebuild the event in developer mode from data layer values |
| Nothing fires after accepting the banner until the next page | Requests before and after consent on the same page | Consent gating with no update after acceptance | Fire on the consent update event as well as later page loads |
| Purchase or form event missing or empty on the confirmation step | Order of data layer pushes and tag firing in preview | Event fired before the data or confirmation exists | Trigger on the push that carries the confirmed data |
Fix, verify and prevent each cause
Base code that never reaches some pages
The base code has to load on every page before any event can fire. It is often missing from the pages that matter most: a checkout on a different template, a booking tool on a subdomain, or a confirmation page served by the shop platform outside the container. In Tag Manager, an edited container that was previewed but never published leaves real visitors on the old version.
Fix: load the base code from one all-pages trigger, add the container to any template or domain that lacks it, and publish, as the pixel and Events API tutorial sets out in its install and check steps.
Verify: the helper shows one pixel on every template of the journey, including confirmation, and the live container version matches the one you edited.
Prevent: list every template and domain that hosts part of the journey and recheck them after each release.
A pixel that belongs to a person, not the business
A pixel created inside an individual's Ads Manager belongs to that login. Events may arrive in its own view, yet the ad account the campaigns run in cannot select them, and when the person leaves, access goes with them. The tutorial's common mistakes call this out directly.
Fix: create or move the pixel into the Business Center that owns the ad accounts and share it with each account that will optimise on it, following the pixel and Events API tutorial. If a new pixel is needed, replace the code on the site in one release.
Verify: in the ad account, a new ad group can select the expected events as its optimisation goal.
Prevent: create all tracking assets in Business Center, and review sharing whenever an ad account is added; the TikTok Business Center setup tutorial puts the pixel, the ad accounts and people's access under the business from the start.
An event the no-code builder cannot see
Standard mode defines events by URL rules or clicked elements, which works for simple page views and fails for anything that needs values or confirmation. A purchase defined as "button clicked" fires on attempts, carries no order value, and disappears when the button's markup changes.
Fix: switch the event to developer mode through the container, reading value, currency and contents from the data layer, as the pixel and Events API tutorial recommends for shops.
Verify: in test events, the event arrives once per completed action with the correct value.
Prevent: do not mix setup modes for the same event, and record in the measurement plan how each event is defined.
Consent that never lets the pixel go
Where consent is required, the pixel should wait for it. The fault is a banner that saves the choice but never signals the container, so the pixel stays silent on the page where the visitor accepted, which is often the landing page from the ad.
Fix: fire the base code and events on the consent update event as well as on later page loads, using the wiring the consent mode guide describes.
Verify: with consent refused, the helper shows no pixel and test events receive nothing; after accepting, the pixel loads on the same page without a reload.
Prevent: test both consent branches after every banner or container change.
An event that runs ahead of its data
Tags read whatever is in the data layer at the moment they fire. If the purchase tag fires on page load and the order details are pushed a moment later, the event goes out empty or not at all; if it fires on a click before the payment is confirmed, it records attempts.
Fix: trigger the event on the data layer push that carries the confirmed order or submission, as the data layer guide explains for timing.
Verify: in preview, the event fires after the push, once, with populated values.
Prevent: make the confirmation push part of the developers' data layer contract and test it in every release that touches checkout or forms.
Prevention: test events before every release
Pixels break when something else ships, so the test belongs in the release. Before a site or container change goes live, walk the key journey in preview with the pixel helper and the test events view open: landing page, product or content view, cart or form, confirmation. Confirm one pixel per page, each planned event once, values present, and nothing sent when consent is refused. After the release, open Events Manager the next day and compare event counts with the previous week; a sudden drop on one event is a break, not a trend. Keep a short register of the pixel code, owner, sharing, events, triggers and consent pattern, as the pixel and Events API tutorial suggests in its final step. Once the browser side is clean, the Events API (Conversions APIServer-side event sharing with Meta.) adds the server route that recovers what blockers remove. The cost per acquisition (CPACost of each conversion.) the campaigns report depends entirely on this routine, and the TikTok measurement hub explains how the events become attributed conversions. When the release is a whole new site, platform or checkout, the website migration tutorial for TikTok ads turns this routine into a plan for the move.
If the browser events are clean but their server copies never reach Events Manager, the diagnosis for missing TikTok Events API events takes over at the server route.
A homeware shop whose purchases stopped arriving
A homeware shop notices that Events Manager has shown no CompletePayment events for nine days, while page views and add-to-cart events continue at about 3,000 and 240 a day. The shop took 186 orders in that period. The pixel helper shows the pixel on product and cart pages but not on the order confirmation page, which a checkout update moved to the payment provider's hosted template. The container is not loaded there. The team adds the confirmation step back inside the shop's own template, which the provider supports, and moves the purchase tag from a page-view trigger to the order-complete data layer push. In test events a test order now shows one CompletePayment with value and currency. Over the next week Events Manager records 151 purchases against 164 shop orders, a gap the team expects from consent refusals and blockers until the Events API is connected.
Common mistakes
Rebuilding tags before checking which pixel code the helper sees. Creating the pixel in a personal login. Defining a purchase by a button click in standard mode. Testing only with consent accepted. Firing the purchase on page load and hoping the data is ready.
