Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking government versus public traffic #5

Open
eeeschwartz opened this issue Jan 29, 2016 · 1 comment
Open

Tracking government versus public traffic #5

eeeschwartz opened this issue Jan 29, 2016 · 1 comment

Comments

@eeeschwartz
Copy link
Contributor

Curious if this is something you've poked at as part of this project?

In the past I've created different views that include or exclude IP ranges to note government or non-government traffic. But it's a bit clunky duplicating the view configuration.

I'm thinking the ideal would be to store internal/external as a dimension. Then you can query against it like any other dimension. But I'd love to hear your thoughts on the matter!

@laurenancona
Copy link
Owner

After coming full circle on this, I think I now agree - in the past I've been very stingy in giving up custom dimensions, since unpaid accounts are limited to 20 and you want to make sure you never change them if at all possible. Setting up a rule for categorizing as internal or not is probably reasonable. Another option is if you have a custom service provider for city traffic, e.g. most official buildings here show up under standard Reporting>Audience>Technology>Network as city of philadelphia. We then create a custom segment for that, which we can non-destructively overlay or apply singly to any other standard report in GA.

But overall, a custom dimension would also work if you don't otherwise want to deal with reconfiguring filtered views every time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants