HTTPS Conversion Solution
To implement conversion tracking, Connect 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 the conversion tracker.
Note: For clients with secure e-commerce sites, the "Thank You" page uses HTTPS which causes undesirable effects. In particular, a customer viewing the "Thank You" page can get a message warning them that the page contains both secure and non-secure data. To resolve this issue, use a proxy program or a proxy server.
There are different ways to implement the conversion solution. Using a proxy program is inexpensive, but requires adding an executable program to the e-commerce site that can cause scaling issues. The proxy server solution requires the client to purchase the server and an SSL server certificate. It is noted that this solution does not touch the site and scalability is not an issue.
Proxy Program Method
The client is supplied with a servlet—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 the conversion tracker and passes the 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.
Note: Cookies are readable only by a member of Tracker’s subdomain. So, for example, if the Tracker domain is tracker.sth.com, the cookies are readable only by an xxx.sth.com subdomain.
Clients with multiple HTTPS domains or service bureaus can overload the HTTPS site with a name compatible with the tracker domain. For example, if the 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. The process is as follows:
The customer clicks the link associated with the desired behaviour.
The conversion tracker sends the tracking cookies kc_customer and kc_click cookies.
The customer completes the qualifying transaction on the e-commerce site.
The e-commerce site sends the "Thank You" page to the customer with the 1x1 pixel image.
The customer downloads the "Thank You" page.
The downloaded 1x1 pixel image triggers the servlet which sends the HTTP request.
The servlet sends the HTTP request to the tracker.
The tracker sends the response back to the servlet.
The servlet sends the tracker response to the customer (i.e. confirm the cookie).
The tracker sends the details of the successful completion of the transaction to the profiler.
Proxy Server Method
The Proxy Server method may also be used. Connect is certified to run using an Apache web server for the proxy server.
The one-pixel by one-pixel invisible image on the "Thank You" page must redirect to the proxy server rather than the conversion 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 the 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.
Note: Cookies are readable only by a member of tracker’s subdomain. For example, if the tracker domain is tracker.sth.com, the cookies are readable only by an xxx.sth.com subdomain. The proxy server must have a name like proxy.sth.com if the tracker is tracker.sth.com.
Clients with multiple HTTPS domains or service bureaus can overload the HTTPS site with a name compatible with the tracker domain. For example, if the 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. The process is as follows:
The customer clicks the link associated with the desired behaviour.
The conversion tracker sends the tracking cookies kc_customer and kc_click cookies.
The customer completes the qualifying transaction on the e-commerce site.
The e-commerce site sends the "Thank You" page to the customer with the 1x1 pixel image.
The customer downloads the "Thank You" page.
The downloaded 1x1 pixel image triggers the servlet which sends the HTTP request.
The proxy server sends the HTTP request to the tracker.
The tracker sends the response back to the proxy server.
The proxy server sends the tracker response to the customer (i.e. confirm the cookie).
The tracker sends the details of the successful completion of the transaction to the profiler.
