Funnels let you track the conversion of users as they progress through a series of defined steps. This enables you to visualize the completion rate of user progression through any event flow and identify which steps users are not converting through.
Including a Dimension allows you to visually compare conversion rates by different attributes. Adding Filters allows you to narrow the scope of the funnel to analyze a subset of users.
Funnel types are comprised of the following:
|User conversion||Reports unique user conversion through the funnel where a unique user will only be counted once through the funnel. When you build and run a query, this type will report on the conversion rate for your app users.|
|Transactional||Reports unique occurrences of user conversion through the funnel where a unique user can be counted multiple times through the funnel.|
Funnel steps can be any custom event instrumented and these pre-defined standard events:
- Install: App is installed on the device.
- Session Start: A session is started on the device.
- Session End: A session is ended on the device.
Build & Run Funnel Queries¶
To build and run Funnel queries, first navigate to Explorer as described in Getting Started.
Once you are in the Explorer UI, you can run saved queries by selecting one from the Saved Queries dropdown or create a new query by clicking the + New Query button at the right side of the page.
To build and run a new Funnel query:
- Click the + New Query button.
- Define the Funnel Type: User conversion or Transactional.
- Specify the first step in the funnel by clicking the first step dropdown.
- Specify the second step in the funnel by clicking the second step dropdown.
- Optional: Add other steps in the funnel.
- Optional: Select a Dimension to contrast across the funnel.
- Optional: Add Filters to limit the scope of the funnel.
- Click Run Query.
Example Use Cases¶
A simple funnel query where you specify the funnel type as the number of user conversions for the First Session will report the First App Launch and the Session Start, as shown in the chart below.
For example, if you select First Session by Gender from the Saved Queries pulldown list, as shown below:
and you build and run a user conversion query with Estimated Gender as your Dimension, your report will look similar to the chart shown, returning values for female, male and unknown genders of your users.
Funnel Event Types¶
To build and execute queries that return data you can slice-and-dice, Explorer lets you work with a lifecycle of Events. Typically, Explorer generates Install and Session Start events, while other events are generated by your app installs.
Once you run queries on different types of events, you can easily analyze the results. Explorer enables you to determine the value represented by those events.
The following Event types are grouped among data elements in the UI:
- Install. Based on an app install: for example, a unique device with your app. Install events include characteristics like install time, acquisition channel and demographic information about the device (age, gender).
- Session Start. Based on a unique session within an app, which starts when the app is open and ends when the app is either closed manually or has been backgrounded for a defined period of time.
- Add constraints. Track specific actions that users take within your app. For example, you can track making a purchase or sharing on Facebook. Custom events are tracked in your specific app’s code in Flurry Analytics.
You can also add a number of Custom Events to your Funnel Steps, like
Using Dimensions, you can define how your data is grouped and summarized. You can also add dimensions to group data.
Note that if there are no data elements in the Dimensions area, the results of the query will be a single number.
For the Date/Time dimension, you use Install Date/Time.
A number of other Attributes can be added to Dimensions, like Attributed/Organic, Acquisition Channel, Acquisition Campaign.
In Demographics, you can specify, for example, Estimated Age / Gender. You use Estimated Age / Gender to see how your users break down along the lines of age and gender.
When you use Filters, the scope of the query can be limited by adding data elements into the Filter box and setting the desired limits.
Was this document helpful?