From the Preview Pages, you can set the rule to run for an exact path or for a specific category page.
Quick reference
The following table lists the available user location trigger settings.
Table 1: User location settings
| Option | Description | Use for |
|---|---|---|
| contains | The rule triggers for all locations and navigation paths that contain the ID* of the current location. | Use this setting to run rules for a chosen facet selection or a chosen category and any subcategories under it, regardless of navigation path. |
| ends with | The rule triggers for all navigation paths that end with the ID* of the current location. | Use this setting to run rules on a chosen category page or facet selection only, regardless of the navigation path. |
| equals | The rule triggers only for the specified complete navigation path. | Use this setting to run rules on a chosen page, after a specific navigation path. |
| starts with | The rule triggers for all navigation paths that begin with the ID* of the current location. | Use this setting to run rules for a chosen facet selection or a chosen category and any subcategories under it, if the location was reached through a specific navigation path. |
* Every category, facet, and other attribute used for navigation purposes has an ID that lets FHR uses to recognize it and the various navigation paths to it uniquely. As a result, the following navigation paths are considered to be different although they might list identical content: Home > Women's > Shoes > Size 37 and Home > Shoes > Women's > Size 37.
Rule runs at chosen locations
Based on where you want your rule to run, complete the configuration steps in Table 2. For reference about how the operation looks in the UI, see Figure 1 and Figure 2.
Table 2: Setting locations for the rule
| Where should the rule run? | Configuration steps |
|---|---|
| Rule runs on the Home page only |
|
| Rule runs everywhere in the catalog | Don't create a user location trigger. |
| Rule runs on a chosen category page, after a specific navigation path |
|
| Rule runs for a chosen category page and any subcategories and facet selections under it, if the location was reached through a specific navigation path |
|
| Rule runs for a facet selection or a chosen category and any subcategories under it, regardless of navigation path |
|
| Rule runs on a chosen category page or facet selection only, regardless of the navigation path |
|
Rule doesn't run at chosen locations
If you want for your rule to trigger everywhere but at specific locations, complete the configuration steps in Table 3. For reference about how the operation looks in the UI, see Figure 1 and Figure 2.
Table 3: Setting location exceptions for the rule
| Where should the rule run? | Configuration steps |
|---|---|
| Rule doesn't run on the Home page but triggers everywhere else |
|
| Rule doesn't run on a chosen category page, for a chosen navigation path |
|
| Rule doesn't run for a chosen category and any subcategories and facet selections under it, if the location was reached through a specific navigation path |
|
| Rule doesn't run for a facet selection or a chosen category and any subcategories under it, regardless of navigation path |
|
| Rule doesn't run on a chosen category page or facet selection, regardless of the navigation path | Navigate to the category page, click Create New, and select the type of rule that you want to create.
|
Rule runs at some locations but doesn't run at others
Create two user location triggers---one that lists the locations where the rule must run and one that lists the exceptions. Complete the respective configuration steps from Table 2 and Table 3.
Comments
0 comments
Please sign in to leave a comment.