I cannot seem to find any straight and clear documentation explaining the differences between these value types. Hits used to be any call to the server regardless of the file type, but Webtrends only tracks page views, so how is a page view different for a hit? As for visits, I assume that 1 visit can produce multiple page views.
I am seeking enlightenment.
Xv
UPDATE:
This is a screen cap of the results im trying to understand.
Hit - any and every request (image, html, css, js etc...)
PageView - every request to a page (html, aspx, asp, php etc...)
Visit - a session, the duration of someone coming to your website, regardless of the number of page views they have generated
These are fairly generic terms and this usage is accepted in most web tracking lingo.
I don't know about Webtrends, but the lingo normally goes something like this:
Hit: a request to the web server. While this could be a page, it could also be an image, CSS file, etc.
Page view: a request to the web server that is a page.
Visit: a unique page view. (unique as in, from the same IP address or same client). Visits depend on what the time frame for unique is; i.e., visits/month is not the same as adding up all of your visits/day.
Ultimately, Hits in this case are equal to page views.
Hope this helps anyone encountering the same issue with Webtrends.
Related
I have a customize request from my client in sitecore mobile module.
I want to be on full view site from my mobile on Career page, i am able to do it but any of the link inside career page with having mobile layout in presentation detail is taking that page again to mobile device.
Can we make any customization that maintain the device in cookies so that it keep user on full view site after coming to career page.
Is there any setting we can do in pipeline or session. I just want to be throughout in full view site after coming on career page and no going back to mobile layout. Kindly suggest.
Yes, you can do exactly that. You'd need to update the rule to detect the various devices (which I'm guessing you already have). You can then create a custom condition to check if cookies have been set for the full site(does not need to be a cookie of course, but that'd be the easiest way).
You can find the existing Conditions and Actions here in the path /sitecore/system/Settings/Rules.
To create custom conditions and actions, please read the following article on SitecoreInsight.com
After creating your custom condition, go into your device item again and update the Rule there to only switch to that device when that cookie has not been set.
[edit]
Come to think about it, it might be possible to have your 'go to full site' link appended with a querystring sc_device={GUID of device}. I'm not sure what would take precedence here, the 51degrees rules or Sitecore's cookies... Worth a try though :-)
I have a website programmed in Django, and as part of the website, I have a view counter for individual pages. However, since I test-view my own files rather often, I don't want to count views that I give to my own pages.
Right now, all I do is that when a specific page is requested, it simply updates a "views" variable in the model for that page by increasing it by 1. This is okay for my own purposes - I don't mind recording multiple views by the same person - but I simply don't want my own views to count.
What ways are there to do this? Please advise.
You can set a temporary cookie variable in your browser.
For example, in Chrome, you can use the following or the Resources tab on the Web Inspector:
browse to website
In browser URL bar, type: javascript:document.cookie="my_app_who_am_i=itsa_me_mario"
and pull it back using some django:
request.COOKIES.get('my_app_who_am_i')
Or if you had sessions setup already on your web server, you could set the cookie only when your account logs in.
response = render_to_response(template_name, context)
response.set_cookie('my_app_who_am_i', 'itsa_me_mario')
return response
You could use session for it. And when the session is for example, admin(you) then, don't count it.
You can add a cookie like "ignore_view" and if the cookie is present you don't increase the counter.
I have a very simple web page that uses the Facebook Javascript API and is installed as a tab on a Facebook page. When the page is loaded, the only thing it does after calling the usual Facebook init code is to listen to auth.authResponseChange and then show/hide various elements depending on whether the user is logged in or not.
If I load this page, via http or https in an ordinary browser session, everything is fine. The page loads reasonably fast.
But if I load the page tab in Facebook, it hangs for about two minutes. Chrome tells me that this wait is due to 'waiting' for my page. But if I watch the access log, I don't see an access request logged until just before the page displays. So it seems like Facebook is masking what is really going on behind the scenes.
I opened a ticket with Facebook, and they replied that this issue was due to my code and reproducible with any POST that contained a signed_response.
After much head scratching and experimentation, I found that adding the following two lines to the view that handles this page fixed it:
if 'signed_request' in request.POST:
pass
So clearly Django 1.3.1 is holding the HTTP session open until you actually read some POST values. Ouch.
I have a question about how Google Analytics tracks pages in a Wordpress site or any other site that uses a template file to include the code for Google Analytics in the footer or header. Since the file is generated and used in all the pages, that would mean that the analytics code is counting all the pages that are viewed correct? Also, is it possible to view what pages are getting hits and have a more detailed report in Google Analytics? I just have a feeling that the page i'm tracking is displaying inaccurate reports since the same code is used on every page. Can anyone help clear this up and educate me a bit on this topic?
The code is always the same, it loads in the footer so you dont have to put it on every single page.
in the code there is a unique code for your website so analytics knows wich analytics account needs to get the information.
The code dosn't need to be changed everypage.
You can see the pageviews like this:
-->google analytics
--->contents
-->Site content
-->all pages
Now you get a list with urls and the page view for every url
You can sort the list by pageviews (how many times is the page loaded) and unique page views(How many uniqe ip addresses have visited the page.).
You can also find bounce rate wich shows how many % of the users left you site on that page.
As the title implies,
I need to fetch data from certain website which need logins to use.
The login procedure might need cookies, or sessions.
Do I need QtWebkit, or can I get away with just QNetworkAccessManager?
I have no experience at both, and will start learning as I go.
So please save me a bit of time of comparing both ^^
Thank you in advance,
Evan
Edit: Having read some related answers,
I'll add some clarifications:
The website in concern does not have an API. So I will need to scrape web elements for the data myself.
Can I do that with just QNetworkAccessManager?
No, in most cases you don't need a full simulated web browser. In most cases, just performing the same web requests like a web browser would do is enough.
Try to record the web requests in your browser, using a plugin like "HTTP Live Headers" or "Firebug" in Firefox. I think Chrome provides a similar tool out of the box. These tools record the GET and POST requests done by the website when you send a form in the webpage.
Another option is to inspect the HTML code of the login page. Find the <form> tag and its fields. Put them together in a GET / POST request in your application to simulate the same form.
Remember that some pages use randomized "tokens" in their forms, some set the tokens as cookies. In such cases, you need to request the login page itself in your application first (before sending the filled in form). Both QWebView and QNetworkAccessManager have cookie support.
To sum things up, I think QWebView provides a far more elegant way to simulate user interaction with a web page. The manual way is, however, more "lightweight", as you don't need Webkit and your application might be faster (because only the HTML page is loaded, without any linked resources like images, CSS, javascript files).
QWebView as class name states is a view, so it views something (in this case web pages). If you don't need to display loaded page, then you don't need a view. QNetworkAccessManager may do the work, but you need some knowledge about HTTP protocol, and also anything about target site: how does it hande logins, what type of request you have to send to login etc.