Loading tutorials…
Loading tutorials…
Pixel was working last week, today Events Manager shows zero events. Or it never fired at all. Either way, this is the diagnostic sequence specialists run — in order — to find the issue in under an hour.
Who this is forAnyone whose TikTok Pixel was working and stopped, or who installed it and never saw events. The fix is rarely complicated once you find the right culprit. Most DIY operators spend 4-8 hours hunting; the diagnostic flow below is 60-90 minutes.
What you'll need
Step 1
Pinpoint exactly what is broken. 'Pixel not firing' can mean 4 different things, each with different fixes.
Open Pixel Helper extension on your site. What does it show?
Case A — Pixel Helper icon is GRAY (no pixel detected): the base pixel is not loading at all. Check installation.
Case B — Icon is GREEN but shows "PageView only, no events": base pixel works, standard events not configured.
Case C — Icon shows GREEN with events firing, but Events Manager dashboard shows zero counts: pixel fires but TikTok is not receiving (rare — usually a recent platform issue).
Case D — Pixel Helper shows errors in RED: specific event misconfiguration. Click each to see the error.
Identify which case you are in BEFORE trying fixes. Diagnostic order matters.
Step 2
Pixel Helper gray. Most common causes: code not deployed, wrong Pixel ID, blocked by ad blocker, or installed in <body>.
View page source (right-click → View Page Source). Search for "ttq.load" or your Pixel ID.
If NOT present: code was not deployed. Re-paste the pixel code in your <head> via your CMS or GTM. Test again.
If present but in <body>: move to <head>. The script must load before page content for reliable firing.
Disable ad blockers in your test browser (uBlock, AdBlock Plus, Ghostery) — they sometimes block pixel domains. If the pixel works without blockers, that confirms the cause.
Verify the Pixel ID in your code matches the one in Events Manager. Wrong ID = pixel fires but to the wrong destination.
Check GTM (if used): is the TikTok pixel tag PUBLISHED? Many users save changes but forget to publish.
Step 3
PageView fires, but ViewContent, AddToCart, Purchase do not. Cause: standard events not configured separately.
TikTok base pixel auto-fires PageView only. Every other event (ViewContent, AddToCart, etc.) must be configured.
In Events Manager → your Pixel → "Web Event Settings" → check which events are detected.
For Shopify users with the official app: re-open app settings, ensure each standard event is toggled ON, save.
For GTM users: check that you have a separate tag per event, each with the right trigger (e.g., AddToCart tag fires on data layer event "ecommerce.add" or button click).
For manual install: add the event-specific code snippets in the appropriate page templates. For Purchase, this is the thank-you/confirmation page.
Validate each event by walking through the funnel with Pixel Helper open.
Step 4
Rare but real. Most common: pixel firing to wrong ID, Events Manager date filter, or TikTok platform issue.
In Events Manager, check the date filter at the top. Make sure it includes "today" or the time window you tested in.
Verify the Pixel ID in your site code matches the pixel you are viewing in Events Manager. Test: copy the ID from your code, search for it in Business Center → Assets → Events.
Check TikTok platform status: status.bytedance.com or downdetector.com. Platform-wide pixel issues happen rarely (maybe 2-3x per year) but can last 1-6 hours.
If you recently changed the Pixel ID in code but Events Manager is still showing the old pixel: refresh the page, clear cache, log out and back in.
If still zero after 24 hours: contact TikTok support via Business Center. Reach out via the Help center (top right) → "Contact us."
Step 5
Helper shows specific errors per event. Common: missing parameters, wrong data types, duplicate firing.
Click the red error indicator in Pixel Helper to see the specific error message.
Common error: "Missing required parameter." Usually content_id, value, or currency missing on a commerce event. Add the field to your code or GTM tag.
Common error: "Invalid data type." Often value passed as a string ("19.99") instead of number (19.99). Fix the code or data layer.
Common error: "Duplicate event detected." You are firing the event twice from two sources (e.g., Shopify app + GTM tag). Disable one source.
Common error: "Event fired without consent." Cookie consent banner is blocking the pixel. Update consent flow to allow tracking after explicit consent (or configure TikTok Consent Mode).
Step 6
Don't trust 'Pixel Helper shows green' alone. Walk a real funnel end-to-end and validate in Events Manager within 24 hours.
Open your site in a fresh incognito session (clean cookies).
Walk: home → category → product (ViewContent) → AddToCart → checkout (InitiateCheckout) → buy (CompletePayment).
After each step, verify Pixel Helper shows the expected event.
After completing the purchase, check Events Manager → "Test Events" tab — events should appear in real time.
After 24 hours, check Events Manager → "Overview" → event counts should be non-zero and increasing.
Step 7
Pixel breakages happen — site code changes, plugins update, ad blockers evolve. Set up alerts.
Events Manager → your Pixel → Settings → "Notifications" → enable email alerts for "Significant drop in event volume."
Set a weekly calendar reminder to spot-check event counts in Events Manager. 5 minutes per week catches issues that compound into 30 days of lost data.
If you have monitoring infrastructure (Datadog, Better Stack, Pingdom), add a synthetic test that walks a critical funnel daily and confirms events fire.
Document the diagnostic steps from this tutorial in your team's runbook so the next person (or future you) finds the issue in 60 min instead of 6 hours.
Common mistakes
Assuming Pixel Helper green = all events working
What goes wrong: Pixel Helper shows the base pixel firing. You launch campaigns. 5 days later you realize Purchase events were never firing because Helper does not validate every event automatically. $1,000-3,000 of wasted ad spend on broken optimization data.
How to avoid: Manually walk the full funnel after every install or major site change. Confirm EVERY event in Pixel Helper, not just PageView. 10 minutes of validation prevents weeks of bad data.
GTM tag saved but not published
What goes wrong: You configured the GTM tag carefully. You closed the tab. You did not click 'Publish.' The tag never went live. You think the pixel is installed; in reality nothing fires on the actual site.
How to avoid: After every GTM change: click the blue 'Submit' button → name the version → click 'Publish.' Then verify on the live site with Pixel Helper.
Wrong Pixel ID in code
What goes wrong: You installed a pixel from a previous account or test pixel. Events fire perfectly — but to a pixel you do not even use. Your real campaigns see zero data. Smart+ has nothing to optimize.
How to avoid: Always copy Pixel ID directly from the Events Manager UI of the pixel you intend to use. Paste into code. Verify by checking page source on your site and comparing to Events Manager.
Ignoring consent mode
What goes wrong: Cookie consent banner blocks tracking until user clicks accept. Many users do not click. You lose 30-70% of events depending on geography (EU especially harsh). Reported conversions drop accordingly.
How to avoid: Implement TikTok Consent Mode v2. Tracking fires in limited mode by default, then upgrades to full tracking after consent. Recovers 20-40% of EU traffic lost to strict consent banners.
Double-firing from two install sources
What goes wrong: Shopify TikTok app fires Purchase. GTM TikTok tag also fires Purchase on the same event. Conversion count doubles silently. Reported CPA looks half of reality. Smart+ optimizes to inflated targets, bids climb.
How to avoid: Pick ONE source per event. If using Shopify app, disable GTM Purchase tag (or vice versa). Test in Pixel Helper — if you see the same event twice in the same page load, you have double-firing.
Not validating after site code changes
What goes wrong: Engineering deploys a site update. The pixel breaks silently (CSS conflict, plugin update, theme change). You discover it 14-21 days later when ad performance tanks. Easy 3-week recovery.
How to avoid: Add 'verify TikTok Pixel on Pixel Helper' to your site-deploy checklist. 2-minute check after every release. Compounds into months of saved data over a year.
Recap
Done — what's next
How to install the TikTok Pixel (direct and via GTM)
Read the next tutorial
Hand it off
Pixel debugging is the kind of work that takes 6 hours when you do it yourself and 60 minutes when a specialist does it. EverestX TikTok Ads specialists who have audited 50+ pixel installs typically charge $30-60 for a 1-hour audit + fix. Cheap insurance against weeks of lost optimization data.
Get a same-day audit
Real-time view ("Test Events" tab): within 60 seconds. Main dashboard: usually 30 minutes to 2 hours. Full match quality data: 24-48 hours. If you see nothing after 24 hours of validated firing, contact TikTok support.
Pixel Helper shows what fires from YOUR browser. Events Manager aggregates across all users. If you blocked the pixel from your browser at some point (cookies, opt-out), Helper might be biased. Test in incognito + a colleague's browser to get a clean view.
Most common: (1) recent site deploy broke the pixel code, (2) plugin update changed how events fire, (3) you updated cookie consent banner, (4) someone disabled a GTM tag, (5) ad blocker extension updated to block TikTok's pixel domain. Audit each in order — usually one of these.
Yes — for example, one pixel for US ads and one for EU ads. Each fires independently. But avoid multiple pixels by accident — if you have a test pixel still firing alongside your production pixel, you will double-count data in the test pixel.
Yes, but requires extra configuration. Standard PageView fires on initial load. For route changes within the SPA, you must manually fire ttq.page() or ttq.track("PageView") on each route change. Same for events. Without this, SPAs report only the entry page.
Use VPN to test from EU. Verify Consent Mode behavior: pixel should fire in limited mode before consent, full mode after. If you do not see ANY pixel activity pre-consent, your Consent Mode is configured too aggressively.
TikTok Ads
TikTok Pixel installs in 10 minutes if you know what you are doing, or 6 hours if you don't. The difference is whether you validate it correctly in Events Manager before launching campaigns. This walks through both paths.
TikTok Ads
iOS 14+ and ITP strip 20-40% of pixel events. Events API is how you get that data back. This walks through the partner-integration path (Shopify, Segment) AND the direct API path for custom stacks — plus the deduplication settings that prevent double-counting.
TikTok Ads
TikTok Ads Manager is structurally different from Meta or Google. Get the Business Center hierarchy wrong on day one and you will be untangling it 3 months later. This walks through the right setup order.
TikTok Ads
TikTok rewards creative velocity more than any other platform — and that is exactly what most founders cannot maintain solo. This is the honest framework: when the cost of self-managing TikTok exceeds the cost of hiring, and how to tell which side you are on.