After you add the Attentive tag to your website, Attentive creates cookies to track and store analytics data to provide an optimized user experience. See below for a list of these cookies.
Note: Not all cookies are created for all Attentive customers. For more information about your specific situation, please contact our White Glove team (whiteglove@attentivemobile.com).
_attn_: This is a secure persistent cookie that contains the visitor ID and some page view and session details.
- Data stored: analytics/identity data
- Required for: encrypted long-term data for analytics/identity
- Size: 170 bytes
- Expiration: 400 days
__attentive_id: This is a unique visitor identifier that gets tied to a subscriber in Attentive. It’s used to attribute onsite events to the visitor and to govern display rules for Attentive sign-up units. This cookie doesn’t expire unless the shopper clears their browser cache/cookies.
- Data stored: visitor ID
- Required for: fatiguing – attributing events to users
- Size: 46 bytes
- Expiration: 60 years or, if GDPR compliant, 390 days
__attentive_dv: used for CCPA compliance
- Data stored: expiration cookie for deleted visitor ID
- Required for: fatiguing – used to prevent too many calls in checking deleted visitor IDs for when to rotate the visitor ID
- Size: 15 bytes
- Expiration: depending on CCPA logic, two hours or 24 hours
__attentive_ss_referrer: used to track where the user came from; primarily used for sign-up unit display logic
- Data stored: Attentive session referrer
- Required for: fatiguing – used in configurable fatigue rules based on browser referrer
- Size: 32 bytes
- Expiration: 30 minutes
__attentive_pv: used to track the number of page views in a visitor's session; primarily used for sign-up unit display logic
- Data stored: page views
- Required for: fatiguing – used in configurable fatigue rules based on page view count
- Size: 15 bytes
- Expiration: 30 minutes
__attentive_cco: used to calculate expiration
- Data stored: created on cookie
- Required for: fatiguing – Once a certain time has elapsed since this time, we rotate the visitor ID.
- Size: 28 bytes
- Expiration: 60 years or, if GDPR compliant, 390 days
attntv_mstore_email: used at checkout for attribution
- Data stored: user email
- Required for: attributing emails to users and events
- Size: varies (would be the size of a user's email)
- Expiration: 30 minutes
attntv_mstore_phone: used at checkout for attribution
- Data stored: user phone
- Required for: attributing phone numbers to users and events
- Size: varies (would be the size of a user's phone number)
- Expiration: 30 minutes
__attentive_ceid: used to identify the Attentive account- Data stored: Attentive external account ID
- Required for: identifying the corresponding Attentive account on customers who use a separate subdomain for checkout
- Size: 19 bytes
- Expiration: 7 days
__attentive_domain: used to identify the Attentive account- Data stored: Attentive regional identifier
- Required for: identifying the corresponding Attentive account on customers who use a separate subdomain for checkout
- Size: varies (would be the size of the identifier)
- Expiration: 7 days
__attentive_client_user_id: (not set by the tag) This cookie lets you pass Attentive a customer identifier that will be incorporated into the identity of a specific user.
Important: Don't send test data via this cookie. It's only for real, identifiable users.
- Data stored: Your Attentive client user ID
- Required for: attributing unique identifiers to subscribers; enables use of your client user ID in the public API
- Size: varies (would be the size of your unique identifier for a specific user)
- Expiration: dependent on your logic creating the cookie