Tracking user flow through your app

Tag views, or screens, in your application in order to track the way users flow through it. To tag views, add a tagScreen call in the viewDidAppear call for each of your views.

If your project doesn't define this function, create it from the definition below. This should live in the view controller code. Don't append the name ‘screen’ to each screen because it'll be redundant when you view the data online.

As with events, don't name each screen dynamically. For example, a screen displaying an article should be tagged simply as Article, rather than with the article's title.

For iOS

- (void)viewDidAppear:(BOOL)animated
{
   [super viewDidAppear:animated];
 
   [Localytics tagScreen:@"Settings"];
}

For Android

onResume() 
{
   super.onResume();
   Localytics.openSession();
   Localytics.tagScreen("Splash");
   Localytics.upload();
}

Note: The library will perform duplicate suppression on two identical tagged screens that occur in a row within a single session. For example, in the set of screens {"Screen 1", "Screen 1"}, the second screen would be suppressed. However, in the set {"Screen 1", "Screen 2", "Screen 1"}, no duplicate suppression would occur.

For web

Call tagScreen after the open for each page.

ll('tagScreen', 'Article View');

For WinRT

Localytics.TagScreen("Article View");

For Javascript/Windows JS

Call tagScreen after the open for each page.

localyticsSession.tagScreen(“Article View”);

Note: localyticsSession.close() needs to be called in order for the Screen data to be uploaded.

For Unity

Localytics.TagScreen("Settings");

For BlackBerry 10

You may add “screens” to each of your QML files to track users as they flow through your application. Screens should be tagged in the onCreationCompleted callback.

onCreationCompleted: 
 {
     localytics.open();
     localytics.tagScreen("Game Screen");
 }

For Roku

The library will perform duplicate suppression on two identical tagged screens that occur in a row within a single session. For example, in the set of screens {"Screen 1", "Screen 1"} the second screen would be suppressed. However in the set {"Screen 1", "Screen 2", "Screen 1"}, no duplicate suppression would occur.

m.LL.TagScreen("home")