GDPR and EPiFind Tracking

Magnus Wallin

Vote:

We've been asked some questions about the tracking that is used when enabling statistics in EPiFind:

/page/in/searchresults/?_t_id=&_t_q=&_t_tags=langu-age:sv,siteid:&_t_ip=&_t_hit.id=/_68d3ab17-d83c-4f64-ae14-288a48d3ffd0_sv&_t_hit.pos=2

These are visible on links in the search results whenever we enable the Track clicking:

SearchClient.Instance.Statistics().TrackQuery(...)
SearchClient.Instance.Statistics().TrackHit(...)

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?

#193323

May 29, 2018 9:23

Son Do

Vote:

We can confirm that this is a Find tracking bug. It will be fixed and released soon.

Thank for your contribution.

/Son Do

#193851

Jun 06, 2018 6:14

Thomas Wolff

Vote:

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?

#193989

Jun 11, 2018 8:39

Son Do

Vote:

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

#195372

Jul 22, 2018 5:20

Magnus Wallin

Vote:

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.

#196815

Sep 12, 2018 12:16