Today just one single database can be connected with campaign as consumer endpoint. So, if we want to send a specific audience to a single database is only possible to the Database that is already connected and, in some cases, use a different database is needed. Per example: A ConversionAbandonment event from tealeaf can be sent directly to a new database to create different types of actions (that is different to the cartAbandonment event that send the data to an RT). Today I need to use Toolkit endpoint to download events, parse it into a tsv file, then import the data to a database, create a process or trigger to sent it to campaign (or also an FTP import to send it diary).

This can be more more simple if just create a new Application access token, and the endpoint put the ID of the database and send the data directly. And dont't need any local integration or installation.