volument

This one is significantly more active than the others.

Can you give few examples of those other companies? Thanks.

It used to be like that, but that's no longer happening. Last winter, there was no snow in Helsinki at all :(

ePrivacy talks about "information stored in the terminal equipment", which includes any information you can get from the device. For example the user agent, location, and operating system. It's not about the information itself being essential or not, but what you do with it: is it for essential purposes (consent not needed) or non-essential purposes (consent needed).

Yes: the location information on the browser. You cannot access it for non-essential purposes without user consent. See Article 5 / Statement 3 in the ePrivacy directive[1]

[1] https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CEL...

That depends solely on what is an "analytics cookie". If it's a permanent identifier, then it's considered PII and requires a GDPR consent. Otherwise GDPR doesn't care. You can freely store foo=bar to a cookie.

The list is only for non-essential services such as website analytics. Is there a better cite for Czech Republic? Happy to edit.

EU is still working on a new version of the directive. I heard they have been doing it for three years now.

The eDirective states that the browser and device information (like the URL) is private data and you need a permission to access it for non-essential purposes such as analytics. This is why Simple Analytics also needs a cookie banner, contrast to what their marketing says.

Cookies are not an issue for GDPR, it's all about respecting users' privacy. In fact you can freely store anonymous data to cookies, localStorage, and sessionStorage without issues. The problem comes when you are dealing with personally identifiable information such as permanent identifiers.

You definitely need a "cookie banner" when using Simple Analytics, Fathom, or Plausible. Any service that accesses the device information such as the URL needs a permission from the user according the ePrivacy directive.

We have consulted EU law specialists when building our upcoming analytics service that is as privacy-friendly as Simple Analytics, while still measuring important things like retention and conversions. More information:

https://volument.com/learn/data-privacy

Being interesting is not enough when you are picking a language for your next major project.

Really curious to hear your findings! We're happy users of Badger, but we have never looked it's internals. I guess you can list the differences you've found without using a bad mouth. Thanks in advance.

This is exactly what happened to me: I did not take a further look on Haskell just because its syntax seemed so weird.

https://volument.com might be a good pick since it focuses strictly on conversion optimization. It attempts to measure the more general conversion flow, known as the AIDA funnel (awareness, interest, desire, and action).

Here's one we are working on: https://volument.com — it focuses on conversion optimization.

That website had too many annoyances and content blockers that I had to leave (which wasn’t easy either). I’ll remember Bloomberg. Same with Forbes.

This feels like a response from a seasoned backend engineer. Seasoned frontend developers value user experience and design — thus the tendency to go "back to static" and rarely back to WordPress.

Hey, we at Volument (volument.com) are using Redis as the primary datastore. We are extremely happy we chose that option. It gives us everything we need: extreme performance, scalability with customized sharding, stability with sentinels, and most importantly: a fantastic data model that is enjoyable to work with. We don't need to add anything extra to our stack if we later need a pub/sub system or realtime support for our custom chat app for example.

We use a custom Go-based system to collect the crazy amount of analytics that easily exceeds our memory, but for the core business logic, Redis is a top-notch choice. We actually build our whole CRM on top of Redis: https://volument.com/blog/the-power-of-simple-crud

Great to hear! Can you shed some light on "script size constrained serverless scripts"? Would possibly make a good FAQ entry.

And yes. Bareserver needs Node currently and is not designed for client-side testing. It's trivial to add if needed.

Made it more clear that account is not needed and email is enough. Thanks!

True. However, according to "The State of JavaScript" [1] Jest is the most popular option these days and it is chosen because it is simple, lightweight, fast, and easy [2] — all of which are the reasons one would choose Baretest.

[1]: https://2019.stateofjs.com/testing/

[2]: https://2018.stateofjs.com/testing/jest/

Good points. Just want to point out that comparing with a basic "sum" function measures the performance of the test runner and leaves out the time it takes to run the application code. Baretest has little overhead so it is good for testing the actively developed code with the `only` function.

With Baretest all the custom things you do like transpiling TS or rendering React is done outside the test runner. This way it can test cases of any complexity.

> Web designers now do the job that typographers did 30 years ago

Easy to agree.

Thanks! Reading makes a lot of sense. Especially fiction, since I'm so bored of all the tech books.

> It serves about 35,000 concurrently running A/B experiments,

With that amount of optimizations, you would expect them to have the best user experience in the world. Do they? I think there is something severely wrong with the current A/B testing methodology.

That's our goal too. We pushed out this simple CRUD first for commenting and private support chat/email. We'll add realtime chat functionality later if needed. Currently, we are doing fine without it.

We could ditch Recurly because we had all the necessary billing data available on the new, central system. Not before that.

This is the original post where the "product/market fit" concept was introduced to the masses.

Bounce rate is essentially the ratio of visitors who visited one page. Someone might stay on a page for 30 minutes or so and the visit is interpreted as a bounce. This metric fails to tell whether a page is good or not.

More about meaningless metrics: https://volument.com/learn/the-broken-metrics

Should have worked. We'll fix that. Thanks!

Here's how Volument works: https://volument.com/learn/volument-data-model

A/B testing in Volument is quite different from, say Optimizely. You can compare a lot of things in apples-to-apples fashion: landing pages, inner pages, market segments, campaigns, site versions, etc. And you can compare both how much traction something generates, or how engaging a page is.

The causation thing is just something we measure. We measure how people behave on their first visit, how intensively they return, and how much they convert. It's not about the statistical validity, it's about choosing metrics that are essential for conversion optimization.