Consent and privacy
Consent modes, Do Not Track and Global Privacy Control, what is stored in the browser and what is never collected.
What is and is not collected#
Avenue Lift measures experiments, not people. It is built so that the data needed for that is all it ever receives.
- No personal data. The snippet sends a random visitor id, a random session id, the page URL, the device class (desktop, mobile or tablet), the referrer's host name, UTM source, medium and campaign, and whether the visitor is new. It does not read form fields, names, email addresses or page content.
- No IP addresses. They are not stored or logged. The visitor's country is taken from a header set at the network edge and nothing else is kept from the request.
- First-party storage only. Identifiers live in a cookie and browser storage on your own domain. There are no third-party cookies and no cross-site identifiers.
- Event properties stay in the browser. Of what you pass to
lift.track(name, props), only the name and a numericvalueare sent.
Consent modes#
Each site has a consent mode, set in the site's settings. It decides what the snippet does before the visitor has said anything.
| Mode | Before a decision | Use it when |
|---|---|---|
| none | Experiments run and are measured, unless the browser sends an opt-out signal or your page calls lift.consent(false). This is the default. | Your legal basis does not require prior consent for this kind of measurement. |
| opt_in | Nothing: no storage, no assignment, no variant, no event. The original page is shown until your page calls lift.consent(true). | You ask visitors for consent before analytics or personalization run. |
This is not legal advice
Connecting your consent banner#
Tell the snippet what the visitor decided with one call. It works with any consent tool that can run a callback:
// consentMode "opt_in": nothing is stored, assigned or sent until this call.
cookieBanner.on('accept', function () {
lift.consent(true);
});
// At any time: stops tracking, reverts applied variants and deletes
// everything the snippet stored in this browser.
cookieBanner.on('reject', function () {
lift.consent(false);
});lift.consent(true)- In
opt_inmode the snippet starts right away, on the current page: it assigns the visitor, applies the variant and begins tracking. Innonemode it re-enables a visitor who had declined. lift.consent(false)- In either mode: tracking stops, applied variants are reverted so the original page shows, queued events are dropped, and everything the snippet stored in the browser is deleted.
- The decision is remembered
- It is saved under
_lift_consentin localStorage, so a returning visitor does not need the call repeated on every page. It is the one value written without consent, because it is the record of the decision.
If your banner's code can run before the snippet has loaded, queue the decision with the pre-load array. It is replayed as soon as the snippet starts:
<script>
// Safe before the snippet has loaded: the decision is queued and replayed.
window.lift = window.lift || [];
if (hasStoredAnalyticsConsent()) lift.push(['consent', true]);
</script>
<script src="https://lift.example.com/s/lift_pk_YOUR_SITE_KEY"></script>Do Not Track and Global Privacy Control#
Each site has a setting to honor browser privacy signals. It is on by default, and while it is on a browser that sends Global Privacy Control or Do Not Track is left alone completely: the visitor gets the original page, nothing is stored and no event is sent.
- The signal wins over everything else for that page view. A call to
lift.consent(true)does not override it. - It is enforced twice: by the snippet in the browser, and again by the ingest endpoint, which drops requests that carry the signal.
- These visitors are not part of any experiment's numbers. Expect the visitor counts in Avenue Lift to be lower than in tools that ignore the signals.
When testing, remember that some browsers and privacy extensions send these signals by default. The debug panel reports the mode Blocked when that is why nothing happens.
What is stored in the browser#
All keys are first-party and start with _lift. Cookies are set with SameSite=Lax, with Secure on HTTPS pages, and expire after 365 days.
| Key | Where | Purpose |
|---|---|---|
| _lift_vid | First-party cookie, mirrored in localStorage | A random visitor id, so a returning visitor keeps their variant. |
| _lift_asg | First-party cookie, mirrored in localStorage | Which variant the visitor was assigned in each experiment (experiment id → variant id). |
| _lift_sid | sessionStorage | A random id for the tab session. |
| _lift_consent | localStorage | The consent decision given through consent(): "1" granted, "0" denied. The only key written without consent, because it is the consent record. |
| _lift_new | sessionStorage | Marks a visitor id created in this session (new versus returning). |
| _lift_exp | sessionStorage | Experiments whose exposure was already reported in this session. |
| _lift_preview | sessionStorage | The active preview, so it survives navigation in the tab. Set only by a preview link. |
| _lift_debug | sessionStorage | Debug mode for the tab. Set only by the debug link or debug(true). |
| _lift_editor | sessionStorage | The visual-editor session token. Set only when you open the editor from the dashboard. |
The last three are functional and only exist in the tab of a team member who opened a preview link, debug mode or the editor. Everything else is written only while storage is allowed: not before consent in opt_in mode, not for browsers that sent an opt-out signal, and not after lift.consent(false).
By default cookies are set for the current host. To share a visitor across subdomains — www.example.com and shop.example.com — set the site's cookie domain to .example.com.
Your visitors, your responsibilities#
Mention the measurement in your privacy notice, and list the cookies above in your cookie notice if you keep one. A visitor who wants their data gone from the browser can clear site data, or your page can call lift.consent(false) for them.
What we do with the data on our side, and for how long, is described in the privacy policy.