-
-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Event based tracking #40
Comments
Events are still planned. It's something I will focus on after v2: #129 |
I would find this extremely useful. Is there any way to help with this to speed up the development? |
Here're some thoughts: Ackee will get two new types of data: An event is like a domain. You can add it in the settings of Ackee and it will be shown in the navigation as
An action is basically like a record. It's the entry you create for an event. Here's how it could look in
@emschwartz Could work well along with a |
This sounds great! Let me know if you could use any help or a beta tester |
Hey @electerious, any progress on this? Let me know if there's any way for me to help get this feature launched |
No news for now. I'm currently focusing on the website and stuff around Ackee, but this feature should be the next big thing as soon as I'm back working on Ackee :) |
@electerious what's the time frame for this i.e. when will you start working on it? I'd love to help anyway I can, as this is something that would be very useful to me too! |
The plan right now is: v2.5 => Events Might start with events today 👀 |
Update: I'm currently refactoring a few parts of the UI, because the old implementation wasn't good at handling different kinds of widgets in a view. That's something we need as events can be displayed as charts and lists, depending on what the user specified in the settings. The good thing is that it allows me to remove tons of redundant code. The old state management was done with a REST API in mind, not with a GraphQL API. Will continue with the events once this showstopper is resolved. |
I'm done refactoring the front-end. It's now possible to display multiple types of widgets. I can therefore continue to work on events :) |
Weekly development update: The events are now in the UI. You can add, edit and delete events and change the display type (more on that once it's done). I'm currently updating ackee-tracker to include the new |
Planning to release this in January as v3 along with some other features. As always: It's a lot of work and I'm happy about every sponsor: https://github.com/sponsors/electerious |
v3 is now on the develop branch and ready for testing. It includes the newest beta of ackee-track. You can find everything you need to know in the changelog and in the events documentation: https://github.com/electerious/Ackee/blob/develop/CHANGELOG.md#unreleased I've also added the ability to show average values (e.g. adding an action with a value of 10 and one with the value of 20 will show 15 in the UI. This could be helpful to measure the performance of sites: #207) Feedback is welcome! |
I just tried the new version and its incredible how much faster it feels, especially the installation part! One thing I noticed is that in the API documentation for events, the example in the get-events section doesn't work. It is missing the
|
Thanks letting me know! I've fixed the docs.
Totally forgot that. I will add the missing filter for the event page.
The problem is that it's currently only possible to set filters globally. It's not possible to adjust a filter for a dedicated widget, but that's something I've in mind and should be changed in an upcoming version. It's also the reason why it's not possible to adjust intervals or sorting on the overview and domain pages. It's possible with the API, but I also need to add it to the UI. This also solves the event type dilemma and would allow us to remove them at all (right now they only define what the UI should show).
Can't wait to see what people do with it. Here's a free idea (😃): GitHub can run scripts in a defined interval via GitHub actions. It would be possible to send reports to Ackee (e.g. GitHub stats, Twitter or Instagram followers, website response times (ping)). |
That's a great idea! I will definitely try this when v3 is out. I had the idea to track uncaught JavaScript errors which are thrown. Using |
It's live ✅ I guess there're still things we can improve. Feedback and suggestions are always welcome. Either in new issues or in the community chat: https://gitter.im/electerious-Ackee/community |
API and UI to allow event based tracking (e.g., button clicks). This is something planned for a later release once all the basics are done (#35)
The text was updated successfully, but these errors were encountered: