Premium Analytics: add Stats email summary endpoint - #49900
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
kangzj
force-pushed
the
endpoint/stats-email-summary-endpoint
branch
from
June 24, 2026 08:28
a33aba5 to
3b53fd8
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Contributor
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 Follow this PR Review Process:
If you have questions about anything, reach out in #jetpack-developers for guidance! |
Contributor
Author
Review-cycle audit summaryNo blocking reviewer feedback is open. Latest invited reviewer feedback is non-blocking, required checks report none for this branch, and the PR is ready with Audit details
|
kangzj
force-pushed
the
endpoint/stats-email-summary-endpoint
branch
3 times, most recently
from
June 25, 2026 00:55
ac2e220 to
f02060b
Compare
kangzj
marked this pull request as draft
June 25, 2026 09:01
kangzj
force-pushed
the
endpoint/stats-email-summary-endpoint
branch
from
June 29, 2026 07:22
c0ae17b to
4cdd612
Compare
Add data-package support for the WPCOM Stats email summary endpoint (stats/emails/summary), following the established Stats endpoint patterns: endpoint query, useStatsEmailSummary hook, public exports, and sanitizer registration. The query is modelled against the real endpoint contract rather than the stale published docblock: - It is an all-time report with no period parameter; only quantity, sort_field and sort_order are caller-controlled. sort_field is typed as the closed union the endpoint accepts (opens, clicks, post_id, post_date) and defaults to post_date to mirror the Calypso Emails screen. - The raw fixture matches Email_Summary::build_response — all metrics as JSON numbers and the full post_date timestamp. Covered by query-key and normalizer tests.
kangzj
force-pushed
the
endpoint/stats-email-summary-endpoint
branch
from
June 29, 2026 07:26
4cdd612 to
1a4512b
Compare
kangzj
marked this pull request as ready for review
June 29, 2026 07:31
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #
Proposed changes
Related product discussion/links
Does this pull request change what data or activity we track or use?
No. This only adds typed client data/query integration for an existing Stats API endpoint.
Testing instructions