Skip to content

Capture LinkedIn Ads data in Fluent Forms in 4 steps

LinkedIn can generate enquiries, but clicks alone do not show which campaign produced a lead, customer or revenue. This guide explains how UTM tagging, hidden form fields and browser-stored attribution data can carry that context through to a Fluent Forms submission and onward to a CRM.

1. Tag the ads and prepare the form

Start with the destination URL for each LinkedIn ad and append UTM parameters that identify the medium, source, campaign and term or ad name. A consistent naming pattern matters more than the exact labels: use the same values every time so later reporting can group results reliably. For example, the pattern illustrated in the source material uses paidsocial for medium, linkedIn for source, a campaign name for the promotion, and the ad name for term. Build the URLs with a UTM builder if that helps keep the format consistent.

Next, open the Fluent form and add hidden fields for each attribution value you want to receive. In Fluent Forms, the Hidden Field type is dragged from the Advanced Fields section into the form. Hidden fields do not need to be completed by the visitor; their values are supplied when the form is submitted. Add only the fields you will actually map and report on, and keep their names stable so CRM mappings do not break when the form is edited.

2. Install attribution code so the context persists

Install the attribution code on the website. When a visitor arrives, the code reads the UTM values from the landing URL, assigns the visit to a marketing channel such as Paid Social, and stores that information in a cookie in the visitor's browser. When the visitor later submits a form, the stored values are placed into the hidden fields and captured with the submission.

This cookie step is the key difference from simply reading UTM parameters on the landing page. If someone clicks a LinkedIn ad, lands on the homepage, then moves to a quote page and submits there, the original campaign context is still available. Without persistence, that context would be lost because the submission page URL no longer contains the ad parameters.

3. Verify the captured data and send it to the CRM

After a submission, check the Fluent entry to confirm that the hidden fields contain the expected source, campaign and ad values. Then forward the submission to the CRM using Fluent's native integration or a connector such as Zapier. Map each hidden field to a dedicated CRM field rather than appending the values to a free-text note, so the data can be filtered and grouped in reports.

Run a test journey before launch: click a tagged LinkedIn-style test URL, browse to a different page, submit the form, and verify both the Fluent record and the CRM record. Also test a direct or organic visit to confirm that non-LinkedIn channels are labelled separately instead of being merged into Paid Social.

4. Report on leads, customers and revenue

Once attribution fields are present on every lead, reporting becomes a matter of grouping the right field. Leads by channel gives a portfolio view across Organic Search, Paid Search, Paid Social and other sources. Customers by campaign shows which LinkedIn promotions produced closed business, not just enquiries. Revenue by ad type separates sponsored content, sponsored messaging and text ads so budget can be shifted toward the format that produces value.

Landing page and landing page category add another useful dimension. They show whether a blog section or an individual article is contributing leads and revenue, which helps distinguish a campaign that generated traffic from content that actually converted that traffic.

Failure modes to check before you trust the numbers

A common failure is tagging the ad but forgetting the hidden fields, which means the UTM values never reach the form. The opposite failure is adding hidden fields without installing the attribution code, leaving them empty. A third failure is relying on the landing URL alone, which breaks when the visitor submits from another page.

Use this checklist before going live: every LinkedIn destination URL has UTM parameters; naming is consistent across campaigns; hidden fields exist on every conversion form; the attribution code is present on all pages where visitors may land; a multi-page test submission populates the fields; CRM mappings use dedicated fields; and reports group by channel, campaign and ad type. If any item fails, fix it before judging campaign performance, because missing attribution will understate LinkedIn results.

Three reports to build after capture
ReportPrimary groupingDecision it supports
Leads by channelChannelWhere enquiries originate across the full marketing mix
Customers by campaignLinkedIn campaignWhich promotions produce closed customers
Revenue by ad typeAd typeWhich LinkedIn format deserves more budget

Use only when the corresponding attribution fields are captured on the lead record.

Frequently asked questions

What is the shortest setup sequence?

Add UTM parameters to each LinkedIn ad, add hidden fields to the Fluent form, install the attribution code on the site so it stores channel information in a browser cookie, then submit a test form and check that the hidden values arrive with the submission before forwarding them to your CRM.

Why does a visitor who browses several pages still get attributed correctly?

Because the attribution information is stored in a cookie when the visitor first lands, it can still be added when they submit a form on a later page. Without that persistence, a visitor who lands on the homepage and submits elsewhere would lose the original campaign information.

Which reports are most useful once the data reaches the CRM?

Useful breakdowns include leads by channel, customers by campaign, and revenue by ad type. Those views separate overall channel performance from the specific LinkedIn campaign or format that produced the result.