Learn what Felgo offers to help your business succeed. Start your free evaluation today! Felgo for Your Business


OverviewFelgo 1 Support › Flurry: Long text event parameters

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #5718

    Felgo Team

    I recently tried using flurry to log something for an app, and I tried adding a really long text as a parameter for an event. But on the flurry backend it appears to be cut off after a limited amount of characters (about ~300).

    So my question is, is that a limitation of the flurry framework/SDK (I couldn’t really find anything about it on the flurry page), or could it be that Felgo cuts of really long event parameters?
    Example code:
    flurry.logEvent("eventName", {reallyLongText: "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras sed rhoncus leo, at posuere purus. Vestibulum a turpis ut nulla ultrices rutrum at eget dui. Suspendisse eu elit non orci aliquam porta sit amet at metus. In ac nunc id sem auctor cursus at et libero. Etiam quis suscipit libero. Integer hendrerit neque elit, in rhoncus quam bibendum quis. Aenean eu orci posuere, accumsan dui ut, laoreet mi. Nullam luctus risus arcu, sed facilisis quam tincidunt nec. Nulla rhoncus nisi in semper auctor. In hac habitasse platea dictumst. Vivamus elementum dignissim lorem ac tincidunt. Vivamus eu viverra enim. Aenean at odio nisi. Phasellus tristique justo eu mi volutpat commodo. Quisque et pulvinar lacus. Nulla facilisi. Aenean id mattis lorem. Maecenas dolor risus, dignissim a enim at, ultricies dapibus erat. In gravida urna et mollis dictum. Proin dui odio, ultrices et nibh a, malesuada feugiat neque."})

    Cheers, Chrisu


    Felgo Team

    Hi Chrisu,

    the Flurry SDK docs say the following for logEvent():

    Use onEvent to track user Events that happen during a session. You can track how many times each Event occurs, what order Events happen in, as well as what the most common parameters are for each Event. This can be useful for measuring how often users take various actions, or what sequences of actions they usually perform. Each project supports a maximum of 300 events, and each Event ID, parameter key, and parameter value must be no more than 255 characters in length. Each Event can have no more than 10 parameters. The parameter argument is optional, and may be null.

    So the limit seems to be 255 characters – although I think you should keep the event names really shorter as you will otherwise loose overview in the web analytics tracking 😉

    Cheers, Chris


    Felgo Team

    Ah I get it – for some reason I couldn’t find this in the docs 🙂


Viewing 3 posts - 1 through 3 (of 3 total)

RSS feed for this thread

You must be logged in to reply to this topic.

Qt_Technology_Partner_RGB_475 Qt_Service_Partner_RGB_475_padded