Skip to content

Conversation

@NicolasGirardot
Copy link
Contributor

Add comprehensive documentation for LinkedIn CAPI native cookie support, explaining how Edgee manages li_fat_id attribution at the edge level.

Key Additions

  • New 'Native Cookie Support for LinkedIn Attribution' section
  • Documentation of cookie format, expiry, and behavior
  • Consent management modes (safe/strong/always) with examples
  • Benefits: no JavaScript required, ad blocker resistant, cross-domain support
  • Updated Getting Started to include mode setting configuration

What's Documented

  • Cookie format: _li_fat_id with format li.1.{timestamp}.{li_fat_id}
  • 90-day expiry
  • Three consent modes with detailed explanations
  • Configuration examples
  • Benefits and use cases

This documentation helps users understand how to configure and leverage edge-level cookie management for persistent LinkedIn attribution tracking.

Ref: EDGEE-875

Add comprehensive documentation for LinkedIn CAPI native cookie support, explaining how Edgee manages li_fat_id attribution at the edge level.

Key additions:
- New 'Native Cookie Support for LinkedIn Attribution' section
- Documentation of cookie format, expiry, and behavior
- Consent management modes (safe/strong/always) with examples
- Benefits: no JavaScript required, ad blocker resistant, cross-domain support
- Updated Getting Started to include mode setting configuration

This documentation helps users understand how to configure and leverage edge-level cookie management for persistent LinkedIn attribution tracking.

Ref: EDGEE-875
Clarify that LinkedIn native cookie uses last-touch attribution:
- Cookie updates when new li_fat_id appears in URL
- Credits most recent LinkedIn ad click
- Ideal for remarketing campaigns and conversion optimization

This provides transparency about the attribution model and helps users understand how LinkedIn attribution works.
Clarify that li_fat_id is stored as-is without timestamp wrapping.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants