Get Started

Jtl: Get Started

Connecting your Store #

The first step of installing Clerk.io, is connecting your store with your Clerk.io account.

After following these simple steps you will be able to see your Demo Store, which gives you a personal overview of how Clerk.io will work on your webshop, before setting up the rest of the system.

1. Add Store #

After logging in to my.clerk.io, the first thing you need to do is add your store:

Example of how it should look
  1. Write the Name and Domain of your webshop

  2. Choose JTL as the Platform and choose your Currency.

  3. Click Add Store.

  4. Once the store is created, then an email about your public and private keys will be sent to the owner of the accounts email.

2. Configure the JTL Connection #

From the main menu of the Setup Guide, click Install Extension:

The next page shows what you need to do, to configure the JTL connection.

Go to your Clerk plugin in the JTL backend and add the public and private keys from the clerk store into their respective fields.

3. Sync your store #

After allowing access, you simply need to synchronise your store.

Go back to the Setup Guide and click Sync Your Data:

Write in your stores details and click Start Sync

The JTL feed url should be made based on this guide Creation of Data Feeds in JTL

Full Installation Example #

IMPORTANT: You should have installed the plugin (S360 CLerk) in your JTL backend under Plugins

This documentation will guide you through the following steps:

Adding a Store in my.clerk.io #

Each Store in Clerk.io is an isolated environment with its own data, API keys and Dashboard. The first thing you will need to do when setting up your Clerk.io account, is to create your first Store:

How the store creation screen looks

After this, the Setup Guide will walk you through the rest of the setup.

Note that each time a store is created, then an email with public and private keys will be sent to the owner of the company account. This is used to create secure access between Clerk and JTL.

Installing the two tracking-scripts #

With the S360 Clerk plugin, you can enable both visitor and order tracking scripts which will be injected to parts of the webshop:

  • The Visitor Tracking script, that initialises Clerk.io. This has to be injected inside of the header of the webshop.

  • The Order Tracking script that allows tracking of orders in realtime. This is usually installed on the order confirmation page.

You can enable them inside the JTL plugin under ALLGEMEIN section:

Inside the clerk plugin if you scroll a bit down

When both scripts are inserted, Clerk.io will been initialised.

Syncing your JTL Store with Clerk.io #

To show results, Clerk.io must sync with the products, categories, sales, pages and customers from JTL in a generated data feed.

This is done by setting up a data feed that allows the data to be accessed regularly. This is further explained in this guide Creation of Data Feeds in JTL.

When the data feed has been generated and added to your Data sync settings under System Status in your my.clerk.io backend.

Adding Search and Recommendations #

Frontend elements in Clerk.io consist of two parts:

  • A Design that controls the visual presentation of products. This can be changed to match any styling you want or you can use some of our standard design templates Template Design to use in Clerk.

  • Most often you will use 3 Designs: One for Instant Search, the Search page and Recommendations.

Example of a recommendation slider using our design editor
  • A Content with an attached embedcode that displays the products. Each content has a specific name in its embedcode which you want to add to the respective fields name Clerk TemplateName. This is used to communicate between your webshop and the respective clerk content.

The Setup Guide will walk you through where each element needs to be placed in most JTL setups.

At the end of your setup then the settings in the plugin should look like this. The following pictures are merely for demonstration purposes.

Credentials
OptionMeaning
API KeyYour API key received from Clerk
Private KeyYour legacy private API key provided by Clerk. Required to restrict access to the data feed.
LanguageLanguage of the data feed
customer groupPrices for the customer group
CurrencyCurrency in the data feed
Faceted designDesign of the facets
Tracking and Search settings
ComponentOptionMeaning
GenerallyUse cookieless trackingTracking without the use of cookies
Use shopping cart tracking?Informs Clerk about changes to the shopping cart (general tracking of the shopping cart)
Anonymize emailsEmail addresses are transmitted to Clerk anonymously (as a hash).
Live Suche (Header)Activate live search?If deactivated, the Clerk Live search will not be displayed in the frontend.
Selektor LivesearchLive search selector independent of Clerk
Clerk TemplateName LivesucheTemplate for the live search (Clerk Backend → Search → Content → Live search → Insert into website → In the code the value from “data-template=”@WERT’”)
Number of search suggestions in the live searchNumber of search suggestions to be displayed
Number of category suggestionsNumber of category suggestions to be displayed
Number of page suggestionsNumber of page suggestions to be displayed
PositionPosition of the live search result in relation to the selector
Search (results page)Activate results page?If deactivated, the Clerk results page will not be displayed in the frontend.
Clerk TemplateName SearchTemplate for live search (Clerk Backend → Search → Content → Search → Insert into website → In the code the value from “data-template=”@WERT’”)
Position facetsPosition of the facets
Show facets in URLShow facets in URL
Clerk Facets AttributeComma-separated list of available facets (JTL features)
Clerk Facets Attributes Multiple ValuesComma-separated list of available facets with multiple values ​​(JTL characteristics for OR filtering)
Data feed and Recommendation settings
ComponentOptionMeaning
Data FeedCron processingHow the cron should be triggered to generate the data feed (explained in more detail in the section Possibilities of data feed creation)
Batch sizeBatch size of the feed’s products (explained in more detail in the batch size section)
Product pageActivate product page slider?If deactivated, the slider on the product page will not be displayed in the frontend.
Article selector sliderSelector for the article slider independent of Clerk
Clerk TemplateName ArticleNames of the slider templates to be output. Multiple template names can be specified as a comma-separated list.
Slider Insert methodHow to add the slider to the selector (After, Append, Before, Prepand, ReplaceWith)
Filter duplicatesPrevents subsequent sliders from containing products from previous sliders (default: Yes)
Shopping cart pageActivate shopping cart slider?If deactivated, the slider on the shopping cart page will not be displayed in the frontend.
Shopping cart selector sliderSelector for the shopping cart slider independent of Clerk
Clerk TemplateName Shopping CartNames of the slider templates to be output. Multiple template names can be specified as a comma-separated list.
Slider Insert methodHow to add the slider to the selector (After, Append, Before, Prepand, ReplaceWith)
Filter duplicatesPrevents subsequent sliders from containing products from previous sliders (default: Yes)
PowerstepActivate Powerstep Slider?If deactivated, the slider in the power step is not played in the frontend.
Powerstep SelectorSelector for the Powerstep Slider independent of Clerk
Clerk TemplateName PowerstepNames of the slider templates to be output. Multiple template names can be specified as a comma-separated list.
Powerstep insertion methodHow to add the slider to the selector (After, Append, Before, Prepand, ReplaceWith)
Filter duplicatesPrevents subsequent sliders from containing products from previous sliders (default: Yes)
Category and exit intent settings
ComponentOptionMeaning
Category pageActivate category page slider?If deactivated, the slider on the category page will not be displayed in the frontend.
Kategorie Selektor SliderSelector for the category slider independent of Clerk
Clerk TemplateName Shopping CartNames of the slider templates to be output. Multiple template names can be specified as a comma-separated list.
Slider Insert methodHow to add the slider to the selector (After, Append, Before, Prepand, ReplaceWith)
Filter duplicatesPrevents subsequent sliders from containing products from previous sliders (default: Yes)
Exit IntentEnable Exit Intent Slider?If deactivated, the exit intent is not displayed in the frontend.
Clerk TemplateName Exit IntentTemplate for the exit intent

Multiple domains #

The easiest way to implement Clerk.io in multiple domains in standard setups is by creating a separate Store for each domain in my.clerk.io, and then syncing them with each of your JTL language domains.

This way, you can separate products, sales, currencies etc. to keep track of each domain.

  1. Start by creating your main Store and follow the Setup Guide to connect your Store to Clerk.io, and choose the Recommendations and/or Search Results you that you want to display on your webshop.

  2. When you are done with the initial setup, go back to the start page of my.clerk.io (by clicking the Clerk.io logo in the upper left side corner of the side-menu) and then click "+ Add new store" the last option of the scroll down list (generally under you the existing store(s) and your company name):

     3. On the Add New Store page, click Advanced to see all settings.

     4. Fill in the details of your domain, and choose your main Store  from the

Copy Content From Existing Store dropdown, then click Add Store.

         This will carry over the Content and Designs from your main Store.

     5. Now you can follow the Setup Guide again, to activate Clerk.io by clicking on Getting Started, to Sync Data for the new domain.

6. This will allow you to sync your domain with your Store at my.clerk.io through

         the Setup Guide.

     7. When Data Sync has finished, your domain is ready and using the same

         setup as your main Store.

8. Repeat this process for every one of your JTL language domains,

Remember to translate Headlines, in Content-> Edit -> Select Design to the right language as well.