Cookies & storage
Client Side Cookies
Name | Lifetime | Description | Is flag secure | Is flag SameSite | If deleted | |
---|---|---|---|---|---|---|
pa_vid | 13 months by default, can be configured | Visitor ID | ✅ | SameSite=lax | New cookie set, new visitor ID assigned | |
pa_uid | 13 months by default, can be configured | User ID | ✅ | SameSite=lax | No persistence of user ID information in events | |
pa_privacy | 13 months by default, can be configured | Privacy Mode persistence | ✅ | SameSite=lax | No persistence of Privacy Mode, privacyDefaultMode configuration assigned |
Server Side Cookies
Name | Lifetime | Description | Is flag secure | Is flag SameSite | If deleted | |
---|---|---|---|---|---|---|
idrxvr | 13 months | Legacy Server Side Visitor ID | ❌ | ❌ | New cookie set, new visitor ID assigned | |
atidx | 13 months | Secured Server Side Visitor ID | ✅ | ❌ | New cookie set, new visitor ID assigned | |
atid | 13 months | Main Server Side Visitor ID | ✅ | SameSite=none | New cookie set, new visitor ID assigned |
Piano Analytics Mobile SDKs
Coming Soon
Our iOS and Android SDKs are coming soon
Legacy cookie management
If you're migrating from SmartTag SDKs to Piano Analytics SDKs, we still use the atuserid
cookie (visitor identification) so as not to cause a break in the detection of the visitor. As soon as this atuserid
cookie is deleted, we replace it with pa_vid
cookie.
The atauthority
cookie (Privacy) is not used anymore. Please implement Privacy methods to deposit the new pa_privacy
cookie instead.
Same applies for legacy atidvisitor
cookie ("identified visitor" detection, now "user"). Please implement Users methods to deposit the new pa_uid
cookie instead.