Flurry Events Walkthrough

Posted By Anchal Goel | 24-Jun-2016

Today I’ll tell you how to track user actions throughout your app using flurry custom events in flurry events section.

    Sometimes we want to know what are the steps user took, before user got stuck at some point. Using custom events of flurry in our app for the in-app actions which user takes, we can track the flow of user actions. With the help of these events we can easily reproduce these issues and it will help developers to solve them as soon as possible.

After event logging is done, whenever user did something on your app those events will get registered to flurry portal. Now, let see how to interpret those events on flurry portal.

    When you open flurry portal on the left hand side you will see “Events” section, all the tagged events will be shown there, when you click on it then you’ll see “Event Summary” section under it where all of the tagged events with their statistics are shown.

The above image shows the event summary section, in this section you’ll see all of your tagged events under event name and their statistics.

    As you can see on the top right corner of the above image there are three dropdown options “All Users”, “All Versions” and a date range.

  • All Users - by clicking on it you can select All users, Custom Segments, Campaigns and channels. For info on how to create custom segments click here.

          

  • All Versions - by clicking on it you can select either all versions of your app or select any particular version, after selecting version number and clicking on update the event summary section will get updated for that particular version.

          

  • Date Range - by selecting this you can select a time frame to see your events, there are many options under this like Last Week, Last Month, Last Year, etc.

Now, when you updated the event summary according to your needs then you will see the updated table with the event names and their statistics.  In this table if you see the “Analyses” column on the right side of the table, you’ll see many options for a particular event.

   

  • The first option is “Event Duration”, it shows the duration of the events which you tagged with the timed event.

  • The second option is “Even Statistics”, it shows you Events per Session, Unique Users Performing Event, Total Events, Avg Events Per Session.

  • Third one is “User Paths”, it shows how your user navigate from this to others, this is based on the events which are triggered after this event.

  • Fourth is “Event Parameters”, it will show you the graphical representation of the parameters which you provided with the respective event, by changing the parameter from the dropdown menu on the top left corner you can see the parameter distribution of each parameter.

  • Fifth option is “Event Logs”, it will show you the timestamp of the particular event for a user and user’s device.

How will you track user actions?

    For this click on “Event Logs” on the left menu of the flurry portal under events section, here you’ll see detail of your user’s actions i.e. the events users triggered. Whenever data is synced to flurry portal this is the first place which gets updated, other statistics will update later.

Developers should look into this place if they are testing their flurry events, so that they can see it’s working fine.

    This section will show you all the events which are triggered at a particular session time, for every session it shows:

  • Session Time - it contains the timestamp of the session for a particular user.

  • Device Type - shows the device of the user on which your app is running.

  • User Id - shows the username only if developer provide this to flurry, never provide user email id to this field.

  • Events and their parameters.

In the above screenshot you can see that some events has ‘+’ sign in front of them this is because they are event with parameters, all those events which contain parameters will be shown like this and to see the parameters you have to click on the ‘+’ sign to expand the event.

    As I am saying earlier that we can find out and reproduce the issue which came to user by checking this “Event Logs” section, as you can see here for a specific session all the events are tagged and these are the steps which user took.

You can also download CSV file from the top right corner of this section for all the event logs and import them on excel sheets or google sheet so that you can easily find any user or you can easily apply any filters on it.

THANKS
Request for Proposal

Recaptcha is required.

Sending message..