-
Notifications
You must be signed in to change notification settings - Fork 218
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
Analytics Event: LOAD_MORE_RESULTS
#2449
Conversation
Size Change: +242 B (0%) Total Size: 843 kB
ℹ️ View Unchanged
|
I just remembered @obulat added some Playwright analytics testing previously: I'll try updating that implementation to use this new code, which would be a good way to validate its usefulness! |
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.
Co-authored-by: Olga Bulat <obulat@gmail.com>
Can you clarify how this would work? Plausible only allows querying by a single custom prop at a time (see the note here). We could work around that by combining the media type and query into a single prop. The media type is critical information for all queries anyway. |
I've added the |
@zackkrida According to @obulat's comment, I suppose this needs to be rebased now that #2454 is merged before it can be reviewed? |
Based on the medium urgency of this PR, the following reviewers are being gently reminded to review this PR: @AetherUnbound Excluding weekend1 days, this PR was ready for review 6 day(s) ago. PRs labelled with medium urgency are expected to be reviewed within 4 weekday(s)2. @zackkrida, if this PR is not ready for a review, please draft it to prevent reviewers from getting further unnecessary pings. Footnotes
|
Drafting to implement the |
LOAD_MORE_RESULTS
analytics event + Playwright helpers for analytics eventsLOAD_MORE_RESULTS
@AetherUnbound and @obulat I've added the currentPage logic and this PR is ready for review. |
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 worked as expected! One comment about tests but otherwise this is good to go :)
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. Tested just fine locally 👍
Fixes
Fixes #1074 by @dhruvkb
Fixes #1992 by @sarayourfriend
Description
This PR adds a
LOAD_MORE_RESULTS
analytics event to the load more button.Crucially, I did not include the original page number property in the event payload, as it requires major additions to the media and search stores.Thanks, @obulat.Testing Instructions
CI should pass, and then review the code. Let me know what you think of this API surface! Should we even be testing analytics events in e2e tests? I suspect it could be a nice additional assurance. If so we might want to add it in other places, like for pageviews and other custom events. That gets into larger issues about our frontend test consistency and coverage though.
Checklist
Update index.md
).main
) or a parent feature branch.Developer Certificate of Origin
Developer Certificate of Origin