Name: tsd-ga-framework
Owner: U.S. General Services Administration
Description: Technology Solutions Division's (TSD) Google Analytics Framework for all digital services
Created: 2015-08-04 14:14:02.0
Updated: 2016-01-05 08:00:32.0
Pushed: 2015-08-17 21:21:34.0
Size: 324
Language: null
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
This repository documents the GSA IT Technology Solutions Division's (TSD) Google Analytics Framework for all digital services.
Due to the ever evolving nature of digital services, this framework will be updated from time to time to incorporate the latest standards to better support the use of Google Analytics.
All Digital Services that are developed or maintained by the TSD division will leverage Google Analytics from the beginning. This is a firm requirement and should be included in the requirements of all projects. This means that each project must understand how this framework affects them and make the appropriate preparations to ensure that once deployed, the digital service is integrated with Google Analytics.
As our division matures in it's usage of Google Analytics, we have noticed how quickly management of the Google Analytics accounts get out of hand. In order to better manage this, we provide the following rules based upon guidance from Google:
Modern web applications blur the line between web pages and web applications. At a bare minimum, every “page” or unique URL must include the appropriate Google Analytics Tracking framework or code. This is an important concept as not adhering to this will cause “holes” in your analytics which could lead to poor business decisions.
Google Analytics tracks webpages in a standard way. However, the TSD division supports multiple web development technologies like; AngularJS, struts II, Django, Drupal, and Coldfusion. Each technology serves content in a different way, which may not lend itself to the standard way that Google Analytics tracks. In order to help teams worry less about customizing their Google Analytics implementation to work for their application, the TSD division has standardized various Google Analytics 3rd party and open source frameworks that should be used.
When leveraging Drupal for your digital service, you should be using the standard Drupal Google Analytics Module.
AngularJS is a phenominal web application framework that obscures the lines between traditional websites and web-applications. Encapsulating everything into API requests, It can deliver an entire web application in a single web page. This provides phenomenal value to the users, but can create challenges when attempting to track what users are using.
To combat this, your application should use Angulartics or Angularytics.
The United States Digital Service (USDS) Digital Analytics Program (DAP) has standardized their implementation of Google Analytics using Google Analytics on Steroids (GAS). If the other frameworks do not apply, the GAS framework should be used.
In support of the USDS DAP program, all TSD digital services should be implementing the USDS DAP tracking code on all websites. This is an additional tracking code in support of the DAP program.
NOTE: DAP does note replace the TSD Division Google Analytics
All digital services should be configured to track the following events using Event Tracking:
Referrer spam occurs when your website gets fake referral traffic from spam bots and this fake traffic is recorded by your Google Analytics. There is no silver bullet for stopping referral spamming and therefore, as part of the TSD Google Analytics Framework, we provide some basic configuration changes as well as a Standard Operating Procedure (SOP) for detecting and blocking referral spam.
All Production views should be configured to use Google Analytics Bot Filtering. This can be accomplished by going to Admin -> View Settings, clicking the “Exclude all hits from known bots and spiders” checkbox, and saving.
All Google Analytics accounts should have an account level filter for the most basic bot spammers. Thanks to research done by other groups, we have settled upon the list provided by analytics-toolkit.com.
darodar\.|semalt\.|buttons-for.*?website|blackhatworth|ilovevitaly|prodvigator|cenokos\.|ranksonic\.|adcash\.|share.?buttons\.|social.?buttons\.|hulfingtonpost\.|free.*traffic|buy-cheap-online|-seo|seo-|videos-for
The filter should be constructed as shown below:
One of the best ways to prevent spammers is to stop them at the source. When providing a Digital Service using an Apache webserver, this is best accomplished through modifying the root .htaccess file. As part of the TSD Google Analtyics Framework, all Apache based webservers should modify its root .htaccess file and implement the “Ultimate Referral Blacklist”.
References:
Each month, the Google Analytics administrator for the property, should go into the production views standard reporting and run the Acquisition -> Overview -> All Traffic -> Referrals report. If any website exist that are not already in your referrer blacklist or account level filter, they should be added. Please post an issue to this repository, and we will be happy to add your finding to the list!
Unlike direct referral spamming, ghost spamming is where a bot will use your tracking code against you without ever touching your site. Understanding that Google Analytics does not include an authentication protocol, we have determined that the easiest and most effective method of combating ghost spamming is through Hostname Filtering.
By Configuring Hostname filtering on your Google Analytics views, you have a quick and effective way of preventing indirect spammers. Aside from your “All Website Data” view, all views should have a hostname filter setup to only capture hits from the hostname of the Digital Service.