li_fat_id first party click ID
A click ID added to ad landing page URLs and saved as a first party cookie.
In one line
Can tag your visit from a LinkedIn ad click with an ID the site saves
A click ID added to ad landing page URLs and saved as a first party cookie.
Survives third party cookie blocking and lets the advertiser's tag and API tie a later purchase to a LinkedIn ad click and member.
What it can and can't do
What the user does: You click a LinkedIn ad and land on the advertiser's page
It can
- Add a click ID to the ad link's web address
- Save that ID as a cookie on the advertiser's own site
- Match a later purchase or sign up back to your ad click
It cannot
- Exist unless you arrived by clicking a LinkedIn ad link
- Follow you to other sites, since it is saved only on the advertiser's site
- Work after you clear cookies or if the browser removes the ID
- Identify you by name; it is a code linked to the click
How it differs between platforms: Some browsers strip known click IDs from links, which cuts this off.
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Supported | Not available | None |
| Edge | Supported | Not available | None |
| Firefox | Supported | Not available | None |
| Safari | Supported | Not available | None |
| Safari on iPhone | Supported | Not available | None |
| Chrome on Android | Supported | Not available | None |
| Samsung Internet | Supported | Not available | None |
How a site asks for it
| API | ?li_fat_id=<uuid> on landing URL; cookie li_fat_id; firstPartyTrackingEnabled on the tag |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Cookie 30 days from latest ad click; member mapping stored 365 days |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Enhanced conversion tracking is on (default for new tags)
- LinkedIn appends li_fat_id to the ad's landing URL
- Insight Tag writes it to a first party cookie
- Value is sent in Insight Tag events and in the Conversions API as LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID
Data you get
What comes back: UUID
Shape: string
How often: each ad click
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
li_fat_id | string | UUID | 36 chars | unique per click |
Technical limits
- Only set for people who arrive from a LinkedIn ad
- Can be stripped by link cleaning (Safari, Brave, Firefox Strict)
The story
What it is
A click code in LinkedIn ad links, saved as a cookie to tie later actions to that click.
For you
You click a LinkedIn ad and the web address has a long code in it. The site saves that code in its own cookie, so a purchase a week later can be linked back to your click.
For makers
Third party cookies are fading, so advertisers need another way to prove an ad worked. A click code saved on the advertiser's own domain survives most blockers. It also lets the advertiser send the code back by server for a more complete count.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | You click a LinkedIn ad for project software, sign up days later, and the vendor ties the signup to that ad. | LinkedIn Ads |
| analytics | A marketing team sees the whole path from ad click to demo to deal, even when the sale takes months. | HubSpot, Salesforce |
| shopping | A business buys office chairs after clicking an ad, and the shop credits the sale to LinkedIn. | None named |
| enterprise | A sales system stores the click code with a lead, so reps can see which ad created each lead. | Salesforce, HubSpot |
| security | Safari and Firefox limit such cookies or strip known click codes, so some clicks are never matched. | Safari, Firefox |
| media | A podcast sponsor tracks signups from a LinkedIn promoted post to decide next quarter budget. | None named |
Risks
- Follows a click to a later purchase
- Survives third party cookie blocking
What the platform says
- LinkedIn: First party cookies. LinkedIn describes first party cookie tracking as a way to keep conversion measurement working with fewer third party cookies.
Good uses and abuse
Legitimate uses
- Attribute conversions without third party cookies
Known abuse
- Cross-site user matching
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
A real example: LinkedIn
Documented by Microsoft Learn enabling-first-party-cookies page.
Related capabilities
Related
- LinkedIn Insight Tag (conversion pixel on other sites). Can tell LinkedIn when you visit or act on an advertiser's site
- Conversions API (server to server events). Can send your purchases and sign ups to LinkedIn from a company's servers
Sources
How well checked: Based on official documentation.