google
Update the partial data state infrastructure to use pivot reports for audiences.
Feature Description
The initial implementation of the partial data state infrastructure requests a report per audience in order to determine the date of the first event for each audience.
Once we have added support for pivot reports (see https://github.com/google/site-kit-wp/issues/8484), we can reduce the number of reports by making a single request for a pivot report to retrieve the data for all audiences.
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
- When retrieving the partial data state for a set of audiences, a single pivot report should be requested to retrieve the data for all the audiences, rather than an individual report per audience.
Implementation Brief
For reference see the initial implementation of *determineResourceDataAvailabilityDate() and how it calls getPartialDataReportOptions() for each audience.
- [ ]
Test Coverage
QA Brief
Changelog entry
Moved to Backlog until we get all the P1 issues done and/or the initial release out.
Note: This will need to be reviewed for viability in light of the issues with pivot reports for audiences as described in https://github.com/google/site-kit-wp/issues/8726#issuecomment-2211014589.
After realising pivot reporting was not appropriate for use in the Audience Segmentation work we don't have a clear use case for it in the current codebase and will remove it in #10298. As a result I'm closing this issue as it's no longer relevant.
