How can we help?/Creating & Managing Your App/Creating Your Mag+ Apps

Understanding Flurry custom events

posted this on April 24, 2012 10:51 AM

One of the analytics choices we offer is Flurry, and in that we have some custom events that let you dig a little deeper into what people are doing in the app. 

To get at these events, choose Events from the menu on the left in Flurry. If you click on the individual events, then click on Event Logs, you can export .csv files (spreadsheets) for each of the custom events and do some sorting in Excel to get aggregate numbers on the individual events captured there (several fields are captured in a single cell, but you can in Excel divide that cell into separate columns using the menu "Data > Text to Columns"; then divide on : and , - this will give you individual columns to sort on). Unfortunately, you have to export the .csv files one page at a time, so gathering a lot of statistic for, say, an entire month is a bit of a manual process. We'll be working on improving this over time. 

For now, here's an explanation of the events captured there: 

1) APP_CLOSED -> time_in_app

This is time spent in the app between app open and app closed in seconds. 


This is measuring the tapping of a hotspot. A hotspot can be attached to a media file (movie, audio) or a pop-up, or a URL or jumplink. is_media_link says whether or not that link is to call an embedded video or audio file. You can also see in the link: field what the tap invoked - pop-ups will be labeled as such and external URLs will be visible tere as well.

issue_id is the file name of that issue file, which is something you define in the Production Tool and is a combination of the brand (set in the brand settings file) and the issue name (set in the production tool)

vertical_id is the ID of that vertical as defined by the designer in the plug in.

3) VERTICAL_READ -> deck_percentage and  tower_percentage:

In Mag+ the deck is the B layer and the tower is the a layer. So this value tells you how much of the B layer was viewed. If you only have one B layer slide, it will render at 100% if the page is viewed because that top slide will be loaded. If you have a vertical that has two B-layer slides (two pages in that InDesign doc), and the user never scrolls down, it will render as 50% because they've seen half of the B layer slides that are available.  

Tower is capturing how much of the A layer was brought into view as a percentage of how much was available.

4) VERTICAL_READ -> time

Time spent on that vertical in seconds. 

5) VERTICAL_READ -> toggled_layers

Whether or not somebody double-tapped to turn the A layer on or off. 


If an embedded (not streaming or HTML) video is in the vertical, this will show you how much of it was watched, both in seconds and as a percentage; the issue_ID shows which issue that was in.

Topic is closed for comments