Skip to content

Capture marketing attribution in FormAssembly forms

FormAssembly shows what a visitor submitted, but not reliably where that visitor came from.

This integration adds that missing context: when a lead arrives through a campaign, the channel and campaign details travel with the submission into the systems already connected to FormAssembly, so reporting can start from the form record rather than from a separate spreadsheet.

How it works

The workflow has three stages. First, add hidden fields to a lead form so there is somewhere for attribution values to land. Second, the attribution tool watches the marketing channel a visitor arrived through and fills those fields automatically. Third, FormAssembly captures the completed values on submission and forwards them to the CRM and other tools already integrated with it.

A practical check before going live:

  • Confirm every form that should carry attribution has the hidden fields in place, not only the homepage form.
  • Submit a test visit from a known campaign link and verify the channel, campaign and landing-page values appear on the resulting record.
  • Check the destination system, not just FormAssembly, to confirm the values arrived in the fields your reports will use.
  • Repeat the test for each major channel you buy or publish through, because detail available for paid search differs from detail available for organic search.

What information you get

Two groups of information are captured.

Channel data identifies where a lead came from, such as paid search, paid social or organic search. For paid search, the capture also includes finer detail such as the campaign, ad group and keyword, which is what makes it possible to judge individual campaigns rather than only broad channels.

Landing-page data records the first page a lead saw on your site, along with the category of that page. Knowing whether a lead entered through a blog article, a product page or a campaign page changes how you interpret the same channel value.

Field and control map: the visible form fields collect what the visitor types; the hidden fields added for this integration carry the attribution values. The protected form-controls-contract module defines the exact form controls for this page and should be used as supplied at implementation, rather than recreating its fields from this summary.

What you can do with it

Once attribution values are stored with each submission, they can be used in the systems where leads, subscribers, customers and revenue are already tracked:

  • CRM: send the values into Salesforce, Zoho, Pipedrive, Insightly and similar systems to see which channels and content produce leads, customers and revenue.
  • Email marketing: send them into Mailchimp, Campaign Monitor, AWeber and similar tools to see which channels produce subscribers and to support more targeted campaigns.
  • Billing: send them into Stripe, Square, PayPal and similar tools to connect channels and content with customers and revenue.
  • Analytics: send them into Tableau, Power BI, Google Data Studio and similar tools to build reports broken down by channel, campaign and related dimensions.

For example, a paid-search lead whose record carries the campaign, ad group and keyword can be compared directly with an organic-search lead whose record carries only the channel and landing page. That difference in detail is a feature of the channel, not a data error, and reports should be designed with it in mind.

Reporting on what drives results

Use the captured values to build reports showing which channels, campaigns and ads are driving leads, customers and revenue. Start with the questions you actually need to answer: which channel produces customers rather than only enquiries, which campaign produces revenue, and which landing pages convert best. Then check that each report field exists on the destination record before relying on the report.

Customer perspective

Customer example worksheet

Record a customer example you can verify. Leave unknown fields blank until you have supporting evidence.

FieldYour details
Customer and permission to use the example________
Problem and starting point________
Configuration or actions________
Measurement period________
Outcome and supporting evidence________
Approval to publish________

Get started

You can begin with a free account and move to a paid plan when your needs grow. Before choosing a plan, check the current pricing page for the plan tiers and monthly cost, and review the signup flow for any trial length, eligibility conditions or limits that apply to your account.