Agile Analytics: A Master Guide to Implementation/
October 10, 2017
In setting up Google Analytics (GA) implementations, we find that we need to integrate the work we do with the clients’ existing workflows and project management approaches. Typically, [from the client’s perspective] our implementations more of a “Waterfall” approach; we take on the implementation directly.
- The development team places Google Tag Manager (GTM) on the website
- We then set up comprehensive web tracking to the client’s specifications.
- We turn the ‘keys’ to the implementation over to the client
- We show the client how best to report on the data.
However, there are other situations that come up. Perhaps the client’s development team needs to be more closely involved. Sometimes stakeholders need to know the project is clearly moving forward or multiple teams need to be involved. In these cases, a more open approach to Google Analytics is called for; breaking down the implementation into smaller components and pushing focus from a “turn-key” solution to iterative releases of a minimal viable product.
The following is an Agile-like framework outlining a typically Google Analytics implementation. When we say agile, we mean that the process outlined below provides incremental steps toward comprehensive tracking within Google Analytics. Each component of this outline will build on the other – achieving the minimum viable product.
Not everyone has the time or resources to dedicate to a massive overhaul, so this process allows you to have a strategy and continually make improvements. You may not need everything listed, but Google Analytics implementations work well when they build off each other. Implement one component, validate that it was done correctly, then move on to the next one.
Overall, there will be two pieces to this methodology:
- The Components – the singular objectives that build upon one another that together furnish a complete GA tracking solution.
- The Process – the actual method that will bring each component to fruition.
The process is where the action takes place. You can visualize this as the spokes on a gear through which each component will pass through. Each component would be subjected to the following process phases:
Discussion – Meeting to discuss a component’s status across the various aspects of the project, accounting for any dependencies – whether working synchronously or asynchronously with other components.
Instruction – Provide guidance and action item assignments based component discussion. This can appear in the form of specific documentation or code requirements.
Execution – Action items determined will be performed alongside support from any necessary parties.
Confirmation – Once the prescribed actions are taken, each action will be reviewed for quality of execution.
Verification – Overall, verify the output of the component, insuring the outcome is as expected and meets specifications.
Each process phase may be repeated in each cycle as deemed necessary. For example, more discussion and instruction may be necessary following a round of verification.
These components are strategic in nature and inform the lesser implementation components. For example, prior to Google Analytics is implemented, a larger data collection strategy should be decided. The Analytics Strategy component would first undergo the process phases. The discussion and instruction phases would first happen. Then, in the Master Component’s execution phase, the “nested” processes and components would begin. Here are some suggested Master Components:
Observing the web property and deciding the interaction(s) that best align with the company’s business objectives and how to best measure them.
Each ecommerce data collection component is dependent on the other. A master component ensures each part will work in concert with the other.
The following components can flex given a client’s needs, but the objectives outlined here will provide a solid platform for which to build a solid plan. Some of these items are dependent on one another, but some can be developed in tandem. Here are the components:
Implementing The Tracking
While all of this involves some form of implementation, there are some basics to learning how to make changes to your site. Your site may be different from others, so the process of setting up tracking should inevitably help setting up future tracking. Hacks and shortcuts in this phase may cause trouble down the line. Take the time to do things correctly, knowing that these are building blocks on which other steps rely.
Tag Manager Implementation
Ensure Google Tag Manager (GTM) is properly configured to implement tracking across the sites.
Set up pageview tracking as a baseline in Google Analytics.
General Event Tracking
Implement best practice and site-wide event tracking.
Create custom dimensions and apply additional code where necessary.
Interface and Configuration Settings
There are changes and setup necessary inside of the Google Analytics interface that will help keep your tracked data clean and organized, easily accessible, and clear to all stakeholders.
Configuration Best Practices
Configure baseline analytics properties according to best practices.
Basic Filter Setup
Learn and understand why we use filters, how to set them up, and implement necessary ones.
Site Search Tracking
Developing an implementation to measure search usage.
Make segments informed by best practices as well as client direction.
One of the most important features, use Goals to track conversions on your site.
Enhanced Ecommerce Tracking
Ecommerce comes in many flavors, at this time, we recommend everyone begin using Enhanced Ecommerce. You don’t need to do everything at once, you can tackle the important stuff first, and then iterate through the extra features.
Enhanced Ecommerce: Transactions
Establish accurate transaction data collection in GA.
Enhanced Ecommerce: Checkout Steps
Establish the checkout steps portion of Enhanced Ecommerce.
Enhanced Ecommerce: Product Views
Track product clicks and views inside Google Analytics.
Enhanced Ecommerce: Cart Actions
Record add to cart actions within Google Analytics.
Enhanced Ecommerce: Internal Promotions
Track internal promotions within the site.
Outside of these baseline components, there may be bigger picture items that can be addressed once the overall Master Components are fulfilled. The same processes could apply to these on the whole, but even these components could be further broken down into more nuclear parts.
Create reports that satisfy any identified stakeholders.
Leverage eCommerce tracking to create insightful reports.
Work on integrating with a CRM database with GA and possibly BigQuery.
GA 360/Advertiser Integrations
Take advantage of potential advertising integrations and other GA 360 features available.
The Big Picture
Looking to the big picture is key. It’s important to constantly reassess how the implementation components align with the Master ones.
Communication is Crucial
When working across multiple teams and organizations, this is essential to any success. Have clearly established protocols for exchanging ideas and brining up issues.
Overall, this agile approach keeps stakeholders in the loop, allows relatively fast results and is one of many ways we can work toward the larger goal.