Funnels Added to Unity Analytics (beta)

We’re excited to announce the release of our newest Analytics feature Funnels. Funnels help you better understand your player progression, identify opportunities to boost your KPIs, and uncover potential issues that are preventing players from having an optimal experience. Funnels are ready to use out-of-the-box as they can pull in historical data to populate the charts. Common funnels we’ve seen customers build: onboarding, level progression, player drop off, purchases, & offer conversion.

Learn more about Funnels here

2 Likes

Hi ! Great addition to the new Analytics tools!

Is there a way to change the “EQUAL TO” operator for an integer/float parameter to INFERIOR/ SUPERIOR ?

It could be very usefull to use for parameters like “number of attempts” to complete a level (here with a funnel, I need a "death_count <= 5 " then "death_count <= 2 " to have a better idea of the distribution of attempts on a specific level).

Thanks.
Tom

This comes up from time to time. Inequalities would not work as expected in a funnel. If death count was less than 2, it would also be less than 5. So the event would be valid in both steps and not demonstrate progression. Funnel steps need to exclusive through equalities.

Hi Jeff ! Thanks for the response. I’m new to Analytics (both beta and legacy so yes the question was probably already asked, sorry).

The problem is that there is two tools to analyse data if I’m not mistaken :

  • the Data Explorer to agregates multiple data with dates in abscisse (great to analyse a parameter over time / to compare metrics with events over time ). The “group by” option only multiplicate the number of curves with all the option but does no aggregation if I’m right
  • the Funnel to demonstrates progression of % of players within more restrictive conditions

Both are great and work with equalites when the parameter is linked to something that separate drasticly things like a level id. But none give hints avec % of players when you want to agregate data that are not exclusive gameplay whise (like number of attempts, time to complete)

Two examples :

  • if a player made 2 attempts before winning, he should be taken account when I want to study the % of players who make less that 5 attempts to win in a specific level (level == 3 && attempt <5).
  • if a player completed the level in 15 seconds, he should be taken account when I want to study the % of players who make completed the level in less than 1 minutes in a specific level (level == 3 && time <60)…

Is there a possibility to analyse such behaviour with Analytics (legacy or Beta), to sum up : to know if a level was too difficult because of the value of a parameter (Funnel will indicate which level was too difficult = where the is a drop of #players if I use a “level id” parameter step by step, but not why because cannot agregate an event parameter as int/float which verify an inequality condition )?

Correct, you would want to pass the levelID as an equality. In your funnel, you would see several users in levels 1, 2 and 3, and then much less in level 4, for example. Then you might know that level 4 is too difficult. But as mentioned, inequalities would logically not work. If you had level = 3 and attempt less than 5, it would also match level = 3 and attempt less than 6, for example. A single user would be in both steps at the same time, and you lose progression. Funnels are purely progressive in nature. Funnels don’t operate with number of attempts or time to complete (or time in general). Another example, let’s assume that you have 2 funnel steps, level = 3 and attempts = 3, then the next funnel step is level = 3 and attempts = 4. Funnel steps are not “buckets” for the condition, but purely progression. So if your user matched level = 3 and attempts = 3, they would be included in the funnel report for that funnel step. But they wouldn’t be included in the next funnel step of level = 3 and attempts = 4, so this user would not make any further progression at all through the funnel. Each funnel step requires the user pass the prior step before continuing through the funnel.