-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add additional properties to the Block Editor activation events #10300
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
Conversation
…ed analytics events: The property `source` can now have the following values: - via-site-settings - on-block-post-open - on-site-creation
…e the block editor
|
Let's target the 13.0 release branch for this one and the WPiOS one when it gets opened? cc @etoledom and headsup @loremattei . |
I wanted to target 13.0 branch, but it's still not there :) |
WordPress/src/main/java/org/wordpress/android/ui/posts/EditPostActivity.java
Outdated
Show resolved
Hide resolved
…ss-Android into add/analitycs-to-GB-editor-flip * 'develop' of https://github.com/wordpress-mobile/WordPress-Android: Don't revert firebase test-targets change Don't revert EditorPage change Fix a crash on the help screen (issue reported at login phase) where we were accessing the selected site, but there isn't any site in the app yet. Revert "Run connected tests on CI for every PR(round 2)"
…s) info are not still there. We should not track this to false, when the user has instead it on `gutenberg`. The analytics are then bumped later at next startup, or when switching site. cc @hypest
|
Hey Danilo, saw 6c2f05a but I wonder if it will make it hard for us to understand the tracks if we don't set a value there. Like, when that case happens that we don't still have the setting at hand, how will we interpret the tracks we see? WDYT? 🤔 |
Well, right after the login we don't have the info to bump the property IS_GUTENBERG_ENABLED correctly, since sites info are still not there. I think its's better to not add a wrong value ( It should not be a big difference, backend query side, since we can read the most recent event from the Track and check if the user has GB on or off. On a side note, there is no user related GB setting anymore, wondering if we need to keep this property at user level...can't we move it to the general properties added when tracking events with site details |
|
I'm bumping this to If you'd like it to be released as part of |
| // If saved site exist, then add info | ||
| if (selectedSite != null) { | ||
| // If saved site exist, then add editor info | ||
| if (selectedSite != null && !TextUtils.isEmpty(selectedSite.getMobileEditor())) { |
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.
Apparently (see here that the flag is set in the user section) we'll write false by default even if we skip setting the flag here. Perhaps leaving empty is a better approach so, wdyt about introducing an additional flag in AnalyticsMetadata to denote if we have set the flag at AnalyticsMetadata.mIsGutenbergEnabled at all or not?
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.
Addressed in b59bd91
…rties, when there is at least one site with the Block Editor enabled on it. cc @etoledom
|
|
||
| if (!newSitePopupNeeded) { | ||
| // Don't track the activation of the block editor on new sites. | ||
| // The flip to GB happened at site creation time, and the flip is tracked there with proper details |
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.
Hmm, should the SiteUtils.enableBlockEditor(mDispatcher, mSite); (line number 1557 above) be inside this conditional too then? 🤔
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.
Well, I think it's better to keep it out, since the user can change the option back to Aztec from settings right after the site creation. Even before creating/opening a new post. It's an edge case I know, but better to show both the dialog and repeat the network call to the server. It's just a call, that doesn't change anything on new sites 99% of the cases.
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.
As per chat convo - cleaned up the code and made more easy to follow in 4db8228
Verified that all test cases worked fine for me 👍 |
hypest
left a comment
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.
LGTM!
Add additional properties to
gutenberg_enabled, andgutenberg_disabledanalytics events:The property
sourcecan now have the following values:Test 1:
Test 2:
Test 3:
cc @etoledom Since we need the iOS counterpart of this PR
Update release notes:
RELEASE-NOTES.txt.