By setting Include Content to com_content you're having it output on every content component view that outputs onContentAfterDisplay trigger. I can't help you in regards to articles anywhere as depending on how they output articles that may indeed output a comments stream.

For front page and article view only you can set context to: com_content.article,com_content.featured

Default value is com_content.article (or empty) and is still working fine in my tests on Joomla 3.7.0.

Ok, so your only issue is with the Articles Anywhere usage. My guess is they're directly outputting the article view, which is going to have the com_content.article context. They'd need to have their own view that has a more specific context or doesn't fire that trigger. There's nothing I can do about that from CB Activity though. The below is the results of my test with Joomla views using com_content.article context.

Featured:


Blog:


Article:


The only thing determining if comments should show is the context and that's based off whatever the trigger is sending.

No, it's the opposite. I don't want to use it on Articles Anywhere, I was explaining that IF I activate it on 'com_content' it appears on published articles set up by Articles Anywhere, in non-published modules.

That's because the com_content context covers all views in Joomla for com_content output.

I ONLY want to use it on the 'normal' articles. But it doesn't show up with the 'contexts' youve provided.
I'll pm you the credentials to show it, it's visible here: www.dkdb.dk

Then it's a problem with how you're outputting articles. I do not test it with articles anywhere. I test normal Joomla views. It is not tested with K2 either.

Having reviewed your install I don't understand the issue. When I view an article directly I see the comments perfectly fine. See PM where I've provided links to articles with working comments. Your home page is outputting the Category Blog view. That is not the Featured Articles view. If you want comments on your home page you need to use "com_content.category", but that may have unexpected output. There is no context specific to blog view.