cookiebot
Forum Replies Created
-
Nice grillz btw
I checked your site, and you may have configured your GA code incorrectly.
This is how it looks like;
<script type="text/plain" data-cookieconsent="statistics">var _gaq=_gaq||[]; _gaq.push(['_setAccount', 'UA-73085602-2']); _gaq.push(['_trackPageview']); (function(){ var ga=document.createElement('script'); ga.type='text/plain'; ga.async=true; ga.src=('https:'==document.location.protocol ? 'https://ssl':'http://www') + '.google-analytics.com/ga.js'; var s=document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })();</script>You are setting
ga.type='text/plain';inside of the script tag. You shouldn’t do that. You should only mark up actual<script>as you’ve already done. Ifga.type='text/plain'wasga.type='text/javascript'before, then move it back to that.So here is how it should look like:
<script type="text/plain" data-cookieconsent="statistics">var _gaq=_gaq||[]; _gaq.push(['_setAccount', 'UA-73085602-2']); _gaq.push(['_trackPageview']); (function(){ var ga=document.createElement('script'); ga.type='text/javascript'; ga.async=true; ga.src=('https:'==document.location.protocol ? 'https://ssl':'http://www') + '.google-analytics.com/ga.js'; var s=document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })();</script>- This reply was modified 7 years, 11 months ago by cookiebot.
Finally we’ve made some videos for you:
https://www.youtube.com/channel/UChhdSqJQvxSs4uQ7MshUQsQ
Although we are aware that you managed to set it up.
I’ll go ahead and close this ticket for now 🙂
Also please have a look at our prior consent tutorial, it should get you going!
I’ll go ahead a resolve this ticket, feel free to open it again, if you are still struggling!
Hola @convospanish
Please have a look at our prior consent video, this should get you going:
Hello Athan – @dreamweavergr,
We regret that you posted this review before we had a chance to respond to your support request, which we received few minutes before this. We will then respond to both here:
Calling Cookiebot and our way of handling subscriptions a ‘fraud’ is a very strong word – especially when it is not true.
When you create a Cookiebot account you can choose whether you register the account as a private person or as a company (we have both types of customers). If you choose that you are a company, there will be appropriate fields for adding relevant company contact information as well as VAT number.
On our pricing page https://www.cookiebot.com/goto/pricing/ you will see that we offer a ‘free plan’. This is for maximum 1 domain and for a website with 100 subpages or less. On the pricing page it is clearly marked that our subscription prices are per domain and fixed by the number of subpages on that domain. You can always see the current subscription size for each domain (when the scan has completed) – this information is available on your Cookiebot account under the menu point ‘Cookies’.
If you would like to add more domains than the 1 free, then you need a premium subscription for each. This is also clearly explained in point 3.1.6 of our Terms of Service – which you accept when you open a Cookiebot account.
According to your support request, you added multiple domains that you only wanted for ‘test reasons’. If you had reached out to us and explained your need for testing Cookiebot on your domains without paying for the scans and the service, then I am sure that we would have been able to help you with this and could have provided you with a free trial. However, upgrading your account to a Premium subscription (adding your credit card), adding multiple domains for scans and then cancelling your account will result in you being charged for the services you have received.
It happens that a customer makes an honest mistake and in that case we will look into providing a refund as we have no interest in charging our customers for honest mistakes. We would however have preferred to look into this without you threatening us in the support request and without you feeling the need to warn everyone on WordPress about us.
If you’ve tagged up your GA script with text/plain and data-cookieconsent=”statistics”, then __utma, __utmb and not coming from this script, as it is not executed before a user consents to statistics.
It **must** be coming from somewhere else.
Does the report at https://manage.cookiebot.com/en/reports say anything about the “Initiator” of __utma, __utmb ? Could you also check if they are attached to a 3rd party domain?
Hi @level-level
If you change the script in VWO to type=”text/plain”, and add the data-cookieconsent attribute, as described in our help step 3, then it does not matter that the script comes before Cookiebot, as it will not be rendered before the user consents.
Hope this makes sense. Please try it yourself. If you are a developer, you are more than welcome to make an addon for VSO at our github repository. The addon is supposed to do the tagging so that you don’t have to do it manually on new updates. The repository will hopefully be released as a WP plugin soon.
- This reply was modified 7 years, 11 months ago by cookiebot.
Hi @iokinpardo
It is possible to scan pages that are behind a login.
You have to reach out to us through our helpdesk, and provide us with some more information.
What we specifically need is:
Your cookiebot account name
The authentication mecahnism
Username/PasswordPlease also link to this WP thread, so that we know it’s you.
Hi @yoanne
Resetting your password should be simple. I’ve created a video for you on how to do it
https://cybotpublic.blob.core.windows.net/cookiebot/CookiebotResetPassword.mp4
You may have copy/pasted the password wrong when you tried.
- This reply was modified 7 years, 11 months ago by cookiebot.
Get back to us when you get out of the tomb @zoricamicanovic 😛
Hi @jibberish666 and @yoanne
You can create a new page called something like “Cookie Declaration” and add the following shortcode to it;
[cookie_declaration]
This will render a full cookie-declaration, including all your cookies.
The Cookie Declaration also contains links to change or withdraw your consent.
Moreover, if you want to place those links somewhere else, then you can do so by using our API;
<a href="javascript: Cookiebot.renew()">Change your consent</a> <a href="javascript: Cookiebot.withdraw()">Revoke your consent</a>Rad more here;
What is the Cookie Declaration (cookie policy) and what is included in it?
For an example you can see our cookie-declaration.
Hi @danieliser
Thanks for the info!
Now, we’re waiting for your pull request over at
https://github.com/cybotas/cookiebotaddons –
let’s solve the worlds problems, one addon at a time! 😀
- This reply was modified 7 years, 11 months ago by cookiebot.
Please see where are the script tags which exlpains how you can identify cookie-setting tags.
Then get back to us here if you have more questions, preferably concrete with some examples.