Native Cookies components can be used to maintain consistent user identification between Edgee and the analytics platform’s JS SDK. These components are particularly useful when you’re using both a client-side analytics JavaScript SDK and its Edgee component version simultaneously, as it ensures consistent user tracking across both implementations. These components are only available for Google Analytics, Amplitude and Piano Analytics for now.Documentation Index
Fetch the complete documentation index at: https://www.edgee.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
How It Works
When enabled, Edgee manages analytics cookies at the edge:- For new visitors, Edgee generates unique identifiers and sets the appropriate cookies
- For returning visitors, Edgee reads the existing identifiers from cookies
- These identifiers are automatically included in all events sent to your analytics platforms
Be careful, with this feature, Edgee is able to unify user ID across JS SDK and Edgee’s component, but it’s not able to unify user sessions.
Using this feature could lead to duplicate user sessions in your analytics platforms.
Configuration
You can control native cookie behavior through the compatible component settings with four modes:
- safe: Cookies are only set after user consent is explicitly granted (default)
- strong: Cookies are set unless user explicitly denies consent
- always: Cookies are set regardless of consent status
Supported Platforms
Native Cookies components are available for the following analytics platforms:- Amplitude: Manages the
AMP_[API_KEY]device ID cookie - Google Analytics: Manages the
_gaclient ID cookie - Piano Analytics: Manages various cookies based on configuration (
atid,_pcid,atuserid)
