Site Search Terms #164
Replies: 6 comments 23 replies
-
+1 for this feature. |
Beta Was this translation helpful? Give feedback.
-
+1 I'd love to have this on https://www.napari-hub.org/ We briefly considered adding search terms as custom data, but did not pursue this b/c we don't want someone to accidentally paste PII or other sensitive info in the search box. It would be 💯 if plausible could offer a special search event and aggregate on the dashboard something akin to Algolia's Out-of-the-box Search Analytics, with some guardrails to prevent sensitive data from bleeding through
|
Beta Was this translation helpful? Give feedback.
-
I think Site Search Metrics is an important feature to have. This is fundamental for many applications that have search as a primary user interface. I'm currently evaluation a web tracking tool for use in my startup's app, and this is the main limitation I see with Plausible. While it is possible to implement this myself, this isn't my core business and would be nice to have this prebuilt like others including Matomo, Algolia as mentioned above and others |
Beta Was this translation helpful? Give feedback.
-
+1 for the feature. As this is a must-have for one of our clients we now have to work with matomo instead plausible. Would love to see this soon and switch 👍🏻 |
Beta Was this translation helpful? Give feedback.
-
We'd like to support this out of the box in the future. In the meanwhile you might be able to use the new feature we released to get search terms too. See https://plausible.io/docs/custom-query-params |
Beta Was this translation helpful? Give feedback.
-
Hey all, we are thinking about tackling this one soon. I'd like to get everyone's feedback on the plan. I've divided site search terms in two phases based on the readiness of our backend. Phase one can be completed with relatively little changes to the backend, whereas phase 2 relies on some improvements we need to make to the database schema and the UI. For now, we are just considering building phase 1. More advanced stuff is not really on the short term horizon at the moment. Phase 1 <script src="https://plausible.io/js/plausible.search.js"></script> When this script extension is loaded, and the page has a special query parameter defined, then a custom event is automatically triggered. The event is called <script data-search-param="q,query" src="https://plausible.io/js/plausible.search.js"></script> In the UI, it would be a custom event Phase 2 I guess the the canonical example would be Algolia/Typesense. Here's how you can hook into their search results: https://www.algolia.com/doc/api-reference/widgets/analytics/js/#plug-with-kissmetrics Being able to track results opens up much more advanced insights like 'Top keywords with no results'. Or just 'Top results'. You could invert the question and ask 'Which search terms lead to this result most often?'. Even more advanced would be tracking clicks on results. This allows things like 'average result click position' etc. The video on this link is a wonderful example of really advanced analytics that can be done on search in Algolia. This would probably require a specialized UI for Search Analytics. Unfortunately doing these things is not currently possible for the same reason as this: #929. We definitely have to remove this limitation in the future but it's only needed when we want to go to phase 2 of search analytics. |
Beta Was this translation helpful? Give feedback.
-
"It would be very helpful to be able to see the search terms users are using on your websites built in search. This is particularly helpful on ecommerce sites. I am talking about the search terms people use on my site. Not the ones they used in google to get to my site. For example, the search bar on an ecommerce site that people use to located a product.
It’d be interesting to connect this with the existing goals feature. E.g. allow the goals to have arguments."
Update: We'd like to support this out of the box in the future. In the meanwhile you might be able to use the new feature we released to get search terms too. See https://plausible.io/docs/custom-query-params
Beta Was this translation helpful? Give feedback.
All reactions