There are a few questions to ask if you have trouble tracking events in Intercom:
Have I tracked more than 120 events?
You can track up to 120 active events. After that limit is exceeded any new events you try to track will not be stored and will return an error. You can archive any unused events to make way for new ones. Keeping within this limit will help reduce the noise in your workspace, making it easier for you to filter and segment users.
Am I sending duplicate events?
Each event is identified using the following data:
The event name
The created timestamp
The user that triggered the event
The workspace the user belongs to
Any two events that have the same values for those fields will be treated as the same event. As such, we don't store subsequent copies of the event after receiving the first copy.
Am I trying to track or view events on a company?
Events are only tracked at the user level. There are no company level events.
How long has it been since the event was tracked?
Events should appear in the user profile as soon as you track them, although the UI is not updated in real time, a browser refresh is required.
It can take up to 24 hours for event metadata to appear in message filters:
Am I sending nested metadata?
If you send events with nested metadata, containing multiple keys and values (like an object), the metadata will be visible in the user list, but it will not be usable in messages.
You may actively track up to 120 events at a time. Events can be archived to avoid hitting the limit.
If you have a large number of events (even archived ones), you may see performance issues when loading the events settings page.
The REST API has a rate limit of 500 calls per minute, so a maximum of 500 user actions can be tracked per minute in one workspace. If this limit is hit, the API will return an error.
With either method, if you send more than 20 pieces of event metadata they won’t be received by Intercom.