Full Stack / Server-Side

Full Stack / Server-Side implementation utilises the Webtrends Optimize Tracking Service (OTS) REST APIs to control optimisation project delivery, combined with the use of the Webtrends Optimize JavaScript library to perform visitor activity tracking after a project has been delivered to the user.

The following diagram and subsequent details explain the process when a new user gets to the first page which is controlled by a server-side test, and the subsequent conversions.

 

 HTTP request to wt-retail.com/mensfashion

Visitor sends HTTP request to Wt.Retail.com, for a page. This request includes

  • URL
  • IP Address
  • First Party Cookies
  • Referer (intentional spelling)
  • User Agent

 WT-Retail API Request to Optimize

WT-Retail servers inspect the request, and identify there is no cookie which indicates to them, the variant to show. WR-Retail servers issue Webtrends OTS REST API request, to enquire which page variant should be shown to the user. The request passes along various attributes from the incoming HTTP request, to enable Optimize to decide which project and segment to match.

 Optimize Chooses Variation

Webtrends Optimize processes the request, matching the user to the appropriate project & segment, and replies with JSON indicating variation B should be shown. The response JSON includes the definition of cookies which should be sent on the users’ browser, which indicate which contain details of the user, the assigned project, throttling settings etc

 WT-Retail Servers Deliver Page Style B

WT-Retail servers interpret the response from Webtrends, including:

  • Generate the page to send to the user, taking into account the variation indicated by Optimize
  • Convert the “cookies” described in the JSON into cookies in the HTTP response header, to be sent to the user
  • Add a session cookie which WT-Retail can use to indicate that for the remaining period of this browsing session page version X can be shown to the user, without the need to ask Optimize

The page is delivered to the user.

 Page is Rendered

The test variation is rendered in the browser. Cookies to identify the user and test variation seen are saved in the browser.

 User Navigates

The user progresses down the conversion funnel, to page 2, on which the Optimize JavaScript file initialises.

 Page-Load Conversion

Optimize JavaScript gathers first party cookies and sends a request to Optimize to indicate that the user has progressed to a new page in the conversion funnel. The page URL and cookies are used to identify against which projects a conversion should be registered.

 Click Tracking

Optimize delivers to the page a confirmation that page-load conversion has been registered. To track clicks and other on-page interactions, JavaScript is delivered to the page, which when activated would send further messages directly to Optimize