Affiliate Networks Technology

[Joe Black]

Hi all,
I'm studing affiliate marketing networks, and I was wondering if anybody
knows how Affiliate Service Providers (ASPs)like cj.com or linkshare.com
track successful sales on merchant websites.

As far as I know the algorithm should be:
1) The affiliate publishes a link with his ID and the Merchant ID in his
website (ie. http://www.cj.com/redirect.xxx?id=12345&merch_id=54321)
2) The visitor clicks on the link with the intention to buy from the
Merchant
3) The link takes the visitor to the site of the Affiliate Service
Provider (in this case cj.com) that logs the visit, referrer, etc. and
sets a cookie in the visitor's PC
4) The visitor is redirected the the Merchant's web site that logs the
new visitor as coming from the ASP either by reading a special ID on the
GET string or by reading the referrer value
5) The visitor proceeds to shop while the Merchant tracks the visitor
around the site with an id binding it to the ASP and probably the Affiliate
6) The visitor checks out paying on a secure server with a credit card

Now here comes the puzzle. How does the Merchant notify the ASP of the
successful transaction?
My hypothesis are:
- The ASP gives the Merchant a snippet of code to be embedded in the
source code of the "Thank you" page that connects to the ASP server
notifying the details of the succesful transaction.
- The ASP tells the Merchant to embed an <IMG> tag in the "Thank you"
page linking to a server-side script in the ASP server.
- The ASP gives/sells a custom e-commerce platform along with the
subscription to the service to the Merchant (not likely)
- The ASP tracks the visitor throughout his "journey" on the Merchant's
webserver via embedded <IMG> tag or some other tracking technique,
including his checkout process in the HTTPS secure pages (not likely).

All of these artifices are perfectly viable, but what puzzles me is that
they all suffer from one huge flaw: the merchant can cheat.
Obviously the whole point of tracking the visitor is to credit
successful sales to the rightful Affiliates (thus giving them the right
commission), but if the Merchant cleverly manipulates the server-side
code in his scripts, for example by randomly or deterministical ly
disabling ASP's tracking tecniques, he can receive free leads for sales
that neither the Affiliate nor the ASP will never be aware of.

Now, my big question is: am I missing something here or is the whole
model of affiliate networks heavily reliant on trust?

I would love to here from you guys if you know anything about the "real"
mechanics going on behind the scenes of ASPs.
Regards
Joe Black

[clintonG]

The real mechanics? Affiliate marketing is based on fraudulent
representation from the get go.

There is absolutely no way to guarantee a referral as HTTP itself is a
flawed protocol in this context. The HTTP_REFERER server variable is not
reliable -- often empty or containing fraudulent data -- and when using the
web using this server variable is the only way to capture the origin of a
click event required to credit an affiliate referrer. The merchant does not
care be they slime or ignoramous as they get the visitor to their website
either way.

QueryString values can also be modified by slimey affiliates and resubmitted
to the merchant's website so there is rampant fraud in that regard as well.
Finally, with regard to mechanics, tracking referrals also depends on
client-side cookies which for a variety of reasons are not reliable either.

I wrote affiliate scripts and consulted for two and a half years attempting
to build a line of business in what I thought would be a lucrative niché --
a win-win for all concerned -- and what I learned while doing so left me
more cynical than ever.

The entire process and most involved were and are corrupt and fraudulent:
software vendors and merchants alike.

It takes a lot of software, testing and reporting to create and manage a
credible affiliate marketing program, most merchants are in fact either
ignoramouses or slime and want something for nothing, the software vendors
are definitely slime and when all is said and done there is no way to
resolve the flawed mechanics. So to what end?

Making referrals is an honorable but idealistic objective that has been
spoiled by the pimps who exploit the vulnerabilities of the process when it
is conducted using Internet protocols as the implementation. I'm out of
here...

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET cs*********@REM OVETHISTEXTmetr omilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/

"Joe Black" <jo*@black.co m> wrote in message
news:fx******** ***********@twi ster1.libero.it ...

Hi all,
I'm studing affiliate marketing networks, and I was wondering if anybody
knows how Affiliate Service Providers (ASPs)like cj.com or linkshare.com
track successful sales on merchant websites.

As far as I know the algorithm should be:
1) The affiliate publishes a link with his ID and the Merchant ID in his
website (ie. http://www.cj.com/redirect.xxx?id=12345&merch_id=54321)
2) The visitor clicks on the link with the intention to buy from the
Merchant
3) The link takes the visitor to the site of the Affiliate Service
Provider (in this case cj.com) that logs the visit, referrer, etc. and
sets a cookie in the visitor's PC
4) The visitor is redirected the the Merchant's web site that logs the
new visitor as coming from the ASP either by reading a special ID on the
GET string or by reading the referrer value
5) The visitor proceeds to shop while the Merchant tracks the visitor
around the site with an id binding it to the ASP and probably the Affiliate 6) The visitor checks out paying on a secure server with a credit card

Now here comes the puzzle. How does the Merchant notify the ASP of the
successful transaction?
My hypothesis are:
- The ASP gives the Merchant a snippet of code to be embedded in the
source code of the "Thank you" page that connects to the ASP server
notifying the details of the succesful transaction.
- The ASP tells the Merchant to embed an <IMG> tag in the "Thank you"
page linking to a server-side script in the ASP server.
- The ASP gives/sells a custom e-commerce platform along with the
subscription to the service to the Merchant (not likely)
- The ASP tracks the visitor throughout his "journey" on the Merchant's
webserver via embedded <IMG> tag or some other tracking technique,
including his checkout process in the HTTPS secure pages (not likely).

All of these artifices are perfectly viable, but what puzzles me is that
they all suffer from one huge flaw: the merchant can cheat.
Obviously the whole point of tracking the visitor is to credit
successful sales to the rightful Affiliates (thus giving them the right
commission), but if the Merchant cleverly manipulates the server-side
code in his scripts, for example by randomly or deterministical ly
disabling ASP's tracking tecniques, he can receive free leads for sales
that neither the Affiliate nor the ASP will never be aware of.

Now, my big question is: am I missing something here or is the whole
model of affiliate networks heavily reliant on trust?

I would love to here from you guys if you know anything about the "real"
mechanics going on behind the scenes of ASPs.
Regards
Joe Black