Set User Properties to enable you to target certain types of push notifications to paid users and send other notifications—perhaps nudges to transition to the subscription tier—to non-subscribers.
Another common push use case is user preferences. Let your users tell you the types of push notifications they want to receive, then use User Properties and Flurry Push Targeting to deliver the right messages. Note that Push Targeting will be available in the coming weeks.
Standard User Properties will automatically be available in reporting, while custom user properties must first be registered. Please see here for full documentation and reach out to us with feedback or questions at support flurry. This option is on by default. When enabled, Flurry will attempt to send session data when the user exits the app and when the user starts the app.
This will improve the speed at which your application analytics are updated but can prolong the app termination process due to network latency. When enabled, Flurry will attempt to send session data when a user pauses the app and when a user starts the app. This will improve the speed at which your application analytics are updated but can prolong the app pause process due to network latency. This option is disabled by default. When enabled, Flurry will not finish the session if the app is paused for longer than the session expiration timeout.
The session report will not be sent when the application is paused and will only be sent when the application is terminated. This allows for applications that run in the background to keep collecting events data. Collectives on Stack Overflow. Learn more. Flurry new users count Ask Question. Asked 5 years, 5 months ago. Active 5 years, 5 months ago. Viewed times. Improve this question. Edmond Edmond 2 2 gold badges 8 8 silver badges 24 24 bronze badges.
Add a comment. Active Oldest Votes. Improve this answer. Michael Rollins Michael Rollins 56 1 1 bronze badge. Is there a way to track and get the accurate number of users? Define "user". In our parlance, a "user" is a known device. If someone clears a device, then that device is a new "user". You, on your side, can log a user ID, but that isn't necessarily reflected in our metrics. Gruntcakes Gruntcakes I found that the deviceToken observed in iOS is different every time.
0コメント