Our developer is having problems. Currently, we are using a cookie to track our visitor movement. Our main sites and the SSL site are different domains (different IPs). Right now, the visitor is not identifiable when they move from the site to the SSL site (Checkout) , and we'd like to fix this problem.
There is a cookie called when the visitor accesses pages on the main site and a different cookie when they access the SSL site, and we'd like to know how to make it so that the same cookie is called for both.
If that is not possible, I'd like to know how people handle this problem.
The SSL site and the main sites are hosted on the same server running IIS, written in asp and html.
Could you point me in the direction of a solution or let me know what you are doing about this?