Skip to main content
The Default Pixel is a small script you add to your website. Once installed, Default captures submissions from the forms you add in Forms. Pageviews, and identifying the people and companies behind a visit, come from a separate Analytics tag copied from the same screen. Default maps each form’s fields to your Default records, so inbound interest flows straight into your workspace.
Select Settings in the sidebar, then Domains. Old Settings → Pixel and Signals links land on the same page automatically.Admin access is required.
Pixel setup uses 2 places in Default:
  • Settings → Domains: add a domain and get its install snippet. See Domains.
  • Forms: add the forms on your site and map their fields. See Your Forms.

Domains

The Website card on Settings → Domains lists every website you added, along with its status.

Add a domain

1

Add a new domain

In Settings → Domains, select Add domain in the Website card. On Load the pixel from your website, enter your website address, for example https://www.acme.com, and select Continue.This registers the domain so the Pixel knows to track it.
2

Copy the Pixel script

Default shows the <script> snippet with your workspace’s public key already filled in. Copy it.To return to the snippet, open the website domain’s detail page and find Pixel. Select Copy next to Forms.
3

Install it

Put the snippet on your site. See Install the Pixel below.
Your workspace has 1 Pixel public key, so the snippet is the same on every domain. A domain covers its subdomains, so adding acme.com also covers try.acme.com. Add different domains, such as acme.com and acme.co.uk, separately, then install the same snippet on each. Forms only lists forms on domains you added.

Domain status

Each website domain shows a status: To stop tracking a site, open it and select Delete Domain under Danger Zone. See Check connection status and Edit or remove a website.

Install the Pixel

Copy the complete snippet from Settings → Domains and paste it into your website as provided. It already includes the <script> tags. Do not wrap it in another <script> tag, and do not retype it: it fills in your workspace’s public key, queues setConsent calls made before the script finishes loading, and retries a failed download. The snippet loads core.js: form capture and the scheduler. It does not load FingerprintJS, set an identity cookie, or record pageviews. To also record pageviews and company reveal, copy the Analytics tag from the same screen and add it to the same pages. It waits for the snippet’s key, so it can go before or after it. When the visitor allows analytics, a form submission from core.js uses the visitor ID and session the tag stores, so it joins that visitor’s page views. Without analytics consent, each core.js submission gets a new ID that is not stored. Sites that already load the combined index.js keep it and do not need the Analytics tag. Earlier examples use pixel.default.com or index.js. Use the script addresses in the snippet you copy from your workspace. Where to put it: paste the snippet into the <head> of every page you want to track. The simplest ways to cover a whole site are:
  • Add the snippet to your site-wide template or layout.
  • Add it through a tag manager, such as Google Tag Manager, as a custom HTML tag that fires on all pages.
A few things worth knowing:
  • It loads asynchronously and starts itself. The snippet sets your public key on window.__defaultPixel__ and loads the Pixel in the background. The Pixel initializes automatically once the page is ready, so there is no other code to write.
  • The public key is safe to expose. The key value is a public key meant to live in client-side code.
  • Single-page apps are supported. The Pixel follows client-side route changes, so a React, Vue, or other single-page app needs no extra setup.
  • 1 snippet for the whole workspace. Your workspace has a single public key, so the same snippet works on every domain you add. Adding a domain tells the Pixel to track that site and does not produce a different snippet.

Verify the installation

The forms snippet sends no page views, so loading a page does not change the domain’s status. A forms-only domain shows Add snippet (“Live after its first form or page view”) until you add its first form, then turns Live in Settings → Domains. To confirm the snippet is installed, open the page in catalog mode from Catalog forms (see Forms below). Catalog mode only starts when the snippet is on the page. With the Analytics tag or index.js, the domain also turns Live once Default receives page views from it. A verified CNAME record without events or forms shows Ready; it confirms DNS, not installation. If fresh Pixel activity is missing, check the following regardless of whether the domain shows Add snippet, Waiting for DNS, Ready, or Live:
  • The snippet is in the <head> of the page you test.
  • A content-security policy does not block the snippet.
  • The page allows the Pixel to run. See Capture controls below.
For pending or incorrect DNS, follow Pending DNS. Until the record verifies, the snippet shown loads from Default’s CDN. After it verifies, copy the snippet again so it loads from your own domain, with Default’s CDN as a fallback. Check the installation separately from the DNS record. See No fresh Pixel activity for the full installation checks.

What the Pixel captures automatically

Once the script loads, the Pixel works on its own. You don’t tag anything per form.
  • Form submissions from the forms you’ve added in Forms, including forms added to the page after it loads, for example in modals or after navigation. The Pixel recognizes embedded HubSpot and Marketo forms. It hears a Paperform embed’s submission message, but catalog mode does not detect that embed, so Catalog forms cannot add it.
  • Page activity, only with the Analytics tag (or index.js): page views and session context. The forms snippet alone does not record page views.

Capture controls

  • Turn off capture on a page by adding this to the page’s <head>:
  • Sensitive pages are skipped by default. The Pixel does not capture forms on a page when a section of its path starts with login, log-in, signin, sign-in, account, checkout, or oauth, or is exactly admin, such as /login, /account/settings, or /admin. A page like /my-account or /admin-training is captured.
See Privacy & Data Handling for the full rules, and Cookies & Storage for what each script stores.

Install guide for agencies

Send this section to whoever puts scripts on the site. They need no Default account.
  1. Which script. Your Default admin copies the snippet from Settings → Domains, on the website domain’s page, and sends it to you. Use it exactly as sent. It loads core.js, which captures forms and opens the scheduler. It sets no tracking cookie and records no page views.
  2. The optional Analytics tag. Add it only if the admin also sends the Analytics tag from the same screen. It records page views and identifies visitors’ companies. Leave it off when a security review does not allow a fingerprinting script on the page.
  3. Where it goes. Paste the snippet, and the Analytics tag if sent, into the <head> of every page with a form, or once in the site’s shared template. In a tag manager, add each one as a custom HTML tag that fires on all pages. Do not wrap either one in another <script> tag.
  4. How to check it is live. Load a page with a form and open the browser’s developer tools. On the Network tab, core.js returns status 200. The snippet lists more than one address and tries the next when one fails or does not answer: a failed request, then a 200 from the next address, is a working install. A request to /api/pixel/known-forms follows. With the Analytics tag, analytics.js loads too. A request to /api/events/pageview follows only when analytics consent is granted. Declined analytics consent sends no page view.
  5. What to send back. The pages or template you changed, whether you added the Analytics tag, and a screenshot of the Network tab from step 4.
The domain in Settings → Domains shows Add snippet until its first form or page view, so the Network tab in step 4 is the check for a forms-only install.

Forms

Default doesn’t list the forms on your site on its own. Add each form with Catalog forms, which opens the page with catalog mode running so you can add the form right there. See Add forms from your site. Turn on Allow pre-enrichment on a form’s detail page to let Default enrich a submission before processing. Records then arrive already filled in with company and contact detail.

Keep forms in sync

If the fields of a form you added change on your site, Default flags it with a Fields changed badge in Forms. Review it to keep your forms in sync without breaking the workflows that depend on them. See Keep catalogued forms in sync.

Map form fields

Map each form field to a field on your Person or Company records, so submissions land on the right fields. Select Map fields on a form’s detail page, or Map all fields in the Forms toolbar to work across every form at once. For each field, pick the Person or Company field it belongs to, then select Save mappings. See Map form fields.

Use a form in a workflow

Once a form is added and mapped, it is available in Workflows as a target for the Form Submission trigger. Create a workflow. Add a Form Submission trigger and choose your form. Everything a visitor submits then runs through that workflow for routing, enrichment, scoring, and scheduling.
A Pixel form selected as a Form Submission trigger in the workflow builder

Advanced: the Forms SDK

Use the Forms SDK when a normal Pixel install cannot observe your form, or when your code must control the scheduler handoff.
Last modified on November 14, 2026