SOLVED

Re: Google Analytics location issue

Go to solution
Katie_DenHollan
Level 3

Google Analytics location issue

I'm not entirely sure if this is a Marketo issue, but I have a hunch it is and wondering if anyone else has this issue, and how to solve for it.

We have a disproportionate number of website visitors showing up with Portland, OR as their location - about 1/3 of our total site visitors. I know our account contacts have always been based out of Portland and we use Munchkin tracking on our website, so I'm thinking there is a connection, I just don't know what that is, or how to fix our GA reports from being impacted.

Any ideas?

1 ACCEPTED SOLUTION

Accepted Solutions
Katie_DenHollan
Level 3

Re: Google Analytics location issue

Hi Sanford,

Thank you for all your troubleshooting, but I've figured it out this morning. I cross referenced the Portland Users by "Browser" and it showed all users using the browser "Smarshbot". Smarsh is the compliance software we use to track emails and our website. It crawls our website every day looking for changes, which must be causing this issue.

View solution in original post

11 REPLIES 11
SanfordWhiteman
Level 10 - Community Moderator

Re: Google Analytics location issue

Munchkin doesn't impact the location reported by GA in any way. They're 2 different analytics paths (with different events and session logic) and unless you're tying them together deliberately, they don't share data.

When you call these "disproportionate" what is this based on? Are you sure you don't just have 1/3 of your visits from internal users and need to exempt them? Is the IP address in Portland, OR the IP of your office there?

Katie_DenHollan
Level 3

Re: Google Analytics location issue

Hi Sanford,

In the past week, we have had just over 3000 visitors to our website, and 1,338 came from Portland, OR. The next two highest cities are 500 and 250, both of which we have offices nearby, and a large population of clients.

The closest office we have to Portland, OR is in Wyoming, and we don't have a large number of clients there, so there is nothing I can think of as to why we would have 1/3 of our visitors coming from there. It's also a 99% bounce rate, which is fishy.

SanfordWhiteman
Level 10 - Community Moderator

Re: Google Analytics location issue

The closest office we have to Portland, OR is in Wyoming

OK, then "our account contacts have always been based out of Portland" doesn't really have any bearing, does it?

I can tell you this isn't Munchkin telling GA where the visits are coming from.

What's an example IP address? Sure this isn't a spider or mail scanner?

Katie_DenHollan
Level 3

Re: Google Analytics location issue

Sorry, what I meant by Account contacts is the people at Marketo that we work with have always been based out of Portland, not our personal contacts in our database.

I'm not sure how to access the IP addresses in GA, sorry, not a regular user of that system, I was just brought in because of this weird issue, so I'll need to get back to you on that.

SanfordWhiteman
Level 10 - Community Moderator

Re: Google Analytics location issue

Are the entry pages for these visitors all URLs that appeared in emails this week? If so, it's a mail scanner (which operates as a headless browser).

Katie_DenHollan
Level 3

Re: Google Analytics location issue

It looks like the entry pages are articles we've shared on LinkedIn...

SanfordWhiteman
Level 10 - Community Moderator

Re: Google Analytics location issue

And the IP(s)?

Katie_DenHollan
Level 3

Re: Google Analytics location issue

I'm being told we can't get IP addresses out of GA due to privacy. Is that your experience? Sorry if this is basic knowledge, I don't know anything about google analytics.

Katie_DenHollan
Level 3

Re: Google Analytics location issue

Hi Sanford,

Thank you for all your troubleshooting, but I've figured it out this morning. I cross referenced the Portland Users by "Browser" and it showed all users using the browser "Smarshbot". Smarsh is the compliance software we use to track emails and our website. It crawls our website every day looking for changes, which must be causing this issue.