Re: affiliate marketing program

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 16621
interpreted = N
texte = I just don't like passing to much variables in URLs. If you already are passing an unique [cart] varible you don't have to pass another variable connected to the [cart] - just store it in a db and call it when you need it.>Refferrer's are great, but adcodes are useful for non internet advertising >-- ie ask for the adcode in a form input -- magazine ad etc... > >>>We definitely do not want to have users sign in, so we were thinking that >>>we could give each affiliate an afcode that would be a unique number that >>>can be passed as a variable on every page on our website. We would then >>>build a log of purchases made with the specific [afcode] by adding it as >>>a database field connected to the info related to the purchase. We then >>>can easily pull up sales records related to each [afcode] by doing a fairly >>>simple search. >>> >>>How does this sound? Is it too complicated... is there an easier way? >>>Anyone have any experience with setting this type of system up? >> >>Log the referer along with the cart number in a db and match that db to you >>orders. No need for assigning afcodes and passing them on every page. Associated Messages, from the most recent to the oldest:

    
  1. Re: affiliate marketing program (Jay Van Vark 1998)
  2. Re:affiliate marketing program (Jay Van Vark 1998)
  3. affiliate marketing program (EnviroLink Tech Support 1998)
  4. Re: affiliate marketing program (christer@ljusaideer.se (Christer Olsson) 1998)
  5. Re: affiliate marketing program (christer@ljusaideer.se (Christer Olsson) 1998)
I just don't like passing to much variables in URLs. If you already are passing an unique [cart] varible you don't have to pass another variable connected to the [cart] - just store it in a db and call it when you need it.>Refferrer's are great, but adcodes are useful for non internet advertising >-- ie ask for the adcode in a form input -- magazine ad etc... > >>>We definitely do not want to have users sign in, so we were thinking that >>>we could give each affiliate an afcode that would be a unique number that >>>can be passed as a variable on every page on our website. We would then >>>build a log of purchases made with the specific [afcode] by adding it as >>>a database field connected to the info related to the purchase. We then >>>can easily pull up sales records related to each [afcode] by doing a fairly >>>simple search. >>> >>>How does this sound? Is it too complicated... is there an easier way? >>>Anyone have any experience with setting this type of system up? >> >>Log the referer along with the cart number in a db and match that db to you >>orders. No need for assigning afcodes and passing them on every page. christer@ljusaideer.se (Christer Olsson)

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:

Separate SSL Server (1997) Resume Catalog ? (1997) Help formatting search results w/ table (1997) Listserver problem (1997) Fun with dates (1997) Price characteristics? (1997) Re:no [search] with NT (1997) Dummy Credit Card Number for debug? (1997) A multi-processor savvy WebCatalog? (1997) Realtime shipping suggestions (2007) [WebDNA] Override price in Wd8.5 (2017) Size limit for tmpl editor ? (1997) RE: Credit Card Checksum (1997) Search/sort in URL Was: GuestBook example (1997) Getting Total Quantity (1997) off topic - dna snipets (1997) WebMerchant 1.6 and SHTML (1997) mass mailing (1998) Initiating NewCart (1997) Problems with webcat 2.01 for NT (1997)