# App Search: Exact matching with Precision Tuning
**URL:** https://discuss.elastic.co/t/app-search-exact-matching-with-precision-tuning/354350
**Category:** Elastic Search
**Tags:** elastic-app-search
**Created:** [February 28, 2024, 1:37pm UTC](https://discuss.elastic.co/t/app-search-exact-matching-with-precision-tuning/354350 "2024-02-28T13:37:42Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@StefanHeijden](https://discuss.elastic.co/u/StefanHeijden)
#### Post date: [February 28, 2024, 1:37pm UTC](https://discuss.elastic.co/t/app-search-exact-matching-with-precision-tuning/354350/1 "2024-02-28T13:37:42Z")
We are trying to tweak our search results using precision tuning. In the image we have set the precision tuning to 11. We we then search for parts of words, like "Koni" or "Konin" or even "Koningi", we find nothing. As expected.
However, when search for "Koning" we match on "Koning" but also on "Koningin", which is not an exact match. Why is this the case, even with precision tuning set to 11?
We have a use case such that "Koningin" should not be found when searching for "Koning".
We have found some possible solutions on the web using multi-fields, however, multi-fields are not available in App Search.
We use App Search.
Engine settings:
Language: Dutch
Synonyms: None
Curations: None
Keywords:
Full word matching, Precision tuning, Search results
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 27, 2024, 1:38pm UTC](https://discuss.elastic.co/t/app-search-exact-matching-with-precision-tuning/354350/2 "2024-03-27T13:38:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.