🍪
Bye bye, cookie prompt
We hardly knew ya
Today we bid a not-so-fond farewell to the auto-displaying cookie prompt that many folks were seeing on their public content.

What's the story?

We previously analysed public documentation using our own Google Analytics instance. This gave us useful insights that helped us improve the product. But to be compliant, we had to ask visitors to opt-in to cookies.
This meant that a bunch of public content visitors were seeing cookie prompts because we – GitBook – used GA. This was frustrating, and there was a pretty obvious solution: stop using Google Analytics on our end.
By removing our own instance of GA, we're able to ensure that public content is compliant, we lose some fidelity with our own analytics, but that's far better than forcing a prompt.

How do I enable this feature?

You don't need to do anything. If you're not using your own GA instance through the GitBook <-> Google Analytics integration, then your public docs will not show the cookie prompt any more.
You may need to clear your cache if you're still seeing a cookie prompt.

What if I use my own Google Analytics?

If you enable Google Analytics for one of your published spaces, your visitors will still see the cookie prompt, and you will be required to provide a URL to your privacy policy.