it seems you really don't understand the idea of a process principle
if you block third party code calls, you block ALL third party code calls, including Google's ones to call ads - which is their main purpose and is the main reason for blocking the third party calls, to stop the ads. The fact it also stops other third party code calls that include sending you to places to get malware is an added benefit.
Now, it seems I've mentioned this process a few times already, but you seem either unable to comprehend the concept or totally uninterested in the idea of people NOT getting ads or malware. We've been around this bush too many times, so I'll reiterate the main point of the original post that relates to the initiating blog - -
When testing a web site works the way you want it to, you need to include checks to test it still works when people have set up security measures that are outside the unsecure default settings most systems come with. In this case I pointed out the police recommended actions of stopping the operation of ALL third party cookies and third party code calls as well as including the use of settings to limit ads via this same process and included some specific third party code calls - such as Googleapis and Google Analytics. Like it or not, it's a way to cut back on paying to have someone force feed ads to your system, and since we pay for each MB downloaded, it saves the users money as well.
