Versions Compared

Old Version 1

changes.mady.by.user vTranslator

Saved on

compared with

New Version 2

changes.mady.by.user Cherlain Gajapersad

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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)

...

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.

Code Block
languagejs
  _sqzl.push({
            "consent": "grant"
        });

or

Code Block
languagejs
  _sqzl.push({
            "consent": "revoke"
        });

...

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

Code Block
languagejs
      _sqzl.push({
            "consent": "grant",
            "permissions": [
                "analytics",
                "marketing"
            ]
        });

You can also send revoke when the visitor changes his settings:

Code Block
languagejs
      _sqzl.push({
            "consent": "revoke",
            "permissions": [
                "analytics",
                "marketing"
            ]
        });

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).

Code Block
languagejs
_sqzl.push({
          "event"      : "EmailOptIn",
          "newsletter" : "yes",
          "marketing"  : "no",
          "service"    : "yes"
        });