Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Created by Guest
Created on Jul 6, 2021

Optimize profile store api delete requests

When working with profile store, there are times that profiles needs to be deleted. At the moment it is only possible to delete them one by one, and the time that request takes is depending on how many profiles the store contain, and how active a visitor has been. If a user is tracked, and one day (by tracking consent or other reason) decides to not to be tracked, we need to remove that user from profile storage.

It would be great if the removal could be done in batches and the removal could be optimized so the request wouldn't take so long (still depends on how many visitors that exists and how active they have been). Keeping a profile storage up to date with visitors that only allow themselves to be tracked is an important issue.