If you’re concerned about part of your page being below the fold, why not check on your suspicions using your site data.
In other words, look for a correlation between your KPIs and the height of the window in which your site is being viewed.
This post is about how to create a custom dimension for the height of the viewing window being used by your visitor. Note: we’re not talking about the full screen height — we’re speaking of the much more useful height of the viewable window area.
The Webtrends SDC tag collects this information in the parameter WT.bs (bs stands for something like Browserwindow Size, I suppose). There is a small problem with WT.bs — values are recorded as a combination of browser width and height, for example “1200x700.”
If we’re interested in only the height, we need just the second part, after the “x“. We can pull out just the height using one of the advanced features of dimension configuration that allows us to extract the part after the x.
Create a new custom dimension definition.
In the General tab:
- Give it a name (Browser Window Height? Viewport Height?)
- Give the report column a name (Height? Browser Window Height? Height in pixels?)
In the Based On tab:
- Value to Base On is “Query Parameter”
- Parameter Name is “WT.bs”
- Click on the “Advanced” button
- Select the Regular Expression radio button and enter this in the regex field. This is how the part after the “x” is pulled out and separated:
In the “When to Collect Data” tab:
- Choose either “first Occurrence in Visit” or “Last Occurrence in Visit” depending on your instincts. (I use First Occurence)
There’s your custom dimension. Use it in a report that has your favorite measures – conversions, or perhaps a measure of success in those items that you think are usually below the fold.
For best results in this kind of report, it’s probably a good idea to filter it to remove mobile devices. Or to include only mobile devices, if that’s your interest. Mobile users seem have different expectations about the fold and seem to be a lot more likely to scroll down. At least, that’s what my instance of this report seems to tell me. Removing mobile users gave me a clearer pattern.
Postscript: If you want to NOT have thousands and thousands of rows, consider collapsing this lengthy table into collections of rows, a.k.a. buckets. We wrote a post on dimension buckets, here.