Skip to content

Use Analytics Adapter to populate Analytics Tab #1331

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

Open
mrmarcsmith opened this issue Oct 4, 2019 · 5 comments
Open

Use Analytics Adapter to populate Analytics Tab #1331

mrmarcsmith opened this issue Oct 4, 2019 · 5 comments
Labels
bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature

Comments

@mrmarcsmith
Copy link
Contributor

I have already read #1031 and this conversations on the community forum. This proposed solution is a simple and universal way to make the Analytics Tab usable with parse dashboard while keeping in step with the direction of the Parse Community.

For this example I will use reading the "AppOpened" Analytics event.

  1. Parse-Dashboard calls GET (not POST) on "/parse/events/AppOpened" on Parse Server (requires master key).

  2. Parse Server then calls the new optional functions "getEvent(){}" or "getAppOpened(){}" on the Analytics Adapter passing the params from the request.

  3. The Analytics Adapter then queries its "raw data source" source using the params from the request (Google Analytics or Mixpanel or even a Mongo instance).

  4. The Analytics Adapter translates the "raw source" data into a universal response object used by Parse Dashboard to display pretty graphs.

This is going to require modifications to
A. Parse REST Docs (adding the "GET")
B. Parse Server
C. Any desired Analytics Adapter
D. Parse Dashboard

I'm able to do A, B, and C but I would struggle in the react native for the parse dashboard. is there anyone willing to help me with the modifications required for parse dashboard? From what I saw most of it is already written from the old Parse days and we just need to uncomment it and work to inject data into it.

@TomWFox TomWFox added type:feature New feature or improvement of existing feature help wanted labels Oct 5, 2019
@mrmarcsmith
Copy link
Contributor Author

@douglasmuraoka @davimacedo @alencarlucas are any of you guys interested in teaming up for this? I’ve got the Parse Server side if you can help with dashboard.

@zanderisrael
Copy link

I'm new to this project but I can try and help, is A-C ready for me to work with?

@mrmarcsmith
Copy link
Contributor Author

Hi @zanderisrael nope! There was no point without someone to help with D. Dashboard.

@zanderisrael
Copy link

Ok, so keep me posted, im ready :)

@mtrezza mtrezza added bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) and removed help wanted bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) labels Sep 30, 2021
@mtrezza mtrezza added bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) and removed bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) labels Nov 6, 2021
@pmmlo
Copy link

pmmlo commented Apr 7, 2022

@mrmarcsmith Does anybody have an updated link to the conversation? Or, does anybody have a copy or can recount the thread? Couldn't find anything cached in wayback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

5 participants