Find out where your service content isn’t working using web analytics
A service is something that helps someone to do something. If a service has a website, finding the pages or screens that are prompting people to ask for help means you can plan what content to improve.
Improving your content, giving your users the information they need, when they need it, means users won’t contact you to ask questions. They won’t need to fill in that enquiry form, send you that email or contact you by phone. You will avoid failure demand.
Showing how you’re improving content and reducing failure demand is a great way of showing the value of content design.
Here’s how you can do it in Google Analytics 4 (GA4).
What you need to measure
Sometimes, web analytics can tell you how confusing your content is. You can find out which pages are prompting people to ask for help.
Here’s an example for a charity grant programme. People find out if they’re eligible and decide if they’re going to apply. Let’s focus on 3 pages:
- Eligibility criteria,
- Frequently asked questions,
- Contact us (for help).
The pattern of traffic looks like this:
- ‘Eligibility criteria’ is referring 10 pageviews to ‘contact us’,
- ‘Frequently asked questions’ is referring 100 pageviews to ‘contact us’.
The ‘Frequently asked questions’ (FAQ) page is referring a lot more traffic to the ‘contact us’ page. Looks like that FAQ page is confusing people!
Show the value of content design
When you start measuring the pattern of traffic, you can find pain points and fix them. And the good thing is this method works for 3 pages or for 3,000 pages.
Keep a log of when you improve content to make it easier to understand and reduce failure demand. Keep ‘before’ and ‘after’ versions of your content.
Page referrals can be tracked over time. Showing how you’re reducing ‘contact us’ page referrals is a great way to show stakeholders the value of content design.
How to measure the pattern of traffic
If you’ve never done this before, don’t worry! We’ll show you every step.
You can either:
- watch our video showing how to build the report (YouTube)
- read the instructions below
In GA4, pageviews are called events.
Pageview events are created when a tracked user looks at a page.
The ‘referrer’ dimension of each page view tells you where that user came from. It’s the page they were looking at before that pageview event was created.
The finished report looks like this:
1. Go to ‘Explore’ and choose ‘blank’
2. Add dimensions and metrics
3. Set up your rows
4. Set values and cell type
5. Add filters
The value for ‘Page path + query string’ may be different for your website. In this example it’s ‘/contact-us’.
What trends are you noticing in your data?
Now that you’ve set up your report in GA4, what trends are you noticing?
If there are service pages that consistently prompt users to contact you, you can:
- review the page with colleagues who handle these enquiries to work out how you can improve it,
- use a simple highlighter test with users to see what they find clear and what they find confusing,
- audit the content and language to see if something could be simplified or explained in a clearer way.
Read more about content maintenance and let us know how you get on by emailing jack.garfinkel@contentdesign.london