Location: Enterprise 420a
Review the Calls-to-Action – Gregg Banse
Aggregating Websites in Analytics - Jan Macario/Danny Collier
- Dimensions vs. metrics
- Dimensions are the ‘rows’, metrics are the ‘columns’.
- Dimensions are how you GROUP the data, metrics ARE the data.
- Creating a custom dimension: “Business Unit”
- Determine ‘key’ field. In this case, the hostname is the key. Show data example.
- Admin -> Select Property -> Custom Definitions -> Custom Dimensions -> New custom dimension
- Populating custom dimension data
- must manually edit webpage analytics code
- must be present on all pages
- high potential for oversight/misapplication
- Would need multiple filters (one per business unit)
- Would have to implement all filters correctly on all views
- data import (preferred in this case)
- only have to import once, and will then apply the custom data to all hits
- a new data import would have to be done each time a new subdomain is created, but that’s manageable
- Admin -> Select Property -> Data Import -> New data set -> Custom Data -> Name -> Choose views
- Viewing custom dimension
- secondary dimension in default reports (less ideal)
- custom report: “Business Unit Report”
Common Filters Everyone Should Use - Jan Macario
- Add hostname (subdomain) to request URI (page path)
- In this case, we have multiple websites feeding into the same analytics account. By default, pages with the same path, even if on different websites (subdomains) will be aggregated into a single line-item. By including the hostname in the request URI field, we can disambiguate the data.
- Why not?
- If you had multiple domain names which resolved to the same website: for example, if testwebsite.com and test website.org domain names were really the same website. In this case, you may not want to split the data up by hostname, but instead to aggregate all path data together, regardless of hostname (google analytics default behavior).
- However, in this case, you should probably have two views to do both to see if there were traffic differences between your domain names.
- Review setup on Roll-up view profile
- Lowercase URI
- Generally, page paths are not case-sensitive. “testwebsite.com/page1” is the same page as “testwebsite.com/PAGE1”. In this case, you would not want to arbitrarily split these request URIs into different line-items.
- See example -> Roll-up view -> Behavior -> Site Content -> All Pages -> Date Range -> September 2014 -> Filter: admissions.gmu.edu/[Aa]pply[Nn]ow/(default.asp)?$
- Why not?
- It is possible on some servers (Unix) to have page paths be case-sensitive (i.e. “testwebsite.com/page1” would not be the same page as “testwebsite.com/PAGE1”). In this case, you wouldn’t want to change the case as it would group different pages together incorrectly. This is obviously not a common configuration.
- Exclude internal traffic.
- Review discussion from last week
- Remove querystring parameters (not a filter)
Establishing a new, best-practices view - Danny Collier/Jan Macario
Filter: Include Hostname in Request URI
Filter: Lowercase URI
Filter: Exclude Internal Traffic
Property setting: Remove querystring parameters