Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Amplitude callback isn't fired if a user enables adblock

See original GitHub issue

One of our developers enables adblock and have found that the callback of logEvent isn’t fired.

I wonder if we can make the callback fires even the sending-data-to-amplitude action fails.

Thank you

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:6 (3 by maintainers)

Top GitHub Comments

5reactions

piougcommented, Oct 12, 2020

Well in my case, I need to log events before the visitor leaves a page so opt_callback must be called.

2reactions

mattlongcommented, Apr 14, 2021

I’m still observing the behavior described in this issue. Using the JS snippet currently on https://developers.amplitude.com/docs/javascript that attempts to load version 8.1.0. With uBlock Origin enabled on Chrome v89, logEvent callbacks are not triggered when attempting to track outbound link clicks.

Related, the console.log statement from the snippet (console.log("[Amplitude] Error: could not load SDK")) isn’t actually being logged. An active ad blocker seems like a situation when when I’d expect to see it triggered.