recently busy fool around, so in a hurry to write some things is not easy, you do not want long, everyone looked easy. There was a time in the United States, not patriotic, but quite love the country, especially be strangers to each other to meet people smile on you say hello how are you, with a warm feeling in a foreign country. Well, I was somewhat reluctant to leave.
today temporarily and then the last report on the topic to talk about, but the beginning of a new topic, talk about the implementation of monitoring site analysis, because recently also in the study in this field, brought back some memories, think of those who have made their implementation just starting site analysis of the errors, it is time to sort out. Originally prepared an article on it, the results of a written, found that it is not so simple, so they have to open the next part.
website analysis is able to achieve analysis, access to web site visitors behavior data. But I’ve never met a situation where you’ve got all the data you need to analyze in 100% place. Believe me, no, never, no matter who are unable to do so, because some things are good, you can’t expect to advance in one hundred percent the data you need.
, however, this does not mean that you should give up on the pursuit of a more comprehensive and accurate data, Napoleon also cannot always expect that he will face all combat details, but no time he isn’t the best prepared beforehand. Ever-victorious general analysis is also the site of you, so you need to do the best in advance, or is likely to suffer a big station in the website analysis above.
therefore, it is undeniable that monitoring of site analysis is extremely important and even more important than how it is performed.
below, I’d like to talk about some of the pitfalls I’ve often encountered in the implementation of web analytics, some of which may be commonplace, but very valuable for beginners. Please note that each of the following can be used as a scan list for monitoring the site before the implementation. At the end of this series, I will also make a list of site implementation preparations. In addition, I sum up is certainly not comprehensive, I hope you can continue to add in the comment box, thank you!
trap 1: cross domain monitoring of
this is the website analysis, implementation of the most likely to forget the problem, I did the first time, completely do not know such a thing, and now think of it was very silly.
cross domain monitoring is a problem for Google Analytics, and Omniture does not have this concern (of course, it does have something else similar to the domain). For Google Analytics, if you want to put different fields (domain) or all the monitoring results of Zi Yu (sub-domain) in one >