Analytics cookies
Set only when the visitor allows analytics (see Consent).
The order tracking pixel reads
reeview_uid, reeview_lsid, and REEVIEW_SESSION, so orders are attributed only for visitors who allow analytics. For the same reason, video campaign checkouts add the visitor ID to the cart only with consent. Until a visitor accepts, their A/B test variant is kept for the current page only.
The live shopping player keeps its own reeview_uid: 1 day for anonymous viewers, 365 days for logged-in viewers.
Set only after a visitor action
These remember something the visitor did. They are never set on page load.
The player also keeps the list of submitted forms in
localStorage (reeview_completedForms) and a few display flags in sessionStorage (unmuteButtonDisplayed, swipeUpDisplayed, openCart).
Consent
Videowise follows one consent signal per page:What happens
The same rules apply on every platform. Tracking events are views, video engagement (play, watch time, sound), product clicks, add to cart, and A/B test events.When tracking starts
Right away, when:- the store has no consent banner and no consent platform;
- on Shopify, the visitor’s region isn’t in your cookie banner regions, so Shopify doesn’t ask for consent;
- with IAB TCF, GDPR doesn’t apply to the visitor;
- with OneTrust, no banner is shown to the visitor and the Videowise group is active;
- the visitor has already accepted, on this page or an earlier one.
When tracking doesn’t start
Nothing is sent and no analytics cookies are set when:- the visitor hasn’t answered the banner yet. If they leave the page before choosing, that page’s events are never sent. Clicking a product isn’t delayed.
- the visitor declined. If they accept later on the same page, tracking starts from that moment; events from before are not sent.
- on Shopify, your region settings require consent but nothing collects it, for example a consent app that doesn’t send the choice to Shopify. Check that
Shopify.customerPrivacy.analyticsProcessingAllowed()changes after the visitor accepts. - on Shopify, the consent API fails to load.
vwConsentRequiredis set butvideowiseConsentis never called.
OneTrust
Videowise listens to OneTrust’sOneTrustGroupsUpdated event, so it follows every choice, including a change made later from the preference center.
- Videowise belongs to the Performance Cookies group (
C0002). If you assigned it to another group, set its ID before the Videowise script:window.videowiseInfo.oneTrustGroup = 'C0003'. - While the OneTrust banner waits for an answer, Videowise waits too, even if your OneTrust setup is opt-out and every group is active by default. If OneTrust shows no banner to the visitor, the group decides right away.
- In OneTrust, list the
reeview_*andREEVIEW_SESSIONcookies under Performance Cookies. If you use OneTrust’s automatic script blocking, don’t categorize theassets.videowise.comscript itself: blocking it would also block the videos.
Other consent banners
Add this before the Videowise script:videowiseConsent from your banner:
On Shopify, OneTrust, IAB TCF, and
vwConsentRequired are not read: the Shopify consent always applies. On OneTrust pages, vwConsentRequired and videowiseConsent are not needed and are ignored.Related
- Order tracking pixel — how these cookies attribute checkout
- Shoppable videos order tracking —
reeview_uid - Live shopping order tracking —
reeview_lsid - Shoppable videos
- Live shopping
- React Native SDK —
getStoredDatareads the sameuidandlsIdvalues from app storage