# Use Offer Attributes to Enhance Catalog Filtering

**LFS version requirement:** v12.22 or later

In the past, the Limio for Salesforce rules builder had limitations on the number of attributes you could specify as Subscription Criteria to match the rule based on the current subscription. With this enhancement, you now have the flexibility to create more precise and granular filtering rules by incorporating any Limio offer attribute - standard or custom - into the rule criteria.

This new feature introduces a dedicated section at the bottom of the Subscription Criteria component, called Subscription's Offer Criteria. Much like in the Configure Offer Filters panel on the right side of the screen, you can effortlessly choose filters from the dropdown menu in the new section and define the specific values that the rule should match.

<figure><img src="/files/7RdYKBEG0FwJynnq1KQ1" alt=""><figcaption></figcaption></figure>

For instance, consider the rule depicted in the screenshot above. It is designed to match an active subscription linked to an offer with a Net 30 Zuora Payment Term. Consequently, the offer catalog will be pre-loaded with the Zuora Payment Term filter, along with two pre-selected values: Due Upon Receipt and Net 60.

This functionality ensures a more nuanced and effective rule application process. It empowers the agents to present the optimal option tailored to each customer's specific case. By honing in on such precise entry criteria, we can significantly enhance the quality of suggestions for future offers to the customer.

### Improvements

In version **12.34 or later**, we introduce the ability to create multiple rules that have the same subscription criteria but different subscription offer attribute criteria. This means that you can define different sets of attributes for different rules, allowing for more flexibility in how you prioritise and manage subscriptions.\
\
When multiple rules match current subscription, the system will evaluate the number of attributes of each rule to determine which one has the most matching attributes. The rule with the highest number of matching attributes will be given higher priority. Let's say you have two rules with the same subscription criteria, but different attribute criteria. Rule A has three matching attributes, while Rule B has five matching attributes. In this case, Rule B will be given higher priority because it has more matching attributes.

### Dynamic Offer Filtering Using Salesforce Attributes

**LFS version requirement:** v13.70 or later

<figure><img src="/files/VQlOCf1lBDgER463EvSk" alt=""><figcaption></figcaption></figure>

In addition to filtering offers using static attribute values, Offer Filtering Rules now support **dynamic values sourced directly from Salesforce records**. This allows offer availability to adapt automatically based on the record data of the customer currently in context.

This enhancement is particularly useful for scenarios where offer eligibility should reflect Salesforce data such as country, labels, codes, etc.

#### **Configuration**

To enable **dynamic offer filtering based on Salesforce attributes**, record id must be passed to the Offer Catalog component

<figure><img src="/files/djGcyf0rksZ8DHJ57p9H" alt=""><figcaption></figcaption></figure>

#### Notes:

**Country-Based Filtering:** When filtering offers by country using Salesforce attributes use country code field rather than free-text country name

### Related articles

[Offers Configuration](/integrations/setting-up-limio-for-salesforce/filtering-rules.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.limio.com/integrations/setting-up-limio-for-salesforce/filtering-rules/offer-attributes-filtering.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
