I added bots to the GEO Case Script. Feel free to use it.

Last month I showed you how to fix your GEO in Google Analytics so you can report more accurately. I added a couple of lines to include and rename bots.

Bot traffic is no big deal, unless of course you are paying for them. This is why you should never filter your bots in Google Analytics. Let them run free and check on them every now and then.

Before

After

The above is pulling from the same Google Analytics account.

Here is the case statement:

CASE 
WHEN REGEXP_MATCH(Service Provider,".*verizon.*")AND REGEXP_MATCH(City,".*.*") AND REGEXP_MATCH(Device Category,".*mobi.*")THEN "Verizon Cell Phone"
WHEN REGEXP_MATCH(Service Provider,".*t-mobile.*")AND REGEXP_MATCH(City,".*.*") AND REGEXP_MATCH(Device Category,".*mobi.*")THEN "T-Mobile Cell Phone"
WHEN REGEXP_MATCH(Service Provider,".*at&t.*")AND REGEXP_MATCH(City,".*.*") AND REGEXP_MATCH(Device Category,".*mobi.*")THEN "AT&T Cell Phone"
WHEN REGEXP_MATCH(Service Provider,".*sprint.*")AND REGEXP_MATCH(City,".*.*") AND REGEXP_MATCH(Device Category,".*mobi.*")THEN "Sprint Cell Phone"
WHEN REGEXP_MATCH(Service Provider,".*amazon.*")AND Source="(direct)" THEN "Bot"
WHEN REGEXP_MATCH(Network Domain,".*amazon.*")AND Source="(direct)" THEN "Bot"
ELSE City

END

The reason I required the “direct” source is because I want to catch a bot that comes from all other sources.

I caught 6, but none of them were purchased so it’s all good.

Bots Are Spreading

You will also learn that bots aren’t only from Ashburn, Virginia.

If anyone wants to add coolness to this please let me know.