ViewLift's Cookie Consent Manager
  • 02 Feb 2024
  • 3 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

ViewLift's Cookie Consent Manager

  • Dark
    Light
  • PDF

Article summary

ViewLift CMS has a built-in cookie consent manager that enables your website users to set their cookie and tracking preferences. Learn how it works for your website.

Cookies are small files that websites store on your computer to track your activity. Major data privacy regulations require websites to request user consent for cookie tracking that stores their data footprint. When a user's consent has been confirmed, the browser will save the data in a file called "cookie.txt" on the user's device. While the browser stores and manages cookies, the browser's internal storage is on the user's device.

Your users on the website will have the power to choose how their data is processed and whether or not they want to give permission. They will have the following options to manage cookies: 

Accept All - By selecting Accept All, users grant permission for the website and its analytics tags to store, process, and utilize their data.

Reject All - Clicking on this, users can turn off all the cookies except the strictly necessary cookies. 

Activate / Deactivate specific cookies - Users can individually activate or deactivate specific cookie categories by clicking on the Cookies settings link in the consent banner.

Users can revise their cookie preferences later at any time from the Cookie Policy page in the footer. The Cookies Settings modal will reappear for modifications.

Aside from a native consent solution, we support integration with OneTrust and Ketch if they are necessary for your specific needs. If you choose to implement OneTrust or Ketch, it will override the native cookie banner.

Cookies are categorized into three distinct types - Strictly Necessary, Performance, and Targeting and Advertising. Apart from Strictly Necessary cookies, users can choose to turn off the rest of the cookies, but to assist with your analytical and marketing efforts, all cookies are turned on by default. 

CategoryPurpose
Strictly Necessary Cookies These cookies are essential for the functioning of the website and will always remain active.
Performance CookiesLogs website usage data. Example, GA4.
Targeting and Advertising CookiesUser tracking and ad targeting purposes. GTM, CleverTap, and Facebook Pixel are all targeting cookies. 

Disclaimer

The default implementation that we provide out of the box covers all major cookies needed for functioning and tracking purposes. Our cookie functionality can currently only find and block those SDK cookies added into one of the above-mentioned cookie categories. Disabling a cookie category will automatically block all cookies within that type. 

Please note that adding cookies or tracking beacons directly into custom modules like Raw HTML or Embedded code bypasses our cookie detection and blocking mechanisms. This can lead to unintentional breaches of your cookie policy and/or applicable law., and ViewLift cannot be held liable for any liability that may result. To ensure compliance and user transparency, all cookies must be managed through the centralized consent form, preferably injected via GTM. If you have specific requirements for cookie management beyond these options, please contact our Support team for assistance.

Our cookie functionality is configured when your website is created. While the core logic resides on our backend, Tools administrators can customize the appearance of the cookie notice. This includes adjusting the color of the CTA buttons and the background overlay for the banner. The default color set for CTAs is blue and gray for overlay. 

To customize your cookie notice, go to the AppCMS module, click on Brand, open THEME, and scroll down to the VL Cookie Consent section.

To edit the text displayed in the cookie pop-up, navigate to the Template Builder > Global Settings > Generic messages.

Cookies for Mobile and TV apps

While the term "cookies" isn't commonly used for TV apps like Roku and Smart TVs, they do utilize a similar technology called Local Storage. This storage allows apps to store data on the user's device, including: 

  • User Preferences: Language, font size, and other personalized settings. 
  • Login Status: This keeps users logged in even after closing and reopening the app. 
  • Player Usage: Tracks how users interact with the app, such as play history and watchlists. 
  • Other Information: App-specific data like content progress or saved content.

While mobile apps don't rely solely on cookies for tracking, they incorporate various methods like Device IDs, App Analytics SDKs, Session ID, Click tracking, etc. We don't currently block tracking on mobile and TV apps. 

As an alternative, apps (and websites) can request VPPA-compliant consent from users. Learn how to create a VPPA screen. When the screen is integrated into your onboarding workflow, our CMS will prevent users from logging into the app unless they select the VPPA checkbox and accept the policies.


Was this article helpful?