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!
Data discrepancy between our DB and Amplitude
Best answer by Saish Redkar
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.
+10We 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?
+10It 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.
+1Data discrepancies between your database and Amplitude happen pretty often. One common reason is event delays since Amplitude processes data differently, sometimes with batching or ingestion lag. Another thing to check is whether your database stores raw events while Amplitude applies filtering or sampling, which can change the numbers. Also, if User IDs aren’t set consistently, some events might get assigned to different users. Try comparing raw event logs from both to spot where the difference comes from.
+1A few things that could be causing it—event delays, since Amplitude might process data in batches, filtering differences where Amplitude excludes bots or applies sampling, or user identification issues if some events don’t have a consistent User ID. Best way to troubleshoot is to pull raw event logs from both and compare timestamps to see where the numbers start to diverge.
Reply
Welcome to the Amplitude Community!
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. You can also create a Guest account below!
If you're a current customer, select the domain you use to sign in with Amplitude.
analytics.amplitude.com analytics.eu.amplitude.comWelcome to the Amplitude Community!
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. Want to sign up as a guest? Create a Community account.
If you're a current customer, select the domain you use to sign in with Amplitude.
analytics.amplitude.com analytics.eu.amplitude.comEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.