Affiliate Link Chaining
Updated: 09/03/2013
This will be very useful to you if you own multiple DAP-Powered membership sites, and you want your affiliates to set affiliate cookies for multiple DAP sites all at once.
DAP allows your affiliates to set the cookie, and then redirect the visitor to any web site URL they want. That second link could be yet another affiliate link from another DAP site, or any affiliate link for that matter.
This allows your affiliates the ability to drop their affiliate cookie on the visitor’s computer for multiple DAP sites. So if they visitor goes on to buy from any of the “network” sites (all powered by DAP), they will get the credit for the sale.
This article is about setting 2 separate DAP affiliate cookies (from two separate membership sites) with one single user-click.
A Tale Of Two Cookies 🙂
Let’s say you have DAP running on two separate web sites. SiteA.com and SiteB.com
You have someone who is an affiliate on both sites. They have user id 1111 on SiteA.com, and user id 2222 on SiteB.com
So here’s how they can create a link that drops two separate DAP affiliate cookies from two different domains on the visitor’s computer, so the affiliate can get credit for any sales happening on either web site.
- Your affiliate’s link for SiteA.com is http://SiteA.com/dap/a/?a=1111
- Now redirect that to a intermediate auto-redirecting page on any of those two sites (doesn’t matter. So let’s pick SiteA.com. And this redirect page – let’s call it redirect.html – is a simple HTML page with a meta-refresh tag as shown below:<html>
<head>
<META HTTP-EQUIV=”Refresh” CONTENT=”0;URL=http://SiteB.com/dap/a/?a=2222“>
</head>
</html> - If you see the URL value in the above text, you’ll see that the above page is basically doing a simple and instant redirect to the 2nd affiliate link – which is http://SiteB.com/dap/a/?a=2222
- So the main affiliate link becomes http://SiteA.com/dap/a/?a=1111&p=www.SiteA.com/redirect.html
That’s it!
So basically, here’s what’s happening:
The first affiliate link (with extra redirection at the end)…
http://SiteA.com/dap/a/?a=1111&p=www.SiteA.com/redirect.html
Redirects to…
www.SiteA.com/redirect.html
And redirect.html in turn redirects the visitor to…
http://SiteB.com/dap/a/?a=2222
That ends the chain. But if you want to take it further, keep reading.
If you want the final landing page to be say SiteC.com/some-page/ then your HTML code for redirect.html becomes…
<html>
<head>
<META HTTP-EQUIV=”Refresh” CONTENT=”0;URL=http://SiteB.com/dap/a/?a=2222&p=www.SiteC.com/some-page/“>
</head>
</html>
Hope this helps.
