How best to track Customer Errors?

  • 8 February 2024
  • 2 replies

Hi all, I was looking for some advice or wisdon on how best to capture (and then measure) Error Messages.

For context, i would like to capture every error message we display to our customers so we can determine the most common ones and measure the impact of UX tweaks.

I have never fired an event via API before so wanted to check if using trackEvent() is using best practise or if there is a better way.. example might be:

FS('trackEvent', {
  name: 'errorMessage',
  properties: {
    errorCode: '101',  
    errorMessage: 'Your bet can not be placed due to insufficient funds',  

and then some easy questions... If i was to arrange this development, would i then be able to:
1. Create metrics based on the properties, ie most common errorCodes?
2. Search for sessions by trackedEvent name (ie “errorMessage”)?  
3. 2. Search for sessions by property name?   (ie errorCode=”101”)

Thank you for passing on any wisdom in advance,

2 replies


Hey Steve! (@Flashmac)


Great question — you're definitely on the right track. FS.event would be the best solution to log error information to use with search and metrics. Here's an example from our testing instance on how you can use custom events with metrics and search:




You can group your metric card data by API Event to see the custom events you've setup (above) or you can search for a specific error and group the data by the error code (below).




In the segments view, you can search for sessions by the custom event name (eg. Product Added) and take this a step further by adding a dependent filter for the custom event property (eg. description).




As another alternative, your developers could also send console errors for search and metrics, but it's a little less specific in terms of properties (eg. text for error, page where error occurs).


If your developers encounter any issues with your custom event implementation, please don't hesitate to reach out to us at We'll be here to help!


Thanks Kim, appreciate excellent reply. I’ll be using the trackEvent() function. Will be sure to update here for all to see and benefit from.