Tracking Error Clicks using FullStory for Mobile Apps

Available for the following Plan types:

FullStory Enterprise*

FullStory Business*

FullStory Free

*with the following add-on:

FullStory for Mobile Apps

Available to the following User roles:

Admin

Architect

Standard

 

If you're using FullStory for Mobile Apps, there are a few steps you must take to track Error Clicks for your mobile application. 

Tracking Error Clicks for iOS Applications

To track error clicks for your iOS application, log errors using:

In Objective-C

+[FS logWithLevel:message:] or +[FS logwithLevel:format:]

In Swift

FS.log(with:message:)

To mark the message as an error, add the 'error' argument like this:

In Objective-C

[FS logWithLevel:FSEventLogLevelError message:@"..."]

In Swift

FS.log(with: .error, message: "..."

Learn more about FS.log() here.

Tracking Error Clicks for Android Applications

You have two options for tracking error clicks for Android applications: update your logcatLevel configuration settings, or log errors using FS.log()

Option 1: update your logcatLevel configuration settings

By default, FullStory disables logging logcat messages, which capture frustration signals like error clicks. To change this behavior and capture frustration signals, update yourlogcatLevel configuration settings. Find more information here: https://help.fullstory.com/hc/en-us/articles/360040596093 

Option 2: log errors using FS.log() 

If you prefer not to update your logcatLevel settings, you can also log errors using FS.log(). To mark the message as an error, add the 'error' argument like this: FS.log('error',msg) 

Learn more about FS.log here

 

 

 

 

 

 

 

 

 

Need to get in touch with us?

The FullStory Team awaits your every question.

Contact us