Manage analytics cookies directly at the edge for unified user tracking.
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.
When enabled, Edgee manages analytics cookies at the edge:
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.
You can control native cookie behavior through the compatible component settings with four modes:
Go to your project > Components > Your component, then configure the Native Cookies mode
Using strong
or always
modes may not comply with privacy regulations in your jurisdiction (such as GDPR, CCPA, or other applicable laws).
By enabling these modes, you assume full responsibility for:
Edgee provides these features as technical capabilities only. We strongly recommend consulting with your legal team or privacy experts before implementing these modes.
Native Cookies components are available for the following analytics platforms:
AMP_[API_KEY]
device ID cookie_ga
client ID cookieatid
, _pcid
, atuserid
)Each platform’s documentation includes specific details about their cookie implementation and configuration options.