Unlike uMatrix, uBlock Origin (uBO) can't foil cookie headers. For privacy-minded users it is strongly suggested to...

• Enable "Block third-party cookies and site data" in "Content settings" / "Cookies".
  • It works very well: see "Outbound cookies" in this benchmark results.
  • But this may break some sites. For instance, you won't be able to enter comments on YouTube.
  • Useful to know: the block also applies to local storage, not just cookies.
• Enable "Click to play" in "Content settings" / "Plug-ins".
• Disable "Predict network actions to improve page load performance", as this causes DNS queries to be made even for blocked network requests (see issue #232).

These command line switches might be of interest to privacy-minded users:

• --disable-component-extensions-with-background-pages
  • "Disable default component extensions with background pages" (ref)
  • This seems to prevent Hangout Services to be launched by the browser as a background process. Even in Chromium there is such a process launched even if you do not use Google's Hangout.
  • With other Chromium-based browsers, maybe more stuff would be disabled, you decide whether this is good or bad.
• --disable-background-networking
  • "Disable several subsystems which run network requests in the background" (ref)
• [add more switch of interests whenever new ones are found]

Another powerful command line switch is:

• --host-rules="MAP *.google-analytics.com 0.0.0.0","MAP *.googleadservices.com 0.0.0.0","MAP *.doubleclick.net 0.0.0.0","MAP *.googletagservices.com 0.0.0.0"
  • This switch maps those hostnames (or any other ones) to the IP address 0.0.0.0 (ref) and hence blocks them effectively (even on the Chrome Web Store where extensions like uBO are disabled). [via archive.org]
  • However, note that blocking those hostnames with that switch might break some websites. That's why blocking them with uMatrix is preferable since you can whitelist them as exceptions for those websites which won't work without them. Alternatively, you could use the important filter option mentioned below.

In case you were not aware, using EasyPrivacy doesn't protect completely against Google Analytics. So if you were using Adblock Plus (ABP) with EasyPrivacy (as recommended by the EFF), you might have thought you were protected against Google Analytics. This is not necessarily the case.

If you are using uBO, it protects you more against Google Analytics out of the box -- via "Peter Lowe's Ad server" list. Yet, given that an exception filter may exist somewhere in one of the many lists, blocking Google Analytics (or similarly ubiquitous hostnames) is not possible with preset filter lists.

However, in uBO 0.5.5.0 a new filter option important was introduced with the consequence that corresponding exception rules are ignored. Example: Adding

||google-analytics.com^$important

to "Your filters" blocks Google Analytics regardless of existing exception rules. You can restrict this rule to specific domains like

||google-analytics.com^$important,domain=example1.com|example2.com

Or to all third-parties:

||facebook.com^$important,third-party
||linkedin.com^$important,third-party

It's unclear why this one is not blocked by Fanboy Annoyance, as the list already blocks many other Twitter widget-related stuff. So if you use above list, you may want to add the following to your filters:

||platform.twitter.com/widgets.js$third-party

Each time you visit a site which pull cute little avatar images aside (typically) a commenter's name, there is a corresponding request to Gravatar's website, and the HTTP referer header contains the site you are visiting. The tracking potential is too much for me, so I block all these requests:

||gravatar.com^$third-party

It's unclear if, and how much this breaks things. But will prevent your browsing habits to be disclosed to gravatar.com. We can live without these cute thumbnails, can't we?

But this applies to any domain which is ubiquitous enough, gravatar.com is just one example among so many.

To deal with this easily, uMatrix is the best tool, as to blocklist a ubiquitous domain with 100% certainty is simply a matter of point and click.