Re: [PHP] Affiliate system




I ran into same issue with a site... I solved this problem by saving
information in 2 places (in cookies and in database). So when saving
data once I saved in the cookie then into database. When I wanted to
read the information I first check if cookie exist and if it doesn't I
read from database.

Andy

Peter Lauri wrote:
Hi guys,

I am reviewing an affiliate system that I created a while ago. I am using a
very simple method to do this, but I am curious if there is any better
system (better I mean less missed affiliate purchases).

1. User click on affiliate link http://thedomain.com/?a=1234
2. The if $_GET['a'] is set, we check if that is an valid affiliate, and
then set a cookie for that
3. At purchase, we check if that cookie still is there, if so, we register
it as a affiliate purchase and that info is stored in the purchase database

What should I do if they do not allow cookies? I could amend a=1234 onto
every url that they pass, but that would not be a "beautiful" solution.

Maybe I can also create a SESSION that stores the affiliate information so
that it at least get registered if the purchase is completed within the
session?

What do you think is the best way?

Best regards,
Peter Lauri

www.lauri.se - personal web site
www.dwsasia.com - company web site

.



Relevant Pages

  • RE: [PHP] Affiliate system
    ... read the information I first check if cookie exist and if it doesn't I ... I am reviewing an affiliate system that I created a while ago. ... At purchase, we check if that cookie still is there, if so, we register ...
    (php.general)
  • Affiliate system
    ... I am reviewing an affiliate system that I created a while ago. ... At purchase, we check if that cookie still is there, if so, we register ...
    (php.general)
  • [UNIX] Wordpress Cookie Authentication Vulnerability
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Wordpress Cookie Authentication Vulnerability ... With read-only access to the Wordpress database, ...
    (Securiteam)
  • Re: Best authentication methods for CGI <- PERL -> DBI
    ... Right now one method which seems to be really unsecured, is to take them, check them against the PW/ID stored in the database and permit/deny against that. ... The client javascript code takes the password and MD5 sums it, and sends that as the password along with the cleartext username. ... One cookie is the record id of the user in the database, ... A solution to not use https would be public key encryption. ...
    (perl.dbi.users)
  • Re: Best authentication methods for CGI <- PERL -> DBI
    ... Right now one method which seems to be really unsecured, is to take them, check them against the PW/ID stored in the database and permit/deny against that. ... The client javascript code takes the password and MD5 sums it, and sends that as the password along with the cleartext username. ... One cookie is the record id of the user in the database, ... A solution to not use https would be public key encryption. ...
    (perl.dbi.users)