Zendesk Google Analytics, Set Up on the Help Centre
Zendesk Google Analytics works on the help centre and nowhere else. Knowing that boundary before you start saves a lot of confused reporting later.
What Zendesk Google Analytics can and can't see
The help centre is a normal website, served on your Zendesk domain, rendered from templates you control. So it accepts a tag and behaves like any other site.
Everything else doesn't. The agent interface is an application, not a set of pages, and you're not putting a tag in it. Tickets, macros, views and SLA data are entirely invisible to GA. Nor does GA follow a visitor from reading an article into submitting a ticket in any joined-up way, because the submission lands in a system it cannot see.
That boundary is the whole design constraint. GA answers "what did people read and search for", and it will never answer "did that stop them contacting us". Pairing it with ticket volume from Explore is how you get the second half.
Getting the tag in
There are two routes and they're not equivalent.
Guide has a settings field for a Google Analytics tracking ID. It exists, and on older accounts it was built for the previous generation of Analytics property. If your property is a newer GA4 one, that field may not do what you want.
The reliable route is editing your theme and putting the tag in the document head template, which is the same thing you would do on any site.
<!-- document_head.hbs -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag("js", new Date());
gtag("config", "G-XXXXXXXXXX");
</script>Editing the theme means you now own that code through every theme update. Keep a note of it somewhere your future self will find, because a theme swap silently removes your analytics and nobody notices for a month.
On a multibrand help centre, each brand has its own theme. Tag each one, and decide whether they share a property or get their own.
Tracking help centre search terms
This is the single most valuable thing GA gives you here, and it's easy because Guide puts the search term in the URL.
A help centre search lands on a results page with the query as a parameter, along the lines of /hc/en-us/search?query=refund+policy. Configure site search in your GA property to read the query parameter and search terms start appearing as data instead of guesswork.
What you're looking for isn't the popular searches. It's the searches that end in nothing: a term with a high exit rate, or a results page with no click. Every one of those is an article you have not written, described in the customer's own words.
Zendesk has its own search reporting on some plans, and where it exists it's often the better source, because it knows what returned zero results. Use both if you can. The help centre search guide covers what search is matching in the first place.
What to measure once it's on
Resist the urge to build a funnel. The step you care about happens in Zendesk, where GA can't follow.
One report that is worth the ten minutes: article pageviews next to ticket volume for the same topic, month by month, pasted into the same spreadsheet. It is crude, and it is the closest thing to a deflection measurement anyone gets without instrumenting the product itself.
Consent, privacy and signed-in users
If your help centre serves the EU or UK, the tag falls under the same consent rules as the rest of your site. That usually means a consent banner on the help centre too, which teams forget because the help centre feels like an internal tool.
The other consent-adjacent trap is ad blockers and privacy browsers. A meaningful share of technical audiences block analytics outright, so help centre traffic is systematically undercounted, and undercounted unevenly across your articles. Treat the numbers as directional. Comparing this month to last month is fine. Quoting an absolute figure to somebody who will act on it is not.
Also worth knowing: help centre URLs can contain identifiers, and requests pages sit behind sign-in. Do not send anything that identifies a customer into an analytics property. Restrict tracking to public content, and keep the authenticated request pages out of it if you have any doubt.
Frequently asked questions
Does Zendesk help center analytics work with GA4?
Yes. Zendesk GA4 tracking is the current setup, added as a tag in the theme. Zendesk help center analytics beyond page views means tracking search terms as events, which is the part worth doing.
Can Google Analytics track Zendesk tickets?
No. GA only sees the help centre pages. Ticket data lives in Zendesk and is reported through Explore.
Does the Guide settings field support GA4?
It was built for an earlier generation of Analytics property, so behaviour with a newer property varies. Adding the tag to the document head template is the dependable route.
How do I see what people search for in the help centre?
Guide puts the search term in the URL as a query parameter, so configure site search in GA to read it. Zendesk search reporting is a useful second source where your plan includes it.
Will a theme update remove my tracking code?
It can. Any tag added to a theme template lives in that theme, so re-apply it whenever you swap or restore a theme.
Do I need a cookie banner on my help centre?
If you are subject to consent rules elsewhere on your site, yes. The help centre is a public website like any other.
Analytics shows the gap, not the repeat
GA can tell you which article is missing. It cannot tell you the same person filed two tickets about it.
Start free trial14-day free trial. No credit card required.