### Eclipse Workspace Patch 1.0 #P drupal-contrib-5 Index: modules/google_analytics/README.txt =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/google_analytics/README.txt,v retrieving revision 1.2.4.3 diff -u -r1.2.4.3 README.txt --- modules/google_analytics/README.txt 30 Aug 2007 11:36:00 -0000 1.2.4.3 +++ modules/google_analytics/README.txt 20 May 2008 22:58:01 -0000 @@ -15,15 +15,12 @@ Installation ============ * Copy the 'googleanalytics' module directory in to your Drupal -modules directory as usual. +sites/all/modules directory as usual. Usage ===== -In the settings page enter your Google Analytics User ID. - -You will also need to define what user roles should be tracked. -Simply tick the roles you would like to monitor. +In the settings page enter your Google Analytics account number. You can also track the username and/or user ID who visits each page. This data will be visible in Google Analytics as segmentation data. @@ -34,16 +31,38 @@ HTML footer can confirm this by viewing the page source from your browser. -'admin/' pages are automatically ignored by Google Analytics. +New approach to page tracking in 5.x-1.5 and 6.x-1.1 +==================================================== +With 5.x-1.5 and 6.x-1.1 there are new settings on the settings page at +admin/settings/googleanalytics. The "Page specific tracking" area now +comes with an interface that copies Drupal's block visibility settings. + +The default is set to "Add to every page except the listed pages". By +default the following pages are listed for exclusion: + +admin* +user* +node/add* +node/*/* + +These defaults are changeable by the website administrator or any other +user with 'administer google analytics' permission. + +Like the blocks visibility settings in Drupal core, there is now a +choice for "Add if the following PHP code returns TRUE." Sample PHP snippets +that can be used in this textarea can be found on the handbook page +"Overview-approach to block visibility" at http://drupal.org/node/64135. +A code snippet that creates opt-out by role functionality for unchecked roles +can be found in the Google Analytics handbook at http://drupal.org/node/37694. Advanced Settings ================= -You can include additional JavaScript snippets in the advanced -textarea. These can be found on various blog posts, or on the -official Google Analytics pages. Support is not provided for -any customisations you include. +You can include additional JavaScript snippets in the custom javascript +code textarea. These can be found on the official Google Analytics pages +and a few examples at http://drupal.org/node/248699. Support is not +provided for any customisations you include. -To speed up page loading you may also cache the Analytics urchin.js +To speed up page loading you may also cache the Analytics urchin.js/ga.js file locally. You need to make sure the site file system is in public download mode. \ No newline at end of file Index: modules/google_analytics/UPGRADE.txt =================================================================== RCS file: modules/google_analytics/UPGRADE.txt diff -N modules/google_analytics/UPGRADE.txt --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ modules/google_analytics/UPGRADE.txt 1 Jan 1970 00:00:00 -0000 @@ -0,0 +1,31 @@ +// $Id$ + +UPGRADING +--------- + +WARNING: If you upgraded from Google Analytics 1.3 or before you must +check your "Role specific tracking settings" settings at +admin/settings/googleanalytics. If not set properly Google Analytics +may begin tracking different pages than you intended after upgrading. + +Beginning with Google Analytics 1.4 the logic for when to include the +Google Analytics code on a page has been reversed. In 1.3 and before, +roles were checked in checkboxes to exclude Google Analytics from +counting pages when users with those roles were logged in. Beginning +with 1.4 those same checkboxes are used to include the tracking code +only on pages for the roles checked. + +Beginning with 1.5, if no boxes are checked, the code will be placed on +all pages. With version 1.5 the visibility settings have designed to +mirror Drupal's block visibility settings. + + +Note that with Google Analytics 1.4 you are not able to track pages for +authenticated users who have no specific role set and also exclude +other authenticated users who do have a specific role. Clicking on the +"authenticated user" role checkbox will automatically cause the tracking +code to be written for all logged in users. + +Beginning with Google Analytics 1.5 admins with permission can include +custom php to get the precise tracking they desire that might not be +possible with the available configuration settings.