An application using this feature may experience additional memory costs due to user profiles being set in an ENEQuery object.

In addition, the application may require additional Java ENEConnection.query() or .NET HttpENEConnection.Query() response time, because the MDEX Engine must do additional work to receive profile information and check if business rules fire. However, in typical application scenarios that set one to five user profile strings of at most 20 characters in the ENEQuery object, the performance impact is insignificant.