8000 Feature Request: Capture `li_fat_id` from cookie for view-through support with LinkedIn Ad Conversions · Issue #33811 · PostHog/posthog · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Feature Request: Capture li_fat_id from cookie for view-through support with LinkedIn Ad Conversions #33811

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ordehi opened this issue Jun 17, 2025 · 1 comment · May be fixed by PostHog/posthog-js#2027
Open

Feature Request: Capture li_fat_id from cookie for view-through support with LinkedIn Ad Conversions #33811

ordehi opened this issue Jun 17, 2025 · 1 comment · May be fixed by PostHog/posthog-js#2027
Labels
enhancement New feature or request feature/pipelines team/web-analytics

Comments

@ordehi
Copy link
Contributor
ordehi commented Jun 17, 2025

Feature request

Is your feature request related to a problem?

According to the LinkedIn docs, capturing li_fat_id (LinkedIn First-Party Ad Tracking ID) from cookies, rather than just URL parameters, enables view-through conversion attribution for up to 30 days after a user clicks a LinkedIn ad.

PostHog’s current behavior only supports capturing li_fat_id from the URL. This means view-through conversions may be missed, resulting in lower match rates and underreported LinkedIn Ads performance.

Describe the solution you'd like

Support reading the li_fat_id value from the document.cookie store (if present) and attaching it to events as a $set_once person property or $set event property. This would allow customers using PostHog's LinkedIn Conversions destination to take advantage of improved match rates and full view-through attribution.

Describe alternatives you've considered

Today, users can manually write code to read li_fat_id from cookies and call posthog.identify() or posthog.capture() with the property, but it's easy to miss, and ideally PostHog should handle this automatically like it does for gclid and other ad click IDs.

Additional context

From: https://posthoghelp.zendesk.com/agent/tickets/32694

Debug info

null
@rafaeelaudibert
Copy link
Member

This is interesting, I'm coming up with something here. BTW, this is definitely not from Team CDP but rather work that can be done in the SDK. This feels very aligned with Marketing Analytics, currently under @PostHog/web-analytics

@rafaeelaudibert rafaeelaudibert linked a pull request Jun 17, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request feature/pipelines team/web-analytics
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: enhance campaign parameter retrieval from cookies and URL PostHog/posthog-js
2 participants
@rafaeelaudibert @ordehi
0