Issue Regarding User count According App's Database

Hi Community!

I have a Question regarding my app’s user count according to my database.
The number of users in my app is not as shown in the Play Console.
My Play console shows that 500 new users Downloaded my app.
Whereas in my Database, only 50 users were visible who downloaded and opened my app (which is counted in total temp users).
Screenshot 2024-02-18 at 3.55.07 PM

a few days ago, if the play console showed 500 new users, 500 new users were also shown in my app’s database which records who downloaded and opened my app.
I have also recently updated my app with the new version.
When I downloaded and opened my app, it WAS RECORDED in my app’s database.
I did it multiple times and it worked flawlessly.
Could someone also please try the thing and say if there is any issue?
Blocks

Thanks, whoocoder

I’m not sure but what happening if a lot of user acces your app simultaneously . Probably some users get the wrong total number (not updated ) and with hundreds of users your count is wrong.
I think the way total +1 is always under danger .
Yog have a list of user where you store data ? You can get the length of the list to know the real dimension of the database.
With a clock and saving date with value you can code to get this value only every month or only every week so you can save the new users for week to week or month to month

1 Like

Nope, I don’t have anything like this, I just count the total number, this issue wasn’t happening 10 days ago

Which database you are using?

1 Like

Google Sheets

Are you sure that number one work for id ? Usually Id is a unique code and not the number of the row

1 Like

Yes, the number works for the ID
Screenshot 2024-02-19 at 8.23.19 PM

1 Like

Oh nice , I remembered not works with row number.
Anyway if the problem is about multi reading value , to be sure to read the right value you have to create a procedure with two value . A true/false value to work , if value is true you can get value and count the user, in the while set value to false .
And another condition to start , if lenght of column is 50 set variable to false and manage the data.
Every users download the app at first have to add +1 in the column, if column lenght= 50 , set variable to false, get the total value and add 50 , then set variable to true again

1 Like

I found it in the docs, number like id works only for Google sheet, for airtable or local data you have to use unique ID.

1 Like

Thanks for your Reply!
What do you mean by Multi Reading Value?

I think if 2 or more people get value contemporarily only one of them will get the right value .
Get and store value take some time , so if user 1 and user 2 get value together they will have both 7738 and they will store both 7739 , so you losted one user .
May be some power user can confirm this iusse .

But chances of this is 1% and I haven’t got any Duplicate ID yet. Should I create single rows each time when a users opens my app?

How many users you lost? Why duplicate ?
Another problem could be a null get or store section.

I haven’t lost any users yet due to duplication of ids
What do you mean by null or store section in the Topic?

Explain better please.

You make a query and no response come from database or you try to store and no value will send to database

I have NOT LOST SINGLE USERS due to the thing when 2 or more people hit the Button at the same time and the Updated count is only 1. Also, could you please Reply about this?

For lost I mean this , you solved this ?

If the problem is about users that get value contemporarily I think you have to create a procedure that when the list of new users reaches a fix number (50 or 100) you have to add 50 or 100 to the total amount, in the while no user can access to the procedure to update total

Ohh! I got you,
I have lost most of the users due to some unknown issue. It is shown in that Message.

Ok, I’ll try the thing you told

For now these are the only things I know.
1 contemporarily clicks
2 database error for get or store

:man_shrugging:t2: I hope you will fix it

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.