Send confirmed conversions from SourceTrack to the LinkedIn Conversions API, so a deal, demo booking or sign-up can be credited to the LinkedIn campaign that started it. SourceTrack sends each one to the LinkedIn conversion rule you choose for its conversion type, or to your default rule.
Server-side sending to ad platforms is in beta. Every attempt, success, failure and skip is listed in SourceTrack so you can check what reached LinkedIn. LinkedIn decides what it accepts and how it matches it.
What SourceTrack records
- The LinkedIn click ID:
li_fat_idfrom the landing page URL, when LinkedIn added one. The standard tracker keeps the latest click ID in the browser, so a conversion on a later page of the same site can still carry it. - A delivery log: each send appears under Delivery Health as sent, failed (with LinkedIn’s status code) or skipped (with the reason).
What SourceTrack sends to LinkedIn
- The conversion rule for the conversion’s type: the per-type rule you set (for example one for leads, one for purchases), or your default rule when that type has none. Also the time of the conversion.
- Match keys: a SHA-256 hash of the email when the conversion has one, and the
li_fat_idwhen the visitor arrived with one. A conversion with neither is not sent. - The value and currency, only when the value is known. A missing value is left out, never sent as zero.
- An event ID, when the conversion has a stable one.
What SourceTrack does not do
- It does not create conversion rules in your LinkedIn account. You create them in Campaign Manager and enter their IDs in SourceTrack.
- It does not send names, phone numbers, company names, IP addresses or user agents to LinkedIn.
- It does not send a conversion the visitor declined consent for, or one from a browser that sent Global Privacy Control or Do Not Track.
- It does not send test conversions, or browser conversions that were never confirmed (see below).
Step-by-step setup
Server-side sending is not part of the free plan.
Step 1: Prepare LinkedIn
In LinkedIn Campaign Manager, create a conversion that receives data through the Conversions API and note its ID. LinkedIn recommends one conversion rule for each conversion type you want to track, so create one per type if you want LinkedIn to optimise for them separately. You also need an access token that is allowed to send conversions for that ad account.
Step 2: Add them in SourceTrack
Open Integrations → Advanced Tracking → Server-side Conversions (CAPI). On the LinkedIn card, enter the Default conversion rule ID and the Access token. The Partner ID field is optional: SourceTrack keeps it if you enter it, but never sends it.
Once connected, you can also enter a separate rule ID for purchases, leads, trial starts, subscriptions or any other conversion type you send (for example demo_booked). A type without its own rule goes to the default rule. A rule ID is the number LinkedIn shows for the conversion; SourceTrack also accepts it as urn:lla:llaPartnerConversion: followed by that number, and refuses anything else when you save.
Step 3: Confirm a delivery
After your next confirmed conversion, open Delivery Health and check that the LinkedIn row says sent.
How it works under the hood
A conversion is sent only after something SourceTrack trusts has confirmed it: a Stripe or Shopify payment webhook, your inbound webhook signed with your secret API key (for example from your CRM when a deal moves), or a CSV import by a site owner or admin who ticks the box confirming the sales are real. A conversion reported by the browser alone is held for up to 72 hours and released only when a payment webhook confirms the same order.
SourceTrack calls LinkedIn’s conversionEvents endpoint with the rule’s ID in the conversion URN. LinkedIn answers with a status code, and SourceTrack records anything other than success as failed.
Common problems and fixes
- “LinkedIn needs a conversion rule ID”. Add the default rule’s ID on the LinkedIn card. The Partner ID (the Insight Tag ID) cannot stand in for it.
- “LinkedIn needs an email or a LinkedIn click ID”. The conversion had neither, so there was nothing for LinkedIn to match. Send the email with the conversion, or check that LinkedIn ad clicks land with
li_fat_idin the URL. - A conversion is counted twice. The LinkedIn Insight Tag on your site may also record it. Record each conversion in one place only.
Related guides
- Server-side tracking explained
- Click IDs explained: gclid, fbclid, msclkid
- Troubleshooting tracking problems
- All integrations
Frequently Asked Questions
How does LinkedIn match a conversion to a member?
From what SourceTrack sends: the li_fat_id click ID captured at landing and, when the conversion has an email, its SHA-256 hash. The matching itself happens at LinkedIn.
Can I send CRM stages such as a qualified lead or a closed deal?
Yes, through your inbound webhook. Each stage goes to the rule you set for its conversion type, or to your default rule when it has none, so set a rule per stage if LinkedIn should count them separately.
Does this import my LinkedIn ad spend?
No. LinkedIn ad spend can be added to SourceTrack by CSV import.
