Capture LinkedIn Ads Data in FormAssembly
LinkedIn can be useful for B2B lead generation because its targeting covers company size, job title and seniority, but clicks and visits alone do not prove value. This guide shows how to attach campaign information to each FormAssembly submission, pass it onward to a CRM or spreadsheet, and report leads, customers and revenue by the LinkedIn activity that produced them.
Why connect ad data to the form submission?
Clicks show that an ad attracted attention. They do not show whether the resulting enquiry became a lead, a customer or revenue. Because LinkedIn advertising can be costly, the useful question is what happened after the click.
The workflow below connects three pieces: the ad URL, the visitor's browser and the form submission. UTM values identify the campaign and ad. A small site script classifies the visit and stores those values. Hidden fields then carry them into FormAssembly with the person's name, email and other answers. From there, native FormAssembly connections or an intermediary such as Zapier can forward the record to a CRM or another tool.
Four steps to capture the data
Use this sequence before sending live traffic:
- Tag every LinkedIn destination URL consistently.
- Install the attribution script on the website.
- Add the matching hidden fields to the FormAssembly form.
- Submit a test enquiry from a tagged LinkedIn URL.
- Check that channel, campaign, ad and landing-page values appear beside the test lead.
- Connect the form to the CRM or spreadsheet and repeat the check in the destination system.
For LinkedIn, the source's suggested pattern is UTM_Medium=paidsocial, UTM_Source=linkedIn, UTM_Campaign=[name of campaign] and UTM_Term=[name of ad]. Replace the bracketed values with the actual campaign and ad names, and keep the same naming style across campaigns so reports do not fragment. Free UTM-building tools can help assemble the URLs.
How the attribution script preserves source data
The attribution script is placed on the website. When a visitor arrives, it examines how they reached the site, assigns a marketing channel such as Paid Social, and stores the source information in a browser cookie. When a form is completed, the script writes that stored information into hidden fields on the form.
That cookie step matters for multi-page journeys. Suppose someone clicks a LinkedIn ad, lands on the homepage, selects Contact Us and submits a form on a separate page. A method that only reads the current page URL may have nothing to pass through. Because the original values were stored earlier, they can still be added to the later submission.
What to do with the captured record
Once submitted, the FormAssembly record can contain both the person's details and the LinkedIn campaign information. Sending that record onward makes it possible to group results in a CRM, spreadsheet or dashboard.
Useful starting reports include leads by LinkedIn Ads, leads by individual campaign, customer numbers and revenue from LinkedIn Ads. The same captured source data can also cover other channels, including Organic Search, Organic Social and Paid Search, giving a fuller picture of where all leads originate.
Landing-page data adds a second reporting dimension
The script also captures the landing page and landing-page category. For example, a page path under /blog can be grouped as blog content. When that information reaches the CRM, reports can show which articles or content sections produced leads and customers, not only which ad campaign produced them.
This distinction helps separate two decisions: whether LinkedIn is generating valuable enquiries, and whether the page those enquiries landed on is doing its job.
Three reports to build first
Leads by channel: Group monthly leads by Organic Search, Paid Search, Paid Social and other captured channels. This high-level view helps compare LinkedIn with search and organic activity before deciding where to shift budget.
Customers by campaign: Group closed customers by LinkedIn campaign. This shows which campaigns produce customers rather than only enquiries, making it easier to expand the strongest campaigns and reconsider weak ones.
Revenue by ad type: Group revenue by LinkedIn ad type. The source lists sponsored content in the newsfeed, sponsored messaging through InMail Ads and text ads in the sidebar. Comparing revenue across those formats can support budget decisions aimed at lowering cost per lead.
Worked example: from ad click to revenue report
A practical example: a visitor clicks a sponsored-content ad tagged with a specific campaign and ad name, browses the homepage, then submits a contact form. The submission should carry Paid Social, the campaign name, the ad name and the original landing page into FormAssembly. After the record reaches the CRM, that person can be counted in the campaign's lead total, later matched to a customer record, and included in revenue reporting for sponsored content.
Before relying on the reports, test the full journey with a tagged URL and a different submission page. If the values survive navigation and appear in the CRM, the setup is capturing the intended attribution path.
Wrap up
Capturing LinkedIn source data at form submission turns an expensive click channel into a measurable pipeline source. Tag the ads, preserve the values across site navigation, add them to FormAssembly hidden fields, forward the completed record, and report by channel, campaign, ad type and landing page. That combination supports decisions based on leads, customers and revenue rather than visits alone.
Frequently asked questions
What is the shortest check that the setup works?
Tag each LinkedIn destination URL with consistent UTM values, install the attribution script on the site, add its hidden fields to the FormAssembly form, and submit a test form. Confirm the campaign, ad, channel and landing-page values arrive with the lead record before connecting the form to a CRM.
Why can UTM values disappear before a form is submitted?
A direct URL-only approach can lose the parameters when the visitor moves to another page before submitting. Storing the source values in a browser cookie preserves them until a later form submission on a different page.
Which reporting view should I build first?
Use channel for overall mix, campaign for customer counts by LinkedIn campaign, and ad type for revenue by sponsored content, sponsored messaging or text ads. Those three views answer different budget questions and should not be treated as interchangeable.