• Google In-Page Analytics – No Pageviews Recorded for this Page

    20th October 2010

    A number of people have now asked for our advice on an error message that they’ve been receiving when trying to use the new In-Page Analytics feature, launched recently in Beta within Google Analytics.

    The error: “There are no pageviews recorded for this page. Try adjusting the date range or select an alternate page.”

    Some have even mentioned that the new feature works on some profiles within their Google Analytics account, but not on all. Trawling the Internet also reveals quite a few others have the same issue but aren’t yet sure what the cause is or how to fix.

    After experiencing this very issue ourselves, and successfully fixing, we decided to post some information.

    So, what’s causing the error message?
    From the testing we’ve carried out so far, the error only seems to appear on accounts where URI filters have been applied at the profile level of the account within Google Analytics. Having questioned those who’ve asked for our advice, we can confirm this to be a common scenario among them. Where the In-Page Analytics tool works, there are no URI filters on the profile and yes, you’ve guessed, where the In-Page Analytics feature doesn’t work, URI filters do exist.

    URI Filters? What are they?
    If not implemented by you, then perhaps your site builder or marketing people have implemented the filter. The particular filter we’ve found to be causing the issue, is that used to append the hostname to the file name of the page. If your homepage was index.php, then it would appear as index.php in Google Analytics reports. This is OK if you only have one index.php file.

    However, websites with more than one sub domain can sometimes have two index.php pages (one per sub domain). Multiple sub domains can also result in confusing reports within Google Analytics because it isn’t clear exactly which sub domain each page belongs to.

    Using profile filters, it is possible to append the Hostname variable to the URI variable, making your analytics reports much clearer to view. This is a fairly common filter, in our experience, on sites with multiple sub domains (eCommerce sites being a good example).

    How to get around this then?
    There are a couple of ways to get around this error message to allow you to use the In-Page Analytics feature:

    1. Removing the URI filter should allow the In-Page Analytics feature to work correctly. However, it will result in the hostname being removed from page names within your analytic reports. Google will view the hostname and the non-hostname versions of each page as separate pages. This is something you’ll need to keep in mind when doing historical analysis. The In-Page tool will only show data for page names with no hostname appended.
    2. In our opinion the best option is to create a new profile based on your regular profile. This can be done by selecting Add New Profile on the Analytics Overview page. Select “Add a profile for an existing domain”, give it a name, then press continue. This new profile won’t include any Goals or Filters you may have added in previous profiles and it won’t include any historic data. It should allow you to view the new In-Page Analytics feature, but only once it has started recording traffic data.

    You will have noticed that the new feature within Analytics is still in Beta, so while you may encounter some issues, there is a chance that Google will fix prior to full non-beta launch.

    If you’d like any more advice on your Web Analytics implementation and setup, feel free to get in touch.