Shopify to Data Studio: connect store reporting
Connect Shopify reporting to Data Studio, formerly Looker Studio. Compare the source, permissions and metric definitions before trusting a store report.
- Published
- Last updated
To connect Shopify to Data Studio, use a documented third-party connector for recurring order reports, or a controlled export for a report you can reconcile. Use Google Analytics 4 for shopping behaviour and traffic. Its events measure a different record from Shopify’s orders.
Choose the Shopify reporting data path
Choose an order-data connection when you need Shopify sales records in your report. A Google Analytics connection answers questions about measured visits and shopping events.
Google’s reporting product is now called Data Studio again. It previously used the name Looker Studio, which still appears in connector documentation. Google’s naming guidance confirms the name change and redirects from the former service address. The Shopify-to-Looker Studio connection described by a provider still needs a supported source and permissions.
Compare the available paths
| Path | Available records | Refresh behaviour | Access and cost |
|---|---|---|---|
| Third-party Shopify connector | Provider-defined order and product fields, with documented refund fields where supported | Provider retrieval plus report caching | Shopify authorisation and a separate provider subscription |
| Controlled export to Google Sheets | Selected order export fields, prepared at a declared row level | Staff replace the source, then the report queries the sheet | Shopify export permission and access to the sheet. Staff preparation costs remain |
| Google Analytics connector | GA4 event, session and traffic metrics | Analytics processing plus connector freshness | Access to the correct GA4 property. Separate from a paid Shopify order connector |
Google’s connector catalogue includes Google Sheets and Google Analytics. A Shopify connector supplied by another company is a third-party dependency.
Supermetrics documents a Shopify connector with Looker Studio as a destination. Its field list includes order identifiers and refund processing dates. The subscription depends on the selected package and connection capacity. Confirm the Shopify source and reporting destination are included in that package before approving the charge.
Supermetrics’ connection guide requires an authorised Shopify account. It describes staff permissions for app installation and charges, plus access to store records. That access is broader than the permission to view a dashboard. Assign the connection to a person authorised to grant it.
Data Studio itself is a no-cost reporting tool. A third-party connector subscription is a separate cost, and a manual export still takes staff time.
Use the controlled export when you need a small, inspectable starting point. Choose a connector once its field coverage and refresh behaviour meet the report’s needs. Keep an export available as the comparison record in either case.
Connect a controlled export
This route needs permission to export Shopify orders and a Google account with access to the prepared sheet.
- In Shopify’s Orders page, filter the orders and choose Export. Select the required scope and CSV format. Keep the original file privately with its export time and filters.
- Prepare separate order and line-item tables. Shopify’s export documentation explains that additional items can occupy separate rows. Keep each order total once in the order table.
- Put the order table in a restricted Google Sheets worksheet. Use one header row and consistent types within each column. Exclude customer contact details that the report doesn’t need.
- In Data Studio, choose Create, then Data Source and the Google Sheets connector. Select the spreadsheet and worksheet, then connect. Google documents this Sheets connection procedure.
- Inspect the resulting fields. Keep identifiers as text, amounts as numbers and the selected reporting date as a date. Create a report from that source and add an order-detail table before building summary charts.
The first checkpoint is simple: the report’s distinct order count and amount must match the prepared worksheet under the same filters. A connector-based report must pass the same comparison.
Define the records and metrics
Define each metric’s source and row level before using its total. A row level states what one row describes, such as one order, one line item or one refund.
Keep the Shopify store identity beside the order ID, plus the displayed order number for investigation. Retain the product and variant identifiers available from your source. Use a stock keeping unit (SKU) where available to trace a purchased item. Product names alone can change or repeat.
For the order record, retain creation and payment timestamps. Keep refund processing timestamps in a refund record with its own identifier. Record the source time zone and the time zone used to group report days.
Currency needs its own field. Separate shop-currency amounts from the customer’s payment currency. Define whether the measure includes tax and shipping, and how it treats discounts. Don’t add different currencies into one unlabeled sales total.
Keep payment status separate from fulfilment status. Write an explicit inclusion rule for cancelled, test and unpaid orders. A paid-order total can differ from a sales report that uses different inclusion rules.
Separate Shopify orders from GA4 events
Shopify orders describe transactions recorded by the store. Google Analytics 4 (GA4) describes measured activity, including purchase events. A purchase event can carry an order reference, but that doesn’t make Analytics the order ledger.
Shopify’s GA4 setup guide uses the Google & YouTube channel to set up tags. Confirm that it sends data to the intended GA4 property. Check that another tag installation isn’t sending the same purchase again.
Google’s Shopify consent guidance explains how the store’s consent setup works with Google tags. Validate the applicable consent states and purchase event behaviour before using Analytics to judge the shopping journey. Consent choices and blocked measurement can change which visits and events appear.
Connect the property through Google’s Analytics connector. The person making the connection needs access to that property. Confirm the property identity in the report before comparing its events with store orders.
For a conversion rate, name the numerator and denominator. A GA4 session purchase rate uses GA4 sessions and its qualifying purchase measure. Dividing all Shopify orders by measured GA4 sessions creates a mixed-source ratio with a different meaning.
Reconcile the report with the store
Reconcile individual orders before trusting a sales chart. A report can produce a plausible total while a duplicated join or wrong date excludes the records you need.
Consider this fictional store in Perth. All amounts below use the same currency and exclude tax and shipping. Each item’s amount is after discounts.
Work the orders and refund
| Record | Event time | Amount | Expected treatment |
|---|---|---|---|
| Order A | First reporting day, 11:50 pm Perth time | $120 | Two line items worth $70 and $50. Count one order |
| Order B | Second reporting day, 9 am Perth time | $80 | One line item. Count one order |
| Refund on Order A | Third reporting day | $30 | Keep a separate refund record linked to Order A |
An order-created view of the first two days contains two orders worth $200 before the later refund. A transaction-period view across all three days subtracts the $30 refund and shows $170 under this example’s definition.
A report that deducts each order’s lifetime refunds from its original creation day shows $90 for Order A after the refund arrives. That can change an earlier period’s total. A report that groups refunds by processing date puts the negative $30 in the third day instead.
Shopify explains sales-report discrepancies caused by timing and reporting logic. Match the named Shopify report’s definition before expecting its number to equal an order export or connector metric.
Now change the report date field from order creation to refund processing. It becomes a report of refunds in that period. Orders without refunds won’t belong in the same result. Label the date control so readers know what it filters.
Time zones can move rows too. Order A’s 11:50 pm Perth timestamp is 3:50 pm UTC on the same day. An order arriving instead at 12:10 am Perth time falls at 4:10 pm UTC on the preceding day. Group both by the agreed store day before comparing daily totals.
Diagnose the first mismatch
| Symptom | Check | Corrective action |
|---|---|---|
| Sales total rises after adding product detail | Count rows per order before and after the join | Aggregate line items before joining order totals, or keep order and item charts separate |
| An order disappears near midnight | Compare source timestamp with the report’s grouping zone | Convert timestamps before assigning the reporting day |
| The store shows a refund that the report omits | Inspect refund fields, processing time and last source retrieval | Retrieve the affected period and apply the declared refund-date rule |
| A report stays unchanged after replacing an export | Compare worksheet contents with the connected range and cached result | Correct the range, then refresh the report after confirming the source changed |
| Order counts differ across charts | Inspect status filters, test-order handling and distinct IDs | Apply the same documented inclusion rule to each chart |
A join can multiply money without creating a new order. If Order A’s $120 total repeats beside each of its two items, summing that column produces $240. With Order B, the mistaken total becomes $320 instead of $200.
For missing rows, compare a list of order IDs from the source with the report’s detail table. Check connector history limits and pagination where relevant. Keep a record of the exact filters so the next refresh can repeat the comparison.
Once the totals reconcile, interpret them alongside the products customers viewed and the questions they asked. A sales change can suggest where to investigate. It doesn’t establish why customers left or bought.
Keep access and refresh accountable
Assign an owner to the source connection and a separate owner to the report’s metric definitions. Both must know how to reproduce a mismatch from the same underlying records.
The store administrator owns Shopify permissions and any app approval. The connector administrator owns its authentication and subscription renewal. The analyst owns transformations, date fields and joins. A named reporting owner checks failed refreshes and keeps the investigation export available.
Data Studio’s credential settings distinguish owner credentials from viewer credentials. Owner credentials can let a report viewer see data without direct access to the underlying source. Review report sharing alongside that choice, particularly when order or customer records are involved.
Record the most recent successful source retrieval separately from the report’s refresh. Google’s freshness documentation explains that reports can serve cached query results. Refreshing a dashboard doesn’t update a CSV that nobody has replaced, or recover a connector whose authorisation failed.
Keep the connector’s billing owner and renewal terms in the operating record. For an export workflow, assign the replacement schedule and backup person. Remove access when a staff member leaves and verify the replacement connection before relying on its next report.
Before sharing the dashboard, compare the fictional example’s equivalent records from your store across the source and the report. Publish the metric definition beside the chart, then keep a detail table that lets an authorised colleague trace its total back to orders.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.