Here we'll outline some internals of how we store data in the database. This can be useful for debugging or when you need to create customizations that the offical API does not support (at your own risk).
We do not see the database design as a contract so we might add or change tables/columns in future releases. However, we always try to "append only".
First of all, most tables have a column for
WorkspaceKey this is used when there are multiple Workspaces in use.
Contains the configured Workspaces for a installation.
Contains any configured user access settings.
Contains the built-in mailing lists for the package.
Stores recipients that are added to any of the built-in mailing lists. If you're sending to Umbraco Members this table does not hold any data about them.
Holds information like:
A relation table between nsMailingList and nsRecipient, holds information about which recipient is subscribed (or unsubscribed) from which list.
This table contains all campaigns created. The
status field indicates if it is a draft, if it sending is in progress, or if it's sent.
This table acts as a queue when sending a campaign email and also as a log for statistic reports. It will contain unique recipients for the campaign and any bounce information for that recipient.
Be aware that it's technically possible that one recipient (unique email) is represented in multiple Recipient List Providers used when sending the email. The send-out engine will make sure that only one unique recipient for each campaign is stored here.
Some of the columns:
errorMessage= Contains any error if sending to this recipient failed.
externalId= Could be used by a Email Service Provider to store a unique id for the message.
statusSeattledAlso used by a Email Service Provider to indicate if the status has been seattled. Some providers might need to run backgroun jobs to check the status from a 3rd party. This column can be used to indicate that the status has been seattled and no more checks is needed.
This table stores any interactions from the recipient like open & click. It also stores a URL when applicable (e.g. which URL was clicked).
This tables stores all transactional emails with it's content and settings.
This tables stores a row each time a transactional email is sent. Since a transactional email can be sent to multiple recipients each recipient is stored in
This table holds a row for each unique email sent when sending a transactional email.
This table holds the interactions performed by a recipient of a transactional email.
A key-value store that we use to store random information e.g. about installation.