> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/integration/after-search-navigation/asn-best-practices.md).

# ASN Best Practices

This section shares practical ideas for integrating FactFinder ASN. Treat these points as suggestions, not rules. Use the ones that fit your shop and product range.

## ASN Examples

Below are a few examples of ASN implementations with color filters, icon-based filters, and sliders.

![ASN\_example\_1](/files/abW5TnIDxIBopgdkTB0E) ![asn\_example2](/files/oEapEH4NsvmdxsIrw2S1)

## ASN Design Best Practices

### Place ASN to the left of the search results

ASN should usually appear to the left of the search results. If you place it above the results, users may not see products right away and may need to scroll first.

### Use preview images

You can return and display preview images for individual filter options. These images can help visitors understand the filtered results more quickly.

### Use visual filter elements

Some attributes work especially well as visual filters because users can understand them at a glance. For example, a color filter can use colored symbols. Small icons can also help communicate the meaning of filter elements, such as fit or cut.

## ASN Functions

### Extracting attributes from descriptive texts

If your shop system does not store attributes in a clearly structured way and product characteristics are hidden in descriptions, the Attribute Generator module can help. It extracts relevant attributes from short and long descriptions and prepares the product data for filter-based browsing.

### Simple limitations for numeric groups

There are several ways to handle numeric filter ranges. For example, you can offer predefined price ranges, dynamic ranges, sliders, or input fields. FactFinder also provides the One-Touch Slider, which lets users select a value range by clicking and dragging.

## ASN Usability

### Limit options

Customers should be able to narrow results with useful attributes. At the same time, the number of filters should not overwhelm the page. Limit the available options by defining dependencies between attribute groups or by showing certain groups only when enough results support that filter.

### Use sliders and numeric groups

Numeric groups need a little extra care. For many users, the easiest way to limit a numeric range is with a slider. If you do not want to use one, present clear and logical ranges instead.

### Enable multiple choices

For some attributes, allow multiple selection so users can narrow results more easily.

### Highlight frequently used filter options

Frequently used filters such as category and manufacturer should be easy to find and use. More specific filters such as size or storage capacity can work well as dropdowns.

### Sort filter elements by number of hits

Filter values should usually be sorted by hit count. There are useful exceptions, though. For example, manufacturers often work better in alphabetical order, and clothing sizes should follow a logical size order instead.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.fact-finder.com/integration/after-search-navigation/asn-best-practices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.