Re: Capturing the referring site
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 23387
interpreted = N
texte = Sandra et al, I recommend capturing the referring site for each cart and keeping it in a (separate) referrer database.1) I wouldn't want to put a referrer in a shopping cart because its content's seem very unpredictable to me (i.e.. it can be some freaky ASCII junk), and I don't want to risk the integrity or consistency of my shopping cart files.2) As for the overhead issues of an extra [showif[lookup]][append][referrer]...., you probably couldn't notice it; WebCat is very fast and efficient with stuff like this. Most of the really big sites have at least this much stuff going on behind the scenes.Steve Stevewa PAt 08:41 PM 2/5/99, you wrote: >A cart # is created when they enter the site, but the file is only >written to disk when an item or header is created for that cart. >Usually, by that time, the [referrer] information is gone. > >It depends on your traffic and database situation on whether or not >creating a cart for each visitor is a performance hit. For one of my >clients, it is. > >>From what I've seen, cookies are about 98% or more reliable. > >It really depends on your situation. > >Regards, > >Sandy > > > >>Hmmm. I have been a little afraid of cookies, since not everyone turns >>them on. But in this case, I'm thinking that the cart file is written >>anyway, so what's one more field? I would only want to to be done when a >>new cart is created. That wouldn't add any overhead, would it? >> >>Sandra L. Pitner wrote: >>> >>> >Any chance that in the future, WebCat might capture the referring page >>> >whenever it creates a new cart, and write it to a field called >>ReferringSite? >>> >>> That's a well-intentioned idea, but it means a disk hit/file for each >>> visitor. Why not set the referrer in a cookie. Then if the shopper is >>> serious enough to store something in a cart, then retrieve the cookie >>> value. >>> >>> Good luck! >>> >>> Sandy >> >>-- >>Gil Poulsen, Webmaster >> >>************************************************************** >>* AltiM@c * Phone: (908) 222-9001 * >>* 111 Mali Drive * FAX: (908) 222-9002 * >>* North Plainfield, NJ * e-mail: help@altimac.com * >>* 07062-2355 * WWW: http://www.altimac.com * >>************************************************************** >> >> > >Steve Rosenbaum steve@pop-art.com http://www.pop-art.com (503) 968-5957
Associated Messages, from the most recent to the oldest:
Sandra et al, I recommend capturing the referring site for each cart and keeping it in a (separate) referrer database.1) I wouldn't want to put a referrer in a shopping cart because its content's seem very unpredictable to me (i.e.. it can be some freaky ASCII junk), and I don't want to risk the integrity or consistency of my shopping cart files.2) As for the overhead issues of an extra [showif
[lookup]]
[append][referrer]...., you probably couldn't notice it; WebCat is very fast and efficient with stuff like this. Most of the really big sites have at least this much stuff going on behind the scenes.Steve Stevewa PAt 08:41 PM 2/5/99, you wrote: >A cart # is created when they enter the site, but the file is only >written to disk when an item or header is created for that cart. >Usually, by that time, the
[referrer] information is gone. > >It depends on your traffic and database situation on whether or not >creating a cart for each visitor is a performance hit. For one of my >clients, it is. > >>From what I've seen, cookies are about 98% or more reliable. > >It really depends on your situation. > >Regards, > >Sandy > > > >>Hmmm. I have been a little afraid of cookies, since not everyone turns >>them on. But in this case, I'm thinking that the cart file is written >>anyway, so what's one more field? I would only want to to be done when a >>new cart is created. That wouldn't add any overhead, would it? >> >>Sandra L. Pitner wrote: >>> >>> >Any chance that in the future, WebCat might capture the referring page >>> >whenever it creates a new cart, and write it to a field called >>ReferringSite? >>> >>> That's a well-intentioned idea, but it means a disk hit/file for each >>> visitor. Why not set the referrer in a cookie. Then if the shopper is >>> serious enough to store something in a cart, then retrieve the cookie >>> value. >>> >>> Good luck! >>> >>> Sandy >> >>-- >>Gil Poulsen, Webmaster >> >>************************************************************** >>* AltiM@c * Phone: (908) 222-9001 * >>* 111 Mali Drive * FAX: (908) 222-9002 * >>* North Plainfield, NJ * e-mail: help@altimac.com * >>* 07062-2355 * WWW: http://www.altimac.com * >>************************************************************** >> >> > >Steve Rosenbaum steve@pop-art.com http://www.pop-art.com (503) 968-5957
Steve Rosenbaum
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:
Virtual Postcard almost complete... (1998)
[WebDNA] Processor usage off the charts (2008)
WebCatalog can't find database (1997)
Tea Room trouble (1997)
Updating fields from different platforms (1998)
[WebDNA] [OT] WebDNA Wiki - need grammar check / suggestions (2009)
searching with if/then (2004)
2nd WebCatalog2 Feature Request (1996)
PROBLEMS WITH PROTECT TAG (2004)
Running 2 two WebCatalog.acgi's (1996)
PHP Live (2005)
user selectable sort order (2000)
Trouble with Showif and Search (1998)
remove line item (2000)
Verifying and adding new users (1997)
international time (1997)
Requird Fields Error Message (2000)
Daze to Dates (1998)
Scientific notation to number, a solution? (2001)
Enhanced Master Counter? (1997)