TraceLead fills hidden inputs that already exist on a form on your own page, so the attribution travels wherever that form already posts: a CRM, an inbox, a spreadsheet. This page lists every form builder, website platform and CRM we write about, and how far each one is tested.
What the statuses mean
- Tested — a browser test renders the builder's real markup and checks, on every release, that the hidden fields are filled after consent, left empty without it, and submitted with the form.
- Verified live — tested as above and also checked on a real install by us or a pilot customer, on the date shown.
- Guide — a documented way to do it that we have not covered with an automated test, often because the platform limits what a page can do. We never call a guide "supported".
We add a builder to this list only with one of these statuses, and the list on this page, on the home page and in the FAQ come from the same file, so they cannot disagree.
The ledger
| Forms and form builders | Status | How |
|---|---|---|
| Plain HTML forms | Tested Tested on every release against the builder's markup | Hidden inputs named tl_<field> or carrying data-tracelead. |
| Forms mounted by JavaScript | Tested Tested on every release against the builder's markup | Single-page apps, modals and forms rendered after load. |
| Contact Form 7 | Tested Tested on every release against the builder's markup | Native [hidden tl_<field>] tags. |
| WPForms | Tested Tested on every release against the builder's markup | Hidden fields with the CSS class tracelead-<field>, through the plugin. |
| Gravity Forms | Tested Tested on every release against the builder's markup | Hidden fields whose parameter name is tl_<field>, through the plugin. |
| Typeform | Tested Tested on every release against the builder's markup | Attribution passed as hidden fields in the embed URL. |
| Jotform | Tested Tested on every release against the builder's markup | Attribution passed as prefilled hidden fields in the embed URL. |
| Google Forms | Tested Tested on every release against the builder's markup | Attribution passed as prefilled answers in the embed URL. |
| HubSpot forms | Tested Tested on every release against the builder's markup | Raw HTML and iframe (new forms editor) embeds; hidden contact properties named tl_<field>. |
| Elementor Pro forms | Tested Tested on every release against the builder's markup | Hidden fields with the ID tl_<field>, through the plugin (1.1.0). |
| Website platforms | Status | How |
|---|---|---|
| WordPress plugin | Tested Tested on every release against the builder's markup | Prints the tag, bridges the WP Consent API and marks builder fields. |
| Webflow | Tested Tested on every release against the builder's markup | Native Form Block: hidden inputs in an Embed element, or data-tracelead as a custom attribute. |
| Unbounce | Tested Tested on every release against the builder's markup | Hidden fields named tl_<field>; the tag in the JavaScripts panel. |
| Leadpages | Tested Tested on every release against the builder's markup | Hidden fields named tl_<field>; the tag in the page tracking code. |
| Wix | Guide Documented pattern, not covered by an automated test | Wix Forms cannot be filled from page code; use an embedded form. |
| Squarespace | Guide Documented pattern, not covered by an automated test | Form block hidden fields read only the page address; use an embedded form. |
| CRMs | Status | How |
|---|---|---|
| HubSpot CRM | Guide Documented pattern, not covered by an automated test | Contact properties named tl_<field>, filled by the form; HubSpot preset. |
| Salesforce Web-to-Lead | Guide Documented pattern, not covered by an automated test | Custom lead fields by 00N id; Salesforce preset. |
| Pipedrive | Guide Documented pattern, not covered by an automated test | Through your form tool's Pipedrive integration; Pipedrive web forms cannot be filled. |
| Zoho CRM web forms | Guide Documented pattern, not covered by an automated test | Source-code web forms, inputs by API name; Zoho preset. |
| Microsoft Dynamics 365 marketing forms | Guide Documented pattern, not covered by an automated test | Hidden columns on real-time marketing forms; mapping edited by hand. |
| Tag managers | Status | How |
|---|---|---|
| Google Tag Manager | Tested Tested on every release against the builder's markup | Custom HTML tag or container import; the tag can fire after page load. |
Not listed?
If your form lives on your own page and lets you add a hidden input with a name or a custom attribute, it almost certainly works: see Installing the snippet. If it is rendered inside an iframe from another site, the embedded forms guide shows how to pass the attribution through the form's URL instead.
Using something else? Email us with the builder's name and we will say honestly whether it works today.