I would like to ask how to see the data required for operations such as the length of time users stay in the app and the daily retention rate of users
Related
How to see the data from Huawei AppGallery Operation analysis such as,
The length of time users stay in the app
The daily retention rate of users
Is there any way to get these data? Anyone please help on this. Thanks in advance.
For viewing the length of time the user stays in the app and the data required for operations such for operations such as the user's daily retention rate, please follow below steps
Click Add filter and set the filter criteria. For details, please refer to Adding a Filter.
Select a time segment as required.
View the report generated, which illustrates the trend in the new user retention rate and daily details through a graph and a table. Click Day, Week, or Month to switch the time dimension.
Save users retained for a specified period as an audience.
For more information please find below link :
https://developer.huawei.com/consumer/en/doc/development/HMSCore-Guides/retention-analysis-new-0000001078671792
I am using flurry analytics in my unity game .
In flurry, we are getting average session duration for a specific date or date range. We want to get session duration for all users individually. i.e. assume 10 users played our game today and total no of session is 25. I like to get session duration for all 25 sessions separately along with user id. is this possible? If yes, can you please share some pointers.
It is not possible to get individual session times for each user through Flurry. Flurry session data is geared towards aggregating the session length, to give you an overall idea of how long users are spending in the app, not to drill down to specific user times. The closest metric to what you are describing is The session length distribution chart on the Usage>Session Length page, which distributes the sessions into buckets based on length, so you can see how many sessions of a given range occurred.
I am building an app about joke telling using soundcloud api. So does soundcloud limit 15000 applied in 24 hour means all my app in in every device can applied for 15000 or one app in individual device?
Form Sound cloud developers portal
Effective July 1, all requests that result in access to a playable
stream are subject to a limit of 15,000 requests per any 24-hour time
window. Currently, this is inclusive of all requests that are made to
/tracks/:id/stream.
After a previous time window has expired, a new time window starts
from the first request made.
The majority of SoundCloud API rate limits are in the form of 24-hour
time windows.
For more details visit
https://developers.soundcloud.com/docs/api/rate-limits
I have an app that used to send more than 50 000 notifications weekly and dropped below 17% CTR. When Facebook blocked the app, we edited and limited the notifications to below 40 000 weekly which increased the CTR to about 20%. FB unblocked the app and DAU skyrocketed.
Today the charts look like FB blocked us again. While our CTR indeed dropped a wee below 17%, we do not exceed the 50 000 notification limit.
Is it possible that once you exceed 50 000 notifications for the first time, the 17% limit "sticks" and haunts you even if you drop below 50 000?
We just got an answer from a FB developer:
No, the limit does not stick once you've gone over 50k for the first time. If you go back down to 40k per week afterwards you should have no difficulties. We look at both click through rate and spam rate when it comes to apps that use notifications, and for more information, if your app is restricted I would recommend submitting an appeal at https://developers.facebook.com/appeal. If your app doesn't appear there, or if there is no notice of restriction on your app dashboard, that means it has not been restricted by us, and there may be something else affecting your notifications.
If you do submit an appeal I'll make sure our team takes a look and we can give you a better explanation. Make sure you keep an eye on the contact email address of your app for our response; you can find this in the Settings tab of your app dashboard if you need to update it.
For more information on notifications in general, I strongly recommend checking out our developer docs, particularly here - https://developers.facebook.com/docs/games/notifications. There's some great tips on how to optimize notifications. We allow apps to send under 50k notifications per week with no CTR requirement because we want to give developers the opportunity to test new notifications before rolling them out to wider audience. We really believe that developers can actually get much higher CTR, usually up in the mid 20's, with careful targeting and thoughtful creative work.
If you're getting that high CTR, that also means you can send notifications to a lot more people who are using your app. So not only are more people getting your notifications, but a higher percentage of people are clicking on them too.
I need your expert advice on this one.
I have been asked to analyse a potential Facebook application.
This application is a parental monitoring for kids accounts. Basically it will search a kid status message for specific keywords amongst others things. And this application will alert the parents when it finds something.
Of course this application will have a valid token to access the kid's data. This is not a tool to spy on the kid.
I am using the Graph API coupled with the 'since' keyword to get the last updates. It's working fine with a single user.
My question is about scalability.
How should I get updates of a huge number of kids to monitor? (between 10,000 and 100,000 accounts)
And for each kids I have to monitor status messages, videos, images, friend, friends' status messages...
Here are some numbers:
~2.1M requests each day to get hourly updates of 10,000 kids' account.
~57.8M requests each day to get hourly updates of 10,000 kids'account plus their friends', with an average of 40 friends each.
And as I read here, it would be limited.
So what do you reckon?
ps: Maybe with real-time updates I won't have this problem or would it be worse?
Yes I would subscribe to real-time updates so as an account gets updated you get a callback and then you get the latest updates. This would avoid the overhead of constantly polling accounts for updates. You will need to get an offline_access token for this to work as well.