Error: Request parameter is empty: accountID.
See original GitHub issueBug Description
One user in the support forums is encountering various errors when connecting the various Site Kit modules, with one such error below when connecting either the AdSense or Tag Manager modules:
Error: Request parameter is empty: accountID.
In addition to the on the primary Site Kit dashboard the below appear in particular widgets:
Data error in Analytics
Request parameter is empty: metrics.
Data error in Analytics
Sort key ga:pageviews is not a dimension or metric in this query.
Error: Request parameter is empty: strategy.
This is occurring on a primary domain only, with no such issues on a subdomain site on the same hosting platform. In the users Site Health information on an impacted site the below warning appears, however their publicly accessible REST endpoints are accessible (example)
The REST API did not correctly process the query context parameter.
Screenshots
Additional Context
- Site Kit 1.35.0
- SH info provided
- Error log provided
- Messaging output seems similar to #2782
Insights & Troubleshooting Checks performed
- Health Check & Troubleshooting plugin check
- Front end check (mixed content, minified content, combined JS)
- Incognito mode
- Checked users Site Health info, no identified causes
- Additional .htaccess rules applied
- Uninstalled and reinstalled plugin
- User confirmed no “Critical errors” in their Site Health status
- Temporary disabled WAF rules at host level - including ModSecurity
- Checked site setup and dashboard from another WordPress site on the same hosting platform
- Reset Site Kit (on the SK service)
- Checked does the same occur from another admin users account
- Reviewed error logs - Some gocache-cdn errors and Analytics 404 responses
- Reviewed XHR requests
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
Implementation Brief
Test Coverage
Visual Regression Changes
QA Brief
Changelog entry
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
@abdullah1908 The user wasn’t able to fix via troubleshooting steps and has moved on from the plugin for now. Should this escalate to L2?
@eugene-manuilov Makes sense to me! Closing.