Adding a new Store #
It’s possible to add more stores to your Clerk account backend. You might want to add a new store with different country domain or a development site.
In your my.clerk.io Dashboard, click on the current Store name in the upper right corner:
Near the bottom of the popup, click + Add New Store:
Fill in the details for your store and click Add New Store.
You will now be redirected to Setup Guide where you can setup your store.
Copying from an existing Store #
When you create a new store in my.clerk.io, you can save yourself a lot of work if you use the same setup as your existing store by simply copying the content and designs.
This is very handy if you are creating a new store for a different language, or a new domain for your original store.
In your my.clerk.io Dashboard, click on the current Store name in the upper right corner:
Near the bottom of the popup, click + Add New Store:
Fill in the details for your store and click Advanced:
Under Copy Content From Existing Store choose the store you want to duplicate from the dropdown. You can even choose if you want to include some elements from the Store:
Click Add New Store.
The new store will then be created with the same Designs and Content as your existing store, ready to use.
Now you just need to make minor changes in the Designs (such as changing the currency symbols and button texts for example).
Deleting a Store #
IMPORTANT: When you delete a store, its settings and data will be removed forever, and cannot be restored.
Start by clicking the Settings in the side-menu. On the following page, scroll to the bottom and click the Delete Store button:
You will see a prompt that you need to Confirm:
After this, your Store is deleted.
API Keys #
Notice: For security for Clerk, the Private API Key will be generated upon store creation and will be sent to to the owner of the MyClerk account.
Each Store has a fixed Public API key and any number of Private API keys.
The Public API key is used when making calls to Clerk, and can be shared anywhere as it does not give access to sensitive data by itself.
Combined a Private API key, you can get access to sensitive data like email addresses and make changes to the data on a Store.
If you need your Store’s keys for any purpose after the initial integration, they can be found under Settings > API Keys.
The Private API keys at the bottom are not used for the plugin or extension but rather for testing purposes for custom API integrations.
API Status #
This contains an overview of all API calls made in a defined period of time. It has a range of information points:
API #
The API endpoint that is called. E.g. recommendations/popular
Labels #
The identification labels used for Clerk to track the results shown. E.g. Products Page / Alternatives
Hits #
The total amount of results found by the endpoint.
Results #
The total amount of results actually shown to customers. Differs from hits if e.g. the limit of products shown is lower than the results found.
Avg. Response Time #
The avg. milliseconds it takes for the API endpoint to return results.
Success Rate #
The percentage of API calls that did not result in error or empty result.
Features #
The Store has a number of toggles that can be used to control which features are active.
Customization Settings #
Standard features that can be toggled on and off. Mainly used for identifying issues caused by modifying Clerks standard behavior. When a feature is Disabled, any functionality within that feature will stop working.
Current features that can be toggled are:
- Customized Search
- Redirects
- Synonyms
- Merchandising
- AI Campaigns
- Fullname Categories
Early Access #
These are features that are still actively being built. They can be activated manually to allow testing of early features before they are released globally by Clerk.
Most can be enabled by any user on a Store, and some can only be activated by Clerk employees if they are still in Beta, which is the stage before they become public Early Access.
If some of the below are not visible to you, it’s because they are still in Beta. Reach out to a Clerk employee if you are interested in testing Beta features.
Search 3.0 In Demo Store #
The latest version of our Search engine can be activated in the Demo Store specifically, to check the difference it makes when compared to the live site. Search 3.0 is a great improvement in how it understands any type of query and ranks search results.
AI Demo Shop Assistant #
Activates the Sales Assistant in the Demo Store, so it can be tested. Only works if you have also activated Search 3.0. More info on the Sales Assistant Introduction page
Search 3.0 #
Activates the latest version of our Search engine on your live site. Search 3.0 is a great improvement in how it understands any type of query and ranks search results. You don’t have to reinstall Search on your site as the change happens on the API level.
It will work with your existing setup.
Semantic Fallback (Beta) #
A groundbreaking way to handle full phrase searches. If no direct match can be found, Clerk will analyse the query and understand semantically what visitors are looking for. E.g. a search for “something to cool my food with” will return refrigerators.
Recommendations 3.0 (Beta) #
A much faster way of showing Recommendations results, based on the same framework used in Search 3.0.
Currently works for these logics:
- Bestsellers (
recommendations/popular) - Bestsellers in Category (
recommendations/category/popular)
This does not require reinstalling Recommendations as the change happens on API level.
Order Scoring (Legacy) #
A different way of scoring products based on their order data in search results in older versions of Search. This is being phased out as our latest version of Search (3.0) handles this in a much better way.
Spell Fix (Legacy) #
A different way of handling spelling mistakes in older versions of Search. This is being phased out as our latest version of Search (3.0) handles this in a much better way.
SKU Search Optimisation (Legacy) #
A different way of handling SKU searches in older versions of Search. This is being phased out as our latest version of Search (3.0) handles this in a much better way.
Autocomplete Improvement (Legacy) #
A different way of autocompleting searches in older versions of Search. This is being phased out as our latest version of Search (3.0) handles this in a much better way.
Improved Category Search (Legacy) #
A different way of searching for categories in older versions of Search. This is being phased out as our latest version of Search (3.0) handles this in a much better way.