-
Notifications
You must be signed in to change notification settings - Fork 0
Add opt-out option and profile tracking #3
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like maybe the distinct_id stuff could be abstracted into somewhere shared?
But I'm not fully versed in the structure of this project
_getToken: => getToken! | ||
|
||
_getTimestamp: => getTimestamp! | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really following why you did this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The other classes inherit this, but these values are defined locally in this file
47f4000
to
61278d1
Compare
33514fc
to
5c996a2
Compare
Turns out Mixpanel doesn't create profiles for users, even if you're passing them a distinct ID.
We'll have to manually create a new profile for each player if we want to be able to treat
disctint_ids
as references in our data.