Capture marketing attribution in MetForm forms
A standard form submission usually tells you who contacted you, but not which campaign, ad or landing page brought them in.
This integration adds that context to MetForm by using hidden fields that are completed automatically before the visitor submits.
What this integration is for
Use this page when the question is whether a MetForm lead can be tied back to the marketing that produced it. The workflow is deliberately small: hidden fields are added to the form, the integration populates them from the visitor's arrival channel, and MetForm stores the values with the submission. That makes the submission itself the record of origin, rather than a separate spreadsheet or manual tagging step.
How it works
Start by adding hidden fields to the relevant MetForm form. Those fields are the destination for attribution values, so they need to exist before any data can be captured. Next, the integration monitors the marketing channel the lead is coming from and writes the relevant information into those hidden fields. Finally, when the visitor submits, MetForm captures the attribution information — for example channel, campaign name or ad name — and sends it onward to the CRM and other tools already integrated with MetForm.
Setup checklist and troubleshooting
Before you rely on the data, check that each form has the hidden fields in place, that a test submission carries channel and campaign values through to the connected destination, and that the landing page recorded matches the first page the test visitor saw. If a value is blank, the most likely place to investigate is whether the hidden field was present on that form or whether the downstream connection is mapping the field. Keep channel data and landing page data separate in your reports: channel answers where the lead came from, while landing page answers where they first arrived on the site.
What information you get
Channel data identifies the broad source of a lead, such as Paid Search, Paid Social or Organic Search, and adds finer detail within that channel. In Paid Search, for example, the captured detail can include campaign, ad group and keyword. Landing page data records the first page the lead saw on the site, along with the category of that page, such as Blog. Together, those two groups let you report on both the media that drove the visit and the content that received it.
Where the data can be used
For CRM use, named examples include Salesforce, Zoho, Pipedrive and Insightly, so channel and content performance can be reviewed alongside leads, customers and revenue. For email marketing, named examples include Mailchimp, Campaign Monitor and AWeber, supporting subscriber analysis and more targeted campaigns. For billing, named examples include Stripe, Square and PayPal, linking customers and revenue back to the channels and content that generated them. For analytics, named examples include Tableau, Power BI and Google Data Studio, enabling reports that break key business metrics down by channel, campaign and related dimensions.
Getting started
Once attribution travels with the submission, reporting can show which channels, campaigns and ads are driving leads, customers and revenue, instead of treating form volume as the only signal. That distinction matters when deciding where to spend more, which landing pages to improve, and which campaigns to pause. Before committing budget, it is worth confirming the current plan terms, any trial period and the price that applies to your account directly with the provider, since these can change and are not fixed by this page.
| Field group | What it records | Example use |
|---|---|---|
| Channel data | Broad channel plus channel-level detail such as campaign, ad group and keyword for Paid Search | Compare Paid Search, Paid Social and Organic Search performance |
| Landing page data | First page seen and its category, such as Blog | See which entry content receives attributed leads |
Examples are illustrative of the captured groups described in the source; confirm field mapping in your MetForm connection before relying on a destination.
Frequently asked questions
How does attribution data get into a MetForm submission?
Add hidden fields to the form first, so there is somewhere for attribution values to be written. The integration then fills those fields as it monitors the channel the visitor arrived from. On submission, MetForm captures the completed values and forwards them to the CRM and other tools connected to MetForm.
What is the difference between channel data and landing page data?
Channel information covers the broad source, such as Paid Search, Paid Social or Organic Search, plus channel-level detail. For Paid Search that detail can include campaign, ad group and keyword. Landing page information records the first page the lead saw and the category of that page, such as Blog.
Which downstream tools are mentioned for the captured data?
Examples named for CRM use include Salesforce, Zoho, Pipedrive and Insightly. Email marketing examples include Mailchimp, Campaign Monitor and AWeber. Billing examples include Stripe, Square and PayPal. Analytics examples include Tableau, Power BI and Google Data Studio. Availability through a particular MetForm connection should be checked before relying on a destination.