Changelog

Your feedback is important to us!

Tell us how we can make the product more useful to you.

Subject Communication Notification

When a new message is received from a data subject, the current notification is just to have that request highlighted in the queue for the person it was assigned to. It would be great to instead have a symbol like a filled in circle near the request to indicate there is a communication so that everyone that has access to the queue can see there is a new message instead of just the person it was assigned to. If you were to keep the highlighting that could work as well but then the suggestion would be to add an option to the request to mark the communication as read. Having the mark as read option would help users accessing the queue (not just the assignee) to be able to see that there is a message that needs to be read. Thank you!

Samantha Beyer 24 days ago

For DSR, we need the pre-built System tiles to have variable results

we have multiple systems and depending on the results of each system, we might have a different communication that we could send our data subjects. we are using pre-built automation tiles and it provides a success result in the success field but we can’t use that field to automate our communications. we would like to have the automation results a variable that we can use to tie to our conditions and completely automate our DSR process.

Dustin Jackson 25 days ago

Show Jurisdiction Based on IP Geo

Given that the platform chooses the jurisdiction based on the IP geo, and given that the jurisdiction (and the law under which the right is being invoked) is not being chosen based on the country/state the data subject may enter, I think it would be good to show to data subjects, which law is being used (which law the right being requested is being invoked under).

Richard Gibbs About 2 months ago

Collect Identity Space Values via Javascript

Currently, when configuring a property within the platform, the only available options to retrieve the space value are “General Variable“, Local Storage, Cookie, etc. However, *many* third party integrations that land on the page do not make this information easily available or accessible; and even if it is available, it’s likely not in a format that Ketch is ready to parse. As an example, integration (vendor) X provides an identity space *only through javascript reference*, meaning that `integration.identify()` needs to be called on the page, which might return a payload such as `USER_ID_NEEDED##SOME_ORG_ID` Currently, this poses two challenges; not only can `identify()` not be called, but even if it could, Ketch doesn’t provide any utility to deconstruct a payload such as using `value.split(“##”).at(0)`. Currently, this leads us to have to engage an internal team to create a new variable/cookie/storageVar etc, which duplicates data and incurs additional integration time. Ideal state would be to have another option(s) that allows for us to simply execute JS on-page to fetch the variable we need, and then another option(s) to manipulate that fetched result. Or something similar.

Ryan Burdett About 2 months ago