Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Totally Remove "localhost" entries from Google Analytics
-
Hello All,
In Google Analytics I see a bunch of traffic coming from "localhost:4444 / referral".
I had tried once before to create a filter to exclude this traffic source, but obviously I did it wrong since it's still showing up.
Here is the filter I have currently:
Filter Name: Exclude localhost
Filter Type: Custom filter > Exclude
Filter Field: Referral
Filter Pattern: .localhost:4444.
Case Sensitive: NoCan anyone see what I'm doing wrong and give me a push in the right direction?
Thanks in advance!
-
The filter I used a long time ago that worked at the time was a hostname one using (.?localhost.?)
Filter Name: Exclude localhost
Filter Type: Custom filter > Hostname
Filter Pattern: (.?localhost.?)
Case Sensitive: NoNow I block via code so I'm not sure if this still works - feel free to try. Also, I'm not sure why the filter uses both * and ? since the star should be inclusive of ? wildcard but I can no longer find the source.
Good luck
-
Hi Robert,
did you resolve this problem as I have exactly the same thing showing on my analytics too and it is driving me mad?
-
Does anyone have any ideas?
I'm still totally stumped!
-
Does anyone have any ideas?
Having this silly "localhost:4444" entry is skewing all of my numbers and no matter what I try, it won't seem to filter it out.
Any help is very much appreciated!
Thanks!
-
Thanks Mike.
At least I know I'm not alone in being totally & completely baffled!
Hopefully someone else can give me a push in the right direction.
Cheers!
-
I'm sort of baffled, myself. I see no reason why this would be unfilterable. I'm marking this as an unanswered question, hopefully someone comes to our rescue here.
-
Putting the filter pattern of "localhost" did not work... sadly.
I still see "localhost:4444 / referral" in my reports.
There must be a way to filter this out.... I'm sure I'm not the only one with this problem (or at least I hope not!)
Any other ideas?
Thanks in advance.
-
There was no real reason I wasn't just trying localhost.
I just thought we needed some other parameters on there... but clearly those weren't working.
I just updated the filter now and I'll check tomorrow's data to see if the answer was really this simple.
Thanks!
-
Was there any reason you're not trying just
localhost
as the filter pattern? No asterisks, quotes, backslashes or anything?
-
Unfortunately that did not work.
I still see this in my referral reports:
localhost:4444 / referral
Just to confirm, the filter I set is:
Filter Name: Exclude localhost
Filter Type: Custom Filter > Exclude
Filter Field: Referral
Filter Pattern: localhost*
Case Sensitive: NoAny other ideas? I'll try anything.

-
Do you have a update on this? Did it work?
-
If I put localhost then I get a "Regular expression is invalid" error.
I'll put: localhost*
I'll watch it for a couple days and see what happens.
Thanks!
-
1: the "." in front of "*localhost" might break the filter i guess. The same goes for the "." after "4444".
2: Have you tried localhost* or localhost ?
-
Thanks for the link... this is kind of what I had followed earlier, but it still doesn't work.
In my original question you can see the current filter I have setup.
Yet, for some reason this is not blocking what I need since I still see "localhost:4444 / referral" in my reports.
Any other ideas?
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Attribution of conversions to payment gateway in Google Analytics
Hi all, We have been having a problem for a while now where most transactions are attributed to referrals from our payment gateway Sagepay. The issue started a couple of months ago, when we finally upgraded our website to https:// for logged in users and transactions. Before, when we were using http://, transactions were attributed to the correct channel. Even weirder, we upgraded 4 websites and only 2 of them have the issue now, the other two continue to attribute transactions correctly. I added Sagepay to the referral exclusion list which made no difference. Over the weekend, we upgraded to the global site tag and it seems to have improved somewhat, but yesterday 50% of transactions were still attributed to referral/sagepay. I am also seeing an odd issue, where for half of the transactions, the revenue and transaction are attributed to one channel, but the products (quantity) are attributed to another. One of the channels is always referral/sagepay and the other is the channel that the transaction should be attributed to. Has anyone seen this issue before? I'd appreciate any tips that might help us fix this issue. Thanks in advance!
Reporting & Analytics | | ViviCa10 -
Google Analytics: Different stats for date range vs single month?
I've been scratching my head, chin, and you name it over this one. I have an advanced segment to remove bot traffic from my data. When I look at the Audience Overview data for a single month (let's say Aug). I am shown a session count. No problems here, however If I set the date range to (January - August). The august monthly stats is incorrect, much lower. What this means is that, if I export a CSV report from Jan-Aug, the data is wrong compared to individually recording a month. Anyone faced this? I've asked the question over at the Google Analytics technical section as well, but no answer P.S I even used the 'control the number of sessions used to calculate this report' tool but no luck.
Reporting & Analytics | | Bio-RadAbs0 -
Google Analytics shows most referrers as "Direct" -- What are some better tools?
Very often Google Analytics will show 50-90% of our referrers as (direct) which is not very helpful. Are there other tools out there that will provide a clearer breakdown of what other websites are sending us our traffic? Specifically, I want to be able to be able to tell who are the top traffic referrers to my top performing pages on my site for the last 30 days. (I want to be able to study this on a per-page basis.) Thanks in advance!
Reporting & Analytics | | Brand_Psychic0 -
How many users completely block Google Analytics cookies ?
Hello everyone! In your experience, how many of your visitors' browsers completely block cookies including those of Google Analytics ?
Reporting & Analytics | | Masoko-T0 -
Google Analytics - Keywords (not set) or ( not provided) WHY???
In Analytics, most of my visitors are landing on my home page, but when trying to see wich keywords they use, most of them are: (not set) or ( not provided) See screencast: http://screencast.com/t/AKwPW76qLVsN Can you tell why? What is going on? Is there a way to solve this? Thank you, BigBlaze
Reporting & Analytics | | BigBlaze2050 -
How to remove unwanted dynamic parameters from a URL in Google Analytics
Hi, Would really appreciate some help with this. I have been experimenting with RegEx to achieve this but as I’ve never used it before am currently failing miserably. We have conversion pages i need to set goals for that are formatted as below: https://www.domain.co.uk//Application_Form/(S(ewhbqp5cki0mppuzukunkqno))/enterCardDetails.aspx I need to remove the (s(xxx)) section from the URL as rather than one pages i currently have thousands of unique URL's. What’s catching me out is that as it’s not a URL parameter I can’t discount and as half way through can’t just do head matches etc to /entercarddetails Help would be much appreciated. Thanks.
Reporting & Analytics | | Sarbs0 -
Setting up Google Analytics default URL
If someone has set: the default url in Google Analytics to a non-www address (http://mysite.com) then placed the UA tracking script from that GA account within the CMS framework of the website... ... and then set the permanent 301 redirect in the htaccess file to redirect to the www address (http://www.mysite.com). How less accurrate will my GA analytics measurements be considering the default url within GA is non-www and the permanent 301 redirect in htacess is to the www-address? Anyone know how reliable GA reports are until the default url in GA analytics is changed to match what is the redirected url in htaccess file? _Cindy
Reporting & Analytics | | CeCeBar0 -
Google Analytics: Difference Between Goal Conversions & Goal Completions
When using Google Analytics, what is the difference between total goal conversions and total goal completions? We have many goals set up in a lead generation environment. Therefore, the only element of conversion is submitted a lead and arriving on the "Thank You" page. THose thank you pages are tagged accordingly. When we run reports though, the number of "Total Goal Conversions" and "Total Goal Completions" never match up.
Reporting & Analytics | | eMagineSEO0