-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Data sharing options #225
Comments
Thanks for the suggestion! It might be possible to extend the permanent tokens with some settings to only share data for a selected domain. We then could allow the creation of sharing URLs which include a permanent token. That would be the simplest solution I guess. It's currently not planned, but I will keep the issue open to see if there's a higher demand for such a feature! |
Surprised this isn't in the product, as data sharing is a common use-case for analytics. My use-case would be running my own Ackee server for my clients (as a freelance agent), and they'd of course want to see reports / access data for their own analytics for the domains which they own. This is possible in both Google Analytics and Matomo/Piwik, but of course I understand Ackee tries to be different from them both in many ways, but data sharing seems like something that really needs to be built into the product. |
🐣 Is your feature request related to a problem? Please describe.
Sharing stats data to other user/client which have their site in my Ackee setup can be done with credentials only.
Of course we can extend Ackee using permanent token, but eh. Finishing project with bunch of revisions from client just made me so damn 'happy' :). And I don't want to touch the code anymore. especially their admin dashboard
💡 Describe the solution you'd like
Which can be SUPER helpful if Ackee provide something like unique url for every target domain and then have some option to access the page without main admin credential. Something like simple access code/pin stored in db, or even just the unique url with option to make it publicly available.
Of course Ackee need to be as lightweight as possible. This solution no need to add multiple user support for ackee, The only additional record in my mind is like a key named public or private with boolean value. Access code, and some frontend route logic. No additional endpoint, no data separation. Just add additional way for data serving. I didn't think this solution will made Ackee more heavy.
❓ Describe alternatives you've considered
📋 Additional context
The text was updated successfully, but these errors were encountered: