Disable Analytics in Sitecore 8

Question

I have a Sitecore Experience Platform (Sitecore version 8 in layman terms) that I would like to NOT use the Analytics. When I look at Sitecore Experience, analytics are all throughout. I would like to disable Analytics in a "clean" way, but for Sitecore 8 as I understand it approach is different. What is the correct approach?

Note: Yes, I know about:

<setting name="Analytics.Enabled" value="false" />

And yes, I saw the seemingly related question on Stack Overflow.

Thank you in advance!! Sasha

Answer 1

The Sitecore KB article which looks like it was published after the initial question mentions only the

<setting name="Analytics.Enabled" value="false" />

line mentioned above in /App_Config/Include/Sitecore.Analytics.config, as well as commenting out / removing the connection strings in /App_Config/ConnectionStrings.config.

<add name="analytics" connectionString="mongodb://localhost/analytics" />
<add name="tracking.live" connectionString="mongodb://localhost/tracking_live" />
<add name="tracking.history" connectionString="mongodb://localhost/tracking_history" />
<add name="tracking.contact" connectionString="mongodb://localhost/tracking_contact" />
<add name="reporting" connectionString="user id=user;password=password;Data Source=(server);Database=Sitecore_Analytics" />

It also outlines the numerous limitations which take affect because of the lack of xDB.

---

This seems to be a popular question/answer, so some updated info: for Sitecore 8.1 without xDB, this is now called "CMS-only mode" and can be enabled in a similar way - by setting Xdb.enabled to "false" in Sitecore.Xdb.config.

Answer 2

I use a dev environment where I delete all the Analytics files in the App_Config/include folder, Sitecore.Analytics.*.config instead of delete you can also rename to .disabled

It works for me But not sure of there are no issue. I also don't need any analytics connectionstring. But i don't go live with that deleted config.

Edit: It is not possible say Sitecore lots of errors in log, and some functions are broken there is a future request to make it possible in future versions.