Map a form's fields

The Form tab reads the structure of a form already on your website: field names, types, labels, and options. You can review them and save them to your CJM project.

This does not create a website form, submit it, or automatically enable contact collection. Sending contacts and answers also requires an integration, such as the one described in Capture a lead with the Pixel.

Before you start

Open the page containing the form and keep the extension's side panel open. To save, sign in and select an organization, project, and Pixel. The form configuration is saved to the selected project.

The form must be accessible on the main page. Forms inside an iframe, an embedded page, cannot be read through this workflow.

Read and review the fields

1. Open Form and press Map a form on this page.
2. Click the form or a field inside it. The extension looks for the containing HTML form.
3. Review Detected fields in the panel. For choice questions, press the option count to display them.
4. Check each field's Category and correct the suggestions where needed.
5. Use the cross to exclude fields you do not want in the configuration. The field remains on the website.

Initial categories are suggested from names and labels. Review them yourself. Choosing Contact does not automatically connect that field to the profile's email or phone; the editor does not offer that association or score settings.

You can change categories and exclude fields. This screen does not let you rename questions, change options, or add fields that were not detected.

Save to CJM

1. Keep at least one field in the list and press Confirm mapping.
2. Wait for Form mapped to CJM.
3. Find the form in Already mapped forms, which shows its name or identifier and source. The list covers the project, not just the open page.
4. In the dashboard, open Setup → Lead forms and check the form configuration.

Discard removes the current review without saving. Closing the panel or leaving the Form tab can also lose the unsaved scan.

If the form is recognized as already mapped, a notice appears and confirmation updates the existing configuration. The submitted list replaces the configured questions and can change previous scoring settings: review the result in the dashboard. Question updates may require publishing the new version from the dashboard; the extension's success message does not confirm publication.

Connect answers to the correct form

The extension generates a form identifier based on the page and selected form, shown in the list after saving. Scanning the same stable form again allows updating the configuration; changing the page path or form structure can generate a new one.

Whoever connects submission must use the same form identifier and match question identifiers to the answers sent. The Pixel's ordinary form_submit event may use a different identifier: do not assume the two are already connected. Submit a test and check both the contact and answers in CJM.

What is detected and what may be missing

• Scanning reads standard HTML inputs, text areas, select menus, radio buttons, and checkboxes. It reads structure and options; it does not use typed answers to create the mapping.
• Passwords, hidden inputs, file uploads, buttons, and fields recognized as spam traps are excluded.
• Fields in hidden steps can be detected if already present on the page and recognized as part of a multi-step form. Fields loaded only later can be missing.
• Custom components or those with isolated internal structures may be unreadable. A menu allowing multiple selections is not necessarily mapped with the same selection mode: check the question type in the dashboard.