Skip to content
TraceLead

Lead source tracking for your form builder and CRM

If your form sits on your own page and can hold a hidden field, TraceLead can fill it with the campaign, click id and channel that first brought the visitor, and your form takes it to your inbox or CRM. Below is each tool we have written up, with exactly how far it is tested.

Guide:
Documented pattern, not covered by an automated test.
Tested:
Tested on every release against the builder's markup.
Verified live:
Tested on every release and verified on a real install.

Forms and form builders

Forms on your own pages, filled through hidden fields, and embedded forms that take the attribution through their URL.

  • Plain HTML forms

    Hidden inputs named tl_<field> or carrying data-tracelead.

    Tested

  • Forms mounted by JavaScript

    Single-page apps, modals and forms rendered after load.

    Tested

  • Contact Form 7

    Native [hidden tl_<field>] tags.

    Tested

  • WPForms

    Hidden fields with the CSS class tracelead-<field>, through the plugin.

    Tested

  • Gravity Forms

    Hidden fields whose parameter name is tl_<field>, through the plugin.

    Tested

  • Typeform

    Attribution passed as hidden fields in the embed URL.

    Tested

  • Jotform

    Attribution passed as prefilled hidden fields in the embed URL.

    Tested

  • Google Forms

    Attribution passed as prefilled answers in the embed URL.

    Tested

  • HubSpot forms

    Raw HTML and iframe (new forms editor) embeds; hidden contact properties named tl_<field>.

    Tested

  • Elementor Pro forms

    Hidden fields with the ID tl_<field>, through the plugin (1.1.0).

    Tested

Website platforms

Where the tag goes on each platform, and which of its form blocks can carry the attribution.

  • WordPress plugin

    Prints the tag, bridges the WP Consent API and marks builder fields.

    Tested

  • Webflow

    Native Form Block: hidden inputs in an Embed element, or data-tracelead as a custom attribute.

    Tested

  • Unbounce

    Hidden fields named tl_<field>; the tag in the JavaScripts panel.

    Tested

  • Leadpages

    Hidden fields named tl_<field>; the tag in the page tracking code.

    Tested

  • Wix

    Wix Forms cannot be filled from page code; use an embedded form.

    Guide

  • Squarespace

    Form block hidden fields read only the page address; use an embedded form.

    Guide

CRMs

The fields to create so the attribution lands on the contact or lead record. Your form tool delivers it; TraceLead never writes to your CRM.

Tag managers

Installing the snippet from a tag manager instead of the page source.

  • Google Tag Manager

    Custom HTML tag or container import; the tag can fire after page load.

    Tested

Attribution without personal data. No names, emails, form values, IP addresses or user agents. Ever.

No privacy workarounds. Nothing before consent, no fingerprinting, no ad-blocker bypass, no cross-site identity.

Made in the UK. GBP pricing, UK consent rules in mind, and a person who answers email.

Using a tool that is not listed?

Any form that sits on your own page and accepts hidden inputs can be filled. Email us with the tool you use and we will say honestly whether it works today.

No card needed. Cancel any time.

The whole install v1.4.0
<script async src="https://app.tracelead.io/snippet/v1/tracelead.js"
        data-site="tl_YOUR_SITE_ID"></script>

<form id="enquiry">
  …your fields…
  <input type="hidden" name="tl_utm_source">
  <input type="hidden" name="tl_utm_campaign">
  <input type="hidden" name="tl_channel">
</form>