Cookies and consent

What the HoloStep script (core.js) stores in the shopper's browser, which consent tools it reads, and how to pass your own consent answer to it.

What HoloStep stores

Name	Where	Purpose	Lifetime
holoClientId	First-party cookie	Statistics: recognises a returning shopper for your 3D statistics	13 months from the first visit; later visits never extend it
holoClientSince	First-party cookie	The first visit of holoClientId, which fixes its expiry	Same as holoClientId
holoSession	sessionStorage	Statistics: groups one visit's events	Until the tab closes
holoReportedOrders	sessionStorage	Necessary: reports each order only once	Until the tab closes

The 3D viewer, add to cart and AR need none of the statistics entries.

Keep the script out of automatic blocking

Mark core.js as necessary (or functional) in your consent tool. If the tool blocks it, the 3D viewer disappears for shoppers who haven't accepted statistics.

• Cookiebot with automatic blocking: add data-cookieconsent="ignore" to the HoloStep script tag.
• Wix: keep the custom code in the Essential category.
• ShopRenter: paste the script under Egyedi scriptek, not Egyedi marketing scriptek.
• Other tools: list the script as necessary.
• Tools that block by domain: allow both onsite.holostep.io and onsite-scripter.holostep.io. The script tag from your dashboard names onsite.holostep.io (older tags name onsite-scripter.holostep.io), and core.js loads its other files from onsite-scripter.holostep.io.

Consent tools HoloStep reads

HoloStep reads the shopper's answer from the first of these it finds on the page:

1. your own answer in HoloStep.consent (below);
2. Shopify's Customer Privacy API;
3. the WordPress WP Consent API (when a consent plugin supports it);
4. Wix's consent policy;
5. Google Consent Mode (analytics_storage, ad_storage);
6. UNAS's cookie banner;
7. Cookiebot, OneTrust (Performance group), CookieYes and Complianz;
8. ShopRenter's cookie bar, whose marketing choice also stands for statistics.

HoloStep currently records this answer with its statistics, without changing what it stores. The next step stores holoClientId and holoSession only with statistics consent and removes them when consent is refused. This page will say when that starts.

Pass your own answer

If your shop uses a tool that isn't listed, set the shopper's answer whenever it is known or changes. This works before and after core.js loads, and HoloStep reads it on every event:

window.HoloStep = window.HoloStep || {};
window.HoloStep.consent = { analytics: true, marketing: false };

Once core.js has loaded, window.HoloStep.setConsent({ analytics: true, marketing: false }) does the same and ignores values that aren't true or false.

analytics covers HoloStep's statistics; marketing covers the Google Ads, Meta Pixel and Segment events HoloStep sends when you have switched those integrations on. Your answer always takes precedence over the tools listed above.