We offer various options in our platform for opt-in and cookie handling. Please note that this page does not provide legal advice as each use case is unique. It's essential to read and understand our Data Processing Addendum and consult legal experts before acting.
However, allowing cookies can unlock additional features. Two options exist for assigning Unless cookies to users:
- Visitors to your website can opt-in and consent via your consent mechanism by using our Consent API.
- Our Identify API allows users who log into your product to be identified - in that case we assume legitimate interest.
- A/B testing requires persistent control group membership tracking, so you need some form of user identification.
- Certain audiences that segment traffic into audiences are persistent across page visits in a session, so you need to be able to recognize a visitor across pages.
- As a logged-in user, you can use the associated user profile to make components show or hide, or use any other personalized actions. For example, you can highlight features of a more expensive plan to people who are in a cheaper plan only.
Assuming that you use our APIs properly, the system is smart enough to decide when certain experiments or components can be shown or not. So, it will show only "cookieless experiences" to people who did not consent or logged in - while your experiments and advanced audience segmentation will only happen after cookies have been explicitly allowed.
Which cookies may Unless use?
Assuming that your user either consented or is identified by logging into your system, you can see the following cookies appearing.
This cookie contains a reference number for a website visitor. It will only be set after explicit consent of the visitor, using the native cookie consent mechanism. The reference identifier allows for a visitor to be a member of specific audiences over a longer period of time, including (but not limited to) a control group for A/B testing. Audience memberships may result in consistent experiences to be shown on the website. The cookie will expire after a year, or when the visitor withdraws consent, or when the visitor deletes their cookies.
This cookie contains a reference number for a website session. It will only be set after explicit consent of the visitor, using the native cookie consent mechanism. The session identifier is not used to identify a visitor, but rather to monitor if certain goals are met in the same visitor session (like buying a product after a few page views). This will reflect in statistics and A/B test results.
The session cookie will be automatically deleted when the visitor session ends, or when the visitor withdraws consent, or when the visitor deletes their cookies during a session. When a visitor comes back to the website, there will be a new session cookie set with a new session reference (under the condition of visitor consent).