## Background In some recommendation scenarios, users filter the results based on their preferences, seeing only the filtered recommendations. In this case, the platform can configure dynamic filtering based on the dynamic filtering feature. When calling the recommendation service API, it returns the filtered attribute values to complete the dynamic filtering. This document guides you through configuring the dynamic recommendation scope and implementing this feature via API calls. ## Notes :::warning \*Note 1. The system **does not perform mutual exclusivity checks**. You must ensure the filtering logic is correct during configuration. If there are mutually exclusive conditions, the system will not trigger an error, but it will result in **empty recommendation results**. 2. If an item in your dataset is missing a field specified in your filters, the system will **automatically ignore** that specific filter for that item. or more information, see [Automatic ignore logic](/docs/85296/1791113#545109f8). ::: ## Business scenarios |**Industry** |**Applicable scenarios** | |---|---| |video |Filter by video type (Movies, TV Shows, Documentaries) or regional attributes (e.g., North America, Asia) while a user is browsing.|\ | |![图片](https://p9-arcosite.byteimg.com/obj/tos-cn-i-goo7wpa0wc/5f9d2290a041459998ed8b0f4058af77 =2228x) | |e\-commerce |Filter by specific brands or dynamically adjust the visible price range based on a user's loyalty points or membership tier.|\ | |![图片](https://p9-arcosite.byteimg.com/obj/tos-cn-i-goo7wpa0wc/2eb3c67bdf7d4f07865ac0a7668fdca7 =2330x) |\ | | | ## Configuration steps 1. **Create or edit filter rules:** In [Recommendation Experience Interface] \- [Strategy] \- [Scope] \- [Define Recommendable Items], create new filter rules. You can also edit existing filter rules and add dynamic filter conditions.

2. **Configure filter fields:** Use [Rule Configuration] to set the fields you want to filter. Combine filtering conditions based on item fields using AND/OR logic, supporting custom configuration of fields, operators (includes/excludes/RANGE, etc.), and values. |**Configuration item** |**Description** | |---|---| |Logical operator |Select condition combination logic (AND requires all conditions to be met, OR requires any condition to be met). | |Filter field |Select the target field within the item dataset.|\ | |:::tip \*Description|\ | |Filter fields only support those set as "filterable"|\ | ||\ | |:::| |Condition type |select match rules (such as contains (in), does not contain (not in), numeric range comparison, etc.) | |Condition value |enter matching values (use commas to separate multiple values; enter numbers directly for numeric fields) | 3. Click the gray "Dynamic Parameter" in the condition value input box to configure. The platform supports selecting multiple item attributes for dynamic filtering, allowing you to configure OR/AND relationships between multiple item attributes. Dynamic parameters act as "placeholders." You do not need to enter specific values here; the actual value is passed dynamically for each request.

4. Save configuration. :::tip \*Note Dynamic filter configuration cannot be experienced on the platform; Dynamic parameter values must be passed through the API to see dynamic filtering effects. ::: 5. If you want to experience dynamic filtering, select the configuration and "Sync changes to API" to activate it. You can experience dynamic filtering by calling the API interface.

--- ## API request Dynamic filtering depends on passing dynamic parameter values when requesting the recommendation interface. If multiple item attributes are configured, you must pass parameter values for each item attribute during online input. You can include the `filter` field in the request body to pass dynamic parameters. :::tip \*Explanation To learn how online requests return parameter values to the API service, please refer to [Filter](/docs/85296/1788543#db3f2d55) ::: ### Request sample Here is a complete example of sending a dynamic filtering request using cURL. > In this sample, `brand` is the name of your configured dynamic parameter, and `selected_brand` is the actual brand value to filter. ```Bash curl -X POST 'https://recommend.example.com/v1/recommend' \ -H 'Authorization: Bearer ' \ -H 'Content-Type: application/json' \ -d '{ "user_id": "12345", "scene": "homepage_feed", "filter": { "brand": "selected_brand" } }' ``` :::tip \*Explanation replace `` with your actual access token for how to obtain it, see [API Authentication](/docs/85296/1544950) ::: --- ## Dynamic filtering supported scope :::tip \*Explanation The dynamic filtering feature for the **publish time** field and **timestamp** field is currently in public beta to try it, please contact Volcano Engine to activate it for you. ::: |

|

|

|

|

|

|

|

|

|\ |Condition type

|String

|Integer

|Float

|Array

|Boolean

|new release time field

|timestamp field

|Object

|\ | | | | | | | | | | |---|---|---|---|---|---|---|---|---| |

|

|

|

|

|

|

|

|

|\ |Found to

|✅

|\-

|\-

|✅

|\-

|\-

|\-

|Not supported

|\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |Not found to

|✅

|\-

|\-

|✅

|\-

|\-

|\-

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |In range

|\-

|✅

|✅

|\-

|\-

|❌

|❌

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |Less than / earlier than

|\-

|✅

|✅

|\-

|\-

|✅

|✅

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |Less than or equal to

|\-

|✅

|\-

|\-

|\-

|\-

|\-

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |Greater than / later than

|\-

|✅

|✅

|\-

|\-

|✅

|✅

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |Greater than or equal to

|\-

|✅

|\-

|\-

|\-

|\-

|\-

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |Equals

|\-

|✅

|\-

|\-

|✅

|\-

|\-

| |\ | | | | | | | | | | |

|

|

|

|

|

|

|

|^^|\ |Not equal to

|\-

|✅

|\-

|\-

|✅

|\-

|\-

| |\ | | | | | | | | | | --- ## Frequently asked questions When online parameters are abnormal, the platform automatically handles the issue and limits the impact scope. The detailed filtering logic is as follows: |**Scenario** |**Default handling logic** | |---|---| |Online request did not upload parameters |Ignore affected dynamic filter settings; other filter settings (static and dynamic) remain effective|\ | |:::tip \*For example|\ | |the platform is configured with (A found in B) AND (A not found to C), but B is not passed in the request|\ | ||\ | |* **A ** **found** ** ** **in** ** B**: dynamic filter condition does not take effect.|\ | |* does not affect other conditions: (A not found in C) dynamic filter condition takes effect.|\ | ||\ | |:::| |Online request uploaded parameters without values |Same as above | |Recall item missing fields |Filter conditions will **automatically ignore** related filters; see [Automatic ignore logic](/docs/85296/1791113#545109f8) for details. |

Viking AI Search