If your store is subject to e-Privacy / cookie disclosure regulations (EU, UK, most recently California via CPRA), you need a cookie policy. eventabee’s banner handles consent, but you still need to disclose what cookies and similar technologies are in use.
Cookies set by eventabee
_eab_vid— visitor ID, first-party, 365-day lifetime. Used to correlate events across sessions. Strictly necessary for the event pipeline._eab_consent— consent state for this visitor, first-party, 365-day lifetime. Strictly necessary — remembers the choice._eab_session— session ID, first-party, 30-minute sliding window. Strictly necessary.
Note: none of eventabee’s own cookies require consent — they’re strictly necessary for the service and do not carry marketing data. The consent state they remember gates the optional cookies set by destinations.
Downstream destination cookies
Each destination you enable may set or access cookies on your storefront. List those in your cookie policy. Typical examples:
- Meta:
_fbp,fr(marketing) - Google:
_ga,_gid,NID(analytics + marketing) - TikTok:
_ttp(marketing) - Klaviyo:
__kla_id(personalization) - Pinterest:
_pinterest_sess,_epik(marketing) - Snapchat:
_scid(marketing)
Your destinations’ own documentation is the authoritative source for their cookie names and purposes.
Sample table
| Cookie | Set by | Category | Purpose | Duration |
|---|---|---|---|---|
_eab_vid |
eventabee | Strictly necessary | Visitor correlation | 365 days |
_eab_consent |
eventabee | Strictly necessary | Remember consent | 365 days |
_fbp |
Meta | Marketing | Advertising measurement | 90 days |
_ga |
Analytics | Site analytics | 2 years |
Keep this table synced with your enabled destinations.