Cloudflare’s privacy-first Web Analytics is now available for everyone
blog.cloudflare.com
blog.cloudflare.com
Options to purge analytics data and visitor logs would also be handy to give us more control over our users’ privacy, as well as the ability to transparently see how much of our user data you have collected and for how long it will be retained.
And while I have your ear, please consider supporting web servers hosted on non-default ports, and the setting of custom Host headers behind your reverse proxy. (in self-serve - hosting on privileged ports shouldn’t be a requirement of using your service for both security and IPv4 exhaustion reasons)
Love Cloudflare. It’s good to see your team self-aware about privacy concerns and working to mitigate some.
Are you looking to rewrite the Host header as the request gets passed to the origin (without changing the resolution of the origin)? Or something more like domain fronting?
An example or two would be great so I can share with the team.
Example 1: A third-party service does not support custom domains, only responds to "Host: my-company.saas-helpdesk.com". For a clean user experience, I want "support.my-domain.com" to reverse proxy to "my-company.saas-helpdesk.com" while rewriting the Host header to their origin as "Host: my-company.saas-helpdesk.com". (I realize CSP headers and all sorts of pain might happen here - perhaps not the best example - but would be great flexibility to have around)
Example 2: My startup's origin only responds to "Host: beta.mydomain.com", and the developer with access to its code is on vacation. I want to release my product. I point "www.mydomain.com" to the IP hosting "beta.mydomain.com" but since that origin does not respond to "Host: www.mydomain.com" - it does not work. I need a Host header rewrite.
Thank you for your time!
What Workers does allow is for you to send a request to a different hostname. In this case, the Host header matches the DNS lookup. So if the third party is on Cloudflare, the request will go through their Cloudflare security settings.
It also allows, via the `resolveOverride` option, for you to do DNS lookup that doesn't match the Host header, as long as the Host header specifies a hostname within your domain. You can't forge a Host header specifying someone else's domain.
(Full disclosure: I'm a co-founder at Admiral)
Any plans to make the "continue without disabling" button harder to click in the future?
But I’m curious - do you have any off the cuff stats on what is typical as far as % of users with Adblock across various types of audiences?
Also, on the pricing page there's a "Get Free Analytics" button that you should be able to click. If you have any issues you can let me know: james at getadmiral.
I'm old enough to remember an internet that respected the sacred open ungated plain of knowledge. Publishers lost the privilege to monetize when they insisted on tracking, whether the visitor paid or not.
How do you sleep at night?
It could be ad-blockers, though. And I want to emphasize a point you mentioned briefly: it very much depends on your target audience. An anecdote from several years ago, around with IE was still the plurality of traffic on most sites but no longer the majority. Two web properties run by the same company, with different audiences. On one of them, IE did not crack the Top 5 in browsers, and was actually outnumbered by Opera. On another, the entire Top 5 browsers were different versions of IE, and Chrome and Firefox combined were less popular than IE6, IE5.5, and AOL's browser (which apparently was a reskinned IE7).
The moral of the story is, what's true for everyone may not be true for you, and vice-versa.
When such crawlers use a distributed network of machines to crawl, there's no easy way to identify them as such, other than _guess_ that they're robotic in nature due to them coming from "data centre" like IPs (i.e. AWS, Azure, GCP, waht-have-you).
While such requests may well be users using those "data centre" services for, say, a personal VPN... the overall pattern is what gives them away.
Not all users look at a page and then start requesting (maybe from a separate IP, mind you, but still from the same provider yet with the same UA) each URL in that page in succession.
Crawlers who want to stay under the radar are much, much harder to detect as such nowadays.
I'm sure it'll be there, lots of people will be interested in what differences a page shows from different vantage points or to robots, but it's probably less than a percent of all robot traffic.
Though checking the thread above mine, I'm not exactly sure what I was replying to. Didn't it say something about robot traffic that wasn't identifiable as such? I don't see that anymore.
Say that again please? Is this tracking unique Referrer’s? What if a significant amount of traffic is direct?
That Google Analytics offers more in depth features is irrelevant for most people.
Thanks! If you do end up "orange clouding" and proxying your site through Cloudflare, we can show you lots of stats about your website, even from clients that don't support JS :)
I occasionally spend time going through the analytics section inside the dashboard. I suppose those are data points gathered by your edge servers (?). If true - how is that different from what is launched today?
Also, if your site is already behind CF, it's not like you give them much more information than they already have.
My thoughts exactly. I'm hoping that we'll see a move from Google Analytics towards more privacy friendly services as they improve.
Then again, I'm not sure marketing people will want to move away from Google Analytics. And I don't think marketing people will read news from cloudflare.. so we'll have to educate them.
What's the point?
You could go with good log parsing programs like awstats.
Am I just being completely incompetent? This feels like it should be a front and centre stats table somewhere
e: oh I was still on the old stats, same bug others reported.
Side note I don't believe for a second my personal blog has had 500 unique visits in the past 24h. I've never really trusted Cloudflare's ability to count visits properly, gotta be miscounting assets as unique visits or showing me Google bots or something there.
I've been using Simpleanalytics, which is pretty good overall, but they keep messing with their site and breaking things...
I think it's a good solution for small side projects when you don't need very accurate analytics.
Marketers sadly don't seem to give a shit about that.
The cookie banner is required due to the ePrivacy law which predates GDPR.
GDPR consent would still be needed in what concerns personal managements and the reasons for collecting, storing and processing said information.
Also browser/device/viewing environment info is a key piece of GA and not something anybody has replicated as well. (the ability to intuitively drill down and compare is second to none with GA. you have to create segments in omo witch is a like 10 click long process with 3 processing pauses vs clicking on `windows` to drill down by family to os version or clicking on a referrer to see the pages they refer traffic to by visit)
They shouldn't even try to report "visits" if it won't be accurate because now they're just going to have a bunch of confused publishers asking why the numbers are so different than GA.
Basically just want to know roughly how many people are reading my blog posts and if any old posts are getting big upticks in traffic.
Hopefully this fills that need!
Small issue; when clicking the link you provided I just get redirected to my accounts dashboard.
Edit: There was a link to web analytics in the right pane, and that worked for me
(We actually did have a replication issue where some folks in the EU had trouble accessing this page)
Tired of this broken all green 'status pages'. :(
Sorry to hear that. We appear to have a client-side caching bug (ironic!)
Can you try refreshing on the 404 page and see if you have access now?
The token makes it seem like it's per-user rather than a general one everyone gets.
At launch, we just support one token per account. We are already working on supporting multiple analytics tokens in one account though!
Particularly looking to add a CNAME record in my DNS to point to the script's domain and have it effectively served from a subdomain of my site.
Is it only an entry-point to attract people on other paid services?
So far Cloudflare cdn in my experience is much faster than google or Amazon. Google cloud cdn really disappoints me. Cloudflare v8 isolate based edge workers are pretty phenomenal too.
You always get what you pay for!
1) JS-based analytics (the free one, advertised in the blog post)
2) Edge server logs based one (available on Pro+ plans only)
Am I right?
I’m disappointed.
I just need an analytics solution that somewhat guarantees I do or don’t need to use a cookie banner.
I need to know how many people visit my website without bothering them with annoying popups.