[cd34]

First question: Are there any sponsors using the beta where a webmaster can sign up?

Second question: Are there screenshots or the ability for one of the members of this board to sign up for that sponsor program and look around, or, can some additional screenshots of the webmaster interface be posted?

As for your referral id tracking:

http://www.domain.com/gallery01/?581222

is a current link. That follows through in a hosted gallery to a link that looks like

http://refer.ccbill.com/cgi-bin/clicks.cgi?CA=924000-0000&PA=581222

The new link code appears to look like:

http://wms.ccbill.com/wmsi/w_id/Lt-rftTOPWQUWhWHQG_TIAXtbGjdaiewnciLvJPZb2tsWMs*

and

http://wms.ccbill.com/wmsi/w_id/Lt-KAJSFDNJASDFAKFQG_TIAXasdcvcxsoSLvJPZb2tsWMs*

I don't believe it would be any different to send a link like:

http://www.domain.com/gallery01/?Lt-KAJSFDNJASDFAKFQG_TIAXasdcvcxsoSLvJPZb2tsWMs*

and have it counted on the new site. This is a non-ccbill issue. The coding on the hosted content would need to change slightly, and wouldn't be backwards compatible, so, if a sponsor started using the new system, all of the hosted content would then need to be tagged as 'new format.' Webmasters could then use the new links from this day going forward leaving the legacy links out there. Its possible that the sponsor could mirror the existing content, make the changes for the new link format so that new webmasters could utilize the 'newly' coded 'older' hosted content.

However, the only real issue is the old-traffic versus new-traffic link format.

Based on the example for Sponsor A and Sponsor B and the url's given above, There's obviously some encoding that has been done. Since you are able to generate the encoded values above for the url, you can take:

http://refer.ccbill.com/cgi-bin/clicks.cgi?CA=924000-0000&PA=581222

parse out the CA (sponsor) -???? (site) and the partner account number, and generate the encoded value that the new system uses and redirect the traffic from refer.ccbill.com/cgi-bin/clicks.cgi over to the http://wms.ccbill.com/wmsi/w_id/ script. Since all of the values you need for the new system should be contained within the old urls, it would be easy to write that redirect. It wouldn't require any re-integration of the existing redirect script to try and insert data into the new system. A surfer would get a double redirect, but, if you can rewrite that url on the fly based on the data in the old link url, you wouldn't have any need to access a database to move old-style link traffic to the new referral link. No integration nightmares of old to new.