How to Build a Data Studio Ecommerce Dashboard with GA4 (2026)

How to Use This Guide

This guide does not simply move numbers from GA4 into a dashboard. It starts with ecommerce business questions and builds a report structure for day-to-day monitoring, advertising reviews, and management reporting. Complete the first version in chapter order, then gradually add modules such as profit, inventory, new versus returning customers, and repeat purchases as needed.

Google reintroduced the Data Studio name in April 2026. Older tutorials, URLs, and some interfaces may still use Looker Studio; in this guide, Data Studio refers to the current product formerly known as Looker Studio.

01 Report Goals and Page Structure

A genuinely useful ecommerce report should help the team answer several core questions quickly: Are revenue and orders rising or falling? Which channels deliver higher-quality traffic and revenue? Do users drop off mainly at product view, add to cart, checkout, or payment? Which products attract traffic but fail to convert? How many orders and how much revenue did advertising spend ultimately generate?

Recommended Six-Page Report Structure

Report Design Principles

• Each page should answer one category of business question. Do not place every chart on a single page.
• Define each metric before designing the layout. The same metric must use the same definition on every page.
• Prioritize trends, differences, and anomalies instead of showing totals alone.
• Keep the first version to 6-10 primary charts per page to avoid excessive information density.

02 Pre-Build Data Checks

2.1 Confirm That GA4 Ecommerce Events Are Collected Correctly

Data Studio displays and combines data; it cannot replace GA4 ecommerce tracking. Before building the report, confirm that the website sends the key ecommerce events and includes complete order parameters.

Implementation Checklist

• The purchase event fires only after successful payment, not when the checkout page loads.
• Every order sends a unique transaction_id to prevent duplicate orders when the thank-you page is refreshed.
• The value and currency parameters are correct and match the actual business currency.
• The items array includes required information such as item name, item ID, price, and quantity.
• Test orders, internal traffic, failed payments, and canceled orders have clearly defined handling rules.

2.2 Standardize Revenue and Order Definitions

GA4 may show similar fields such as Purchase revenue, Gross purchase revenue, Total revenue, Purchases, Ecommerce purchases, and Transactions. Because their scopes differ, choose the primary definitions before building the report.

If the business focuses on gross sales before refunds, replace Purchase revenue with Gross purchase revenue and clearly label the report or note as “Gross Sales.” Do not mix different order fields across pages.

2.3 Confirm Time Zone, Currency, and Data Range

• Keep the GA4 property time zone aligned with the daily reporting time zones used by the ecommerce platform and advertising platforms.
• For multi-currency stores, decide which currency the report will display and confirm whether exchange-rate conversion has been completed.
• Validate the first version using one complete calendar week so incomplete same-day data does not distort the comparison.

03 Create the Report and Connect GA4

3.1 Create a New Report

1. Open the Data Studio home page and click Create in the upper-left corner.
2. Select Report.
3. In the “Add data to report” window, select Google Analytics.
4. Select the Google Analytics account and the appropriate GA4 property.
5. Click Add to connect the data source to the report.
6. Rename the report “Ecommerce Performance Dashboard” or another clear business-facing title.

Navigation Path

Create → Report → Google Analytics → Select the GA4 property → Add

After you add the data source, Data Studio usually creates a default table automatically. Delete the default component, then add scorecards, time-series charts, tables, and filter controls step by step.

3.2 Select Data Credentials

3.3 Recommended Data Source Naming

Consistent naming reduces confusion when blending data, copying charts, and troubleshooting access issues later.

04 Set Up the Base Layout and Filters

4.1 Create a Consistent Page Template

Build one consistent page template first, then duplicate it for the remaining pages. Keep the report title, metric-definition note, date range, and global filters at the top. Structure the main body in three layers: core scorecards, trend and category charts, and detailed tables.

• Set the canvas width to 1366 or 1440 pixels and keep the left and right margins consistent.
• Limit each page to 6-10 primary charts to maintain a clear reading flow.
• Set the title, date control, and global filters as report-level components when appropriate.

4.2 Add a Date Range Control

Navigation Path

Add a control → Date range control

Place the date control in the upper-right corner. For a day-to-day performance dashboard, set the default range to “Last 30 days, excluding today” to avoid misreading incomplete same-day data.

4.3 Add Global Drop-Down Filters

Navigation Path

Add a control → Drop-down list

A drop-down control can use a default value, custom sorting, single or multiple selection, and a search box. After configuring it, test whether the filter affects every relevant chart on the page.

05 Build the Ecommerce Overview Page

The purpose of the overview page is not to show every data point. It should help a manager assess overall business performance within 30 seconds and quickly identify issues that require deeper analysis.

5.1 Add Core Scorecards

Navigation Path

Add a chart → Scorecard

Enable previous-period comparison for every scorecard and standardize number formats. Use currency for revenue, whole numbers or K/M abbreviations for orders and users, and two decimal places for rates.

5.2 Create Average Order Revenue

Field name: Average Order Revenue

CASE
  WHEN Ecommerce purchases = 0 THEN 0
  ELSE Purchase revenue / Ecommerce purchases
END

Set the field type to Currency. Because the formula uses Purchase revenue after recorded refunds, “Average Order Revenue” is more precise than “Average Order Value” in this context.

5.3 Create Orders per Session

Field name: Orders per Session

CASE
  WHEN Sessions = 0 THEN 0
  ELSE Ecommerce purchases / Sessions
END

Set the field type to Percent. Avoid calling it “Website Conversion Rate,” because one user may complete more than one order in a single session.

5.4 Add Revenue Trend Charts

Revenue and order count usually differ greatly in scale. For readability, use two separate trend charts or a dual-axis combination chart instead of forcing both metrics onto the same axis.

5.5 Add Channel Revenue Charts and Detail Tables

06 Build the Conversion Funnel Page

The conversion funnel page helps identify the shopping stage where users drop off most. For the first version, use four metric blocks with stage conversion rates instead of relying on a complex third-party funnel component.

6.1 Add the Four Funnel Stages

6.2 Create Stage Conversion Rates

View-to-Cart Rate

CASE
  WHEN Item view events = 0 THEN 0
  ELSE Add to carts / Item view events
END

Cart-to-Checkout Rate

CASE
  WHEN Add to carts = 0 THEN 0
  ELSE Checkouts / Add to carts
END

Checkout-to-Purchase Rate

CASE
  WHEN Checkouts = 0 THEN 0
  ELSE Ecommerce purchases / Checkouts
END

6.3 Recommended Page Layout

Use four rectangular blocks from left to right: “Item Views → Add to Cart → Begin Checkout → Purchase,” with the relevant conversion rate between each pair of stages. This is not a traditional funnel shape, but the hierarchy is clear and works well in weekly reports and management presentations.

07 Build the Traffic Acquisition Page

The acquisition page should not merely answer “Which channel brings the most traffic?” It should answer “Which channel brings the most commercially valuable traffic?”

7.1 Create the Channel Performance Table

Field name: Revenue per Session

CASE
  WHEN Sessions = 0 THEN 0
  ELSE Purchase revenue / Sessions
END

7.2 Create the Source / Medium Detail Table

Use Session source / medium as the dimension, reuse the channel-table metrics, and sort by Purchase revenue in descending order. Add conditional formatting to highlight sources with high traffic but no orders, sources with low traffic but strong revenue efficiency, and abnormal traffic classified as Unassigned.

7.3 Do Not Mix Session and First User Dimensions

08 Build the Product Performance Page

The product page is where ecommerce reports most often develop scope and definition errors. The key rule is simple: item-scoped dimensions must be paired with item-scoped metrics.

8.1 Create the Product Detail Table

8.2 Create Product Conversion Metrics

Item Add-to-Cart Rate

CASE
  WHEN Items viewed = 0 THEN 0
  ELSE Items added to cart / Items viewed
END

Item Purchase Rate

CASE
  WHEN Items viewed = 0 THEN 0
  ELSE Items purchased / Items viewed
END

Revenue per Item Sold

CASE
  WHEN Items purchased = 0 THEN 0
  ELSE Item revenue / Items purchased
END

These are item-unit ratios, not user conversion rates. They can exceed 100% when quantities differ. When a user-based rate is required, use GA4’s Cart-to-view rate or Purchase-to-view rate where available.

8.3 Use a Product Performance Matrix

8.4 Compare Item-Scoped and Event-Scoped Fields

09 Build the Pages, Devices, and Geography Page

9.1 Landing Page Performance Table

A minimum traffic threshold prevents pages with only one or two visits from appearing to have exceptionally high conversion rates because of a single accidental order.

9.2 Device Performance Analysis

• Is mobile traffic significantly higher than desktop traffic?
• Is the mobile order rate significantly lower?
• Is average order revenue lower on mobile?
• Does most checkout abandonment occur on mobile?

If mobile accounts for a large share of traffic but converts much worse, review page speed, product images, payment methods, coupon-code entry, and the mobile checkout flow first.

9.3 Country or Region Performance Table

10 Connect Advertising Cost Data and Calculate ROAS

GA4 can show orders and revenue, but complete ROAS, CPA, CPC, and CTR calculations also require advertising cost data. Google Ads can be connected directly. For other platforms, organize the cost data in Google Sheets and blend it with GA4.

10.1 Prepare the Advertising Cost Sheet

• Date must use a true date data type, not a text-formatted date.
• Cost, Impressions, and Clicks must be numeric fields with the default aggregation set to Sum.
• Keep Campaign ID as text so leading zeros are not removed.
• Standardize cost currency across advertising platforms before blending the data.
• Do not add temporary notes that change daily to Campaign name.

10.2 Connect Google Sheets

Navigation Path

Resource → Manage added data sources → Add a data source → Google Sheets

After connecting the sheet, check the date type, numeric types, and default aggregations in the data-source field panel. Use a clear name such as “Ad Cost | Platform Mix | Daily” for easy identification later.

10.3 Blend Advertising Cost and GA4 Data

Navigation Path

Select a chart → Blend data

10.4 Create Advertising Efficiency Metrics

ROAS

CASE
  WHEN SUM(Cost) = 0 THEN 0
  ELSE SUM(Purchase revenue) / SUM(Cost)
END

CPA

CASE
  WHEN SUM(Ecommerce purchases) = 0 THEN 0
  ELSE SUM(Cost) / SUM(Ecommerce purchases)
END

CPC

CASE
  WHEN SUM(Clicks) = 0 THEN 0
  ELSE SUM(Cost) / SUM(Clicks)
END

CTR

CASE
  WHEN SUM(Impressions) = 0 THEN 0
  ELSE SUM(Clicks) / SUM(Impressions)
END

Field aggregation in blended data can vary by source and blend structure. If “Re-aggregating metrics is not supported” appears, check whether the field is already aggregated and try removing the outer SUM().

11 Common Calculated Fields and Aggregation Rules

11.1 Ecommerce Calculated Field Reference

11.2 Handle Zero Denominators in Every Division Formula

General Template

CASE
  WHEN Denominator field = 0 THEN 0
  ELSE Numerator field / Denominator field
END

A calculated field can be created at the data-source level or only within a specific chart. Data-source fields are best for repeated use; chart-level fields are better for testing a new formula or serving a single chart.

11.3 Do Not Add SUM to GA4 Metrics Automatically

Metrics returned by the GA4 connector are usually already aggregated. Writing SUM(Purchase revenue) directly in a native GA4 data source may trigger “Re-aggregating metrics is not supported.”

12 Interactions and Visual Design

12.1 Enable Chart Cross-Filtering

Settings Path

Chart interactions → Cross-filtering

Once enabled, viewers can click a channel, country, device, or item to filter the other charts on the page automatically. Use only the primary channel, country, and device charts as filters; do not turn every chart into a filter control. Cross-filtering is unavailable for scorecards and bullet charts, is off by default for Ads-related connectors, and follows the same cross-data-source compatibility limits as other controls.

• Click Paid Search to view paid-search performance only.
• Click United States to view U.S. market data only.
• Click Mobile to view mobile conversions only.
• Click an item to view its trend only.

12.2 Add Optional Metrics

Enable Optional metrics on product and channel tables so viewers can switch metrics themselves. This reduces the number of charts while preserving deeper analysis.

12.3 Visual Design Standards

Example of Consistent Number Formatting

13 Data Validation and Troubleshooting

13.1 Validate with a Fixed Date Range

Do not publish immediately after completing the report. First select one complete calendar week and make sure Data Studio, GA4, the ecommerce platform, and the advertising platforms use exactly the same dates, time zone, currency, and filters.

Validate GA4

• Purchase revenue
• Ecommerce purchases
• Sessions
• Active users
• Items purchased

Validate the Ecommerce Platform

• Successful order count and paid revenue
• Refund amount and canceled orders
• Test orders and internal orders
• Offline orders or orders from non-website channels

GA4 will not always match Shopify, WooCommerce, or another order system exactly because the systems handle payment status, refunds, cookies, ad blockers, and cross-device users differently. The important question is whether the difference is stable and explainable.

Validate the Data Blend

Manual Spot-Check Formulas

ROAS = Revenue ÷ Cost
CPA = Cost ÷ Orders

• Is Date being used as the only join key?
• Do the left and right tables use the same level of granularity?
• Is Campaign ID duplicated or formatted inconsistently?
• Does one campaign map to multiple names?
• Do duplicate rows already exist before blending?

13.2 Troubleshoot Common Issues

13.3 Common Incorrect and Correct Field Combinations

14 Sharing, Publishing, and Final Checks

14.1 Sharing and Permissions

After completing the report, use Share in the upper-right corner to invite specific users, set viewer or editor access, generate a viewing link, or schedule report delivery. Before sharing externally, check the data credentials and the sensitivity of the information again.

PDF is useful for archiving, while the online report is better for changing date, channel, country, and device filters. Keep the online report link as well.

14.2 Final Publishing Checklist

• GA4 item-view, add-to-cart, checkout, and purchase events are collected correctly.
• Purchase revenue and Ecommerce purchases definitions have been standardized.
• Dates, currency, and time zone are aligned.
• Scorecards compare against the previous period or previous year.
• The traffic page consistently uses Session dimensions for current-session attribution or First user dimensions for first-touch acquisition; the two scopes are not mixed within the same table.
• Item dimensions are paired only with item-scoped metrics.
• Every division formula handles a zero denominator.
• Native GA4 metrics are not incorrectly aggregated again with SUM.
• Advertising cost and GA4 data are blended at the same level of granularity.
• The advertising blend has been checked for duplicate calculations.
• Date and channel filters control the charts correctly.
• Report permissions and data credentials meet the organization’s security requirements.
• The report has been validated against GA4, the order platform, and advertising platforms using a fixed date range.

Appendix: Metric Reference and Additional Modules

A.1 GA4 Field Naming Reference

A.2 What to Build Next

• Profit dashboard: product cost, payment fees, shipping cost, advertising cost, and contribution profit.
• New versus returning customer analysis: new-customer revenue, returning-customer revenue, repeat purchase rate, and customer acquisition cost.
• Inventory dashboard: available inventory, inventory turnover, stockout risk, and slow-moving products.
• Regional performance dashboard: performance by country, state or province, city, language, and currency.
• Advertising creative dashboard: asset, format, copy, video length, and landing-page performance.