Skip to content

Capture marketing attribution data in Formsite forms

A Formsite submission alone usually tells you who contacted you, not how they found you.

Adding hidden attribution fields lets channel, campaign and landing-page details travel with the lead into your CRM, email, billing or analytics tools, so reporting can start from the form entry rather than a separate spreadsheet.

How the hidden-field workflow works

The workflow has three parts. First, you add hidden fields to a lead form so there is somewhere for attribution values to land. Second, the attribution tool watches the marketing channels a visitor came from and fills those fields. Third, when the visitor submits, values such as channel, campaign name and ad name move onward with the submission to a CRM or another connected tool, including analytics, email marketing or billing systems. A practical check before going live: submit a test form from a known campaign link and confirm every hidden value arrives in the destination record, not just in the form notification.

What information you get

Two groups of detail matter for reporting. Channel data identifies the broad source, for example Paid Search, Paid Social or Organic Search, plus finer detail within that channel such as campaign, ad group and keyword for Paid Search. Landing-page data records the first page the lead saw, such as a blog article URL, and the category of that page. Keeping those two groups separate helps you answer different questions: which channel brought the lead in, and which page first earned their attention.

What you can do with the data

Once attribution values are attached to a submission, they can be used to build reports showing which channels, campaigns and ads produce leads, customers and revenue. In a CRM, that supports pipeline and revenue reporting by source; the source names Salesforce, Pipedrive and AgileCRM as examples. In email marketing, subscriber origin can inform segmentation and targeted campaigns; the source names Mailchimp, Campaign Monitor and AWeber as examples. In billing platforms, it connects customers and revenue back to the marketing that generated them; the source names Stripe, Square and PayPal as examples. In analytics and BI tools, it enables breakdowns of key metrics by channel and campaign; the source names Tableau, Power BI and Google Data Studio as examples. These named tools are source-captured examples pending owner confirmation, not current guaranteed integrations. The value depends on consistent field naming across Formsite and the destination, so agree the field map before launch.

Decision checklist

Use this checklist to decide whether the setup fits your stack: 1) Your forms are built in Formsite and visitors arrive from more than one channel. 2) You can add hidden fields to each form you want to measure. 3) Your CRM, email, billing or analytics tool can accept the extra fields on submission. 4) You have a named owner for the field map and for checking test submissions. 5) You will review reports by channel, campaign and landing page, not just total submissions. If any point fails, fix that layer first; attribution data is only useful when it survives the journey from form to destination.

Attribution data captured with a Formsite submission
Data groupWhat it recordsExample use
Channel dataBroad channel plus channel-specific detail such as campaign, ad group and keywordCompare Paid Search, Paid Social and Organic Search performance
Landing page dataFirst page seen and its categorySee which pages first attract leads

Examples are illustrative, drawn from the captured evidence; confirm exact field names with the owner before implementation.