Analysis systems, systems, information processing devices, and analysis programs

Abstract

This invention provides an analytical system, a system, an information processing device, and an analytical program that can improve the effectiveness of promoting the use of SaaS via email. [Solution] The analysis system 70 is characterized by outputting analysis results regarding emails based on detection results from a tracking system that detects at least one of the following: opening of an email delivered by an email delivery system that delivers emails to users of SaaS provided by a SaaS provider system, and clicking on a link within the email, and the usage rate of the SaaS (S368).

Description

Technical Field

[0001] The present invention relates to an analysis system, a system, an information processing device, and an analysis program for promoting the use of SaaS.

Background Art

[0002] Conventionally, techniques for promoting the use of SaaS by users have been known (see, for example, Patent Documents 1 to 3).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Patent Document 3

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the conventional technology, there is a problem that the use of SaaS cannot be promoted by email. Note that SaaS is an abbreviation for Software as a Service, and refers to a service that allows users to use software provided by a vendor on a cloud server. In the present invention, applications provided on a cloud server are also included in SaaS.

[0005] Therefore, an object of the present invention is to provide an analysis system, a system, an information processing device, and an analysis program that can improve the effect of promoting the use of SaaS by email.

Means for Solving the Problems

[0006] The analysis system of the present invention is characterized by outputting analysis results regarding the email, based on detection results from a tracking system that detects at least one of the opening of an email delivered by an email delivery system that delivers emails to users of the SaaS provided by a SaaS delivery system, and a click on a link within the email, and the usage rate of the SaaS.

[0007] With this configuration, the analysis system of the present invention outputs analysis results regarding emails based on detection results from a tracking system that detects at least one of the following: opening of emails delivered by an email distribution system to users of SaaS provided by a SaaS provisioning system, and clicking of links within those emails, as well as the SaaS usage rate. As a result, senders can be encouraged to improve their emails based on the analysis results, thereby improving the effectiveness of promoting the use of SaaS via email.

[0008] The analysis system of the present invention may divide the users of the SaaS into multiple segments based on their usage rate, and may also show the email open rate for each segment as the analysis result.

[0009] With this configuration, the analysis system of the present invention divides SaaS users into multiple segments based on their usage rate and displays the email open rate for each segment as an analysis result. This allows senders to recognize which emails are more likely to be opened by users in a specific segment, thereby improving the effectiveness of promoting SaaS usage via email.

[0010] The analysis system of the present invention may divide the users of the SaaS into multiple segments based on their usage rate, and may also show the click-through rate of the links for each segment as part of the analysis results.

[0011] With this configuration, the analysis system of the present invention divides SaaS users into multiple segments based on their usage rate and displays the click-through rate of links for each segment as an analysis result. This allows senders to recognize links that are more likely to be clicked by users in a specific segment, and as a result, the effectiveness of promoting SaaS usage via email can be improved.

[0012] The analysis system of the present invention may also show the utilization rate before and after the opening of the email as the analysis result.

[0013] With this configuration, the analysis system of the present invention displays the usage rate before and after email opening as analysis results, allowing senders to recognize emails that are effective in promoting SaaS usage, and as a result, the effectiveness of promoting SaaS usage via email can be improved.

[0014] The analysis system of the present invention may also show the utilization rate before and after the click of the link as the analysis result.

[0015] With this configuration, the analysis system of the present invention displays the usage rate before and after a link click as an analysis result, allowing senders to recognize links that are effective in promoting the use of SaaS, and as a result, the effectiveness of promoting the use of SaaS via email can be improved.

[0016] The present invention is characterized by comprising: a SaaS provisioning system that provides SaaS; an email distribution system that distributes emails to users of the SaaS provided by the SaaS provisioning system; a tracking system that detects at least one of the opening of the email distributed by the email distribution system and the clicking of a link within the email; and an analysis system that outputs analysis results regarding the email based on the detection results from the tracking system and the usage rate of the SaaS.

[0017] With this configuration, the system of the present invention outputs analysis results regarding emails based on detection results from a tracking system that detects at least one of the following: opening of an email delivered by an email distribution system to a user of SaaS provided by a SaaS provisioning system, and clicking on a link within that email, as well as the SaaS usage rate. As a result, the sender can be prompted to improve their emails based on the analysis results, thereby improving the effectiveness of promoting the use of SaaS via email.

[0018] The information processing device of the present invention is characterized by outputting analysis results regarding the email, based on detection results from a tracking system that detects at least one of the opening of an email delivered by an email delivery system that delivers emails to users of the SaaS provided by a SaaS delivery system that provides the SaaS, and a click on a link within the email, and the usage rate of the SaaS.

[0019] With this configuration, the information processing device of the present invention outputs analysis results regarding emails based on detection results from a tracking system that detects at least one of the opening of an email delivered by an email distribution system to a user of SaaS provided by a SaaS provisioning system, and a click on a link within the email, as well as the SaaS usage rate. As a result, the sender can be prompted to improve the email based on the analysis results, and consequently, the effectiveness of promoting the use of SaaS via email can be improved.

[0020] The analysis program of the present invention is characterized by causing a computer to display analysis results regarding the email, based on detection results from a tracking system that detects at least one of the opening of an email delivered by an email delivery system that delivers emails to users of the SaaS provided by a SaaS delivery system, and a click on a link within the email, and the usage rate of the SaaS.

[0021] With this configuration, the computer that executes the analysis program of the present invention outputs an analysis result regarding an email based on the detection result by a tracking system that detects at least one of opening an email delivered by a mail delivery system to a user of SaaS provided by a SaaS providing system and clicking on a link within the email, and the utilization rate of the SaaS. Therefore, the sender can improve the email based on the analysis result, and as a result, the effect of promoting the use of SaaS by the email can be improved.

Effect of the Invention

[0022] The analysis system, system, information processing apparatus, and analysis program of the present invention can improve the effect of promoting the use of SaaS by email.

Brief Description of the Drawings

[0023] [Figure 1] It is a block diagram of an example of a system according to an embodiment of the present invention. [Figure 2] It is a block diagram of an example of the SaaS providing system shown in FIG. 1 when configured by one computer. [Figure 3] It is a diagram showing an example of tenant management information shown in FIG. 2. [Figure 4] It is a diagram showing an example of tenant user management information shown in FIG. 2. [Figure 5] It is a diagram showing an example of usage history information shown in FIG. 2. [Figure 6] It is a block diagram of an example of the mail delivery system shown in FIG. 1 when configured by one computer. [Figure 7] It is a diagram showing an example of sender management information shown in FIG. 6. [Figure 8] It is a diagram showing an example of the tracking database shown in FIG. 1. [Figure 9] It is a block diagram of an example of the tracking system shown in FIG. 1 when configured by one computer. [Figure 10] Figure 1 is a block diagram of an example of an analysis system that consists of a single computer. [Figure 11] Figure 10 shows an example of analyst management information. [Figure 12] Figure 1 is a block diagram of an example of a SaaS-based device. [Figure 13] Figure 1 is a block diagram of an example of a broadcasting terminal. [Figure 14] Figure 1 is a block diagram of an example of a customer terminal. [Figure 15] Figure 1 is a block diagram of an example of an analyst terminal. [Figure 16] Figure 1 is a sequence diagram of the system's operation when sending emails according to the customer's usage stage of the SaaS provided by the SaaS provider system. [Figure 17] Figure 1 is a sequence diagram of the system's operation when a general user logs into a SaaS provider's system. [Figure 18] Figure 1 is a sequence diagram illustrating the operation of the system when a general user utilizes SaaS. [Figure 19] Figure 1 shows the sequence of system operations when a regular user logs out of a SaaS provisioning system. [Figure 20] Figure 10 is a flowchart illustrating the operation of the analysis system when collecting usage history information from a SaaS provider system. [Figure 21] Figure 1 is a sequence diagram of the system's operation when sending emails in response to instructions from the sender. [Figure 22] Figure 1 is a sequence diagram of the system's operation when an email delivered by the email distribution system is opened by a customer. [Figure 23] Figure 10 shows a flowchart illustrating the operation of the analysis system when collecting tracking data from a tracking database. [Figure 24]Figure 1 is a sequence diagram of the system's operation when the analysis system analyzes data according to instructions from the analyst. [Modes for carrying out the invention]

[0024] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0025] First, the configuration of a system according to one embodiment of the present invention will be described.

[0026] Figure 1 is a block diagram of an example of the system 10 according to this embodiment.

[0027] As shown in Figure 1, System 10 includes a SaaS delivery system 20 that provides SaaS. The SaaS delivery system 20 may consist of one computer, such as a PC (Personal Computer), or it may consist of multiple computers. The SaaS delivery system 20 may also be configured on the cloud.

[0028] System 10 includes a mail delivery system 30 that delivers emails in HTML (HyperText Markup Language) format. The mail delivery system 30 may be configured using one computer, such as a PC, or it may be configured using multiple computers. The mail delivery system 30 may also be configured on the cloud.

[0029] System 10 includes a template database 40, which serves as a database for storing templates, which are HTML-formatted data that saves the design of emails delivered by the email delivery system 30. Templates can be created using either a design view or HTML code.

[0030] System 10 includes a tracking database 50, which serves as a database for storing tracking data indicating the viewing status of emails distributed by the email distribution system 30 by recipients of those emails. The tracking data includes, for example, open tracking, which shows the number of times recipients have opened emails distributed by the email distribution system 30, and click tracking, which shows the number of times each link in the email distributed by the email distribution system 30 has been clicked, i.e., the number of clicks on each link.

[0031] System 10 includes a tracking system 60 that tracks views of emails distributed by the email distribution system 30. The tracking system 60 may be composed of one computer, such as a PC, or multiple computers. The tracking system 60 may be configured on the cloud.

[0032] System 10 includes an analysis system 70 that performs analysis according to KPIs (Key Performance Indicators) based on data showing the usage status of the SaaS provisioning system 20 and tracking data. The analysis system 70 may be composed of one computer such as a PC, or it may be composed of multiple computers. The analysis system 70 may be configured on the cloud.

[0033] System 10 includes a SaaS user device 110 that utilizes SaaS provided by the SaaS provider system 20. System 10 may also include at least one other SaaS user device besides the SaaS user device 110 that utilizes SaaS provided by the SaaS provider system 20. The SaaS user device is used by customers who utilize SaaS provided by the SaaS provider system 20. The SaaS user device may consist of, for example, an image forming apparatus such as an MFP (Multifunction Peripheral), a PC, a tablet, or other computer.

[0034] System 10 includes a sender terminal 120 used by senders who send emails through the email distribution system 30. System 10 may also include at least one other sender terminal used by senders besides the sender terminal 120. The sender terminal may consist of a computer, such as a PC or tablet.

[0035] System 10 includes a customer terminal 130 used by customers who utilize the SaaS provided by the SaaS provisioning system 20. System 10 may also include at least one other customer terminal used by customers besides the customer terminal 130. The customer terminal may consist of a computer such as a PC or tablet. The SaaS user device may also serve as a customer terminal.

[0036] System 10 includes an analyst terminal 140 used by an analyst. System 10 may also include at least one other analyst terminal used by an analyst. The analyst terminal may consist of a computer such as a PC or tablet.

[0037] Figure 2 is a block diagram of an example of a SaaS delivery system 20 that is configured on a single computer.

[0038] As shown in Figure 2, the SaaS provisioning system 20 includes an operation unit 21 which is an operation device such as a keyboard or mouse into which various operations are input; a display unit 22 which is a display device such as an LCD (Liquid Crystal Display) that displays various information; a communication unit 23 which is a communication device that communicates with external devices via a network such as a LAN (Local Area Network) or the Internet, or directly via wired or wireless connection without going through a network; a storage unit 24 which is a non-volatile storage device such as a semiconductor memory or HDD (Hard Disk Drive) that stores various information; and a control unit 25 which controls the entire SaaS provisioning system 20.

[0039] The memory unit 24 is capable of storing a SaaS provisioning program 24a for providing SaaS. The SaaS provisioning program 24a may, for example, be installed on the SaaS provisioning system 20 during the manufacturing stage, or it may be additionally installed on the SaaS provisioning system 20 from an external storage medium such as a USB (Universal Serial Bus) memory, or it may be additionally installed on the SaaS provisioning system 20 from a network.

[0040] The memory unit 24 is capable of storing tenant management information 24b for managing tenants of the SaaS provisioning system 20.

[0041] Figure 3 shows an example of tenant management information 24b.

[0042] As shown in Figure 3, the tenant management information 24b includes the tenant ID as tenant identification information and the initial settings for each tenant. The tenant management information 24b shown in Figure 3 is depicted with some information omitted.

[0043] Initial settings for a tenant can be added, for example, by the tenant's administrator (described later) via the tenant's website. The tenant's website is provided by the SaaS provider 25a (described later).

[0044] As shown in Figure 2, the storage unit 24 is capable of storing tenant user management information 24c for managing tenant users (hereinafter referred to as "tenant users").

[0045] Figure 4 shows an example of tenant user management information 24c.

[0046] As shown in Figure 4, the tenant user management information 24c includes, for each tenant user, the tenant ID of the tenant to which the tenant user belongs, the tenant user ID as identification information for the tenant user, the tenant user's password, the tenant user's email address, and the tenant user's role. Examples of tenant user roles include tenant administrator and general user. In Figure 4, the tenant user management information 24c is depicted with some information omitted.

[0047] Furthermore, general users of a tenant can be added or removed, for example, by the tenant's administrator via the tenant's website. The tenant's website is provided by the SaaS provider 25a described below, as mentioned above.

[0048] As shown in Figure 2, the storage unit 24 can store usage history information 24d, which shows the history of SaaS usage by general users.

[0049] Figure 5 shows an example of usage history information 24d.

[0050] As shown in Figure 5, the usage history information 24d includes the date and time of SaaS usage, the tenant ID of the tenant to which the general user who used the SaaS belongs, the tenant user ID of the general user who used the SaaS, and the details of the SaaS usage for each SaaS usage. The details of the SaaS usage include, for example, the start or end of the general user's login to the SaaS provisioning system 20, and the general user's use of any function of the SaaS. The usage history information 24d shown in Figure 5 is depicted with some information omitted.

[0051] The control unit 25 shown in Figure 2 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Access Memory) used as a working area for the CPU of the control unit 25. The CPU of the control unit 25 executes programs stored in the storage unit 24 or the ROM of the control unit 25.

[0052] The control unit 25 implements a SaaS provisioning unit 25a that provides SaaS by executing a SaaS provisioning program 24a.

[0053] Figure 6 is a block diagram of an example of an email distribution system 30 that is configured using a single computer.

[0054] As shown in Figure 6, the email distribution system 30 includes an operation unit 31 which is an operation device such as a keyboard or mouse into which various operations are input; a display unit 32 which is a display device such as an LCD that displays various information; a communication unit 33 which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly by wired or wireless connection without going through a network; a storage unit 34 which is a non-volatile storage device such as a semiconductor memory or HDD that stores various information; and a control unit 35 that controls the entire email distribution system 30.

[0055] The memory unit 34 can store an email distribution program 34a for distributing emails. The email distribution program 34a may be installed in the email distribution system 30 during the manufacturing stage, or it may be additionally installed in the email distribution system 30 from an external storage medium such as a USB memory stick, or it may be additionally installed in the email distribution system 30 from a network.

[0056] The memory unit 34 is capable of storing sender management information 34b for managing senders who will send emails to the email distribution system 30.

[0057] Figure 7 shows an example of distributor management information 34b.

[0058] As shown in Figure 7, the distributor management information 34b includes a distributor ID as identification information for the distributor and a distributor password for each distributor. The distributor management information 34b shown in Figure 7 is depicted with some information omitted.

[0059] The distributor may be, for example, someone who runs a campaign to encourage customers to use the SaaS provided by the SaaS delivery system 20. The distributor may also be someone who belongs to an organization that performs customer success.

[0060] The control unit 35 shown in Figure 6 includes, for example, a CPU, a ROM that stores programs and various data, and RAM as memory used as a workspace for the CPU of the control unit 35. The CPU of the control unit 35 executes programs stored in the storage unit 34 or the ROM of the control unit 35.

[0061] The control unit 35 implements an email distribution unit 35a that distributes emails by executing an email distribution program 34a.

[0062] Figure 8 shows an example of a tracking database 50.

[0063] As shown in Figure 8, the tracking database 50 includes, for each combination of email and email address, an email ID as identification information for the email, the recipient's email address, the date and time the email was sent, the specific content of the email such as the subject and body, open tracking, click tracking for each link within the email, and redirect information indicating the redirect destination of the links within the email. The tracking database 50 shown in Figure 8 is depicted with some information omitted. For example, the specific content of the email is omitted.

[0064] Open tracking includes the URL of data (hereinafter referred to as "open detection data") used to detect when an email delivered by the email delivery system 30 is opened, and the number of times the recipient has opened the email delivered by the email delivery system 30. In the example of open tracking shown in Figure 8, "https: / / example.net / m-0000000001 / a.png" is the URL of the open detection data, and the "2" to the right of "https: / / example.net / m-0000000001 / a.png" is the number of times the recipient has opened the email delivered by the email delivery system 30.

[0065] Click tracking includes the destination URL of the link in the email delivered by the email delivery system 30, and the number of clicks on the link in the email delivered by the email delivery system 30, for each link in the email delivered by the email delivery system 30. In the example of click tracking shown in Figure 8, "https: / / example.net / m-0000000001 / link / abc" is the destination URL of the link in the email, and the "3" to the right of "https: / / example.net / m-0000000001 / link / abc" is the number of clicks on the link corresponding to "https: / / example.net / m-0000000001 / link / abc".

[0066] The redirect information includes the URL of the link in the email delivered by the email delivery system 30, and the redirect URL, for each URL of the link in the email delivered by the email delivery system 30. In the example of the redirect information shown in Figure 8, "https: / / example.net / m-0000000001 / link / abc" is the URL of the link in the email, and "https: / / example.org / abc", located to the right of "https: / / example.net / m-0000000001 / link / abc", is the redirect URL corresponding to "https: / / example.net / m-0000000001 / link / abc".

[0067] Figure 9 is a block diagram of an example of a tracking system 60 that is comprised of a single computer.

[0068] As shown in Figure 9, the tracking system 60 includes an operation unit 61 which is an operation device such as a keyboard or mouse into which various operations are input; a display unit 62 which is a display device such as an LCD that displays various information; a communication unit 63 which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly by wired or wireless connection without going through a network; a storage unit 64 which is a non-volatile storage device such as a semiconductor memory or HDD that stores various information; and a control unit 65 which controls the entire tracking system 60.

[0069] The memory unit 64 can store a tracking program 64a for tracking views of emails distributed by the email distribution system 30. The tracking program 64a may be installed in the tracking system 60 during the manufacturing stage, or it may be additionally installed in the tracking system 60 from an external storage medium such as a USB memory, or it may be additionally installed in the tracking system 60 from a network.

[0070] The storage unit 64 is capable of storing data 64b for detecting tampering. The data for detecting tampering is, for example, image data.

[0071] The control unit 65 includes, for example, a CPU, a ROM that stores programs and various data, and RAM as memory used as a workspace for the CPU of the control unit 65. The CPU of the control unit 65 executes programs stored in the storage unit 64 or the ROM of the control unit 65.

[0072] The control unit 65 implements a tracking unit 65a that tracks views of emails delivered by the email delivery system 30 by executing a tracking program 64a.

[0073] Figure 10 is a block diagram of an example of an analysis system 70 that consists of a single computer.

[0074] As shown in Figure 10, the analysis system 70 includes an operation unit 71 which is an operation device such as a keyboard or mouse into which various operations are input; a display unit 72 which is a display device such as an LCD that displays various information; a communication unit 73 which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly by wired or wireless connection without going through a network; a storage unit 74 which is a non-volatile storage device such as a semiconductor memory or HDD that stores various information; and a control unit 75 which controls the entire analysis system 70.

[0075] The memory unit 74 can store an analysis program 74a for performing analysis according to KPIs based on data showing the usage status of the SaaS provisioning system 20 and tracking data. The analysis program 74a may be installed in the analysis system 70 during the manufacturing stage, or it may be additionally installed in the analysis system 70 from an external storage medium such as a USB memory, or it may be additionally installed in the analysis system 70 from a network.

[0076] The memory unit 74 can store data showing the usage status of the SaaS provisioning system 20 and analyst management information 74b for managing analysts who perform analysis according to KPIs based on tracking data.

[0077] Figure 11 shows an example of analyst management information 74b.

[0078] As shown in Figure 11, the analyst management information 74b includes the analyst ID as identification information for each analyst, and the analyst's password. The analyst management information 74b shown in Figure 11 is depicted with some information omitted.

[0079] The analyst could, for example, also be the broadcaster.

[0080] As shown in Figure 10, the storage unit 74 can store usage history information 74c, which shows the history of SaaS usage by general users. The configuration of the usage history information 74c is the same as that of the usage history information 24d (see Figure 5).

[0081] The storage unit 74 can store tracking information 74d, which serves as a database for storing tracking data indicating the viewing status of emails distributed by the email distribution system 30 by recipients of those emails. The configuration of the tracking information 74d is the same as that of the tracking database 50 (see Figure 8).

[0082] The control unit 75 includes, for example, a CPU, a ROM that stores programs and various data, and RAM as memory used as a workspace for the CPU of the control unit 75. The CPU of the control unit 75 executes programs stored in the storage unit 74 or the ROM of the control unit 75.

[0083] The control unit 75 executes the analysis program 74a to realize an analysis unit 75a that performs analysis according to KPIs based on data showing the usage status of the SaaS provisioning system 20 and tracking data.

[0084] Figure 12 is a block diagram of an example of a SaaS utilization device 110.

[0085] As shown in Figure 12, the SaaS user device 110 includes an operation unit 111, which is an operation device such as a keyboard or mouse into which various operations are input; a display unit 112, which is a display device such as an LCD that displays various information; a communication unit 113, which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly via wired or wireless connection without going through a network; a storage unit 114, which is a non-volatile storage device such as a semiconductor memory or HDD that stores various information; and a control unit 115 that controls the entire SaaS user device 110.

[0086] The storage unit 114 can store a SaaS user program 114a, which is a program for using SaaS provided by the SaaS provisioning system 20. The SaaS user program 114a may be installed on the SaaS user device 110 during the manufacturing stage of the SaaS user device 110, or it may be additionally installed on the SaaS user device 110 from an external storage medium such as a USB memory, or it may be additionally installed on the SaaS user device 110 from a network.

[0087] The control unit 115 includes, for example, a CPU, a ROM that stores programs and various data, and RAM as memory used as a workspace for the CPU of the control unit 115. The CPU of the control unit 115 executes programs stored in the storage unit 114 or the ROM of the control unit 115.

[0088] The control unit 115 implements a SaaS utilization unit 115a that utilizes SaaS provided by the SaaS provisioning system 20 by executing a SaaS utilization program 114a.

[0089] Figure 13 is a block diagram of an example of a broadcaster terminal 120.

[0090] As shown in Figure 13, the broadcaster terminal 120 includes an operation unit 121 which is an operation device such as a keyboard or mouse into which various operations are input; a display unit 122 which is a display device such as an LCD that displays various information; a communication unit 123 which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly via wired or wireless connection without going through a network; a storage unit 124 which is a non-volatile storage device such as a semiconductor memory or HDD that stores various information; and a control unit 125 that controls the entire broadcaster terminal 120.

[0091] The control unit 125 includes, for example, a CPU, a ROM that stores programs and various data, and RAM as memory used as a workspace for the CPU of the control unit 125. The CPU of the control unit 125 executes programs stored in the storage unit 124 or the ROM of the control unit 125.

[0092] Figure 14 is a block diagram of an example of a customer terminal 130.

[0093] As shown in Figure 14, the customer terminal 130 includes an operation unit 131 which is an operation device such as a keyboard or mouse into which various operations are input; a display unit 132 which is a display device such as an LCD that displays various information; a communication unit 133 which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly via wired or wireless connection without going through a network; a storage unit 134 which is a non-volatile storage device such as a semiconductor memory or HDD that stores various information; and a control unit 135 that controls the entire customer terminal 130.

[0094] The storage unit 134 is capable of storing an email client program 134a, which is a program for an email client. The email client program 134a may, for example, be installed on the customer terminal 130 during the manufacturing stage of the customer terminal 130, or it may be additionally installed on the customer terminal 130 from an external storage medium such as a USB memory, or it may be additionally installed on the customer terminal 130 from a network.

[0095] The memory unit 134 is capable of storing a web browser program 134b as a program for a web browser. The web browser program 134b may, for example, be installed on the customer terminal 130 during the manufacturing stage of the customer terminal 130, or it may be additionally installed on the customer terminal 130 from an external storage medium such as a USB memory, or it may be additionally installed on the customer terminal 130 from a network.

[0096] The control unit 135 includes, for example, a CPU, a ROM that stores programs and various data, and RAM as memory used as a workspace for the CPU of the control unit 135. The CPU of the control unit 135 executes programs stored in the storage unit 134 or the ROM of the control unit 135.

[0097] The control unit 135 implements the email client 135a by executing the email client program 134a.

[0098] The control unit 135 implements the web browser 135b by executing the web browser program 134b.

[0099] Figure 15 is a block diagram of an example of an analyst terminal 140.

[0100] As shown in Figure 15, the analyst terminal 140 includes an operation unit 141 which is an operation device such as a keyboard or mouse into which various operations are input; a display unit 142 which is a display device such as an LCD that displays various information; a communication unit 143 which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly via wired or wireless connection without going through a network; a storage unit 144 which is a non-volatile storage device such as a semiconductor memory or HDD that stores various information; and a control unit 145 that controls the entire analyst terminal 140.

[0101] The control unit 145 includes, for example, a CPU, a ROM that stores programs and various data, and RAM as memory used as a workspace for the CPU of the control unit 145. The CPU of the control unit 145 executes programs stored in the storage unit 144 or the ROM of the control unit 145.

[0102] Next, we will describe the operation of system 10.

[0103] In the following, SaaS user device 110 will be described as a representative of the SaaS user devices. Similarly, the distributor terminal 120, customer terminal 130, and analyst terminal 140 will be described as representatives of the distributor terminal, customer terminal, and analyst terminal, respectively.

[0104] First, we will explain the operation of system 10 when sending emails according to the customer's stage of using the SaaS provided by the SaaS provisioning system 20.

[0105] The stages of customer use of SaaS provided by the SaaS provisioning system 20 include: Stage 1, when the customer enters into a contract with the SaaS provider to use the SaaS; Stage 2, when the customer's administrator is registered with the SaaS provisioning system 20 in order for the customer to use the SaaS; Stage 3, when the necessary initial setup is performed or the customer's general users are registered with the SaaS provisioning system 20 in order for the customer to use the SaaS; and Stage 4, when the customer actually uses the SaaS. The contract entered into between the customer and the SaaS provider is a contract for the continuous use of the SaaS, such as a subscription contract.

[0106] Figure 16 is a sequence diagram of the operation of system 10 when sending emails according to the customer's usage stage of the SaaS provided by the SaaS delivery system 20.

[0107] As shown in Figure 16, the SaaS provisioning unit 25a of the SaaS provisioning system 20 identifies the stage of customer usage (S201). For example, the SaaS provisioning unit 25a may identify the stage of usage for a target customer of a tenant identified by a tenant ID for which there is no administrator associated in the tenant user management information 24c as the first stage. Alternatively, the SaaS provisioning unit 25a may identify the stage of usage for a target customer of a tenant identified by a tenant ID for which there is an administrator associated in the tenant user management information 24c, but there are no general users associated with this administrator in the tenant user management information 24c as the second stage. Furthermore, the SaaS provisioning unit 25a may identify the stage of usage for a target customer of a tenant identified by a tenant ID for which there is an administrator associated in the tenant user management information 24c, but there are no initial settings associated in the tenant management information 24b as the second stage. Furthermore, the SaaS provider unit 25a may identify as the third stage of usage for a target customer of a tenant identified by a tenant ID that has a general user associated in the tenant user management information 24c and an initial setting associated in the tenant management information 24b, but no SaaS usage history associated in the usage history information 24d. Furthermore, the SaaS provider unit 25a may identify as the fourth stage of usage for a target customer of a tenant identified by a tenant ID that has a SaaS usage history associated in the usage history information 24d.

[0108] If the SaaS provider unit 25a determines in S201 that the customer's usage stage is stage 2, and a certain period of time has elapsed since the initial determination that the customer's usage stage is stage 2, it instructs the email distribution system 30 to send an email to the email address associated with the administrator's tenant user ID in the tenant user management information 24c, requesting that the administrator advance the customer's usage stage to stage 3 (S202).

[0109] When the email distribution unit 35a of the email distribution system 30 receives the instruction in S202, it sends the email specified in S202 (S203).

[0110] If the SaaS provider unit 25a identifies in S201 that the customer's usage stage is stage 3, and a certain period of time has elapsed since the initial identification of the customer's usage stage as stage 3, it instructs the email distribution system 30 to send an email to the email address associated with the administrator's tenant user ID in the tenant user management information 24c, requesting that the administrator advance the customer's usage stage to stage 4 (S204).

[0111] When the email distribution unit 35a of the email distribution system 30 receives the instruction in S204, it sends the email specified in S204 (S205).

[0112] The delivery of emails when the customer is in stage 4 of their usage will be discussed later.

[0113] Next, we will explain the operation of system 10 when a general user logs in to the SaaS provisioning system 20.

[0114] Figure 17 is a sequence diagram of the operation of system 10 when a general user logs in to the SaaS provisioning system 20.

[0115] A general user can instruct the SaaS user device 110 to log in to the SaaS provider system 20 via the operation unit 111 of the SaaS user device 110. When the SaaS user device 110's SaaS user unit 115a receives an instruction to log in to the SaaS provider system 20, it sends a request to execute the login process (hereinafter referred to as the "login processing request") to the SaaS provider system 20, as shown in Figure 17 (S221). The SaaS user unit 115a of the SaaS user device 110 includes the combination of tenant ID, tenant user ID, and password entered from the operation unit 111 of the SaaS user device 110 in the login processing request.

[0116] When the SaaS provisioning unit 25a of the SaaS provisioning system 20 receives a login processing request sent in S221, it performs authentication based on the combination of tenant ID, tenant user ID, and password included in the received login processing request and the tenant user management information 24c (S222). Specifically, the SaaS provisioning unit 25a determines that authentication is successful if the combination of tenant ID, tenant user ID, and password included in the login processing request sent in S221 is included in the tenant user management information 24c. On the other hand, the SaaS provisioning unit 25a determines that authentication has failed if the combination of tenant ID, tenant user ID, and password included in the login processing request sent in S221 is not included in the tenant user management information 24c.

[0117] If the SaaS provider unit 25a determines in S222 that authentication was successful, it adds a record to the usage history information 24d indicating that the login status of the successfully authenticated general user has begun (S223).

[0118] When the processing in S223 is completed, the SaaS provider unit 25a notifies the SaaS user device 110 that login permission has been granted (S224).

[0119] When the SaaS user unit 115a of the SaaS user device 110 receives the notification in S224, it displays on the display unit 112 of the SaaS user device 110 that login has been permitted (S225).

[0120] Next, we will explain how System 10 operates when a general user uses SaaS.

[0121] Figure 18 is a sequence diagram showing the operation of System 10 when a general user uses SaaS.

[0122] When a general user is logged into the SaaS provisioning system 20, that is, while logged in, they can instruct the SaaS user device 110 to use a specific function of the SaaS provided by the SaaS provisioning system 20 via the operation unit 111 of the SaaS user device 110. When the SaaS user device 110 receives an instruction to use a specific function of the SaaS provided by the SaaS provisioning system 20, the SaaS user unit 115a of the SaaS user device 110 sends a request to use the specific function of the SaaS provided by the SaaS provisioning system 20 (hereinafter referred to as "function usage request") to the SaaS provisioning system 20, as shown in Figure 18 (S241).

[0123] When the SaaS provisioning unit 25a of the SaaS provisioning system 20 receives a function usage request sent in S241, it executes the function corresponding to the received function usage request (S242).

[0124] When the processing in S242 is completed, the SaaS provider unit 25a adds the execution history of the function in S242 to the usage history information 24d (S243).

[0125] When the processing in S243 is completed, the SaaS provider unit 25a notifies the SaaS user device 110 of the result of the execution of the function in S242 (S244).

[0126] When the SaaS utilization unit 115a of the SaaS utilization device 110 receives the notification in S244, it displays the result of the function execution notified in S244 on the display unit 112 of the SaaS utilization device 110 (S245).

[0127] Next, we will explain the operation of system 10 when a general user logs out of the SaaS provisioning system 20.

[0128] Figure 19 is a sequence diagram of the operation of system 10 when a general user logs out of the SaaS provisioning system 20.

[0129] A regular user can instruct the SaaS user device 110 to log out of the SaaS provider system 20 via the operation unit 111 of the SaaS user device 110. When the SaaS user device 110 receives an instruction to log out of the SaaS provider system 20, the SaaS user unit 115a of the SaaS user device 110 sends a request to execute the logout process (hereinafter referred to as the "logout processing request") to the SaaS provider system 20, as shown in Figure 19 (S261).

[0130] When the SaaS provisioning unit 25a of the SaaS provisioning system 20 receives a logout processing request sent in S261, it performs the logout of the general user who is the target of the logout processing request (S262).

[0131] When the processing in S262 is completed, the SaaS provider unit 25a adds a history to the usage history information 24d indicating that the login status of the general user who was the target of the logout processing request sent in S261 has ended (S263).

[0132] When the processing in S263 is completed, the SaaS provider unit 25a notifies the SaaS user device 110 that the general user has logged out (S264).

[0133] When the SaaS user unit 115a of the SaaS user device 110 receives the notification in S264, it displays on the display unit 112 of the SaaS user device 110 that the general user has logged out (S265).

[0134] Next, we will explain how the analysis system 70 operates when collecting usage history information from the SaaS provisioning system 20.

[0135] Figure 20 is a flowchart showing the operation of the analysis system 70 when collecting usage history information from the SaaS provisioning system 20.

[0136] As shown in Figure 20, the analysis unit 75a of the analysis system 70 determines whether a specific period of time has passed since the last update of the usage history information 74c until it determines that a specific period of time has passed since the last update of the usage history information 74c (S281). If the usage history information 74c has not been updated even once, the analysis unit 75a treats the passage of a specific period of time from the start of the operation shown in Figure 20 as the passage of a specific period of time since the last update of the usage history information 74c.

[0137] If the analysis unit 75a determines in S281 that a specific period of time has elapsed since the last update of the usage history information 74c, it requests the usage history information from the SaaS provisioning system 20 (S282). Upon receiving the request in S282, the SaaS provisioning unit 25a of the SaaS provisioning system 20 sends the same usage history information as the usage history information 24d to the analysis system 70.

[0138] The analysis unit 75a of the analysis system 70 determines whether or not it has received usage history information from the SaaS provision system 20 after the processing in S282 is completed, until it determines that it has received usage history information from the SaaS provision system 20 (S283).

[0139] When the analysis unit 75a determines in S283 that it has received usage history information from the SaaS provisioning system 20, it updates the usage history information 74c with the usage history information received from the SaaS provisioning system 20 (S284) and executes the process in S281.

[0140] Next, we will describe how System 10 operates when sending emails in response to instructions from the sender.

[0141] Figure 21 is a sequence diagram of the operation of System 10 when an email is delivered in response to instructions from the sender.

[0142] The sender can instruct the sender terminal 120 to log in to the email distribution system 30 via the operation unit 121 of the sender terminal 120. When the sender terminal 120 is instructed to log in to the email distribution system 30, the control unit 125 of the sender terminal 120 sends a login processing request to the email distribution system 30, as shown in Figure 21 (S301). The control unit 125 of the sender terminal 120 includes the sender ID and password combination entered from the operation unit 121 of the sender terminal 120 in the login processing request.

[0143] When the email distribution unit 35a of the email distribution system 30 receives a login processing request sent in S301, it performs authentication based on the combination of sender ID and password included in the received login processing request and the sender management information 34b (S302). Specifically, the email distribution unit 35a determines that authentication is successful if the combination of sender ID and password included in the login processing request sent in S301 is included in the sender management information 34b. On the other hand, the email distribution unit 35a determines that authentication has failed if the combination of sender ID and password included in the login processing request sent in S301 is not included in the sender management information 34b.

[0144] If the email distribution unit 35a determines in S302 that authentication was successful, it notifies the sender terminal 120 that login is permitted (S303).

[0145] When the control unit 125 of the broadcaster terminal 120 receives the notification in S303, it displays on the display unit 122 of the broadcaster terminal 120 that login has been permitted (S304).

[0146] When the sender is logged into the email distribution system 30, they can instruct the email distribution system 30 via the sender terminal 120 to obtain candidate email addresses for recipients of emails distributed by the email distribution system 30. When the email distribution unit 35a of the email distribution system 30 is instructed to obtain email addresses for recipients of emails distributed by the email distribution system 30, it requests the email addresses from the SaaS provisioning system 20 (S305).

[0147] When the SaaS provisioning unit 25a of the SaaS provisioning system 20 receives a request in S305, it sends the list of email addresses shown in the sender management information 34b to the email distribution system 30 (S306).

[0148] The sender can instruct the email distribution system 30, via the sender terminal 120, to use the email addresses of recipients of emails distributed by the email distribution system 30, based on the list of email addresses sent from the SaaS provisioning system 20 in S306. Specifically, the sender may decide to use the email addresses included in the list sent from the SaaS provisioning system 20 in S306 as they are, or they may decide to use the email addresses of recipients of emails distributed by the email distribution system 30 after deleting at least some of the email addresses included in the list sent from the SaaS provisioning system 20 in S306 and adding new email addresses. When the email addresses of recipients of emails are instructed, the email distribution unit 35a of the email distribution system 30 sets the email addresses of recipients of emails distributed by the email distribution system 30 as instructed by the sender (S307).

[0149] The sender can instruct the email distribution system 30 to generate emails to be distributed via the sender terminal 120. Specifically, the sender can select one of the templates stored in the template database 40 and generate an email using the selected template. The sender may also generate an email without using a template. When the email distribution unit 35a of the email distribution system 30 is instructed to generate an email, it generates the email as instructed (S308). Here, the email distribution unit 35a sets the URL of the open detection data 64b in the tracking system 60 as the URL of the open detection data in the email generated in S308. The email distribution unit 35a also sets the URL in the tracking system 60 as the URL of the link in the email generated in S308. The email distribution unit 35a makes the URL of the open detection data in the email generated in S308 and the URL of the link in the email generated in S308 different for each combination of email and email address.

[0150] Once the processing in S308 is complete, the sender can instruct the mail distribution system 30 via the sender terminal 120 to send the email generated in S308. When the mail distribution unit 35a of the mail distribution system 30 is instructed to send the email, it sends the email generated in S308 to the email address set in S307 (S309).

[0151] When the processing in S309 is completed, the email distribution unit 35a of the email distribution system 30 adds the tracking data of the email sent in S309 to the tracking database 50 for each recipient email address of the email sent in S309 (S310).

[0152] In the operation shown in Figure 21, the email distribution system 30 obtains email addresses from the SaaS provisioning system 20. However, the email distribution system 30 does not need to obtain email addresses from the SaaS provisioning system 20. For example, the email distribution system 30 may have all the recipient email addresses of the generated emails entered by the sender.

[0153] Next, we will describe the operation of system 10 when an email delivered by email distribution system 30 is opened by a customer.

[0154] Figure 22 is a sequence diagram of the operation of system 10 when an email delivered by the email distribution system 30 is opened by a customer.

[0155] A customer, i.e., a tenant administrator or general user, can receive an email delivered by the email distribution system 30 to their email address via the email client 135a on the customer terminal 130, and then instruct the email client 135a to open the received email via the operation unit 131 of the customer terminal 130. When the email client 135a is instructed to open the email, it requests the tracking system 60 for open detection data, which is identified by the URL of the open detection data contained in the email (S321).

[0156] When the tracking unit 65a of the tracking system 60 receives the request in S321, it increments the open tracking associated with the URL accessed in S321 in the tracking database 50 by 1 (S322).

[0157] When the processing in S322 is completed, the tracking unit 65a sends the open detection data for the target of the request in S321 to the email client 135a (S323).

[0158] When the processing in S323 is completed, the email client 135a uses the read receipt data sent in S323 to display the contents of the email on the display unit 132 (S324).

[0159] When an email is displayed on the display unit 132 in S324, the customer can click on the links in the email according to their own interests. When a link in the email is clicked, the email client 135a instructs the web browser 135b to access the URL of the clicked link (S325).

[0160] When the web browser 135b receives the instruction in S325, it requests the tracking system 60 to provide the web page identified by the URL corresponding to the instruction in S325 (S326).

[0161] When the tracking unit 65a of the tracking system 60 receives the request in S326, it increments the click tracking associated with the URL accessed in S326 in the tracking database 50 by 1 (S327).

[0162] When the processing in S327 is completed, the tracking unit 65a sends the redirect destination URL, which is associated with the URL of the request in S326 in the redirect information of the tracking database 50, to the web browser 135b (S328).

[0163] When the web browser 135b receives the URL sent in S328, it displays the web page identified by the received URL on the display unit 132 (S329).

[0164] Next, we will describe the operation of the analysis system 70 when collecting tracking data from the tracking database 50.

[0165] Figure 23 is a flowchart showing the operation of the analysis system 70 when collecting tracking data from the tracking database 50.

[0166] As shown in Figure 23, the analysis unit 75a of the analysis system 70 determines whether a specific period of time has passed since the tracking information 74d was last updated, until it determines that a specific period of time has passed since the tracking information 74d was last updated (S341). If the tracking information 74d has not been updated even once, the analysis unit 75a treats the time elapsed since the start of the operation shown in Figure 23 as the time elapsed since the tracking information 74d was last updated.

[0167] If the analysis unit 75a determines in S341 that a specific period of time has elapsed since the last update of the tracking information 74d, it requests tracking data from the tracking database 50 (S342). Upon receiving the request in S342, the tracking database 50 transmits the tracking data from the tracking database 50 to the analysis system 70.

[0168] The analysis unit 75a of the analysis system 70 determines whether or not it has received tracking data from the tracking database 50 after the processing in S342 is completed, until it determines that it has received tracking data from the tracking database 50 (S343).

[0169] If the analysis unit 75a determines in S343 that it has received tracking data from tracking information 74d, it updates tracking information 74d with the tracking data received from tracking information 74d (S344) and then executes the process in S341.

[0170] Next, we will describe the operation of system 10 when the analysis system 70 analyzes data in accordance with instructions from the analyst.

[0171] Figure 24 is a sequence diagram of the operation of system 10 when the analysis system 70 analyzes data according to instructions from the analyst.

[0172] The analyst can instruct the analyst terminal 140 to log in to the analysis system 70 via the operation unit 141 of the analyst terminal 140. When the analyst terminal 140 is instructed to log in to the analysis system 70, the control unit 145 of the analyst terminal 140 sends a login processing request to the analysis system 70, as shown in Figure 24 (S361). The control unit 145 of the analyst terminal 140 includes the combination of analyst ID and password entered from the operation unit 141 of the analyst terminal 140 in the login processing request.

[0173] When the analysis unit 75a of the analysis system 70 receives a login processing request sent in S361, it performs authentication based on the combination of analyst ID and password included in the received login processing request and the analyst management information 74b (S362). Specifically, the analysis unit 75a determines that authentication is successful if the combination of analyst ID and password included in the login processing request sent in S361 is included in the analyst management information 74b. On the other hand, the analysis unit 75a determines that authentication has failed if the combination of analyst ID and password included in the login processing request sent in S361 is not included in the analyst management information 74b.

[0174] If the analysis unit 75a determines in S362 that authentication was successful, it notifies the analyst terminal 140 that login is permitted (S363).

[0175] When the control unit 145 of the analyst terminal 140 receives the notification in S363, it displays on the display unit 142 of the analyst terminal 140 that login has been permitted (S364).

[0176] When an analyst is logged into the analysis system 70, they can instruct the analysis system 70 via the analyst terminal 140 to evaluate emails distributed by the email distribution system 30. When the analysis unit 75a of the analysis system 70 is instructed to evaluate emails distributed by the email distribution system 30, it calculates the usage rate of SaaS provided by the SaaS provisioning system 20 based on the usage history information 74c (S365).

[0177] The analysis unit 75a may calculate the usage rate of the SaaS provided by the SaaS provisioning system 20 by the usage rate of each individual user of the SaaS.

[0178] The analysis unit 75a may calculate the utilization rate of the SaaS provided by the SaaS provisioning system 20 based on the length of time that a general user is logged into the SaaS provisioning system 20. For example, the analysis unit 75a may calculate the utilization rate of the SaaS by a particular general user as the ratio of the total time that a particular general user was logged into the SaaS provisioning system 20 to the total time for a specific time period within a specific period in the past. Here, the specific period may be, for example, 20 days. The specific time period may be, for example, a part of the day, such as from 8 a.m. to 5 p.m., or the entire day, such as from 0 a.m. to 0 a.m. the following day. For example, if the analysis unit 75a calculates the SaaS usage rate by a particular general user as the percentage of the total time that a specific general user was logged into the SaaS provisioning system 20 out of the total time during the period from 8:00 AM to 5:00 PM over the most recent 20 days, and the total time during that period is 90 hours, then the analysis unit 75a calculates the SaaS usage rate by this general user as 50% because the total time during that period is 180 hours.

[0179] The analysis unit 75a may calculate the usage rate of a specific function of the SaaS by general users as the usage rate of the SaaS provided by the SaaS provisioning system 20. For example, the analysis unit 75a may calculate the usage rate of the SaaS by a specific general user as the ratio of the number of days that a specific general user used a specific function of the SaaS to the total number of days in a specific period in the past. Here, the specific period may be, for example, 20 days. For example, if the analysis unit 75a calculates the usage rate of the SaaS by a specific general user as the ratio of the number of days that a specific general user used a specific function of the SaaS to the total number of days in the most recent 20 days, and the number of days that this general user used a specific function of the SaaS in the most recent 20 days is 1 day, then the usage rate of the SaaS by this general user will be calculated as 5%.

[0180] The analysis unit 75a may calculate the SaaS utilization rate provided by the SaaS provisioning system 20 by the utilization rate of SaaS by a group of general users. For example, the analysis unit 75a may calculate the average of the SaaS utilization rates of all general users belonging to a specific tenant as the SaaS utilization rate for that tenant.

[0181] When processing S365 is completed, the analysis unit 75a calculates the open rate of emails delivered by the email delivery system 30 based on the tracking information 74d (S366).

[0182] The analysis unit 75a may calculate the open rate for each individual user as the open rate for emails delivered by the email distribution system 30.

[0183] The analysis unit 75a may calculate the open rate of emails delivered by the email delivery system 30 to a specific general user during a specific period in the past, by determining the ratio of the number of emails opened by that general user to the total number of emails. Here, the specific period may be the most recent 20 days. For example, if the analysis unit 75a calculates the open rate of emails sent by the email distribution system 30 to a specific general user over the past 20 days, by determining the ratio of the number of emails opened by this general user to the total number of emails, then if the total number of emails sent by the email distribution system 30 to this general user over the past 20 days is 10, and the number of emails opened by this general user over the past 20 days is 2, then the open rate of emails sent by this general user over the past 20 days is calculated as 20%.

[0184] The analysis unit 75a may calculate the open rate of a specific email sent by the email distribution system 30 to a specific general user as 100% if the general user opens the email, and as 0% if the general user does not open the email.

[0185] When the processing in S366 is completed, the analysis unit 75a generates analysis results regarding emails delivered by the email delivery system 30 based on the SaaS utilization rate calculated in S365 and the email open rate calculated in S366 (S367).

[0186] The analysis unit 75a may generate analysis results for emails distributed by the email distribution system 30 based on the open rate calculated in S366 for each general user to whom the email was distributed by the email distribution system 30, for each specific range of SaaS usage rate calculated in S365. For example, the analysis unit 75a may generate analysis results for emails distributed by the email distribution system 30, specifically the average open rate for general users to whom the email was distributed by the email distribution system 30 whose SaaS usage rate calculated in S365 is below a specific value, and the average open rate for general users whose SaaS usage rate calculated in S365 is above a specific value. For example, with respect to an email delivered by the email distribution system 30, if the average open rate of general users whose SaaS usage rate calculated in S365 is below a certain value is greater than the average open rate of general users whose SaaS usage rate calculated in S365 is above a certain value, it is possible to evaluate that the email may be more likely to be opened by general users with low SaaS usage rates. Here, the specific value is, for example, 30%.

[0187] The analysis unit 75a may generate analysis results including the average of the SaaS usage rate after the delivery date of the email for general users (hereinafter referred to in this paragraph as "users within the specified range") whose SaaS usage rate before the delivery date of the email falls within a specific range and who received the email but did not open it, the average of the SaaS usage rate after the delivery date of the email for general users within the specified range who did not receive the email, and the average of the SaaS usage rate after the delivery date of the email for general users within the specified range who received the email and opened it. If the average SaaS usage rate of general users within a specific range who received and opened this email, after the date and time of delivery, is higher than the average SaaS usage rate of general users within the specific range who received this email but did not open it, and the average SaaS usage rate of general users within the specific range who did not receive this email, then it is possible to evaluate whether this email has the potential to promote SaaS usage among users within that specific range.

[0188] The analysis unit 75a may generate analysis results that include the average SaaS usage rate before the email delivery date and time among general users (hereinafter referred to as "users within the specified range" in this paragraph) whose SaaS usage rate before the email delivery date and time falls within a specific range, and who received and opened this email, and the average SaaS usage rate after the email delivery date and time among general users within the specified range who received and opened this email. If the average SaaS usage rate among general users within the specified range who received and opened this email improves around the time the email was delivered, it is possible to evaluate that this email may have the effect of promoting SaaS usage among users within the specified range.

[0189] Furthermore, the analysis unit 75a can associate tenant users in the usage history information 74c with tenant users in the tracking information 74d using their email addresses.

[0190] When the processing in S367 is completed, the analysis unit 75a notifies the analyst terminal 140 of the analysis results generated in S367 (S368).

[0191] When the control unit 145 of the analyst terminal 140 receives the notification in S368, it displays the analysis result notified in S368 on the display unit 142 of the analyst terminal 140 (S369). Therefore, by checking the display in S369, the analyst may be able to recognize, for example, what kind of email content is effective in promoting the use of SaaS, and may be able to improve the emails distributed by the email distribution system 30 to be effective in promoting the use of SaaS. In addition, by checking the display in S369, the analyst may be able to recognize, for example, what kind of email content is likely to be opened, and may be able to improve the emails distributed by the email distribution system 30 to be more likely to be opened. Furthermore, by checking the display in S369, the analyst may be able to recognize, for example, what kind of email content is effective in promoting the use of SaaS, and what kind of email content is likely to be opened, for each range of SaaS usage rates, and may be able to differentiate the emails distributed by the email distribution system 30 for each range of SaaS usage rates.

[0192] In the above, the analysis unit 75a of the analysis system 70 calculates the email open rate in S366, but in addition to the email open rate, or instead of the email open rate, it may also calculate the click-through rate for emails or the click-through rate for each link contained in the email. The analysis unit 75a may also calculate the click-through rate for a specific email delivered to a specific tenant user by the email distribution system 30 as the ratio of the number of links actually clicked by the tenant user to the total number of links contained in the email. The analysis unit 75a may also generate analysis results regarding emails delivered by the email distribution system 30 based on the SaaS usage rate calculated in S365 and the click-through rate for emails. Therefore, the analyst can, for example, recognize what kind of email content is effective in promoting SaaS usage, or what kind of email links are more likely to be clicked.

[0193] The analysis unit 75a may calculate, in addition to or instead of the email open rate, the click-through rate for emails or the click-through rate for each link contained in the email. For a specific link in a specific email delivered by the email delivery system 30 to a specific general user, the analysis unit 75a may calculate the click-through rate for this link as 100% if the general user clicks on the link, and as 0% if the general user does not click on the link. The analysis unit 75a may generate an evaluation of each link contained in the email delivered by the email delivery system 30 based on the SaaS usage rate calculated in S365 and the click-through rate for each link contained in the email. Therefore, the analyst can recognize, for example, what kind of content on the linked page is effective in promoting the use of SaaS.

[0194] As explained above, the analysis system 70 outputs analysis results regarding emails (S368) based on the detection results from the tracking system 60, which detects at least one of the following: opening of emails delivered by the email delivery system 30 to users of SaaS provided by the SaaS delivery system 20, and clicking of links within these emails, as well as the SaaS usage rate. Therefore, the sender can be encouraged to improve their emails based on the analysis results, thereby improving the effectiveness of promoting SaaS usage via email. Consequently, the possibility of customers dropping out of contracts for continued use of SaaS can be reduced, and as a result, the customer's CLTV (Customer LifeTime Value) can be improved.

[0195] The analysis system 70 divides SaaS users into multiple segments based on their usage rate and displays the email open rate for each segment as an analysis result. This allows senders to identify emails that are more likely to be opened by users in specific segments, thereby improving the effectiveness of promoting SaaS usage via email.

[0196] The analysis system 70 divides SaaS users into multiple segments based on their usage rate and displays the click-through rate of links for each segment as an analysis result. This allows distributors to identify links that are more likely to be clicked by users in specific segments, thereby improving the effectiveness of promoting SaaS usage via email.

[0197] The analysis system 70 displays the usage rate before and after email opening as analysis results, allowing senders to recognize emails that are effective in promoting SaaS usage, and as a result, the effectiveness of promoting SaaS usage via email can be improved.

[0198] The analysis system 70 displays the usage rate before and after a link click as an analysis result, allowing the sender to recognize links that are effective in promoting SaaS usage, and as a result, the effectiveness of promoting SaaS usage via email can be improved.

[0199] In this embodiment, System 10 consists of a SaaS delivery system 20, an email distribution system 30, a tracking system 60, and an analysis system 70, each configured on separate computers. However, at least some of the computers comprising the SaaS delivery system 20, the email distribution system 30, the tracking system 60, and the analysis system 70 may be common. For example, the analysis system 70 may be configured on a computer shared with at least one of the SaaS delivery system 20, the email distribution system 30, and the tracking system 60. [Explanation of Symbols]

[0200] 10 Systems 20 SaaS provision systems 30 Email distribution system 60 Tracking Systems 70. Analytical Systems (Computers, Information Processing Devices) 74a Analysis Program

Claims

1. An analysis system characterized by outputting analysis results regarding the email, based on detection results from a tracking system that detects at least one of the opening of an email delivered by an email delivery system that delivers emails to users of the SaaS provided by a SaaS provisioning system, and a click on a link within the email, and the usage rate of the SaaS.

2. The analysis system according to claim 1, characterized in that it divides the users of the SaaS into a plurality of segments according to the usage rate, and shows the email open rate for each segment as the analysis result.

3. The analysis system according to claim 1, characterized in that it divides the users of the SaaS into a plurality of segments according to the usage rate, and shows the click rate of the link for each segment as the analysis result.

4. The analysis system according to claim 1, characterized in that the usage rate before and after opening the email is shown as the analysis result.

5. The analysis system according to claim 1, characterized in that the usage rate before and after clicking the link is shown as the analysis result.

6. A SaaS provider system that provides SaaS, A mail distribution system that delivers emails to users of the SaaS provided by the SaaS provision system, A tracking system that detects at least one of the opening of an email delivered by the email distribution system and a click on a link within the email, An analysis system that outputs analysis results regarding the email based on the detection results from the tracking system and the usage rate of the SaaS, A system characterized by comprising the following features.

7. When the SaaS provisioning system manages a tenant of a specific customer and the administrator of that tenant, and does not manage at least one of the general users of the SaaS as users of that tenant or the initial settings for that tenant, the system identifies the stage of the specific customer's use of the SaaS as a specific stage. The system according to claim 6, characterized in that when the SaaS provisioning system identifies that the stage of use of the SaaS by the particular customer is the particular stage, and a certain period of time has elapsed since the initial identification of the stage of use of the SaaS by the particular customer as the particular stage, the system instructs the email distribution system to send an email to the administrator of the tenant of the particular customer requesting that the stage of use of the SaaS by the particular customer be advanced to the next stage.

8. When the SaaS provisioning system manages a specific customer's tenant, the administrator of the specific customer's tenant, the general users of the SaaS as users of the specific customer's tenant, and the initial settings for the specific customer's tenant, if there is no history of the general users of the specific customer's tenant using the SaaS, the system identifies the stage of the specific customer's use of the SaaS as a specific stage. The system according to claim 6, characterized in that when the SaaS provisioning system identifies that the stage of use of the SaaS by the particular customer is the particular stage, and a certain period of time has elapsed since the initial identification of the stage of use of the SaaS by the particular customer as the particular stage, the system instructs the email distribution system to send an email to the administrator of the tenant of the particular customer requesting that the stage of use of the SaaS by the particular customer be advanced to the next stage.

9. An information processing device characterized by outputting an analysis result regarding the email, based on detection results from a tracking system that detects at least one of the opening of an email delivered by an email delivery system that delivers emails to users of the SaaS provided by a SaaS provisioning system, and a click on a link within the email, and the usage rate of the SaaS.

10. An analysis program characterized by causing a computer to display analysis results regarding the email, based on detection results from a tracking system that detects at least one of the opening of an email delivered by an email delivery system that delivers emails to users of the SaaS provided by a SaaS delivery system that provides the SaaS, and a click on a link within the email, and the usage rate of the SaaS.

Images