Unified data management device, unified data management program, and unified data management method

Abstract

To provide a technique for individually identifying a customer even if the customer visits a store without making a reservation, and easily grasping information regarding the customer's visit situation. [Solution] The information processing system acquires first customer visit order information including first identification information from an information communication terminal, issues second identification information if the first identification information included in the first customer visit order information is not registered in pre-stored customer relationship information, acquires second identification information corresponding to the first identification information from the customer relationship information if the first identification information included in the acquired first customer visit order information is registered in the customer relationship information, registers the first customer visit order information with the second identification information assigned to it in the customer visit order information, associates the customer visit order information with transaction information based on the second identification information and registers it in the customer relationship information, and when a specified period is acquired from the second information communication terminal, displays information regarding the customer's visit status on the second information communication terminal based on the customer relationship information compiled based on the specified period.

Description

[Technical field]

[0001] The present invention relates to a data unified management device, a data unified management program, and a data unified management method. [Background technology]

[0002] In recent years, an increasing number of users are reserving seats at restaurants, movie theaters, etc., via Web sites, or purchasing products sold on the Web sites. For example, a user uses a search engine to search for a store or the like that provides a service that the user desires to use, and accesses a Web site that appears in the search results and browses the site. If the site accessed is the desired site, the user will use the service of that site. On the other hand, if the site accessed does not match the user's purpose, the user will not use the service of that site and will move on to another searched website.

[0003] For this reason, in recent years, there has been a need among website operators to know how users are accessing the Internet. In response to this need, services have been provided that analyze how users are accessing websites and provide the results of that analysis.

[0004] The services provided include information on the number of visitors per page, the number of page views (PV), the average time spent on a page, bounce rate, exit rate, etc. The number of page views (PV) is the number of times a web page is displayed on the display unit of a user's terminal, and the bounce rate is the percentage of sessions in which only one web page was viewed (sessions in which the user left the site without moving from the page they started viewing to another page). The exit rate is, for example, the percentage of users who moved to another website or closed the web browser to stop viewing.

[0005] In response to such growing needs, for example, a Web analysis program has been disclosed that obtains aggregated results from a marketing analysis perspective (aggregated results corresponding to marketing analysis units) based on Web access logs (for example, Patent Document 1).

[0006] In addition, for example, it has been disclosed that an event feature model can be provided that can be used for comparison to estimate the potential possibility of access to the target access destination, even for new customers, by analyzing the tendency of access history for each unit period, deriving for each session a latent characteristic indicating the potential possibility of access to the target access destination, performing a principal component analysis on the frequency distribution of access to the latent characteristic for each unit period, deriving the distribution of the latent characteristic for each principal component, generating a latent characteristic principal component table that matches the principal components and the distribution of the latent characteristics, classifying the relative relationship of each principal component into a plurality of classes based on the results of the principal component analysis, generating a class composition ratio table that matches the classes and the principal component composition ratios for each class, and further generating an event classification table that matches the classes and the contents of the events carried out (for example, Patent Document 2).

[0007] Also disclosed is an access analysis image providing device that includes an acquisition unit that acquires multiple analysis results obtained by statistically analyzing access conditions to web pages, an evaluation unit that uses an analysis result selected from the multiple analysis results acquired by the acquisition unit according to a predetermined evaluation index to generate an evaluation result for each web page in multiple web pages within a website based on the predetermined evaluation index, and an image providing unit that provides an image that visualizes the evaluation results generated by the evaluation unit via a network (for example, Patent Document 3).

[0008] Also disclosed is an analysis information centralized management device that includes an acquisition unit that acquires user operation logs for content related to store reservations and advertisements from multiple websites, an analysis unit that analyzes user behavior for the content for each website based on the acquired operation logs, and a display control unit that aggregates user behavior for the content analyzed for each website in response to a display request from an information processing terminal, and displays the number of store reservations made via the multiple websites and user behavior for the content for each website on a monthly or daily basis on a display unit of the information processing terminal. [Prior art documents] [Patent documents]

[0009] [Patent Document 1] JP 2004-258977 A [Patent Document 2] JP 2009-244981 A [Patent Document 3] JP 2016-167168 A [Patent Document 4] JP 2020-201650 A Summary of the Invention [Problem to be solved by the invention]

[0010] Conventionally, customers who made reservations were required to provide information that could identify them when they registered their contact information in advance, making it possible to identify them later. However, customers who came to the store without a reservation were not registered in advance and placed an order, so even if they visited the store later, it was not possible to identify them as customers who had visited the store previously.

[0011] In addition, in Patent Document 4, the behavior of users with respect to the contents of each store on each website is displayed so that it can be visually checked in a unified manner, but the trends of customers who come from other than the website, such as customers who come to the store without making a reservation, are not taken into consideration. Therefore, it is difficult to easily grasp the order information of customers who visit the store and the situation of such customers visiting the store for the second or subsequent times.

[0012] Also, from a marketing perspective, it is important to capture new customers who visit without making a reservation and encourage them to return, thereby improving the repeat visit rate, i.e., increasing the number of repeat customers.

[0013] The present invention provides a data unified management technology that can individually identify customers, even if they come to a store without making a reservation, and easily grasp information about the customer's visit status. Also, the present invention provides a data unified management technology that can individually identify customers, even if they come to a store without making a reservation, and easily grasp information about the new customer's visit status. [Means for solving the problem]

[0014] In one embodiment of the present invention An information processing system including a first server device and a second server device, the first server device comprising: a storage unit that stores customer store order information that associates information regarding the customer's order or visit to a store, including first identification information transmitted from a first information communication terminal when a customer orders a product or service via the first information communication terminal, with second identification information that identifies the customer, and customer relationship information regarding a history of the customer store order information. the second server device acquires first customer store order information including first identification information transmitted from an information communication terminal of a first customer, issues second identification information for identifying the first customer when the first identification information included in the acquired first customer store order information is not registered in the customer relationship information, and acquires second identification information corresponding to the first identification information from the customer relationship information when the first identification information included in the acquired first customer store order information is registered in the customer relationship information, The first server deviceThe first customer store visit order information to which the issued or acquired second identification information has been added is registered in the customer store visit order information, the customer store visit order information and transaction information are associated with each other based on the second identification information and registered in the customer relationship information, and when a designated period is acquired from a second information communication terminal, the customer relationship information is compiled based on the designated period, and information regarding the store visit status of the customer is displayed on the second information communication terminal based on the compiled customer relationship information. ,child It is characterized by:

[0015] The above First server device The present invention is characterized in that customer relationship information relating to new customers during the specified period is extracted from the customer relationship information, and information relating to the store visit status of the new customers is displayed based on the extracted customer relationship information.

[0016] The above First server device is characterized in that it calculates a representative value of the visit interval or the visit frequency of each customer from the customer relationship information, and estimates the next visit date of each customer based on the most recent visit date of each customer and the representative value of the visit interval or the visit frequency.

[0017] The above First server device The method further includes notifying each of the customers of a predetermined message a predetermined period before the estimated next visit date.

[0018] The above First server device is characterized in that it calculates a representative value of the visit interval or the visit frequency for all or some of the customers from the customer relationship information, and estimates the next visit date of the new customer based on the first visit date of the new customer and the representative value of the visit interval or the visit frequency.

[0019] The above First server device The method further includes notifying the new customer of a predetermined message a predetermined period before the estimated next visit date.

[0020] The above First server device further stores segment extraction condition information including search conditions for extracting a group of customers that meets a predetermined search condition as segment information; First server device is characterized in that, when a target segment is specified from the second information communication terminal, segment information corresponding to the target segment is extracted from the segment extraction condition information as target segment information, and store operation status information including the number of reservations for the store and the behavior of the customers regarding the media used when they visited the store, aggregated by specified period, as well as the income and expenditure status of the store, the customer's store visit status, and the customer's order status, are displayed on the second information communication terminal based on the target segment information.

[0021] When the first identification information is identification information generated based on a communication application software installed in the first information communication terminal, the communication application software is communication application software for transmitting and receiving messages between users, in which a friend request is sent from the communication application software used by one user to the communication application software used by the other user, and the other user approves the friend request, thereby completing friend registration and enabling the users to transmit and receive messages, First server device The method is characterized by displaying the number of customers who have registered friends with the store.

[0022] The above First server device The above 1 The method is characterized in that the usage status of coupon information issued based on the identification information is monitored, and a predetermined notice is given to the customer based on the usage status of the coupon information.

[0023] The above First server deviceis characterized by displaying on the second information communication terminal the number of new customers, the customer's repeat visit rate, the cumulative sales amount, the average price per course, the table utilization rate, a ranking of popular courses, the frequency with which the customer uses the store, and the number of times the customer has used the store.

[0024] According to one embodiment of the present invention A program to be executed by an information processing system including a first server device and a second server device, and storing in a storage unit customer store order information that associates information regarding the customer's order or visit to a store, including first identification information transmitted from the first information communication terminal when a customer orders a product or service via the first information communication terminal, with second identification information that identifies the customer, and customer relationship information regarding a history of the customer store order information. and causing the second server device to execute a process of: Acquire first customer store order information including first identification information transmitted from the first customer's information communication terminal; When the first identification information included in the acquired first customer visit order information is not registered in the customer relationship information, a second identification information for identifying the first customer is issued, and when the first identification information included in the acquired first customer visit order information is registered in the customer relationship information, a second identification information corresponding to the first identification information is acquired from the customer relationship information. and causing the first server device to execute a process of: The first customer store order information to which the issued or acquired second identification information has been added is registered in the customer store order information, and the customer store order information and transaction information are associated with each other based on the second identification information and registered in the customer relationship information, and when a designated period is acquired from a second information communication terminal, the customer relationship information is compiled based on the designated period, and information regarding the store visit status of the customer is displayed on the second information communication terminal based on the compiled customer relationship information. vinegar R, process Execute the command.

[0025] According to one embodiment of the present invention, An information processing method to be executed by an information processing system including a first server device and a second server device, the first server devicestores in a storage unit customer store order information that associates information regarding the customer's order or visit to a store, including first identification information transmitted from the first information communication terminal when a customer orders a product or service via the first information communication terminal, with second identification information that identifies the customer, and customer relationship information regarding the history of the customer store order information; The second server device, acquire first customer visit order information including first identification information transmitted from an information communication terminal of a first customer, issue second identification information for identifying the first customer when the first identification information included in the acquired first customer visit order information is not registered in the customer relationship information, and acquire second identification information corresponding to the first identification information from the customer relationship information when the first identification information included in the acquired first customer visit order information is registered in the customer relationship information; The first server device, The first customer store visit order information, with the issued or acquired second identification information attached, is registered in the customer store visit order information, and based on the second identification information, the customer store visit order information and transaction information are associated with each other and registered in the customer relationship information, and when a designated period is acquired from a second information communication terminal, the customer relationship information is compiled based on the designated period, and information regarding the customer's store visit status is displayed on the second information communication terminal based on the compiled customer relationship information. Effect of the Invention

[0026] According to one aspect of the present invention, even if a customer comes to a store without making a reservation, the customer can be individually identified and information on the customer's visit status can be easily obtained. Also, even if a new customer comes to a store without making a reservation, the customer can be individually identified and information on the new customer's visit status can be easily obtained. [Brief description of the drawings]

[0027] [Figure 1] FIG. 1 is a diagram illustrating an overview of a data unification management device according to an embodiment of the present invention. [Diagram 2] FIG. 1 is a diagram illustrating an example of a network configuration according to an embodiment of the present invention. [Diagram 3]2 is a functional block diagram of a unified data management server, a store management server, an external linkage server, and a POS linkage server in the present embodiment. FIG. [Figure 4] 2 is a diagram showing an example of a data structure of a database managed by a data unified management server in the present embodiment. FIG. [Diagram 5] 4 is a diagram showing an example of a structure of an analysis information DB in the present embodiment. FIG. [Figure 6] FIG. 4 is a diagram showing an example of information items displayed on a store terminal in the present embodiment. [Figure 7] FIG. 4 is a diagram showing an example of data to be tabulated by an analysis and tabulation unit in the present embodiment. [Figure 8] 13 is a flowchart showing a process for acquiring customer identification information by a store management server according to the embodiment. FIG. [Figure 9] FIG. 13 is a diagram showing an example of a segment list screen in the present embodiment. [Figure 10] FIG. 13 is a diagram showing an example of a segment registration / editing screen in the present embodiment. [Figure 11] FIG. 2 is an overall sequence diagram according to the present embodiment. [Figure 12] FIG. 11 is a screen diagram showing an example of a data unified management screen in this embodiment (Example 1). [Figure 13] FIG. 11 is a screen diagram showing an example of a data unified management screen in this embodiment (Example 2). [Figure 14] FIG. 13 is a screen diagram showing an example of a data unified management screen in this embodiment (Example 3). [Figure 15] FIG. 13 is a screen diagram showing an example of a data unified management screen in this embodiment (Example 4). [Figure 16] FIG. 11 is a diagram showing an example of an analysis process flow for a target segment in this embodiment. [Figure 17] FIG. 13 is a diagram showing an example of a process flow for transmitting a notification encouraging a customer to visit the store next in this embodiment (Example 5). [Figure 18]FIG. 23 is a diagram showing an example of a process flow for transmitting a notification encouraging a customer to visit the store next in this embodiment (Example 6). [Figure 19] FIG. 2 is a block diagram showing an example of the configuration of a hardware environment of a computer that executes a program according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0028] 1 is a diagram illustrating an overview of a data unified management device according to an embodiment of the present invention. The data unified management device 1 includes a storage unit 2, an acquisition unit 3, an extraction unit 4, and a display control unit 5. An example of the data unified management device 1 is a data unified management server 15, which will be described later.

[0029] The storage unit 2 stores customer relationship information related to the history of customer store visit order information, which is information related to a customer's order or store visit including predetermined identification information transmitted from an information communication terminal when a customer orders a product or service via an information communication terminal. An example of an information communication terminal is a user terminal 17 described later. An example of the predetermined identification information is a unique ID, a telephone number, an email address, or a terminal ID described later. An example of customer store visit order information is order management information 49 described later or information related to a customer's store visit (for example, information that records the date and time of the store visit and the fact that the customer has already visited the store by receiving the customer at the store). An example of customer relationship information is a customer relationship management DB 35 described later. An example of the storage unit 2 is a memory unit 31 described later.

[0030] The acquisition unit 3 acquires first customer store visit order information including first identification information transmitted from the information communication terminal of the first customer. Examples of the first identification information include a unique ID, a telephone number, an email address, or a terminal ID, which will be described later. Examples of the first customer store visit order information include order management information 49, which will be described later, or information related to a customer's store visit (for example, information that records the store visit date and time, and the fact that the customer has already visited the store, by receiving the customer at the store). An example of the acquisition unit 3 is the acquisition unit 22, which will be described later.

[0031] The extraction unit 4 extracts customer store order information related to a customer during a first predetermined period (e.g., the same day, one week, two weeks, three weeks, four weeks, one month, two months, three months, etc.) based on the first identification information from the order-related information. An example of the extraction unit 4 is the analysis and tabulation unit 23 described later.

[0032] The display control unit 5 displays information about customer store visit status on a display device (for example, a display device) based on the extracted customer store visit order information. An example of the display control unit 5 is the display control unit 24 described below. Examples of the information about customer store visit status include the number of new customers on the day, the repeat customer rate, the average store visit interval, the average store visit frequency, and the like.

[0033] By configuring in this way, even if a customer comes to the store without making a reservation, the customer can be individually identified and information on the customer's visit status can be easily obtained. As a result, even if the customer does not input customer information in advance on a reservation site, etc., the customer can be identified using any one of the unique ID, telephone number, email address, terminal ID, etc. transmitted from the customer's information communication terminal as a key.

[0034] The extraction unit 4 may extract customer order information related to new customers during a first predetermined period from the order-related information based on the first identification information. The display control unit 5 may display information related to new customer visit status on the display device based on the extracted customer order information.

[0035] By configuring in this way, it is possible to individually identify new customers and easily grasp information on the visit status of new customers. As a result, even if the customer does not input customer information in advance on a reservation site, etc., the customer can be identified using any one of the unique ID, telephone number, email address, terminal ID, etc. transmitted from the customer's information communication terminal as a key.

[0036] The extraction unit 4 may calculate a representative value of the visit interval or the visit frequency of each customer from the customer relationship information, and estimate the next visit date of each customer based on the most recent visit date of each customer and the representative value of the visit interval or the visit frequency. Here, the representative value is a value used in statistics, such as the average, median, or mode. For example, when calculating a weighted average of visit intervals from the customer's visit history, the average may be calculated by weighting the more recent the visit dates are, the heavier the weight is. By configuring in this way, it is possible to estimate the next visit date of each customer.

[0037] The data unified management device 1 further includes a notification unit 6. The notification unit 6 may notify each customer of a predetermined message a third predetermined period (for example, one day before, two days before, etc.) before the estimated next visit date. By configuring in this way, it is possible to take action to have the customer come on the estimated next visit date.

[0038] The extraction unit 4 may calculate a representative value of the visit interval or the visit frequency for new customers from the customer relationship information, and estimate the next visit date based on the new customer's first visit date and the representative value of the visit interval or the visit frequency. Here, the representative value is a value used in statistics, such as the average (weighted average), median, or mode. For example, when calculating a weighted average of visit intervals from a customer's visit history, the average may be calculated by weighting the more recent the visit dates are, the heavier the weight is. By configuring in this way, it is possible to estimate the next visit date for a new customer.

[0039] The data unified management device 1 may further include a notification unit 6. The notification unit 6 may notify the new customer of a predetermined message a third predetermined period (for example, one day before, two days before, etc.) before the estimated next visit date. By configuring in this way, it is possible to take action to have the new customer come on the estimated next visit date.

[0040] The storage unit 2 stores segment extraction condition information including search conditions for extracting a group of customers matching a predetermined search condition as segment information. An example of segment extraction condition information is the segment management DB 34 described later. At this time, when a target segment is specified from the information processing terminal, the display control unit 5 extracts segment information corresponding to the target segment from the segment extraction condition information as target segment information. Based on the target segment information, the display control unit 5 causes the display unit of the information processing terminal to display store operation status information including the number of store reservations and customer behavior toward media, the store's income and expenditure status, customer store visit status, and customer order status, all of which are collected by a predetermined period.

[0041] By configuring in this manner, customer behavior, the store's income and expenditure situation, customer visits, customer ordering status, etc. can be analyzed for each pre-defined user group (segment) and displayed in a centralized manner.

[0042] In the case where the customer identification information is identification information generated based on the communication application software installed in the customer terminal device, the communication application software is communication application software for transmitting and receiving messages between users. Here, the communication application software is communication application software in which a friend request is sent from the communication application software used by one user to the communication application software used by the other user, and when the other user accepts the friend request, friend registration is completed and it becomes possible to transmit and receive messages between the users. In this case, the display control unit may display the number of customers who have established friend registration with the store.

[0043] By configuring in this way, for example, it is possible to know the total number of customers who have registered the store as a friend. Also, an operating parent company that operates multiple restaurants (stores) may display the total number of customers who have registered the store as a friend for all stores.

[0044] The extraction unit 4 may monitor the usage status of coupon information issued based on the customer identification information. In this case, the display control unit 5 may provide a predetermined notification to the customer based on the usage status of the coupon information.

[0045] With this configuration, it is possible to check the frequency with which customers use coupons, and to notify customers who do not use coupons or who use them infrequently of a message encouraging them to use coupons.

[0046] The display control unit 5 may display, as store operation status information, the number of new customers, the customer repeat visit rate, cumulative sales amount, average course price, table utilization rate, popular course ranking, frequency of customer use of the store, and number of times the customer has used the store.

[0047] By configuring it in this manner, it is possible to easily and centrally grasp the number of new customers, the repeat visit rate of customers, cumulative sales amount, average course price, table utilization rate, popular course rankings, frequency of customer use of the store, and number of times a customer has used the store.

[0048] 2 is a diagram showing an example of a network configuration in this embodiment. A Web server 11, an external linking server 12, a POS linking server 13, a store management server 14, a data unified management server 15, a store terminal 16, and a user terminal 17 are connected to a communication network 19.

[0049] The Web server 11 is a server device that manages a Web site (medium) for accepting reservations for stores, and provides users with a service for accepting reservations for various stores via the Web site (hereinafter, referred to as a Web reservation service).

[0050] 2, only one Web server 11 is shown for convenience, but in reality, multiple Web servers 11 may be connected. For example, one of the Web servers 11 may have Web site A (medium A) managed by company A that provides a reservation system. Another Web server 11 may have Web site B (medium B) managed by company B that provides reservation system B.

[0051] The various media (websites such as Website A (Medium A) and Website B (Medium B)) may be, for example, a reservation site for restaurants and other establishments managed by Company A, a site with a web search engine that provides web search services, or company-owned media.

[0052] The external linking server 12 is a server device operated by an external organization or another company. The external linking server 12 provides external information such as search analysis information provided by a company that provides a search service using a search engine, search analysis information of a map information providing service, information on the ranking of sites in search results, and the number of page views for each medium.

[0053] The POS linking server 13 is a server for linking a POS (Point of sale) system with the unified data management server 15. The POS linking server 13 obtains information (accounting information) on the chronological product names (product numbers, etc.) ordered, the amount, etc., of the payments made by the customer from the linked POS (Point of sale) system, and provides the information to the unified data management server 15.

[0054] The store management server 14 is a server device that manages store management information such as seat reservations from media (such as various websites and reservation services provided by other companies) for the restaurant, reservations by phone, reception of customers when they visit the restaurant, waiting in line, adjustment of seating arrangements, and orders. Orders include not only orders for eating in the restaurant, but also take-out orders and delivery orders. An order for eating in the restaurant is an order type that is made after a customer is shown to or sits down at a seat for eating in the restaurant. A take-out order is an order type that is made by using a reception terminal, an ordering terminal, or a user terminal 17 installed in the store to order products to be taken home. A delivery order is an order type that is made by having products ordered via the Internet or phone delivered to a specified location. The store management server 14 provides the store management information to the data unified management server 15.

[0055] The unified data management server 15 integrates, tabulates, and analyzes the external information provided by the external linking server 12, the transaction information provided by the POS linking server 13, and the store management information provided by the store management server 14, and centrally manages the integrated, tabulated, and analyzed information. In response to a request from the store terminal 16, the unified data management server 15 displays the integrated, tabulated, and analyzed information on the store terminal 16.

[0056] For example, the unified data management server 15 compiles and displays new customers, income and expenditure information, order information, etc. for each store, and compiles and displays ranked ordered items. Based on the provided external information, accounting information, and store management information, the unified data management server 15 collects all data related to store operation, such as media information, new customer information, sales information, and ranking information, and consolidates it into one so that it can be easily viewed from the store terminal 16.

[0057] The store terminal 16 is an information processing terminal located in the store where the store terminal 16 is installed, and includes, for example, a personal computer (PC), a smartphone, a tablet computer, etc. In this embodiment, the store terminal 16 is, for example, an information processing device of store A, a restaurant.

[0058] Although only one store terminal 16 is shown in FIG. 2 for the sake of convenience, there may be multiple store terminals 16 in one store, and each of multiple stores may have one or more store terminals 16.

[0059] The user terminal 17 is, for example, an information communication terminal having a communication function that is owned or occupied by each user, and includes, for example, a personal computer (PC), a smartphone, a tablet computer, etc. Although only one user terminal 17 is shown in FIG. 2 for convenience, there may be multiple user terminals.

[0060] An arbitrary OS (Operating System) is installed in the user terminal 17, and further application software is installed. For example, the application software may be a web browser, a chat application, an ordering application, a restaurant reservation application, etc. In Fig. 2, as an example, a chat application 18 is installed in the user terminal 17.

[0061] The chat application 18 is one of the communication tools, and when one user of user terminals having the chat application 18 installed sends a friend request to another user and the other user accepts the friend request, a friendship relationship is established between the users (this is called "friend registration"). When a friendship relationship is established, the users can share the same predetermined electronic space within the chat application 18 and can exchange messages in real time.

[0062] Here, it is assumed that the chat application 18 provides a service (chat application official account) that allows companies and stores to open accounts on the chat application 18 and directly distribute information to users who have registered as friends. Therefore, it is assumed that the store A has opened a chat application official account on the chat application 18. A customer can make a friend request to the chat application official account of the store A and register the account as a friend on the chat application 18 installed on the user terminal 17. Then, after registering as a friend, the customer can communicate with the store via the chat application official account of the store A. For example, the customer can make a reservation for the store, accept a visit to the store, place an order (take-out order, delivery order, etc.), and receive coupons and advertisement information via the chat application official account of the store A. When a customer makes a reservation for the store, accepts a visit to the store, places an order (take-out order, delivery order, etc.), or receives a coupon via the chat application official account of the store A, customer identification information (unique ID) is sent to the store management server 14 in the chat application 18 together with the reservation information and order information.

[0063] Also, on the store A side, the store terminal 16 can display the registered names of customers who are registered as friends (user names registered on the chat application 18) and the number of such customers on the management screen of the chat application 18.

[0064] A customer can access the Web server 11, for example, via a web browser or chat application 18 installed on the user terminal 17, to view a website for making a reservation at a restaurant, and click a button or the like on the website to make a reservation. A customer can also access the Web server 11, for example, via a web browser or application installed on the user terminal 17, to view a website for making a take-out order or a delivery order. Then, the customer can click a button or the like on the website to make a take-out order or a delivery order.

[0065] FIG. 3 shows a data unified management server according to this embodiment. Store management server, external linkage server, and POS linkage server 1 is a functional block diagram of the unified data management server 15. The unified data management server 15 includes a control unit 21 and a storage unit 31. The control unit 21 is a processing device that controls the entire unified data management server 15. The control unit 21 functions as an acquisition unit 22, an analysis and aggregation unit 23, and a display control unit 24 by reading and executing the program in this embodiment.

[0066] The acquisition unit 22 acquires external information provided by the external linking server 12, transaction information provided by the POS linking server 13, and store management information provided by the store management server 14. The acquisition unit 22 also acquires requests from the store terminal 16 to display a specific screen, register items entered on a specific screen to the server, and so on.

[0067] The analysis and aggregation unit 23 analyzes, for example, IMP, CVR, CV, CALL, CPC, CPA, ROAS, PV, dwell time, store data, reach, referrer, cookie, engagement, etc. from external information provided by the external link server 12.

[0068] IMP is an abbreviation for impression, and refers to an advertisement being displayed to a user, and the number of times it is displayed is called the "number of impressions." CVR stands for conversion rate, and indicates the percentage of the number of times an advertisement was clicked by a user that led to an outcome (conversion) such as a purchase or membership registration, which is the site's goal. CV is an abbreviation for conversion, and in the marketing field, refers to the final outcome of a website. CALL indicates a user action by telephone, such as an inquiry or reservation by telephone.

[0069] CPC is an abbreviation for "Cost Per Click" and indicates the cost per click. More specifically, it indicates the cost per click in pay-per-click online advertising, such as listing ads and some banner ads, where advertising fees are incurred for each click by a user.

[0070] CPA is an abbreviation for "Cost Per Action" and indicates the cost per customer acquisition, or more specifically, the cost incurred to acquire one customer, for example, through performance-based or pay-per-click advertising.

[0071] ROAS is an abbreviation for "Return On Advertising Spend" and is a figure obtained by dividing the sales generated through advertising by the advertising costs, and indicates the cost-effectiveness of advertising. ROAS can be calculated as sales / advertising costs x 100 (%) and means the "recovery rate of invested advertising costs."

[0072] PV is an abbreviation for "Page View" and represents the number of times a website, or a specific page within it, has been viewed, and is widely used as a general indicator of the size of a website.

[0073] The duration of a visit indicates the time spent on a target website by each person who came into contact with the website. Store data is, for example, store information acquired from a company's own website (owned media). Reach is the rate at which an advertisement reaches a user, and is an index showing how many users came into contact with a particular piece of content.

[0074] A referrer is a page that was the link source viewed immediately before a user came to a certain page. Referrers are recorded in the web server's access log, and not only the actions of users who transitioned from an external site, but also pages previously viewed within the same site are recorded as referrers.

[0075] Cookies are a mechanism for temporarily writing and storing data on a visitor's computer via a web browser. Cookies are used to identify visitors and are widely and commonly used as a core technology in personalization systems that customize the content displayed to each visitor.

[0076] Engagement represents the intimacy, strength of connection, affection, etc. between a company and consumers, and varies depending on what is used as an engagement indicator. For example, in the case of social networking services (SNS), engagement rates can be calculated from "likes," "comments," "shares," or the number of clicks.

[0077] In addition, the analysis and tabulation unit 23, for example, based on the accounting information 46 provided by the POS linkage server 13 and the store management information 47 provided by the store management server 14, tabulates new customers and income / expense information for each store, and tabulates and ranks ordered items.

[0078] Furthermore, the analysis and tabulation unit 23 aggregates store information scattered across various media and media for user groups (segments) that match the set search conditions based on the DB stored in the storage unit 31, and predicts store sales, call numbers, and media effects based on market conditions and past information, etc. Furthermore, the analysis and tabulation unit 23 aggregates new customers, income and expenditure information, etc. for each store for user groups (segments) that match the set search conditions based on the above DB and segment management DB 34.

[0079] In response to a request from the store terminal 16, the display control unit 24 causes the display unit of the store terminal 16 to display a predetermined screen so that the analysis results and the tabulation results by the analysis and tabulation unit 23 can be managed in a unified manner.

[0080] The memory unit 31 stores, for example, a reservation management DB 32, an order management DB 33, a segment management DB 34, a customer relationship management DB 35, an analysis information DB 36, and a transaction information DB 37. Store management information 47 provided by the store management server 14 is stored in the reservation management DB 32 and the order management DB 33 for each corresponding piece of information.

[0081] The reservation management DB 32 is a database that manages information regarding reservations of seats made through media (such as various websites and reservation services provided by other companies) and reservations made by telephone. The order management DB 33 is a database that manages detailed information regarding products ordered for in-store dining, takeout, and delivery. The segment management DB 34 is a database that manages search conditions in order to extract user groups (segments) that match the set search conditions. The customer relationship management DB 35 is a database that manages information regarding the store visit history of customers, and the medium from which each customer came in and the means used when visiting (such as telephone, web, chat app, etc.) obtained by the analysis results. The analysis information DB 36 is a database that manages the analysis results of external information by the analysis and aggregation unit 23 (for example, the number of page views, ranking information). The transaction information DB 37 stores transaction information 46 sent from the POS linkage server 13. Information regarding the reception and waiting of customers when visiting the store may be stored in the reservation management DB 32 or in a store reception waiting management DB (not shown).

[0082] The external linking server 12 provides external information 41 to the data unified management server 15. The external information 41 includes, for example, search engine analysis information 42, the number of page views of various media 43, third-party data 44, and company-specific data 45.

[0083] The search engine analysis information 42 includes search analysis information provided by companies that provide search services using search engines, search analysis information from map information providing services, and information on the ranking of sites in search results.

[0084] The number of page views of various media 43 is, for example, the number of page views of various media such as a restaurant introduction site, a restaurant introduction and review site, etc. The third-party data 44 includes, for example, a seasonal index, a day of the week index, a weather index, a market index, an advertisement index, and third-party perspective data. Customer trends are also affected by external factors such as the weather, so by using external influence data provided by external institutions and companies, more accurate analysis can be performed.

[0085] The seasonal index is a numerical representation of monthly sales fluctuations analyzed from past sales data. The day of the week index is a numerical representation of sales fluctuations for each day of the week analyzed from past sales data. The weather index is a numerical representation of sales fluctuations for each weather condition analyzed from past sales data. The market index is an index that aggregates the prices of a group of stocks selected based on certain rules into a single value using a simple average or weighted average.

[0086] An advertising index is, for example, an index that represents the quality of a specific search advertisement of a specific advertiser that has been placed in the past by a search engine, and basically, the higher the index is, the more users have selected the specific search advertisement of a specific advertiser in the past (for example, the more clicks per time have been made on the advertising information of the search advertisement) and the higher the sales of the product or service that is the target of the selected search advertisement.

[0087] Third-party data includes, for example, market analysts' opinions, industry growth rates based on the domestic economic situation, changes in trends between this year and last year, changes in end-user purchasing behavior, per capita consumption amounts, and future ups and downs.

[0088] The company-specific data 45 includes corporate data, store marketing information, member information, survey results obtained from customers / users, etc., personnel information, and information regarding sales promotion costs for a specific company.

[0089] The external information 41 may be stored in a storage device in the external link server 12, or may be stored in a storage device of another information processing device. Note that the external information 41 is merely an example and is not limited thereto, and may be information relating to factors that may affect the user's behavior regarding store reservations.

[0090] The POS linked server 13 provides transaction information 46 for each store obtained from the linked POS (Point of Sale) system to the centralized data management server 15. The transaction information 46 includes, for example, information (transaction information) about the chronological product names (item numbers, etc.) ordered by customers at each store, the quantity ordered, the amount, etc., as well as the date and time of payment. The transaction information 46 may be stored in a storage device within the POS linked server 13, or it may be stored in a storage device of another information processing device.

[0091] The store management server 14 provides store management information 47 to the unified data management server 15. The store management information 47 includes, for example, reservation management information 48 and order management information 49. The reservation management information 48 includes, for example, information regarding seat reservations made via media (such as various websites or reservation services provided by other companies), reservations made by phone, customer reception upon arrival at the store, and waiting in line. The order management information 49 includes, for example, information regarding dine-in orders, take-out orders, and delivery orders.

[0092] When a customer makes a reservation for a store, accepts a visit, places an order (take-out order, delivery order, etc.), or receives coupons or advertisement information via the chat application 18, the store management server 14 may obtain a unique ID from the user terminal 17 along with reservation information, acceptance information, order information, and coupon / advertisement receipt information.

[0093] For example, as shown in FIG. 3, assume that a customer uses the chat application 18 installed on the user terminal 17 to place an order (take-out order, delivery order, etc.) via the chat application official account of store A. In this case, the products to be ordered are temporarily stored in an order storage area called a cart in the chat application 18 (hereinafter referred to as "chat application cart 51"). When the ordered products are stored in the chat application cart 51, the chat application 18 generates a unique ID (e.g., a Universally Unique Identifier (UUID)). When the customer operates the chat application 18 to confirm the order, the chat application 18 transmits the unique ID to the store management server 14 together with the order information stored in the chat application cart 51. Note that, in the case of a second or subsequent order, the unique ID already generated is transmitted to the store management server 14 together with the order information stored in the chat application cart 51.

[0094] Also, for example, as shown in FIG. 3, assume that a customer accesses the ordering site of store A via a web browser installed in the user terminal 17 and places an order (take-out order, delivery order, etc.). In this case, the items to be ordered are temporarily stored in an order storage area called a cart in the web browser (hereinafter referred to as "WEB cart 52"). When proceeding with the order procedure on the ordering site, the customer is asked to enter a phone number, so the customer enters the phone number. After that, when the customer operates the web browser to confirm the order, the phone number 54 is sent to the store management server 14 via the web browser together with the order information stored in the WEB cart 52.

[0095] Also, for example, as shown in FIG. 3, when a customer places an order (take-out order, delivery order, etc.) using an ordering app for store A installed on user terminal 17, the items to be ordered are temporarily stored in an order storage area called a cart in the ordering app (hereinafter referred to as "ordering app cart 55"). When the ordered items are stored in the ordering app cart 55, the ordering app obtains a terminal ID from the user terminal 17. When the customer operates the ordering app to confirm the order, the ordering app sends the terminal ID 56 to the store management server 14 together with the order information stored in the ordering app cart 55.

[0096] In this way, by acquiring the unique ID 52, the telephone number 54, and the terminal ID 56, these can be used as identification information (customer identification information) for identifying the customer. Note that in the above, the unique ID 52, the telephone number 54, and the terminal ID 56 are acquired as customer identification information, but this is not limited thereto, and for example, an email address may be acquired.

[0097] The reservation management DB 32, order management DB 33, segment management DB 34, customer relationship management DB 35, analysis information DB 36, and transaction information DB 37 may be stored in a storage device of the centralized data management server 15. The reservation management DB 32, order management DB 33, segment management DB 34, customer relationship management DB 35, analysis information DB 36, and transaction information DB 37 may also be stored in or shared with a storage device of another information processing device (for example, the store management server 14).

[0098] FIG. 4 is a diagram showing an example of the data structure of a database managed by the data unified management server 15 in this embodiment.

[0099] The reservation management DB32 includes data items such as "store ID", "reservation ID", "visit ID", "customer name", "reservation date and time", "number of people", "unique ID", "telephone number", "email address", and "terminal ID". The item "store ID" stores identification information (store ID) that identifies a store. The item "reservation ID" stores identification information (reservation ID) that identifies reservation information about a reservation made by each customer. The item "customer ID" stores identification information (customer ID) that identifies a customer registered at the time of reservation. The item "customer name" stores the name of the customer registered at the time of reservation. The item "reservation date and time" stores the date and time of the reservation. The item "number of people" stores the number of people registered at the time of reservation. In the item "unique ID", if the chat application 18 is used at the time of reservation, the unique ID used in the chat application 18 is acquired and stored. In the item "telephone number", if a telephone number is input in an input form at the time of reservation, the telephone number is stored. In the item "email address", if an email address is input in an input form at the time of reservation, the email address is stored. In the item "Terminal ID", if a reservation is made via a specific application, the terminal ID of the user terminal 17 is acquired and stored. When making a reservation, a menu order for the day of the reservation can also be registered, and the information on the reserved menu is registered in the reservation management DB 32.

[0100] The order management DB33 includes data items such as "store ID", "reservation / visit ID", "order ID", "order date and time", "order content", "customer ID", "unique ID", "telephone number", "email address", and "terminal ID". The item "store ID" stores identification information (store ID) that identifies a store. The item "reservation / visit ID" stores the reservation ID of a customer who has made a reservation, and stores identification information (visit ID) that is newly issued to identify a customer who visits without a reservation. The item "order ID" stores identification information (order ID) that identifies the order of each customer. The item "order content" stores detailed information of each ordered item. The item "customer ID" stores identification information (customer ID) that identifies a customer. When an order is made via the chat application 18, the unique ID used in the chat application 18 is acquired and stored in the item "unique ID". When an order is made by telephone (for example, a take-out order or a delivery order), the telephone number is stored in the item "telephone number". In the item "email address", when an order is placed via the user terminal 17 and an email address is entered in the input form, the email address is stored. In the item "terminal ID", when an order is placed via the user terminal 17 and an order is placed via a predetermined app, the terminal ID of the user terminal 17 is acquired and stored. Note that the menu information for the reserved order registered in the reservation management DB 32 is registered in the order management DB 33 when the customer arrives at the store on the day and the reception (check-in) process is completed, and the order is processed.

[0101] The segment management DB34 includes data items such as "store ID", "segment ID", "segment name", "period", "usage type", "member type", "DB to be searched", and "conditions". The item "store ID" stores identification information (store ID) that identifies a store. The item "segment ID" stores a number (segment ID) that identifies a segment. The item "segment name" stores the name of the segment. The item "period" stores the period to be extracted that is set as a search condition. The item "usage type" stores the format in which the store was used (e.g., visiting the store, taking out, both, etc.). The item "membership type" stores whether the user is a member or non-member of the store, or both, etc. The item "DB to be searched" stores the name of the DB to be searched. The item "conditions" stores search conditions (e.g., an SQL WHERE statement).

[0102] The customer relationship management DB35 includes data items such as "store ID", "customer ID", "customer name", "unique ID", "telephone number", "email address", "terminal ID", "first visit date", "number of visits", and "last visit date". The item "store ID" stores identification information (store ID) for identifying a store. The item "customer ID" stores identification information (customer ID) for identifying a customer. The item "customer name" stores the name of the customer. The item "unique ID" stores a unique ID stored in the reservation management DB32 or the order management DB33. The item "telephone number" stores a telephone number stored in the reservation management DB32 or the order management DB33. The item "email address" stores an email address stored in the reservation management DB32 or the order management DB33. The item "terminal ID" stores a terminal ID stored in the reservation management DB32 or the order management DB33. The item "first visit date" stores the date of the first visit. The item "number of visits" stores the number of visits since the first visit date (first time). The item "Latest visit date" stores the date of the most recent visit. The customer relationship management DB 35 also stores the customer's visit history (dates of past visits to the store).

[0103] 5 is a diagram showing an example of the structure of the analysis information DB in this embodiment. The analysis information DB 36 may be stored in a storage device in the data unified management server 15, or may be stored in a storage device of another information processing device.

[0104] The analysis information DB36 includes, for example, "number of advertising media page views," "number of advertising media calls," "number of advertising media reservations," "analysis data of other companies' map services," "number of searches for other companies' map services and other actions," "search keywords for other companies' map services," "owned media search keywords," "number of owned media page views," "number of owned media calls," "number of owned media reservations," "advertising media costs," "owned media costs," "advertising media display ranking," "search display ranking," "cost per action," "simulation data," "various advertising data," "store data location information," "area population data," and "area business data."

[0105] "Number of advertising medium pageviews" is the number of pageviews of the store's (restaurant's) advertisement (including reservation reception screens, etc.; same below) on a medium (for example, a website provided by the web server 11; same below). "Number of advertising medium calls" is the number of calls made to the store via a page advertising the store on the medium. "Number of advertising medium reservations" is the number of reservations made for the store via a page advertising the store on the medium. "Other company map service analysis data" is analysis data for map services provided by other companies, and is information on access to the store's advertisement on the map service. "Number of searches on other company map services and other actions" is analysis data for map services provided by other companies, and is the number of searches for the store on the map service and the number of other actions. "Other company map service search keywords" is analysis data for map services provided by other companies, and is keyword information searched on the map service.

[0106] "Owned media search keywords" is keyword information searched on the company's website. "Owned media page views" is the number of page views on the company's website. "Owned media call count" is the number of calls made to the store via the company's website. "Owned media reservations" is the number of reservations made for the store via the company's website. "Advertising media costs" is the cost spent on advertising media. "Owned media costs" is the cost spent on the company's website. "Advertising media display ranking" is the display ranking of the store on advertising media.

[0107] "Search display ranking" is the search ranking when a search is made on a search engine. "Cost per action" is the cost per action. "Simulation data" is data obtained when a simulation is performed. "Various advertising data" is advertising data for various types of stores. "Store data location information" is information on the location of the store. "Area population data" is data regarding the population around the area where the store is located. "Area business data" is data regarding businesses around the area where the store is located.

[0108] FIG. 6 is a diagram showing an example of information items displayed on the store terminal in this embodiment. The store manager operates the store terminal 16 in this embodiment to access the data unified management server 15, and information on user behavior (action) by medium, which is unifiedly managed by store, is displayed on the display unit of the store terminal 16. The store terminal 16 displays, for example, "store name", "date", "number of page views by medium", "number of reservation calls", "number of calls (reservation not completed)", "number of WEB reservations", "weather", "maximum temperature", "minimum temperature", "search data at the time of access", "ranking when displayed with specific words", "predicted effect by medium", "cost-effectiveness alert by medium", "action rate / action cost by medium", "number of clicks by search engine advertising keyword", "various data of other companies' map services", "population data by area", and "number of businesses by area".

[0109] For "Store Name," if the same operator has multiple stores, selecting a store will display analysis information for the selected store. For "Date," analysis information is stored for each day, so by selecting daily or monthly on the screen, analysis information compiled for the selected unit will be displayed. For "Number of pageviews by medium," data is stored for each medium, and can be compiled by dividing it into, for example, "menu screen" and "course screen."

[0110] The "number of reservation calls" (the number of reservations made by phone), "number of calls (unsuccessful reservations)" (the number of reservations made by phone that were unsuccessful), and "number of web reservations" (the number of reservations made via the website) are obtained for each medium and displayed on the screen.

[0111] Data on "weather," "maximum temperature," "minimum temperature," "search data at the time of access," and "ranking when displayed for specific keywords" is stored on a daily basis.

[0112] For "Effectiveness forecast by medium," forecasts are calculated daily. For "Cost-effectiveness alert by medium," an alert is generated for media that are spending too much on advertising. For "Action rate / action cost by medium," examples include cost per page view, cost per visitor, cost per call, cost per online reservation, and ROAS, by medium. For "Number of clicks by search engine advertising keyword," data is obtained from other companies' advertising services. For "Various data from other companies' map services," data is stored daily. "Population data by area" shows the population and population pyramid by store area. "Number of businesses by area" is the number of businesses by store area.

[0113] 7 is a diagram showing an example of data to be tabulated by the analysis and tabulation unit in this embodiment. Examples of data to be tabulated by fixed or predetermined period such as day, week, month, year, a predetermined period designated by a user, or the entire period (hereinafter referred to as "by period") include "number of new customers", "repeat rate", "ROAS", "sales amount", "number of calls", "online reservation CVR", "number of accesses", "number of sessions", "bounce rate", "average stay time", "number of visits", "number of visitors", "average course unit price", "number of reservations", "table occupancy rate", "number of users by medium", "popular course ranking", etc.

[0114] "Number of new customers" represents the number of new customers by period. "Repeat rate" represents the percentage of customers who return (repeat rate) by period. "ROAS" represents the ROAS by period. "Sales amount" represents the sales amount by period. "Number of calls" represents the number of calls by medium or the total number of calls across all media by period. "Online reservation CVR" represents the CVR for reservations made via the internet by period. "Number of accesses" represents the number of calls by medium or the total number of calls across all media by period.

[0115] "Number of sessions" is an indicator that shows the number of times a user accessed a website during a certain period. The time from when a user accessed a specific website until they left is called a session, and the number of such sessions is called the number of sessions (also called the number of accesses or visits).

[0116] "Bounce rate" is the percentage of sessions during a given time period in which only one web page was viewed (i.e., sessions in which a user leaves the site without navigating to any other pages after the page they started viewing).

[0117] "Average visit duration" represents the amount of time spent on a specific website by period. "Number of visits" represents the number of visits (number of groups of customers who visited) by period. "Number of visitors" represents the number of visitors (number of customers who visited) by period. "Average course price" represents the unit price of courses ordered by period. "Number of reservations" represents the number of reservations by period. "Table occupancy rate" represents the table occupancy rate by period (the ratio of the number of tables that accommodated customers to the total number of seats). "Number of users by medium" represents the number of customers who came in through which medium (e.g. website, SNS, etc.) by period. "Popular course ranking" represents a ranking of products by the number of most ordered items by period.

[0118] 8 is a diagram showing a flowchart of the process of acquiring customer identification information by the store management server in this embodiment. The store management server 14 acquires information sent from the user terminal 17 (S1). The store management server 14 determines whether the acquired information is order management information 49 or reservation management information 48 (S2). Here, the reservation management information 48 and the order management information 49 each include customer identification information (e.g., a unique ID, a telephone number, an email address, a terminal ID, etc.).

[0119] If the acquired information in S2 is order management information ("order management information" in S2), the store management server 14 accesses the unified data management server 15 and queries the customer relationship management DB 35 as to whether there is customer identification information included in the order management information 49 (S3). If there is customer relationship information corresponding to the customer identification information in the customer relationship management DB 35 (YES in S4), the store management server 14 acquires a customer ID from the customer relationship information (S5). If there is no customer relationship information corresponding to the customer identification information in the customer relationship management DB 35 (NO in S4), the store management server 14 issues a new customer ID (S6).

[0120] After completing the process of S5 or S6, the store management server 14 issues a new order ID (S7). The store management server 14 transmits order management information (including the order ID and customer ID) to the unified data management server 15 (S8).

[0121] If the acquired information in S2 is reservation management information ("reservation management information" in S2), the store management server 14 accesses the unified data management server 15 and queries the customer relationship management DB 35 as to whether there is customer identification information included in the reservation management information 48 (S10). If there is customer relationship information corresponding to the customer identification information in the customer relationship management DB 35 (YES in S11), the store management server 14 acquires a customer ID from the customer relationship information (S12). If there is no customer relationship information corresponding to the customer identification information in the customer relationship management DB 35 (NO in S11), the store management server 14 issues a new customer ID (S13).

[0122] After completing the process of S12 or S13, the store management server 14 issues a new reservation ID (S14).The store management server 14 sends reservation management information (including the reservation ID and customer ID) to the unified data management server 15 (S15).

[0123] Fig. 9 is a diagram showing an example of a segment list screen in this embodiment. Fig. 9 shows an example of a segment list screen 71 that is displayed when a store manager accesses the data unified management server 15 using the store terminal 16.

[0124] The segment list screen 71 includes a search word input field 72, a Search button 73, an Add New button 74, and a segment list display field 75. When a search word (e.g., a segment name) is entered in the search word input field 72 and the Search button 73 is pressed, segment information 76 that matches the search word is displayed in the segment list display field 75. When the Add New button 74 is pressed, the segment registration / editing screen 81 in Figure 9 is displayed, and the segment information 76 can be added.

[0125] Segment information 76 added with the Add New button 74 is displayed in the segment list display area 75. Each piece of segment information 76 displays the segment name, registration date, update date, and number of target users, and includes an Edit button 77 and a Delete button 78. The number of target users indicates the number of users who meet the conditions set for that segment. Pressing the Edit button 77 displays a segment registration / edit screen 81 for that segment information 76, allowing the content to be edited. Pressing the Delete button 78 allows the segment information 76 to be deleted.

[0126] 10 is a diagram showing an example of a segment registration / editing screen in this embodiment. The segment registration / editing screen 81 includes a segment name input field 82, a search period input field 83, a usage type selection field 84, a membership type selection field 85, an additional condition setting field 86, an add condition button 87, and a register button 88.

[0127] The segment name input field 82 allows the user to input a segment name. The search period input field 83 allows the user to input a period to be searched. The usage type selection field 84 allows the user to select the usage type of the store to be searched for (visiting the store, take-out, or both). The membership type selection field 85 allows the user to select the type of membership to be searched for (members, non-members, or both).

[0128] In the additional condition setting field 86, a search item can be arbitrarily set by pressing an add condition button 87. For example, by pressing the add condition button 87, search items such as payment amount, number of times of store use, cumulative payment amount, average payment amount, age, date of birth, sex, place of residence, occupation, family structure, hobbies and preferences, site referral (from which website an approach was made), and route of site referral (natural search, direct transition, advertisement, email) are displayed, and an item to be added to the search condition can be arbitrarily selected from these.

[0129] When the register button 88 is pressed, the contents entered on the segment registration / edit screen 81 are transmitted to the data unified management server 15 and registered in the segment management DB 34 .

[0130] In this embodiment, the segment list screen 71 and the segment registration / editing screen 81 are displayed, as an example, when the data unified management server 15 is accessed, but they may also be displayed by accessing the store management server 14.

[0131] 11 is a diagram showing a flowchart of the analysis and tabulation process in this embodiment. The acquisition unit 22 acquires store management information 47 (reservation management information 48, order management information 49) from the store management server 14 (S21). The acquisition unit 22 registers the reservation management information 48 and the order management information 49 in the reservation management DB 32 and the order management DB 33, respectively (S22).

[0132] The acquisition unit 22 acquires external information 41 (search engine analysis information 42, number of pageviews of various media 43, third-party data 44, and company-specific data 45) from the external linkage server 12 (S23). The external information may include a seasonal index, a day-of-the-week index, a weather index, a market index, an advertising index, and third-party perspective data (market analysts' opinions, industry growth rates in light of the state of the domestic economy, changes in trends between this year and the previous year, changes in end-user purchasing behavior, information such as per capita consumption amounts, and information on future ups and downs, etc.).

[0133] The analysis and tabulation unit 23 analyzes the external information 41 and registers the analysis results (analysis information) in the analysis information DB 36 (S24). Here, the analysis and tabulation unit 23 analyzes the user's actions on the store contents for each store and each website from the acquired external information 41. Specifically, the analysis and tabulation unit 23 analyzes the "number of advertising medium PVs," ​​"number of advertising medium calls," "number of advertising medium reservations," "analysis data of other companies' map services," "number of searches and other actions for other companies' map services," "search keywords for other companies' map services," "owned media search keywords," "number of owned media PVs," ​​"number of owned media calls," "number of owned media reservations," "advertising medium costs," "owned media costs," "advertising medium display ranking," "search display ranking," "action cost," "simulation data," "various advertising data," "store data location information," "area population data," and "area business data" for each store and each website from the acquired external information 41. The analysis and tabulation unit 23 stores the analyzed information in the analysis information DB 36. The acquisition unit 22 acquires the transaction information 46 from the POS linkage server 13 and registers it in the transaction information DB 37 (S25).

[0134] The analysis and tabulation unit 23 tabulates the number of customers who visited the store on that day and the number of new customers from the order management DB 33 (S26). For example, the analysis and tabulation unit 23 extracts order management information about customers who visited the store on that day from the order management DB 33, and counts the number of records of the extracted order management information. The analysis and tabulation unit 23 extracts order management information about customers who have not visited the store on a day prior to the current day (new customers) from the extracted order management information, and counts the number of records of the extracted order management information.

[0135] The analysis and tabulation unit 23 calculates the repeat rate of customers who visited the store on that day (S27). That is, the analysis and tabulation unit 23 calculates the repeat rate by dividing (the number of customers who visited the store on that day - the number of new customers on that day) by the number of customers who visited the store on that day.

[0136] The analysis and tabulation unit 23 associates the store management information 47 (reservation management information 48, order management information 49) registered in the reservation management DB 32 and the order management DB 33 with the transaction information 46 registered in the transaction information DB 37, and registers the association in the customer relationship management DB 35 (S28). Here, for example, the analysis and tabulation unit 23 registers the visit date of the day (the first visit date if it is the first visit, or the most recent visit date if the customer has already visited) and updates the number of visits in the customer relationship management DB 35. At this time, the analysis and tabulation unit 23 registers part or all of the analysis information in the customer relationship management DB 35 based on predetermined rules. When registering the store management information 47 in the customer relationship management DB 35, information on overlapping customers may be unified by name matching. In this case, for example, the information may be unified with the customer relationship management information with the smaller customer ID (the difference is registered in the customer relationship management information with the smaller customer ID), and the customer relationship management information with the larger customer ID may be deleted.

[0137] The acquisition unit 22 determines whether or not a display request for a unified management screen for data of various media related to the store has been made from the store terminal 16 (S29). The analysis and tabulation unit 23 is in a waiting state (NO in S29) until a display request for a unified management screen for data of various media related to the store is made from the store terminal 16.

[0138] When a display request is made from the store terminal 16 for a data unified management screen for various media related to the store (YES in S29), the analysis and tabulation unit 23 acquires the designated period included in the display request (S30). The analysis and tabulation unit 23 tabulates the information registered in the customer relationship management DB 35 and the analysis information for the designated period (S31). The display control unit 24 displays the data unified management screen reflecting the tabulated daily information and analysis information on the display unit of the store terminal 16 (S32). For example, the analysis and tabulation unit 23 displays the number of customers visiting the store on the day tabulated in S26, the number of new customers visiting the store on the day, and the repeat customer rate of the day calculated in S27. Note that the customer relationship management DB 35 manages the most recent visit date and the number of visits to the store, so the analysis and tabulation unit 23 may calculate the number of customers visiting the store on the day, the number of new customers visiting the store on the day, and the repeat customer rate of the day from the customer relationship management DB 35.

[0139] Furthermore, for example, the analysis and tabulation unit 23 may tally up new customers and income and expenditure information for each store, or tally up ordered items and create a ranking, based on store management information 47 associated with the transaction information 46. Specifically, the analysis and tabulation unit 23 may tally up each item of information in store management information 47 associated with the transaction information 46 for a specified period, and cause the display control unit 24 to display it. Furthermore, for example, the analysis and tabulation unit 23 may calculate a cost per action based on store management information 47 associated with the transaction information 46. Here, the evaluation as a function of advertising cost is made using the advertising cost per click, the advertising cost per impression, or the advertising cost per reservation. These are referred to as the cost per action. The following process, for example, is performed as the process for calculating the cost per action. Media advertising costs ÷ PV Media advertising costs ÷ visitors Media advertising costs ÷ Number of reservations (total) Media advertising costs ÷ Online reservation email Media advertising costs ÷ number of calls Media advertising costs ÷ number of reservations Media advertising costs ÷ number of reservations Media advertising costs ÷ reservation sales Furthermore, the number of reservations is accumulated for each reservation channel (reservations made via website, telephone, etc.), and by linking this media data with call (number of phone calls) data, number of emails data, and POS (accounting) data, it becomes possible to calculate the cost per action that is more closely linked to user behavior.

[0140] The analysis and tabulation unit 23 also manages data by day, week, month, year, day of the week information, weather information, and area information. For example, the analysis and tabulation unit 23 manages data related to the tabulation results shown in Fig. 7. The analysis and tabulation unit 23 also manages data based on reservation composition ratios that depend on the following external influences, for example. Reservation composition ratio for each business day in the month Reservation composition ratio for each day of the week within the month Reservation composition ratio by weather within the month - Reservation composition ratio of monthly temperatures (e.g., in 1°C intervals) -Search ranking of search engines specified by the user · Store display ranking on each media site

[0141] The display control unit 24 may perform an alert process such as displaying a warning message or highlighting a corresponding portion on the screen depending on whether the action unit cost is higher or lower than a target value (threshold value) set by the store manager, and may cause the display unit of the store terminal 16 to display such a warning message or highlight the corresponding portion on the screen. The target value may be a target ratio (ratio).

[0142] This allows the system to identify media that are spending too much on advertising and issue an alert, making it easier for users to understand which media are cost-effective or not.

[0143] Also, suppose that the budget for each medium for a future month is entered on the unified data management screen by the store terminal 16. The display control unit 24 then determines the past trends of the store (day of the week, weather, trends for the past three months, trends compared to last year, etc.) based on the store management information 47 associated with the transaction information 46, and may perform a simulation process to determine how much conversion can be expected. In this case, the display control unit 24 may cause the display unit of the store terminal 16 to display the results of the simulation process.

[0144] This allows store managers to predict store sales, number of reservations (number of reservation calls, number of online reservations), and the effectiveness of each medium based on market conditions and information on the store's past performance, thereby increasing opportunities to improve profits.

[0145] In addition, regarding the simulation process, for example, a statistical method, correction values ​​based on various statistical models, multivariate analysis, or data mining may be used.

[0146] FIG. 12 is a screen diagram showing an example of the data unified management screen in this embodiment (Example 1).

[0147] In Figure 12, the data unified management screen 101 displays a daily usage status display field 102, a traffic summary display field 103, a display field for inflow customers by medium 104, a display field for visitor numbers by day of the week 105, a display field for the number of cancellations by medium 106, a display field for the number of cancellations by day of the week 107, a period setting field 108, a total sales display field 109, a number of cases display field 110, a number of people display field 111, an average course unit price display field 112, and a popular course ranking display field 113.

[0148] The period setting field 108 is a setting item field that displays the analysis status and tally status for the set period or date and time on the screen, and the year and month can be changed with the "Previous" button and the "Next" button. In addition, by pressing the "Monthly" button and the "Daily" button, respectively, the unit of tally on the data unified management screen 101 can be changed to monthly or daily.

[0149] When "daily" is set in the period setting field 108, the daily number of new customers, repeat rate, ROAS, sales amount, number of calls, and online reservation CVR are displayed in the daily usage status display field 102. When "monthly" is set in the period setting field 108, the monthly number of new customers, repeat rate, ROAS, sales amount, number of calls, and online reservation CVR are displayed.

[0150] The traffic summary display field 103 displays the number of users and their increase rate (e.g., compared to the previous month), the number of sessions and their increase rate (e.g., compared to the previous month), the bounce rate and its increase rate (e.g., compared to the previous month), and the average stay time and its increase rate (e.g., compared to the previous month).

[0151] The field 104 for displaying inbound customers by medium tallies which customers (inbound customers) made reservations or visited the restaurant from which medium (online advertisements, reservation sites, restaurant search apps, SNS, etc.) and displays this in a pie chart. The field 105 for displaying inbound customers by day of the week tallies the number of visitors by day of the week and displays this in a pie chart. The field 106 for displaying in a pie chart the number of cancellations by medium tallies the number of reservation cancellations by medium. The field 107 for displaying in a pie chart the number of reservation cancellations by day of the week.

[0152] The total sales display field 109 displays the total sales amount for this month, as well as a comparison with the previous month and the same month last year. The number of cases display field 110 displays the number of visits (number of groups visiting) for this month, as well as a comparison with the previous month and the same month last year. The number of people display field 111 displays the number of people visiting for this month, as well as a comparison with the previous month and the same month last year. The average course price display field 112 displays the average price of courses ordered this month, as well as a comparison with the previous month and the same month last year. The popular course ranking display field 113 displays the courses ordered this month in a ranking format from highest sales.

[0153] Fig. 13 is a screen diagram showing an example of a data unified management screen in this embodiment (Example 2). In Fig. 13, a data unified management screen 121 displays a reservation summary display field 122, a user number transition display field 123 by SNS, a call number transition display field 124, a repeat rate display field 125, and a new / existing ratio display field 126.

[0154] The reservation summary display field 122 displays the number of reservations, the total number of customers, and the table occupancy rate. The number of reservations displays the number of reservations (number of reservations) for this month, the comparison with the previous month, and the comparison with the same month last year. The total number of customers displays the number of customers (number of visitors) for this month, the comparison with the previous month, and the comparison with the same month last year. The table occupancy rate displays the table occupancy rate for this month, the comparison with the previous month, and the comparison with the same month last year. The SNS user number trend display field 123 displays the trend in the number of users by SNS from which users are coming.

[0155] The call number transition display field 124 displays the number of calls (number of incoming calls, number of answers, number of abandonments (=number of incoming calls - number of answers), and answer rate (=number of answers / number of incoming calls)) by day. The repeat rate display field 125 displays, for example, the repeat rate of visitors for a specified period, the entire period, or this month in a pie chart. The new / existing ratio display field 126 displays, for example, the ratio of new visitors to existing visitors for a specified period, the entire period, or this month in a pie chart.

[0156] 14 is a screen diagram showing an example of a unified data management screen in this embodiment (Example 3). In FIG. 14, a unified data management screen 131 displays a monthly trend display field 132 and a keyword search ranking display field 136.

[0157] The monthly trend display field 132 displays a stacked bar graph 133 of the number of searches, a stacked bar graph 134 of the number of impressions, a stacked bar graph 135 of the number of responses, and a table 136 corresponding to them. The stacked bar graph 133 of the number of searches graphs the number of direct searches (direct searches: the number of searches where a store name or address was directly searched) and indirect searches (searches for related products, services, and categories, e.g., searches for "Italian restaurants nearby"). The stacked bar graph 134 of the number of impressions graphs the number of impressions depending on whether a search engine or a map display service was used. The stacked bar graph 135 of the number of responses graphs the number of times a website was accessed, a route to a store was confirmed, or a phone call was made.

[0158] The keyword search ranking display field 137 displays the most frequently searched keywords in a ranking format.

[0159] Fig. 15 is a screen diagram showing an example of a data unified management screen in this embodiment (Example 4). In Fig. 15, a data unified management screen 141 displays a user inflow channel transition graph display field 142 and a user inflow channel comparison numerical value display field 143.

[0160] The user inflow channel trend graph display field 142 displays a stacked bar graph showing the trend in the number of visitors for each user inflow channel (natural inflow, direct inflow, search ads, display ads, via other sites, via email, via SNS, and others (including unknown)). The user inflow channel comparison numerical value display field 143 displays a table corresponding to the user inflow channel trend graph display field 142.

[0161] It should be noted that the screens of Figures 12 to 15 can be displayed one after the other by scrolling the data unified management screens 101, 121, 131, and 141. It should be noted that the layouts of Figures 12 to 15 are merely examples and are not limited to these.

[0162] Furthermore, by pressing a button (not shown) on the data unified management screens 101, 121, 131, and 141, the reservation status and access status from each medium or all media, store sales, customer status, various rankings, inflow routes, etc., for a user group included in a selected segment may be tallied and displayed based on the segment management DB 34. This will be described with reference to FIG.

[0163] 16 is a diagram showing an example of an analysis process flow for a target segment in this embodiment. First, the store manager operates the store terminal 16 to access the data unified management server 15 and display the segment registration / editing screen 81. Then, the store manager sets conditions (segment information) for extracting users who match predetermined search conditions on the segment registration / editing screen 81. After setting, when the registration button 88 is pressed, a segment registration request is sent to the data unified management server 15.

[0164] If a segment registration request is made (YES in S41), the control unit 21 registers the setting contents in the segment management DB 34 (S42). Here, regarding the items displayed on the segment registration / editing screen 81, which items are included in which DB is managed in a search item / DB name management DB (not shown). This allows the control unit 21 to set the name of the DB to be searched in the "DB to be searched" in the segment management DB 34. The control unit 21 also generates a WHERE statement in SQL based on the conditions set on the segment registration / editing screen 81, and sets the WHERE statement in the "conditions" in the segment management DB 34.

[0165] Next, the store manager operates the store terminal 16 to display the segment list screen 71, and selects a target segment to be analyzed and tabulated from one or more created segments. The store manager operates the store terminal 16 to display a unified data management screen for the target segment. Then, a view request specifying the target segment is sent to the unified data management server 15.

[0166] When a display request for a data unified management screen for the target segment of the store is made from the store terminal 16 (YES in S43), the control unit 21 acquires segment information corresponding to the target segment from the segment management DB 34 (S44). The control unit 21 acquires the "search target DB" and "conditions" from the segment information, and generates SQL using the "search target DB" and "conditions". The control unit 21 uses the SQL to search the DB to be searched (S45).

[0167] As a result of the search, the control unit 21 extracts various information about users (target segment) that match the search conditions, and performs tabulation and analysis by period (S46). Specifically, the control unit 21 performs tabulation for the target segment using store management information 47 associated with transaction information 46 and analysis information, and displays unified data management screens 101, 121, 131, 141 for the target segment of that store (S47).

[0168] In this way, the data unified management screens 101, 121, 131, 141 can display reservation status and access status from each medium or all media, store sales, customer status, various rankings, inflow routes, etc. in table and graph formats. This makes it possible to display user behavior for store content for each medium, the store's income and expenditure status, business status, etc. in a unified manner.

[0169] In addition, a medium name can be specified in a medium designation field (not shown) to select the medium on which the aggregation and analysis results are to be displayed on the data unified management screens 101, 121, 131, and 141, thereby selectively displaying the medium of interest.

[0170] In addition, the statistical graph to be displayed is not limited to a bar graph, and may be, for example, a line graph, a pie chart, a band graph, a scatter plot, a radar chart, etc., depending on the statistical method, ease of viewing, etc. The format of the graph to be displayed may be switched by pressing a switching button provided on the data unified management screen 101, 121, 131, 141.

[0171] As described above, a warning message or highlighting can be displayed according to the action cost on the unified data management screens 101, 121, 131, and 141. This allows the store manager to recognize at a glance what matters to pay attention to.

[0172] Furthermore, a simulation execution button may be provided on the unified data management screens 101, 121, 131, and 141. When the simulation execution button is pressed, the analysis and tabulation unit 23 determines the past trends (day of the week, weather, trends for the past three months, trends compared to last year, etc.) of the store based on the reservation management DB 32 and order management DB 33, and performs a simulation process to determine how much conversion can be expected. The display control unit 24 can display the results of the simulation process on the unified data management screens 101, 121, 131, and 141.

[0173] In addition, historical information such as reservation information for a seat at the store, order information at the store, and payment information may further include historical information regarding reservation information for a seat at the store, order information at the store, website information or web service information from which the information originates when a reservation, take-out order, or delivery order is made via the Internet, and payment information.

[0174] In addition, when a customer registers the official account of the store as a friend in the chat app, the total number of customers who are registered as friends can be displayed on the store's management screen. At this time, the total number of customers who are registered as friends may be displayed on a centralized data management screen. In addition, in the case of a management organization that operates multiple stores, the total number of customers who are registered as friends may be displayed on the centralized data management screen for each store or for all stores.

[0175] The unique ID and order information acquired from the chat application are registered together in the customer relationship management DB 35. Therefore, the analysis and aggregation unit 23 can aggregate the information registered in the customer relationship management DB 35 and calculate the frequency of use of the store, the number of times the store has been used, and the cumulative sales ranking of the products and services. At this time, the display control unit 24 may display the frequency of use of the store, the number of times the store has been used, the cumulative sales ranking of the products and services, etc. on the unified data management screen.

[0176] The customer relationship management DB 35 also manages information regarding coupons used for each individual's identification ID (for example, "customer ID," "unique ID," "telephone number," "email address," or "terminal ID"). Thus, the analysis and tabulation unit 23 can manage the frequency of coupon use for each customer in the customer relationship management DB 35. The analysis and tabulation unit 23 may extract customers who have not used coupons or have used them infrequently (for example, once or twice) from the customer relationship management DB 35, and notify the customers by a chat app (message transmission, push notification), SMS (short mail service), email, etc., encouraging them to use coupons.

[0177] Conventionally, it was not possible to identify customers who did not make a reservation (customers who came to the store without a reservation), but in this embodiment, the customer identification information of customers who approached through various media can be managed in a unified manner, making it possible to perform various analyses. That is, the customer identification information of customers who approached through various media is associated with the reservation ID in the reservation management DB 32 and the order ID in the order management DB 33, making it possible to perform various analyses.

[0178] In addition, in this embodiment, by using the unique ID of the chat app, it is possible to manage customer information limited to individuals. For example, even if a customer has never visited a store, if the customer registers the official account of the store in the chat app and is registered as a friend, the store can identify the customer.

[0179] In addition, when making reservations or orders (take-out orders, delivery orders) via a web browser, if you ask customers to enter their phone number in the phone number input field on the input form, it will be possible to analyze each individual person using their phone number and order ID.

[0180] In addition, a survey may be conducted via a chat app, website, etc., and the survey information may be associated with an individual's identification ID (e.g., "customer ID," "unique ID," "telephone number," "email address," or "terminal ID," etc.) and registered in the customer relationship management DB35, thereby enabling management of data with even higher purity.

[0181] Next, a fifth embodiment of the present invention will be described. In the fifth embodiment, a date of a customer's next visit is estimated based on the frequency of the customer's visit to the store that is equal to or greater than a predetermined number of times, and a notification is sent to the user to encourage the user to visit the store next.

[0182] 17 is a diagram showing an example of a process flow for sending a notification encouraging the next visit in this embodiment (Example 5). The data unified management server 15 extracts customer relationship information of customers who have visited the store a predetermined number of times (e.g., 2 times, 3 times, etc.) or more within a predetermined period (e.g., 1 week, 2 weeks, 3 weeks, 4 weeks, 10 days, 15 days, 30 days, 1 month, 2 months, 3 months, etc.) from the customer relationship management DB 35 (S51).

[0183] The data unified management server 15 calculates the number of store visits of each customer from the extracted customer relationship information (S52). The data unified management server 15 calculates a representative value (e.g., average (including weighted average), median, mode, etc.) of the store visit interval for each customer by dividing the above-mentioned predetermined period by the number of store visits for each customer (S53). Alternatively, the data unified management server 15 may calculate a representative value (e.g., average (including weighted average), median, mode, etc.) of the store visit interval for each customer from the store visit history included in the customer relationship information. Alternatively, the data unified management server 15 may calculate the store visit frequency for each customer from the store visit history included in the customer relationship information or the above-mentioned predetermined period. For example, the data unified management server 15 may calculate the store visit frequency for each customer by dividing the number of store visits in the above-mentioned predetermined period for each customer by the above-mentioned predetermined period.

[0184] For example, when calculating a weighted average of visit intervals from a customer's visit history, the average may be calculated by weighting the more recent visit dates (or the older visit dates) so that the weight is heavier (or lighter). For example, if the visit history is January 21, January 28, February 3, February 8, February 17, and February 22, the visit intervals are 7 days (January 21-January 28), 6 days (January 28-February 3), 7 days (February 3-February 8), 9 days (February 8-February 17), and 5 days (February 17-February 22). In this case, a weighted average ((5×1.0+9×0.9+7×0.8+6×0.7+7×0.6)÷5=5.42) may be calculated by decreasing the weights from the most recent visit interval by 1.0, 0.9, 0.8, etc. Or, for example, a weighted average ((5×1.0+9×0.8+7×0.7+6×0.6+7×0.4)÷5=4.7) may be calculated by decreasing the weights from the visit interval by 1.0, 0.9, 0.8, etc. for every five days going back from the most recent visit date.

[0185] In addition, for example, the standard deviations σ, 2σ, and 3σ of the visit intervals are calculated, and if the visit interval is within the range of -σ≦average visit interval≦+σ, the weight of the weighted average can be set to "1.0", if the visit interval is within the range of -2σ≦visit interval<-σ, or +σ<average visit interval≦+2σ, the weight of the weighted average can be set to "0.9", and if the visit interval is within the range of -3σ≦visit interval<-2σ, or +2σ<average visit interval≦+3σ, the weight of the weighted average can be set to "0.8".

[0186] The data unified management server 15 estimates the next visit date for each customer based on the representative value of the visit interval for each customer (S54). For example, if the average visit interval for a certain customer is 7 days, the data unified management server 15 estimates the next visit date as the date obtained by adding the average visit interval (=7 days) to the most recent visit date of the customer. Alternatively, the data unified management server 15 may estimate the next visit date for each customer based on the frequency of visits of each customer. For example, if the frequency of visits of a certain customer is 1 / 7, the data unified management server 15 may estimate the next visit date as the date obtained by adding the reciprocal of the visit frequency (=7 days) to the most recent visit date of the customer.

[0187] The data unified management server 15 notifies the customers of each extracted customer relationship information of a message encouraging them to visit the store together with a coupon a predetermined period (e.g., one day or two days before) prior to the estimated store visit date (S55). The notification is made using a contact method (chat app, phone number, email, SMS, etc.) registered in the customer relationship information.

[0188] Next, a sixth embodiment of the present invention will be described. In the sixth embodiment, an example will be described in which the next visit date of a new customer is estimated and a notification is given to encourage the new customer to visit the store again.

[0189] 18 is a diagram showing an example of a process flow for sending a notification encouraging the next visit in this embodiment (Example 6). The data unified management server 15 extracts customer relationship information of customers who have visited the store a predetermined number of times (e.g., 2 times, 3 times, etc.) or more within a predetermined period (e.g., 1 week, 2 weeks, 3 weeks, 4 weeks, 10 days, 15 days, 30 days, 1 month, 2 months, 3 months, etc.) from the customer relationship management DB 35 (S61).

[0190] The data unified management server 15 calculates the number of store visits for each customer from the extracted customer relationship information (S62). The data unified management server 15 divides the above-mentioned predetermined period by the total number of store visits for all extracted customers to calculate a representative value of the store visit interval for all extracted customers (for example, the average (including weighted average), median, mode, etc.). Alternatively, the data unified management server 15 may calculate a representative value of the store visit interval for each customer from the store visit history included in the customer relationship information, and then calculate the average store visit interval for all customers. Alternatively, the data unified management server 15 may calculate the store visit frequency for each customer from the store visit history included in the customer relationship information or the above-mentioned predetermined period. For example, the data unified management server 15 may calculate the frequency of store visits for each customer by dividing the number of store visits in the specified period by the specified period, and then calculate the average (or median, or mode) of the frequency of store visits for all customers.

[0191] For example, when calculating a weighted average of visit intervals from a customer's visit history, the average may be calculated by weighting the more recent visit dates (or the older visit dates) so that the weight is heavier (or lighter). For example, if the visit history is January 21, January 28, February 3, February 8, February 17, and February 22, the visit intervals are 7 days (January 21-January 28), 6 days (January 28-February 3), 7 days (February 3-February 8), 9 days (February 8-February 17), and 5 days (February 17-February 22). In this case, a weighted average ((5×1.0+9×0.9+7×0.8+6×0.7+7×0.6)÷5=5.42) may be calculated by decreasing the weights from the most recent visit interval to 1.0, 0.9, 0.8, etc. Or, for example, a weighted average ((5×1.0+9×0.8+7×0.7+6×0.6+7×0.4)÷5=4.7) may be calculated by decreasing the weights from the visit interval to 1.0, 0.9, 0.8, etc. for every five days going back from the most recent visit date. After calculating the representative value of the visit interval for each customer in this way, this is used to calculate the average (or median, mode) of the representative values ​​of the visit intervals for all customers.

[0192] Also, for example, the standard deviations σ, 2σ, and 3σ of the visit intervals are found, and if the visit interval is within the range of -σ≦average visit interval≦+σ, the weight of the weighted average may be set to "1.0", if the visit interval is within the range of -2σ≦visit interval<-σ, or +σ<average visit interval≦+2σ, the weight of the weighted average may be set to "0.9", and if the visit interval is within the range of -3σ≦visit interval<-2σ, or +2σ<average visit interval≦+3σ, the weight of the weighted average may be set to "0.8". After finding the representative value of the visit interval for each customer in this way, this is used to calculate the average (or median, mode) of the representative values ​​of the visit intervals for all customers (hereinafter referred to as the "representative value of the visit interval for all customers").

[0193] The unified data management server 15 identifies new customers who have visited the store on that day (S64). For example, the unified data management server 15 extracts customer relationship information for the first visit date=the day from the customer relationship management DB 35, and identifies new customers who have visited the store on that day.

[0194] The data unified management server 15 estimates the next visit date as the date obtained by adding the representative value of the visit intervals of all customers to the first visit date of the new customer (S65). Alternatively, the data unified management server 15 may estimate the next visit date of each customer based on the average (or median, mode) of the visit frequency of all customers. For example, if the average visit frequency of a certain customer is 1 / 7, the data unified management server 15 may estimate the next visit date as the date obtained by adding the reciprocal of the average visit frequency (=7 days) to the first visit date of the customer.

[0195] The data unified management server 15 notifies new customers of the day of a message encouraging them to visit the store together with a coupon a predetermined period (e.g., the day before, two days before, etc.) before the estimated next visit date (S66). The notification is made using a contact method (chat app, phone number, email, SMS, etc.) registered in the customer relationship information.

[0196] 19 is an example of a configuration block diagram of a hardware environment of a computer that executes a program in this embodiment. The computer 151 may be a data unified management server 15, a Web server 11, a user terminal 17, a store terminal 16, or an external linkage server 12. The computer 151 is composed of a CPU 152, a ROM 153, a RAM 154, a storage device 155, an input I / F 156, an output I / F 157, a communication I / F 158, a reading device 159, and a bus 160.

[0197] Here, CPU refers to a central processing unit. ROM refers to a read-only memory. RAM refers to a random access memory. I / F refers to an interface. A CPU 152, a ROM 153, a RAM 154, a storage device 155, an input I / F 156, an output I / F 157, a communication I / F 158, and a reading device 159 as necessary may be connected to the bus 160.

[0198] The CPU 152 reads out the program according to this embodiment from the storage device 155, and when functioning as the data unified management server 15, for example, executes the program as the acquisition unit 22, the analysis and aggregation unit 23, and the display control unit 24. The ROM 153 is a read-only memory. The RAM 154 is a temporary storage memory.

[0199] The storage device 155 is a device that stores a large amount of information. As the storage device 155, various types of storage devices such as a hard disk, a solid state drive (SSD), a flash memory card, etc. The storage device 155 stores a program according to an embodiment of the present invention, a reservation management DB 32, an order management DB 33, a segment management DB 34, a customer relationship management DB 35, an analysis information DB 36, and various other data.

[0200] The input I / F 156 can be connected to input devices such as a keyboard, a mouse, an electronic camera, a web camera, a microphone, a scanner, a sensor, a tablet, a touch panel, an information reading device, etc. The output I / F 157 can be connected to output devices such as a display, a touch panel, a projector, a printer, a speaker, etc.

[0201] The communication I / F 158 is an interface such as a port for connecting to a communication network and communicating with other devices. The communication network may be the Internet, a local area network (LAN), a wide area network (WAN), a dedicated line, a wired line, a wireless line, etc. The reading device 159 is a device for reading a portable recording medium.

[0202] The program for realizing the process described in the above embodiment may be stored in, for example, the storage device 155 from the program provider via the communication network and the communication I / F 158. The program for realizing the process described in the above embodiment may be stored in a portable storage medium that is commercially available and distributed. In this case, the portable storage medium may be set in the reading device 159, and the program may be read and executed by the CPU 152. As the portable storage medium, various types of storage media such as CD-ROM, flexible disk, optical disk, magneto-optical disk, IC card, USB memory device, and semiconductor memory card can be used. The program stored in such a storage medium is read by the reading device 159.

[0203] Furthermore, the program may be installed on a stand-alone computer, or may be installed by a cloud computer and provide only its functions to the user.

[0204] According to this embodiment, even if a customer comes to the store without making a reservation, the customer can be individually identified and information on the customer's visit status can be easily obtained. Also, even if a new customer comes to the store without making a reservation, the customer can be individually identified and information on the new customer's visit status can be easily obtained.

[0205] In addition to customers who make reservations in advance, customers who come to the store without making a reservation can also be individually identified, and the store's visit status, order status, and income and expenditure status of customers who come to the store from various routes can be grasped in a unified manner.

[0206] In addition, customer identification information is registered each time a customer takes an action such as making a reservation or placing an order, so that the media from which the customer came can be tracked each time, making it easy to analyze the media from which the customer came.

[0207] In addition, the user's behavior (telephone reservation, web reservation, access to the media) with respect to the store's content for each medium (reservation screen, store advertisement, etc.) can be displayed in a centralized manner. This allows the user to visually grasp what kind of user behavior leads to store reservations for each medium. In addition, since it is possible to analyze the cost-effectiveness (for example, cost per action) of various user trends in each medium used in this way, it is possible to understand which media actually lead to reservations and spend money on such media more intensively as an investment strategy. In addition, it is possible to use external influence data to perform analysis and prediction based on diversifying user trends. When performing this analysis and prediction, for example, statistical methods and multivariate analysis may be used.

[0208] Although the present aspect has been described above based on the embodiment and modified examples, the above-mentioned embodiment of the aspect is intended to facilitate understanding of the present aspect and does not limit the present aspect. The present aspect may be modified or improved without departing from the spirit and scope of the claims, and equivalents are included in the present aspect. Furthermore, if a technical feature is not described as essential in this specification, it may be deleted as appropriate. [Explanation of symbols]

[0209] 1. Data unification device 2 Acquisition part 3 Analysis and tabulation section 4. Display control section 5 Storage section 11 Web Server 12 External Linkage Server 13 POS Linkage Server 14 Store management server 15 Data centralized management server 16 Store terminals 17 User terminal 18. Chat Apps 19. Communications Networks 21 Control section 22 Acquisition Department 23 Analysis and tabulation section 24 Display control section 31 Storage section 32 Reservation Management DB 33 Order Management DB 34 Segment Management DB 35 Customer Relationship Management DB 36 Analysis information DB 37 Accounting Information DB 41 External Information 42 Search Engine Analysis Information 43 Number of page views of various media data 44 Third Party Data 45 Company-specific data 46 Accounting Information 47 Store Management Information 48 Reservation Management Information 49 Order Management Information 51 Chat App Cart 52 Unique ID 53 WEB Cart 54 Telephone Number 55 Order App Cart 56 Device ID

Claims

1. An information processing system including a first server device and a second server device, the first server device has a storage unit that stores customer store order information that associates information regarding the customer's order or visit to a store, including first identification information transmitted from the first information communication terminal when a customer orders a product or service via the first information communication terminal, with second identification information that identifies the customer, and customer relationship information regarding a history of the customer store order information; The second server device is Acquire first customer order information including first identification information transmitted from an information communication terminal of the first customer; If the first identification information included in the acquired first customer store order information is not registered in the customer relationship information, a second identification information for identifying the first customer is issued; When the first identification information included in the acquired first customer store order information is registered in the customer relationship information, a second identification information corresponding to the first identification information is acquired from the customer relationship information; The first server device is registering the first customer store order information to which the issued or acquired second identification information has been added, into the customer store order information; based on the second identification information, associate the customer order information with the transaction information and register them in the customer relationship information; when a designated period is acquired from the second information communication terminal, the customer relationship information is compiled based on the designated period, and information regarding the customer's store visit status is displayed on the second information communication terminal based on the compiled customer relationship information; An information processing system comprising:

2. The first server device extracts customer relationship information relating to new customers during the specified period from the customer relationship information, and displays information relating to a store visit situation of the new customers based on the extracted customer relationship information.

2. The information processing system according to claim 1 .

3. The first server device calculates a representative value of a visit interval or a visit frequency of each customer from the customer relationship information, and estimates a next visit date of each customer based on the most recent visit date of each customer and the representative value of the visit interval or the visit frequency.

2. The information processing system according to claim 1 .

4. The first server device further A predetermined message is sent to each of the customers a predetermined period before the estimated next visit date.

4. The information processing system according to claim 3.

5. The first server device calculates a representative value of a visit interval or a visit frequency for all or some of the customers from the customer relationship information, and estimates a next visit date of the new customer based on a first visit date of the new customer and the representative value of the visit interval or the visit frequency.

3. The information processing system according to claim 2.

6. The first server device further A predetermined message is sent to the new customer a predetermined period before the estimated next visit date.

6. The information processing system according to claim 5.

7. The first server device further stores segment extraction condition information including search conditions for extracting a group of customers matching a predetermined search condition as segment information; When a target segment is specified from the second information communication terminal, the first server device extracts segment information corresponding to the target segment from the segment extraction condition information as target segment information, and displays on the second information communication terminal store operation status information including the number of reservations for the store and the behavior of the customers with respect to the media used when the customers visited the store, which are collected for each predetermined period, as well as the income and expenditure status of the store, the store visit status of the customers, and the order status of the customers, based on the target segment information.

2. The information processing system according to claim 1 .

8. When the first identification information is identification information generated based on communication application software installed in the first information communication terminal, the communication application software is communication application software for transmitting and receiving messages between users, in which a friend request is sent from the communication application software used by one user to the communication application software used by the other user, and the other user approves the friend request, thereby completing friend registration and enabling the users to transmit and receive messages, The first server device displays the number of customers who have established friend registration with the store.

2. The information processing system according to claim 1 .

9. The first server monitors the usage status of coupon information issued based on the first identification information, and issues a predetermined notification to the customer based on the usage status of the coupon information.

2. The information processing system according to claim 1 .

10. The first server device displays on the second information communication terminal the number of new customers, the customer's repeat visit rate, the cumulative sales amount, the average course price, the table operation rate, the ranking of popular courses, the frequency of the customer's use of the store, and the number of times the customer has used the store.

2. The information processing system according to claim 1 .

11. A program to be executed in an information processing system including a first server device and a second server device, The first server device, execute a process of storing in a storage unit customer store order information, which associates information regarding the customer's order or visit to a store, including first identification information transmitted from the first information communication terminal when a customer orders a product or service via the first information communication terminal, with second identification information that identifies the customer, and customer relationship information regarding a history of the customer store order information; The second server device, Acquire first customer order information including first identification information transmitted from an information communication terminal of the first customer; If the first identification information included in the acquired first customer store order information is not registered in the customer relationship information, a second identification information for identifying the first customer is issued; When the first identification information included in the acquired first customer store order information is registered in the customer relationship information, second identification information corresponding to the first identification information is acquired from the customer relationship information. Execute the process, The first server device, registering the first customer store order information to which the issued or acquired second identification information has been added, into the customer store order information; based on the second identification information, associate the customer order information with the transaction information and register them in the customer relationship information; when a designated period is acquired from the second information communication terminal, the customer relationship information is compiled based on the designated period, and information regarding a store visit status of the customer is displayed on the second information communication terminal based on the compiled customer relationship information. A program that executes a process.

12. An information processing method to be executed by an information processing system including a first server device and a second server device, The first server device, storing in a storage unit customer store order information that associates information regarding the customer's order or visit to a store, including first identification information transmitted from the first information communication terminal when a customer orders a product or service via the first information communication terminal, with second identification information that identifies the customer, and customer relationship information regarding a history of the customer store order information; The second server device, Acquire first customer order information including first identification information transmitted from an information communication terminal of the first customer; If the first identification information included in the acquired first customer store order information is not registered in the customer relationship information, a second identification information for identifying the first customer is issued; When the first identification information included in the acquired first customer store order information is registered in the customer relationship information, a second identification information corresponding to the first identification information is acquired from the customer relationship information; The first server device, registering the first customer store order information to which the issued or acquired second identification information has been added, into the customer store order information; based on the second identification information, associate the customer order information with the transaction information and register them in the customer relationship information; when a designated period is acquired from the second information communication terminal, the customer relationship information is compiled based on the designated period, and information regarding the customer's store visit status is displayed on the second information communication terminal based on the compiled customer relationship information; 23. An information processing method comprising:

Images