Using a custom recipient table
When designing your Adobe Campaign data model, you can use the out-of-the-box Recipient table , or decide to create a non-standard recipient table to store you marketing profiles.
Indeed, if your data model does not fit the recipient-centric structure, you can set up other tables as the targeting dimension within Adobe Campaign. For example, this can be relevant when you need to target households, accounts (like mobile phones) and companies/sites rather than simply recipients.
In this case, you will need to create a new target mapping .
All the principles and steps needed when using a custom recipient table are detailed in this section .
The benefits of using a custom Recipient table are as follows:
Flexible data model
The out-of-the-box Recipient table is useless if you do not need most of the Recipient table fields, or if the data model is not recipient-centric.
Large volumes require a streamlined table with few fields for an efficient design. The out-of-the-box Recipient table would have too many useless fields, which could impact performance and lack efficiency.
If data resides on an external existing marketing database, it may require too much effort to use the out-of-the-box Recipient table. Creating a new one based on an existing structure is simpler.
No maintenance is needed to check that all extensions are still valid upon upgrade.
Using a custom recipient table is reserved for advanced users and is subject to some limitations. For more on this, see this section.