The most likely cause for an event to stop capturing data is a recent site change or release. If you recently updated your code, the original criteria set for the event, such as a CSS class, may now be out of date. This can happen to labeled and autocaptured events.
Here are some ways to fix this:
- Navigate directly to the event details page and manually edit the event criteria.
- Use visual labeling to create a new version of this event, them combine the new and old versions as a combo event.
- Use your browser’s developer tools to inspect elements on your site to check if IDs or classes have changed, then update your events accordingly. For guidance on how Heap works with relation to your frontend code, see HTML & CSS Best Practices.
- If you are using React, this may result in your CSS classes changing frequently. We recommend checking in with your developer team if this is the case, and reviewing Using Heap with React Websites.
- If you’re sending custom events or snapshots via API calls, check with your developer to ensure the client-side or server-side API calls are implemented correctly.
For a general overview of different types of events, see our Events overview guide.
You can see a list of all events which are no longer collecting data, and get help fixing them, via our event repair flow.