Skip to main content
Forms is Default’s website tracking and form-capture product. Add one script to your site and Forms starts identifying visitors, capturing the forms they submit, and handing qualified activity off to your workflows — no per-form setup required.
Forms is rolling out to workspaces gradually, so you may not see it yet, and it’s available to admins only. Where it’s enabled, it takes over from the Pixel page under Settings — the same domains, forms, and field mappings now live here.

​
How it works

One script on your site does the work. Once it’s live:
  1. It watches for forms. The Pixel finds the forms on your pages by itself — the ones you built, and the ones HubSpot, Marketo, Pardot, or Paperform render for you. You don’t tag or configure anything per form.
  2. You approve what it finds. New forms don’t go live on their own. You confirm which ones to capture and tell Default what their fields mean, so submissions land on the right person and company records.
  3. Submissions flow into Default. From then on, every submission arrives with the visitor’s context attached — the pages they viewed, the campaign that brought them, and who they turned out to be — and can trigger a workflow.
Alongside that, the Pixel tracks page views and builds up a picture of each visitor, so a submission isn’t just a form but a history. Reveal can identify visitors who never submit anything at all.

​
The pieces

  • Signals is the tracking layer. Connect a domain and install the snippet, and the Pixel — the small script that runs on your site — starts sending data.
  • Form Capture detects and captures submissions from forms already on your site (including HubSpot, Marketo, Pardot, and Paperform), or from forms you build in Default.
  • Reveal de-anonymizes visitors who never submit a form, so anonymous traffic still shows up as identified people and companies where possible.

​
What the Pixel captures

No per-form setup is needed for any of this.
  • Form submissions, including forms added to the page after it loads (for example, in modals or after navigation). Third-party form tools are recognized too — HubSpot, Marketo, Pardot, and Paperform.
  • Form interactions. As a visitor fills a form — on focus, field change, blur, and paste — the Pixel sends the field values entered so far, before and independently of submission. That’s what lets Default start resolving who someone is from their email as soon as they type it, so the record is ready by the time they submit. It also means a form a visitor abandons partway can still have been partly captured.
  • Page activity, such as page views, UTM and click-ID parameters, and basic session context, so submissions arrive with context attached.
  • Anonymous-to-identified visitor matching. As a visitor’s activity accumulates — and once they’re identified, whether by submitting a form or through Reveal — Default connects their earlier anonymous activity to who they turned out to be.
Page activity and stored visitor identity are subject to the visitor’s analytics consent choice. Form capture and form discovery are not — see Privacy & data handling for why, and for what the Pixel never captures. If you’d rather submit forms from your own code than have the Pixel detect them, see Set up the Pixel and Forms SDK.

​
Where to find it

Forms appears in the sidebar as two entries:
  • Signals — the websites you’ve connected, their status, and the paths discovered on each.
  • Forms — every form Default knows about across those domains, detected and built alike.
Submissions don’t have a place of their own; each form’s submissions appear on that form’s detail page.

​
Where to go next

Start with Set up the Pixel and Forms SDK — it walks the whole path from connecting a domain to a verified submission. Until the script is live, nothing else in Forms has anything to work with. From there: The Default SDK section covers submitting forms from your own code, the options and events available, and how the scripts behave end to end.