How to track comparison page visit to demo request for LinkedIn Ads

Architecture

The exact event sequence

Five stages. Nothing breaks technically here. What breaks is the reporting: the entry page is not stored on the lead, so the best-performing traffic on the site cannot be identified afterwards. The identifier has to survive all of them.

1. Step 1

   Ad click

   Onto a comparison page, frequently from a competitor-brand keyword.

2. Step 2

   Comparison page read

   Scroll depth and time here genuinely predict intent, unlike on most content.

3. Step 3

   Demo requested

   The conversion most teams report.

4. Step 4

   Demo held

   Comparison-sourced prospects show up at a higher rate than content-sourced ones, which is worth knowing and is invisible if you stop at the request.

5. Step 5

   Opportunity created

   The outcome. Comparison traffic reaches it far more often than its volume suggests.

Diagnostic sequence

What's specific to LinkedIn Ads

The funnel logic above is the same wherever you advertise. These are the parts that change because it's LinkedIn Ads.

1. 1

   Click identifier: li_fat_id

   LinkedIn's click identifier, available where first-party tracking is enabled alongside the Insight Tag. It's the least commonly captured of the major identifiers, largely because LinkedIn is usually a B2B afterthought in a stack built for Google and Meta.

2. 2

   Import mechanism: the Conversions API

   Server-side conversions, including offline outcomes from a CRM, sent against the click identifier or matched on hashed user data. Verify the current field requirements in LinkedIn's documentation — this API is newer than Meta's and has moved more.

3. 3

   Deduplication

   Use a stable reference from your own records — the opportunity ID or lead ID — so the same conversion uploaded twice is recognised as one. Because LinkedIn conversions are frequently uploaded in batches from a CRM rather than fired in real time, duplicate uploads are a more realistic risk here than double-firing.

4. 4

   Window and timing

   LinkedIn's attribution and import windows differ from Google's and are worth reading directly. This matters more here than on any other platform, because B2B cycles routinely outrun every window available.

5. 5

   The LinkedIn gotcha

   The B2B cycle is the real constraint. LinkedIn's audience is the one most likely to take six months to close, which frequently puts the outcome you actually care about outside any import window. Plan to optimize on a qualified mid-funnel stage and use closed revenue for budget decisions rather than for bidding.

Source-of-truth validation

How to prove the chain works

One real journey, followed all the way, then a reconciliation. Neither on its own is enough.

• A live LinkedIn ad clicked, and the identifier confirmed present on the landing URL.
• The same identifier confirmed on the demo request and the opportunity it became after a full real journey through every step.
• Opportunity created confirmed arriving at LinkedIn Ads, verified by LinkedIn's conversion reporting, plus a reconciliation against your CRM.
• Your crm, with the entry page recorded on the lead reconciled against LinkedIn Ads per record over a fully closed window.
• The same reconciliation repeated 30 days later.

Straight talk

When this doesn't apply to you

Worth checking before you build anything, because two of these are common and both mean the work isn't worth doing.

• If you do not run comparison content or bid on competitor terms, there is no distinct funnel here.
• If your LinkedIn spend is small relative to your other channels, the honest answer is to get Google and Meta correct first. The same infrastructure extends to LinkedIn afterwards as an additional destination rather than a separate build.
• If your cycle from click to opportunity created regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward demo request with the entry page attached instead and use the later data for budget decisions rather than for bidding.
• If almost none of your demo requests carry a click identifier today, that's the whole project. Fix capture first — the import is the easy half and no tooling rescues a record with nothing to reference.