GA4 Dashboards: The 14+1 Card Build for Indian D2C Brands
Google Analytics now has native dashboards, capped at 15 cards. Here is the exact setup path and the 14+1 card layout we would build for an Indian D2C store.

Google Analytics now has native dashboards, capped at 15 cards. Here is the exact setup path and the 14+1 card layout we would build for an Indian D2C store.

01Google Analytics added drag-and-drop GA4 dashboards on 9 September 2026, built from Reports via + Create, then Dashboard.
02GA4 dashboards allow 15 cards on standard properties and 30 on premium properties, and every chart counts as a card.
03Every published GA4 dashboard is shared with everyone on the property, and segments, API access and card-level comparisons are not supported yet.
04The PingTalks 14+1 layout uses 14 cards for an Indian D2C daily view and keeps one card spare for campaigns or AI referrals.
Fifteen cards. That is all a standard GA4 property gets on one of the new GA4 dashboards Google added to Analytics on 9 September 2026, and most teams will waste half of them on vanity scorecards. Spend 14 of them on the layout below, keep one spare, and your founder gets a daily D2C view without anyone opening Data Studio.
We built the plan around how Indian D2C stores actually sell: festive spikes, UPI checkouts, and Tier 2 cities that convert differently from Mumbai and Bengaluru.

You create a GA4 dashboard from the Reports menu: click + Create at the top of the left navigation, choose Dashboard, drag chart types onto the grid, drop dimensions and metrics into each chart, then Save and Publish. You need the Editor or Administrator role. Anyone with property access can view it once published.
Here is the exact path, from Google’s own help article:
Watch out: every published dashboard is shared with the whole property. If your agency, freelancers or a former employee still have access, they will see your founder’s revenue view. Audit users under Admin before you publish.
GA4 dashboards support six chart types, a 15-card cap on standard properties and 30 on premium ones, and automatic sharing with the property. Google’s help page says API support, segments and card-level comparisons are not supported yet, so treat dashboards as a quick daily view, not an analysis tool.
| Feature | GA4 dashboards (Sept 2026) | What it means for you |
|---|---|---|
| Chart types | Scorecard, table, line, bar, donut, funnel | No geo maps or scatter plots. Use a city table instead. |
| Card limit | 15 standard, 30 premium | Every chart counts, scorecards included. |
| Sharing | Shared with everyone on the property | No private dashboards. |
| Segments, API, card comparisons | Not supported | Explorations still handle cohort and segment work. |
Two practical quirks surfaced in early testing. Ruchelle L, writing on the Ray Pastoors analytics blog on 21 September 2026, reported that dashboards follow the Paid and Organic Last Click model used by standard reports, and that she could only add 10 cards before hitting what she suspected was a bug. Score cards show a percentage change only when you apply a date comparison.
Use six scorecards for sales health, one daily trend line, one checkout funnel, three tables for source, city and landing page, two bar charts for device and product, and one donut for channel mix. That is 14 cards. The fifteenth stays empty for whatever your next campaign needs to track.
We call it the 14+1 layout. It answers one question only: did the store sell well yesterday, and why? Ruchelle L gives the same advice from the other side: build each dashboard around one question, not everything you can fit.
| Cards | Chart | Dimensions and metrics |
|---|---|---|
| 1 to 6 | Scorecards | Sessions, Ecommerce purchases, Purchase revenue, Average purchase revenue, Session key event rate, New users |
| 7 | Line | Date by Sessions and Purchase revenue, daily |
| 8 | Funnel | view_item, add_to_cart, begin_checkout, add_payment_info, purchase |
| 9 | Table | Session source / medium by Sessions, Purchases, Revenue |
| 10 | Table | City by Sessions, Session key event rate |
| 11 | Table | Landing page by Sessions, Session key event rate |
| 12 and 13 | Bar | Device category by Revenue; Item name by Item revenue |
| 14 | Donut | Session default channel group by Purchase revenue |
| 15 | Spare | Campaign of the month, or a Source Group card for AI referrals |
Card 8 matters most in India. The gap between add_payment_info and purchase is where failed UPI collect requests and card OTP drop-offs show up. If that step loses far more users than begin_checkout, call your payment gateway before you touch your ads.
Card 10 is your Tier 2 check. If Indore, Lucknow or Coimbatore bring sessions but convert at half your metro rate, fix COD and delivery-date messaging on those landing pages first.

Pro tip: Google added a Source Group dimension on 11 June 2026 that groups variants such as fb and facebook into one value, with built-in grouping for ChatGPT and Perplexity. If it shows in your dashboard field list, use it on card 15 to watch AI referrals. For deeper AI-bot tracking, see our guide to Microsoft Clarity’s AI visibility report.
A revenue scorecard rises with traffic, so festive weeks look like wins even when the site converts worse. Pair Purchase revenue with Session key event rate and divide revenue by sessions yourself. If revenue per session falls while revenue climbs, your extra festive traffic is leaking money at checkout or on the landing page.
Our maths, using an illustrative D2C store:
The revenue card shows a 33% jump and everyone celebrates. Revenue per session actually fell 24%. Had the rate held at 1.6%, the same 3,500 sessions would have produced 56 orders and ₹78,400. That is ₹25,200 a day left on the table, or about ₹1.76 lakh across a seven-day sale.
A dashboard that only shows revenue will congratulate you for the worst week of conversion you had all year.
This is why scorecards 3 and 5 sit side by side in the 14+1 layout. Apply a date comparison against the previous period and both show their percentage change at a glance. If you want to see how far measurement gaps distort Indian marketing decisions, our breakdown of the Nielsen Annual Marketing Report puts numbers on it.
Yes, for anything that blends data or goes to a client. Google renamed Looker Studio back to Data Studio on 11 April 2026, and its free tier still connects Google Ads cost, CRM and Shopify data. GA4 dashboards cannot. Use dashboards for the in-house daily check and Data Studio for reports leaving the building.
Here is where we disagree with the excitement. Antonio Fernandez, founder and CEO of Bangkok agency Relevant Audience, argued on 13 September 2026 that dashboards expose messy tracking rather than fix it. He is right. If your purchase event fires twice on UPI redirects, the new scorecard will show doubled revenue in a prettier box. Fix tagging first using our GA4 setup guide.
Luis Rijo, founder of PPC Land, raised a second risk on 12 September 2026: with shared-by-default publishing, dashboard sprawl becomes a governance problem for the property. Agencies managing 20 client properties face a related pain. With no API, each dashboard must be rebuilt by hand in every property.
There is also a moving target. Josh Moser, Senior Director of Product Management at Google, wrote on 10 August 2026 that Gemini-built dashboards from Google Ads were “coming soon in Google Analytics”. The September release has no prompt builder, and Google has not said whether the two will merge. Expect the manual canvas to change.

Skip them if your team already lives in a working Data Studio report, if you need segments such as repeat versus first-time buyers, or if you are an agency that must roll one template across many client properties. Small brands with one property and no analyst gain the most.
Consent matters too. If your cookie banner blocks analytics for people who decline, their visits never reach any GA4 card, so treat the numbers as consenting users only. Our explainer on the DPDP consent manager rule covers what brands actually need to do.
Build one GA4 dashboard this week if you run a single D2C property and nobody opens your Data Studio reports. Use the 14+1 layout, pair revenue with conversion rate, and watch the payment step of the funnel. Agencies and teams that need segments or blended ad cost should stay on Data Studio and revisit when Google adds API and segment support.
Yes. Dashboards are part of standard Google Analytics 4 properties at no cost. Standard properties get 15 cards per dashboard, while premium (Analytics 360) properties get 30.
Only users with the Editor or Administrator role can create and publish GA4 dashboards. Anyone with access to the property can view a published dashboard.
No. Google says all published dashboards are shared with the property. Check who has property access before you publish anything showing revenue.
Not yet. Google lists segments, API support and card-level comparisons as unsupported. Use Explorations for segment analysis such as new versus returning buyers.
No. GA4 dashboards only show Analytics data and have six chart types. Data Studio, renamed from Looker Studio in April 2026, still handles blended data such as ad cost and CRM numbers and client-facing reports.
Early testing reported on the Ray Pastoors analytics blog found dashboards use the Paid and Organic Last Click model of standard reports, not data-driven attribution. Google has not documented this on its help page, so verify in your own property.
What changed in marketing and AI, why it matters and exactly what to do. In your inbox at 11:00 IST.