Configuring a email in the FCI requires action across both Unica Campaign and Acoustic Campaign. In Acoustic Campaign, email templates and database templates, must be configured, and in Unica Campaign test runs and a final production run must be coordinated.

After the email is sent, responses are routed back to Unica Campaign via Acoustic Exchange and the Exchange Toolkit.

To route response data from Acoustic Campaign back to Unica Campaign, an Exchange Toolkit user (typically the Unica Campaign user) runs scripts. Some organizations automate the scripts so data routing occurs automatically.

You can then use Unica Campaign to retarget responders and non-responders.

Note: Email messages must be sent by configuring message delivery in the Email process box.

Acoustic Campaign concepts unique to the FCI

To support this highly specialized integration, Acoustic Campaign implements two unique database types that can only be used if the FCI is active. The two database types are the database template and the audience database. They can be defined as:

• Database template: A database created in Acoustic Campaign that contains no contacts but instead comprises the column structure used for template personalization, Dynamic Content rule building, etc. This type of database can only ever be flexible/non-keyed, and the only way to create this database type is through the Acoustic Campaign user interface. Existing databases cannot be converted to database templates.
• Audience database: A database that is created by an API request from Unica Campaign and that inherits its list structure from a database template. It is populated with recipient records directly by a data import from Unica Campaign. This is the list that Acoustic Campaign will use to send a message. These are automatically removed from the product 30 days after creation.

Exporting of audience information

When you complete a test run or a production run, the audience database information is exported by Unica Campaign in one special field, campaignaudienceId. Consider the following points about the campaignaudienceId field:

• When contact data is uploaded to the Acoustic Campaign database for the first time, a campaignaudienceId column is added to the database. This campaignaudienceId field is a lookup key.
• After the campaignaudienceId column is added, the audience information is uploaded to this column when contact data is uploaded.
• The campaignaudienceId is included in each event that is sent by Acoustic Campaign to Acoustic Exchange for contacts. For example, emailSend, emailOpen, emailBouce, emailClick.
• You cannot map the campaignaudienceId database column from the Field mappings tab of the Email process. The campaignaudienceId database column is updated internally.
• The format for the campaignaudienceId is AudienceName~#field1Name~#fieldValue~#field2Name~#fieldvalue~#fieldnName~#fieldvalue.

  For example, Customer~#CustomerID~#20.