Skip to content
TraceLead
Start free trial

Unbounce and Leadpages

The tag and hidden fields on landing pages built with Unbounce or Leadpages.

Overview: Unbounce, Leadpages

Unbounce and Leadpages render their forms on the page they host, so TraceLead fills hidden fields there exactly as on any other site. The values arrive in the builder's lead list and in every integration it sends leads to.

Status: tested on every release against each builder's published form markup (tests/e2e/fixtures/unbounce.html, leadpages.html). Not yet verified on live pages; see the integrations ledger.

Before you start

The domain the landing page is published on must be one of your site's allowed domains in TraceLead (for example go.example.com or the builder's preview domain while you test). The first touch is stored per domain, so a visitor who arrives on the landing page directly is attributed there; a separate main site on another domain keeps its own record.

Unbounce

  1. Add the snippet. In the page builder, open JavaScripts → Add new JavaScript, paste the TraceLead tag and your consent call from Installing the snippet, and set Placement to Head. To use it on every page, add it under Settings → Script Manager instead.
  2. Add hidden fields. Edit the form, add a Hidden Field per value and set its Field name and ID to tl_channel, tl_utm_campaign, tl_source, and so on. Leave the default value empty.
  3. Publish and check a submission under Leads.

Unbounce can also fill a hidden field from a URL parameter of the same name. TraceLead's value replaces that when consent is given, so the first touch wins even when the visitor returns later without UTMs.

Leadpages

  1. Add the snippet. Open Page Settings → Tracking Code and paste the TraceLead tag and your consent call into the Head section. Site-wide code goes under the site's settings in the same way.
  2. Add hidden fields. In the form widget, choose Add hidden field for each value and name it tl_channel, tl_source, tl_utm_campaign, and so on, with no value.
  3. Publish and check a submission in Leads or in the connected integration.

Field names

The names must match your site's field mappings in TraceLead; tl_<field> is the default, and the full list is in Installing the snippet. If the builder lets you set a custom attribute instead, data-tracelead="<field>" works with any name.