Skip to main content
LinkedIn · Checkout → purchaseUse-case guide

How to track checkout to purchase for LinkedIn Ads

Everything between checkout starting and the order existing is where ecommerce tracking actually fails, and it fails differently depending on how your checkout is built. A hosted payment page is a different domain. A wallet payment can complete without the customer ever seeing the confirmation. Both produce orders in your store that no platform ever hears about. On LinkedIn Ads the specifics that matter are the click identifier (li_fat_id), the import mechanism (the LinkedIn Conversions API), and deduplication relies on a conversion identifier you supply, so a stable business reference is what makes it work. The chain only works end to end if the identifier is captured on landing and stored on the order record in your store — no cookie survives the gap between checkout started and purchase sent with the order id.

Free30 minutesNo obligation

Specific to LinkedIn × Checkout → purchase

LinkedIn: B2B checkouts that end in an invoice, not a card

On LinkedIn, send the purchase through the LinkedIn Conversions API from the order record when the order is created, matched on li_fat_id saved at checkout or the buyer's hashed work email, with the order ID as the conversion identifier. For invoice or purchase-order checkouts, decide whether placement or payment counts as the conversion.

LinkedIn rarely drives consumer checkouts, so the cases worth building for are B2B: software bought by card, equipment, training seats, trade supplies. Those checkouts often don't end in a card payment. They end in a request for an invoice, a purchase order or net-30 terms, and the money arrives weeks later. Choose which event is the LinkedIn conversion: the order placed, which is fast and in-window, or the invoice paid, which is truthful but may land outside it.

A sane setup sends the order placement as the conversion through the Conversions API, with value, and keeps paid revenue for your own reporting. If you upload paid invoices instead, use the order ID as the conversion identifier so a re-run of a batch upload doesn't count an order twice, which is the realistic duplicate risk on LinkedIn.

Checkout identity is the usual break. The person who clicked the LinkedIn ad is often not the person who checks out; procurement or finance completes the order with a different email. li_fat_id saved on the cart at checkout start is the only link that survives that handoff, and it only exists if first-party tracking was on when the click landed.

LinkedIn · Checkout → purchase · what breaks

Where this funnel usually breaks — LinkedIn · Checkout → purchase

  1. 01

    Wallet payments skip the confirmation page

    Shop Pay and PayPal can be abandoned after the money moves. The order is real; the page view never happened.

  2. 02

    A hosted payment page on another domain

    Session splits, the click identifier doesn't cross, and the purchase gets credited to your own site as a referral.

  3. 03

    Every payment method assumed to behave the same

    Card, wallet and redirect gateways each return differently, and the untested one is where the missing conversions are.

LinkedIn · Checkout → purchase · the fix

What working looks like — LinkedIn · Checkout → purchase

  • Purchase sent with the order ID attributed to the click

    Weeks later if necessary, because the identifier lives on the order record in your store rather than in a cookie.

  • LinkedIn bidding fed the real outcome

    Via the Conversions API, so it optimizes toward completed orders rather than toward checkout starts.

  • A reconciliation that closes

    Your store's order records, web orders only matched per record against what LinkedIn Ads reports, over a fully closed window.

LinkedIn · Checkout → purchase · architecture

The exact event sequence — LinkedIn · Checkout → purchase

Stage three is the one you often can't instrument, which is precisely why stage four has to be the source.

  1. 1

    Checkout started

    Browser-side, with value. The last point you reliably control the page.

  2. 2

    Payment info submitted

    Worth splitting out — it turns one opaque step into a diagnosable one.

  3. 3

    Payment authorised

    Often on someone else's domain, and frequently invisible to your tags entirely.

  4. 4

    Order created

    From the order webhook. This is the only step that sees every order regardless of how payment happened.

  5. 5

    Purchase sent with the order ID

    Deduplicated on that ID, with refunds wired to reverse.

LinkedIn · Checkout → purchase · diagnose

What's specific to LinkedIn Ads

  1. 01

    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. 02

    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. 03

    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. 04

    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. 05

    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.

LinkedIn · Checkout → purchase · prove

How to prove the chain works — LinkedIn · Checkout → purchase

Source of truth

your store's order records, web orders only

  • The same identifier confirmed on the order record in your store after a full real journey through every step.
  • Purchase sent with the order ID confirmed arriving at LinkedIn Ads, verified by LinkedIn's conversion reporting, plus a reconciliation against your CRM.
  • Your store's order records, web orders only reconciled against LinkedIn Ads per record over a fully closed window.

LinkedIn · Checkout → purchase · free audit

What we check in the free audit

  • Click identifier: li_fat_id
  • Import mechanism: the Conversions API
  • Deduplication
  • Window and timing
  • The LinkedIn gotcha

Checked against

your store's order records, web orders only

Get my free conversion tracking audit

Free30 minutesNo obligation

LinkedIn · Checkout → purchase · when not to buy

When this doesn't apply to you — LinkedIn · Checkout → purchase

  • If your checkout is entirely on your own domain with no wallet options and a confirmation page every customer reaches, the browser-side event may genuinely be sufficient — reconcile a closed week and find out before building anything.
  • 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 purchase sent with the order id regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward payment info submitted instead and use the later data for budget decisions rather than for bidding.
  • If almost none of your orders carry a click identifier today, that's the whole project.

LinkedIn · Checkout → purchase · what we deliver

The implementation, on LinkedIn Ads

  • Capture li_fat_id on landing

    li_fat_id requires first-party tracking to be enabled with the Insight Tag. Add it to your capture list explicitly — it's the identifier most often missing entirely, because the capture code predates LinkedIn being in the mix.

  • Persist it to the order record in your store

    Set a first-party cookie server-side before the hop, and pass the identifier into the payment domain where the provider supports it — where it doesn't, the order record is the only path.

  • Send purchase sent with the order id from the record

    The order webhook fires once per order, independent of which payment path the customer took or whether they ever saw a confirmation page.

  • Deduplicate and reverse

    Deduplication relies on a conversion identifier you supply, so a stable business reference is what makes it work. Refunds reverse from the refund webhook; failed and cancelled orders should never have counted in the first place.

FAQ

LinkedIn · Checkout → purchase questions, answered

Usually the order placed, because it arrives inside LinkedIn's window. Track invoice payment in your own reporting and reconcile the two monthly.

Free · 30 min

Get checkout to purchase tracked properly on LinkedIn Ads

Free30 minutesNo obligation