Designing great dashboards – part 3 now available

Further to my post a few weeks back on Designing great dashboards parts 1 and 2 from Juice Analytics, part 3 is now available.

"The third part of our dashboard design guide provides practical tips for putting information on the page in a way that communicates effectively to your audience…"

To register please visit http://www.juiceanalytics.com/registration/dashboard_design/

Using Google Analytics to Track Email Newsletters (and RSS feeds)

I often get asked how can I see if my email subscribers are looking / reading the newsletter I send out. Google Analytics provides you with an easy and free way of doing this. Today I will take you through the process step by step.

1. You need a Google Analytics account

• Set up a Google Analytics account
• If you don’t have one – all you need is a gmail email address
• Register here http://www.google.com/analytics/
• Place the code in the footer of all your web pages (How do I add tracking code to my website)

2. How does it work?

• Tracking email campaigns in Google Analytics uses a process called link tagging
  – for example the eGovernment Resource Centre Newsletter uses link tagging Eg., http://www.egov.vic.gov.au/newsletters/200809.html would be modified to look like: http://www.egov.vic.gov.au/newsletters/200809.html#?utm_source=newsletter&utm_medium=email&utm_campaign=aug2009news
• When someone lands on your site after clicking on a tagged link from your newsletter (or RSS feed), Google Analytics removes the information from the URL and puts it in a cookie
• This way Google Analytics can now link all that particular visitor’s actions on your site from that email link.
• You can then view the results in the Google Analytics interface

3. How do you make the tags?

Google provides a tool called the URL builder –

 

• Campaign Source (utm_source) – Required. Use utm_source to identify a search engine, newsletter name, or other source.  Example: utm_source=egovnewsletter
• Campaign Medium (utm_medium) – Required. Use utm_medium to identify a medium such as email or cost-per- click.  Example: utm_medium=email
• Campaign Term (utm_term) – Used for paid search. Use utm_term to note the keywords for this ad.  Example: utm_term=government+2.0
• Campaign Content (utm_content) – Used for A/B testing and content-targeted ads. Use utm_content to differentiate ads or links that point to the same URL.  Examples: utm_content=logolink or utm_content=textlink
• Campaign Name (utm_campaign) – Used for keyword analysis. Use utm_campaign to identify a specific product promotion or strategic campaign.  Example: utm_campaign=aug2009news

For example I use the following for the eGov site:

• For email newsletter content : #?utm_source=newsletter&utm_medium=email&utm_campaign=aug2009news
• For RSS feed items : #?utm_source=rssfeed&utm_medium=rss&utm_campaign=rssaug2009
• Why use the # ? This stops the campaign tracking urls being spidered by search engines and appearing in the search results.

4. What do you see in the GA interface?

Your campaign data is listed as ‘Other’ in your Traffic Sources section

For the eGov site this = 12.56% of visits for the month

You can also segment you data and look at what topics visitors arriving via your newsletters look at on the site – but that is a topic for another day.

So that’s how you track visitors to your site who arrive from your email newsletters or RSS news feeds. Have fun and experiment.

Accessibility toolkit version 3 now available

The Victorian Government’s Accessiiblity Toolkit (version 3 – Sept 2009) has now been published on the eGovernment Resource Centre.

The Victorian Government’s Accessibility Standard requires that: All websites must be Level AA compliant (W3C Web Content Accessibility Guidelines, Version 1.0 – WCAG 1.0). However, where audience needs are specific, websites should become Level AAA as appropriate.

This toolkit shows departments and agencies how to conform to this policy and the W3C Web Content Accessibility Guidelines, Version 1.0. The toolkit is designed for Victorian Government business managers and web site owners to enable them to effectively present the business case for accessibility and manage the processes involved.

An HTML version of the toolkit is currently being developed.

At over 270 pages the toolkit provides very detailed guidance on how to make government websites accessible to all visitors.