-
Notifications
You must be signed in to change notification settings - Fork 135
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
Tracks for JITM displayed #7657
Tracks for JITM displayed #7657
Conversation
…tm-displayed-track
…dismiss-tapped-track
…tm-displayed-track
…ta-tapped-track # Conflicts: # WooCommerce/src/main/kotlin/com/woocommerce/android/ui/mystore/MyStoreViewModel.kt
…dismiss-tapped-track # Conflicts: # WooCommerce/src/main/kotlin/com/woocommerce/android/ui/mystore/MyStoreViewModel.kt
…itm-dismiss-success-track # Conflicts: # WooCommerce/src/main/kotlin/com/woocommerce/android/ui/mystore/MyStoreViewModel.kt # WooCommerce/src/test/kotlin/com/woocommerce/android/ui/mystore/MyStoreViewModelTest.kt
You can test the changes on this Pull Request by downloading an installable build, or scanning this QR code: |
…tm-displayed-track # Conflicts: # WooCommerce/src/main/kotlin/com/woocommerce/android/ui/mystore/MyStoreViewModel.kt
…dismiss-tapped-track
…itm-dismiss-success-track
Generated by 🚫 dangerJS |
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.
Thanks @AnirudhBhat! LGTM, I've left one minor comment.
@@ -237,6 +237,10 @@ class AnalyticsTracker private constructor(private val context: Context) { | |||
const val KEY_HAS_MULTIPLE_SHIPPING_LINES = "has_multiple_shipping_lines" | |||
const val KEY_HAS_MULTIPLE_FEE_LINES = "has_multiple_fee_lines" | |||
|
|||
const val JITM_ID = "jitm_id" | |||
const val JITMS = "jitms" |
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.
❓ This doesn't seem to be used. Is it necessary?
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.
Even though the Instrumented Tests fail because of the missing WireMock request matcher, I believe this will be solved after the current branch eventually ends in issue/7559-jitm-api
branch, to which I took the liberty of adding (20bb09e) the missing WireMock file.
As per the jitm_displayed
event, I confirm that it's indeed tracked:
…tm-displayed-track # Conflicts: # WooCommerce/src/main/kotlin/com/woocommerce/android/ui/mystore/MyStoreViewModel.kt
…ta-tapped-track # Conflicts: # WooCommerce/src/main/kotlin/com/woocommerce/android/ui/mystore/MyStoreViewModel.kt
…dismiss-tapped-track
…itm-dismiss-success-track
…cess-track Tracks for JITM dismiss success
…ped-track Tracks for JITM dismiss tapped
…track Tracks for JITM CTA tapped
Closes: #7625
Description
This PR has analytics to track when the JITM is displayed on the screen. Please note that this tracks only JITM display and not the JITM fetch success. There might be a chance that the JITM API succeeds but the JITM list will be empty and hence, not displayed.
*_jitm_displayed
Properties:
source :
my_store
jitm_id : {jitm_id}
jitm_group : {FEATURE_CLASS}
More info: pdfdoF-1zc-p2
Testing instructions
Pre-requisite
As mentioned in this post (pdfdoF-1vt-p2) make sure you have installed any one of the mentioned barcode plugin installed on your store. For example - you can install A4 Barcode Generator
Your store must be set up in the US. JITM is not supported in any other country.
RELEASE-NOTES.txt
if necessary.