Website Script and Forms

The Marcenta website script connects approved website forms to Lead Routing and Calendar Booking. It observes supported form submissions, sends the configured mapped values to Marcenta, and opens the booking experience when the selected routing outcome allows it.

The script does not route every form it sees. A website must have its own Marcenta configuration, the script must load from an allowed origin, and each form must be reviewed and enabled before its submissions participate in routing.

Before installation

Identify:

• the exact production website origin;
• every page containing a form that should route;
• whether deployment is managed in application code, a CMS, or Google Tag Manager;
• any consent or cookie policy controlling when the script may load;
• the fields required by routing and Salesforce matching; and
• where the calendar booking experience should appear.

An origin includes the protocol, hostname, and port. https://www.example.com and https://example.com are different origins. Use separate website configurations for production, staging, or other origins that must be managed independently.

Create the website configuration

1. Open Settings → Web Script.
2. Enter the customer-facing website URL when prompted, or select the intended website when more than one exists.
3. Confirm that the displayed website is the environment where the script will be installed.
4. Choose Standard HTML or Google Tag Manager.
5. Copy the generated installation snippet.

Each generated snippet contains the identifier for one Marcenta website configuration. Do not copy a snippet from another website, replace its identifier, remove its integrity settings, or combine fragments from different snippets.

Install directly with Standard HTML

Use Standard HTML when you can edit the website application, shared layout, theme, or CMS custom-code area.

1. Copy the Standard HTML snippet from Settings → Web Script.
2. Add it to the shared layout or custom-code area used by every page containing a routing form.
3. Ensure the snippet is rendered once on a page. Avoid placing separate copies inside individual form components.
4. Publish the website change.
5. Open a real public page containing the form and verify the installation in Marcenta.

Use the snippet shown in Marcenta rather than copying an example from documentation. This keeps the website identifier, script address, and integrity value current for that website.

Install with Google Tag Manager

1. Copy the Google Tag Manager snippet from Settings → Web Script.
2. In the website's Google Tag Manager container, create a Custom HTML tag.
3. Paste the complete generated snippet into the tag.
4. Select the Initialization – All Pages trigger so the script can observe supported forms as they become available.
5. Preview the container and open a page containing the intended form.
6. Confirm the tag runs once and is not blocked by a trigger exception or consent configuration.
7. Publish the container.
8. Verify the installation under Settings → Web Script.

If your organization loads optional scripts only after consent, use its approved consent trigger instead of bypassing that policy. Test both the consented and non-consented experience.

Check whether the script is installed correctly

Open a public page containing the form, then return to Settings → Web Script and refresh Script status.

Confirm Last seen and Detected URL match the environment and page you tested. Detection proves that the script loaded from the allowed website; it does not prove that a form is configured, that fields are mapped correctly, or that booking succeeds.

If the script is not detected:

1. Confirm the website or tag-manager change is published rather than only previewed.
2. Confirm the generated snippet belongs to the selected Marcenta website.
3. Match the page's protocol, hostname, and port to the configured origin.
4. Check whether a consent manager, content-security policy, browser extension, or tag trigger prevents loading.
5. Confirm the snippet appears only once and has not been altered.
6. Reload the public page, then refresh Script status again.

Supported forms

The script currently supports:

• standard HTML forms represented by a <form> element;
• HubSpot legacy embedded forms; and
• current HubSpot embedded forms.

The script can observe forms rendered shortly after the page loads, including supported HubSpot embeds. A custom form that never uses a real form element or a supported provider event may require manual configuration and may still need implementation changes on the website before its submission can be captured reliably.

Test multi-step forms, forms inside custom overlays, and heavily customized form frameworks end to end. Visual similarity to a supported form does not guarantee compatible submission behavior.

Discover and enable a form

After the script is detected:

1. Open a public page containing the intended form.
2. Return to Marcenta and open Settings → Forms.
3. Select the correct website when more than one exists.
4. Find the observed form and open Manage form.
5. Review the suggested form selector and every suggested field mapping.
6. Correct incomplete or ambiguous mappings.
7. Select Enable form or Update form.
8. Submit safe test data and confirm the submission appears under Routing.

The script currently reports up to 10 supported forms from a page and up to 50 fields per discovered form. If a page exceeds those limits, configure the required form manually or simplify the page so the intended form is unambiguous.

Understand form statuses

Merely discovering a form does not route its submissions. Only a configured form can participate in routing.

Name mapped fields

A mapped field name describes the value's meaning inside Marcenta. The selector identifies the corresponding input on the website. Keep the Marcenta name stable even when the website's label or selector changes.

Use these standard names where applicable:

Use lowercase snake_case names for custom fields, such as employee_count, requested_product, or annual_revenue. Names can contain letters, numbers, underscores, hyphens, and up to four dot-separated segments. Prefer simple flat names unless an established routing field already uses a nested structure.

The email and company mappings have special importance. Email supports visitor identity, invitations, and Salesforce Lead or Contact matching. Company or a business-email domain can support Salesforce Account matching. Do not map a label, placeholder, or unrelated hidden value merely because its name looks similar.

Hidden form fields

Hidden fields are inputs that visitors do not see but that are submitted with the form. They are commonly used for attribution and operational context, including UTM parameters, advertising click IDs, lead source, campaign identifiers, or a product selected elsewhere on the page.

Marcenta can capture a hidden field when:

• the field belongs to the configured form;
• the field has an explicit mapping in Marcenta; and
• its value has been populated by the time the form is submitted.

Map the field using the same process as a visible input. Give it a clear Marcenta field name, such as utm_campaign or lead_source, and select the hidden input using a stable ID, name, or data attribute. If JavaScript, Google Tag Manager, a consent manager, or the form provider populates the field, confirm that this happens before submission.

To verify the mapping, populate the hidden field with a distinctive but safe test value, submit the public form, and confirm that the value appears under Routing → Submitted fields. Repeat this test after changes to the form, page scripts, tag-manager configuration, or consent behavior. If the hidden field is renamed, removed, moved outside the form, or populated too late, review and update the saved mapping.

Do not map passwords, authentication or CSRF tokens, session identifiers, CAPTCHA values, API keys, or other secrets. Map only information required for approved routing, attribution, and booking purposes.

Choose reliable selectors

Prefer selectors based on stable IDs, field names, or explicit data attributes controlled by your website team. Avoid generated styling classes, layout position, visible copy, or deeply nested selectors that can change during a redesign.

Each mapped selector should identify exactly one intended field inside the configured form. Verify radio buttons, checkboxes, dropdowns, hidden attribution fields, and multi-value controls using the values a real submission produces.

Add a form manually

Use Add form when automatic discovery is unsuitable. Provide:

• a stable, unique form ID;
• the form selector;
• one Marcenta field name and website selector for every required mapping; and
• an optional calendar container ID.

The calendar container determines where the booking experience is mounted. If the configured container does not exist, the script can create a container directly after the form. Provide a dedicated stable container when the page layout must be controlled precisely.

When the page or form changes

A website deployment can change a form's selector, field selectors, provider identity, or available fields. The script may mark an existing configuration as Changes detected when the newly observed structure differs from what was saved.

When that happens:

1. Open the affected form under Settings → Forms.
2. Compare the current form selector and suggested fields with the saved mappings.
3. Confirm that every business-critical Marcenta field still points to the correct website input.
4. Remove obsolete mappings and add required new ones.
5. Select Update form.
6. Re-test important routing branches through the public page.

Do not approve changes solely to clear the warning. A selector can remain syntactically valid while pointing to the wrong field. If a page moves to another origin, also update or create the appropriate website configuration and install its generated snippet.

Test the complete capture flow

1. Open the public page in a clean browser session.
2. Confirm Script status is recent for the correct website.
3. Submit distinctive but safe values through the configured form.
4. Open Routing and locate the new submission.
5. Compare Submitted fields with the values entered in the browser.
6. Confirm the intended routing rule and fallback behavior.
7. If a calendar should appear, complete a test booking and verify the representative event and visitor invitation.
8. Repeat after material form, page, consent, or tag-manager changes.

Troubleshooting