Skip to main content
The Pixel is a small script you add to your website. Once installed, Default captures the forms your visitors submit and identifies the people and companies behind that activity. Default maps the form fields it finds to your Default records. Inbound interest flows straight into your workspace.
Open the Forms app and select Signals in the sidebar. Old Settings → Pixel links land on the same page automatically.Admin access is required.
The page has two tabs:
  • Domains: add a site and get its install snippet.
  • Forms: review captured forms and map their fields.

​
Domains

The Domains tab lists every website you added the Pixel to, along with its connection status.

​
Add a domain

1

Add a new domain

Select Add new Domain. Enter your website address, for example https://www.acme.com.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.You can return to it anytime with Copy Pixel script.
3

Install and test

Add the snippet to your site. See Install the Pixel below.Then run the connection test back in Default.
Your workspace has one Pixel public key, so the snippet is the same on every domain. If your forms live on more than one domain, for example acme.com and try.acme.com, add each one here. Then install that same snippet on each. The Forms tab only shows forms detected on domains you added.

​
Domain status

Each domain shows a status so you know whether the Pixel is working: To stop tracking a site, open the domain’s menu. Select Remove.

​
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 snippet from the Domains tab rather than typing it by hand.
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.
  • One 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 the snippet is live, run the connection test on the domain in Default. It confirms each step in order:
1

Snippet added

Default confirms the snippet is present on the page.
2

Pixel detected

Default confirms the script loaded and initialized.
3

Test event received

Default sends and receives a test event to confirm data is flowing.
If the test stalls, check the following:
  • 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.

​
What the Pixel captures automatically

Once the script loads, the Pixel works on its own. You need no per-form setup.
  • Form submissions, 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.

​
Forms

When the Pixel sees a form on one of your connected domains, that form appears on the Forms tab. Each form shows its name, the domain where the Pixel saw it, and the detected fields. The first time someone loads or submits a form on a tracked page, Default reads its structure. This includes the form’s name, its fields, and the field types. The form can take a few minutes to show up. On a low-traffic page, load the page yourself to speed things along. Turn on Allow Pre-Enrichment on a form to let Default enrich a submission before processing. Records then arrive already filled in with company and contact detail.

​
Review and approve forms

New forms do not go live on their own. On the Forms tab, select Approve fields in the banner to open the review dialog. Check what Default detected. Approve the forms you want to track, and skip the ones you do not. Approving a form tells Default this is the correct shape of the form going forward. A later site change, such as a renamed or added field, then does not quietly change what your workflows receive. If an approved form changes later, Default flags it with an unaccepted field changes alert. Review it the same way to keep your forms in sync without breaking the workflows that depend on them.
Reviewing and approving captured forms on the Forms tab

​
Map form fields

Map each detected form field to a field on your Person or Company records. This makes submissions land on the right fields. When the Pixel finds a new form or new fields, Default prompts you to review them.
1

Open the field mapping

When new forms or fields are detected, open the review dialog from the prompt on the Forms tab.
2

Match each field

For each detected field, the dialog shows its label, name, and input type. Use the dropdown to map it to a standard or custom field, grouped under Person and Company.Use the search and filters, by form, domain, or path, to work through long lists. Turn on Hide mapped fields to focus on what is left.
3

Save your mapping

Select Save to confirm the mapping and approve the form.New submissions then populate the fields you mapped.

​
Use a form in a workflow

Once a form is approved 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.