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 and identifies the people and companies behind that activity. 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 Add the snippet to your site.
3

Install it

Add the snippet to 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

The snippet Default generates looks like the example below. Your real snippet has your workspace’s public key already filled in, plus built-in retry handling. Copy the complete snippet from Settings → Domains and paste it into your website as provided. It already includes the <script> tags. Do not put it inside the example below or another <script> tag. The example below uses handshake.default.com. Earlier examples use pixel.default.com. The form scripts can load from their own address, so your snippet may list more than one. Use each script address 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

After installing the snippet, load a page on the domain yourself and verify fresh Pixel activity. The domain turns Live in Settings → Domains once Default receives events from it, but a saved form or earlier activity can also produce that status. A verified CNAME record without events shows Ready; it confirms DNS, not installation. Then add your first form (see Forms below). 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. The supplied snippet can use Default’s CDN while custom hosting is pending, so check its 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 also recognizes common third-party form tools, including HubSpot, Marketo, and Paperform.
  • Page activity, such as page views and basic session context, so submissions have context.

​
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 common account and checkout paths, such as /login, /signin, /account, /checkout, /oauth, and /admin.
See Privacy & Data Handling for the full rules.

​
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 October 29, 2026