WOGAA tracks screen transitions and attaches information about the current screen to the events, enabling you to track how your users engage different parts of your app.
Much of this data collection happens automatically, but it may not be in the form which easy for a non-technical user to understand as these names are usually names given within the code.
Manually tracking screens is useful also if your app do not use a seperate
Activity for each screen you may wish to track.
Automatic screen tracking¶
WOGAA automatically tracks some information about screens in your application that is currently in focus.
When a screen transition occurs, WOGAA logs a
screenview event that identifies a transition to a new screen. Events that occur on these screens are automatically tagged with a generated unique id to be associated with the
screenview event and the
topViewController (iOS specific) and
fragment (Android specific).
Manual screen tracking¶
In certain cases, you may manually set the screen name and optionally override the class name when screen transitions occur to have more granular control on what is being tracked.
Benefits of Manual screen tracking¶
Manually setting screen names has many benefits:
- Have more user friendly names that can be recognised by users analyzing these data
- Unify naming convention across platforms (i.e. Android & iOS) to help better collate your overall app traffic usage for specific screens
Implementating manual screenview tracking¶
The accepted arguments are:
| ||Human-readable name for this screen||No|| |
| ||Unique identifier (UUID) for this screen||No|| |
The following example shows how to manually set the screen name.
Tracker.trackScreenView(with: "fdb28d62-cb20-11ea-87d0-0242ac130003", name: "ScreenName")
[Tracker trackScreenViewWith: "fdb28d62-cb20-11ea-87d0-0242ac130003" name: "ScreenName"]