-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Concept - Aggregation plugins #4613
Comments
The issue here is that all those "data aggregation" use cases are very specific and each require a slightly different way of aggregating data.
Here I'd make a plugin that takes the user's properties, checks
This requires the session tracker plugin and then a custom plugin that emits whatever is needed when getting the "Session end" event.
We can tally them as they come in, or make an API call to get the count. The latter is probably more accurate and fast enough in this case. .... This is all to say: I'm not sure what common abstraction we can build to help users, other than the one that we have already built (called plugins :D). Since nobody really asked for anything explicitly tangible here, I propose we punt :). |
This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the |
This issue was closed due to lack of activity. Feel free to reopen if it's still relevant. |
Is your feature request related to a problem?
Plugins are pretty powerful to manipulate data coming in, yet I may want to extend this functionality to get more robust analytics that I can share on other places (see examples below). The key thing to consider here is that I may want to run analysis on a larger scope than a single event.
Describe the solution you'd like
For instance, I may want to have in my CRM information around how many days has the user been active in the last week. Or information on my customer support platform around the last session duration. Or the number of
$exception
events in the last 3 days.Another interesting thing to consider is whether it might be useful to have that information both available as user properties, dynamically-calculated properties for internal analytics.
Describe alternatives you've considered
I could build my own service that processes by continuously hitting PostHog's API or DB and then updating the downstream app.
Additional context
Suggested by a Big 5 (not a request, just a suggestion to consider).
Related to #3357
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered: