To implement conversion tracking, the Connect client adds a one pixel by one pixel invisible image in the e-commerce Thank You page. When the customer downloads that page, the image triggers an HTTP request to Tracker. However, for clients with secure e-commerce sites, the Thank You page uses HTTPS causing undesirable effects. In particular, a customer viewing the page can get a message warning that the page contains both secure and non-secure data. To resolve this issue, use a proxy program or a proxy server.
The client's approach depends on their circumstances. Using a proxy program is inexpensive, but it requires adding an executable program to the e-commerce site causing scale issues. The proxy server solution requires the client to purchase the server and an SSL server certificate; this solution does not touch the site and scalability is not an issue.
Proxy Program Method
The client is supplied with a servelet—a jsp, asp, PERL, or cgi script—to place on the secure e-commerce site. The Thank You page points to the script on the HTTPS site rather than the tracker domain. When the customer downloads the invisible image, the script is activated. The script passes the customer’s HTTP request to Tracker and passes Tracker’s response back to the customer, activating the confirmation cookie. Because the script is located on the secure site, there is no warning message. The customer never interacts with unsecure data.
Clients with multiple HTTPS domains or service bureaus can overload the HTTPS site with a name compatible with the Tracker domain. For example, if Tracker resides at tracker.sth.com, one HTTPS site can be at www.domain1.com overloaded as www1.sth.com. Another site can be at www.domain2.com and overloaded as www2.sth.com.
Proxy Server Method
An alternate method is to use a proxy server. Connect is certified to run using an Apache web server for the proxy server.
The invisible image on the Thank You page must redirect to the proxy server rather than the Tracker domain. The proxy server is set up to listen only on the HTTPS port and work with all HTTPS requests. The proxy server intercepts the HTTPS request, passes the customer’s HTTP request back to Tracker and passes the Tracker response back to the customer while activating the confirmation cookie. The proxy server also sends the Tracker conversion cookies back to the HTTPS site. The customer never interacts with unsecured data.
Clients with multiple HTTPS domains or service bureaus can overload the HTTPS site with a name compatible with the Tracker domain. For example, if Tracker resides at tracker.sth.com, one HTTPS site can be at www.domain1.com overloaded as www1.sth.com. Another site can be at www.domain2.com and overloaded as www2.sth.com.
