Currently, we can only search archive by using a session attribute or an event. This has become problematic. Sometimes we need to search for specific text where an event or session attribute doesn't exist. Because of this limitation, we cannot find the sessions. Here are a couple examples:

1. We had a situation where we needed to purge the archive where there was a specific cookie. If that cookie appeared, we needed those sessions purged. We were able to find the sessions in our Active/Completed storage using FTS and purged the impacted data, but we were unable to do this for archive. We opened a ticket with support to address this, but to date, there isn't a solution. Being able to search archive for free text, would have addressed the problem in 30 min vs the two months we've been waiting for engineering.

2. Our business partners asked to see when a particular error message started to occur and if any customers who had completed an order had seen that message. We didn't have any events or session attributes for that error message so we were unable to meet address their request.

Having the ability to perform FTS in archive, gives us a safety net when we need to find something in archive where an event or session attribute was not created. Without it, we are unable to meet our internal customer needs.