141–150 of 182 posts
1. the OP works for Plausible 2. The OP uses a non-standard call to Plausible which probably isn’t in many block lists 3. It’s in mine
(The site owner submitted the site to HN, and is taking part in the discussion.)
Earlier quoted context omitted.
This depends on monetization. If you're selling copies of newspapers, 2 purchases by 1 customer = 2 purchases. The number of customers is irrelevant. If you're monetizing via on-page ads or affiliate links (as the author is), revenue is much more likely to correlate to unique visitors than to page views.
>> revenue is much more likely to correlate to unique visitors That's the bit I don't understand. Why does an advertiser not value a customer seeing an ad twice, or for a longer time? In fact I would say that those customers are much more valuable because their multiple views bookend an extended period of viewing an ad. If I view a website at home in the morning, then again while at work, I have been exposed to that…
In traditional media, it's pretty much an axiom that people have to see the same ad at least seven times in order to get the message. There is no sin in showing the same advertisement more than once. It's why, for example, advertisers pay extra to have their ad appear at both the beginning and end of a commercial break on television. It's called "bookending."
When digital advertising started, the ad companies decided that someone seeing the same ad more than once was a bad thing, and then convinced their advertisers this was true.
I don't know why this happened. Maybe the digital people had some data that proved it. Maybe the digital people were just computer people and not advertising people and so didn't know about the decades of prior research into this.
But it's where we are now. Digital advertising companies value unique visitors, so web site owners do, too.
Earlier quoted context omitted.
If you use a CNAME (tracker.mysite.example → tracker.example), uBlock Origin on Firefox will still be able to block it. (I have no idea whether Plausible offers this mode of operation. I don’t see “CNAME” mentioned on their site, so probably not.) If you run some kind of proxy yourself on an unconventional name (e.g. “ads.mysite.example” may well be blocked) and make sure that any script it needs loads from your own…
> I have no idea whether Plausible offers this mode of operation The site of the article cloaks `custom.plausible.io` as `ms.markosaric.com`.
Earlier quoted context omitted.
Are you not tracking your sites performance at all or are you just not using Google Analytics of Facebook analytics for that? Are there any (open source) privacy friendly alternatives with similar basic features?
Piwik is probably the most “out of the box” open source GA alternative, there’s also Snowplow if you want it to be a full edge-through-to-data-warehouse solution.
What happened to using your web logs? It requires absolutely no javascript and no third parties and there's no invasion of privacy.
It also is completely useless because of the tens of thousands requests random bots and hacking tools do each day on most websites, the many network hops for mobile users, the utterly impossible task of counting time spent per page (on active tab), conversion tracking and so many data that web logs aren't designed to collect or present in any useful way.
1. the OP works for Plausible 2. The OP uses a non-standard call to Plausible which probably isn’t in many block lists 3. It’s in mine
So, the domain in question is ms.markosaric.com. Which is a CNAME to custom.plausible.io. uBlock Origin is able to block based on CNAMEs, but it is not a default configuration. PiHole V5 blocks based on CNAME as well, and it is actually enabled by default. I run a little blocklist project [1] and I've had custom.plausible.io blocked in my list since April 8th [2]. So, although I didn't have ms.markosaric.com blocked…
1. the OP works for Plausible 2. The OP uses a non-standard call to Plausible which probably isn’t in many block lists 3. It’s in mine
So, the domain in question is ms.markosaric.com. Which is a CNAME to custom.plausible.io. uBlock Origin is able to block based on CNAMEs, but it is not a default configuration. PiHole V5 blocks based on CNAME as well, and it is actually enabled by default. I run a little blocklist project [1] and I've had custom.plausible.io blocked in my list since April 8th [2]. So, although I didn't have ms.markosaric.com blocked…
1. the OP works for Plausible 2. The OP uses a non-standard call to Plausible which probably isn’t in many block lists 3. It’s in mine
So, the domain in question is ms.markosaric.com. Which is a CNAME to custom.plausible.io. uBlock Origin is able to block based on CNAMEs, but it is not a default configuration. PiHole V5 blocks based on CNAME as well, and it is actually enabled by default. I run a little blocklist project [1] and I've had custom.plausible.io blocked in my list since April 8th [2]. So, although I didn't have ms.markosaric.com blocked…
I believe this is the default now, isn't it? [0]
1. the OP works for Plausible 2. The OP uses a non-standard call to Plausible which probably isn’t in many block lists 3. It’s in mine
So, the domain in question is ms.markosaric.com. Which is a CNAME to custom.plausible.io. uBlock Origin is able to block based on CNAMEs, but it is not a default configuration. PiHole V5 blocks based on CNAME as well, and it is actually enabled by default. I run a little blocklist project [1] and I've had custom.plausible.io blocked in my list since April 8th [2]. So, although I didn't have ms.markosaric.com blocked…
It is a default configuration.
Seeing that Plausible Analytics is not using cookies and instead hashes fields including IP address - the measure of "unique site visitors" could be a proxy for false uniques by Plausible Analytics. For example, an user visits once via his data connection and once via wifi - Plausible may see different users where Google's cookie will pin it as one user. Another interesting result is the 16% of total page views - I d…
I think this is probably correct. I wrote my own hit-tracker for my website and I spent a lot of time looking at logs to see if I could reliably track unique users by hashing headers and the IP address. My conclusion is that you can't - you will always double count some users. It is no uncommon for consecutive requests from obviously the same user to come in from different IP addresses. Usually these are either cell…