FAQs: Google Analytics Dashboard for Help Center | Zoho Desk

FAQs: Google Analytics Dashboard for Help Center

Dashboard Overview

What is the Google Analytics Dashboard for Help Center?
The Google Analytics Dashboard brings Help Center traffic and engagement data into Zoho Desk. It helps support teams understand how customers reach the Help Center, which pages they use, where visitors are located, and whether visitors engage with content or leave without continuing.

Instead of reviewing raw analytics reports separately, teams can use the dashboard to monitor key Help Center indicators in one place. This is useful for identifying content gaps, measuring the impact of support campaigns, and prioritizing article improvements.
Does the dashboard work without a Google Analytics integration?
No, The dashboard is preconfigured only after Google Analytics integration has been set up in Zoho Desk.
If the integration is not configured, Help Center traffic and engagement data will not be available through this dashboard. Confirm that the intended Google Analytics profile is connected before attempting to review reporting data.
Where can the Google Analytics Dashboard be accessed?
  1. Open the Knowledge Base module.
  2. Select the Dashboard tab in the left panel.
  3. Click Google Analytics under the Dashboard submenu.
  4. Select the required Google Analytics profile.
  5. Choose a date range.
The dashboard then displays data for the selected profile and period.
Can the dashboard be limited to a specific reporting period?
Yes. Select a date range after choosing the Google Analytics profile. All dashboard metrics are then displayed for that selected period.

For example, a support manager can compare Help Center activity for the week after publishing a new troubleshooting article with activity from the preceding week.

Site Visit Report

What does the Site Visit Report measure?
The Site Visit Report summarizes how visitors arrive at the Help Center and how they interact with it during their sessions. It categorizes traffic into direct, email, referral, and total visits, while also showing engagement indicators such as pages per visit, average time on site, new-visit percentage, and bounce rate.

This report helps answer two different questions:
  1. How are customers finding the Help Center?
  2. What do customers do after they arrive?

What is a direct visit?
A direct visit occurs when a customer reaches the Help Center by entering its URL in a browser or using a browser bookmark.
However, direct traffic should not always be interpreted as deliberate URL entry. Google Analytics can categorize visits with an unidentifiable source as direct. A high direct-visit count may therefore include traffic whose original source was not captured.
What is an email visit, and why might email traffic appear as direct traffic?
An email visit is traffic from customers who follow a link to the Help Center from an email. This can include product announcements, support communications, or campaigns that direct recipients to an article.
To identify email traffic accurately, links in email messages must be tagged with campaign or UTM variables. Without those tags, the visit may be recorded as direct traffic instead.

For example, if an email campaign links to a “Reset Password” article without campaign tagging, the dashboard may show the resulting visits as direct rather than email traffic. Tagging the link makes the campaign’s contribution visible.
What is a referral visit?
A referral visit is traffic from another website that is not a major search engine. It indicates that a visitor reached the Help Center by following a link on an external site.

For example, if a company’s product website, customer portal, or partner site links to a Help Center article, visitors arriving through that link may be counted as referral traffic.
What does total visits mean?
Total visits counts every visit to the Help Center, including repeat visits by the same person.

This metric is useful for measuring overall activity, but it does not represent the number of individual visitors. A customer who returns several times during the selected period contributes multiple visits.
What does pages per visit indicate?
Pages per visit is the average number of Help Center pages viewed during a session. It helps assess whether visitors continue exploring content after arriving.

A higher value can indicate that visitors are navigating through multiple useful articles or sections. It can also indicate that customers need to search through several pages before finding an answer. Interpret this metric alongside time on site, bounce rate, and the purpose of the content.
What does average time on site indicate?
Average time on site measures how long visitors spend on Help Center content during a session.

Longer time can suggest that customers are reading detailed or useful content. It should not automatically be treated as a success metric: a lengthy time on a simple troubleshooting article may indicate that instructions are difficult to follow.

For example, if an article intended to explain a one-minute account update has a high average time on site and a high exit rate, the content may need clearer steps or visuals.
What does percentage of new visits show?
Percentage of new visits shows the proportion of visits made by people who are visiting the Help Center for the first time.

This helps teams understand whether Help Center usage is coming primarily from new visitors or returning users. A rise in new visits after a product launch may indicate that new customers are seeking setup guidance or answers about newly introduced functionality.
What does bounce rate mean for a Help Center?
Bounce rate is the percentage of visitors who leave the Help Center after viewing the landing page without opening another page.

A high bounce rate may indicate that the landing content is not meeting visitors’ needs, is difficult to navigate, or needs better search optimization. It should be investigated rather than treated as conclusive evidence of poor performance.
For example, if many visitors arrive from a search engine at an article but leave immediately, review whether the title, article content, and search terms align with the question that brought them there.

Traffic Sources and Location

What can the Site Traffic by Source report show?
The Site Traffic by Source report identifies how users found the Help Center. Sources can include direct traffic, search engines, email campaigns, social sources, and referring websites.

Each source can show:
  1. Page views
  2. Unique page views
  3. Average time on site
  4. Bounce rate
  5. Exit rate
This information helps teams determine which acquisition channels bring relevant visitors to the Help Center and which sources may need better-targeted links or content.
Can the traffic source report focus on email or referral traffic?
Yes. The report can be toggled to view:
  1. All Traffic
  2. Referral
  3. Email
This is useful when evaluating a specific support campaign or an external site that links to Help Center content.
For example, after a product-status email directs customers to a service-update article, filter to Email traffic to assess whether recipients reached and engaged with that information.
How can traffic-source data improve Help Center content?
Traffic-source data can reveal where customers are finding content and whether they engage after arriving.
Examples include:
  1. A search source producing a high bounce rate may indicate a mismatch between search expectations and article content.
  2. An email campaign producing substantial traffic but little time on site may require a more precise link destination.
  3. A referral site sending visitors to an outdated article may need its link updated.
The dashboard provides the evidence needed to investigate these patterns; teams should then review the related pages and sources before changing content.
What does the Site Traffic by Location report show?
The Site Traffic by Location report uses a map to show where Help Center visitors are located. Hovering over a country displays the number of users who visited at least one Help Center page.

Location data helps organizations understand their audience distribution and identify regions where localized Help Center content may be valuable.
How can location data support language planning?
Use location data to identify countries or regions generating meaningful Help Center activity, then evaluate whether customers in those locations would benefit from translated content.

For example, sustained traffic from Brazil may justify reviewing whether Portuguese (Brazil) articles are available and current. Location alone should not determine language strategy; it should be considered alongside customer needs and the organization’s ability to maintain localized content.

Page Visits

What does the Page Visits dashboard show?
The Page Visits dashboard provides page-level traffic and engagement information for Help Center pages. It includes:
  1. Page views
  2. Unique page views
  3. Average time on site
  4. Bounce rate
  5. Exit rate
This allows teams to identify highly viewed articles, pages that retain attention, and pages from which visitors commonly leave.
What is the difference between page views and unique page views?
Page views count all views received by a Help Center page. Unique page views represent the number of distinct visitors viewing that page.

A page may have more page views than unique page views when the same visitor opens it more than once. Reviewing both metrics provides a clearer picture of overall activity and audience reach.
What does exit rate mean?
Exit rate measures the rate at which visitors leave from a particular Help Center page.

An exit is not inherently negative. A customer may leave after successfully finding the answer they needed. However, a high exit rate combined with a high bounce rate or low time on site can warrant a closer review of the page’s relevance, clarity, and navigation.
How should a highly viewed article be evaluated?
A high view count indicates that the topic attracts significant attention, but it does not by itself confirm that the article is effective.

Review it with related metrics:
  1. High views and long time on site: Customers may find the topic important or the article detailed.
  2. High views and high bounce rate: The page may not match visitor expectations.
  3. High views and high exit rate: The article may be resolving the issue, or it may be a point where customers stop searching without finding further help.
For instance, an article about account access may receive high traffic after a login change. If its bounce rate also rises, the instructions may need to address the exact issues customers are encountering.

Using Analytics Responsibly

Can dashboard data prove that an article solved a customer’s issue?
No, Dashboard metrics show visits and engagement patterns, such as page views, time on site, bounces, and exits. They do not independently confirm whether a customer’s issue was resolved.

Use the dashboard to identify pages requiring attention, then combine the findings with support-ticket trends, search behavior, and customer feedback to make content decisions.
Why should source, page, and engagement metrics be reviewed together?
Individual metrics can be misleading when viewed alone. Reviewing the relationship between source, page behavior, and engagement provides more useful context.

For example, a high bounce rate on an article might look concerning. If the article is reached from a precisely targeted email and customers leave after reading a short confirmation message, that behavior may be expected. If the same article receives broad search traffic with short time on site, its content may need improvement.