> 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/suggest-integration/suggest-integration-best-practices.md).

# Suggest Integration Best Practices

## Summary

This article outlines practical recommendations for integrating the FactFinder Suggest module. These best practices help users find products faster and create a smoother search experience.

These are general guidelines. Use the ones that best fit your shop and product domain.

## Enhancing User Experience and Usability

The primary goal of Suggest is to make searching easier and faster. Focus on intuitive interaction:

* **Support multiple selection methods** — Let customers select suggestions with both the mouse and the keyboard. This improves accessibility and supports different browsing styles.
* **Clearly highlight the current selection** — Make the focused suggestion visually distinct, for example with a contrasting background or bold text. This gives users clear feedback while they move through the list.
* **Emphasize the matching part of the term** — Highlight the characters or words that match what the user has already typed. This makes the suggestion feel more relevant and easier to scan.
* **Offer autocomplete for the top suggestion** — Consider completing the search input automatically with the most relevant suggestion. Users can then accept it quickly with `Tab` or `Enter`.

## Optimizing Visual Design and Layout

A seamless integration into your existing shop design is crucial for a professional look and feel:

* **Maintain a unified color scheme** — The Suggest dropdown should match your shop’s overall color palette and branding. Consistency makes the experience feel more polished and trustworthy.
* **Align the dropdown closely with the search box** — Keep the visual gap between the search field and the suggestion list as small as possible. The list should feel like a natural extension of the search box.

## Leveraging Functional Enhancements and Behavior

* **Use preview images wisely** — If product imagery stays clear at a small size, preview images in the suggestion list can improve recognition. Usually, the first product image associated with the search term is used. For brand suggestions, brand logos can work well too.

  Images increase the overall size of the suggestion dropdown, potentially reducing the number of visible suggestions. Balance visual appeal with information density.
* **Include non-product suggestions when useful** — FactFinder [Campaign Manager](/integration/campaign-specific-integration.md) can direct users to relevant content pages such as terms and conditions, legal pages, buying guides, or catalog pages. If you want those terms to appear as suggestions, add them through the appropriate whitelist.
* **Use direct navigation for specific suggestion types** — By default, selecting a suggestion runs a search for that term. If a suggestion clearly refers to a specific product, consider linking directly to the product detail page. For brand or category suggestions, link to the matching landing page or a pre-filtered result page. These behaviors are often configurable in FactFinder response templates. For custom implementations, check with your FactFinder contact.

## Prioritizing Performance

* **Aim for fast suggestion display** — Suggestions should appear almost instantly as the user types. Delays reduce the value of the feature and can frustrate users.
* **Keep the suggestion list focused** — Avoid overwhelming users with a long list. Show a concise set of relevant suggestions, such as 5 to 10 items, and prioritize the most likely matches.

## Visual Examples of Suggest Implementation

![suggest\_intergation\_example1](/files/xSkRJH7dEnvU4nokZXDH) ![suggest\_intergation\_example2](/files/0HiBXLffEX8IlSR4w5vY)


---

# 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/suggest-integration/suggest-integration-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.