How often should I identify User for analytics? - aws-amplify

The analytics plugin allows me to identify users (Amplify.Analytics.identifyUser(...)). How often should I call this?
It is apparent I should call it whenever a user signs up and signs in, or signs out. But should I run it evevy time the user opens the app? Not sure what frequency is best.

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

Discriminate between User Groups using User ID in Google Analytics

I am working on a pre-existing Google Analytics set up and having to develop an understanding of how certain users of our website are interacting with the site.
An important component of this will require user-journey analysis to understand how, say, a premium user interacts with the site compared to a free user compared to someone who isn't logged in at all.
I understand that I can start using User-ID to start discriminating between logged in users and those who are not; however, I am unsure of how to handle the distinction between free and premium users.
Is there any way to add additional information to User-ID to include a "User Group"? Or is there an alternative recommended way to create these segments in Google Analytics?
While it is certainly possible to pass something along with the User-ID to identify the premium and the free users. Example: P-007 vs F-006. I'd recommend you to look into Custom Dimensions(CD) instead.
I'd set up a User Scoped CD and along with your sign-in event push the string "free" or "premium" along with it.
Reason for doing this is that when you set the User-ID, the user is identified by it across multiple devices. If a user starts with free, F-007 and then later converts to premium, P-007, then the user suddenly becomes a different user to GA. Using a CD will allow you to keep the ID the same while converting the user to "free" or "premium" without losing the client.

How to track how many users logged in using Google One Tap Sign Up

I want to track how many users login/Sign up using one tap Sign up feature
Sorry, we don't provide any externally available metrics for this, you'd have to keep track of it using your own analytics systems. e.g. in Google Analytics, track when user signs in or up based on the results from your backend

Google One-tap sign in to auto select the last user

With Google One-Tap sign in it explains you need to add googleyolo.retrieve() on the pages that require sign in for pages that need the user signed in and googleyolo.hint() for when you want to pop-up a sign-up dialogue to first-time users.
Question: Is it possible to auto-select the user even though he has multiple credentials wherever the googleyolo.retrieve() is executed?
My app saves the last user id in the cache, so the next time he opens the app, I want the app to auto choose his last used account.
From the documentation:
If the user has only one credential saved, the credential can be retrieved without user interaction, which makes completely automatic sign-in possible.
When multiple credentials are saved, the user can choose the one to use with a single tap.
I'd like to change this behaviour (the bold text) to auto choose the last user.
I'm the product manager at Google for this library. This is something we've thought about but unfortunately currently don't have plans to support. The current experience is optimized for switching between accounts, which we've found equally common as using a previously selected account. So for now, this behavior can't be changed. I'll update this answer if there is a future revision.

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