Skip to main content

​
Domain stuck on “Inactive”

A domain stays Inactive until Default receives its first event, so start by generating one — load a page on that domain yourself. If it still doesn’t go Active:
  • Confirm the install snippet is in the <head> of every page you expect traffic from — see Set up the Pixel and Forms SDK for the exact snippet and placement.
  • Confirm the public key in the snippet matches the domain you’re looking at.
  • Check for ad blockers or a content-security policy blocking pixel.default.com — try loading the page in a private/incognito window with extensions disabled.
  • Confirm the page you’re testing isn’t one the Pixel skips by default. /login, /checkout, /account and similar paths are excluded, so testing only on those pages produces no events at all. See Privacy & Data Handling.
  • Look in browser devtools for a request to pixel.default.com. If the script loads but the domain stays Inactive, the key is the most likely culprit.

​
A form isn’t showing up as “Awaiting approval”

  • Make sure the domain the form lives on has been added and is Active (see above).
  • Confirm the form isn’t excluded from capture — check the default-excluded paths, a <meta name="default:pixel" content="noform"> tag on the page, and a data-default-ignore attribute on the form or any element wrapping it. See Privacy & Data Handling.
  • If it’s a password-gated page, note that the Pixel treats a bare CMS gate form (Webflow’s page/pass/path) as a gate, not a lead form. The real form is detected once the page is public.
  • Visit the page with the form yourself once — detection can take a few minutes to register on low-traffic pages.

​
Re-copying the install script

You don’t need to regenerate anything to get your snippet again — select Copy Pixel script in the Signals toolbar to get the exact snippet, with its public key, at any time.