WebmasterID logoWebmasterID
UTM tracking

LinkedIn campaign tracking with UTM

LinkedIn is a high-intent B2B channel, but its mobile app and shortened links can drop the web referrer. UTM tagging keeps LinkedIn visits measurable. This page gives a recommended utm_source/utm_medium structure for organic posts and LinkedIn Ads, with the rule that no personal data belongs in a UTM.

Verified against primary sources

Recommended structure

Use one lowercase convention for every LinkedIn link you control. Separate organic from paid in utm_medium so you can compare reach against spend:

Worked example

For an organic post linking to a gated whitepaper:

https://example.com/guide?utm_source=linkedin&utm_medium=social&utm_campaign=q3-webinar

For the paid promotion of the same asset, switch the medium so the two are comparable:

https://example.com/guide?utm_source=linkedin&utm_medium=paid&utm_campaign=q3-webinar&utm_content=carousel-a

Why this matters for B2B

LinkedIn audiences are smaller and higher-intent than broad social channels, so undercounting them in a direct bucket hides your best B2B source. Tagged links survive in-app browsers and link shorteners, keeping the LinkedIn number honest.

How it appears in analytics and logs

A visit with utm_source=linkedin confirms a LinkedIn-driven click regardless of referrer. Splitting utm_medium into social versus paid lets you see organic reach separately from spend.

Diagnostic use case

Tag the LinkedIn links you control so B2B traffic is attributed reliably, separating organic posts (medium=social) from paid campaigns (medium=paid or cpc).

What WebmasterID can help detect

WebmasterID reads utm_source=linkedin at ingest and attributes the visit to your LinkedIn campaign even when the referrer is missing, so organic and paid LinkedIn traffic appears as a real source rather than direct.

Common mistakes

Privacy and accuracy notes

Keep LinkedIn UTM values generic — campaign and creative labels only. Never encode a recipient name, company, email, or account ID. UTM values are visible in the URL and logs.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.