Localytics doesn't automatically capture events. Events are sent to Localytics based on tags that have been inserted into your app's code base by your app developers. When users interact with your app, event tags are like digital tripwires that can be activated when an action occurs. If a user performs an action which triggers that tripwire, Localytics creates a timestamped event.
When the number of events doesn't align with expectations, the explanation is usually one of the following: either the event tripwire is getting unintentionally triggered by unintended actions, or the event tripwire is not getting triggered by the intended action under all circumstances. In technical terms, we describe these as tags that are not considering all possible code paths.
The good news is that event tags are not a "black box." Developers can insert tags into the code base, then interact with the app, and watch to see if the tripwires are being triggered as expected. This process is called Quality Control (QA) or Auditing.
Learn more about event tags, here.