Copernica databases can be layered, allowing you to for example store purchase histories. It's also possible to make selections for segmentation and personalization. Copernica stores a lot of data like clicks, opens, bounces and errors. For this exact reason it's also important that you structure and update your databases correctly, preventing you from creating new databases every now and then.
Inside the Copernica database management you find terms like collection and subprofile. In the purchase history example, you can create a collection of orders. The customer is in this case the profile and the product is the subprofile. You could apply the same principle on for example employees of a company or the children from parents.
Things to consider
The most important thing to consider in your database is the structure. You want your database to be clear and effective. It's also possible to set up rules and restrictions to prevent invalid data from entering your system or sending out unintended mailings.
There is a lot to know about databases, which is why we have documented everything you need to know thoroughly. The following articles will help you build, maintain and export your databases.