You can use a custom data schema linked to Recipient when you want to store data in a separate table and link it to the recipient table1.

When collecting data from a web form that includes both identifiable information (such as first and last name) and preferences (such as color preferences), the best practice is to store this information in a custom data schema that is linked to the recipient. This linkage allows the stored data to be associated with a specific recipient, which can be anonymized initially and then identified later if necessary. By using a custom data schema, you can extend the recipient schema to include additional fields without modifying the out-of-the-box recipient schema, ensuring that the database remains organized and scalable for future needs. Reference: This answer is based on best practices for data management in Adobe Campaign Classic and similar marketing automation platforms, which often involve creating custom schemas for additional data collection while maintaining a link to the central recipient or customer schema for proper data association.