It'd be good to be able to disable registration on self-hosted instances, so people can't create accounts on private instances.

"i have quite a few websites and i would like to change my landing page. i would like to order it such that the important sites are on top and the open source projects are on the bottom. currently there does not seem to be a UI element for this."

(imported from the old roadmap)

"Add meta data to page events so I can see which Landing Page / User Group has reached a Goal."

(imported from the old roadmap)

"Fabric.io was bought by Google. Now it is being sunset in favour of Firebase Analytics. There is a need for a simple dashboard analytics for mobile."

(imported from the old roadmap)

In HOSTING.md you have written about the hosting setup you are using with Digital Ocean. It would be nice to have details about what kind of traffic that setup is handling right now.

"It would be nice to have an option to reset (zero) the stats. Thanks!"

(imported from the old roadmap)

Hi folks,

thank you so much for your work. 🙏
I just thought it would be nice to have an official 🐋 Docker container for easier trying out plausible on a local machine or server.

See also nolt.io issue 56.

It'd be great to disable the subscription workflow entirely when running self hosted. A 100 year free trial is definitely a quick way of implementing (and so generous 😉), but it'd be nice if it were removed.

Specifically, the trial box on the top right, the "Subscription Plan" box in settings, and any integration with upstream payment.

First off, thanks for working on this! 👏 As a privacy-conscious person, I for one appreciate it.

I wanted to see if you had any API documentation available, as I'd like to build an Android SDK for use of Plausible in some of my apps. Many of the reasons for tracking user interactions with a website apply to an app as well, and I'd like to help provide a nice alternative to Google Analytics for mobile developers as well (at least on Android). I don't imagine you want to take on the burden of supporting an official Android SDK but I'd love to put together an unofficial one an perhaps collaborate if you're interested.

Hello, we just enabled our public dashboard at https://plausible.io/kitspace.org/ (looks great!)

For our use, I think it would be cool if people could click on the top pages: i.e. go "oh what's this, it seems to be very popular" and go check out the page on our site.

"When sending an event, it would be nice to attach arbitrary metadata to it. For example, I could send a “SignUp” event but add a formName property as metadata to track which sign up form they used. i.e { formName: “footer” } or { formName: “popup” }

Also need the ability to sort events by that metadata in the dashboard UI"

Update: Metadata for goals is now live! See instructions here: https://docs.plausible.io/custom-event-goals#using-custom-props

"I’ve added Plausible to my home screen, but the website doesn’t have an iOS icon. Creating a simple iOS app using a web view would also be nice.

This would be much appreciated and would take about 5 minutes. Just create a PNG (512x512) file in the root of the site named: apple-touch-icon.png with the apps icon. Done.

I’d recommend this, if you haven’t yet seen it: https://realfavicongenerator.net/"

(imported from the old roadmap)

Our self hosted version is behind a network-level authentication wall already, it would be nice to not require additional accounts.

An easy way perhaps is to automatically sign into the default account and disable the sign out option?

P.S. Thank you thank you so much for supporting open source efforts <3

Hi there,

I am experiencing the following behavior:

1. created an account
2. added a website, added your script to my website
3. tested website, noticed you do use cookies despite advertising you don't, so felt tricked
4. clicked delete account, got message "account cannot be deleted",
5. account still there, but website disappeared in plausible account
6. cannot recreate website because it seems it wasn't actually deleted
7. ...and cannot delete account either.

Thanks,
Daniel

One of the main reasons for me to want Analytics is to see the users flow inside the Website itself, so that I can tailor it to the way the users are actually using it. The way I did it previously (when I had Google Analytics) was to have a Sankey Diagram which showed me how many users were flowing from one page to another. Is this something supported by Plausible or planned to be supported at some point?

Details:
For this to be useful for larger websites, I will describe how I would imagine it for a Blog (The web's standard Hello World of websites :P )

The user would define custom page types. In this case, it would be:
HomePage: Has it's own type
About: Has it's own type
Posts: All posts share this type.

Then the Analytics allows me to select a page type (Say HomePage) and see how users flow from there (maybe 90% go to a Posts type page, and 10% to the About page).

Does this make sense?

Example Diagram:

Hello,

Is there an official method for sending custom data via the JS API?

I have seen users use window.plausible('eventName', ...) How would the Plausible API react to an object as the second parameter? Would it serialise it?

So many questions... 😝

Many thanks,
Synth

"A new report alongside the referrers report to show you:

• How much traffic is coming from each search engine respectively
• The keywords that lead to your site being found"

(imported from the old roadmap)

"It would be nice to have a little column added to https://plausible.io/sites so that I can see an overview of my daily traffic, for each website, without having to click through to each one."

(imported from the old roadmap)

"Would love to see current visitors count on the My Websites listing page. At high level, this could be useful to see across all sites in the list."

(imported from the old roadmap)

"It feels like there’s something not rendering 100% right there. Minor thing, but probably good to mention."

(imported from the old roadmap)

"It’d be nice if you could click on urls in "Top pages" to get a breakdown page of the traffic for that specific url, with all the same data.

The same would be true for other items (great to filter on them if you click), but I find myself trying to do it for urls most of all.

I really like this idea of being able to filter based on whatever you click in the UI (referrers, countries, screen sizes, etc). When you click on a page, let’s say would you want to see only traffic that landed on that page (so this was strictly the entry page), or all traffic that visited that page at some point during their session? Let me know if the question isn’t clear.

I think I’d keep it consistent with the original section head (page views) so I assume views rather than landing pages. Landing pages might be nice but feels like it would be another section focused more on the user journey through the site (so I wouldn’t have landing pages but perhaps something like journeys instead)."

(imported from the old roadmap)

The first 962 bytes of https://plausible.io/js/plausible.js (as it is at present) is unnecessary build tool nonsense and should be deleted. Combined with the matching three bytes at the end, this makes up about 30% of the file size (26% gzipped).

The whole inner thing is an IIFE doing no exports, so it doesn’t need that wrapping at all.

Skimming through it, there’s quite a lot of other low-hanging fruit too. Some examples: the programmatic RegExp construction in IIFE for cookie matching can readily be reduced to /(?:^|; )plausible_user=([^;]*)/; XMLHttpRequest.DONE can become 4; window.foo (i.foo as minified) is a waste of window., just write foo if you know it exists; more IIFEs can be vanquished.

I’m also bemused by the plausible_user encoding—to encode it, you URL-encode values, then in putting them in an object JSON-encode them. When decoding it, you URL-decode the entire result first, so that you’re URL-decoding twice. That seems wrong, though probably fairly harmless in practice. But it’d be more compact if you just encoded the object directly and then URL-encoded it once.

Also just FYI, no browser will respect your request for a cookie expiry 3000 years in the future! (I’m guessing you’ve used someone else’s code there; for something like this I’d say hand-write the entire lot, inlining any dependencies manually and making sure they’re sanely written.)

Then as often happens I got sucked into manual minification which is a hobby of mine. Here’s what I ended up with:

!function(e){"use strict";try{var t=window.plausible&&plausible.q||[],n=0,i=function(){return(location.search.match(/[?&](?:ref|source|utm_source)=([^?&]+)/)||[null])[0]},r=plausible=function(t,n){if(/localhost$/.test(location.hostname)||"file:"==location.protocol)return console.warn("[Plausible] Ignoring event because website is running locally");if("prerender"==document.visibilityState)return console.warn("[Plausible] Ignoring event because document is prerendering");var r={name:t,url:location.protocol+"//"+location.hostname+location.pathname+location.search,domain:s,referrer:document.referrer||null,source:i(),user_agent:navigator.userAgent,screen_width:innerWidth};c&&((t=(t=document.cookie.match(/(?:^|; )plausible_user=([^;]*)/))?JSON.parse(decodeURIComponent(t[1])):null)?(r.initial_referrer=t.initial_referrer&&decodeURIComponent(t.initial_referrer),r.initial_source=t.initial_source&&decodeURIComponent(t.initial_source)):((t=new Date).setTime(t.getTime()+94608e6),document.cookie="plausible_user="+JSON.stringify({initial_referrer:(r.initial_referrer=document.referrer||null)&&encodeURIComponent(r.initial_referrer),initial_source:(r.initial_source=i())&&encodeURIComponent(r.initial_source)})+"; expires="+t.toUTCString()+"; samesite=strict; path=/"));(t=new XMLHttpRequest).open("POST",e+"/api/event"),t.setRequestHeader("content-type","text/plain"),t.send(JSON.stringify(r)),t.onreadystatechange=function(){4==t.readyState&&n&&n.callback&&n.callback()}},o=function(){r("pageview")},a=document.querySelector('[src*="'+e+'"]'),s=a&&a.getAttribute("data-domain")||location.hostname,c="string"==typeof(a&&a.getAttribute("data-track-acquisition")),l=history.pushState;for(l&&(history.pushState=function(){l.apply(this,arguments),o()},addEventListener("popstate",o));n<t.length;n++)r.apply(this,t[n]);o()}catch(r){(new Image).src=e+"/api/error?message="+encodeURIComponent(r.message)}}("https://plausible.io");

1.88KB, 0.92KB gzipped (40%/36% smaller compared to the current baseline). Even less warranty on that than any warranty that might have been offered, but it should behave the same. Do what you will with it, including ignoring it if you like.

Just passing by, I have no intention of using your product at this time and do not plan to speak further about this beyond what I have already written in this issue.

"As a privacy-respecting service I think it would be cool if you would accept cryptocurrencies as a payment method for your paid plans. Preferably Monero, as it’s the best privacy coin, but just Bitcoin for simplicity would also be fine.."

(imported from the old roadmap)

At this stage, our payment processor Paddle doesn't allow cryptocurrency payments and they deal with all the VAT and taxes for us. We may move to a more flexible system later on.

First of all, thank you for the work on plausible and especially the recent effort on self-hosting.

I am using podman instead of docker to run the containers. When running the main container, I get the following error:

# podman run --name plausible-eph --hostname plausible --pod plausible plausible:http db migrate
Loading plausible..
Starting dependencies..
Starting repos..
Running migrations for plausible
** (Postgrex.Error) ERROR 42704 (undefined_object) type "regnamespace" does not exist
    (ecto_sql 3.4.4) lib/ecto/adapters/sql.ex:593: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.10.3) lib/enum.ex:1396: Enum."-map/2-lists^map/1-0-"/2
    (ecto_sql 3.4.4) lib/ecto/adapters/sql.ex:686: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.4.4) lib/ecto/migration/runner.ex:343: Ecto.Migration.Runner.log_and_execute_ddl/3
    (ecto_sql 3.4.4) lib/ecto/migration/runner.ex:117: anonymous fn/6 in Ecto.Migration.Runner.flush/0
    (elixir 1.10.3) lib/enum.ex:2111: Enum."-reduce/3-lists^foldl/2-0-"/3
    (ecto_sql 3.4.4) lib/ecto/migration/runner.ex:116: Ecto.Migration.Runner.flush/0
    (stdlib 3.12.1) timer.erl:166: :timer.tc/1

I am using this bash script to start all the containers. I always start the main container manually to make sure the db and clickhouse are up.

Please let me know if I need to add more detail.

I setup a custom domain to broker the javascript include and noticed that Firefox was throwing the following error message in the console:

The script from “https://stats.mashword.com/js/index.js” was loaded even though its MIME type (“text/plain”) is not a valid JavaScript MIME type

Upon inspection it seems that the content-type header is returning "text/plain" when it should be returning "application/javascript". Firefox still loads the script, but I'd like to avoid having this error show up in the console.

"Being able to selectively hide/remove clusters of visitors (For example I had 40 spam visits at 5pm one day, trying to visit pages that don’t even exist on my site), so that they don’t inflate our stats and skew the data in our chats would put Plausible over the moon in my opinion, or an option to filter/remove visitors that end on a 404 would help too.

Spam/bot blocking is currently fairly basic and relies on the bots identifying themselves via the User-Agent header. This can be improved by using commercial IP address blocklists for bots as well as referrer spam blocklists. So we can definitely improve automatic bot detection. I’m not sure about a UI for manual bot removal, however. Since we don’t create individual visitor profiles on purpose, I can’t think of a way for users to select which visitor’s activity to delete?

In this case, the bot visited a bunch of random URLs on my blog for pages that don’t exist, so there are a bunch of pages showing up in my analytics like /random-plugin-name/453545.php (It seems like the bot was trying to phish for sites that may have vulnerable plugins installed, by visiting the pages those plugins would be located at, then when it finds sites that have said plugin, it knows they are vulnerable - thankfully, I didn’t have any of the plugins installed) - so perhaps, a work around could be an option to just remove a particular URL from showing up in the analytics, for example the /plugin-name/45345435.php types of pages, I have about 30 of those in my analytics yesterday. So maybe they can be removed on a URL level rather than a user level? This would help when the bots are visiting random/non-existant URLs like in my case, but I suppose it wouldn’t help when the bots are visiting actual pages that do exist, since we wouldn’t want to remove those."

(imported from the old roadmap)

Was reading: https://opensource.com/article/20/5/plausible-analytics , couldn't get to your roadmap.

https://feedback.plausible.io/roadmap

Error 525 Ray ID: 58d599a59b4fc5ec • 2020-05-02 23:42:41 UTC
SSL handshake failed
You Browser Working Newark
Cloudflare Working
feedback.plausible.io
Host Error
What happened?
Cloudflare is unable to establish an SSL connection to the origin server.

"Some SPAs use hash-based routing. We should have an option to pick that up with the Plausible script"

(imported from the old roadmap)

"It would be really helpful to track the pages that couldn't be found and which ones those are. Maybe set 404 as a parameter to the tracker on the error page or define the page on the admin interface?"

(imported from the old roadmap)

"So you don't have to use anything google related to port it."

(imported from the old roadmap)

Hi, thank you for creating/open-sourcing plausible.io!

It's just what I wanted for personal/hobby projects and very easy to setup / migrate to it (I think it took me less than 1 hour to set it up and migrate all my personal projects from google analytics)

Some questions popped up, most of them already have issues with the self-hosted label, but one I couldn't find is: how do I have to set the environment variables if my email server doesn't require auth?

I noticed in the config auth is set to :always. It appears there's also a :if_available setting documented in bamboo_smtp -- assuming it does what I think, would it be possible to use that or, probably even better, make the option configurable?

Not sure how easy it is, but including a "send me a test email" button would be very helpful

There's no button to revert the setting after having once configured a custom domain to server the JS file

Somewhat like, Google Analytics might need an extra step for SPA, as it does not detect popstate, nor hash router.

https://developers.google.com/analytics/devguides/collection/gtagjs/single-page-applications

gtag('config', GA_MEASUREMENT_ID, {'page_path': page_path});

I believe, Gatsby also counts as SPA on latter navigations.

Hi,

you advertise this product as being cookie-free.
I like that, so I added plausible to my website.

However, when I checked there were plausible cookies in my browser.

Thanks,
Daniel

"The containers have height in px. For people who’ve set a non-default font size in their browser, this pushes data outside the container. Removing the height elements, using em/rem, or using height: auto will fix this."

(imported from the old roadmap)

Clicking the red "Delete my Account" button under /settings results in a 500 error.

"Measure average session length. Breakdown by referrer."

(imported from the old roadmap)

Hi,

Just want to report an issue, it looks like you can concat any string after you put valid domain in custom domain option, including malicious one. It can lead to remote code execution on ssl provision server.

How to repro:

• Add a new website
• Go to settings -> Add custom domain
• Fill it with valid domain concatenated with some command payload
  eg: stats.test.com || wget google.com replace wget google.com with any malicious command, it will run on the provision server

Tested with simple wget and curl, which send request to my server, and my server logs can see the request coming

Hey,

I know you are probably super busy but consider adding https://github.com/marketplace/dependabot-preview and set it to run once a month just to keep on top of things.

Cheers
Sam

Running this self hosted is nice, but it'd be nice if it didn't contain all the marketting site components with it. Having the homepage either be the login prompt, or a list of public sites (configurable?) would be so much nicer!

Specifically, things which act a bit weirdly when self hosting:

• "Live Demo" button doesn't work unless there's a site setup for 'plausible.io'
• Loading up to marketing site for Plausible feels weird.
• Footer links don't really work

"A board where one can see what is currently going on on the page. Things like

number of visitors
URLs opened
etc….

Definitely just a nice to have, not essential imho."

(imported from the old roadmap)

I think the image explains the changes needed

Hey, sorry for (probably) stupid question, but how do I setup custom events while using Typescript? When I add the script tag into html, ts doesn't reflect that and throws a compilation error about window not having a field called plausible.

"Would be great to have ability to send pageviews by HTTP. This is useful for native mobile apps, because obviously JS script is not possible to use.

This could also be useful to send events from your website’s backend so you don’t need to install a script"

(imported from the old roadmap)

"Show all website traffic on one main graph. Multicolored lines.

It would also be nice to see combined data of which devices and browsers users are using across all of your sites."

(imported from the old roadmap)

"My co visits the site but has weird vibes in adblocks block plausible feature and It would be amazing if views could be subtracted by will if they were to ever be downloaded or fully reflective of real hits!
Thanks!"

(imported from the old roadmap)

"Would allow for a KPI for some startups wanting to keep an eye out on how their product is preforming online instead of tracking the signups metric"

(imported from the old roadmap)

"Make a settings button in website’s dashboard page

This, please! I think this is borderline a bug. There should be a navigation menu to go from the dashboard to the site settings."

(imported from the old roadmap)

"CSV file for top pages and time. It would be nice to get an overview of number of views, per timestamp, per page. Just a csv would be fine … I can do the analytics from there.

Would this be possible? I understand if there are privacy concerns. Alternatively just getting the pages part into a .csv file would also be a nice start.

I can imagine that getting the stuff more low-grain is gonna be a tad bit too close for ‘privacy aware’ tracking. But if I can get all the aggregated data that is shown on this page as a csv; that’d be sweet.

I don’t think I can give you all individual pageviews with timestamps in a csv. In fact I’m planning to move to a data storage format where this would be impossible. In the future, Plausible will only store aggregate data so it would be impossible to find individual pageviews.

Providing the same information as you can see in the graph via csv is very possible :)"

(imported from the old roadmap)

"Hi, instead of the “last 30 days” it would be of great help if “Current month” could be added and chosen as default. A lot of people work with monthly targets that “reset” at the beginning of each new month. Keep settings date ranges is cumbersome."

(imported from the old roadmap)

Godaddy doesn't allow me to add the . at the end of the CNAME target. It always takes it away automatically. Is there something you can do on your end to allow it without a .? Or would it work without the . already anyways? As of right now it doesn't load the script yet (20 minutes after setup).