analytics pricing

Thread is closed for posting
3 posts, 0 answers
  1. Muhammad
    Muhammad avatar
    7 posts
    Member since:
    May 2014

    Posted 28 Feb 2015 Link to this post

    I am seeking some clarifications on the way analytics is priced.. what does 100 concurrent devices means? does this represents that I can get stats for a maximum of 100 devices with the base subscription? Comparing this with other big names like flurry and google analytics this seems like I have a wrong understanding on this one. Please clarify     
  2. Hristo
    Hristo avatar
    352 posts

    Posted 04 Mar 2015 Link to this post

    Hi Muhammad,

    Could you please give us a link to the page containing the "concurrent devices" text?

    We have identified this wording to be quite confusing and changed it with "unique active devices per month". This means the if you have 10K customer and only 100 or less are active every month you should be OK. Every month the unique devices counter is reset.

    You could take a look at the current pricing page here:

    EQATEC Application Analytics is now Telerik Analytics. For more information on the new name, plus what's new in Telerik Analytics, please, check out the Analytics Service Announcement.
  3. joffery
    joffery avatar
    4 posts
    Member since:
    May 2015

    Posted 04 Aug 2015 Link to this post

    marketing speaks in terms of transactions a day or even unique customers
    on the site, the only measurement useful for capacity planning is how
    many people were on the website at the same time, the instantaneous
    peak. By “on the website”, I mean looking at their browsers at a page on
    the website, regardless of whether that customer is reading or
    clicking. It’s tempting to use hits/sec or transactions/sec, which are
    fine metrics, but what happens when you redesign the site for higher
    performance and the number of hits/sec or transactions/sec drops as a
    result? The capacity of the site may have gone up, but the number of
    hits/sec would drop. In the end you need a metric that is implementation
Back to Top