Try our conversational search powered by Generative AI!
AI OnAI Off
GDPR and EPiFind Tracking
We can confirm that this is a Find tracking bug. It will be fixed and released soon.
Thank for your contribution.
/Son Do
Jun 06, 2018 6:14
What information is EPiServer Find storing to support the statistics listed on /EPiServer/Find/#manage/statistics? Are IP-adresses stored when not using tracking as well?
Jun 11, 2018 8:39
Hi Thomas,
Currently tracking data was minimum and was only used for statistics. For example, search keyword that client typed in search textbox, what's in search result that client clicked on,...
"IP-adresses stored when not using tracking?" - For your question, the answer is yes in history, no for now.
And for supporting GDPR, we already had a task for creating new APIs that query all information we tracked. So please wait for that.
Hope this help.
/Son Do
Jul 22, 2018 5:20
Any news regarding bugfixing this issue? I've tried to follow the releases for Find but couldn't track any changes back to this particular issue.
Sep 12, 2018 12:16
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
We've been asked some questions about the tracking that is used when enabling statistics in EPiFind:
These are visible on links in the search results whenever we enable the Track clicking:
The main issue here is the namespace and the IP-adress which can, contain sensitive information and our customer asked us to remove at least the IP-address. But this will break the tracking.
Can we send the trackingdata on the backend side in some programatic way so we can keep the URL clean? One idea was to make an async call to the above URL after user clicked but wondered if there was a more elegant way?