Module tracking is relevant for all who have the News Modules design (iOS and/or Android) implemented in their apps. The new main event ‘Module tracking’ will be a simple tracking event that will send data every time a user press content within a module.
Module tracking will help you gain insights about the popularity of all the different modules used in your App. Thus, this new tracking will make it possible for you to make A/B testing in order to test the impact of rearranging your modules or implanting additional content modules.
Module tracking does not include a scroll depth parameter; hence, it is not possible to see how far down the front page a user scrolls, or if the module is visible within the initial screen view. However, all custom dimensions are sent together with the module tracking event and together with Google’s own dimensions. Therefore, it is possible to use the Device Category to analyze if there is a difference between the module’s performance on a mobile, tablet or desktop device. If you are not familiar with our custom dimensions, you can read about them here.
Combining Module and Source tracking
Module tracking works closely together with the Source tracking event, which has recently been updated. Thus, with Source tracking, it is now possible to analyze how articles, podcast, and publications that are available from the front-page-modules are performing. You can read more about the source expansion and its values here.
Module tracking can therefore help you gain insights about how to place your modules to reach the best possible user engagement result. Furthermore, it will also make you able to compare, how effective it is to have a given piece of content displayed in a frontpage module and how the modules are performing on different devices.
Table: Module tracking data structure in Google Analytics.
Comments