Freemius Insights Enables Plugin Developers to Make Data-Driven Decisions

The WordPress plugin directory gives authors a set of statistics but many are left wanting more. Freemius Insights, is a new service founded by Vova Feldman, that allows authors to accumulate detailed statistics from users.

Feldman and his team of four, created the service after speaking to more than 100 plugin developers and realizing there’s a huge gap between what WordPress authors have in terms of data, compared to what web and mobile products have in the market.

Up Front Opt-in

According to the WordPress plugin directory guidelines, plugins are not allowed to phone home. That is, secretly send data without the user’s consent. Freemius Insights provides an opt-in form that displays immediately after activating a plugin. If a user skips this step, data won’t be sent to the author and the user is forwarded to the plugin’s settings screen.

Freemius Insights Ope-in
Freemius Insights Opt-in

The opt-in form is compatible with the plugin directory’s guidelines and is an easy way to be up front and honest with users that data is sent to a third-party.

Data Collected by Freemius Insights

If a user clicks the allow and continue button in the opt-in form, the following data is collected by Freemius Insights.

  • Active Sites
  • Users
  • How many users are connected to Freemius
  • How many users deactivated the plugin
  • How many users uninstalled the plugin
  • Plugin versions
  • WordPress versions
  • PHP versions
  • Reasons for uninstalling
  • Top 10 languages

Developers can use the Insights dashboard to see compiled data at a glance.

Freemium Insights Stats Dashboard
Freemium Insights Stats Dashboard

This type of information helps developers make critical decisions such as what new features to work on, backwards compatibility, what translations to focus on, and more.

See Which Sites Are Using Your Plugins

In addition to these stats, developers can see which domains the plugin is activated on. Knowing the sites a plugin is activated on is valuable data. For example, if a plugin is used on, the developer can leverage that information to possibly establish a one to one relationship. Developers can also create up sells to those specific sites.

Sites the Plugin is Activated On
Sites the Plugin is Activated On

Freemius Insights also uses this data to automatically send an email if a user uninstalls the plugin within the first hour after installation. The email template is personalized with the user’s name and site address. It asks for feedback on how the plugin can be improved or why it didn’t meet their needs.

Developers can even dive deep into a site’s activity and view recent events associated with their plugin such as updates, installs, activation, and who initiated the action. You can see the site’s language, PHP version, and a variety of other data.

Detailed Site View
Detailed Site View

If you want to know the names of the people who opted in, you can see that too. Since Freemius Insights collects a user’s email address, developers can interact with users on an individual level instead of broadcasting emails.

See Who Opted In
See Who Opted In

Receiving Feedback at a Critical Time

One of the most annoying things plugin developers face are one star reviews with no explanation behind the review. Based on data collected during the beta testing process, Feldman discovered that more than 20% of the users who install a plugin will uninstall it within the first 15 minutes.

Freemius Insights has a Deactivation Feedback Form. This form appears when a user deactivates the plugin and gives users an opportunity to explain why they deactivated it.

Deactivation Form
Deactivation Form

This could be annoying if you’re deactivating a plugin to troubleshoot WordPress but Feldman explains why the form is tied to the deactivation procedure, “Once the user deactivates the plugin, the plugin can’t modify anything in the dashboard.

The data is not sent until the plugin is deleted. If the user provides feedback, it’s stored locally in the database. When a user proceeds with the deletion process, it fires the uninstall hook and sends the data to the server,” he said.

Reasons Why Users Uninstall a Plugin

In general, people give negative feedback more than positive. During the beta testing period, Freemius Insights witnessed more than a 82% conversion rate with the feedback form. This data is invaluable to developers and can be viewed on the Insights dashboard.

Reasons Why Users Deactivated The Plugin
Reasons Why Users Deactivated The Plugin

Although Other is not helpful in this chart, it’s valuable because it represents how many users chose to provide custom feedback. It reinforces the fact that users are more than willing to tell developers what’s wrong if given the opportunity. Developers can also filter sites by Uninstalls to get a deeper understanding as to why a specific user uninstalled the plugin.

Webhooks for Developers

Freemius Insights has a webhooks mechanism built-in that enables developers to forward events to another location. For example, when a user installs a plugin, the developer can push the user’s email address into MailChimp. Another example is when a user upgrades a plugin, you can send them an email that lists new features in that version.

Free and Paid Subscription Plans

Freemius Insights has a free plan available to developers of free plugins. The free plan includes an unlimited amount of team members and captured users, but no email export. Paid plans start at $29.99 a month up to $299.99 a month depending on your install base.

Freemium Insights Pricing Chart
Freemium Insights Pricing Chart

If you’re interested in connecting your plugin to Freemius Insights, you’ll need to request a hands-on demo with the team. Feldman explains the benefits of a hands-on approach:

  • We want to be in control of our scale. Analytics requires a significant amount of storage and performance. If one of the most popular plugins joins the service without a heads up, it might drain our server’s resources and affect the performance of the rest of our users.
  • FTUE (first-time user experience) is crucial for every service. Signing into an empty dashboard might make the wrong impression, and we know the first impression is critical. Therefore, we prefer to demo the platform by showing real data from our plugin.
  • We believe the personal touch is more than a cliché. We are willing to spend time getting to know each developer we work with, building a personal relationship, and making sure every integration is a success story. We also love to learn new things, and user feedback is extremely valuable to us.

Feldman says Insights is for plugin developers who want to make data driven decisions, “Freemius Insights provides ad-hoc data so developers don’t have to base decisions on gut instinct.”

Out of Beta

Freemius Insights is out of beta and today marks the first opportunity the public has to see Insights in action. I’ve only scratched the surface of what’s possible and how developers can leverage the data collected by the service. Again, if you’re interested in using Freemius Insights, schedule a demo with the team as spots will fill up quickly.


33 responses to “Freemius Insights Enables Plugin Developers to Make Data-Driven Decisions”

  1. This looks like a fantastic product. Cheers to the team behind it. It’ll be very interesting to see how users react to it but I think we’ll probably give it a try for Postmatic and Epoch both. The trick of course is going to be in who opts in and who does not.

    My hunch is that the type of users that would quickly discount (and one star) a plugin without really digging in are the same group that wouldn’t opt in. And that’s probably fine, because those are the users that wouldn’t likely convert to paying customers anyway.

    But for the kind of users we want to have as paying customers (who would likely opt in with the right language and understanding) this will be fantastic. It’ll really help us understand where the trouble spots are. I’m going to dive in.

    • @Terence, Why do you say such a thing? The users will get another service that spies over what happens on their site.

      I think the idea is cool but the privacy issue is very problematic and I don’t see how it can be fixed as AFAIK you can not accept TOS before activating a plugin.

      • That’s unfair to say. The first thing that happens when a plugin using Freemius Insights does after activation is to ask the user whether or not they want to opt-in to giving the developer the data. If they skip the step, the data is not sent and nothing happens. It’s not spying if the user knows it’s happening and they explicitly allow it to happen.

      • To be fair here it is totally opt-in. I haven’t used Freemius yet but the screenshots i’ve seen show it to be incredibly transparent and fully above the boards.

        We already have something like this in our plugin. We ask people to share usage statistics with us so we know what other plugins they run alongside our own, what version of PHP they run, and what their WP version is. It’s totally opt in. Some users do it and it guides our roadmap. Others don’t and it’s fine. It’s great to have the data when we can get it.

        Accusing a fully transparent opt-in analytics tool of spying is kind of like asking for a ride in my car and then accusing me of abduction. Spying is secretive. Opting into sharing data is not.

      • Hey, @mark. I just checked your blog’s source code, and you use Google Analytics. Theoretically you can roll out your own analytics solution, but you prefer to delegate that responsibility to a 3rd party that focuses all their resources on analytics. Even though Google “spies over what happens”. And you don’t even tell it to your site users.

        In a perfect world, plugin developer could build everything himself. Unfortunately, it’s not feasible.

        At least with Freemius Insights the user is presented with the -exact- data that is being collected. And yes, not like GA, the user can simply click the Skip button.

        • I think it is a great product. I am one of the developers and founders of WP App Studio, a WordPress design and development platform offered as a service (PaaS). Folks use our WPAS plugin to design and develop limited functionality WordPress plugins for free or pay for commercial grade plugins with full functionality.

          I wanted to chime in because when we first published our plugin to the repository more than two years ago, a guy accused us being a hacker, thief etc. on our plugin reviews page, started up a page inviting all his friends to submit reviews accusing us, accused people supporting us for working for us, contacted Otto to take our plugin down …. Some of those comments are still there.. some were removed by the moderation team.

          All because we alert our users inside the plugin that their plugin development is ready and give them a download link from Amazon S3 through a htps connection. Nothing else.. Users signup or pay to use this service.

          After more than 2 years, we have more than 17k users who downloaded our plugin, a store with plugins developed with WPAS and all. So Freemius developers.. don’t be discouraged. People talk. I will be one of the first to sign up.

        • @Vova, no, I can not write my own analytics server as things like google search tools integration are not possible to be written with the API google offers, and I can not do a like button without letting FB track you, etc. This is something the US don’t care about but the EU cares.

          Even if it is a properly done opt-in (no info is gather on anything else, and no info is gathered unless enabled) it is a surprise to the user that just downloads a plugin from which doesn’t specify it has any tracking code by a 3rd party service. This is potentially very annoying to the user as it will probably never be stated upfront.

          There is also the security aspect. if you can give a list of sites on which the plugin is installed. All an attacker needs to do is write a subtle back door into a plugin and use your service to know which sites to attack. And then of course there are your own security practices, why should I trust your security.

          There is really no need to be offended by my comment as all these points were raised when the repository was started against the idea of having an update service integrated into it. But the update service offered features which are obviously good to the user, while it doesn’t seem lie you offer any such features.

          Side Note: obviously every plugin can do its own usage tracking and I think some do (I think yoast and EDD) but it is very subtle and not disruptive to the user in anyway. I am sure users will be shocked when they will receive emails asking them why did they deactivate plugin Y.

        • @Vova, Google “spies” front ends, not backends. That’s a big difference. And, sorry, you’re not Google yet :-) If others will follow you with similar concepts it will create new opportunities for hackers, most probably.
          The latest tendency to “spy”, advertise, creating facebook-like pages for plugins in WordPress admin is quite horrible, in my opinion. Why providing a link is not enough anymore?
          And there are already a lot of great places for “sharing data” between users and plugins authors. Yoast SEO users easily found a way to share their “data” with the developer – just an example:-)

        • Hey @Victor, thanks for joining the conversation. Of course I’m not Google (yet!) :-) If you think about it, when a platform is so customizable like WordPress (which we love), any plugin in the WordPress repository can create “opportunities for hackers”. Today, all the data-capturing-flows are different. Every developer that collects data does it in his way (it’s the wild-wild-west). And in most cases, the messaging is not clear and transparent enough to the user. I’ve seen examples like “Get 20% discount on our premium products for tracking,” without even explaining what is data is being monitored.

          What we are trying to do is to standardize that process following the repo guidelines religiously, making sure it’s done “by the book”.

          With regards to “front end” vs. “backend” tracking, I’m sorry to disappoint you but you can easily track the user by assigning their unique ID ( which could be later mapped to the email from your DB. And if not GA, then Mixpanel, and if not Mixpanel then Kissmetrics, and so on…

          The current interactions between plugin authors to users are happening when there are issues (which is great). BUT, most of the users simply uninstall the plugin and not initiate a support ticket/question. Moreover, sole-developers don’t have the resources to consume all the support, and aggregated view of the problems is a very convenient solution to figure out the top issues. Let’s say that I would like to add namespaces to my new plugin version, how would I know how many users are in risk still using PHP 5.2? Without tracking PHP versions, it would be impossible. And that’s just one use-case.

          I already mentioned it in one of the responses here, but wouldn’t it be awesome if, in a case of a major security leak, the plugin developer could interact with you to tell you when the patch is ready? I would love to have that.

          Like any data in the world, if it goes to the wrong hands it can be abused. But I strongly believe in my fellow plugin developers–we are the “right hands.” And based on personal acquaintance with the WP developers community, the data will be used to improve the ecosystem (at least by the most).

      • @Mark K, there is no such a thing called “insecure idea” or “secure idea”. It looks like after being 2+ years in service, 17k+ downloads, others commented positively, and more than 5000+ sites/plugins developed by WPAS, your two of the best WordPress experts were wrong.

        Spreading hyperbole on an open source software without proof is not a sign of authority or expertise . I and my wife are behind this “insecure idea”. We have 30+ years of combined experience in software development and grad degrees in computer science in addition to being core developers of one of the most advanced development platforms ever built for WordPress.. and yet we do not call ourselves as experts on anything.

        In the end, as members of WordPress community, we should not be badmouthing other fellow developers and designers but support them for being innovative and taking risks.

        My previous comment was not meant to degrade your idea or comment. I agree with you on the privacy 100%. As you said, there are serious privacy concerns whenever you want to collect data. That’s why developers providing a service like Freemius Insights should use double opt-in when signing up users.

        • While it’s legit, it’s also not expected. Why would a service for tracking php / WP / plug-in / theme users need my *email*?

          As a user I would be happy for a developer to collect information based on environment / application information – but not personal data like my name or e-mail. So, as a user I would definitely not opt-in.

          As a developer this really reduces the usefulness of the service: I’d be asking for data I don’t want and (a lot) of users wouldn’t want to give.

          I hope the service does succeed, it’s a really solid idea – but it would be great if you could consider allowing developers to request the data they want. Or offer pre-set levels.

          The web-hooks also lead you to a legal quagmire. I’m assuming you have legal ownership of the provided data. The web-hooks expose that data to a third-party (the developer), who could as mentioned in the article sign me up to a newsletter I never opted-into.

          While legal side of that can be swept out of the way by adding a sentence to the effect of ‘you agree we can share your data with our partners’ – as a user, that’s another reason to opt-out.

        • Appreciate the feedback @Stephen. At the moment, ALL the data that we collect is valuable and actionable. We put a lot of thinking to make sure we only collect the “minimum viable data”, there are use-cases for all, we don’t collect it for the sake of collection.

          Here’re two common scenarios why email collection is very useful for you and your users:

          1) Let’s assume that you mistakenly release a plugin version with major security leak. Since you are a responsible developer, you immediately patch it and release a new version to the repo. Unfortunately, it takes time till your users will all upgrade to the secure and patched version. BUT, with Freemius, you’ll be able to see all the users who are still using the vulnerable version and send them an email to encourage them to upgrade. You’ll be their hero, and they will be thankful for you taking care of them.

          2) As you read, Freemius Insights adds “Deactivation Feedback Form”. Let’s assume that 10% of the users who abandon your plugin do it since you don’t have featureX. Since you are customer feedback driven developer, you develop that feature to stop losing those 10% of users every day. Now, you can email all this hundreds/thousands of users who abandoned your plugin because of featureX to try and win them back. Not only that you’ll win some of them back, but you are also a hero since you listened to your users and made the extra mile to implement it and engaged with followup after it’s ready.

          With regards to the webhook, it’s in the responsibility of the developer what he does with the webhooks. But we’ll do our best to educate about do-s and don’t-s, and best practices, to prevent any legal violations.


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: