{"id":24,"date":"2011-11-03T03:45:09","date_gmt":"2011-11-03T03:45:09","guid":{"rendered":"http:\/\/digitaldatatactics.com\/?p=24"},"modified":"2015-08-22T16:06:42","modified_gmt":"2015-08-22T16:06:42","slug":"gapages","status":"publish","type":"post","link":"https:\/\/www.digitaldatatactics.com\/index.php\/2011\/11\/03\/gapages\/","title":{"rendered":"Using Google Analytics Settings to Properly Identify Pages"},"content":{"rendered":"

This year, I\u2019ve been involved in many Google Analytics implementations and audits, and there has been a recurring theme around misunderstood GA Configuration Settings, mostly regarding how a page is identified. For instance, one recent client of mine had a 350-page site. But because of missed configuration settings, those 350 pages were showing up as literally 28000 URIs! Can you imagine pulling a report on any given page of that site? So to clear the air and hopefully save some GA users out there from future headaches, here are 3 quick ways to use GA Configuration to properly identify your pages:<\/span><\/p>\n

1. DEFAULT PAGE DOES NOT MEAN \u201cMY DEFAULTIEST PAGE\u201d<\/b><\/h3>\n

The default page setting is used whenever a page URI ends in a trailing slash without specifying a file name- for instance, if you used this setting to specify that \u201cindex.html\u201d is your default file name, <\/span>\u201cexample.com\/\u201d<\/span>and <\/span>\u201cexample.com\/index.html\u201d <\/span>would merge into just <\/span>\u201cexample.com\/index.html\u201d <\/span>in your content report, making analysis on that single page much easier.<\/span><\/p>\n

Unfortunately, the name of the setting is misleading and tempts people into entering what they consider the \u201cdefault page\u201d of their site: their home page. But if you enter <\/span>\u201chttp:\/\/www.example.com\/index.html\u201d <\/span>as your default page, the real result would be that any page that ends in a trailing slash will have the full home page URL appended to it:<\/span><\/p>\n

www.example.com\/folder\/<\/span><\/pre>\n
would become this in the reports:<\/span><\/p>\n
www.example.com\/folder\/http:\/\/www.example.com\/index.html<\/span><\/pre>\n
This is obviously not desirable, so please do not put your full home page URL as your \u201cDefault Page\u201d. If you have a site that sometimes uses index.html or index.php, then you may want to specify THAT as your default page, so all pages with a trailing slash would consistently have index.html appended to them. Otherwise, leave the setting blank.<\/span><\/p>\n
2. SO WHAT DO I DO ABOUT THOSE TRAILING SLASHES?<\/b><\/h3>\n
The default page setting cannot be used for what most people WANT to use it for- to standardize whether or not a page ends with a trailing slash. If you give in to the temptation to simply put a \u201c\/\u201d in this setting, then \u201c<\/span>folder\/\u201d<\/span> and \u201c<\/span>folder\u201d<\/span> wouldn\u2019t merge together as desired- rather, <\/span>\u201cfolder\/\u201d <\/span>would become <\/span>\u201cfolder\/\/\u201d, <\/span>and <\/span>\u201cfolder\u201d<\/span>would stay the same (remember, the setting only looks at which pages have a trailing slash, then appends the setting value to it).<\/span><\/p>\n
If you would like to have all trailing slashes removed as the standard, so that <\/span>example.com\/folder\/ <\/span>and <\/span>example.com\/folder <\/span>would appear as the same line item in the Content report- and who wouldn\u2019t want that?- you will need to set up a custom filter that removes all trailing slashes:<\/span><\/p>\n
\"GApages\"<\/a><\/p>\n
Field A -> Extract A should be set to “^\/(.*?)\/+$”<\/span>
\n<\/span>Output To -> Constructor should be set to “\/$A1”<\/span><\/p>\n
Please note, much to my chagrin, such a filter would prevent your profile from being eligible for the not-filter-friendly Real Time Analytics(for now), but I promise this isn\u2019t as big a deal as you might think it is, though I\u2019ll save my reasoning for the unimportance of \u201creal time\u201d analytics for another blog post.<\/span><\/p>\n
3. EXCLUDE PARAMETERS!<\/b><\/h3>\n
Most GA implementations I\u2019ve seen have at least a few query string parameters excluded, but I don\u2019t think I\u2019ve seen anyone get it \u201cjust right\u201d yet (admittedly, my level of nitpickiness may be a tad unrealistic). The problem with not excluding all non-content-identifying parameters is that parameters will cause one page to show up as separate items in the content report. For instance, if I want to report on how many page views<\/span>promotions\/springlanding.html<\/span> got, I might need to pull the following 3 pages:<\/span><\/p>\n
promotions\/springlanding.html<\/span><\/pre>\n
promotions\/springlanding.html?secured=true<\/span><\/pre>\n
AND<\/span><\/p>\n
promotions\/springlanding.html?type=4<\/span><\/pre>\n
Into my reports, to report on only one piece of content. This isn\u2019t the end of the world; using filters in my reports I can usually get the info I need, though it does make trending harder. But it\u2019s such an easy fix!<\/span><\/p>\n
To see which query parameters might have escaped your settings, go to your Top Content report and do a search for \u201c?\u201d. If there are a variety of those pernicious params in there, you may want to use an advanced filter to filter them out one at a time, to be sure you\u2019ve got them all. Now you have a handy list of parameters you can take to your configuration settings for exclusion. If you want to track one of the parameters, but not necessarily in your content report, don\u2019t forget you can always use a Profile Filter if you want to extract a query parameter and put it into another field, like a user defined variable, or just clean up parameters in general.<\/span><\/p>\n
Be careful to not exclude parameters that actually have importance in identifying content. For instance, a products page may have a <\/span>?sku=12345 <\/span>that specifies which product is being viewed- this is a rather critical piece of information for some types of analysis, and should not be excluded.<\/span><\/p>\n
Please be aware that users can add whatever parameters they want to your URLs, so you will never have full control here. Tools like Google Translate like to wreak havoc on URIs, but generally account for a very small percentage of page views.<\/span><\/p>\n
Cleaning up your Content Report is an easy quickwin- it doesn\u2019t take a lot of effort and can make analysis much easier. For questions about identifying content in Google or SiteCatalyst, contact me on twitter- <\/span>@Jenn_Kunz<\/span><\/a>.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"
This year, I\u2019ve been involved in many Google Analytics implementations and audits, and there has been a recurring theme around misunderstood GA Configuration Settings, mostly regarding how a page is identified. For instance, one recent client of mine had a 350-page site. But because of missed configuration settings, those 350 pages were showing up as … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,17],"tags":[11,10],"_links":{"self":[{"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/posts\/24"}],"collection":[{"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/comments?post=24"}],"version-history":[{"count":1,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/posts\/24\/revisions"}],"predecessor-version":[{"id":26,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/posts\/24\/revisions\/26"}],"wp:attachment":[{"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/media?parent=24"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/categories?post=24"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.digitaldatatactics.com\/index.php\/wp-json\/wp\/v2\/tags?post=24"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}