Skip to main content

Hello!

I’m looking to brainstorm solutions for a data discrepancy issue I have between my website’s production database and Amplitude. The discrepancy is with an event we call “Article View”. Our DB tracks an article view on the backend, and originally I setup Amplitude tracking on the frontend. The difference was quite surprising (several thousand view difference), so I decided to track this event on the server and in the same block of code where we track article views for our database. This has produced much better results, but there is still a difference in event volumes (only ~200 event total difference now). 

Has anyone else had a similar issue and found a fix? Is this type of problem to be expected? Would really appreciate any help, thanks!

Hi @Scott Kieronski 

We encounter this quite frequently and one of the most common reasons we suspected is the presence of some extensions/ad blockers on the user’s browser. This can block some frontend events based on what library is being loaded / not loaded. There could be other reasons as well, but this seems to be the major one.
Hope this helps.

Thanks Saish,

I can definitely see that affecting amplitude output too. Would extensions/ad blockers affect server-side events as well?

It shouldn’t normally. Only in cases when a device id sends too many events in a short time, then the HTTP API throttles the events. This can cause some event loss if error handling isn’t in place.

Reply


Terms & ConditionsCookie settings