Skip to content

Capture marketing attribution in Netlify forms

If your Netlify site collects leads through forms, you can record where each visitor came from before they submit.

Hidden fields carry channel, campaign and landing-page details through to your CRM and other tools, so reports can connect enquiries to the marketing that produced them.

Why attribution belongs on the form record

A Netlify form submission on its own usually tells you who contacted you and what they asked for, but not which campaign, ad or organic result brought them to the page. Attribution capture fills that gap at the moment of submission.

The workflow has three parts:

  • Add hidden fields to the lead form so attribution values have somewhere to travel.
  • Let the attribution tool detect the visitor's marketing channel and write the result into those fields.
  • Send the completed submission onward, with channel, campaign, ad and landing-page values attached, to the systems where leads are managed and reported.

That sequence matters because the data is attached to the form record itself. When the record later becomes a contact, opportunity, subscriber or customer, the origin information can travel with it instead of living in a separate analytics report.

Setup checklist

Use this checklist before relying on the data in reports:

  • Identify every lead form on the Netlify site that should carry attribution, including contact, demo and newsletter forms.
  • Add the required hidden fields to each form; a form without them cannot pass the values through.
  • Confirm the fields are present in the submitted data, not merely visible in the form builder.
  • Map each hidden field to the matching field in your CRM, email platform, billing system or analytics tool.
  • Test with visits from different sources, such as paid search, paid social and organic search, and check that channel and campaign detail change appropriately.
  • Check the first landing page and its page category are recorded for the test submissions.
  • Review a completed record in the destination system to confirm the values arrived under the expected field names.

A common failure is treating a successful form submission as proof that attribution worked. The submission can succeed while the hidden fields are empty, mis-mapped or overwritten. Always inspect the destination record.

What information is captured

Two groups of information are captured.

Channel data identifies the broad source, such as Paid Search, Paid Social or Organic Search. For paid search, the detail can extend to campaign, ad group and keyword, which makes it possible to compare performance below channel level.

Landing-page data records the first page the lead saw on the site and the category of that page, for example a blog article. This distinguishes a visitor who entered through educational content from one who landed directly on a product or contact page.

Together, channel detail and landing-page detail answer two different questions: which marketing activity produced the visit, and where that visit began on the site.

Where the data can be used

Once attribution values are attached to form submissions, they can be routed to the tools already used to manage leads and revenue.

For CRM use, destinations named in the captured evidence include Salesforce, Pipedrive, Zoho and HubSpot. The purpose is to see which channels and campaigns generate leads, customers and revenue inside the same record.

For email marketing, destinations named include Mailchimp, Campaign Monitor and AWeber. Attribution attached to subscribers can show which channels and content produce subscribers and support more targeted campaigns.

For billing, destinations named include Stripe, Square and PayPal. Linking origin data to payment records helps show which channels and content generate customers and revenue.

For analytics and business intelligence, destinations named include Tableau, Power BI and Google Data Studio. Those tools can combine attribution with other metrics to produce reports broken down by channel, campaign and related dimensions.

Choose destinations based on where decisions are made. If pipeline is managed in a CRM, map the fields there first. If revenue analysis happens in a BI tool, ensure the same channel and campaign values are available there so reports use consistent labels.

Example: from visit to report

For example, a visitor arrives through a paid search campaign, lands first on a blog article, and later submits a contact form. With attribution capture, the resulting lead record can show the paid search channel, the campaign and keyword detail, and the blog landing page. A report can then compare that lead against an organic search visitor who landed on a product page, rather than treating both enquiries as identical in origin.

Getting started

Before committing to a plan, check the current pricing page and trial terms directly, since commercial details can change. A practical way to evaluate fit is to run a small pilot: add the hidden fields to one or two live Netlify forms, submit test entries from a few different sources, and confirm that channel, campaign and landing-page values arrive correctly in your CRM or reporting tool. If the data lands where you expect and the reports answer your channel questions, the setup is working as intended. Sign-up and trial options are listed on the provider's own signup page, so confirm the current offer there rather than relying on second-hand figures.