Automated data protection
Consentmanagement.
One small box. Many problems. Not with Smarda.
Whether for analytics, marketing, or external content, your visitors must be able to choose which services they want to consent to. What sounds simple is a complex undertaking with existing plugin systems—and it is not always handled properly. Thanks to its unique all-in-one concept, Smarda connects the cookie box directly to the integrated tools and platforms. Consent management is a native part of the website and shop system, not an external tool that tries to check and control independently operating plugins.
Set up at the touch of a button
How consent management organizes itself automatically.
Smarda detects the tools and systems in use and configures the cookie box accordingly. If you add your own programs relevant to data management, you can easily add them here. The cookie box, tracking, external content, and legal texts work together in Smarda: integrated tracking pixels are linked to consent, and you assign your own services to a cookie platform. Legal text generation takes system features into account and can include details about your own integrations. You remain responsible for your own code and for checking it.
01
Platforms assigned automatically
Systems requiring consent are automatically integrated with the appropriate cookie platform. For your own service, add the relevant platform information.
02
Cookie box created automatically
The cookie box layout is created automatically based on the integrated features. It also automatically disables features when requested by the visitor.
03
Customize your cookie box
Regardless of the technically relevant features and content, you can customize the appearance of the cookie box however you like, because it also shapes the first impression of your website.
Integrated, not added on
More than a cookie banner.
A cookie box alone does not control integrations. What matters is that information, choices, and the loading of a service work together. In Smarda, these components come together in one system.
Make an informed choice
The platform name, provider, and purpose make it clear what a service is used for. Your visitors can accept or reject the services offered accordingly.
Tracking with consent
Integrated tracking connections work together with the cookie box. New tracking pixels are automatically added to the consent options.
Include external content
Link integrations that require consent to the appropriate cookie platform. For example, an assigned iframe can be loaded only after consent has been given.
Manage information centrally
Relevant details are already prepared for supported platforms. For your own services, add the information, such as purpose, cookie type, and a link to the privacy policy.
Good to know
Questions about consent management
Consent management means informing visitors about services that require consent and connecting their choices to the technical integration. So it is not just about displaying a notice; the decision must also be taken into account when services are loaded.
Typical examples include analytics and marketing services such as Google Analytics, Google Ads, or the Meta Pixel, as well as embedded YouTube or Vimeo videos, Google Maps, social media content, and external chat or review widgets. These integrations may set cookies, access information on the user's device, or transfer data to third parties. Whether consent is required depends on the specific service, its configuration, and its purpose. Therefore, check each integration individually and only load services that require consent after the appropriate consent has been given.
Because websites, shops, and service integrations all work together in Smarda, consent management is directly connected to these features. This means your visitors' choices control not only the cookie notice, but also whether services requiring consent are loaded. You do not have to coordinate the banner and technical integration using separate solutions. For external services you integrate yourself, it is important to link them to the appropriate consent as well.
With plugin systems, extensions can independently load external services, scripts, or cookies. A cookie box does not always automatically detect and control these integrations. As a result, services requiring consent may become active before consent is given. It is therefore essential to ensure that the cookie box and plugins are coordinated and checked after updates.
Yes. For your own integrations, you can assign the appropriate cookie platform and add any missing platform details. When using third-party code, always check the provider's guidance and whether consent is required for the integration in your specific case.
No. Technically necessary cookies are generally assessed differently from optional analytics or marketing cookies. The specific purpose and applicable regulations are decisive. Simply labeling a cookie as necessary is not enough.
Smarda provides technical support and helps you create appropriate privacy information. This is not a blanket legal guarantee. Complete disclosures, correctly classifying your services, and reviewing your specific use remain important. For legal questions, seek qualified advice.