Cookies

NotifyVisitors stores first-party cookies only. All cookies are stored with the prefix _nv.

NotifyVisitors does not save any user's Personally Identifiable Information (PII) data in cookies.

COOKIES	DESCRIPTION	DOMAIN	EXPIRATION	SECURE	SAMESITE
Common Cookies
_nv_uid	To store user identifiers. This is a unique id generated by NotifyVisitors for each user.	example.com	2 years	True	Lax
_nv_did	This is a unique id generated by NotifyVisitors as a device_id to identify the same device for returning users.	example.com	1 year	True	Lax
_nv_sess	To track new sessions for each user.	example.com	30 mins	True	Lax
_nv_hit	To track session level activities being performed by each user on NotifyVisitors channels like push, pop ups, forms.	example.com	6 months	True	Lax
_nv_hit_uid	To track user level activities being performed by each user on NotifyVisitors channels like push, pop ups, forms.	example.com	2 years	True	Lax
_nv_utm	To store the traffic source or campaign through which the user visited the website.	example.com	30 mins	True	Lax
Push Specific Cookies
_nv_push_subscribe	Push subscription id of user subscribed to the browser push.	example.com	1 year	True	Lax
_nv_push_error	User denied browser push notification.	example.com	1 year	True	Lax
_nv_push_domain	Domain from which user subscribed to browser push.	example.com	1 year	True	Lax
_nv_pu_clid	To track conversions after engagement on push notifications by the user.	example.com	30 days	True	Lax
Popups Specific Cookies
_nv_banner_x	To track popups closed by the user.	example.com	6 months	True	Lax
_nv_ba_clid	To track conversions after engagement on popups by users.	example.com	30 days	True	Lax
Forms Specific Cookies
_nv_form_x	To track forms closed by the user.	example.com	6 months	True	Lax

Note

We do not set “HttpOnly” attribute on cookies because all our cookies are set on browser using javascript.