Set up the Default Pixel and Forms SDK

Connect your website to Default so a form submission can start a workflow. This guide covers the Pixel for existing website forms and the Forms SDK for forms with your own submission code.

Before you begin

You need:

Admin access to your Default workspace.
Access to your website’s shared layout or tag manager.
A published test page with the form you want to connect.
Made-up visitor details, such as alex@example.com, for testing.

Test submissions are real. They appear in Recent Submissions and can run published workflows. Use a test form and made-up visitor details while you set up the connection.

Choose how to connect your form

Your form	What to install
An existing website form without your own submission handler	Install the Pixel. Then add the form with Catalog forms.
A custom form whose submission your code controls	Add the form in Default. Then use its Use the SDK sample.
A new form you want to copy onto your website	Create the form in Default. Then copy Embed this form from Install.

You can install the Pixel for website tracking alongside the Forms SDK. Keep submitForm() in your form handler so loading the page does not send a submission. If the Pixel and your code both submit the same form, Default can receive it twice. Follow Prevent duplicate submissions before combining them.

Connect your domain

Add your domain

Select Settings in the sidebar, then Domains.Select Add domain in the Website card.Enter the domain that hosts your form, such as www.example.com.A registered domain also covers its subdomains. If you register both example.com and www.example.com, Default uses the more specific matching domain for that page.Select Continue.

Copy your Pixel script

The domain detail page shows your install snippet under Add the snippet to your site. Select Copy.For a domain you already added, open its detail page under Settings → Domains and find Add the snippet to your site.Copy the complete snippet. It includes your workspace’s public key, load retries, and the consent controls. Paste it into your site as provided, including its <script> tags. Do not put it inside another <script> tag or replace it with a shortened example.Use each script address in your copied snippet. The form scripts can load from their own address, so your snippet may list more than one. When custom hosting is configured, those scripts load from a dedicated hostname such as connect.example.com, with the default CDN as a fallback.If a content-security policy or an ad blocker allowlist controls what loads on your site, allow the script host(s) in your snippet and the tracking API host.

Connect the custom hostname when available

If the detail page provides a CNAME record under Connect your domain, add it at your DNS provider. Copy the exact Name and Points to values shown; keep your website’s existing DNS records. Then select Check status. DNS changes can take up to 48 hours to propagate.If custom hosting is unavailable and no record is provided, skip this step. The copied snippet loads from Default’s CDN without a custom connection.Finish this step before testing a snippet that uses the custom hostname. While its DNS is unfinished, the loader retries that hostname before falling back to the default CDN, which can delay loading on short visits. See Connect a website.

Install and publish the script

Add the copied snippet to your shared layout or site-wide tag manager. Load it on every page you want to track.Publish your website changes.Open the exact page that contains your form.If your cookie banner blocks the Pixel script, allow it to load before you test catalog mode.The domain’s status turns Live when Default receives traffic from it or the domain has a form. A verified custom connection without traffic shows Ready. It does not confirm that the script runs on every page.

These walkthroughs use a test workspace. Copy your own workspace’s snippets. Watch where to add a domain, copy the script, and open the form catalog on an existing test domain.

The Pixel allows analytics and marketing until your banner supplies a visitor’s choice. If your website waits for permission, deny tracking only when there is no saved choice. Place this immediately after the copied install snippet, before its downloaded scripts run:

<script>
  function hasStoredDefaultChoice() {
    var match = document.cookie.match(/(?:^|;\s*)_dflt_consent=([^;]*)/);
    if (!match) return false;
    try {
      var stored = JSON.parse(decodeURIComponent(match[1]));
      return stored.v === 1 && typeof stored.analytics === 'boolean' && typeof stored.marketing === 'boolean';
    } catch (e) {
      return false;
    }
  }
  if (!hasStoredDefaultChoice()) {
    window.__defaultPixel__.setConsent({ analytics: false, marketing: false });
  }
</script>

When your visitor makes a choice, pass that choice through the same method. For example, this visitor allows analytics and declines marketing:

window.__defaultPixel__.setConsent({ analytics: true, marketing: false })

Do not send a new denial on every page while your banner loads. That overwrites the saved choice and clears the visitor’s identity. Pass later changes from the banner too, including withdrawal. Analytics controls visitor identity, pageviews, sessions, and Reveal’s Account Signal. Marketing controls Reveal’s People Signal through Vector. These choices do not turn form submission capture off.

Enable website intent when you need it

The Pixel includes Reveal support. Installation alone does not complete its setup. Choose pages for Account Signal, check the Vector integration for People Signal, and publish the workflow that should use each signal. Follow Reveal for those steps and page rules.

Add your form

For an existing website form, follow the catalog steps below. For your own submission code or a new form, open Forms, select Create new, then New form. In Fields, set each field’s name and type to match the values your code will send. Then check its mappings and submission settings below before opening Install. See Create a form in Default. Catalog mode needs a supported form on a page where the Pixel runs. It skips forms marked data-default-ignore. Use New form for those forms or for controls outside a native <form>. The Pixel supports HTML, HubSpot, Marketo, and Paperform submissions. Pardot needs a custom SDK connection. For an iframe on another domain, the parent page cannot read its forms. Install the Pixel inside the iframe if you control it, and connect that domain in Default. See Form binding.

Open catalog mode on your website

In Forms, select Create new, then Catalog forms.Choose your domain.Under Start on, choose or type the path of the page with your form.Select Open catalog mode. Your website opens in a new tab.On a Ready website detail page under Settings → Domains, select Open Forms to open the Forms app.

Catalog forms dialog with the request-demo page selected on a test domain

The Pixel must already run on this page. Default does not add new website forms to Forms automatically.

Add the website form

Select Add form beside your form.Enter a name that you can recognize in Default.Confirm the addition. The form becomes Active and appears in Forms.

Add form to catalog dialog with a form name and three detected fields

See Add forms from your site for the complete catalog procedure, including forms inside embedded pages.

Map the form fields

Open your form in Forms.Select Map fields.Choose the Default field for each form field you want to save.Select Save mappings.

Map fields dialog with form fields and their Default field destinations

A mapping applies everywhere the same field name appears. Check its destination before you save. If Default reports different types for a field name, check the forms that share that name.

Check where Default accepts submissions

Confirm the form is Active.Check Form ID(s) against your website’s HTML form ID. Use Add ID for additional IDs that represent the same form.Check Track submissions on. Use Limit to specific pages if the form must only accept submissions from selected pages.Select Edit Form, then open Fields. Keep Accept submissions on to save submissions and run workflows.

Form editor Fields tab with Accept submissions enabled and three example fields

Allow pre-enrichment can start enrichment when a visitor enters their email. It uses credits and needs an accepting form, a published enriching workflow, and a primary enrichment waterfall. Use that same waterfall in the workflow’s Enrich step to reuse the early result. See Map form fields for its requirements.

Watch how catalog mode finds a form and opens its name and field review.

Install the Forms SDK

Skip this section if the Pixel captures your existing website form and you do not use your own submission handler.

Open the form's install options

Open your form in Forms.Select Edit Form, then open Install.Choose Embed this form for complete form HTML, or Use the SDK for your own markup. The generated sample includes your public key, Default form ID, and response field names.

Install tab with Install Pixel and Embed this form sections

Load the SDK before your visitor submits

Copy the Use the SDK sample.Load sdk-core.js and call DefaultPixelSDK.init() when the page starts.Move DefaultPixelSDK.submitForm() into your form’s submission handler. Replace the sample responses with the values your visitor enters.

The SDK applies consent choices queued on the Pixel’s install loader and sets no tracking cookies of its own, so load order does not matter for consent.

Use pixelFormId for the Default form ID in the sample. Use formId for your website’s HTML form ID. Pass the same pixelFormId (and formId, if you use one) to recordFormInteraction().See Build a reliable Forms SDK flow for initialization, error handling, and scheduler behavior.

Prevent duplicate submissions

If the Pixel runs alongside your SDK handler, add data-default-ignore to the form or its wrapper. Do this for Embed this form too when the Pixel also runs on the page.

<form id="request-demo" data-default-ignore>
  <!-- Your form fields -->
</form>

This stops automatic capture of that form. Your handler still calls submitForm() once. Disable the submit button while that request is pending. The ignored form also loses automatic email interaction capture. If you use pre-enrichment, call recordFormInteraction() when the visitor leaves the email field. Use the same pixelFormId and formId for that call and the submission. See the complete SDK example. The form editor’s Use the SDK sample loads sdk-core.js. It handles form submission and the scheduler. It does not fingerprint visitors, track sessions or pageviews, or run Reveal by itself. Reveal’s Account Signal needs the Pixel: on a page with only the Forms SDK, it does not run. Your cookie banner can disable analytics while form submissions continue. See Connect your cookie banner. Watch how to open the form editor and find the install and test options.

Verify the result

Send a test from Default

Open your form and select Test.Enter made-up values that match your field types.Select Send test submission.Check Submission result for "success": true.Then confirm that this test appears in Recent Submissions. A successful response alone does not prove that Default saved it. Disabled submissions and rejected page paths can still return success.

Submission result showing a successful test request

Test tab with fields for work email, first name, and company

This test sends values from Default. It does not prove that the script runs on your website, that an email interaction starts pre-enrichment, or that a visitor can book a meeting.

Connect a workflow

Create or open a workflow.Add a Form Submission trigger.Select your active form.Add the steps that should run after submission.Publish the workflow before you test its result.

Submit from the website

Open the published page with your form.Complete the form with made-up visitor details.Submit it once.Confirm the submission appears in Recent Submissions.Confirm that one submission created one entry. Reload the page and test again with the visitor’s saved consent choice. If tracking can be declined, also test form submission with tracking denied.If you use pre-enrichment, enter a valid email and leave that field before submitting. Check the early result separately from the submission result.Check that the published workflow produces the expected result. If it opens a scheduler, confirm that the visitor can see it in the configured modal, inline location, or destination page. Complete a test booking and check the expected booking result. Check redirect workflows on the actual destination page too.

Troubleshooting

Problem	What to check
Last activity stays empty	Check the snippet on the exact published page and the browser’s errors. Check analytics consent. Verify form capture with an actual submission.
Catalog mode does not open	Confirm the Pixel runs on that page. Open a fresh catalog link from Default. Allow the new browser tab.
The form does not appear in Forms	Add it with Catalog forms. Website visits alone do not add it.
Default does not save submissions	Confirm the form is Active, Accept submissions is on, and Track submissions on includes the test page.
The Pixel skips the website form	Check `data-default-ignore`, the `default:pixel` `noform` meta tag, and protected paths such as `/login`, `/signin`, `/account`, `/checkout`, `/oauth`, or `/admin/`.
The form sends twice	Choose one submission method. Mark an SDK-managed form `data-default-ignore` when the Pixel also runs, and block repeated clicks.
Field mapping shows different types	Check the forms that share that field name. Mappings apply across those forms.
The SDK test fails	Check the public key, `pixelFormId`, response names, and field types against the Use the SDK sample.
The workflow does not run	Check its Form Submission trigger and selected form. Publish the workflow before you submit.
A test in Default succeeds, but the website fails	Check that the website loads the script and submits its real field values. Then repeat the website test.

Next steps

Build a reliable Forms SDK flow

Add early initialization, pre-enrichment, result handling, and scheduler messages.

Understand the full integration

Learn how identity, form capture, workflows, and scheduler handoffs work together.

Use the API reference

Find configuration options, methods, return values, and scheduler events.

Overview

Get started

Switching to Default

Guides

Tables

Enrichment and data

Routing

Scheduling

Workflows

Forms

Pixel and Forms SDK

MCP

Chrome extension

Settings

API

Set up the Default Pixel and Forms SDK

Before you begin

Choose how to connect your form

Connect your domain

Enable website intent when you need it

Add your form

Install the Forms SDK

Prevent duplicate submissions

Verify the result

Troubleshooting

Next steps

Build a reliable Forms SDK flow

Understand the full integration

Use the API reference

Overview

Get started

Switching to Default

Guides

Tables

Enrichment and data

Routing

Scheduling

Workflows

Forms

Pixel and Forms SDK

MCP

Chrome extension

Settings

API

​Before you begin

​Choose how to connect your form

​Connect your domain

​Connect your cookie banner

​Enable website intent when you need it

​Add your form

​Install the Forms SDK

​Prevent duplicate submissions

​Verify the result

​Troubleshooting

​Next steps

Build a reliable Forms SDK flow

Understand the full integration

Use the API reference

Before you begin

Choose how to connect your form

Connect your domain

Connect your cookie banner

Enable website intent when you need it

Add your form

Install the Forms SDK

Prevent duplicate submissions

Verify the result

Troubleshooting

Next steps