We have processes in our backend that generate a target audience and personalized information regarding a certain period of time. Even more, a contact may be part of different target audiences in the same day.

In Acoustic, we have recurring jobs and automated programs that manage the information and we've added mobile custom actions and custom inbox templates.

We've had to configure quite a complex workaround to implement our use case. Without using relational tables, we're forced to import that personalized information that is very variable into the contact database. This way, we need to add custom fields in the contact database and update once a day (or more). This also has the limitation that we can't assign more than one personalization to a contact at the same time.

Being able to use information imported into relational tables, personalizing inbox messages would be much easier and more dynamic.