-
Notifications
You must be signed in to change notification settings - Fork 181
Description
Spike moving from Google Analytics to Mixpanel.
Mixpanel is being used company wide. We have work to do on GA so is it worth just going straight to Mixpanel now.
See Mixpanel Implementation Plan on Confluence
- Would we want a separate Vortex project or the same project as the site?
- If same project we could do site downloads to vortex install funnels
- Security issues with mixpanel token being cleartext and so open to data pollution
- Could we proxy our analytics through to mixpanel?
- Is it worth the effort in trying to stop it?
- Can we detect it?
Data team says we have 2 projects in Mixpanel - a dev project (we could use that for Beta) and a prod project (for Stable)
Super Properties
❌ = we don't have that data in Vortex
✅ user_id // being sent as distinct_id
✅ user_type
✅ is_mod_author
✅ is_staff
❌ premium_status
❌ plan_type
✅ platform_type = app
✅ app_name = Vortex
UI review
Settings > Vortex
Diagnostics and usage data
Allow tracking
This information is sent to our team entirely anonymously and only with your express consent More about the data we track.
When you first log in
Diagnostics & Usage Data
Find out more about how we use diagnostic and usage data
Click More...
Diagnostics & usage data
Help us provide you with the best modding experience possible!
With your permission, Vortex can automatically collect analytics information and send it to our team to help us improve quality and performance.
This information is sent to our team entirely anonymously and only with your express consent. More about the data we track.
Testing
- Not logged in user
- Free user
- Logged in User
- Mods download
- Collection download
- [] Compare server-side started event with client-side completed event and make sure all ids and uids are exactly the same