JP7625919B2 - Information processing device, program, system, and page data generation method - Google Patents

Description

The present invention relates to an information processing device, a program, a system, and a page data generation method.

Traditionally, marketing has been known to attract customers using mass media such as television, radio, magazines, and train advertisements, but in recent years, digital marketing using digital channels has become more common. Digital marketing refers to the use of all digital channels, such as websites, email, social media, smartphone apps, and the Internet of Things (IoT), to implement appropriate promotional measures and conduct marketing by visualizing customer data.

In digital marketing using websites, improving CVR (conversion rate) is becoming increasingly important. For this reason, experts in using websites repeatedly carry out the cycle of "measure CVR → propose improvements → implement improvements → measure CVR," and companies improve their websites according to the experts' guidance.

There is also known a technology that presents measures necessary to improve a website (see, for example, Patent Document 1). Patent Document 1 discloses a technology that collects information about access to a website, analyzes trends in access to the website from the collected data, and presents measures necessary to improve the website as recommended information according to the analysis results.

However, with conventional technology, the person in charge of managing the website needs to improve the website based on the presented recommendation information, which is time-consuming.

The present invention aims to provide an information processing device that can improve CVR.

In view of the above problems, the present invention provides an information processing device that provides page data of a website to a viewer terminal, and includes: a display order information determination unit that determines the access route with the most successful CV judgments as display order information based on an access history management table in which CV judgments are associated with each access route through which multiple pages included in the website are viewed; a communication unit that receives a request for page data of a first page; and a screen generation unit that generates page data of the first page including information regarding a second page to be displayed next to the first page based on the recommended display order information of multiple pages included in the website, the display order information including the display order of multiple pages with the highest CVR, and the communication unit transmits the page data of the first page generated by the screen generation unit to the viewer terminal.

It is possible to provide an information processing device that can improve CVR.

1A and 1B are diagrams illustrating a method for improving CVR performed by an information processing system. FIG. 1 is a diagram illustrating an example of a system configuration of an information processing system. FIG. 1 is a diagram illustrating an example of a hardware configuration of a computer system. 2 is an example of a functional block diagram showing functions of a viewer terminal, a HP publishing server, a support server, and an MA server in blocks. 11 is a diagram showing an example of the configuration of page data generated by a screen generating unit; FIG. 11 is an example of a sequence diagram in which the support server generates page data. 11 is a flowchart illustrating an example of a procedure for a screen generation unit to generate a top page. FIG. 13 is a diagram showing an example of a top page displayed by a viewer terminal. 11 is a flowchart illustrating an example of a procedure in which a screen generation unit generates a transition destination page. FIG. 13 is a diagram illustrating a display example of a product information page as a transition destination page. FIG. 13 is a diagram showing an example of page transition using a subheader.

Below, an information processing system and a page data generation method performed by the information processing system will be described as an example of a form for implementing the present invention.

<Overview of CVR Improvement>
First, in this embodiment, it is assumed that the website 505 has a plurality of web pages (hereinafter, simply referred to as pages), and the page displayed on the viewer terminal transitions from one page to another in response to the viewer's operation.

Figure 1 is a diagram explaining a method for improving CVR performed by the information processing system of this embodiment. As shown in Figure 1, each page of a website 505 mainly has the components of a header 501, a subheader 502, content 504, and a footer 503 (it may not have all of these). There are websites that have components other than these, but their explanation will be omitted in this embodiment.

The information processing system of this embodiment automatically generates the configuration of the header 501 and footer 503. As will be described in detail later, the information processing system places in the header 501 the page name included in the "route information with the highest CVR (=recommended access route)" that has been observed in advance, and a link to the page with that page name. Since the header 501 has a high chance of being seen by the viewer, it becomes easier for the viewer to view the website 505 in the order of the recommended access route.

The information processing system also places in the footer 503 the page names of pages that exist in the "page management table (list of all pages)" but not in the "suggested access route" and links to those pages. Because the footer 503 is rarely seen by viewers, it becomes difficult for viewers to view pages included in routes with low CVRs. In addition, links to pages that exist in the page management table can be left.

In addition, in this embodiment, the information processing system places a component called a subheader 502 on the website. In the subheader 502, the name of the next page in the recommended access route and a link to that page, or the name of the page with the lowest order among the pages not viewed by the viewer in the recommended access route and a link to that page, are placed. When the viewer presses the subheader 502, the pages are displayed in the order of the recommended access route, so that the information processing system can allow the viewer to view the pages in the order of the recommended access route. Even if the viewer deviates from the recommended access route, the information processing system can bring the viewer back to the recommended access route.

The subheader 502 may be displayed anywhere on each page. The location of the subheader 502 may vary depending on the page. Also, the subheader 502 is referred to as a header for convenience only, and does not need to have a similar format to a header, nor does it need to be recognized as a header. However, the subheader 502 is preferably displayed in a location that will attract the viewer's attention. Also, the subheader 502 is preferably displayed in a form (color scheme or size) that will attract the viewer's attention.

In this way, the information processing system of this embodiment can arrange the subheader 502 so that the viewer views the page along the recommended access route (the route with the highest CVR). By arranging the subheader 502, the homepage (hereinafter referred to as HP) can guide the viewer to view the HP along the recommended access route.

<Terminology>
A website is generally a collection of multiple web pages under a particular domain name. It is also sometimes called a home page.

A link is information written on a page that indicates the location of another page, and is called a "hyperlink," which is an abbreviation of this term. When a user clicks on the location of the link, the other page is displayed.

A header is information that is displayed at the top of a website and is described using the header tag. However, in this embodiment, the header tag does not necessarily have to be used.

The footer is information that is displayed at the bottom of a website and is described using the footer tag. However, in this embodiment, the footer tag does not necessarily have to be used.

The display order information is the recommended display order of multiple pages included in a website. Being recommended means that it will lead to increased effectiveness of the website from the perspective of the website provider. In this embodiment, the display order information is described by the term recommended access route.

<System configuration example>
2 is an example of a system configuration diagram of the information processing system 100. The information processing system 100 has a support server 50, a CMS server 20, an MA server 40, a HP publishing server 60, an administrator terminal 13, and a viewer terminal 14 that are capable of communicating via a communication network N. Being capable of communicating does not necessarily mean that communication is always possible, but rather that communication can be possible when necessary. In addition, the support server 50 and the CMS server 20 may be integrated, and may be called a service system 101 that serves as a gateway for HP-related services.

The communication network N is assumed to be a general network such as the Internet. It may include a LAN within a company or home, or a wide area Ethernet (registered trademark) or a WAN consisting of multiple LANs. The network may be partially or entirely wireless. Wireless networks may include wireless LAN, WiMAX, and mobile phone networks such as 3G, 4G, and 5G.

The support server 50, CMS server 20, MA server 40, and HP public server 60 are so-called server devices and have the functions of information processing devices. A server is a computer that provides files, data, etc. to other computers connected via a network. They may be called Web servers, HTTP servers, WWW servers, etc. However, the support server 50, CMS server 20, MA server 40, and HP public server 60 do not need to be dedicated server devices and may be general-purpose information processing devices.

The support server 50 is a server that provides the administrator with a one-stop service of the CMS server 20 and the MA server 40. The support server 50 provides a web application for creating a web site in cooperation with the CMS server 20 and the MA server 40. The support server 50 mainly accepts input of site creation information from the user, and generates parameters for creating a HP template so that the CMS server 20 can create a HP template according to the site creation information.

Note that in FIG. 2, the support server 50 and the CMS server 20 are separate entities, but the two may be integrated.

The CMS server 20 is a server that performs or supports lead generation to actualize potential customers. For example, it acquires customer information, acquires customer interest information, creates customer lists, etc. Specifically, the CMS server 20 is a server that provides a homepage creation tool that creates, updates, and manages homepages (i.e., websites). Note that in this embodiment, it is assumed that the homepage has already been created.

The HP publishing server 60 is a server that accepts requests to view the HP. The HP publishing server 60 may have HP data for each page of the website and transmit the page data to the viewer terminal 14, or the support server 50 may have the HP data and transmit the page data to the support server 50 in response to a request from the HP publishing server 60.

The MA server 40 is a server that performs or supports lead nurturing, which turns actualized customers into potential customers. The MA server 40 performs, for example, email distribution, printed matter delivery, opening counts, observation of other response behavior, response aggregation, accuracy analysis, approach classification, approach judgment, accuracy confirmation, scheduling of business meetings, first visits/revisits, proposals, contracts, etc. As a simple example, it provides an MA tool that performs access analysis for a website.

The CMS server 20 and the MA server 40 do not have to be separate servers, and one server may provide the CMS tool and the MA tool. In reality, many CMS servers 20 and MA servers 40 exist, and the support server 50 can link with each of the CMS servers 20 and MA servers 40. As for which CMS server 20 or MA server 40 to use, the support server 50 may select it based on the functions or cost of the CMS server 20 or MA server 40. If it is difficult or not troublesome for the user to select the CMS server 20 or MA server 40, the user may specify it. The support server 50 may present an index (function, popularity, etc.) for the user to select the CMS server 20 or MA server 40.

The support server 50, the CMS server 20, the MA server 40, or the HP publishing server 60 may correspond to a cloud system. A cloud system is a system that uses cloud computing, which is a form of usage in which computer resources are provided as a service via a computer network such as the Internet. However, on-premise cloud systems in which one or more of the support server 50, the CMS server 20, the MA server 40, and the HP publishing server 60 are located on-premise are also known.

The administrator terminal 13 is a terminal device used by an administrator, and is a general-purpose information processing device with communication and display functions. An administrator is a person who creates, operates, improves, etc. a website. Information processing devices that can serve as the administrator terminal 13 include, for example, a PC (Personal Computer), a tablet terminal, a smartphone, a mobile phone, and a wearable PC such as a watch-type PC. Other devices that can run browser software include electronic whiteboards, video conferencing terminals, digital signage terminals, and car navigation systems. There may be one or more administrator terminals 13.

The viewer terminal 14 is a terminal device used by a viewer of the website, and is a general-purpose information processing device with communication and display functions. An example of the viewer terminal 14 may be the same as the administrator terminal 13. It is assumed that there are multiple viewer terminals 14.

Browser software runs on the administrator terminal 13 and the viewer terminal 14. The support server 50 transmits page data (screen information for each page) to the administrator terminal 13. The CMS server 20 also publishes the HP on the HP publishing server 60, which transmits the page data of the HP to the viewer terminal 14. The page data is written in HTML, XML, a script language (JavaScript: registered trademark), and CSS (Cascade Style Sheet), etc. The website may be provided by a Web application. There is no clear definition of a Web application, but it refers to software or its mechanism that runs on a browser by cooperation between a program written in a script language (e.g. JavaScript (registered trademark)) that runs on the browser software and a program on the Web server side. Note that application software having equivalent functions may run on the administrator terminal 13 and the viewer terminal 14 instead of browser software.

<<Examples of hardware configurations of the support server, CMS server, MA server, HP publishing server, administrator terminal, and viewer terminal>>
The support server 50, the CMS server 20, the MA server 40, the HP publishing server 60, the administrator terminal 13, and the viewer terminal 14 are realized by a computer system having a hardware configuration shown in Fig. 3. Fig. 3 is a hardware configuration diagram of an example of a computer system 300 according to this embodiment.

As shown in FIG. 3, computer system 300 is constructed by a computer, and includes a CPU 201, a ROM 202, a RAM 203, a HD 204, a HDD (Hard Disk Drive) controller 205, a display 206, an external device connection I/F 208 (Interface), a network I/F 209, a bus line 210, a keyboard 211, a pointing device 212, a DVD-RW (Digital Versatile Disk Rewritable) drive 214, and a media I/F 216.

Of these, the CPU 201 controls the operation of the entire computer system 300. The ROM 202 stores programs used to drive the CPU 201, such as IPL. The RAM 203 is used as a work area for the CPU 201. The HD 204 stores various data such as programs. The HDD controller 205 controls the reading or writing of various data from the HD 204 according to the control of the CPU 201. The display 206 displays various information such as a cursor, menu, window, character, or image. The external device connection I/F 208 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or a printer. The network I/F 209 is an interface for data communication using the communication network N. The bus line 210 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 201 shown in FIG. 3.

The keyboard 211 is a type of input means equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 212 is a type of input means for selecting and executing various instructions, selecting a processing target, moving the cursor, etc. The DVD-RW drive 214 controls the reading and writing of various data from the DVD-RW 513, which is an example of a removable recording medium. Note that the DVD-RW is not limited to this, and may be a DVD-R or the like. The media I/F 216 controls the reading and writing (storing) of data from the recording medium 215, such as a flash memory.

<About the function>
Next, the functions of the support server 50, the MA server 40, the HP publishing server 60, and the visitor terminal 14 will be described with reference to Fig. 4. Fig. 4 is an example of a functional block diagram showing the functions of the visitor terminal 14, the HP publishing server 60, the support server 50, and the MA server 40 in blocks.

<<Viewer's device>>
The viewer terminal 14 has a first communication unit 21, an operation receiving unit 22, and a display control unit 23. Each of these functional units of the viewer terminal 14 is a function or means realized by any of the components shown in Fig. 3 operating in response to an instruction from the CPU 201 in accordance with a program loaded from the HD 204 to the RAM 203. This program may be, for example, browser software.

The first communication unit 21 transmits and receives various information to and from the HP publishing server 60. In this embodiment, the first communication unit 21 transmits a request to view the HP (URL) to the HP publishing server 60 and receives HP page data from the HP publishing server 60.

The display control unit 23 analyzes the page data received by the first communication unit 21 and displays it on the display 206. That is, the display control unit 23 displays a website (web page). The website allows the viewer to navigate between pages and enter information into an input field on an inquiry page.

The operation reception unit 22 receives various operations for the viewer terminal 14. For example, the operation reception unit 22 receives various inputs for the HP, instructions to receive information, and instructions to send information.

<<HP public server>>
The HP publishing server 60 has a second communication unit 61. In this embodiment, the HP publishing server 60 only relays the page data of the HP to the support server 50, and the generation of the page data and the like are performed by the support server 50. The second communication unit 61 transmits the URL of the requested HP to the support server 50, and transmits the page data transmitted from the support server 50 to the viewer terminal 14.

<<Support Server>>
The support server 50 has a third communication unit 51, a screen generation unit 52, an access history recording unit 53, and a recommended access route determination unit 49. Each of these functional units of the support server 50 is a function or means realized when any of the components shown in Fig. 3 operates in response to an instruction from the CPU 201 in accordance with a program loaded from the HD 204 to the RAM 203. This program is distributed from a server for program distribution, or is distributed in a state where it is stored in a storage medium.

The third communication unit 51 transmits and receives various information to and from the HP public server 60 and the MA server 40. Details will be described later.

The screen generation unit 52 generates page data by arranging a header 501, a footer 503, and a subheader 502 for the HP content 504 requested for viewing.

The access history recording unit 53 records in the recommended access route management table 58 whether or not the viewer has viewed each page of the recommended access route 57. The access history recording unit 53 also records in the access history management table 56 the order in which the websites were accessed.

The recommended access route determination unit 49 determines a recommended access route 57 based on the access history management table 56.

The support server 50 also has a memory unit 59 constructed in the HD 204 shown in FIG. 3 or the like. The memory unit 59 stores a page management table 54, HP data 55, an access history management table 56, a recommended access route 57, and a recommended access route management table 58. Of these, the HP data 55 is the HP content 504, and as it varies depending on the HP, a description thereof will be omitted.

表１は、ページ管理テーブル５４の一例を示す。ページ管理テーブル５４は、ＨＰが有するページの書誌情報などである。ＨＰはＵＲＬにより特定される。
・ページＩＤはＨＰが有する各ページの識別情報である。
・ページ名は、管理者にとってわかりやすいページの名称であり、例えばページのタイトルである。
・ページパスは、ＨＰのトップページから当該ページへ遷移するためのパス（フォルダ名）である。

Table 1 shows an example of the page management table 54. The page management table 54 contains bibliographic information of pages on a website. A website is specified by a URL.
The page ID is identification information for each page on the HP.
- The page name is a name of the page that is easy for the administrator to understand, for example, the title of the page.
The page path is the path (folder name) for transitioning from the top page of the HP to the page in question.

表２は、アクセス履歴管理テーブル５６の一例を示す。アクセス履歴管理テーブル５６は、ＨＰが有するページに対する各閲覧者のアクセス履歴が記録されたものである。
・アクセスＩＤは、閲覧者端末１４のアクセスごとに割り当てられる識別情報である。例えば、アクセスＩＤとしてセッションＩＤが使用されてもよい。
・アクセス日時は、閲覧者がＨＰのトップページにアクセスした日時である。
・アクセス元は、例えば閲覧者端末１４のＩＰアドレスである。
・アクセスルートは、閲覧者がＨＰ内の各ページを閲覧した順番である。
・ＣＶ判断は、ＭＡサーバ４０からＣＶ成功が通知されると「成功」となる。デフォルト値は「失敗」である。ＣＶ成功かどうかは、一例として、問い合わせがあったかどうかに基づくものとするが、ＣＶ成功の判断基準は管理者等が定義できる。例えば、商品の購入や申込みなどがＣＶ成功の基準となる場合もある。本実施形態では、閲覧者がお問い合わせすると、ＨＰに埋め込まれた「ＭＡタグ」によってＭＡサーバ４０に問い合わせがあった旨が通知される。この通知が支援サーバ５０にも送信され、支援サーバ５０はＣＶ成功かどうかを判断する。

Table 2 shows an example of the access history management table 56. The access history management table 56 records the access history of each visitor to pages on the HP.
The access ID is identification information assigned to each access of the viewer terminal 14. For example, a session ID may be used as the access ID.
The access date and time is the date and time when the viewer accessed the homepage of the website.
The access source is, for example, the IP address of the viewer terminal 14 .
- The access route is the order in which a visitor views each page on the website.
- The CV judgment becomes "success" when the MA server 40 notifies the success of the CV. The default value is "failure". As an example, whether or not the CV is successful is based on whether or not an inquiry has been made, but the criteria for judging whether or not the CV is successful can be defined by an administrator, etc. For example, the criteria for CV success may be the purchase or application of a product. In this embodiment, when a viewer makes an inquiry, the MA server 40 is notified that an inquiry has been made by an "MA tag" embedded in the homepage. This notification is also sent to the support server 50, which judges whether or not the CV is successful.

表３は、推奨アクセスルート５７の一例を示す。推奨アクセスルート５７は、表示されるページの次に表示すべきページの順番を記述した情報であり、本実施形態では、例えばＣＶＲが最も大きいアクセスルートである。
・順番は、推奨アクセスルート５７においてＨＰ内のページが閲覧される順番である。
・アクセスルートは、推奨アクセスルート５７に含まれる各ページのページ名（又はページＩＤ）である。

Table 3 shows an example of the recommended access route 57. The recommended access route 57 is information describing the order of a page to be displayed next to a currently displayed page, and in this embodiment, is, for example, the access route with the highest CVR.
The order is the order in which pages in the HP are viewed along the recommended access route 57.
The access route is the page name (or page ID) of each page included in the recommended access route 57.

The recommended access route determination unit 49 tallies the number of times the CV judgment is "successful" for each access route in the access history management table 56, and identifies the access route with the highest number of times the CV judgment is "successful" as the recommended access route 57. Alternatively, the recommended access route determination unit 49 may determine the access route with the highest ratio of the number of times the CV judgment is "successful" to the number of each access route as the recommended access route 57.

In addition, the recommended access route 57 is not limited to the one with the highest number of "success" CV judgments, but may be a top several recommended access routes 57.

The recommended access route determination unit 49 may tally up all access histories, or may tally up access histories for a predetermined period of time. Furthermore, the tallying process may be performed automatically, or may be performed at the instruction of an administrator. When the recommended access route determination unit 49 executes the process at a predetermined timing (for example, nighttime processing), the tallying process may be performed periodically (for example, tallying up once an hour) or in real time (tallying up immediately when a new access history is registered).

In addition, when counting the number of times the CV judgment is "successful," the recommended access route determination unit 49 may determine that if the same access route is included consecutively, it is the same access route. For example, if the CV is "successful" for an access route such as "product information ⇒ implementation case ⇒ inquiry," the access route "greetings from the president ⇒ product information ⇒ implementation case ⇒ inquiry," which includes this access route, may be counted as having a CV judgment of "success."

表４は、推奨アクセスルート管理テーブル５８の一例を示す。推奨アクセスルート管理テーブル５８は、推奨アクセスルート５７のうち閲覧者が閲覧したページをリアルタイムに記録する一時的なテーブルである（セッションが切れると消去される）。
・順番は、推奨アクセスルート５７においてＨＰ内のページが閲覧される順番である。
・アクセスルートは、推奨アクセスルート５７が有するページのページ名（又はページＩＤ）である。
・アクセス済みは、閲覧された場合にＹｅｓとなる（初期値はＮｏ）。

Table 4 shows an example of the recommended access route management table 58. The recommended access route management table 58 is a temporary table that records in real time the pages of the recommended access route 57 that the user has viewed (the table is deleted when the session ends).
The order is the order in which pages in the HP are viewed along the recommended access route 57.
The access route is the page name (or page ID) of the page included in the recommended access route 57 .
- Accessed becomes Yes if the page has been viewed (default value is No).

<<MA Server>>
The MA server 40 has a fourth communication unit 41 and an access management unit 42. Each of these functional units of the MA server 40 is a function or means realized by any of the components shown in Fig. 3 operating in response to an instruction from the CPU 201 in accordance with a program loaded from the HD 204 to the RAM 203.

The fourth communication unit 41 transmits and receives various information to and from the support server 50. In this embodiment, the fourth communication unit 41 receives information transmitted by the execution of the MA tag from the viewer terminal 14, and notifies the support server 50 that an inquiry has been made based on this information.

The access management unit 42 generates a notification that an inquiry has been made based on the information sent by the execution of the MA tag (in this embodiment, information accompanying the inquiry content).

<Composition of each page>
Fig. 5 is a diagram showing an example of the configuration of page data generated by the screen generation unit 52. The page data has, from top to bottom, elements of a header 501, a subheader 502, content 504, and a footer 503. For this reason, the screen generation unit 52 generates page data by arranging HTML data of the header 501, the subheader 502, content 504, and footer 503 in a template as shown in Fig. 5. The header 501 is displayed in the header area of the HP, the footer 503 is displayed in the footer area of the HP, the content 504 is displayed in the content area, and the subheader 502 is displayed in the subheader area.

- In the header 501, the page names and links of each page included in the recommended access route 57 are arranged in ascending order from left to right.

- Subheader 502 is an area where the message displayed changes dynamically depending on the viewer's access. In this message, a page name and link are placed to allow the viewer to view the website according to recommended access route 57, or a page name and link to lead the viewer back to recommended access route 57.

- Content 504 is page data of any page of HP data 55. It is a fixed area in which HP content 504 is displayed depending on the viewer's access.

- In the footer 503, the page names and links of each page not included in the recommended access route 57 are arranged from left to right with increasing page ID.

In Figure 5, the HP is shown as a table (as displayed on the viewer terminal 14, etc.), but the template for the page data is, for example, an editor where HTML data is stored.

<Overall operation of information processing system>
Next, the overall operation of the information processing system 100 will be described with reference to Fig. 6. Fig. 6 is an example of a sequence diagram in which the support server 50 generates page data. Note that the overall operation will be described first, and then detailed processing will be described with reference to the flow charts of Figs. 7 and 9.

S1: The viewer operates the viewer terminal 14 to input an operation to display the homepage of the website. The operation reception unit 22 receives this operation.

S2: The first communication unit 21 of the viewer terminal 14 sends a request for page data of the top page to the HP publication server 60. The page data of the top page is identified by a URL. It also includes the IP address of the viewer terminal 14.

S3: The second communication unit 61 of the HP publishing server 60 receives a request for page data of the top page and transfers the request to the support server 50.

S4: The third communication unit 51 of the support server 50 receives a request for page data of the top page, and generates page data of the top page identified by the URL. Details will be explained in Figure 7. The access history recording unit 53 assigns an access ID and generates an access history management table 56 and a recommended access route management table 58. The access history recording unit 53 registers the access ID, access date and time, access source, and access route (which gradually increase) in the access history management table 56. The access history recording unit 53 records the access ID, access date and time, access source, order, and access route (same as the recommended access route 57) in the recommended access route management table 58. The third communication unit 51 transmits the page data of the top page to the HP publication server 60.

S5-S6: Page data for the top page is sent to the viewer terminal 14. In this case, the access ID is also sent.

S7: The first communication unit 21 of the viewer terminal 14 receives the page data of the top page, and the display control unit 23 displays the top page. An example of the top page is shown in Figure 8.

S8: The viewer operates the viewer terminal 14 to input an operation to transition from the top page to another page. The operation reception unit 22 receives this operation.

S9: The first communication unit 21 of the viewer terminal 14 sends a screen transition request to the HP publication server 60. The screen transition request includes a URL. It also includes the IP address and access ID of the viewer terminal 14.

S10: The second communication unit 61 of the HP publishing server 60 receives the screen transition request and transfers the request to the support server 50.

S11: The third communication unit 51 of the support server 50 receives the screen transition request and generates page data for the transition destination page specified by the URL. Details will be explained in FIG. 9. The third communication unit 51 transmits the page data for the transition destination page to the HP publishing server 60.

S12: The access history recording unit 53 also records the page name of the transition destination page in the access route of the access history management table 56.

S13-S14: Page data for the destination page is sent to the viewer terminal 14.

S15: The first communication unit 21 of the viewer terminal 14 receives the page data of the transition destination page, and the display control unit 23 displays the transition destination page. An example of the transition destination page is shown in FIG. 10.

The viewer repeats steps S8 to S15 to display any page on the viewer terminal 14.

S16: The viewer operates the viewer terminal 14 to input information into the inquiry page and enters an operation to send. The operation reception unit 22 receives this operation.

S17: An MA tag is embedded in the inquiry page, and JavaScript (registered trademark) included in the MA tag collects information to be sent to the MA server 40. The information to be sent to the MA server 40 includes, for example, the access ID, the entered content, the destination email address included in the MA tag (the forwarding destination of the entered content), and the URL of the current page.

S18: The first communication unit 21 of the viewer terminal 14 transmits the MA information to the MA server 40.

S19: The fourth communication unit 41 of the MA server 40 receives the MA information, and the access management unit 42 specifies the URL and access ID based on the current URL and transmits a message to the support server 50 indicating that an inquiry has been made.

S20: The third communication unit 51 of the support server 50 receives the notification that an inquiry has been made, and the access history recording unit 53 determines that the CV was successful because an inquiry has been made. The access history recording unit 53 registers success in the CV judgment column of the access history management table 56, which is identified by the URL and access ID.

By storing the CV judgment in the access history management table 56, the recommended access route determination unit 49 can determine the recommended access route 57.

<Top page generation>
FIG. 7 is a flowchart showing an example of a procedure for the screen generating unit 52 to generate a top page.

The screen generation unit 52 places the page names of each page included in the recommended access route 57 in the header 501 of the template in Figure 5 in ascending order from left to right (S101).

The screen generating unit 52 acquires the page name of the page having the first page number from the recommended access route 57 (S102).
The screen generator 52 generates a message based on the acquired page name, and places the generated message as an initial value in the subheader 502 of the template in Fig. 5 (S103). The message has a predetermined template. For example, "Please see <page name>" is a template. The screen generator 52 generates the message by substituting the page name of step S102 for <page name>. A link to the page is embedded in the page name.

The screen generation unit 52 retrieves the requested top page content 504 from the HP data 55 and places it in the template content 504 of Figure 5 (S104).

The screen generation unit 52 places the page names of each page in the page management table 54 that is not included in the recommended access route 57 in the footer 503 of the template in Figure 5 so that the page IDs increase from left to right (S105).

The top page has now been generated. Note that the order of steps S101, S102, S103, S104, and S105 can be reversed.

Figure 8 is an example of a top page displayed by the viewer terminal 14. In the header 501, the names of each page in the recommended access route 57 are displayed from left to right in ascending order. Each page name has a page path in the page management table 54 embedded as a link.

The subheader 502 displays a message using the page name (product information) that is number 1 on the recommended access route 57. A link to the product information page is embedded in the page name.

Content 504 displays the contents of the top page.

In the footer 503, the names of each page that is not included in the recommended access route 57 are arranged from left to right with increasing page ID. Each page name has the page path in the page management table 54 embedded as a link.

<Generating destination page>
FIG. 9 is a flowchart showing an example of a procedure in which screen generating unit 52 generates a transition destination page.

The screen generation unit 52 retrieves the content 504 from the HP data 55 based on the URL of the destination page, and switches to the destination page (an example of the first page) (S201).

Next, the screen generation unit 52 identifies the page path of the transition destination page in the page management table 54, and obtains the page name corresponding to the page path from the page management table 54 (S202).

Next, the access history recording unit 53 sets "Yes" to the "Accessed" item corresponding to the page name of the transition destination page in the recommended access route management table 58 (S203). This is not necessary if the transition destination page is not registered in the recommended access route management table 58.

Next, the screen generation unit 52 determines whether the page name of the transition destination page is included in the recommended access route 57 (S204).

If the page name of the transition destination page is included in the recommended access route 57, the screen generation unit 52 obtains the page name of the page (an example of a second page) that corresponds next to the transition destination page from the recommended access route 57 (S205).

If the page name of the transition destination page is not included in the recommended access route 57, the screen generation unit 52 obtains the page name of the page with the lowest page order (an example of a second page) among the page names whose item value in the "Accessed" item is "No" in the recommended access route management table 58 (S206).

The screen generation unit 52 generates a message based on the acquired page name and places the generated message in the subheader 502 (S207). The message has a template. The template is, for example, "Please see <page name>." If "Product Information" is the destination page, the screen generation unit 52 generates the message by substituting the page name of "Introduction Examples", which is the next page of "Product Information", for <page name>.

Figure 10 is a diagram for explaining an example of the display of a product information page as a transition destination page. The header 501 and footer 503 are the same as the top page in Figure 8. Figure 10 shows an example in which the page name of the transition destination page is included in the recommended access route 57. A case in which it is not included will be explained in Figure 11.

The name of the page next to the product information page, which is the transition destination page in the recommended access route 57, is "Introduction Case Studies." In the subheader 502, the page name "Introduction Case Studies" is displayed in a message 506. In the content 504, the content 504 of the product information page, which is the transition destination page, is displayed.

<Example of page transitions using headers, footers, and subheaders>
As described above, by arranging the header 501 and the subheader 502 on each page of the HP, the HP can guide the viewer to view the HP via the recommended access route 57 .

Figure 11 is a diagram showing an example of a page transition using a subheader 502. The route in the upper part of Figure 11 is a recommended access route 57.

That is,
This shows a case where each page is displayed along a recommended access route 57 of product information page → introduction case page → inquiry page.

Therefore, when the viewer terminal 14 displays the product information page, the screen generation unit 52 places the links "Product Information Page," "Introduction Case Page," and "Inquiry Page" in the header 501 from the left.

In addition, in the recommended access route 57, the screen generating unit 52
The message 506 in the subheader 502 of the “product information page” 571 is set to the page name of the “case study page” that is next in order to the “product information page” 571 in the recommended access route 57 .
In the message 506 of the subheader 502 of the “Introduction example page” 572 , the page name of the “Inquiry page” that corresponds to the next page in the recommended access route 57 after the “Introduction example page” 572 is set.
Since there is no page that corresponds to the next page in the order after “Inquiry Page” 573 in the recommended access route 57 , “Inquiry Page” 573 does not have a subheader 502 .

In the footer 503, links to pages in the page management table 54 that are not in the recommended access route 57 are placed, so that the "Product Information Page" 571, "Introduction Case Page" 572, and "Contact Page" 573 have the "Company Information Page" and "Message from the President Page" placed in order of page ID.

On the other hand, the lower part of FIG. 11 shows pages that are not included in the recommended access route 57. For example, the "Company Information Page" 581 and the "Message from the President Page" 582 are not included in the recommended access route 57.

The header 501 and the footer 503 are generated in the same manner as the recommended access route 57. The screen generator 52 arranges the following sub-headers 502.
The "company information page" 581 is transitioned from the top page. The screen generation unit 52 places a link to the "product information page" 571, which has the lowest accessed number in the recommended access route management table 58, in the subheader 502 of the "company information page" 581.
The "Message from the President" 582 is transitioned from the "Product Information Page" 571. The screen generation unit 52 places a link to the "Introduction Example Page" 572, which has the lowest accessed number in the recommended access route management table 58, in the subheader 502 of the "Message from the President" 582.

Therefore, even if the viewer views a page that is not included in the recommended access route 57, the viewer can return to the recommended access route 57 by pressing the subheader 502.

<Major Effects>
The information processing system of this embodiment can arrange a subheader 502 in which a page name and a link are arranged so that a viewer views the page along a recommended access route (a route with the highest CVR). By arranging the subheader 502, the HP can guide a viewer to view the HP along the recommended access route.

<Other application examples>
The above describes the best mode for carrying out the present invention using examples, but the present invention is not limited to these examples in any way, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention.

For example, the support server 50, the HP publishing server 60, and the MA server 40 include multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link, including a network, shared memory, etc., to perform the processing disclosed herein. Similarly, the viewer terminal 14 may include multiple computing devices configured to communicate with each other.

The configuration examples in FIG. 4 and the like are divided according to main functions to make it easier to understand the processing by the viewer terminal 14, the support server 50, the HP publishing server 60, and the MA server 40. The method of dividing the processing units or the names of the processing units does not limit the present invention. The processing by the viewer terminal 14, the support server 50, the HP publishing server 60, and the MA server 40 can also be divided into even more processing units depending on the processing content. Also, one processing unit can be divided so that it includes even more processes.

14 Viewer terminal 20 CMS server 40 MA server 50 Support server 60 HP public server 100 Information processing system

JP 2019-079474 A

Claims (10)

An information processing device that provides page data of a website to a browser terminal,
a display order information determination unit that determines an access route with the most successful CV judgments as display order information based on an access history management table in which CV judgments are associated with each access route through which a plurality of pages included in the website are viewed;
A communication unit for receiving a request for page data of a first page;
a screen generating unit that generates page data of the first page including information about a second page to be displayed next to the first page based on the recommended display order information of a plurality of pages included in the website, the display order information including a display order of a plurality of pages having the highest CVR;
The communication unit is an information processing device that transmits the page data of the first page generated by the screen generation unit to the viewer terminal. The information processing device according to claim 1, wherein the screen generation unit places the page name of the second page on the first page as information about the second page, and embeds information indicating the location of the second page in the page name of the second page. When the first page is included in the display order information, the screen generating unit:
3 . The information processing apparatus according to claim 1 , further comprising: determining, in the display order information, that the page next in order to the first page is the second page to be displayed next to the first page. When the first page is not included in the display order information, the screen generating unit:
An information processing device as described in claim 1 or 2, wherein, based on a management table in which whether or not a page of the display order information has been displayed by the viewer terminal is registered for each page, the page that is lowest in the display order information among pages that have not been displayed by the viewer terminal is determined to be the second page to be displayed next to the first page. The information processing device according to claim 2, wherein the screen generation unit sets the page name of the second page to a predetermined message template and places the message on the first page. The information processing device according to any one of claims 1 to 5, wherein the screen generation unit arranges the page names of each page included in the display order information in the header area of the first page in ascending order from left to right. The information processing device according to any one of claims 1 to 6, wherein the screen generation unit arranges the page names of the pages of the website that are not included in the display order information in the footer area of the first page from left to right in order of increasing page ID. An information processing device that provides a web site's page data to a browser terminal,
a display order information determination unit that determines an access route with the most successful CV judgments as display order information based on an access history management table in which CV judgments are associated with each access route through which a plurality of pages included in the website are viewed;
A communication unit for receiving a request for page data of a first page;
a screen generating unit that generates page data of the first page including information about a second page to be displayed next to the first page, based on the recommended display order information of a plurality of pages included in the website, the display order information including a display order of a plurality of pages with the highest CVR;
The communication unit is a program that transmits the page data of the first page generated by the screen generation unit to the viewer terminal. A system having a viewer terminal and an information processing device that provides page data of a website to the viewer terminal,
The information processing device includes:
a display order information determination unit that determines an access route with the most successful CV judgments as display order information based on an access history management table in which CV judgments are associated with each access route through which a plurality of pages included in the website are viewed;
A communication unit for receiving a request for page data of a first page;
a screen generating unit that generates page data of the first page including information about a second page to be displayed next to the first page based on the recommended display order information of a plurality of pages included in the website, the display order information including a display order of a plurality of pages with the highest CVR;
the communication unit transmits the page data of the first page generated by the screen generation unit to the viewer terminal;
The viewer terminal includes:
The system further comprises a display control unit that displays the page data of the first page received from the information processing device. A page data generation method performed by an information processing device that provides a web site page data to a browser terminal, comprising:
a display order information determination unit determining, as display order information, an access route with the most successful CV judgments based on an access history management table in which CV judgments are associated with each access route through which a plurality of pages included in the website are viewed;
A communication unit receives a request for page data of a first page;
a screen generation unit generating page data of the first page including information about a second page to be displayed next to the first page based on the recommended display order information of a plurality of pages included in the website, the display order information including a display order of a plurality of pages having the highest CVR ;
a step of transmitting, by the communication unit, the page data of the first page generated by the screen generation unit to the viewer terminal;
The page data generating method includes:

Images