Skip to content

Capture Marketing Channel Attribution in Unbounce Forms

A landing page form is often the only moment where a lead's marketing context is still visible to your stack.

Recording that context at submission means the lead record itself can later answer which channel, campaign and landing page produced a customer. This guide describes the hidden-field approach to that problem on Unbounce forms, what values it can carry, and how to tell a broken setup from a misconfigured one.

How the hidden-field workflow fits together

The setup depends on three things lining up: containers in the form, values written into those containers, and a destination that keeps them.

Start with the form. You add fields that visitors never see, and those fields become the slots where attribution values are stored. Next, a script running on the page works out the visitor's marketing context and fills those slots before the form is sent. Finally, on submission, the stored values travel with the rest of the form data into your CRM, analytics or email platform.

It helps to separate the two ways this breaks, because they look similar in a CRM record but have different causes. If a hidden field is absent from the live form, the value has no slot and never arrives — the submission looks complete but the attribution column is blank. If the field exists but the script did not run, the slot arrives empty. A missing field is a form-building problem; an empty field is a script or page-load problem. Checking which one you have saves time before you touch your CRM mapping.

What data the form can carry

Two families of values are described for this setup.

Channel data. The channel a lead arrived through — Paid Search, Paid Social, Organic Search and similar — plus finer detail inside that channel. For Paid Search, the campaign, ad group and keyword are captured alongside the channel itself.

Landing page data. The first page the lead saw on your site, together with a category for that page. A blog article URL would arrive next to a page category such as Blog.

Both families live in form fields, so both can be forwarded to whatever receives the submission. That is the mechanism that makes downstream reporting possible: the record identifying the lead also identifies the marketing context behind it.

Where the data can go

The captured values are not tied to one destination. On the CRM side, submissions can carry attribution into systems such as Salesforce, Zoho, Agile and Capsule. On the email side, the same values can reach Mailchimp, Campaign Monitor, AWeber and others.

The payoff differs by destination. In a CRM, channel and campaign fields let you report on which marketing produced leads, customers and revenue. In an email platform, the same fields let you segment subscribers by how they arrived and target campaigns to that context.

Before you trust the reports

  • Confirm every hidden field you need exists on the live form, not only on a draft variant.
  • Submit a test entry from a known source and check the values land on the destination record.
  • Verify the field mapping in your CRM or email tool — a correctly captured value can still be dropped by a misconfigured mapping.
  • Check that page category values match the labels your reports expect.
  • Re-test after any form rebuild or page migration, since hidden fields are easy to lose in a redesign.

Turning captured fields into reporting

Once channel, campaign, ad and landing page values sit on the lead record, reports can group leads, customers and revenue by those fields. The value is cumulative: one submission tells you little, but a consistent set of records lets you compare channels and content against outcomes rather than against clicks alone.