Add Amplitude integration to front-end. #1439
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This attempts to add amplitude integration to the front-end, so we have a bit more visibility into what our users are doing.
As per Amplitude's Data Taxonomy Playbook, I've attempted to use event names that are concise without being too broad:
Right now this is entirely uncommented and untested because I just want to see if it's even useful before doing more.
Various user properties are also reported, such as what state/city the user claims to be from. No sensitive user data or PII is submitted to Amplitude.
Note that this PR is different from #940, which adds Amplitude integration to the back-end by exporting the data in our user database to Amplitude.