Skip to main content

Hi there Amplitude Community!

When using Amplitude Web SDKs, it is possible that some users’ events are not ingested into Amplitude due to ad blockers. Currently, we are not able to estimate the percentage of events that do not get ingested as we do not have the data to support it. 

While we do not offer official support for circumventing ad-blockers, our Engineering Team has provided a workaround - run a reverse proxy through your own domain. Please note that it is best that this process is done by an Engineer or a Developer as this is a technical workaround.

Details on what a proxy service is and how to use it in this setting can be found here:

https://www.docs.developers.amplitude.com/analytics/domain-proxy/

Hope this helps! 

----- please give this post a thumb-up if you find it helpful! This will help us know what content we should publish in the future 🙂 -----

Amplitude Team

Hi!

The solution is quite interesting, so I implemented it on my existing nginx.

Now, is it possible to get rate limited when all our events come from the same IP? After a few days of using the proxy, I notice a high failure rate on the proxy route, with 403 errors. Some of those 403 errors contain error messages from ElasticSearch, when we don’t even have one instance of ES installed.

So I’m wondering if those are coming from Amplitude or from a misconfiguration issue. Does any of you have an idea about that? 

Thanks. 

We have a high number of users on the Android app who don’t fire FE events but do fire BE events. Is there a similar solution for Android? 

Reply


Terms & ConditionsCookie settings