How to track referral to closed sale for LinkedIn Ads

Architecture

The exact event sequence

Five stages. The break is at stage three and it is a logic decision, not a technical failure. Two identifiers arrive and something has to choose. The identifier has to survive all of them.

1. Step 1

   Referral link shared

   Person to person. No campaign produced this.

2. Step 2

   Referred visitor arrives

   With a referral parameter, onto a browser that may already hold a paid identifier from last week.

3. Step 3

   Precedence decided

   The moment that determines who gets credit, and the moment almost nobody has consciously configured.

4. Step 4

   Sale closed

   Attributed to whichever identifier survived.

5. Step 5

   Reward issued

   Which frequently produces a second purchase that must not inherit the first sale's attribution.

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 closed sale, with its true origin recorded after a full real journey through every step.
• Reward issued confirmed arriving at LinkedIn Ads, verified by LinkedIn's conversion reporting, plus a reconciliation against your CRM.
• Your order or crm record, with referral and paid sources held apart 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.

• With no referral program there is no conflict, and this is an ordinary purchase funnel.
• 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 reward issued regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward sales with both source parameters retained for later analysis instead and use the later data for budget decisions rather than for bidding.
• If almost none of your closed sales by origin 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.