Re: [WebDNA] Page close data

This WebDNA talk-list message is from

2014


It keeps the original formatting.
numero = 111437
interpreted = N
texte = I have built several tracking systems for clients over the years, but I don't recall if I ever built one that tries to track the amount of time a visitor stays on each page. I'm not even sure this makes sense any more, at least with the way I typically visit a site ... I find myself frequently opening a bunch of pages, each in a new tab, so that they are already loaded and available when I'm ready to look at them. If your "time on page" tracking system were used with me, it would appear that I spent a second or two on each page except the last one. There's a problem with timing the last page as well ... You cannot determine when the user leaves the 'last page' of your site for another site unless two things happen: 1- Rather than just closing the tab like I normally do when I leave a site, the visitor must click a special link that sends him/her to a "leave the site" webdna page. 2- Your "leave the site" webdna page must records the click time, then redirect to the other site. Even if these two requirements were met, leaving tabs open for hours while doing something else before leaving the site would create wildly inaccurate data. Having said all this, I should also mention that Google Analytics is easy to setup and your client will probably be much happier with this data than anything you could create in webdna. Obviously webdna has its place, but sometimes it makes sense to use better and free existing tools. Not always, but sometimes. :) Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Management On 07/05/2014 09:53 PM, Steve Braun wrote: > Hi All, > I'm building some minor page analytics for a customer. > I'm just subtracting the time when moving from page to page to > capture the 'time-on-page' data. > I also want to be able to find the time (ie [time]) when the user > leaves the web site for a new domain, or the 'time-on-last-page' data. > > Has anyone done anything like this with WebDNA before? > > Thanks for any suggestions. > sfb > --------------------------------------------------------- This > message is sent to you because you are subscribed to the mailing > list . To unsubscribe, E-mail to: archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > support@webdna.us Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Page close data (Tom Duke 2014)
  2. Re: [WebDNA] Page close data (Stuart Tremain 2014)
  3. RE: [WebDNA] Page close data (Marc Thompson 2014)
  4. Re: [WebDNA] Page close data (Steve Braun 2014)
  5. Re: [WebDNA] Page close data (Kenneth Grome 2014)
  6. [WebDNA] Page close data (Steve Braun 2014)
I have built several tracking systems for clients over the years, but I don't recall if I ever built one that tries to track the amount of time a visitor stays on each page. I'm not even sure this makes sense any more, at least with the way I typically visit a site ... I find myself frequently opening a bunch of pages, each in a new tab, so that they are already loaded and available when I'm ready to look at them. If your "time on page" tracking system were used with me, it would appear that I spent a second or two on each page except the last one. There's a problem with timing the last page as well ... You cannot determine when the user leaves the 'last page' of your site for another site unless two things happen: 1- Rather than just closing the tab like I normally do when I leave a site, the visitor must click a special link that sends him/her to a "leave the site" webdna page. 2- Your "leave the site" webdna page must records the click time, then redirect to the other site. Even if these two requirements were met, leaving tabs open for hours while doing something else before leaving the site would create wildly inaccurate data. Having said all this, I should also mention that Google Analytics is easy to setup and your client will probably be much happier with this data than anything you could create in webdna. Obviously webdna has its place, but sometimes it makes sense to use better and free existing tools. Not always, but sometimes. :) Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Management On 07/05/2014 09:53 PM, Steve Braun wrote: > Hi All, > I'm building some minor page analytics for a customer. > I'm just subtracting the time when moving from page to page to > capture the 'time-on-page' data. > I also want to be able to find the time (ie [time]) when the user > leaves the web site for a new domain, or the 'time-on-last-page' data. > > Has anyone done anything like this with WebDNA before? > > Thanks for any suggestions. > sfb > --------------------------------------------------------- This > message is sent to you because you are subscribed to the mailing > list . To unsubscribe, E-mail to: archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > support@webdna.us Kenneth Grome

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

RE: Credit card processing - UK (1997) [Sum] function? (1997) Quickie question on the email templates (1997) using cookies to prevent access (2000) WebCatalog f2 Installation (1997) [TaxableTotal] - not working with AOL and IE (1997) RE: Formulas.db + Users.db (1997) Problems with store (1998) [CART] (1997) Server crashes and triggers . . . are they linked? (2001) Solaris + WebCat (2001) Using Applescript to process WebCatalog functions (1998) upgrade? (1997) Uh...can someone help me out with the b10? (1997) Search in 2 or more catalogs (1997) uploads (2000) RE: Loss in form (1998) Forms Search Questions (1997) Question... [OT] (2002) RAM issue (2006)