Plausible Analytics

January not only marked our 5th anniversary but it was also our best month yet in terms of MRR growth! We’re celebrating these milestones with our first logo redesign in all this time. Here’s to the next 5 years! 🙏😍🎉

We have cleaned up your "Top Sources" report! Now, each source is consolidated into a single entry, regardless of capitalization stemming from UTM tagging differences. For example, If you saw "Facebook", "facebook", and "FACEBOOK" as three separate sources (due to differences in UTM tagging and referrals), it all now combines to show one source: "Facebook." Want to see the specific source data? Just click on any entry to see specific source breakdowns, or explore the "Campaigns" tab. We've updated all your historical data too. Coming up: Straight up see your sources combined into types of acquisition channels, like "direct", "email", "social", etc. Your dashboard is getting a whole lot exciting. 🤩

More than five years in business and still growing mainly through "word of mouth." This works because of simple basics: people believe their trusted people to give a product a whole-hearted chance. So all we really try to do is enable that chance by constantly listening to feedback from our existing users, and improving the product. 🚀

🎉 Setting up enhanced measurements is now super easy! Just pick what you need from a checklist during onboarding, and we’ll give you a code snippet to use. You can also update these settings anytime by clicking "Review Installation" in the General page of your "Site Settings."

Implementing enhanced measurements is about to become a whole lot easier. Construction underway. 👷

Filter and segment your traffic based on custom properties. A custom property is an attribute about an event (pageview or custom events) tracked on your website. Let us say your life was analogous to your website and it had a tracking device. You could define certain general events to be tracked. Like, a “waking up” event. Then, the descriptive data (properties) to be collected about the “waking up” event could be “time-of-sleep”, “quality-of-sleep”, “length-of-sleep”, etc. Later, you could view a report about your waking up patterns in the past 3 months and these tracked facts would be presented as custom properties. Coming back to websites, following is an example from our own live demo to see the visitors segmented by the language they're using to view our site. Tip: your Plausible dashboard can be directly filtered with a custom property.

Using Plausible Analytics for Revenue Attribution: In this example, the dashboard is filtered by “All time” data, the goal of “complete purchase” and the property of “product category is hoodies”. So every metric seen on this single-page report is directly related to the sessions in which the conversions (hoodie sales) occurred. You can see the conversions, revenue earned, the campaigns that contributed to the sale (possible with UTM tracking), the all-time top pages that received the most traffic (and how much) in the sessions receiving conversions, and some other data like locations and devices. By toggling among UTM sources, mediums, campaigns, content, and terms, you can understand the effectiveness of such traffic sources too. Similarly, you can toggle between Top, Entry and Exit pages to understand the best performing webpages.

New record: Our new largest subscriber's site is pulling in 100k+ current visitors! And our servers are in high gear. 🔥

[Anatomy] How a user travels from a place on the internet to converting on your site? Think of it from the perspective of the tracking JavaScript (JS) snippet provided by your web analytics tool. When a visitor comes to your site through a referral link, the snippet checks for any referral or UTM values. So, it is able to record where the session came from. This, by the way, is how our "Top Sources" report is made. For example, if someone clicks on a link from a social media post with utm_source=facebook, the JS snippet will note ‘facebook’ as the source of that visit. Then as the user interacts with your site, the JS snippet keeps recording such interactions in the form of pageviews, button clicks, or any custom events for that matter. Let’s say, the user now goes to a subdomain, where you have a sign-up button tied to a key business or marketing goal. The JS snippet continues to monitor their actions. This approach ensures that the visitor’s session remains active across your main site and its subdomains. In Plausible, you can set up custom events or pageview goals to track specific actions and even create a funnel to follow the user’s journey across a domain and its subdomains.

Creating an event: Web Analytics edition In GA4: - Determine if the event already exists under Enhanced Measurements, or Recommended Events from GA4's robust documentation. - Follow specific naming conventions for each event name (snake case) to avoid breaking your setup. For eg. While setting up an ecommerce event on GA4, if you don't use the exact recommended event name, "Purchase" (maybe you overlooked and named it as "transaction"), your setup will break. - Make sure you adhere to the character and other limits (refer screenshot). ...And also know that you're supposed to know all that. 😅 -- In Plausible: - Decide what to track. - Name it whatever you want. - Setup in minutes, not hours.