Maximum number of user events in Flurry analytics?

Question

What is the maximum number of custom events you can report per session using Flurry analytics?

Answer 1

The number of events that you can report in a Flurry session is 1000. I asked this question to Flurry support, as I could not find it anywhere else (and none of the answers here really answered the question). They answered and also sent me a short document entitled “Methodology and Best Practices”, which, among other things, contained the following summary:

• 300 unique events in the application
• 1000 events maximum per session
• 100 unique event names per session
• Maximum 10 parameters per event
• Key / value for parameters should be Strings
• Maximum key length 255 characters
• Maximum length value 255 characters

Since the definition of “session” is important, I quote from the same document:

Flurry analytics is based on a session model that only “rings home” at startup and session background. This prevents talkativeness from the SDK, saves battery power because the radio does not always work, and allows data to move in a consistent package. "

(...)

One of the additions to the Flurry session model is the concept according to which the user can exit the application for a short time and re-enter the application, while remaining in the original session. The time can be set in milliseconds, which is colloquially called a “session timeout”. It is configured at application startup (see SetContinueSessionMillis for more information) in the range of 5 seconds to 1 minute with a default value of 10 seconds. If, when the user returns to the application, the “session timeout” has not been exceeded, then the SDK will consider the “new” session as a continuation of the previous session.

With this new start, if any sessions are not sent, they will be sent. At the same time, the SDK will decide whether to continue the session or not start a new one.

The document is here. Flurry Support sent it to me at the end of February 2015.

Answer 2

The limit appears to be 300 different event identifiers and therefore 300 custom events. Quote: http://support.flurry.com/index.php?title=Analytics/GettingStarted/TechnicalQuickStart

Currently, your application is limited to counting entries for 300 different event identifiers (maximum length 255 characters).

More details here

Yes, there is a limit of 300 events for each application. Each event can have up to 10 parameters, and each parameter can have any number of values.

Answer 3

I believe this is infinite:

Each event can have up to 10 parameters, and each parameter can have an infinite number of values ​​associated with it. For example, for "Author Parameter" there may be 1000 possible authors who are the article. We can track each author through this single parameter.

So, if you can have an infinite number of meanings, you can have 10 million authors. Since all of them are just values, each of them can be tracked (via a parameter). If they “can track each author through this single parameter”, then I don’t think that your account of events would be relaxed. This assumes that you are setting up event types correctly, as in their example:

NSDictionary *articleParams = [NSDictionary dictionaryWithObjectsAndKeys: @"John Q", @"Author", // Capture author info @"Registered", @"User_Status", // Capture user status nil]; [Flurry logEvent:@"Article_Read" withParameters:articleParams]; 

One event with a maximum of 10 dictionary elements with an infinite number of possible values ​​... I think it is safe to say that you are not limited here.

Answer 4

There is a limit of 300 events for each application. Each event can have up to 10 parameters, and each parameter can have any number of values. Please check everything here.