This section details the principles for using a custom (or external) recipient table.
By default, Adobe Campaign offers a built-in recipient table to which out-of-the-box functions and processes are linked. The built-in recipient table has a number of predefined fields and tables that can be easily extended using an extension table.
If this extension method offers good flexibility to extend a table, it does not allow the number of fields or links in it to be reduced. Using a non-standard table, or ‘external recipient table’, allows for a greater flexibility but requires certain precautions when implementing it.
This functionality allows Adobe Campaign to process data from an external database: this data will be used as a set of profiles for deliveries. Implementing this process involves several precisions that may be relevant according to the client’s needs. Such as:
This section describes the key points that let you map existing tables in Adobe Campaign and the configuration to apply to execute deliveries based on any table. Finally, it describes how to provide users with querying interfaces as practical as those available with the built-in recipient table. To understand the material presented in this section, good knowledge of the principles of screen and schema design is required.
Using a custom recipient table has the following limitations:
Adobe Campaign does not support multiple recipient schemas, know as targeting schemas, linked to the same broadlog and/or trackinglog schemas. This can otherwise lead to anomalies in data reconciliation afterwards.
The graphic below details the required relational structure for each custom recipient schema:
You cannot use the standard Services and Subscriptions offered in the product.
This means the overall operation detailed in this section is not applicable.
The link with the visitor table does not work.
Thus, to use the Social Marketing module you must configure the storage step to reference the correct table.
Similarly, when using referral functions, the standard initial message transfer template must be adapted.
You cannot manually add profiles in a list.
Therefore, the procedure detailed in this section is not applicable without an additional configuration.
You can still create recipient lists using workflows. For more on this, refer to Creating a profile list with a workflow.
We also recommend checking the default values used in the different out-of-the-box configurations: depending on the functionalities used, several adaptations must be carried out.