Internal URL filters

[#1]

When configuring internal URL filters, does https:// need to be specified? Reason I ask is because the current filter doesn't specify https://, and in the referrers report I'm seeing the domain of the client which should be filtered out and classified as internal.

Example filters:

fakenewsportal.com

www.fakenewscom

Please advice and thanks in advance!

[#2 · Accepted solution]

No, you do not need to specify the protocol. If you want to include all subdomains, you don't even need to include www.

If you wanted to include everything on example.com, all you'd need is example.com and you'd be good.

[#3]

Yeah, double check that the filters are implemented correctly, then wait a day, then look at that day's data. If it's working with that date range, you should be good. Unfortunately there's not much that can be done about the previously collected data.

[#4]

My thought is the current filter isn't working correctly because the filter in place is protocol agnostic. Even with the rule in place, I'm still seeing the domain I'm trying to specify as internal showing in the referring domain report. In the referring domain report, I'm seeing https:// which is why I wanted to try specifying the secure protocol. Good to know it isn't retroactive.

[#5]

Well it only works on data moving forward, not historical data. If internal URL filters were placed after data was collected for the date range you're looking at, they'll still be in the referrer report.

I'd recommend updating your internal URL filters and make sure they're correct, wait a day, then check the referrers report just for that day to verify they're working correctly.

[#6]

Seems odd to me that I'd be seeing it as a referring domain. Any other ideas on removing it from referring domain? It's an internal domain and makes no sense why it'd be classified as referring domain.