Tip: Segmenting visitors by screen resolution in Google Analytics

The problem
I needed to answer this question: How many readers will be affected by the bigger size of the new site design?
Basically, I needed to know how many visitors are using a screen resolution higher or lower than the one I had in mind, which is 1280×800. A high proportion of visitors with a lower resolution than that would mean that I’d better reconsider downsizing the site to, say, a 1024 width, as it’ll impact negatively the usability of the site for them.
Fortunately, Google Analytics has a nice feature that can answer that question as long as you want to deal with regular expressions. And, fortunately again, I’ve done the hard work for you.
The solution

Time to access your Google Analytics account and:
- In My Customizations (the sidebar at left, lower part), click on Advanced Segments.
- Click on +Create a new custom segment (top right area)
- Drag and drop Screen Resolution from the Systems submenu inside Dimensions (at left sidebar) to the dimension or metric grayed out box at right.
- Change the Condition to Matches regular expression.
- In Value insert this: (^12?[0-7]?[0-9]|^1?[0-1]?[0-9]?[0-9]|^[0-9]?[0-9]?[0-9])x
- Type a name for this segment in the Name segment area ( I use: Lower than 1280)
- Click on the Save Segment button.
Now, let’s see this in action:
- For this example, let’s just check the Dashboard, so click on that link in the left sidebar.
- In the top right area of the screen click on Advanced Segments.
- That’ll show a popup with two lists. The one at left has the segments already built in Google Analytics. The one at right will show the one you just created (and any other custom segment of your own). Select it.
- Click the Apply button.
There you have it. Just remember to uncheck All Visits if you only want the stats of that particular segment.
The regular expression
The important part in all the steps listed above is this:
(^12?[0-7]?[0-9]|^1?[0-1]?[0-9]?[0-9]|^[0-9]?[0-9]?[0-9])x
This regular expression is checking only the width of the user’s screen resolution, which is the aspect I was interested in, and should be just enough, in my opinion.
If you’re curious, this is what it does in detail. It checks if:
- ^12?[0-7]?[0-9]: The screen resolution width is somewhere between 1200 and 1279.
- ^1?[0-1]?[0-9]?[0-9]: Or between 1000 and 1199.
- ^[0-9]?[0-9]?[0-9]: Or between 000 and 999.
What about resolutions of 1280 and higher?
This part is way easier once the above segment has been created. Let’s say you want now to know the stats of those visitors with screen resolutions of 1280×800 and higher:
- In the list of your Advanced Segments click on the Copy link in the entry you just created (that link is in the right part of the line)
- Change the Condition to Does not match regular expression.
- Type a name for the segment (I use: 1280 or higher)
- Save the segment.
In my case, that will tell me how many visitors won’t have any problem with the new size of the site design I have in mind.
What about 1024×768?
If you have the same problem, but you’re wondering about screen resolutions of 1024×768, use this regular expression instead:
(^10?[0-2]?[0-3]|^10?[0-1]?[0-9]|^[0-9]?[0-9]?[0-9])x
Again, this only checks the width, not the height, but should be enough for most cases.
Conclusion and acknowledge

Now that I can easily see the amount of visitors with resolutions lower than 1280×800 I know that, taking the last month (November) as an example, they’re about 21,60% of the total visitors, which is a low percentage, as I expected. From those, only 16.24% are returning visitors, compared to the 65.83% of those with higher resolutions. Those percentages are quite similar in past months. It seems the new size won’t be a problem for most of the readers. That said, it’ll still be usable in resolutions as low as 1024×768, as the comic page and the navigation buttons will be centered and will fit perfectly in that resolution (you’ll have an annoying horizontal scrollbar at the bottom, though).
This trick is a personal adaptation of an article I found on Google, which focused on finding visitors who use mobile devices. That link points to the post where I found the information first, but it seems that this info has been copied over and over in other blogs, so I’m not sure if that’s the original source. In any case, thanks to whoever came up with this first.
That’s all. I hope someone finds all this of any use. Oh, and if you’re wondering, the new site design won’t be public until next year, I’m afraid.




7 Comments
White text on yellow backgrounds is too hard to read, a change would be appreciated.
I’m afraid I really don’t know what are you referring to. Are you talking about the design of this site? In that case it must be something related to your browser, as there’s no white text over yellow backgrounds anywhere AFAIK.
I apologize for not being more clear, I have a screenshot if it would help.
It’s not a setting on my side, as I neither changed any colors for anything in my browser, not links, and certainly not the websites yellow background.
To be a little more specific, it’s the first/previous/next/last text that is made very difficult to read as it shows up white by default, on the yellow background of the webpage.
Thank you.
By the way, I really like the comic.
OK, there’s no need for a screenshot now that you described where it happens. What would come in handy is knowing which browser and version you’re using. My bet is Internet Explorer, and probably a version prior to 6, as I already tested that version and it doesn’t show the glitch you describe there. The site also works on any other modern browser almost identically, as long as you’re using their latest versions: IE, firefox, chrome, opera, safari. I always test it in all those when modifying something in this site.
In short, it’s probably a mix of a exotic computer / browser that’s causing your glitch. Knowing what’s your computer device (PC, mac… PS3, iphone…. ), operating system (Windows, MacOs, Linux…) and your browser name and version would be interesting. That doesn’t mean I’d be able to fix it, though.
It’s Firefox 3.5.7 on Windows 7, with Geforce GTX 260 video card.
Nothing exciting or anything, just a fairly basic PC that can play games.
Don’t stress over it or anything, I’m sure you’ve got better things to deal with.
Now, that’s weird. I’m also using Firefox 3.5.7 and I’m not experiencing that problem. I’m using XP SP3, though.
After googling for problems with the latest Firefox in Windows 7 there’s been quite a lot of matches. It seems the Mozilla guys are still trying to make their browser work properly with the latest Windows so, the only solution is just wait and hope for it to be fixed by them soon.
Found it: you’re blocking the ads in this site.
Adblock (which is the extension I guess you’re using) uses to break havok like this. Adding projectwonderful.com or robomeks.com (or, better, both) to your whitelist will fix it.
I also encourage anyone reading this to allow Project Wonderful ads, as 90% of the sites that use them are webcomic authors like me. Displaying ads is the only way I currently have to cut the losses Robomeks creates (yes, I didn’t say lower the profit, I mean stop losing money). So, if you like Robomeks, don’t block their ads. It makes the guys sad. And poor. And unhealthy. So they’ll die. Miserably.