Media
3 items
Description
Detect GASS tracking install (JS, CTA link, visitor_id) plus Meta/TikTok pixels and page tech. Check a landing page in one click: GASS tracking install, CTA tagging, visitor cookie, Meta & TikTok pixel events, page tech. Open a landing page, click the icon, and get a straight answer to the question every setup ends with: is the tracking actually working? GASS Landing Page Inspector reads the page the way the tracker does and reports what it finds — no login, no dashboard, no waiting for data to land. ── INSTALL VERDICT ────────────────────────────── Three checks decide whether the page is live: • GASS JavaScript — detects both install shapes: the hosted script tag (t.gass.co.id/jsvN/<key>.js) and the inline snippet pasted straight from the setup generator, which never makes a request at all. • CTA links — counts /cta links, how many carry the visitor id (?v=), and how many match the cookie in the browser right now. Stale hrefs from an earlier session are called out separately. • visitor_id cookie — proof the handshake finished, not just that the script loaded. You get INSTALLED, PARTIAL or NOT INSTALLED, and when something is off, the specific failure: the loader threw before initialising, the snippet is missing its gass.run() call, the script and an inline copy are both installed and events will double count. ── PIXEL EVENTS ───────────────────────────────── Meta and TikTok pixel IDs, plus the events actually sent. Events are read from the requests the page made, not from what the page's code claims — so an event that never reached the platform shows as missing. • Event names in fire order, with a repeat count • A ×2 count exposes a pixel installed twice • Meta's own event counter compared against the requests observed • TikTok events that post their payload are reported as "not readable" rather than silently counted as zero ── CONFIGURATION ──────────────────────────────── • Subdomain, project key, loader version, interval, experience mode • Platforms three ways: configured in the script URL, actually loaded on the page, and implied by the active connectors — so a mismatch is obvious • Connectors returned by the handshake, with their public IDs (pixel_id, measurement_id, partner_id, account_id, waba_id) and mapped events • Tracking options with both values: what the snippet declares and what the loader is really running. When they disagree, you see it. ── PAGE TECH ──────────────────────────────────── Over 80 technologies, grouped so an audit reads top to bottom: CMS and page builder, JS framework, CSS/UI, analytics and ad platforms, chat and lead capture, payment gateways, hosting and CDN, embedded media. Plus the page facts that break tracking when they are wrong — HTTPS, mobile viewport, form count, iframes, language, title. ── PRIVACY ────────────────────────────────────── The extension has no servers and makes no network requests of its own. Nothing is collected, stored or transmitted. It reads the active tab only when you click the icon, and the report exists only in the popup until you close it. Connector payloads can contain secrets — the extension reads a fixed list of public ID fields and never touches the rest. Copy hands you the full report as JSON, for pasting into a ticket.