WebApp
Zivver Insights report
Insights report
The Zivver Insights report provides in-depth information about Zivver usage in your organization. The exact significance of every possible entry in the report is explained in the table below:
Zivver messages
zivver_messages
contains a row for each Zivver message sent by a user in the organization
Column | Description | |||
---|---|---|---|---|
zivver_message_id | A unique identifier for the Zivver message | |||
conversation_id | A unique identifier for the Zivver conversation that the message appears in | |||
sent_at | The date and time at which the message was sent | |||
rank_in_conversation | The rank of the message in the conversation (first, second, third, etc.) | |||
original_sender_account_id | The account identifier of the user that sent the message. If the message was sent through an access delegation (i.e. via a functional account), this is the user to which access was delegated. Normally this would NOT be the functional account but the user that logged into it. | |||
original_sender_organizational_unit_name | The organizational unit of the original sender | |||
original_sender_email_domain | The email domain of the original sender | |||
is_sent_by_delegated_user | A boolean indicating whether the message was sent via an access delegation | |||
delegated_sender_account_id | The account identifier of the functional account through which the message was sent in case it was sent through an access delegation | |||
is_revoked | Whether the message has been revoked | |||
revoked_at | When the message was revoked, if applicable | |||
revoke_action | What action was taken when revoking the message. Either Revoke or Delete, respectively meaning revoking for only recipients or revoking for everyone. | |||
revoke_type | The type of revoke. Either Manual or Scheduled, respectively meaning revoking immediately by user action or upon a schedule previously set by the user or the organization’s policy. | |||
submission_method | How the message was submitted to Zivver, either via API or via our SMTP component | |||
zivver_client | Which Zivver client was used to send the message | |||
zivver_client_version | What version of the Zivver client was used to send the message | |||
total_number_of_attachments | The number of attachments attached to the message | |||
total_attachment_size_bytes | The total size of all attachments combined, in bytes | |||
total_attachment_size_megabytes | The total size of all attachments combined, in megabytes | |||
total_attachment_size_segment | The total size of all attachments combined, divided into discrete segments | |||
is_message_to_self | A boolean indicating whether the message has no recipients other than the sender | |||
number_of_recipients | The number of recipients of the message, excluding the sender | |||
has_external_recipient | Whether the message had any recipients that are not part of the same organization as the sender, nor on any of its trusted domains | |||
is_decrypted_by_any_recipient | Whether the message has been decrypted by at least one recipient. Every opened message must have been decrypted. A message may have been decrypted without having been opened by the recipient, in case they use a Zivver product that automatically decrypts incoming messages. |
Zivver message recipients
zivver_message_recipients
contains one row per message recipient. One message may have multiple recipients, meaning that one message may correspond to multiple rows in this table.
Column | Description |
---|---|
zivver_message_id | A unique identifier for the Zivver message |
original_sender_account_id | The account identifier of the user that sent the message. If the message was sent through an access delegation (i.e. via a functional account), this is the user to which access was delegated. Normally this would NOT be the functional account but the user that logged into it. |
sent_at | The date and time at which the message was sent |
recipient_account_id | The account identifier of the recipient of the message |
recipient_account_type | The type of account that the recipient has, either Guest, Personal or Business |
is_guest_recipient | A boolean indicating whether the recipient is a guest recipient |
is_internal_recipient | A boolean indicating whether the recipient is part of the same organization of the sender, or any of its trusted domains |
recipient_email_domain | The domain of the recipient |
verification_method | The verification method used for this recipient |
is_decrypted | A boolean indicating whether the message has been decrypted by this recipient. Every opened message must have been decrypted. A message may have been decrypted without having been opened by the recipient, in case they use a Zivver product that automatically decrypts incoming messages. |
decrypted_at | The date and time at which the message was decrypted, if any |
hours_to_decryption | The number of hours between sending and decryption of the message |
Messages
messages
contains a row per email message. This could be a Zivver message or a non-Zivver message. For non-Zivver messages to appear in this overview, the plug-in setting to log non-Zivver messages must be enabled.
Column | Description |
---|---|
message_id | A unique idenifier for the message |
sent_at | The date and time at which the message was sent |
zivver_message_id | A unique identifier for the Zivver message, if the message is a Zivver message |
original_sender_account_id | The account identifier of the user that sent the message. If the message was sent through an access delegation (i.e. via a functional account), this is the user to which access was delegated. Normally this would NOT be the functional account but the user that logged into it. |
original_sender_organizational_unit_name | The organizational unit of the original sender |
original_sender_email_domain | The email domain of the original sender |
is_delegated | A boolean indicating whether the message was sent via an access delegation |
delegated_sender_account_id | The account identifier of the functional account through which the message was sent in case it was sent through an access delegation |
is_sent_securely | A boolean indicating whether the message was sent securely with Zivver or as a normal email |
can_client_send_normal_email | A boolean indicating whether the client used to send this message can also be used to send normal emails |
is_opted_in_to_log_normal_email | A boolean indicating whether the user that sent this message is opted in to log normal emails to Zivver |
is_logging_normal_email | A boolean indicating whether both the client also sends normal email AND the sender is opted in to log normal emails to Zivver |
zivver_client | Which Zivver client was used to send the message |
zivver_client_version | What version of the Zivver client was used to send the message |
number_of_attachments | The number of attachments attached to the message |
is_message_to_self | A boolean indicating whether the message has no recipients other than the sender |
number_of_recipients | The number of recipients of the message, excluding the sender |
has_external_recipient | Whether the message had any recipients that are not part of the same organization as the sender, nor on any of its trusted domains |
is_rule_triggered | Whether the message has triggered any wordlist or sensitive identifier rules enabled by the organization |
is_wordlist_rule_triggered | Whether the message has triggered any wordlist rules enabled by the organization |
is_sensitive_id_rule_triggered | Whether the message has triggered any sensitive identifier rules enabled by the organization |
number_of_rules_triggereds | The number of triggered wordlist or sensitive identifier rules enabled by the organization |
number_of_wordlist_rules_triggered | The number of triggered wordlist rules enabled by the organization |
number_of_sensitive_id_rules_triggered | The number of triggered sensitive identifier rules enabled by the organization |
Message triggered rules
message_triggered_rules
contains a row for each rule triggered by a message. Contains only rules enabled by the organization. One message may trigger multiple rules.
Column | Description |
---|---|
message_id | A unique idenifier for the message |
sent_at | The date and time at which the message was sent |
zivver_message_id | A unique identifier for the Zivver message, if the message is a Zivver message |
is_sent_securely | A boolean indicating whether the message was sent securely with Zivver or as a normal email |
can_client_send_normal_email | A boolean indicating whether the client used to send this message can also be used to send normal emails |
is_opted_in_to_log_normal_email | A boolean indicating whether the user that sent this message is opted in to log normal emails to Zivver |
is_logging_normal_email | A boolean indicating whether both the client also sends normal email AND the sender is opted in to log normal emails to Zivver |
rule_category | The type of rule, either ‘Sensitive Word List’ or ‘Sensitive ID’ |
rule_identifier | The identifier of the rule triggered, generally the name of the wordlist or identifier |
violation_level | The violation level set for the triggered business rule, either ‘Suggestion’, ‘Warning’ or ‘Error’ |
Sender statistics
sender_statistics
contains one row per account in your organization with key performance metrics over the period selected on the dashboard
Column | Description |
---|---|
original_sender_account_id | The unique identifier of the account |
email address | The primary email address associated to the account |
messages_sent_with_zivver, | The number of messages sent with Zivver |
messages_with_rule_triggered | The number of messages (Zivver or non-Zivver) sent that had at least one rule triggered. Only includes messages where non-Zivver messages were also being logged, to ensure the % sent with Zivver is computed correctly. |
zivver_messages_with_rule_triggered | The number of Zivver messages sent that had at least one rule triggered. Only includes messages where non-Zivver messages were also being logged, to ensure the % sent with Zivver is computed correctly. |
percentage_of_messages_with_rule_triggered_sent_with_zivver | The percentage of messages with at least one rule triggered that were sent with Zivver. Only includes messages where non-Zivver messages were also being logged, to ensure the % sent with Zivver is computed correctly. |
message_recipients | The number of recipients of Zivver messages. One Zivver message may have multiple recipients. Each counts once. |
message_recipients_with_preferred_verification_method | The number of recipients of Zivver messages using one of the recommended verification methods, i.e. not email verification. One Zivver message may have multiple recipients. Each counts once. |
percentage_of_message_recipients_with_preferred_verification_method | The % of recipients of Zivver messages that are verified using one of the recommended verification methods |
revoked_messages | The number of messages revoked |
Accounts
accounts
contains one row per account in the organization
Column | Description |
---|---|
account_id | The unique identifier of the account |
email_address | The primary email address associated to the account |
is_deleted | A boolean indicating whether the account has been deleted |
is_suspended | A boolean indicating whether the account has been suspended |
is_admin | A boolean indicating whether the account is an admin of the Zivver organization |