WooCommerce 10.7 added country, state, and guest-vs-registered filters to the wc-analytics/customers API on April 14, 2026 — exactly two weeks after MODPA enforcement made state-level customer counts a compliance question. The filters work via direct REST queries today. Looker Studio, Power BI, and Tableau dashboards won’t see them until each connector’s maintainer ships an update. That gap is where compliance windows close before the data is visible.
The Changelog Entry Most Stores Missed
The WooCommerce 10.7 release notes list PR #62267 in the Enhancements section as a one-liner: country, state, and customer-type filtering on the wc-analytics/customers API route. Read past quickly, and it sounds like a developer convenience.
It isn’t. The dimensions WooCommerce just added are exactly the dimensions state-level US privacy laws use to count consumers. MODPA — the Maryland Online Data Privacy Act — sets a 35,000-consumer threshold calculated by state of residence. CCPA, CPA, CTDPA, VCDPA, and the rest of the 2025–2026 state-privacy wave all rely on state-resident counts to determine which businesses are in scope.
WooCommerce shipping a state filter on the customers API two weeks after MODPA enforcement is timing, not coincidence. The platform put the dimension where it needed to be for stores trying to answer the new compliance question.
The dimension WooCommerce shipped is the dimension the regulator counts on.
The Connector Lag Problem
The technical mechanism behind the lag is straightforward. Looker Studio, Power BI, and Tableau don’t talk to WooCommerce directly. They use connectors — third-party data sources that wrap the WooCommerce API and expose its fields as report-ready dimensions and metrics.
When WooCommerce adds a new filter to its API, the connector doesn’t know about it until someone updates the connector’s schema definition. That update is a separate release on a different schedule, maintained by a different team, sometimes shipped quarterly, sometimes annually, sometimes only when a customer files a support ticket.
For a store running Looker Studio dashboards, the practical effect is this: the filter exists in the data, the data is reachable through the API, but the dashboard cannot show it. The privacy and reporting team is blind on the dimensions that just became compliance-relevant.
And the cost compounds at the agency level. Looker Studio Pro charges $9 per user per project, and every WooCommerce client an agency manages is a separate project. Connector lag at scale is connector lag multiplied by client count multiplied by user seat.
The Direct REST Query Workaround
While connectors catch up, the new filters are accessible immediately through direct REST queries. The endpoint is /wp-json/wc-analytics/customers and the new parameters work as you’d expect:
country=US— filter to a single country.state=MD— filter to a single state, applied within the country filter.customer_type=guestorcustomer_type=registered— split the user-type dimension.
A working query for the MODPA threshold check looks like /wp-json/wc-analytics/customers?country=US&state=MD&per_page=100 and returns the Maryland-resident customer list as JSON. Authentication is the standard WooCommerce REST API mechanism — either a logged-in admin session for browser use or an API key pair for automated pulls.
For stores running a small custom dashboard or a scheduled compliance report, the direct API path is faster than waiting for a connector update. The query can be wrapped in a daily cron, output to a CSV, and ingested by whatever reporting tool the store uses next.
You may be interested in: Your WooCommerce BigQuery Integration Is Missing 90% of Your Data
The HPOS Performance Improvement Hidden in the Same Release
The 10.7 release also halved the SQL query count for order pulls. The /wc/v4/orders endpoint went from 271 SQL queries to 132 — a 51% reduction — through cache priming. For stores running HPOS at scale, that’s the kind of improvement that doesn’t show up in feature roundups but changes whether the analytics endpoint times out under reporting load.
The two changes together — new filters plus faster execution — make the wc-analytics/customers endpoint genuinely usable for compliance-grade queries on stores with hundreds of thousands of orders. Pre-10.7, the same query path would have been slow enough to discourage daily use. Post-10.7, it’s a routine call.
Why First-Party Pipelines Don’t Have the Connector Problem
The architectural lesson sits one layer up. The connector lag exists because there’s a translation layer between the source data and the reporting tool. Each layer that translates the data is a layer that has to be updated whenever the source changes.
Stores that pipe raw WooCommerce events directly to BigQuery don’t have a translation layer in the middle. The events land in the warehouse with their full field set intact. When WooCommerce adds a new field — country, state, customer type, or anything else — the field appears in the next event written, and any SQL query the store runs against the warehouse can use it immediately.
That isn’t a connector update problem because there’s no connector. The data flows from WooCommerce hooks straight to BigQuery, and the dashboard tool reads from BigQuery — not from WooCommerce.
You may be interested in: The Eight Hops a WooCommerce Conversion Has to Survive
Here’s How You Actually Build This on WordPress
Transmute Engine™ is a first-party Node.js server that runs on your subdomain. The inPIPE WordPress plugin captures WooCommerce events and sends them via API to Transmute Engine, which writes raw events directly to your own BigQuery dataset. New WooCommerce field? It lands in the next event. New compliance dimension? It’s already queryable. The connector lag problem stops being a problem because the connector stops being in the path.
Key Takeaways
- WooCommerce 10.7 (April 14, 2026) added country, state, and guest-vs-registered filters to the wc-analytics/customers API.
- The timing aligns with MODPA enforcement — state-level customer counts are now a compliance question for many stores.
- Looker Studio, Power BI, and Tableau connectors won’t expose the new filters until their maintainers ship updated schema definitions.
- The direct REST query at /wp-json/wc-analytics/customers works today — useful for custom compliance pulls while connectors catch up.
- First-party pipelines that write to BigQuery have no connector lag — every WooCommerce field is queryable the moment it ships.
Frequently Asked Questions
Looker Studio uses connectors to talk to WooCommerce, and connectors expose only the fields their maintainer has explicitly defined. WooCommerce 10.7 added country, state, and guest filters to the underlying wc-analytics/customers API on April 14, but the Looker Studio data source definition has to be updated by whichever connector you use before those filters appear in the UI. Until then, the filters work via direct REST queries but not through the connector layer.
After upgrading to WooCommerce 10.7, the endpoint accepts country and state parameters. A direct REST query looks like /wp-json/wc-analytics/customers?country=US&state=MD. You’ll need an authenticated request — either a logged-in admin session or a WooCommerce REST API key — and the store must be on 10.7 or later. The result returns the customer list filtered by that state.
After 10.7, partially. The wc-analytics/customers API now supports country, state, and registered-vs-guest filters, which covers the dimensions MODPA, CCPA, and similar state-level laws use to calculate consumer thresholds. The compliance reporting still has to be built on top of those filters — WooCommerce exposes the data, but doesn’t generate the threshold reports itself.
The Customers report is the WooCommerce admin UI screen. The wc-analytics/customers API is the underlying REST endpoint that the report queries. Direct API access lets you apply filters and pull data programmatically — useful for BI tools, custom reports, or compliance threshold calculations. The 10.7 filters live at the API layer; the admin UI exposes some of them but not all.
No. If your store pipes raw WooCommerce events directly to BigQuery via a server-side pipeline, every dimension is queryable the moment it exists in the source data — country, state, customer type, and any custom attribute you’ve configured. The connector lag problem is specific to BI tools that depend on a packaged WooCommerce connector translating the API for them. Direct event pipelines bypass the translation layer entirely.
Test the new filters today by hitting /wp-json/wc-analytics/customers?country=US&state=MD on your own store. Seresa builds the architecture that doesn’t make you wait for a connector update to see what WooCommerce just shipped.
