Church Metrics That Matter: A Practical GA4 + Search Console Setup for Non-Technical Leaders
By
Izzy Gregorio
·
5 minute read
Church Analytics · Setup Guide
How to Set Up GA4 and Search Console for Your Church
If you have ever asked whether your website is actually helping people take next steps, and nobody in the room could answer, this is the fix. Written for church leaders who are not technical and should not have to be.
By Izzy Gregorio · Updated August 2026 · 9 min read
In short
Google Analytics 4 shows what people do once they reach your site. Search Console shows how they found you and whether Google is struggling with your pages. Configure seven events covering plan a visit, directions, calls, sermons, giving, form submissions, and group or serve interest. Then watch for broken pages, dead links, and slow loading. One page, three sections, one decision a month.
Why this matters
Missing visibility is a leadership problem wearing a technical costume
When a team cannot see clearly, it drifts. Meetings turn into opinion contests and the loudest voice sets direction. That costs more than time. It costs the chance to serve people better, because effort goes where someone felt strongly rather than where someone was actually looking for help.
Analytics is not about becoming a data person. It is about getting your team to agree, in advance, on what success looks like. That is leadership work that happens to use a dashboard.
The whole goal, in one sentence: one system that answers three questions. What is getting discovered, what is getting engaged, and what is driving next steps. Everything below serves those three, and anything that does not serve them can wait.
The two tools
GA4 and Search Console, in plain English
People conflate these constantly, and the confusion is why so many church dashboards say nothing useful. They answer different questions, and you need both. Here is the difference in one table.
| Google Analytics 4 | Google Search Console | |
|---|---|---|
| The question it answers | What happened after somebody arrived on your site. | What happened before the click, and why the click might not have happened at all. |
| What you look at | Users: how many people visited. Engagement: whether they actually interacted or left immediately. Events: the specific actions they took. |
Queries: what people typed into Google. Pages: which of yours Google shows, and which get clicked. Errors: problems quietly hurting your visibility. |
| The trap | Tracking only users. Then you chase traffic and never learn whether anybody did anything. | Never opening it. Errors here are silent and can suppress a page for months without anyone noticing. |
| Best single use | Counting the next steps people actually took this month. | Reading the real phrases your neighbors typed when they were looking for help. |
Set up both. They take an afternoon, they are free, and neither one works properly without the other. If you only track users, you will chase traffic. If you track events, you can measure whether anyone actually moved.
The core setup
The seven events every church should track
Events are where GA4 stops being trivia and becomes useful, because these are the actions that show real intent. Start with these seven. You can add more later, and most churches never need to. Between them they cover the overwhelming majority of meaningful behavior on a church website.
| # | The event | What to capture | What it tells you |
|---|---|---|---|
| 1 | Plan a visit click | Clicks on the plan a visit page link or button, wherever it appears. | The clearest signal of intent on your site. Somebody is considering walking in on Sunday. |
| 2 | Get directions click | Clicks to Google Maps or your directions link. | Even higher intent than plan a visit. This person is deciding how to get there. |
| 3 | Call click | Taps on your phone number, which happens almost entirely on mobile. | Often someone in urgent need. Worth reviewing separately from everything else on this list. |
| 4 | Watch sermon click | Clicks from your site to your video platform or sermon player. | Quiet consideration. People often watch for weeks before they visit, and this is the only trace they leave. |
| 5 | Give click | Clicks through to your giving platform. | Compare this against completed gifts. A wide gap means the giving flow is broken, usually on a phone. |
| 6 | Form submit | Completions on contact, prayer request, and next steps forms. | Somebody raised a hand and gave you their name. The most actionable number on the dashboard. |
| 7 | Group or serve interest | Clicks to groups, serve, or signup actions. | Existing attenders moving deeper. This is the number that predicts retention rather than growth. |
Practical note: most website platforms can send these to GA4 without custom code, and GA4 detects some automatically. If your setup needs a developer, that is one afternoon of work, once, and it is the highest-value hour anyone will spend on your website this year.
What to watch for
The three silent killers
The most damaging website problems are the quiet ones. Nobody complains, nobody files a ticket, and your visibility and next steps drop month over month while everyone assumes the content is the issue.
| The problem | What it does | Where to find it |
|---|---|---|
| Broken pages | Removed or renamed pages that still get linked to. Damages trust immediately and search visibility slowly. | Search Console flags these under page indexing. Check monthly. |
| Dead links and buttons | Menu items and buttons that go nowhere, most often on mobile after a redesign nobody re-tested. | Your own phone. There is no report for this one. |
| Slow pages | Oversized images, video backgrounds, and heavy page builders. People leave before anything appears. | Free page speed tools, or the phone test below, which is faster and honest. |
The five-minute check, no technical skill required
Open your site on your phone, off wifi, and do this in order.
Tap every item in the top menu. Every one.
Tap plan a visit. Tap directions. Tap give. Complete the giving flow to the payment screen without paying.
Count the seconds each page takes to become usable.
If it feels slow, it is slow. You are the most patient visitor your site will ever have, because it is yours. A stranger on a hard day has considerably less patience than you do.
The output
The one-page monthly dashboard
Your pastor and board do not need a dozen charts. They need one page that supports a stewardship decision. Five sections, in this order.
- Discovery
Search impressions, Google Business Profile actions, and sermon watch time. Are people finding you at all?
- Engagement
Engaged sessions, your top pages, and how the sermon page performed. Did they stay once they arrived?
- Next steps
Plan a visit clicks, directions clicks, give clicks, and form submissions. Did anybody actually move?
- Issues
Broken pages, dead links, and slow pages to fix next month. Name them, do not just count them.
- One decision
What you are changing next month because of what is above, with a name and a date attached.
If your dashboard does not lead to a decision, it is just a report.
Keep it to one page and force one action a month. A church that changes one thing every month for a year has changed twelve things. Most change nothing and describe it thoroughly.
See it in a real church
Rock Valley Christian Church, Murrieta
A working example of this setup applied to a local congregation: which events were tracked, what the monthly page looked like, and the decisions that came out of it. Worth reading before you build your own.
Common questions
Church analytics setup, answered
What is the difference between GA4 and Google Search Console?
GA4 shows what people do after they reach your website: how many visited, whether they engaged, and which actions they took. Search Console shows what happened before the click: the phrases people searched, which pages Google displays, and technical errors that reduce visibility. They answer different questions and a church needs both.
Which GA4 events should a church track?
Seven cover almost everything meaningful: plan a visit clicks, get directions clicks, phone number taps, sermon or video clicks, giving platform clicks, form submissions for contact and prayer requests, and clicks toward groups or serving. Start with these and add more only if a specific question requires it.
How do I check my church website for problems without technical skills?
Open it on your phone, off wifi. Tap every top menu item, then plan a visit, directions, and give, following the giving flow to the payment screen without paying. Count how long each page takes to become usable. If it feels slow to you, it is slow, because you are the most patient visitor the site will ever have.
What should a church website dashboard include?
One page with five sections: discovery, engagement, next steps, issues to fix, and one decision for the coming month with an owner and a date. Anything longer stops being read. If the page does not produce a decision, it is a report rather than a tool.
Why are broken pages and slow loading such a problem for churches?
Because they fail silently. Nobody reports a dead button or a page that took eight seconds. They simply leave, and the loss appears as flat numbers rather than as a complaint. Search visibility also declines gradually when Google finds broken pages, which compounds the problem over months.
Start here
You do not need more dashboards. You need a clean setup.
If GA4 and Search Console feel confusing, the answer is not more charts. It is the right seven events tracked properly and one page that shows discovery, engagement, and next steps. Bring your questions and you will leave knowing exactly what to fix first, whether or not anyone else does the work.
Book a ministry strategy consult
Free. No obligation.
Not ready yet? Subscribe to the newsletter and get the next breakdown in your inbox.