Какие теги ищет сканер?
Meta Pixel, TikTok Pixel и Google Tag Manager.
Pixel Scanner
Проверяйте, что теги Meta, TikTok и Google срабатывают на любом лендинге.
Используйте Pixel Scanner для быстрой QA-проверки лендинга, чтобы подтвердить наличие тегов Meta, TikTok или Google, либо проверить, не ломают ли редиректы browser-side tracking до загрузки финальной страницы.
What to do after the scan
The browser-side result is only the first proof point. Keep one minimum evidence set together: redirect trace, final landing URL, click-ID state, browser-side tag proof, the scope limits of that proof, and the matching Meta server response. If the conversion later depends on a hosted form, thank-you page, or upsell step, keep that page context in the same packet too. The next steps below keep those artifacts tied to one test path and one owner handoff instead of repeating the scan in isolation. A strong recovery pass should end with one explicit next route into the knowledge-base hub, the fix library, or the exact Meta payload lane.
Confirm the final URL first
Trace the real redirect chain before you blame the page when smartlinks, HTTPS rewrites, or partner hops may be sending traffic somewhere else.
Check the landing-page identifiers
Use the same resolved URL to confirm fbclid, gclid, ttclid, or partner IDs still coexist with the browser-side tags you just validated.
Keep the proof packet inside the tools hub
Open the broader routing hub when the scan already proved the page-side state but you still need the neighboring redirect, click-ID, postback, or repair branch without restarting the investigation.
Что делает этот инструмент?
Pixel Scanner проходит лендинг, загружает скрипты и проверяет, запускаются ли маркетинговые пиксели.
Keep one browser-versus-server evidence pack
Pixel issues usually stay unresolved because each owner reviews a different artifact. Keep one compact proof set tied to the same landing-page session or replay so the handoff from Pixel Scanner into Facebook CAPI Test, Click ID Extractor, or the fix library stays decisive.
- The original campaign or tracker URL plus the Redirect Checker trace that proves which landing page users actually reached.
- The exact final landing URL you scanned so browser-side tag proof and downstream Meta payload tests refer to the same page variant.
- One note on whether the conversion later moved into a hosted form, modal, iframe, thank-you page, or upsell step so the team knows if the entry-page scan and the conversion-step proof belong to different URLs.
- A Click ID Extractor snapshot showing whether fbclid, gclid, or other identifiers survived on that same final URL.
- One note about consent, GEO, device, or template conditions when different visitors can receive different browser-side tag states.
FAQ
FAQ по Pixel Scanner
Проверяйте наличие пикселей.
Нужен ли браузерный плагин?
Нет, достаточно вставить URL — сканер анализирует HTML на сервере.
Покажет ли отсутствующий пиксель?
Если скрипт отсутствует в исходном коде, инструмент подсветит проблему.
Безопасно ли проверять рабочие лендинги?
Да, запросы только читают страницу и не отправляют события.
Следующий шаг