Quickstart
This simple guide shows you how to get started with Openli and become a better data citizen. Once you've completed this guide, you'll be ready to collect compliant cookie consent.
Watch this 6-minute video for a tour of the cookie consent solution.
You must add a domain(s) if you haven't already during sign-up. You can add multiple domains that you would like Ope to scan for cookies.
To add a domain simply go to "Settings" in the Openli dashboard (bottom left corner), and select the project in which you wish to add your cookie widget.
You must remove any existing cookie-blockers/cookie-banners before adding your domain, so that our first scan can detect your cookies properly.
If you wish to manually add your cookies instead, you can follow this guide that shows you how to manually add any cookies.
After an initial scan of your website you'll see an overview of the cookies found on your domain. You need to create your cookie providers to be able to categorise your cookies.
In the Openli dashboard, click on “Cookies” and then “Add new cookie provider”. Each cookie provider belongs to a category, and you must select only one. Make sure to choose the correct category for your provider.
Afterwards, fill in the following fields:
- 1.The name of the cookie provider, e.g. Openli
- 2.The purpose of the provider
Finally, click on the green “Save cookie provider” button and repeat this step for all your providers.
Openli scans your website for cookies, however, you must select which provider sets a specific cookie and thereby which category that cookie belongs to.
Cookies can either be in the categorised as necessary, analytical or marketing cookies. You define the cookie category via the cookie provider. This determines how the consent is collected, and whether you need to obtain consent from the website visitor before cookies can be set.
In the Openli dashboard, click on “Cookies” . If you have any uncategorised cookies, Openli asks you to categorise them immediately. Click on "Categorise your cookies".
For each cookie, you must click on the dropdown menu “Select provider” and choose the correct provider for that cookie or add a new provider if needed.
Do this for every uncategorised cookie.
You must have a cookie policy that your visitors can read when they accept cookies. This is how it looks in the Openli widget:
To create your first cookie policy, click on "Agreements" in the Openli dashboard. Click on "New agreement" and select cookie policy. Give your agreement a title and save it. Next you must write your policy.
Save your draft. You're asked to write a few notes on why you're creating/changing this policy. Add a few thoughts and click "Save Notes". If you're ready to publish your draft, click on "Publish now!" and confirm by clicking on "OK".
If you already have a cookie policy, but wish to make changes to the text, you can do so by:
- 1.Clicking on the name of the cookie policy in the overview
- 2.Click on “Update agreement”
- 3.Make the relevant changes in the text box
- 4.Click on the button “Save draft”
- 5.Write about which changes you made in the notes box (for your records)
- 6.Click on “ Save notes”
- 7.If you are ready to publish the changes click on “Publish now!”
- 8.Confirm by clicking on “OK”
Openli automatically updates your cookie policy and widget when you add new cookies or create new cookie providers if you use our tags.
Our cookie widget blocks the cookies that you need consent before setting, until the website visitor gives consent.
Our cookie widget currently uses manual categorisation to properly block cookies that are set on your website. You must make changes to your HTML to enable blocking, and for it to work properly. You can read more in this section of our developer documentation.
You will need to repeat this step if you get new cookie providers and add them to your account.
The rest of this guide is for customers with their own developed website. If your website is based on WordPress, Squarespace, Wix, or a similar website-builder, please see the separate guides in the menu on the left to find out how to install your widget.
In this final step, you'll install the widget on your website. You'll need your widget's JavaScript code snippet to do so.
To find your code snippet, go to the Openli dashboard and select "Widgets" in the side menu. Click on the cookie widget you previously created and copy the code.
It will look like this:
<script>
!function(){var i,e,t,s=window.legal=window.legal||[];if(s.SNIPPET_VERSION="3.0.0",i="https://widgets.legalmonster.com/v1/legal.js",!s.__VERSION__)if(s.invoked)window.console&&console.info&&console.info("legal.js: The initialisation snippet is included more than once on this page, and does not need to be.");else{for(s.invoked=!0,s.methods=["cookieConsent","document","ensureConsent","handleWidget","signup","user"],s.factory=function(t){return function(){var e=Array.prototype.slice.call(arguments);return e.unshift(t),s.push(e),s}},e=0;e<s.methods.length;e++)t=s.methods[e],s[t]=s.factory(t);s.load=function(e,t){var n,o=document.createElement("script");o.setAttribute("data-legalmonster","sven"),o.type="text/javascript",o.async=!0,o.src=i,(n=document.getElementsByTagName("script")[0]).parentNode.insertBefore(o,n),s.__project=e,s.__loadOptions=t||{}},s.widget=function(e){s.__project||s.load(e.widgetPublicKey),s.handleWidget(e)}}}();
legal.widget({
type: "cookie",
widgetPublicKey: "xxxxxxxxxxxxxxxxx",
});
</script>
Notice that the value for
widgetPublicKey will be different in your code snippetThe code snippet you can see in the text box needs to be copied and added to your website. If you have experience with coding, you can do this yourself. If not, the final part of the step will need to be completed by your developer or someone who manages your website. You can read more in this section of our developer documentation.
The snippet must be included immediately before the closing-tag of the
body element in your site's main template, like this:...
...
<script>
!function(){var i,e,t,s=window.legal=window.legal||[];if(s.SNIPPET_VERSION="3.0.0",i="https://widgets.legalmonsterl.com/v1/legal.js",!s.__VERSION__)if(s.invoked)window.console&&console.info&&console.info("legal.js: The initialisation snippet is included more than once on this page, and does not need to be.");else{for(s.invoked=!0,s.methods=["cookieConsent","document","ensureConsent","handleWidget","signup","user"],s.factory=function(t){return function(){var e=Array.prototype.slice.call(arguments);return e.unshift(t),s.push(e),s}},e=0;e<s.methods.length;e++)t=s.methods[e],s[t]=s.factory(t);s.load=function(e,t){var n,o=document.createElement("script");o.setAttribute("data-legalmonsten","sven"),o.type="text/javascript",o.async=!0,o.src=i,(n=document.getElementsByTagName("script")[0]).parentNode.insertBefore(o,n),s.__project=e,s.__loadOptions=t||{}},s.widget=function(e){s.__project||s.load(e.widgetPublicKey),s.handleWidget(e)}}}();
legal.widget({
type: "cookie",
widgetPublicKey: "xxxxxxxxxxxxxxxxx",
});
</script>
</body>
</html>
If you are unable to do this, you must ensure that the call to
legal.widget(...) occurs after the DOM is ready, using a combination of the DOMContentLoaded event and the document.readyState property. This reference article provides a good overview of the events involved. Contact us if you are in doubt.Congratulations on completing your first step towards collecting compliant cookie consent. Pat your self on the back and know that our privacy mascot Li is proud of you.
