Skip to main content

​
Overview

This guide takes you through the 5 steps to implement PureClarity on your site using the bespoke implementation approach. Before you begin, PureClarity provides a number of Plug-ins that will automatically undertake a number of these steps. Please check out our integration page to see if we have a plug-in for your ecommerce platform.

​
1. Planning

The first decision before implementing PureClarity is whether you will adopt the client-side or server-side implementation method. The Client-side method is our recommended approach, however server-side may give you more control for complex installations. For more information see the Implementation Methods below. To get the best out of PureClarity you need to consider the most optimal placement of the merchandising zones. To help you decide we have provided a best practice guide on where to place these zones. We recommend you review them before adding the PureClarity elements to your site as described below in step 2. For more information see our guide on the Optimal Placement of Zones.
PureClarity allows you to make up to 8 zone requests per page load. Each additional set of 8 zone requests after this are counted as an additional page view, which is taken from your monthly page view charge.

​
2. Implementation

There are 3 main stages to implementing PureClarity into your ecommerce platform:
  • Add the PureClarity JavaScript Snippet (PCJS) master function to each page.
  • Add event tracking, to track user activity such as product views and add to basket.
  • Add Merchandising Zones, to display PureClarity content, such as product recommenders or banner images.
The PureClarity JavaScript Snippet (PCJS) master function manages PureClarity’s interaction with the site, keeps track of sessions and assists with debugging, and depending on your implementation type (Server/Client) the script may be responsible too for sending tracking events to PureClarity. The PCJS master function Javascript snippet needs to be at the top every page on the website, ideally after the closing <head> tag. This is detailed in PCJS Master Function section. Event tracking is needed in order to send user activity to PureClarity, such as product views, basket content, orders placed, currency changes and customer login & logout. Depending on the implementation type the approach varies. For client-side implementations events are added using Javascript and the PCJS master function. For server-side implementations your ecommerce platform will be responsible for sending events as HTTP requests. The approach to adding event tracking to your site is outlined in the relevant implementation sections. Zones are areas on the site that display PureClarity content to your users. Similar to event tracking, described above, the approach varies depending on your implementation type. For client-side implementations <div> elements on your site are tagged with specific attributes, and the PureClarity Javascript takes care of the rest injecting HTML onto the page. For server-side implementations HTTP requests are made to PureClarity to retrieve data and then you will need to render HTML around the data models returned. The approaches are outlined in the relevant implementation sections.

​
3. Data Feeds

Feeds are required to tell PureClarity about your data. You will need to build and test them. Feeds include a mandatory product feed & non-mandatory category, brand, user and order history data feeds. Submission and feed management can be found in the PureClarity Admin console under ‘Settings > Feed Management’ or via our API. For more information see: Data Feeds

​
4. Templates

Following on from Step 2 if you opt for client-side implementation you can edit the look and feel of the HTML that is returned from PureClarity. This HTML and CSS is generated by PureClarity using the Template Management system, and can be managed and edited in the admin console under ‘Settings’. See the Templating section for further information about how to style the look and feel of the various PureClarity content types. For server-side implementations, the styling and HTML will be controlled by your platform, from the data model returned from PureClarity. This is explained in further detail in the Server-side implementation section.

​
5. Historical Order Feed

Once you’re ready to start to use PureClarity it is advisable to upload 6 months of past order history to kick-start the AI’s learning and increase the relevancy of recommendations. For more information on creating this data see the: Historic Order Feed section. You can also use this method to provide a daily feed of orders that are generated offline (e.g. phone and in store orders). PureClarity’s machine learning will use this data to adapt its recommendation results. This is optional. Now, you’re ready to go live!

​
Need Further Help?

If you have issues while implementing PureClarity, Developer Debug Mode may help you to debug the problem. Alternatively if you have any questions you can contact our support team by emailing support@pureclarity.com