I am looking for someone to setup a masking redirect system for me using two domains. Here is basically what I am looking to do:
When a member from "domainA" clicks on a link from the member area of "domainA" they are redirected to "domainB" which then would go to the final destination which we'll call "domainC". I want this redirect to be invisible to the user from domainA. They should just click the link, and then the next thing they see is the final destination at domainC.
The idea is that I want the traffic to appear like it is coming from "domainB". So, the website/server at domainC thinks the traffic is coming from "domainB" and knows nothing about "domainA".
I am wanting to hide the origin of the traffic to my competition...which is the final destination for the user.
Also though, I need to be able to track each user, and pass some info on with the redirect.
I think that the very best way to handle this, is going to be to have the user setup a member account on domainA. In doing so they will create a username.
This username is what will need to be passed along with the click if they click on an offer. Here would be an example of a link that would be clicked.
[url removed, login to view]
If you follow that link, you will get to the final destination page: domainC
Where it says "example" in the link would be the username. So, if you could append the username to the end of the link, and then pass the whole link on...all of the information that is vital to my tracking would be intact.
The user would login to their account, and then be shown offers like you see there. The username would then need to be appended to the end of the link and passed on to domainB.
DomainB will actually be very, very similiar...almost exact with the exception of some design elements being changed to domainA. The click then needs to look like it originated from domainB.
I'm not sure how I'm going to handle the membership management part...but I was hoping that there would be an easy solution to append the username onto the link and pass it on.
Hopefully this is making sense to you. Once again:
I need a real click from domainA to turn into a false click from domainB, and then the user gets to domainC without knowing any of this has happened...other than the fact that they clicked on a link from domainA.