-
Notifications
You must be signed in to change notification settings - Fork 241
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
Update Venmo with FPTI Analytics Events #846
Merged
Merged
Changes from 7 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
1f37c59
Replace Venmo analytics with FPTI events
sarahkoop e13dc5d
Update unit tests
sarahkoop c722c9d
Add new unit tests
sarahkoop 5bb6ce5
Fix unit tests
sarahkoop 7a9fec8
Convert VenmoAnalytics to class
sarahkoop 2d5cfe0
Remove companion object
sarahkoop ef8b821
Add helper analtyics methods
sarahkoop 8de3d07
Update app switch failure analytics
sarahkoop de18ecd
Remove extra analytics event
sarahkoop File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
14 changes: 7 additions & 7 deletions
14
Venmo/src/main/java/com/braintreepayments/api/VenmoAnalytics.kt
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,14 @@ | ||
package com.braintreepayments.api | ||
|
||
internal enum class VenmoAnalytics(@JvmField val event: String) { | ||
internal object VenmoAnalytics { | ||
|
||
// Conversion Events | ||
TOKENIZE_STARTED("venmo:tokenize:started"), | ||
TOKENIZE_FAILED("venmo:tokenize:failed"), | ||
TOKENIZE_SUCCEEDED("venmo:tokenize:succeeded"), | ||
APP_SWITCH_CANCELED("venmo:tokenize:app-switch:canceled"), | ||
const val TOKENIZE_STARTED = "venmo:tokenize:started" | ||
const val TOKENIZE_FAILED = "venmo:tokenize:failed" | ||
const val TOKENIZE_SUCCEEDED = "venmo:tokenize:succeeded" | ||
const val APP_SWITCH_CANCELED = "venmo:tokenize:app-switch:canceled" | ||
|
||
// Additional Detail Events | ||
APP_SWITCH_SUCCEEDED("venmo:tokenize:app-switch:succeeded"), | ||
APP_SWITCH_FAILED("venmo:tokenize:app-switch:failed") | ||
const val APP_SWITCH_SUCCEEDED = "venmo:tokenize:app-switch:succeeded" | ||
const val APP_SWITCH_FAILED = "venmo:tokenize:app-switch:failed" | ||
} |
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
If the app switch fails, I think we want that to count as a holistic "tokenize_failed", right? For that case on iOS we did this, and send both a "conversion" event (tokenize_failed) + the "extra details" event (app_switch_failed).
This way we can use the "conversion" event of tokenize_failed to capture all failures, to use to measure against the total # of "start" events.
Though we went back and forth a few times on this with iOS, so definitely down to talk through this and come up with a pattern that makes sense across both.
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.
Ok agreed I think that makes sense - updated the app switch failure to send both the conversion analytic event and the app switch failure one. I agree with that approach for all the events 👍