Rule one in writing: Know your audience. Project analysis begins with building a reader profile. With a proper reader profile, writing to an audience becomes easy. The message is specific, and needs can be anticipated. By using this method, your documentation will increase product value and customer loyalty.
In today’s evolving world, the audience never stays the same. Needs change over time, new types of members emerge with every product release, and technology changes the way audiences expect to interact with documentation. Have you talked to Alexa lately?
Fortunately, with advanced HTML5 outputs that use Google Analytics, technical writers can now use their audiences’ behavior to build better profiles, measure and predict changes in needs, and test the efficiency of documentation. Google Analytics shows visits to documentation through page views, sessions, and bounce rates. Google Event Tracking shows engagement through scrolling text, TOC item clicks, and video plays. When you use Google Analytics and Google Event Tracking together, you can see where your audience is going and what they do when they get there. Having this information will super charge anyone’s documentation.
During this presentation, you will learn:
- The definition of Google Events and how they differ from standard Google analytics.
- How Google Events tracking works and how to incorporate it to your published outputs
- How to read a Google Events report
- How to build a Project Analysis Strategy with Google Events Tracking
After this presentation, you will understand Google Events Tracking and how it benefits a content strategy. You can also develop a solid analytics strategy for upper management and work with an analytical strategy handed to them.