If you can’t see an event you expected to see in a specific users event history, it could have several reasons:
Cache
The most common reason would be, that the event happened very recently (e.g. in the last minutes or so). We have a bit of a delay for the display of the event history in the user profile directly, because data needs to get transfered between different internal systems/databases, to have the best overall performance for each use case. The user profile is partly cached, so it might take a few minutes, until an event appears there.
Tipp: check the global event stream instead, because that shows incoming events in realtime (but later more).
Event doesn’t exist
It could also be that the system doesn’t know this particular event yet, or it was misspelled and therefore the API declined it. In this case the sending environment receives a status code 400 for the API call and “UNKNOWN_VALUE”, but it won't be visible anywhere in the App.
If a new event need to get created, please contact our Customer Experience team (ActivatePro Support) so they can create this event for you.
Wrong user
Especially if website tracking is involved, it sometimes happens that the tracked events are connected to another XNG user, e.g. when the user is not logged in yet, or if there is a misconfiguration.
If you use our Tracking SDK2, please look here to check what XNG user id is active in your session, or if the event actually fires.