Vulnerability in EPiServer.Forms
"Searches without relevant hits. Searches that generated hits but had a low click-through rate. Phrases that are most frequently searched for and for which search results are clicked the least appear at the top."http://webhelp.episerver.com/17-2/find/statistics-input.htm
A customer is wondering why the search statistics displayed at "Searches without relevant hits" does not seem to update correctly compared with what they see in Google Analytics for search queries. I have tried to understand how it works and in that solution as well as in another customers Find implementation the percentage does not seem update correctly.
I tried this again today and made a search for phrase that I saw had 20% the last month. After doing the search the number of searches was updated from 5 to 6 but the percentage was updated to 0% from 20%. The search did not find any hits at all. Does that affect the percentage or is it a bug in Find? I made another attempt at a phrase that had 25% and 4 searches. After making a search and clicking a result the number of searches was updated to 5 and the percentage again updated to 0% instead of affecting the percentage positively (at least that's how I understand how it should work).
From my search on world.episerver.com and Google in trying to understand this issue, what I can see is that people are referring to a script that should be added to the page and values that should be added to the querystring. It might be that this has worked earlier but have for some reason stopped working in this customer's site.
On https://world.episerver.com/documentation/developer-guides/find/search-statistics/tracking/ it says that "When using Unified Search, Track() enables tracking of a query and its hits. When using Track() on a non-Unified Search, only query tracking is enabled. Use custom tracking (explained below) to track hits with a non-Unified Search." We have not changed the implementation to use TrackHit or TrackQuery so I am wondering if this has changed in a new version and the click-through rate has stopped working because of that?
Have anyone else found this issue? What could be the cause of this?
What is needed to implement click-tracking with a non-unified search implementation of Find? How do I check if everything is in place?
hey, did you solve this? I have the same issue. We use unified search though, so we only use .Track(), and we have implemented the scripts and all that. Still it does not affect the click through.