Blocks Google AdWords remarketing even when to configured to allow every tracker #19
Comments
|
@googleanalyticsresoneo in the screenshot you shared it looks like Ad-Blocking is enabled. Can you try disabling it by clicking on the purple stop sign in the Ghostery panel and toggling off, then try that page again? |
|
@trickpattyFH20 What about enhancing the configuration / options ? Thanks! |
|
@googleanalyticsresoneo there are already some UI changes implemented that we plan to release soon. the changes should make it more clear what's happening with the additional ad-block and anti-tracking settings |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Description
I use Ghostery to detect and list installed trackers, not to block them. Thus it is configured to accept every tracker.
But I notice an error in the Google Chrome console saying "net::ERR_BLOCKED_BY_CLIENT" which is typical of a network request being blocked by an Ad blocker
https://googleads.g.doubleclick.net/pagead/viewthroughconversion/866289170/?random=1522398994693&cv=9&fst=1522398994693&num=1&guid=ON&resp=GooglemKTybQhCsO&u_h=900&u_w=1600&u_ah=900&u_aw=1538&u_cd=24&u_his=7&u_tz=120&u_java=false&u_nplug=4&u_nmime=5>m=G3r&sendb=1&frm=0&url=https%3A%2F%2Fwww.resoneo.com%2F&tiba=RESONEO%20-%20Conseil%20en%20strat%C3%A9gie%20et%20marketing%20pour%20l%27e-business&async=1&rfmt=3&fmt=4
net::ERR_BLOCKED_BY_CLIENT
The Ghostery panels says no tag were blocked. But this isn't what happens here
Expected Behavior
Don't block any tag when configured to accept all
Actual Behavior
At least AdWords remarketing hits are being blocked on https://www.resoneo.com/
Steps to Reproduce
is canceled
as well as
https://www.google.com/ads/ga-audiences?v=1&aip=1&t=sr&_r=4&tid=UA-806633-1&cid=890926785.1522398754&jid=362213292&_v=j66&z=1861897420
with net::ERR_BLOCKED_BY_CLIENT
5. look at Ghostery panel : saying no tracker blocked
If you go to https://www.reddit.com/ you get way more trackers being blocked
Versions
Ghostery 8.1.0


The text was updated successfully, but these errors were encountered: