Firebase Remote-Config crash free users - firebase

I'm trying to display a "Rate Me" popup to most active users that haven't received crashes recently.
I can easily track how active an user is by using analytics and conditions, and setting a remote-config flag to true.
Is there a way to create an audience or a condition to select users without crashes?

Yes, you can do this by creating an exclusion group in your Analytics audience that excludes users who have logged an app_exception event within a specific timeframe.
The best way to do this, assuming you're already creating an audience for the active users you want to target, is to add on the exclusion group to that audience as well to remove users who have experienced a crash recently.
See attached screenshot for an example from the Firebase console.

Related

When do Firebase Analytics count a user as active?

I have an app where users need to sign-up in order to use it. The signup process can take up to a minute or so and eventually, it could fail, so the user doesn’t actually use the app.
My question is, how can I make Firebase count a user active, only after he/she has verified his/her account, so I can have proper retention analytics?
you can have a login page that when accessed triggers your analytics to report that a user has accessed the page in question, this way, you are able to track both app instances and logged-in users.
You can find the list of events and parameters here:
https://support.google.com/firebase/answer/7061705?hl=en

Firebase Analytics: first_open event missing for part of my users

I'm creating some funnels and journeys for my app's events from Firebase Analytics using BigQuery, starting with first_open and continuing with other custom events. My understanding is that using user_pseudo_id, I should be able to track a single user's journey.
The problem I'm facing is that some user_pseudo_ids found in the custom events do not have a corresponding first_open event, so I'm not sure when they started using my app.
Are there cases where a first_open may not be recorded? Or cases where the user_pseudo_id may change after first_open?
TL;DR: In order to reliably track users, one should use setUserId().
As noted in this answer, user_pseudo_id comes from getAppInstanceId(), and it's reasonable to assume its lifetime is not dissimilar to FirebaseInstanceId, which can change in the following cases:
App deletes Instance ID
App is restored on a new device
User uninstalls/reinstall the app
User clears app data
Reinstalling triggers the first_open event again, so that wouldn't be my case, and my app does not delete the Instance ID.
Going through the logs, the last option can be discarded (in my case), because I can see the users were logged into my app when the new user_pseudo_id started being used.
So that leaves restoring the app on a new device as the likely culprit.
I'm now using setUserId() in order to track users.

Firebase RemoteConfig and conditions with audience

In Firebase I am trying to set up some RemoteConfig parameters that should have different values based on the audience membership of the user that is logged in to an Android app we are developing.
The problem is that I am not allowed to set up a RemoteConfig condition based on audience. The option is greyed out.
Also, if I attempt to view events filtered by my Audience in Firebase
Analytics, no events appear.
My audience configuration in Firebase looks like this:
I understand that I my audience needs to be "reasonably well
developed" for them to be targetted by RemoteConfig
(https://support.google.com/firebase/answer/6317509?hl=en)
So I have followed this procedure to populate the audience:
Install app
app triggers "login" event with custom user property "chain_id" set.
uninstall app
reset advertising ID (as noted here https://stackoverflow.com/a/39183589/930653)
I have repeated this about 20 times and waited 48 hours.
The audience ("Minibuss") now lists 23 members:
But still, I can not use the audience as a condition in RemoteConfig,
or filter events in Firebase Analytics based on this audience.
I have tried looking at DebugView in the Firebase console, and I can see the user has the correct porperty "chain_id" set to 524, and so the event should match the audience.
Am I missing something?
This rule requires an App ID rule to select an app associated with
your Firebase project.
from https://firebase.google.com/docs/remote-config/parameters
You need to set Applies if "App" and choose your app, and then User audience option will be available.

Firebase audience not being populated after several days

I'm attempting to build a Firebase audience for my Android app based on users who live in the United States. From what I've gathered, users' countries are a property that's gathered out of the box simply by integrating with the Firebase SDK. I built an audience in the analytics dashboard (criteria is user property -> country -> exactly matches 'US'), but I still haven't seen any users populated in the audience. It's been over 3 days since I created the audience, as I've read from several other questions that the audience is not populated retroactively.
I also tried creating a separate audience for users that are on the latest version of my app, and that audience hasn't gathered any users either since it was created.
Here's a screenshot of my audience configurations
Is there anything I could be missing here, or is this a potential bug in Firebase?
To become audience member a user needs to trigger an event and match all the conditions in the audience. Using country as the only condition will not automatically make all users that are in US members as there is nothing to trigger the audience evaluation.
Also audiences are sticky so your audience is users who are in US or have been in US at any time in the past since you defined the audience.
You have two options to make this work:
You don't need to define audience for location. Every event has the current location already and you can use location to target push notifications or change remote config values. Its redundant to define location as audience.
Add common event as audience trigger to your audience. You can use something like session_start. This will make audience evaluated every time "session_start" event is triggered. Once the user location matches and the user starts a session he/she will become a member. The membership is sticky so your audience is users who have started session while in the US not users who are in the US now. If you want users in the US now use option 1.

Using firebase to show all active page visitors on shopify site?

I am trying to see if its possible to use Firebase to show the number of active users in real time on my shopify site. I also want to show the active users on a single product page if thats possible.
I see the Firebase example code for Presence but it looks like this only works for logged in users. How do I or is it even possible to show the real time user count ignoring whether someone is logged in or not...similar to the real time google analytics count?
The Firebase presence samples (one, two, three) all rely on the Firebase onDisconnect() handling. This method allows you to specify write/delete actions that should happen to your Firebase data on the server, once it detects that the connection to a client has been lost.
A system like this can work fine with using Firebase Authentication, but you need some way to uniquely identify each user. This can be any sufficiently random identifier, or for example the uid generate by Firebase's anonymous authentication. Both serve the same goal: authentication without identifications. That last approach is somewhat similar to how many analytics services work: they give you a unique ID when they first see you and then track you by that ID.

Resources