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
How do you use MixPanel with different flavors and build types? #9
Comments
Could you please elaborate? |
There is different App stores on Android such as the Play Store vs Amazon App Store. The App is essentially the same but there could be data that only makes sense for one app vs the other if one app store supports features. Can one use the same key/setup but separate out data when needed by package name? |
You could definitely have a project token as a build param which will be different for different flavors and resolve that token at runtime. |
Yeah for sure, I'm aware of that setup my question is whether its best practice to separate by token or if one can collect the data from all apps with the same tokens and just filter out within the Mixpanel dashboard. |
Ah, got it. That's a great question. At Mixpanel we used to encourage having different projects projects for different apps. We now have a product in beta called Workspaces where you can create filter views within a project. In your case, you could create two workspaces: one per flavor and do the analysis using the same project token. |
No description provided.
The text was updated successfully, but these errors were encountered: