According to eMarketer, while most marketers leverage Facebook and Twitter to communicate with customers, not nearly as many consumers comment about these companies and brands on the social sites.
Here are Analytics and Optimization blog posts from last week
There are following three main reasons why your own domain name shows up as the referring domain.
1. If a user waits for 30 min (or whatever your session time out is) before clicking on the next link on your site.
It is a standard practice to use 30 min session time out. This means that if a visitor waits more than 30 mins to click on a link on the website, the click constitutes a new visit.
As in my last post, let’s take an example of visits for one visitor. For this example I am only showing 5 fields (s-ip, data, time, URI stem, cs(referrer) )
Below is the data for a visitor:
The visit started with a referral from http://www.google.com/?q=seattleindian. The referring domain in your web analytics tool will be Google.com
Let’s assume, this visitor goes on a lunch break leaving the site open in her browser. Come back after an hour and clicks on the home page links, here is how the log file will look like as
This constitutes a second visit (I am assuming a 30 min session time out). The referring page will be http://www.seattleindian.com/seattle/advetise.asp and the referring domain will be SeattleIndian.com for this second visit.
If you are a content site that has long articles or have downloads that takes more than 30 mins to complete, chances are you will see your own domain as the number one referring domain.
Taking the same example as above, the log file will look like the following
is no longer there. The log file won’t even contain Google.com as the referrer because the visit did not begin at http://www.seattleindian.com/seattle/default.asp (since it was not tagged or was excluded). In fact, according to the analytics tool, the visit began at /seattle/bollywood.asp and was referred by the non-tagged (or excluded) page, the home page of SeattleIndian.com. In this case /seattle/default.asp, the page which is not tagged will show up as the referrer and the referring domain will be the domain itself SeattleIndian.com
Note: I have seen a lot of unintentional excludes that affect the reporting. It is highly recommended to use a third party accuracy audit to make sure your reports are configured properly. Contact me if you need more details or help with this. We do this all the time.
3. If you have sub domains that have their own reporting profiles or suites (or whatever you call them) they could cause your own site to show up as referring domain.
Let’s take an example of http://www.usaindian.net which has several city-specific subdomains e.g. seattle.usaindian.net, ortland.usaindian.net etc. Any reporting that excludes http://www.usaindian.net home page will show a lot of referrers from its own domain i.e. usaindian.net
Here is the log file of a user who searches seattleIndian on Google and then clicks on the link to seattle support page (http://seattle.usaindian.net/seattle/support/asp) from USAIndian.net home page.
Say you want to create a profile for Seattle area only i.e. exclude everything else and only report on traffic to seattle.usaindian.net domain. If you only include traffic from seattle.usaindian.net (or s-ip of 18.104.22.168 in the example above) in your reports then the referring domain will be http://www.usaindian.net, i.e. your own domain.
I hope this was helpful. This concludes my two part series on Referring domains and pages. As always send me your comments and questions.
Business analysts might be able to learn something from quantum physicists. Consider this great article about a discovery that neutrinos might be able to travel faster than light—a feat thought physically impossible. It is a discovery that questions the most fundamental theories about the way the universe works (talk about promotion material!). But the scientists are not celebrating.
I’ve been proud to call myself a web analyst ever since I realized there was a title for it. It’s an emerging field full of talented people. Frankly, it’s the future of business management, and a web analyst possesses a critical skill set and mentality for any company to have.
I’ve come to realize, however, that I can no longer call myself a web analyst. There are three main reasons for this conclusion. Continue reading “3 Reasons I'm Not a Web Analyst”
Tomorrow’s web analysts will look very different from today’s.
Being a web analyst today usually means being lonely. Most companies don’t hire full-time analysts to work onsite. They hire consulting agencies or they hire a web analyst and make them do SEM work on the side (or vice versa). In the few companies that do hire a full-time analyst, that person ends up being by themselves. That means being lumped into an existing organization that doesn’t make sense (IT, marketing, new media, etc.) and needing to defend analysis and recommendations alone. Continue reading “Future of the Web Analyst”
Career chat has always interested me. When I was a new college grad I spent a fair amount of time in my alma mater’s career services office, getting advice as I prepared to make a start for myself. I’m glad I did it. The career counselors liked me enough to use my resume as an example for other new grads, and I managed to land an internship at a multimedia CD-ROM publishing company (which, back in 1995, was so totally cutting edge).
After more than a decade out in the workforce I feel like I’ve learned a great deal about my strengths, preferences and motivations when it comes to my career. But I also know that career planning didn’t end when I left my college campus – it’s something I must always keep in the back of my mind. I like hearing about how my peers are handling their own career choices, and I think it’s a productive thing for us to talk about with each other.
So I’m planning to write about career-related topics, now and then, in this blog. Before I get started I’d like to acknowledge 4 fellow bloggers who’ve already written some great web analytics career-related material:
- Alex L. Cohen
I appreciate Alex’s enthusiasm – right now he’s doing an interactive marketing tip-a-day for the entire month of November [really, Alex, even on Thanksgiving?]. Occasionally he writes about career-related issues, including this piece on how to write a good web analytics resume.
- Stephane Hamel
As Stephane was contemplating his own impending career move he wrote this very compelling post on the importance of doing regular career self-evaluations. I liked it so much I wound up using it in my presentation on career management at eMetrics. Neither Stephane nor I can fly a kite too well, but luckily that’s not a requirement for our line of work.
- Avinash Kaushik
Oh, what’s not to love. I wouldn’t say Avinash has written about careers, though, so much as he’s written about the flip side of the coin – hiring. I thought this post about whether to hire fresh blood or old hands was especially good, and you can see from the comments that many of his readers turned it around and talked about the issue from the job candidate’s perspective.
- Anil Batra
Anil has compiled a whole collection of interviews with web analysts; as of this writing he’s accumulated 32 career-related posts. I’ve really enjoyed reading the interviews – just to get a sense of who “we” are – but I think they could be equally valuable to someone who’s contemplating an entry into web analytics.
Read what these fine gentlemen have to say, and read my blog, too. I think there’s still more we can and should talk about when it comes to careers in web analytics, and I aim to be a part of that conversation.
Originally posted at: http://june.typepad.com/june/2007/11/web-analytics-c.html