User consent / cookie management (EN)
Managing permission levels in Squeezely
Being transparent about how you keep your customers' personal data is important to gaining their trust. An important part of being transparent is getting the visitor their permission to manage their data. Squeezely offers multiple levels that you can set per visitor. By using these, Squeezely ensures that their data is managed within their own stated permission. These permissions also affect the third party trackers that Squeezely sends data to so you shouldn't set that either.
If you're not using multi level consent, that's the equivalent of multi consent being set to 'grant' by default. This means that the data for that visitor is stored if the tracker is loaded. When activating the multi level consent setting, it means you need to explicitly forward the grant status on every page and you can also extend this on a per level basis. To set this up go to settings -> consent management and tick custom pixel consent management.
Permission levels
We distinguish between two different types of cookies, below is a list of the impact they have on your visitor.
Level | Function | Attribute Value |
|---|---|---|
Analytics cookies | Only keeps statistics and doesn't load 3d party marketing scripts. | analytics |
Cookies for Marketing | Gives permission to load 3d party scripts (Google, FB). | marketing |
Squeezely cookies
This is a list of all the cookies that Squeezely store on your website. For those cookies marked with it can be of added value to overwrite them server-side on your end. This is to avoid possible data loss due to ITP restrictions. See the ITP article for more information.
Cookie name | Function | Set server side? |
|---|---|---|
sqzllocal | The unique ID of the visitor that we use to identify him in Squeezely. | |
sqzl_vw | Information about which personalization was seen by the visitor when. |
|
sqzl_disable_personalization_<id> | Keeps track of when users explicitly click away personalizations. |
|
sqzl_session_id | Each user session is assigned a unique ID for distinction. |
|
sqzl_abs | Whether the user uses ad-block or not. |
|
Cookie consent management (multi-level consent)
Consent for Analytics and Marketing cookies is handled by the Squeezely tracker in this setting. This means that every time a page loads you have to tell the Squeezely tracker if the visitor has given permission to store cookies. For example: when a visitor visits your site for the first time, he has to give permission for cookies. As long as he does not do so, Squeezely (on the same page) will queue the events until permission is given. Once that is the case, forward your grant as shown in the examples below.
Using simple permission
Simple permission is the "all or nothing" option. Here you only send "grant" or "revoke", which allows you to keep statistics and do third party tracking. When you do revoke, nothing is stored for that visitor and no third party events will be sent from Squeezely.
_sqzl.push({
"consent": "grant"
}); |
or
_sqzl.push({
"consent": "revoke"
});
Make full use of multi level consent
You can also choose to make a distinction between analytics and/or marketing cookies. You would then ask this explicitly in your cookie banner and, based on the chosen options, send a variant of the code below
_sqzl.push({
"consent": "grant",
"permissions": [
"analytics",
"marketing"
]
}); |
You can also send revoke when the visitor changes his settings:
Manage Email Permission
Besides browser behavior, we also support three different permission levels for what can happen to a visitor's email address. We explain these below.
Name | Function | Attribute Value |
|---|---|---|
Marketing | Permission for sharing with third parties such as Google and FB. | marketing |
Newsletter | Permission to send a newsletter. | newsletter |
Service messages | Permission to send essential service emails. | service |
Use Email Consent Levels
Retaining email permission works differently to the permission above: it is stored on the profile. This means you only need to forward it once unless there is a change in consent. For this you can use the following EmailOptin event. (You can also send a "yes" permission with other events like purchase e.g., but a "no" permission can only be sent with this event).