yukes.com >> Lazy Jay

Despite the many advantages of Tracking202 Pro — I get a lot of traffic to my offers from the old self-hosted open source solution — Prosper202 (Which can still be downloaded here http://prosper.tracking202.com/apps/download/)

When using Prosper202 on a separate tracking domain (i.e. different domain from your Landing Pages) — there can be problems setting cookies in IE6 + IE7. Take a look at this thread on WickedFire: http://www.wickedfire.com/newbie-questions/64275-tracking202-cookies-blocked-ie6-ie7.html Still unanswered 3 months later…

I Google’d it to see if anyone else was having issues –http://offermonitor.com/wordpress/?p=447 Yep, people be blogging about it.

There is a somewhat longwinded (and confusing) solution on Propser support forums: http://prosper.tracking202.com/forum/12/21/p3p-privacy-policy-problems-and-solutions

———-

Basically, we need to add support for some dumbass Internet cookie privacy standard — P3P — check all the criticisms in this Wikipedia reference.

The first thing I did when confronted with this problem was look at how other top affiliate networks set their cookies.

Let’s start with Hydra – I love these guys.
Here’s the P3P header that Hydra sends:

P3P: policyref="/w3c/p3p.xml", CP="NOR DSP COR ADM OUR"

And their P3P policy file (http://lynxtrack.com/w3c/p3p.xml) looks like this:
<?xml version="1.0" encoding="UTF-8" ?>
<META xmlns="http://www.w3.org/2000/12/P3Pv1">
<POLICY-REFERENCES>
<POLICY-REF about="/w3c/policy.xml">
<INCLUDE>/*</INCLUDE>
<COOKIE-INCLUDE>* * * </COOKIE-INCLUDE>
</POLICY-REF>
</POLICY-REFERENCES>
</META>


———

Next, lets look at Azoogle — or is it Epic — I dunno
Here’s the header that Azoogle sends:

P3P: policyref="http://azjmp.com/w3c/policy.xml", CP="ALL BUS LEG DSP COR ADM CUR DEV PSA OUR NAV INT"

Their P3P policy file was too long and boring for me to include — linked here: http://azjmp.com/w3c/policy.xml

———

CoreMetrics does it differently:
P3P: CP="NON DSP COR CUR ADMo DEVo PSAo PSDo OUR IND ONL UNI PUR COM NAV INT DEM STA"

Not to be outdone – DoubleClick adds:
P3P: policyref="http://googleads.g.doubleclick.net/pagead/gcn_p3p_.xml", CP="CURa ADMa DEVa TAIo PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR"

Atlas Solutions adds this:
P3P: CP="NOI DSP COR CUR ADM DEV TAIo PSAo PSDo OUR BUS UNI PUR COM NAV INT DEM STA PRE OTC"

AdShuffle looks like this:
P3P: CP="CURa ADMa DEVa PSAo PSDo OUR BUS UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR"

Look at MSN
P3P: CP=BUS CUR CONo FINIVDo ONL OUR PHY SAMo TELo

———

I started off confused — and looking at other implementations certainly didn’t help!
The more I looked around — the more confused I got…

But if you think about it — these guys ALL know what they’re doing — they can’t be losing conversions — so I’m gonna guess that any of these are gonna work.

I picked Hydra’s implementation because I love those Beverly Hills bastards!

Just install that /w3c/p3p.xml
And add this line right before you setcookie:
header( 'P3P: policyref="/w3c/p3p.xml", CP="NOR DSP COR ADM OUR"' );

Okay thats about it … no more techiness for today.