-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Stepper Tracking: Simplify calypso_new_user_site_creation
#97130
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~29 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~1462 bytes removed 📉 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~42 bytes added 📈 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
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.
Found unrelated issue. Testing now.
<AsyncLoad | ||
require="@automattic/help-center" | ||
placeholder={ null } | ||
handleClose={ handleClose } | ||
shouldUseHelpCenterExperience={ | ||
! isLoading && experimentAssignment?.variationName === 'treatment' | ||
} | ||
/> |
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.
These seem to have leaked from #97119
client/layout/index.jsx
Outdated
'calypso_helpcenter_new_support_flow' | ||
); | ||
|
||
const shouldUseHelpCenterExperience = user?.ID ? user.ID % 100 < 75 : false; |
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.
+1
client/layout/index.jsx
Outdated
shouldUseHelpCenterExperience={ | ||
! isLoading && experimentAssignment?.variationName === 'treatment' | ||
} | ||
shouldUseHelpCenterExperience={ shouldUseHelpCenterExperience } |
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.
+1
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.
Can confirm it works as advertised! Will do a final test once it's cleaned up and approve.
is_new_user: isNewUser, | ||
is_newish_user: isNewishUser, |
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.
Just double checking that this is intentional.
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, if we go with this new version, is_new_user
will always be true, and we are not using is_newish_user
anymore.
Let's hear what @MicBosi thinks!
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.
Yes indeed! I also expected to remove these two fields which were added recently and I don't think are actually being used by us in data, perhaps they were more useful for debugging - and now we don't need them because the if
condition.
Oh well, I may have done too many things at the same time, let me clean things up! |
@escapemanuele I noticed that in Stepper (not in Start) if I have already created a new user and new site and then try to go again to
|
@escapemanuele Actually, it looks like stepper sets In the Stepper test Calypso knows I'm already logged in and redirects me from In this case I also don't see the expected |
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 tested and can confirm the event is fired for new users with and without closing the tab.
I also confirmed closing the tab (but not the window) and reopening it worked as expected:
I also tested both /start and /setup in the scenario where:
Result:
|
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.
Besides the small issue with is_new_user being null instead of false mentioned here, everything looks good to me. [Edit: there is no issue]
We debugged the apparent issue with @escapemanuele and it turned out to be testing error on my side when logging back in, I should have swapped the .live domain into the URL sent to my email - since I didn't it was picking up the non-fixed Calypso version. |
Fixes #96724
Proposed Changes
Simplify the logic to calculate
calypso_new_user_site_creation
.It will be triggered only if the user has just been created and the site is new.
Why are these changes being made?
Too much complexity in the calculation may lead to problems in retrieving the right data.
Testing Instructions
calypso_new_user_site_creation
is triggered when using a new user, and it is not when using an already existing one.