🎯Pixel Scanner

Final destination unclear

Prove the real landing page before you scan it again

Start with redirect evidence when trackers, shorteners, smartlinks, or HTTPS upgrades might be sending buyers to a different page than the one you intended to test.

Browser tag missing

Inspect the landing-page build and scripts

Move here when the browser-side tag is absent and you need page-level proof about script loading, asset delivery, or template-specific rendering on the final URL.

Pixel visible but attribution still off

Compare Pixel vs CAPI instead of guessing

Use the Meta comparison workflow when browser-side tags exist but match quality, deduplication, or conversion credit still looks wrong in Events Manager or downstream reports.

Multi-system disagreement

Escalate when redirects, tags, and server events conflict

Open the broader audit path when the page scan, click-ID proof, and server-side Meta evidence point to different owners and you need one coordinated diagnosis packet tied to a single landing-page session.

Browser tag absent

The final page loads but the tag never appears

Move into landing-page inspection when the redirect path is correct but the rendered page, GTM container, or consent flow still hides the browser-side tracking code.

Identifier mismatch

The pixel exists but click IDs do not survive on the page

Check the final landing URL for fbclid, gclid, ttclid, or partner IDs before you blame Meta event quality. If the identifier is missing in the browser, server-side recovery will not fix attribution.

Browser vs server drift

The page looks healthy but Meta still undercounts conversions

Use the comparison workflow when browser-side tags exist yet deduplication, match quality, or event volume still diverge between the landing page and Events Manager.

Meta rejects the payload

The browser proof is clean but the server-side event still fails

Escalate here when Meta receives or validates the wrong payload after a healthy browser-side scan. This is the lane for payload structure, hashing, event_id, or trust issues, not for another page scan.

Landing-page proof gap

The page loads the pixel but the session still lacks reusable identifiers

Go here when the browser-side tag is visible yet the final landing URL still drops fbclid, gclid, or other identifiers before any form submit or server replay. Match quality will stay weak until the landing session keeps the same IDs that your server event expects.

Server payload gap

The page keeps IDs but the server event still lacks match keys

Replay the same landing-page context through Meta's server-side path when browser proof looks clean but customer_data, external_id, hashed email, phone, or event_source_url still look thin or inconsistent in the payload you send.

Accepted but weak

Meta accepts the event but attribution still looks soft

Use the comparison workflow when the browser tag exists and the server call returns success, yet Event Match Quality, deduplication, or event volume still disagree across Pixel, CAPI, and downstream reporting.

Storage handoff break

The landing page proves the click ID but the lead record still loses it

Escalate into the storage fix when the pixel fires, the landing URL keeps the identifier, but the CRM or form handoff still strips the same Meta click ID before the backend can reuse it for server-side matching.

Lock the landing-page context

Freeze the exact URL, identifiers, and browser proof first

Use the same final landing page that already passed the browser-side scan, then confirm whether fbclid, gclid, or partner IDs survived on that exact URL before you open another server-side ticket. If the identifier state changes between checks, the retest is no longer describing the same visitor path.

Promote the same session

Reuse the browser-approved URL inside the server retest

Carry the same landing URL, page variant, and click-ID proof into the Meta replay so event_source_url, external_id, hashes, and event naming all refer to the browser state you already approved. This is the fastest way to tell whether the weak layer is the payload, not the page.

Check shared fields before editing

Compare the two layers before you touch tags or hashes again

Line up the browser-side page proof against the server-side response and compare event_name, event_id, action_source, event_source_url, click IDs, and match keys as one evidence pack. When those fields disagree, a second scan rarely helps until the comparison route is explicit.

Choose one escalation path

Escalate with one owner-ready packet when multiple layers still disagree

Once the browser scan, identifier check, and server replay all point in different directions, stop branching into fresh ad hoc tests. Escalate the full packet through one coordinated route so frontend, GTM, backend, and media teams all review the same session evidence instead of rebuilding it from partial artifacts.

Media buyer or QA lead

Keep the session anchored to one live landing URL

Return to the main tools hub when you still need one place to compare the redirect trace, final URL, click-ID state, and browser-side scan before handing anything to engineering. That prevents tickets built from ad URLs, screenshots, or expired previews instead of the real destination users reached.

Landing-page or GTM owner

Escalate browser-side loss with page-level proof

Move into the page-level repair lane when the scan already proved the tag is missing or variant-specific on the rendered landing page. Carry the failing template, consent state, device, and final URL together so the browser-side owner can reproduce the same break without reopening the routing audit.

Backend or Meta owner

Reuse the same landing session inside the server-side retest

Jump into the Meta payload workflow when the browser scan looks healthy and the remaining question is match keys, event_source_url, deduplication, or rejected server fields. Reuse the same landing-page URL and click-ID proof so the CAPI retest measures the same session instead of a different traffic path.

Cross-team escalation

Escalate with one proof set when multiple layers disagree

Open the full audit when redirects, tags, click IDs, and downstream attribution each point to different owners. That route keeps the cluster together instead of splitting the incident across separate Slack threads and half-matching screenshots.

Use the main tools directory when you need the neighboring redirect, click-ID, landing-page, and CAPI diagnostics around this scan.

Follow the side-by-side Meta workflow when the browser tag exists but match quality, deduplication, or accepted event volume still looks wrong.

Use the landing-page arrival workflow when browser-side tags are present but the same session still lacks the Meta click ID that server-side matching depends on.

Replay the same landing-page context through Meta when the browser scan looks healthy and the remaining question is match keys, event_source_url, or deduplication.

Move here when the landing page looks healthy but the server-side Meta event never reaches Events Manager reliably.

Use this guide when Meta receives the server call but rejects, drops, or distrusts the payload after the browser handoff.

Read the step-by-step validation workflows before you change GTM, page templates, or server-side event logic.

Escalate into concrete repair paths when the browser-side issue is already proven and you need a resolution sequence, not another scan.