AdLintBack to Check Reference
META·Meta Pixel·critical

Missing Meta PageView Event

Your Meta Pixel isn't firing PageView. PageView is the floor of the pixel. Without it, Meta has no record that any user ever visited the site, which means website custom audiences are empty and every conversion event below it lands without browsing context.

CL
By Christopher LandaverdeCreator of AdLint · ad-tech tracking specialistUpdated

Why It Matters

PageView is what `fbq("init", ...)` followed by `fbq("track", "PageView")` produces. Meta hangs a lot off that single event. The "All website visitors" audience and every "Visited specific pages" audience read from PageView — no PageView, no remarketing pool. Event match quality gets scored partly on whether a conversion arrived with prior PageView hits from the same browser; a Purchase that lands cold looks like a server-side leak or a bot, and the match score drops. And the Events Manager diagnostics panel grades pixel health against expected traffic, which goes sideways when PageView is missing entirely. The usual causes: the base pixel snippet got installed but `fbq("track", "PageView")` was commented out, the pixel is gated behind a consent state that never resolves to granted, or the tag was added through GTM with a trigger narrower than All Pages.

How To Fix It

  1. Install the Meta base pixel on every page, either inline, via GTM, or through your platform integration (Shopify, WordPress, etc).
  2. Confirm `fbq("track", "PageView")` runs once per page load. Pixel Helper should show one PageView per navigation, not zero and not three.
  3. If the pixel is consent-gated, verify it actually fires once consent is granted. Walk the denied path, the granted path, and a returning-visitor path.
  4. Open Meta Events Manager, go to Test Events, paste a URL from the site, and confirm PageView lands within a few seconds.
  5. Republish and re-run AdLint.

Example

Configuration
fbq('init', '1234567890');
fbq('track', 'PageView');
For Your Client Report

This Meta Pixel is not firing a PageView event. Per Meta's pixel documentation, PageView is the base event emitted by `fbq("track", "PageView")` after `fbq("init", ...)` and is required for website custom audiences, event match quality scoring, and Events Manager diagnostics. Without it, the "All website visitors" audience cannot populate, conversion events arrive without prior browsing context (which lowers their match score), and the pixel grading panel in Events Manager will not produce meaningful health data. The pixel may be installed but commented out, blocked by a consent state that never resolves, or attached to a GTM trigger narrower than All Pages. Fix: install or unblock the base pixel, confirm one PageView per pageview in Meta Pixel Helper, and verify in Events Manager Test Events before publishing. Source: developers.facebook.com/docs/meta-pixel.

Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.

References

  1. [1]Meta. Meta Pixel implementation guide
  2. [2]Meta. Standard events reference
  3. [3]Meta Business Help. About Standard Events

Audit your own files for this check

AdLint runs this check (and 177 others) against your GTM, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Twitter/X, and Snapchat exports. Everything stays in your browser. No uploads, no accounts.

Run a free audit