li_fat_id
LinkedIn First-Party Ads Tracking UUID
How it works
With enhanced conversion tracking via first-party cookies switched on in Campaign Manager, LinkedIn adds ?li_fat_id=... to the landing page URL when someone clicks an ad. The Insight Tag stores the value as a first-party cookie of the same name. LinkedIn's Conversions API accepts the li_fat_id as an identifier, alongside the hashed email address.
Why it matters
LinkedIn campaigns are mostly B2B, and there leads give their work email. Their LinkedIn account, though, often runs on a personal address. The hashed email then matches no member, and only the click ID connects the conversion to the ad. TSO reads the li_fat_id from the URL, or else from the Insight Tag's cookie, and sends the person's latest LinkedIn click through the Conversions API with every conversion.
Example
A software company promotes a white paper. Anna clicks the ad and downloads it with anna.berger@company.com. She signed up for LinkedIn with a personal address. Six weeks later she books a demo. The email alone doesn't help LinkedIn, but the stored li_fat_id does: the demo counts for the campaign that brought the click.
Common mistakes
- Enhanced tracking not enabled: without the setting in Campaign Manager, no li_fat_id arrives.
- Relying on email alone: work addresses rarely match the LinkedIn account. The click ID belongs in the event too.
- Expecting a li_fat_id from Lead Gen Forms: with forms inside LinkedIn, nobody visits your website. There the form's lead ID plays this role.