> ## Documentation Index > Fetch the complete documentation index at: https://docs.os.default.com/llms.txt > Use this file to discover all available pages before exploring further. # Set up the Pixel and Forms SDK > Connect a domain, configure a form, install the SDK, and verify a submission from start to finish. Follow this guide to connect a domain, approve a detected form, install the Forms SDK, and verify a workflow. After you complete this guide, Default can capture and process submissions from your custom form. ## Before you begin You need: * Admin access to your Default workspace. * A test page with the form you want to connect. * Access to the page's shared layout or tag manager. * Synthetic visitor data for testing. Test submissions are real. They can run published workflows, so use synthetic data while you configure the form. This tutorial uses the Forms SDK. Use the automatic Pixel when your page has a standard HTML form and your code does not control submission. ## Connect your domain Open **Signals**. Select **Add Domain**, then enter the domain that hosts your form. Add domain dialog with app3.localhost entered Copy the generated snippet. Default includes your public key in the snippet. Pixel installation dialog with the generated script snippet Put the configuration block before the script. Install both in your shared layout or site-wide tag manager. ```html theme={null} ``` Open the test page after you publish this change. The domain turns **Active** when Default receives traffic. Signals page with the app3.localhost domain added ## Detect and approve your form Visit the exact page with the installed Pixel. Use the form normally so Default can detect its fields. Open **Forms**. The new form appears with **Awaiting approval** status. Forms list with Request a demo awaiting approval Open the form actions and select **Review**. Confirm the domain, path, form name, and fields. Request a demo form actions with Review available Map every detected field to the correct Default field. Save the mappings before you continue. Email, first name, and company fields mapped to Default fields Open the form detail page and confirm its status is **Active**. Check the form name before you install the SDK. Active Request a demo form detail page Open **Edit Form** → **Settings**. Turn on the rules that match your intake policy. Request a demo form settings with submission and enrichment rules enabled ## Install the Forms SDK Open the **Install** tab. Copy the **Use the SDK** sample. It includes your public key, Pixel form UUID, and mapped field names. Form Install tab with the Forms SDK sample Load and initialize `sdk.js` when the page starts. Call `submitForm()` only inside your form handler. Use the HTML form ID for `recordFormInteraction({ formId })` and `submitForm({ formId })`. Use the Pixel form UUID only for `submitForm({ pixelFormId })`. See [Build a reliable Forms SDK flow](/pixel-sdk-best-practices) for a complete example. ## Verify the result Open the **Test** tab. Enter synthetic values that match the mapped field types. Form Test tab with synthetic request demo values Select **Send test submission**. Confirm the result has `"success": true`. Successful synthetic form submission result Create or open a workflow. Add a **Form Submission** trigger and select the approved form. Add the steps that should run after submission. Publish the workflow before you test those steps. Workflow canvas with the Request a demo Form Submission trigger Submit the form from its test page with synthetic data. Confirm the submission appears in **Recent Submissions** and the published workflow produces the expected result. If the workflow returns a scheduler, confirm it opens in the configured modal, inline target, or page redirect. ## Troubleshooting | Problem | What to check | | --------------------------------------- | ------------------------------------------------------------------------------------------------ | | The domain does not connect | Confirm the snippet is in the page ``. Then load the exact domain you added. | | The form does not appear | Confirm the Pixel runs on the form page. Interact with the form, then check **Forms** again. | | The form stays in **Awaiting approval** | Open **Review**, map every required field, and save the changes. | | The test submission fails | Confirm the public key, Pixel form UUID, and mapped response names match the **Install** sample. | | The workflow does not run | Confirm the workflow uses the approved form and is published before you submit. | ## Next steps Add early initialization, pre-enrichment, result handling, and safe scheduler messages. Learn how identity, form capture, workflows, and scheduler handoffs work together. Find every configuration option, method, return value, and scheduler event.