Shifu is our in-house CMS (hand-crafted), that works perfectly as an agentic CMS by accident!
The main reason for that is that the structure is really simple and all content + structure is JSON. You can generate modern websites with a single prompt!
https://t.co/bLUqt3u5ff
Our website got a visual upgrade, thanks to our CMS working perfectly as an "agentic" system! 🤖
We'll keep programming by hand, but for stuff like this, it's perfect! You can check out the CMS using the link below.
Our upgraded website!👇
https://t.co/k7TTffvPVc
We finally have a release date for Pirsch version 3! 🥳
It will be released on November 21st!
On that day, we will migrate the existing statistics to the new data format. At first glance, not a lot will change, as we have mostly changed the internals. We'll share more details soon! 🧐
No cookie banner. No blind spots from ad blockers. Our new open-source #OrchardCore module adds privacy-friendly analytics (via @PirschAnalytics) and a URL shortener with server-side UTM tracking.
🔗 https://t.co/krTJAwJJBC
🎥 https://t.co/SAaQe0Nlsg
#OrchardCMS#OpenSource
So far, it's looking really good 👍
We will roll out version 3 as an incremental update. First, we will migrate to the new data schema (JSON support for events) and use it internally.
Afterwards, a new API version will be made available, including a simplified permission model that you'll be able to use to dynamically query reports!
See our last post for details on how this works, or follow the link below.
The first draft for v7 is merged! 🥳
We'll now start integrating and testing it in Pirsch. Hopefully, there won't be too many bugs🤞
https://t.co/yeNgh9m5K0
@rubenssoto_ai@nicopuhlmann@mixpanel Just try it. It's free for 30 days 👍
Tracking is the first step to optimize traffic streams. We found a ton of sites that you can use to build back-links via our referrers, just to give one example.
Two months after the change, I can report that it works!
I managed to reverse the trend of losing visitors for a specific page. Check out the quoted post for how I did that.
It is now growing 🔥
It's probably a bit boring as a Tweet, but we're really excited, as this will make everything so much simpler:
- Storing *full* JSON as meta data on events (think of storing the entire shopping cart for example)
- A *single* endpoint for all reports (not including funnels), you'll no longer have to use dozens of different endpoints as an API user to read statistics + it's way more flexible
- New filter combinations (you can compose logical groups)
- Faster data ingestion
- Better reporting performance
- New and improved bot filters
And much more!
The first draft for v7 is merged! 🥳
We'll now start integrating and testing it in Pirsch. Hopefully, there won't be too many bugs🤞
https://t.co/yeNgh9m5K0
We've decided to roll out API version 2 in parallel to v1. The v1 API will use the "old" version of our open-core library, while v2 will use the new one.
This ensures data integrity and that everything is well tested before we replace it entirely.
1/3
A lot of traffic to @PirschAnalytics is currently coming from https://t.co/xtca2BWDZt.
I haven't compared our pricing to Plausible in a while, but man, their tool might be simple, but 10+ websites is only available on the enterprise plan? 👀
Compare link below 👇
With our latest update, you can now track events via HTML meta tags 👏
This works via a selector and makes it possible to set up more advanced event tracking without the need for JS.
See the example screenshot below.
Docs link in the comments 👇
3/3
Reporting will be simpler (a handful of endpoints instead of a dozen), and events will support nested meta data.
Here is an example for such data (JSON):
{
"cart": [
{"id": 591, "name": "Lamp (white)"},
{"id": 79, "name": "Door Stop"}
],
"total": 5930,
"currency": "USD"
}
We've decided to roll out API version 2 in parallel to v1. The v1 API will use the "old" version of our open-core library, while v2 will use the new one.
This ensures data integrity and that everything is well tested before we replace it entirely.
1/3
Development of version 7 of our open-source core has begun! 👏
It will bring significant enhancements to the data ingestion and reporting API. These improvements will be available in Pirsch v3 once the core is ready later this year.
Follow along on GitHub! 👇
2/3
Don't worry, API v1 will stay intact, but it will be simulated on top of the next version of our open-source core. This means you don't need to use the new API, but it will be simpler and more powerful.
Lombiq has added a new Pirsch Analytics integration to the Orchard Content Management System! 👏
Read their blog article below to find out how it works and why it's important. It has some great integrated features, such as a URL shortener that improves tracking accuracy.
👇