D3CRM GUIDE

How to connect website contact forms to d3CRM

d3CRM receives contact-form submissions from your existing website. Its connection wizard generates HTML and JavaScript for a new form, or a submit handler for an existing form. You need a website that supports custom JavaScript and a d3CRM workspace.

Create a form and match its fields

Create a form in your workspace using the form builder, a template, or a reviewed AI-generated definition. Field IDs are the keys sent by your website: an email field with ID email needs a website control named email. Use email, number, checkbox, and other field types to match the values you collect. Keep required fields limited to the information needed to respond.

Configure access and make the form live

Owners and admins can set allowed website origins and make a form live. An origin includes the protocol and host, such as https://example.com; a www address is a different origin. Copy the publishable key when it is created. It is visible to website visitors and identifies the form; it does not grant access to your workspace. Rotate a lost or replaced key and update the website snippet.

Generate and test your integration

Open Connect website on the form. Choose complete HTML/JavaScript or a handler for an existing form ID. Add the generated test code on the actual website to check browser-origin rules and field validation. The test endpoint checks the payload without creating an enquiry or triggering email or webhooks. A dashboard check alone does not prove the snippet is installed on the website.

Switch to live mode

Replace the test handler with the live handler. Keep one submit handler, show loading and success feedback, and preserve answers when a request fails. Submit one intentional test enquiry and confirm it reaches the inbox. Endpoint validation and notification delivery are separate checks. Use the form launch checklist before handing the website to a client.

Keep campaign context with the enquiry

The generated snippet can include the landing page, referrer, and current-page UTM parameters in a separate _context object. Reports group submitted enquiries by reported source. This is enquiry attribution, not visitor analytics or advertising ROI. Avoid personal information in campaign names and page URLs; d3CRM strips query strings and fragments from stored page URLs.