This article will help you:
- Troubleshoot for missing events, event properties, or user properties
Sometimes you want to use an event or property for an analysis but can't find it. Even if the data was successfully sent to Amplitude, there could be several reasons why it is not showing up. This article will discuss a few of these scenarios, including how best to troubleshoot for each one.
The instrumentation limit has been met
If your project's instrumentation limit has been met, data for any event types and event or user properties that exceed the limit cannot be queried from Amplitude. You'll only be able to access it by exporting raw data via a CSV file or Amplitude's Export API.
You can try to get back under the limit by deleting unneeded event types in Amplitude Data. Once you are under the limit, it will take approximately 24 hours for the new event types, event properties, and user properties to appear in Amplitude.
Data has been hidden, blocked, or deleted
The expected data may have been hidden, blocked, or deleted. Make sure you understand the differences between those actions, and double check whether or not one of these actions has been setup against your missing data. If desired, you can modify a hide, block, or delete action from your main branch to ensure the data is ingested properly moving forward.
NOTE: Hidden or blocked events and properties will count towards your project's instrumentation limit, whereas deleted events and properties will not.
The data may also be named in a way you do not expect, or have a display name you're not familiar with. If you need to adjust the name, learn about making retroactive changes to your data in this help center article.
Hidden events
Sometimes an event may be visible in an event stream but not in a chart. This could be because of a filters, like a drop filter mentioned previously, or because the event was previously hidden from view via Amplitude Data, as seen in this image.
NOTE: Events and properties can also be hidden from drop-downs, Pathfinder results, and Personas charts.
Schema doesn't include unplanned data
The missing data might be considered unplanned. This means the data conflicts with your current schema settings, and Amplitude doesn't know what to do with it. Double-check that your project's tracking plan is set up to receive unplanned events or properties. If it is not, Amplitude will not store the event or its properties.
Data ingestion or access is delayed
If you can see the event or property data for some users and not others, the ingestion of your data may be delayed. For example, if you are using a Mobile SDK to send data to Amplitude, there is no way to guarantee that the events appear as soon as they are logged - a user may not have been connected to the internet or the SDK's event upload threshold may not have been met.
NOTE: By default, Amplitude's Mobile SDKs have an event upload threshold of 30 seconds or 30 events. Until an event threshold has been met, the event data will not be sent.
Modified user properties
New or modified user properties sent via the Identity API or another integration can be seen immediately on a user's profile, but will not be accessible in a chart until the users trigger another event. This is because user property values are applied to events, and will not be shown until users trigger events after the user property is applied. Read more about user and event properties in Amplitude.