Installation and first run

The basic setup takes about 15 minutes. The longest part is reviewing the list of scripts (step 5).

1. Download the module in your customer account under My account → My modules. The license file is already included in the package.
2. In the PrestaShop admin, open Modules → Module Manager and click Upload a module.
3. Select the downloaded ZIP file. Once it is uploaded, install the module.
4. Click Configure next to the module.

The banner and the settings window link to a policy page. Create it:

1. Open Design → Pages and add a new page (e.g. “Cookie Policy”).
2. Describe which cookies the shop uses and what for. The list of services in the Scripts (Skripty) panel and the settings window, which shows the cookies of each service, can help.
3. Publish the page.

Under Configure next to the module:

1. In the Settings (Nastavenia) section, choose the page in the Cookie Policy page field. Check the Banner position and the texts.
2. In the Google section, leave Google Consent Mode v2 on. If your shop inserts Google Tag Manager (GTM) through the theme or another module, leave the Google Tag Manager field empty. Otherwise enter its ID (GTM-XXXXXXX).
3. Click Save.

Open several pages of the shop (home, category, product, cart). The module detects which scripts they load and records them in a list. It does this at most once every 10 minutes, so the list may not be complete right away.

1. In the Scripts panel, go through the list. For each service and module check the category (Functional, Analytics, Marketing), or leave Do not block.
2. Turn on Block scripts before consent and save.

A detailed description is in Script blocking.

Open the shop in an incognito window of the browser (no stored consent):

• The banner appears.
• Until you accept, advertising and measuring tags must not run. Check in the browser tools (Network / Application → Cookies).
• After clicking Accept all, the tags run.
• Try changing the choice via Cookie settings in the footer.

The module license is perpetual and valid for one paid domain, its subdomains and local copies. The price includes 12 months of updates and support, which can be extended.

• You can see the license status in the last License panel in the module settings. You can also upload a new .lic file there.
• Without a valid license the module does not work. The settings show only the License panel.
• Moving to another domain: the module keeps working for another 14 days with a warning, then it switches off. You change the domain in your customer account (My account → My modules).
• When the 12 months of updates end, the module keeps working; you just do not receive new versions.
• Multistore is supported if all shops run on the licensed domain or its subdomains (e.g. eshop.sk and wholesale.eshop.sk).
• At most once a day (when you open the settings) the module checks the license and looks for new versions. It sends only the license number, the domains and the versions of the module, PrestaShop and PHP.

If a new version is available and your updates are active, the License panel (the last panel in the module settings) shows an Update to X.Y.Z button.

1. Click the button and wait. Do not close the page; it takes a few minutes at most.
2. The module downloads the new version from moduly.webvision.sk, checks it and installs it.
3. The original version is saved as a backup. If the update fails, it is restored automatically.

What is new in the version is shown in the What’s new drop-down in the same panel.

• Major versions (e.g. from 1.x to 2.0) may change behavior or settings. Read the changes before updating; the link is next to the button.
• If several WEB Vision modules have a new version, the Update all WEB Vision modules button updates them at once.
• If updates have ended (the 12 months are over), the module keeps working. You can download a new version after extending your updates in your customer account.
• Rolling back: the Roll back version button is in the License panel under Details.
• An overview of available updates is on the Module updates page.

Uninstalling the module deletes its settings. Consent records remain in the database as an archive.