1. No Images
2. No Cookies
3. Perfect redirect script. Domain A accepts traffic from the ads and using a javascript POST, it redirects to Domain B. Domain B verifies the traffic is coming from Domain A, and if it is, decrypts the ad code, looks that up and redirects via a javacript POST to the appropriate aff offer. The aff offer only sees a referrer of Domain B. It works flawlessly and has been tested hundreds of times.
4. On Domain B, the only reference to Domain A is within a php script that checks to see if the referrer of incoming traffic is Domain A.
Both of the domains are hosted with the same hosting service, but are on separate servers with diff ips, so no connection there. Both domains have whois privacy, so no connection there. Both domains were registered about a month apart, so no connection there.
The only thing I can think of is that one of these traffic reporting services like Compete or Quantcast has recorded traffic going from Domain A to Domain B, but the kicker is, none of those sites report anything for either of the domains, as there has been no traffic to either domain to speak of, cept for testing.
The only purpose of using a Domain A was to hide inbound links from ads. If the ads pointed directly to Domain B and the aff offer knows Domain B from its referrer logs, they could just do a backlink discovery on Domain B and find all the sites where our ads are placed.
A lot of people think that just because they hide/blank/obscure the referrer that they are hiding their traffic sources, especially for media buys. Not so. If your traffic is pointing to the same domain that then refers to the aff site, the aff site can easily find your traffic sources.
In fact, one 'expert' told me at an event, that he can tell me anything about any campaign I do, although he wouldn't elaborate.
If we don't figure it out, we're simply going to tell the network either tell us how you found Domain A or we're not dropping 50K in ads for your network.
Go figure...
Bookmarks