Why Does It Require a Refresh to Display Custom Events in Event Log?
New
We are sending custom events to FullStory and they appear to be working correctly. However, in order for them to show up in the event log for a user session, I have to refresh the FullStory session page. All other events (click, etc.) show up without refresh, but custom events do not display until after refresh. Is this expected behavior? Something else I’m missing? Thank you.
0
Comments
3 comments
Hi @willashe,
I haven’t run into this issue - do you have any API errors logged that maybe can help?
https://help.fullstory.com/hc/en-us/articles/360020624394-Troubleshooting-Client-API-FS-event-FS-setUserVars-and-FS-identify-errors
Thanks,
Hi @drozo ,
Thank you for the reply. Unfortunately we’re not getting any API errors. Again, the events display correctly but only after refreshing the fullstory page when viewing a given user session, so it appears they are being sent/captured correctly. All other events display in near real-time, but the custom events only show up after refresh. They appear in the correct order as well, e.g. if click events happen before/after the custom event, once refreshed the custom event shows up between the click events.
Hey @willashe! Thanks so much for reaching out, and thanks @drozo for jumping in! 😊
It sounds like you may be viewing live sessions. If that is the case, although sessions are generally available almost immediately after the user begins navigating your site, sessions do take a bit of time to index. So, while a refresh seems to fix an issue, this is actually an expected behaviour as these events take a bit of time to be indexed in session playback. So there is no error be fixed. 😊 This Go Live article may be worth a read.
Now, if you’re viewing an older session that has already been fully indexed and you’re still seeing this issue, we might need to take a deeper look for you!
Please let me know and I can create a support ticket on your behalf for our team to review.
Please sign in to leave a comment.