Certona

Introduction:
Certona is a third party real-time personalization and revenue optimization platform for multi-channel retailers. Certona provides recommendations to Clients based on various tagging on the web pages

Purpose:
This document contains instructions on how to configure adidas web site to allow the Certona recommendation engine to collect data elements that will be used to create personalized recommendations.

Page Layout and template markup

Certona will be implemented on following pages: PDP (YMAL).

Category pages:

Cart page (YMAL section)

Null Search Results page:

Home page: On home page, Certona will be implemented at below 6 sections. These will be individual divs.

Design Approach:
Design approach is divided in to below two sections: 1. Basic Tagging 2. Certona cartridge implementation. 1. Basic Tagging: This refers to the tagging that needs to be done across pages to help Certona return the recommendations based on specified Certona rules. For this the variables needs to be included across pages in addition to including resxclsa.js(provided by certona):
Variable name resx.host resx.appid resx.top1 resx.top2 resx.links Value qa.res-x.com, left blank for prod environment addias01 100000 100000 Link ids on pages product, wishlist, shopping+cart, purchase+confirmation, Event type wont be passed for home page, null search results and search results page. Item ids Email id of customer IsConfigurable Yes Yes Yes Yes No

resx.event resx.itemid resx.customerid

No No No

2. Cartridge implementation: The Certona cartridge implementation returns recommendations for various pages based on specified Certona rules. Design steps: 1. Include all input parameters across pages.(See section Input parameters for details) 2. Create cartridge for Certona. The cartridge can be included by business on various pages in content sections. 3. Cartridge will contain three configurable parameters. a) resx.rrec: Value will be configurable from properties file. b) resx.rrnum : Business can specify how many recommendations request needs to be made for specific page and for specific section. Note: If this value is not specified in cartridge, then default value passed to Certona will be 1. c) resxx.rrelem: Business needs to specify the div id for various sections across pages here. This will be concatenated with resx.event parameter to keep it unique across

various pages. It can be multiple across single page but single for a specific section of page. Note: If this value is not specified in cartridge, then Certona cartridge wont be visible as this is the mandatory parameter. d) Overwrite: If checkbox is checked, business can overwrite the existing cartridge with Certona cartridge. Else both cartridges will be visible on front end. 4. Value for resx.rrnum and resxx.rrelem parameters will be substituted in js scripts and passed as request to Certona. The multiple values passed will be delimited via semicolon; Both variables are consecutive to each other. For eg. resxx.rrelem = home1;hoem2;home3; resx.rrnum = 1;3;2; The above statement specifies that the div with home1 id will have 1 recommendation, home2 will have 3 and home3 will have 2 recommendations. 5. The current implementation across pages will remain as-is. So if business wants to add Certona cartridge in place of any other cartridge, he can configure that. Various possible options are as follows a) Certona Cartridge: If business drops Certona cartridge in any section, the recommendations will be available from Certona. b) If business adds Certona cartridge in addition to default existing cartridge on any section, Both cartridge will be visible on front-end. c) If business adds Certona cartridge in addition to default existing cartridge and checks overwrite checkbox , Certona will overwrite the default cartridge.
Input Parameters: The input parameters for Certona Cartridge implementation are:
1. resx.rrec= true

This parameter is used to send a recommendation request to the Resonance server. For this the value passed should be true. When false, no request is made and the page displays "as is."
2. resx.rrnum = "1;2;3;

This value is the number of recommendation items the Resonance engine will return for each request. On pages with just one scheme, there will be one value. On pages with multiple schemes, you have two options: Provide just one value and the engine will return the same number of items for each scheme. Provide multiple values, one per scheme, separated by semicolons (;).resx.rrnum

3. resx.rrelem = "home_rr";

This parameter is used to specify the div ids for various div on pages.
4. <div id="home6_rr"> <!-- Recommendation box n and items appear here --> </div>

When recommendation boxes are placed on a page, each box should appear inside individual HTML div tags that have the same ID values as the scheme names in the resx.rrelem variable. In addition to above specified variable, the basic tagging elements to be include on pages are. 1) resx.host = This is the Certona host variable that needs to be passed on staging environment. The value for staging environment is qa.res-x.com. This value needs to be removed prior to deployment on production environment. The empty parameter request passed will point to production environment. 2)resx.appid = This value is the client id for various clients. The value for this is addias01. 3)resx.top1 = This parameter refers to a constant value 100000 provided by Certona. 4)resx.top2 = This parameter refers to a constant value 100000 provided by Certona 5)resx.links = This parameter refers to various links present on pages other than selected items. For eg, This parameter contains the YMAL product ids on PDP page. 6)resx.event = This value contains a constant parameter for various pages. Value for various page are as follows. PDP= product Cart= Shopping+cart Confirmation page = Purchase+confirmation Wishlist= wishlist 7)resx.itemid = This variable contains the itemid. If on PDP, it refers to the selected item. In cart and confirmation page, it refers to the items in cart and so on. 8)resx.customerid = The customer id being passed to Certona is the email id of user. For registered user, this will be the saved value in account and for anonymous, this value will be the email id value entered in checkout flow. Output Parameters: Output parameter for Certona will be recommendations based on request made. For eg, If user specifies resx.rrnum value to be 2, Then two product recommendations will be returned to Front-end.

Design Task TBD/WIP/CMS

Home page design- WIP Cart YMAL section TBD , Certona dependent. Adding JS and CSS: TBD, Certona dependent. Products Links will be

Design Flow
Whenever user opens any page where business has used Certona cartridges, the recommendations will come from Certona. End User behavior wont change here.

Exception Scenario:
If Certona recommendations are not available at any point of time, Following are the various possible options as per configurations;

a) Certona Cartridge: If business drops Certona cartridge in any section, the recommendations will be available from Certona. -In this exception scenario, blank place will be shown to user. b) If business adds Certona cartridge in addition to default existing cartridge on any section, Both cartridge will be visible on front-end. - In this exception scenario, only default cartridge will be visible to user.. c) If business adds Certona cartridge in addition to default existing cartridge and checks overwrite checkbox , Certona will overwrite the default cartridge. -In this exception scenario, blank place will be shown to user. 3. If Default cartridge is removed and div id is left blank by user, then no output.
4. Cannot relace div id with Certona id as design will not be configurable. 5.

Dev Setup:
Client set up:

For Client setup, We need to pass resx.host variable in input parameters. Based on this variable, Certona will return the recommendation for that host.
Third party setup:

Certona needs to set up database for various environments for adidas data collection

Abbreviations
TBD WIP CMS To be done Work in Progress Content Management System