Skip to content
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

[FEATURE] Provide ability to "export" to various backend services #103

Open
Mjboothaus opened this issue Jul 2, 2024 · 1 comment
Open
Assignees
Labels
enhancement New feature or request

Comments

@Mjboothaus
Copy link

Is your feature request related to a problem? Please describe.
I would like to be able to export analytics data to other backends e.g. MotherDuck

Describe the solution you'd like
Make it easy for the use with documented API to access analytics data to be able to push to other backends and/or support other backends.

Describe alternatives you've considered
Firestore backend already exists.

Additional context
I use DuckDB for ETL of data and for analytics (which it is designed for) - MotherDuck provides a SaaS version of DuckDB which is persistent and easily shareable.

p.s. Nice work on project - I'd also like multipage app tracking support e.g. with latest st.Page() features.

@Mjboothaus Mjboothaus added the enhancement New feature or request label Jul 2, 2024
@444B
Copy link
Owner

444B commented Jul 2, 2024

Hi @Mjboothaus
Thank you for this FR! I appreciate so much to know what the community wants developed
I also would love to get the multi page tracking working - I think that has been one of the biggest requested features overall and has been raised in #47
I am struggling to put the time into refactoring the code and creating the other changes desired as part of our #53 release

I would love to have a config screen where you select your collection method and have it options such as Local json / firebase/ Motherduck/ SQL instance, etc
Thats the dream

I will keep this FR in mind when we get around to developing alternatives
For now, I will happily review and accept any PRs but I also acknowledge that what is needed to encourage more PRs would be to make the code more approachable with a refactor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants