It’s important to note the message here regarding the number of monthly active users. If you’re trying to set this up for a small sample project then you may be waiting some time for results to show up. If your company is already using Firebase analytics, maybe they’ll let you try out Predictions 🙂

To continue, you can go ahead an click the “Yes, I’m in” button. At this point you’ll be shown some default predictions which have been setup for you out of the box. This is also the screen you will come back to when you want to view predictions, alter the risk levels for them or add a new prediction.

At this point you may or may not have data tracked in your project to show some results, if this is the case you’ll just have to sit patiently (or try and get more usage in your app!). However if you do have enough tracked data you’ll notice a percentage value along with a slider. The percentage value here is the number of users in your application that are likely to perform the given event within the next seven days. The slider determines the risk tolerance you want to take when performing actions on your predictions — we’ll come onto that more soon. Hitting the target users button will allow you to perform your desired action on this predicted user group.

These built in predictions alone are already likely to be pretty useful for a lot of applications, these so far include:

churn — A predicted group of users who are likely to churn

— A predicted group of users who are likely churn not_churn — A predicted group of users who are likely not to churn

— A predicted group of users who are likely to churn spend — A predicted group of users who are likely to spend money with your app

— A predicted group of users who likely to spend money with your app not_spend — A predicted group of users who are not likely to spend money with your app

However these predictions may not be enough for your application. Thankfully we are able to create out own custom predictions, let’s take a look at how these work.