Magento's sales tables are ready for charting almost as they are. The question is whether the database doing the charting should be the one taking orders.
There is no Magento connector in Looker Studio, so the realistic routes are its MySQL connector aimed at your store, or a copy. The sales side rewards you quickly: sales_order has real columns, so revenue by month is one short custom query and a chart.
The catalogue punishes you just as quickly. Because product attributes live in EAV, a "top products by revenue" chart that shows names rather than SKU ids needs joins through catalog_product_entity_varchar and eav_attribute. Written once as a custom query that's fine; written six times across six charts, it becomes six places for the definition to drift.
And a dashboard is not one query. Each chart issues its own, they fire when the report opens and when the cache expires, and they fire for everyone you shared the link with. Magento installs are large — 300 to 400 tables is normal — and the store database is already doing indexing work of its own. Reporting traffic on top of that is a capacity decision, not a detail.
All three end with a Magento dashboard in Looker Studio. They differ in what your report is allowed to do to your store.
Looker Studio connects straight to Magento's database with custom queries you write.
Magento's own hosted reporting, enabled from the admin, with prebuilt dashboards.
BeQuery clones Magento into an isolated PostgreSQL copy that Looker Studio's built-in PostgreSQL connector reads directly.
Read-only MySQL credentials, host and port. BeQuery clones the database into an isolated PostgreSQL copy, verified against the source on every sync.
In Settings → External connections, generate a PostgreSQL user scoped to your team's schema. It is SELECT-only: it cannot write, alter or drop anything, and it can't see another workspace. External connections are available on the Cloud and Enterprise plans.
Add data → PostgreSQL → paste the host, database, user and password. No community connector, no OAuth dance, nothing to install: PostgreSQL is one of Looker Studio's built-in connectors.
Choose the custom query option and paste SQL that already aggregates. Your report then reads a few hundred rows instead of scanning your largest table on every interaction — which keeps dashboards fast and stays inside the 30-second statement timeout on external credentials.
Both are legitimate. With Magento the deciding factor is usually the cost of the queries, not just who opens the report.
Join catalog_product_entity to catalog_product_entity_varchar on entity_id, restricted to the attribute_id that eav_attribute gives for 'name' on the product entity type. Do it once in the custom query behind the data source rather than per chart — that way the definition lives in one place and every chart inherits it.
Yes. It was validated end-to-end on a real Magento 2 store — 387 tables cloned and verified, with the insights checked against the source rather than assumed.
It can — MySQL is a built-in connector, and for a small shop that's a legitimate choice. What you're accepting is that your production database has to be reachable from Google's IP ranges, and that every viewer opening the report, and every scheduled refresh, runs queries against the server your customers are checking out on. It works fine until the report gets popular or someone builds a dashboard with twelve charts on it.
No, and this is the real difference from the BigQuery route. Looker Studio speaks PostgreSQL natively, and BeQuery's clone is a real PostgreSQL database — so the report reads the copy directly. There's no load step to schedule and nothing to keep in sync beyond the sync you already have.
External PostgreSQL credentials — the thing Looker Studio connects with — are available on the Cloud (pay-as-you-go) and Enterprise plans. The clone itself, the SQL editor and the in-app dashboards work on every plan, including the free tier.
As fresh as your last sync, plus whatever caching you leave on in Looker Studio. Sync runs nightly on lower plans and down to roughly every minute on higher ones. For a report someone opens each morning, nightly is usually what people settle on anyway.
Free tier, no credit card, read-only access. Production is never written to — and you can explore the demo store before connecting anything.