Tutorial
IntermediateA Five-Question GA4 Dashboard, Ready in About an Hour
Copy a free official Google template, plug in your association's GA4 property with a click, and get a one-page dashboard that answers the five questions your team actually asks: where visitors come from, what they read, and which pages turn them into members, registrants, and subscribers.
Time needed: About an hour the first time; the dashboard itself takes about five minutes
Before you start:
- Admin access to your association's GA4 property
- A Google account (for Looker Studio — the same login works)
- One colleague who knows which pages matter: the join page, the event registration page, the newsletter signup
Ga4 Analytics Dashboard Looker Studio Marketing
By the end of this tutorial you will have a one-page dashboard on your own GA4 data that answers five questions your team actually asks about the website: where visitors come from, what members read, and which pages turn visitors into members, registrants, and subscribers. No building from scratch, no exports, no downloads — you copy an official Google template and plug in your property with a click.
Most association teams already collect web data and still cannot answer those questions. Back in 2012, NTEN’s State of Nonprofit Data, covered by ASAE’s Associations Now, found that 99 percent of nonprofits tracked metrics somewhere, but communications and marketing data were tracked less consistently than financials, and many merely measured instead of using data strategically. The tooling got a major upgrade since; the habit mostly did not. This tutorial builds the habit: one page, five questions, numbers you will actually open.
See the finished thing first: open the five-question GA4 dashboard example — five tiles on demo data, no signup. When you’re ready, the steps below get you the same dashboard on your own numbers in about an hour.
Step 1: Write your five questions before you open any tool
Dashboards fail when they start with charts. Start with the questions your team asks in meetings, in plain words. For most associations, five cover nearly everything:
- Where do new visitors come from?
- Which pages do members actually read?
- Which pages lead to membership joins?
- Which pages lead to event registrations?
- Which pages lead to newsletter signups?
Write yours down and get your colleague to agree they are the right five; everything below exists to answer exactly these. AOTA, the occupational therapy association, did this well: a 2017 Associations Now piece describes how its team joined Google Analytics with CMS and membership data to see the paths members took through the site, then used on-site search data to overturn a content policy hiding articles members wanted. The dashboard served the questions; the questions came first.
Step 2: Fix data retention before you build anything
This is the step everyone skips and the one that silently ruins dashboards months later. In your GA4 property, go to Admin, then Data Settings, then Data Retention, and change event data retention from 2 months to 14 months. The default is 2 months, which means your explorations and funnel reports quietly lose older data while the standard reports look fine. Set it to 14 months now; it cannot recover what already aged out.
Step 3: Mark your three key events
A dashboard answers “which pages lead to joins” only if GA4 knows what a join is. In Admin, under Events, mark these as key events: the membership join confirmation, the event registration confirmation, and the newsletter signup confirmation. Name them in plain words your successor will understand: membership_join, event_registration, newsletter_signup, not conv_1. If GA4’s event model is new to you, TechSoup’s nonprofit GA4 walkthrough covers events, conversions, and account structure in nonprofit terms.
Step 4: Tag the links you send out
“Where do new visitors come from” is unanswerable if every link looks identical. Tag the links in your emails, social posts, and partner mentions with UTM parameters: utm_source (newsletter, linkedin), utm_medium (email, social), utm_campaign (spring_membership_drive). Keep a one-line log of campaign names so next quarter’s staff uses the same spellings. Ten minutes here is the difference between “traffic went up” and knowing which email brought the joins.
Step 5: Copy Google’s template and plug in your data
This is the whole build. Google publishes official Looker Studio templates — built by Google, free, no vendor branding, no sales call. Open the template gallery, choose an Analytics template, and click through to use it. (Google’s own instructions cover the copy flow if you want them.)
Then the one click that matters: the template opens with a data control asking which data to use. Select your association’s GA4 property. The copy saves to your Drive, and from that moment every tile reads your numbers. If you see a merchandise store’s numbers instead of yours, you’re looking at Google’s sample data — swap the data control to your property and it goes away.
No exports, no CSVs, nothing to install. And because the data never leaves your GA4 property, there is nothing for anyone to hold hostage — more on that below.
If the template’s tiles don’t match your five questions exactly, rename, delete, or duplicate tiles until each one answers one question from step 1. Resist tile six. Every dashboard grows barnacles; the discipline of this tutorial is that a tile must answer one of the five questions or it does not ship.
Step 6: Learn to read it — a worked example
Open the example dashboard and set the range to Last 30 days. The numbers are fictional, but read it exactly the way you’ll read yours:
- Where do new visitors come from? The longest bar wins. In the example it’s organic search — so the example association’s first job is keeping its search listings healthy, not buying ads.
- Which pages do members actually read? Sort by engagement time, not views. The webinar page holds people for over three and a half minutes — the site’s best-read page, even though the homepage gets more views.
- Which pages lead to joins? Nearly half the example’s joins start on
/membership/joinitself — the join page earns its keep — with the benefits page a distant second. - Which pages lead to registrations? The conference page drives registrations; the newsletter barely registers. That’s a content decision: promote the conference where registrations actually start.
- Which pages lead to signups? The trend line jumps in the weeks emails went out. The newsletter grows the newsletter — which tells you what to do more of.
Each tile on the example ends with a one-line takeaway. Write yours the same way: one sentence per tile, in plain words, the kind you’d say out loud in a meeting.
Step 7: Share it and schedule delivery
A dashboard nobody opens is a hobby. Share the report with your team, and schedule a monthly email delivery to yourself and your colleague from step 1: the report arrives, you spend ten minutes asking whether each tile moved and why. Put a quarterly thirty-minute review on the calendar now, while you are thinking about it.
Step 8: Run the two-minute check
Ask each of your five questions and point at the tile that answers it. Two failure modes to fix on the spot:
- A tile shows “(not set)”. GA4 is missing dimension information, usually because a custom dimension was never registered. In Admin, under Custom Definitions, register it (event-scoped), wait a day, and check again.
- A funnel is empty. The key event from step 3 is not firing. Open the page, complete the action yourself, and watch GA4’s real-time view to confirm the event arrives.
Ask questions in plain English
Dashboards answer the questions you thought of in advance. For the ones you think of in the meeting, Looker Studio can also answer typed questions about your data through Conversational Analytics: you type “which channels brought the most new visitors last month?” and get a chart back. One honest caveat: it chats with BigQuery data agents, not the GA4 connector this tutorial just set up, so there is a setup path (link GA4 to BigQuery, build a data agent, then chat). Our article Ask Your Website Data Questions in Plain English walks through what that takes, what it costs, and the five prompts to try first.
Your data stays yours
There is a reason this tutorial has you copy Google’s template into your own account instead of letting a vendor build the dashboard for you. Some platforms will happily build it inside their system, on their contract — and then warn you that leaving means losing your data, your history, your reports. The threat usually leans on something technical-sounding, like a tracking cookie, to make staying feel mandatory.
With this setup the threat is empty. Your data lives in your GA4 property, which you own. The report is a copy in your Drive, which you own. If you ever fire a vendor, change platforms, or just change your mind, the dashboard and every number in it come with you. Build on ground you own; rent everything else.
The dashboard that measures everything and answers nothing
Four mistakes we see in nearly every first dashboard, so you can skip them:
Building before writing the questions. The tool makes it easy to add tiles. Tiles without questions become decoration within a month. If a tile does not answer one of your five, delete it.
Skipping step 2. The retention default is the cruelest setting in GA4: everything looks fine until the quarter you need last year’s funnel and it is gone. Fourteen months, once, today.
Copying the template and stopping there. A template still pointed at Google’s sample data answers nobody’s questions. Connect your property in step 5 the same day, or the copy goes stale and nobody ever opens it again.
Reporting views instead of reading. A page with ten thousand views and eleven seconds of average engagement time is a page people bounced from, not a page people read. Sort by engagement time when the question is what members read.
One more, for the revenue side of the house: sponsors and exhibitors increasingly ask for proof their investment reached the right audience. A dashboard that joins web behavior with membership and event data answers exactly that: which segments engaged with which content, and what brought them there. The AOTA example above joined analytics to membership data for content decisions; the same join, pointed at sponsor questions, turns this dashboard into renewal-season evidence. Build it for your team first; the sponsor story follows.