Skip to main content
Videowise uses cookies to count video views, count each view once, and connect an order to the shopper who watched. We don’t use cookies for advertising, and we don’t store names, emails, or other personal data in them. Videos always load and play, whether or not the visitor accepts cookies. Consent only changes what Videowise stores and measures.

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). 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 the visitor accepts, events from the current page are sent at that moment, so they are recorded with the time of acceptance.

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.
  • vwConsentRequired is set but videowiseConsent is never called.
Up to 200 events wait per page; later ones are dropped until the visitor chooses.

OneTrust

Videowise listens to OneTrust’s OneTrustGroupsUpdated 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_* and REEVIEW_SESSION cookies under Performance Cookies. If you use OneTrust’s automatic script blocking, don’t categorize the assets.videowise.com script itself: blocking it would also block the videos.
For IAB TCF, Videowise reads purpose 1 (store and/or access information on a device). Add this before the Videowise script:
Then call videowiseConsent from your banner:
Call videowiseConsent on every page load once the visitor has made a choice, and again whenever they change it. Until it is called, Videowise stores and sends nothing. Use vwConsentRequired only if your banner calls videowiseConsent.
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.
For the full policy, see videowise.com/privacy.