I would like to know if anyone know any documents, articles or source code to study a little in order to implement this.
Just to say that I'm a ASP.NET newbie with few "navigation hours".
Thank you.regardless of asp.net, you can use several methodologies to incorporate affilliate tracking. The best one (in my opinion) would be to simply track the affilliate by passing around their value in the querystring (ie: mysite.com/page.aspx?aff=2343444)
Then you can look for this number -- say when a user submits a form to purchase an item.
OK. I'll avoid any discussion around more complex methods of handling the same functionality, and describe in terms of pages, session etc.
How about:
- Create an incoming page that can decode an incoming affiliate request.
e.g. http://www.mysite.com/affprogramme.aspx?affid=<insert id here>&sku=<product id here>
The page will:
- Set the session to the affiliate id, which is then recorded when items are placed in the cart.
- Redirect the incoming request to the appropriate product.
Then, when an order is placed, it's easy to pull a report based on affiliate purchases.
Be aware that this is open to abuse for click through payments.
Anyway, it's a start of a more refined solution.
Hope it helps,
Why not just pass the affiliate id in the querystring as opposed to keeping it in a session? Im asking because 90+% may not order, so why even look at that value until an order has been placed? (unless you want to track each page, even then why not just use the querystring.)
although I'm not that stingy with Sessions, imagine 50,000 users going to your site on a good month.
Either way both methods would work (just putting in my .02)
Thank you all for your "opinion" :
Question :
It is best to save the affiliate ID code in the cookie ?
Why ? Because if the user have been redirected to my page trough an affilliate link, and want to become later to buy something , he will type my direct address (www.mysite.com) without the affiliate link. I think I should know (remember) what affiliate have indicated my webpage.
What you think about this ?
Thank you.
Good point! But what if the user does not accept cookies?
hmmm... always something to think about.
I think the best way would be:
- Persist to cookie if user accepts cookie
- Use QueryString if not
if user does not accept cookies and goes back to the site by typing the url directly the affiliate would not get paid... hmmmm.
I should use both I think :
I should use the :
www.mysite.com/affiliates.aspx?affid=<insert id here
And use this affid to fill the cookie.
If the user don't accept cookies ... the affiliate don't win a comission ... sound right or not ?
Well, this could be a commercial issue.
What defines an affiliate 'sale'? Is it if a purchase is made from your site in the next session, 20 days, 30 days and so on.
This is what defines the use of cookies and the like.
The page will not sell products, will sell services.
Possible customers can bought the service now, today, next month or never. If he buy the service, until he's an active customer the "affiliate" will win comission of sale.
This is important to keep the affiliate information much time as possible.
What do you think ?
Technically, I think it's fine.
Commercially, I think that's a pretty good deal for your affiliates.
Cheers,
Commercially is a great deal for me too.
Imagine ... you will have a "free" comercial team.
Don't have problem paing 10% of comission to anyone that gives me a new customer (the rest of the profit is all mine). In this mode it is more simple to anunce my services. Just to say that the customer pay monthly for the service ... the affiliate will won the comission montly too.
Thank you all for your technical help.
Don't use affiliate.aspx?affiliateID=XXXX
If I find a link like that I'll manually go out of my way to simply type in the main URL into another window without the affiliate info.
However if it were something less obscure such as in.aspx?in=XXXX I don't know if it's an affiliate in link or simply a link exchange hit counter or a redirect so I'll just click and leave it.
Jake,
Thank you for you nice idea. I allways do the same but forget that detail.
Best regards,
also you could always:
1.) Create the link with the reseller Id in the page name (without having to create the page)..
ie: www.myDomain.com/res1233.aspx
Then create a custom handler to convert the res1233.aspx to an actual page (from the ASP.NET pipeline) while capturing the affiliate reference at the same time.
:-)
Although technically since you will be the owner of the affiliate program if people did what I do (just type in the base URL without affiliate code) it would benefit you as you wouldn't be paying out any commissions on those sales..
0 comments:
Post a Comment