As an introduction we’ll go through the description of the following features:
- Prior loading blocking
- Async loading after consent
- Embedded content
- Location based preferences
- Consent management
- Policy and docs
- Subjects’ requests management
- Process definition
- Widget customization
– Prior loading blocking and async loading after consent
Now, to block the script from loading in the visitor’s browser, you’ll remove it from your page and add it to your Clym account. Now every new user that visits your website will be asked to accept the Analytics script, and only after receiving consent Clym will inject the script in the page. Once accepted, on every other future visit, Clym will keep track of the user’s previous consent settings and load third party tags accordingly.
– Embedded content
– Location based preferences
Different countries have different laws, so you can customize the way the consent loader works. As an example: if your visitor comes from a country that allows cookies to be loaded prior to consent, but asks for an option to remove them, Clym allows you to set this exact behavior. The cookies will load initially but the user is given the option to OPT-OUT. Or maybe your visitor comes from a country that is outside the scope of any cookie law. You can set Clym to not even show up for these visitors, but load every third-party cookie.
– Consent management
Every time a user interacts with the Clym widget to accept or reject cookies, a consent receipt is created. The receipt can be viewed by both the visitor, and the website owner, to make proof of the user’s consent. It contains information about every cookie you have previously configured in Clym and the user’s preference.
– Policy, Terms and other Documents
– Subjects’ requests management
According to the new regulations, you need to provide your visitors a way for them to create requests like data erasure, or other types of requests. Using Clym you’re not only giving them a way to make requests, but you have a way to manage all of these requests in a single place. Working on the requests as well as closing them will also notify the user about the current status of the request.
– Process definition
Subjects’ requests might need to pass through more than a person or a department to be considered done. You can define processes for your custom needs, assigning responsible people for every stage of a request. With every status change, the current responsible will be notified to further manage the request.
– Widget customization
The appearance of the widget can be customized to meet your website’s design. There are different layouts according to every need, and colors can match your main theme. The policies and documents can also include custom css to match your preferences.