Maxiumum number of custom events in Flurry analytics?

Question

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

Answer 1

The number of events you can report per session in Flurry is 1000. I asked this question to Flurry support, as I couldn't find it elsewhere (and none of the answers here really answered the question). They answered and also sent me a short document titled "Flurry Methodology and Best Practices" that contained, among other things, this summary:

• 300 unique events per app
• 1000 events max per session
• 100 unique event names per session
• 10 params max per event
• Key/Value for params must be Strings
• Key max length 255 chars
• Value max length 255 chars

As the definition of "session" is important, I quote, from the same document:

Flurry analytics is based on a session model that only “phones home” at the launch and backgrounding of a session. This prevents “talkiness” from the SDK, conserves battery by not always running the radios and allows data to travel in a coherent package."

(...)

One addition to the Flurry session model is the concept that a user may bounce out of an app for a very brief time and reenter the app and still be within the original session. A time may be set, in millis, that is colloquially referred to as the “session timeout”. It is configurable at app launch (see setContinueSessionMillis for more details) within a range of 5 seconds to 1 minute with a default of 10 seconds. If, when the user comes back into the app, the “session timeout” has not been exceeded, then the SDK will treat the “new” session as a continuation of the former session.

Upon this new launch, if there are any sessions not sent, they will be sent. At that time, as well, the SDK will make a decision on whether or not to continue a session or start a new one.

The document is here. Flurry support sent it to me in late February, 2015.