The Plausible Blog

We’ve had an amazing journey to date. It took us 324 days to reach $400 in monthly recurring revenue (MRR) since we got our first paying subscriber on May 14 2019. Then things got a bit crazy.

There are several privacy concerns with running Google Analytics but there are worries about data accuracy too. How much data is missing from Google Analytics due to adblockers and privacy-friendly browsers?

We’ve grown from less than 100 subscribers to more than 4,000 subscribers since April 2020. With all this success also comes a growing volume of support requests.

Google is rolling out a significant change as a part of their page experience ranking algorithm in June 2021.

As a site owner, you’ve probably heard about Google’s page experience update and the introduction of Core Web Vitals but what does it all mean?

Google is starting to track your site visitors for advertising purposes even when you’re not using Google Analytics or having any relationship with Google.

Started your WordPress site, published some posts and now want to get some stats to figure out how you’re doing? It’s time to install a WordPress plugin for web analytics.

We’ve made it to $10,000 MRR with Plausible! Several people asked about our lessons learned, so I wanted to share some in this post.

Plausible Analytics is the first open source project I’ve been involved in as a developer and maintainer. And what a great journey it has been until now.

Having 404 error pages on your website can lead to a bad user experience, a negative first impression, and even damage your search engine rankings and traffic you get from SEO.

Outbound links play a significant role on the open web, but how do you track clicks on outbound links using your website analytics? Here’s a guide on how to automate external link click tracking on your site using Google Analytics and Plausible Analytics. Let’s get started.

TL;DR: A privacy policy is recommended for all sites if you want to be transparent and open to your visitors. If you’re not collecting or processing any personal data and not using cookies, you may not legally need a privacy policy. For all other use cases, a privacy policy is legally required.

We experienced big growth in October, breaking our traffic and signup records once again. These numbers can be attributed to Marko who published three articles that landed on the front page of Hacker News. Here are the stats from last month:

Plausible Analytics is a software as a service open source web analytics project. With the increase in popularity of Plausible in recent months, we’ve become aware that there are risks associated with permissive open source licenses that corporations that don’t care about open source are happy to take advantage of.

Plausible seems to be settling into a more steady rate of growth. I had to double our server capacity in late September to accommodate the new trial signups and customers. Here are the stats from last month:

UTM parameters are a useful tool for business owners. They can help you get more insights into the dark traffic, track paid marketing campaigns, newsletters and identify specific pieces of social media content that deliver the best conversions.

Apple has declared privacy a “fundamental human right” and now they’re putting their money where their mouth is, and doing something about it. Apple’s Safari 14 browser and its Privacy Report names, shames and prevents websites that use cross-site trackers to profile web users.

Plausible Analytics is a simple, lightweight, privacy-first and open-source web analytics. We reject, exclude and say no to the majority of the best marketing practices for growing a startup.

The recap for this month is a week late because I just got back from holiday. I’ve been working on Plausible pretty much non-stop all this year so it felt great to take a breather. We still got a lot done in August:

We’ve just had a successful Product Hunt launch for Plausible Analytics. More than 850 upvotes, more than 100 comments, featured twice on the official Twitter account and in the daily and weekly newsletters too.

Plausible Analytics is a simple, lightweight, open source and privacy-friendly web analytics tool. We’re a SaaS startup with subscriptions as a business model.

This last month I’ve been able to get into a nice groove with development. We added a couple of new metrics that should help customers understand their traffic better.

Google’s Chrome browser is the most popular web browser. It has a market share of more than 70%. Whatever new policy Chrome implements will have an affect on all websites as chances are the majority of your visitors use Chrome too.

The last few months have been remarkable for Plausible Analytics. We got more than 180,000 visitors in this period which is a 2,200% increase compared to the prior period. We also saw 10x more trial signups and a 690% increase in subscribers.

California Consumer Privacy Act (CCPA) is a Californian privacy law that has been inspired by the European General Data Protection Regulation (GDPR) but it also differs from it in several ways.

We have now moved all of the website data from servers in the UK to servers in Germany.

June was easily the best month of all time for Plausible. We added some large customers and had our biggest revenue growth ever, both in absolute ($) and relative (%) terms.

What’s the difference between server logs such as AWStats and JavaScript-based web analytics such as Google Analytics? Are client side or server side analytics more accurate? And which should I use on my website? Let’s take a look.

Many open source projects are terribly under-resourced and under-funded. Some open source developers even have to sacrifice their financial security to work on their passion.

Plausible Analytics has been open source since September 2019 but we haven’t offered a convenient way for people to host the code on their own infrastructure. There’s always been a strong interest from the community to self-host the code.

Let’s take a look at the meaning of GDPR, how it impacts web analytics, steps you need to take to make Google Analytics GDPR compliant and also explore our GDPR compliant Google Analytics alternative.

Last month we joined Adam Stacoviak and Jerod Santo over at changelog.com to talk about Plausible Analytics.

Another month, another update. Here’s what went down with Plausible in May:

Are you confused about using Google Analytics on your website, the cookies and the requirement to show the cookie consent banner to your visitors? And can you have a cookieless web analytics alternative to Google Analytics? This post is here to figure it all out. Let’s get started.

April 2020 was by far the most successful month in Plausible’s history. Here are the highlights from the last month:

Over the last few weeks, we’ve been in touch with many different website owners who are considering our Google Analytics alternative product. I’ve been surprised by the number of people who have asked something along these lines:

Google Analytics is the largest web analytics platform. 84% of sites that use a known web analytics provider, use Google Analytics to track their visitors and get website statistics.

We recently relaunched Plausible Analytics as a no-cookie, GDPR compliant alternative to Google Analytics. We had some very eventful days and here’s what we learned.

We are working on a leaner and more transparent alternative to Google Analytics. It’s called Plausible Analytics and it comes without all the privacy baggage. Here’s a look at some of the issues with Google Analytics.

March has been one of the weirdest months in my life. I had a week-long holiday in France just before most countries went into lockdown due to the coronavirus outbreak. I flew back to Estonia 2 days before the borders were closed. Having flown through Geneva airport, I had to strictly self-quarantine for 14 days.

As promised, here’s another monthly update on building Plausible. February was a really good month:

I haven’t been regular with updates on how Plausible is doing, but I intend to put more effort into this blog this year. Let’s kick things off with the highlights for January 2020:

If you’re running a website with Google Analytics installed, you may be wondering how it affects the privacy of your website’s visitors. There’s a growing distrust towards the digital advertising sector but what are the actual issues besides calling out ‘creepy’ ads? Let’s discuss the wider ethical questions around personal data collection and digital targeting.

One of the main reasons I started Plausible was to provide a more transparent alternative to Google Analytics. I believe that people should be able to control and know about their data, instead of having it sold to the advertisers behind their back.

If you’ve ever had to develop transactional HTML emails with slick designs, you’ll know that it’s a complete mess. The incompatibilities between email clients are way worse than what you see with different browsers. Testing emails is extremely difficult, and there’s a seemingly endless number of problems with various clients.

I spent the second half of June back home in Estonia to recharge my batteries and reconnect with family+friends. Summer solstice is a huge celebration in Estonian culture so everyone seems to be on holiday at the moment, enjoying nature, good food and drinks. I haven’t had as much time for Plausible as I normally do, but I’m totally OK with that.

For more than a decade I used a variety of products made by Google. Their products and services are reliable, intuitive, and often free to use. Like many other programmers, I really looked up to the company and followed their rapid rise to one of the biggest companies in the world.

It’s been 4 months since I wrote about the analytics tool I want. My idea was to create an alternative for Google Analytics that simplifies the UI and enhances the privacy of online tracking.

Solo founders and makers often have a dilemma: when communicating with customers, should I describe myself as I or we? It’s tempting to use a royal we, even if you’re working on a product alone:

The meteoric rise of front-end frameworks like React, Angular, Vue.js, Elm, etc. has made single-page applications ubiquitous on the web. For many developers, these have become part of their ‘default’ toolset. When they start a new project, they grab the tools they know already: a REST API on the backend, and a React/Angular/Vue/Elm frontend.

This week, I worked on some under-the-hood improvements to Plausible to give me better insights into my userbase. One of these was to store a last_seen timestamp for all users. This is a private piece of data that I use to determine:

• How many users are actively logging on and checking their analytics
• What is the average usage frequency of Plausible?
• When should I consider an account as ‘rotting’? Meaning I’m about to lose them as a user/customer

In general I don’t think that the tech stack matters too much for software projects. Especially if you’re a solo maker, almost all of the risk is on the sales and marketing side as opposed to the tech side. The best approach is normally to just pick some boring tools and start solving your customers’ problems.

Working on plausible.io I often find myself doing things I have no clue how to do. I struggle massively with marketing, copywriting, and most of all, UX/UI design. Here are some tips I’ve found helpful when trying to design for the web as an unimaginative developer who hasn’t designed a single thing in his life.

While working on Gigride, our marketing head asked me to integrate Google Analytics for our landing page. My first thought was: