You can also switch to the
Visual tab to build the rule using Visual Rule Builder.
In the settings panel, enter the below details to enable the visual rule builder preview:
- Image attribute
The name you assign the particular rule. An example might be “PS3 Upsell”. The name must be unique.
Best practice is to keep your names structured, with a nested path and ownership. E.g.:
Search > Brands > Nike > July Promote OS
Navigation > Categories > Headers OS
Promotion > Back To School 2017 KR
A trigger is a search and navigation state that triggers a rule; because they determine where a rule will fire, defining a trigger is necessary step in creating a rule. The Command Center offers a number of trigger types, which give the the ability to cross-sell and upsell at every possible intersection of data that your data supports.
Please see the Triggers page for more details.
The following section adjust what happens to the rule based on the context of the user’s current state.
Continue to apply the rule as user selects additional filters
If checked, this rule will apply at the trigger state, and additional navigation and searches will keep this rule firing. If a user searches for PS3 and navigates by $200-300, this rule will follow them around and continue to apply the PS3 themed page as well as PS3 themed upsells.
You should check this box if you expect additional filters to be applied behind the scenes by your web application.
Apply user selected filters to query zones
If checked, all of the zones that populate based on a query will also update as the user navigates. For example if you are cross promoting a headset for the PS3, when the user navigates by $200-300, only headsets that fall within that price range will be displayed.
The percentage of traffic that will be sent to this rule. For example, you may only want to send 50% of traffic to one rule, and create a second similar rule that upsells something slightly different or uses a different layout, and then compare conversion rates. Note, the last rule of an A/B test should be set to 100% of traffic. For example, if you are doing a 50 / 50 split, the first rule should be set to 50% and the second rule should be set to 100% so that it catches all the requests that didn’t hit the first rule.
Start Date and End Date
A start date and end date determine when the rule will begin firing and when it will end. The time is specified in UTC so that the trigger does not change due to Daylight Savings.
Your web application must fetch from the GroupBy service with each user request, with a unique
If you have a cache - and don’t fetch the latest state - then you cannot use the A/B split. Similarly, if you cannot pass in the
sessionId as part of the Search query, the service can’t split the traffic accurately.
Pick the Biasing Profile - the profile sets the business rules to boost and bury products - to apply to the search results that this rule is applied to. You can create new Biasing Profiles under the Engine Configuration section of Command Center.
Pick the Match Strategy - how many words must match within the search query - on the searches that this rule is applied to. You can create new Match Strategies under the Engine Configuration section of Command Center.
The field you want to sort by based on the sort order. The field is from the list of sortable fields in the config file from the data upload. For example, if you want to sort by price, you’ll need to know the field name for price - e.g. it could be
item.price. Then the Sort By box would hold
Sort By with Visual Rule Binder
The order in which the field is sorted; either sorted in ascending or descending order.
Possible values are:
It is either in lexographic or numerical order depending on the field type from the config file. The sort order overrides the relevance order normally returned by search.
Relevancy is always the last tie-breaker sort.
Inject Additional Filters
A post-filter can be applied to a query when the rule is fired. You can apply Navigation Value and Search queries as additional filters to the results.
Read more about Injected Filters
Push To Top
You can push specific products to the top of the results by using their record ID.
The order that you use within this section will be the order of the products in the response.
There is a limit of 300 ids that can be added to the list. If you exceed the limit, the following error will appear when saving the rule:
Bring to top limit of 300 exceeded
Caveat with Push to Top when Navigation or Filters is applied
When doing a “Push to Top” the expected behavior is for push-to-top products that are added to appear at the top of the result list for a specific query. These products will be pushed to the top of the list regardless of whether they would have been in the original query set or not.
Push To Top with Visual Rule Binder
If you apply the navigation filter which has the enabled
OR Queries option to the result set, it won’t include
push-to-top-products that were not present in the original results.
Restrict To ID
You can restrict your result set to a specific set of products by selecting them in the Visual Rule Builder or adding the product ID’s in the form view. Only the products selected using Restrict to ID would be returned in the result set. Visual Rule Builder will grey out products to indicate they will not be returned in the result set. You can use Restrict to ID and Sort By ID in combination to filter your result set.
Restrict To ID with Visual Rule Binder
You can control which Dynamic Navigations are shown to your customers based on your merchandising strategy. The Dynamic Navigations must first be set up in the Dynamic Navigation section of Command Center, or by IT through the bulk-upload process. Navigations can be specified by their attribute name, e.g.
variants.size, or using wildcards:
? for a single character match, and
* for multi-character match.
variants.* would return both the Dynamic Navigations for
If no Navigations are defined in the Rule, the set that are defined in Dynamic Navigations will be returned.
The set of Navigations returned can be overridden at query time by the API, using the
You can use pinned refinements to control the order of up to twenty refinements returned when the rule is fired, by defining the values for the refinements you wish to return. This gives you the ability to promote certain brands or styles, as well as enforce a limited manual sort order for sizes or dimensions.
If fewer than twenty refinements are pinned, the order for the remaining refinements will be determined by the existing logic (either by value or count.) Pinned refinements will only be returned if there is at least one record in the results set for that refinement.
You can pick from available Templates, and populate the zones that were defined for each template.
Within each template, you can have additional content - for example, plain text, HTML, or additional searches to bring back.
Please see Templates and Zones for more information.
You can decide if a rule should be promoted when the Area is copied by changing the toggle within the rule screen from
Where Can I Edit This?
You can find the toggle near the
When you promote an Area, it will override the content of the Area that you are copying into. For example, if you copy from Staging into Production, all items in Production will be overwritten with all items that are marked as a
Yes to promote.