Skip to main content
This page lists fixes for the most common problems with Forms and the Pixel in Default.

​
No fresh Pixel activity

A domain with no Pixel activity can show Add snippet, Waiting for DNS, or Ready in Settings → Domains, depending on its custom hosting connection. Ready confirms DNS verification, not that the Pixel is installed. Live can also come from a saved form or earlier activity, so the status alone does not confirm that events are arriving now. Load a page on the domain yourself. If fresh Pixel activity is missing, or catalog mode doesn’t start on the page, check the following regardless of the domain’s status:
  • 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 your workspace’s key. Your workspace has 1 Pixel key for every domain, so open the domain in Settings → Domains, copy the snippet again from Add the snippet to your site, and compare.
  • Check for ad blockers or a content-security policy blocking any script address in your copied snippet or the tracking API host. 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 each script address in your copied snippet. Older snippets may use pixel.default.com. If the script loads but Last activity stays empty, the key is the most likely culprit.

​
Pending DNS

If the domain shows Waiting for DNS, Finish DNS setup, or DNS record doesn’t match, open it and check Connect your domain. If a CNAME record is provided, copy its exact values to your DNS provider, then select Check status or Check again. DNS changes can take up to 48 hours to propagate. See Check connection status. If no record is provided, skip DNS setup and use the supplied snippet through Default’s CDN. The supplied snippet also retains that CDN as a fallback while custom hosting is pending. Check for fresh Pixel activity separately; a verified CNAME alone does not prove installation.

​
Submissions from a form don’t show up in Default

  • Check the form is listed under Forms for that domain, with the same Form ID as the id on the page. Default doesn’t list new forms on its own, and it drops submissions from forms you haven’t added. Add the form with Catalog forms or create it in Default.
  • Make sure the domain the form lives on has been added and is Live (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.
  • A form marked data-default-ignore is invisible to Catalog forms on purpose. If your own code submits it to Default later, create it in Default with the matching Form ID.

​
Re-copying the install script

You don’t need to regenerate anything to get your snippet again. Open the domain in Settings → Domains and select Copy under Add the snippet to your site to get the exact snippet, with its public key, at any time.
Last modified on October 29, 2026