Best practices

Always consider if you intend to communicate or segment based on the data you intend to store. The amount of rows should not grow indefinitely. Perform data deletion cleanups of your data tables or update existing rows for several reasons:

• Data quickly becomes irrelevant for communication and segmentation, either new data is added or simply with time passing.
• GDPR requires personal data not to be stored after it is no longer needed
• The more data you have stored the slower the system will be going through all information.

One-to-Many Data Tables#

One-to-many tables are designed for storing multiple rows of data per recipient that you will use for personalisation – either in segmentation or content in communication. This also means that one-to-many data should not be used for reporting or activity logging. Always consider if you intend to communicate or segment based on the data you intend to store.

• Keep the number of rows per recipient, per one-to-many table within the 50-100 range.
• Do not store unnecessarily large amounts of static texts (such as product description) – consider using a lookup.
• Only keep relevant data – perform regular cleanups.

Global Data Tables#

As a general guideline, the amount of rows stored in your Global Data Table should not be dependent on your total recipient count. Common use-cases include tables of Products, Articles and Locations. As more recipients are added to your environment, the size of your Global Data tables should not be affected.

• We recommend keeping the amount of rows below 1 million per table.
• Only keep relevant data – perform regular cleanups.