Cookie Manager in the frontend
When a user visits your shop for the first time, the cookie manager is displayed. The customer therefore has the possibility to choose which cookies he wants to allow.
Required cookies are cookies that are used by the shop system and without which the shop cannot operate. According to the guideline, no consent is required for these cookies. For this reason, this option cannot be changed by the shop visitor and is already preselected. Below you will find a list of the required cookies that are set by Smartstore.
|ASP.NET_SessionId||This cookie is set by the ASP.NET Framework when a user visits the shop for the first time. It simply stores an ID that is used by ASP.NET to identify a user's session.|
|SMARTSTORE.AUTH||This cookie is set by the ASP.NET Authentication Framework when a user logs in to the shop. It is used to identify the user who is logged in.|
|SMARTSTORE.VISITOR||This cookie is set by Smartstore the first time a user visits the shop. It is used in order to be able to assign users who are not logged in.|
This cookie is set when a user interacts with the cookie manager. The settings made by the customer are stored here
|SmartStore.RecentlyViewedProducts||This cookie stores the product IDs of the products that the customer has viewed recently.|
|sm.compareProducts||This cookie stores the product IDs of the products that the customer has added to the comparison list.|
With the help of analytical cookies, statistical web services, such as Google Analytics, collect data on the usage behaviour of a website. These data are used by site operators to improve their own website.
Third Party Cookies
Cookie Manager in the Backend
The Cookie Manager can be enabled or disabled in Admin > Configuration > Settings > Customers > Privacy. Depending on the activated plug-ins, the Cookie Manager now already displays information on cookie usage in the frontend.
To include the corresponding scripts, there is either the possibility to add them as a widget in the backend or to include them directly in views.
To mark a script that sets cookies as such, first add it to Admin > CMS > Pages. The topic must now be displayed as a widget by checking the option Display as HTML Widget. The Cookie Type option now determines whether the script is output depending on the customer selection in the Cookie Manager. Information about the cookie can be stored in the data protection settings as described above.
The scripts can also be included in views after asking whether the respective cookie type is allowed.
Within scripts you can query the status of the cookie settings made by the customer via the CookieManager object. The two properties AllowsAnalytics and AllowsThirdParty are available here. An initialisation code of a script could then look like this:
A cookie hint is only required for countries in the EU, so there is a possibility to turn off the hint at country level. To disable the cookie manager for visitors from a country, go to Admin > Configuration > Regional settings > Countries > Country and uncheck the option Display Cookie Manager