Cookie consent on your site

Solidshop ships a cookie banner of your site’s own. It asks each visitor once, keeps the choice in a first-party cookie, runs the scripts you hold back only for the categories the visitor accepts, and tells Google tags the choice through Consent Mode. No account with a third party, nothing sent anywhere: the banner runs on your site, in your template’s colours, in the shopper’s language.

Turning it on

Go to Solidshop → Configuration → Settings, open the Cookie consent tab and set Show the cookie banner to Yes. A site built from a Solidshop quickstart has it on already. The other settings:

Setting What it does
Ask for analytics / marketing / preferences The categories offered beside the necessary cookies. Analytics is for measuring visits (Google Analytics, Matomo, Plausible), Marketing for advertising tools (Google Ads, Meta, Microsoft Advertising, TikTok). Preferences is for scripts you mark yourself, such as an embedded map or video; nothing in Solidshop uses it. Analytics and Marketing are offered by default, Preferences is not. A script of a category the banner does not offer never runs.
Banner position A box in a bottom corner (the default), a bar along the bottom, or a box in the middle of the page.
Your own sentence One line of plain text under the standard text, up to 500 characters.
Keep a choice for (months) How long a visitor’s choice is kept before the banner asks again, from 1 to 13 months; 6 by default.
Revision Raise this number when the site starts using cookies for something new. Every visitor is asked again, with a line saying that the site’s use of cookies has changed.

The banner links the privacy policy you enabled on the store’s Policies tab, the same one checkout links. Without one it shows no link.

When it asks

The banner opens only when the page has something to ask about: a script held back for one of the offered categories, a Google tag, or a tool set up in the Conversion Tracking plugin to wait for this banner. The order Solidshop publishes on the data layer is no tag and asks nothing by itself. A site that loads none of these never shows a banner, and a visitor who has chosen is not asked again until the retention runs out or the revision changes. The visitor sees Accept all, Reject all and Settings, with equal weight; nothing runs before a choice except what is necessary.

Holding back your own scripts

Write any script that should wait for consent with type="text/plain" and the category it belongs to:

<script type="text/plain" data-category="analytics" src="https://example.com/analytics.js"></script>

<script type="text/plain" data-category="marketing">
  // an inline tag
</script>

Once the visitor accepts the category, the banner runs the held scripts in page order; a script that follows an external one waits until it has loaded. Withdrawing Analytics or Marketing in the settings reloads the page without their scripts and clears the cookies the common analytics and advertising tools set; withdrawing Preferences takes effect from the next page.

Google Consent Mode

Before any tag runs, the banner sets Google Consent Mode v2’s four signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) to denied, and updates them from the visitor’s choice. A gtag or Tag Manager container on the page reads the state on its own, which Google Ads measurement in the EEA requires. You never set Consent Mode yourself.

The Cookie settings link

A visitor can change their choice at any time. Add a menu item of type URL pointing at #cookie-settings to your footer menu, or give any element the attribute data-solidshop-consent-settings; clicking it reopens the settings. A page with neither shows a small floating button once a choice exists.

For developers

On every page where the visitor has chosen, the banner fires solidshop:consent on document, with the accepted categories in event.detail.categories. window.SolidshopConsent.accepted() returns the same list (necessary always included), and window.SolidshopConsent.showSettings() opens the settings. An extension that loads tools needing consent tells the banner to ask with $document->addScriptOptions('com_solidshop.consent', ['required' => true]).

What it does not do

The banner holds only the scripts you mark; it does not scan the page for others. It keeps the visitor’s choice in their browser, in a first-party cookie named sshop_consent, and records nothing on the server. It is not an IAB TCF platform: no vendor list, no geo-targeting. Whether your site needs a banner, and which categories, is for you to read in the law that applies to you.