Integration process decision overview¶
During the course of an integration of Apptus eSales several decisions must be taken in order to progress. These decisions will affect the integration outcome and performance of the system.
The most critical decisions during an Apptus eSales integration process are summarized below.
These decisions are presented according to a chronological process order.
|What parts of Apptus eSales will be used||Retailer||The business decision of the Retailer that sets the scope of the Apptus eSales integration.||Before Integration start|
|Level of Personalisation||Retailer||The level of personalisation is a business strategy decision that determines how sessions and visitor identification is to be managed. This will affect how behaviour data is managed and how results and personalised content is presented.||During Data Integration|
|Data Model||Retailer and Implementing partner||The data model is the base of how products and more are defined and managed within Apptus eSales. Should there be one language per attribute or one product per market in the data model.||During Data Integration|
|Import strategy and scheduling||Retailer||The Implementing partner must know what functions to develop to transfer data from the Retailers PIM/ERP systems to Apptus eSales.||During Data Integration|
|Market set-up||Retailer and Implementing partner||The different functions of the Apptus eSales apps are divided and managed by market.||During Data Integration|
|Product Cost||Retailer||To be able to use an exposure strategy for profit-optimisation, the cost of products must be defined per product.||During Site Integration|
|Notification set-up||Retailer and Implementing partner||The Implementing partner must know what parts that must send Notifications back to Apptus eSales.||During Site Integration|
|Search attribute set-up||Retailer and Implementing partner||The Retailer must decide how Apptus eSales should return search results.||During Site Integration|
Apptus eSales Apps¶
Apptus eSales includes four different web based apps for managing product promotions, controlling exposure strategies, gaining insights into search relevance, user administration, and more. All is presented in an easy to use interface with contextual help on every page. Some apps include step-by-step guides on how to set up and get started with the different functions of that specific app.
App availability is dependent on what functions of Apptus eSales the retailer has implemented.
Retailer administrators can set and allow user access for each app on a cluster and market level.
The Business app enables a merchandiser to control exposure strategies, promote products, and perform A/B-tests with just a few clicks. It also allows for quick insights into sales origins for a market segmented on conversions, revenue, and profit.
The Experience app is where statistics of search phrases per market are presented and synonyms are managed. The search summary presents relevant statistics for each search phrase including overall search conversion rate and hit ratio.
Synonyms can be used for all or for specific markets and enables additional words and phrases to be used together with an existing search phrase. Using synonyms will provide more relevant search results for visitor leading to a better experience.
The Integration app dashboard allows for a quick overview of the system status of Apptus eSales. It shows the servers and their status in the cluster including the software version it is running. The dashboard also shows when the latest import was made plus how many products, categories, variants, and ads are present.
The Admin app is where the retailer administrators can manage users, access rights to apps and markets as well as system configuration for locales, market currencies, and more.
Notification set-up recommendations¶
The following list items are recommendations when implementing notifications with Apptus eSales.
- Notify Apptus eSales when clicks are made on Apptus eSales content such as products and ads. Notifying clicks on categories is not necessary.
- Notify Apptus eSales when a product is added to cart with an "addtocart"-notification
- Notify all purchased carts to Apptus eSales when they happen
- Notify cost, quantity, and selling price for each purchased item in the cart
- Session-handling must support the selected level of personalisation
- Market must be present on all notifications
For more information about Notification set-up, see Working with Notifications.