HubShout SEM System Help

Referring URL of Hubshout

  • Member 6225 Reply

    On one of my client's accounts, one of the top referring URLs showing up in Google Analytics is reports.hubshout.com.

    This, obviously, is something that the client sees, especially since it's the top referring URL. I think one of the most important parts of successful white-label reselling is a very clear distinction and trust...in this case, I don't know how to explain what Hubshout is.

    All of the referring visits came from Rochester, so clearly a Hubshout employee is just using their own dashboard and clicking through to my client's website. Is this something that should happen?

    06/02/13 at 12:43 AM (7612)
  • Chad Reply

    Thanks for reporting that. More than likely, yes it is someone working on an onsite report, setting up keyword mapping or reviewing the website as part of our monthly AM review. So, it means that someone was working on your client's account which is a good thing. But, let me see if we can do better.

    We've never had anyone report this as an issue in the past 5 years. I raised support ticket 3033374 on your behalf. Let me discuss with Adam to see if there is something we can do here.

    06/02/13 at 01:19 PM (7614)
  • Member 6225 Reply

    Perfect - thanks, Chad! I figured it meant that, but just want to make sure we're careful and all bases are covered. "Someone from Hubshout was just working on your campaign" won't necessarily fly from our end. :-P Thanks for the response!

    06/02/13 at 10:42 PM (7616)
  • Roger Reply

    Hi Chad

    How about a standard page on the sites that allows the HS Employee to be ignored by GA stats. This is way better, because we also don't want to pump up visits either or need to filter HS's visits on all our reports because what wasn't said is how this harms the numbers on their conversion pages too.

    This is the method we use:
    http://www.mcbuzz.com/2011/how-to-exclude-visitors-from-google-analytics/

    So it could be client site e.g. client.com/ga

    So all visitors go to this non-page to get their visit ignored by GA. This could be standardized super easy and taught in a webinar with downloadable features,etc.

    Just a thought.

    Roger

    06/03/13 at 12:02 PM (7658)
  • Clarke Reply

    Or could it be possible to use Google Analytics filtering to block those specific IP addresses.

    https://support.google.com/analytics/answer/1034840?rd=1

    06/04/13 at 03:27 PM (7738)
  • Roger Reply

    Hi Clarke

    That's effective, but this solution is more durable. The reason is your solution requires that all viewers that are internal e.g. HS use static IPs. What about you? Do you check their site via your mobile? From your home? Does the client check from their client sites for information?

    If you do it the way I mentioned then you will sanitize all results that were based on internal (direct or indirect) usage. IPs are great, but very much reliant on the permanency and accuracy of the input.

    Good point though, I just think in this case it wouldn't be the best solution.

    06/04/13 at 06:55 PM (7740)
  • Chad Reply

    Just an update on this thread. I like your ideas Roger but there is no way we could consistently get a file implemented on a client site and in reality it defeats the purpose of what we are doing since we are trying to validate a URL.

    We are going to either 1) remove the referral header info or 2) redirect the request through the reseller portal URL. I'll post an update when we have an update.

    06/05/13 at 06:42 PM (7771)
  • Member 6225 Reply

    Thanks, Chad!

    06/06/13 at 03:35 PM (7809)
  • Terrance Reply

    Chad,

    I had another reseller ask about the referral header and what was the final outcome of this. It's understandably scary to see if their client was to Google our name and find out that they are indeed a Reseller. Thanks. looking forward to the update

    06/13/13 at 10:44 AM (7999)
  • Chad Reply

    Thanks Terrance. Adam is working on a fix in the next day or two. First, people should understand that we have many different people in the company who are actively working on client websites. Our team get tasks to go do work on the client's website (whether that be pulling together research facts or doing an onsite report). They are clicking from that task to the client's website which is then registering that as a referral.

    We understand that isn't desirable but that handshake is a core part of the way that HTTP works. So, we have to dig in deep and find a way around it. It turns out that if you are on a secure page (HTTPS) and you go to a unsecure page HTTP then the referrer is hidden. So, we are going to be building a special hop page for all people logged into the hubshout portal that will go from HTTPS to HTTP and therefore not pass the referrer.

    Adam will be building something in the next few days and then we will do some testing and roll out. I'll post when that is done.

    06/13/13 at 11:25 AM (8002)