JP6153476B2 - Information processing apparatus and program - Google Patents

Description

  The present invention relates to an information processing apparatus and a program.

Conventionally, when a change occurs in the customer status (subscription period, purchase amount), a technology related to the PDCA cycle (see Patent Document 1 below) for conducting a campaign in accordance with the change, and a consumer segment classification (preference, purchase place) , Profiles, etc.) and vending machine segments (
There is a technique (see Patent Document 2 below) for calculating a correlation for each combination of location, sales by product, etc.) and planning a sales strategy.

JP 2001-243342 A JP 2012-003728 A

  However, the above prior art can only plan sales promotion strategies for sales objects.

  For example, a participant who participates in an event such as a performance first purchases a ticket for the performance, but the performance ticket purchaser does not purchase the ticket but aims to view the performance and go to the venue. become. In such a case, in addition to promoting performance tickets, the entertainment company wants to increase sales in the entire performance by promoting sales of food and drinks at the performance venue. It was difficult to predict and an appropriate sales strategy could not be formulated.

  An object of the present invention is to provide an information processing technique for analyzing purchase behavior of event participants and planning a sales strategy.

  In order to achieve the above-mentioned object, the present invention uses a past performance history and attribute information of a performance ticket purchaser, and a group of performance ticket purchasers using the attribute information of the performance and the attribute information of a store in the performance venue. It is possible to predict the purchase behavior of those segmented buyers in a specific performance and to establish an effective sales strategy.

According to one aspect of the present invention, at least one of member attribute information of a member, member event ticket purchase history information, product sales purchase history information at a member event venue, and visit history information of a member at an event venue is included. An information processing device for processing data in a database having behavior information, the information processing unit having a segment data creation unit for creating segment data, and the segment The data creation unit receives a plurality of member attribute designations, searches the member attribute information, creates a member list having the designated member attribute, and receives a plurality of behavior information designations. Then, referring to at least one of the event ticket purchase history information, the product sales purchase history information, and the visit history information, the member list A filtered member list creating unit that creates a filtered member list that is narrowed down based on the specified behavior information, and a filtered member list that is shared by the filtered member list based on the filtered member list created by the filtered member list creating unit A segment ID for uniquely identifying a segment having member attribute information and the behavior information; a segment name for identifying the member attribute information and the behavior information shared by the segment identified by the segment ID; A storage processing unit for performing processing for storing in the storage unit, segment information including segment information including the segment ID, and the segment ID and member ID included in the segment specified by the segment ID. An information processing apparatus characterized by having the information processing apparatus is provided.

  The database further includes event attribute information including an event schedule, the information processing unit includes a purchase prediction unit that performs purchase prediction based on the segment data, and the purchase prediction unit An expected number of visitors calculation unit, the expected number of visitors for each segment receives the designation of the date of the event, refers to the event attribute information of the event specified by the date of the event, and Search the segment information sharing the attribute information that matches the attribute information, determine as long as the segment ID of the segment information is matched, for each segment ID, obtain a member ID included in the segmentation target person information, Referring to event ticket purchase history information, the member ID has event attributes similar to those in the past. That is possible to identify the members who purchase a ticket for the event, and said that to predict the number of visitors to the specified event.

  The purchase forecasting unit includes a purchase trend calculation unit for each segment, and the purchase trend calculation unit for each segment obtains one segment ID of the segment group for which the expected number of visitors to be calculated is a purchase trend. Refer to the segment ID acquisition unit to be acquired, the member ID included in the acquired segment ID as a target ID while referring to the segmented target person information, and the product purchase history information And a segment-by-segment purchase trend prediction unit that obtains a purchase purchased by the member ID and obtains a purchase trend for each segment that does not depend on the member ID.

  It has a purchase prediction unit for each segment that predicts sales of purchased products at an event on a specified date based on the expected number of visitors for each segment and the purchase tendency for each segment.

  Furthermore, the process of repeating the prediction of the purchase prediction unit for each segment for each segment is performed.

  The present invention is characterized in that the recommended information on the purchased product is attached to the event ticket and transmitted by e-mail to the segmented person's terminal.

  According to another aspect of the present invention, at least one of the member attribute information of the member, the event ticket purchase history information of the member, the product sales purchase history information at the member event venue, and the visit history information of the member at the event venue. An information processing program for processing data in a database having event information including event schedules and event attribute information including an event schedule, and searching for the member attribute information in response to designation of a plurality of member attributes In response to the member list creation process for creating a member list having the designated member attribute, and a plurality of behavior information designations, the event ticket purchase history information, the product purchase history information, and the visit history information And creating at least one member list by narrowing down the member list by the specified action information. Based on the refined member list creation process to be performed and the refined member list created by the refined member list creation process, the segment having the member attribute information and the behavior information shared by the refined member group is uniquely identified. Specified by the segment ID, the segment information having the segment name for specifying the attribute information of the member and the behavior information shared by the segment specified by the segment ID, the segment ID, and the segment ID There is provided an information processing program for causing a computer to execute a storage process for storing a segmentation target person information including a member ID included in a segment to be stored in a storage unit.

  According to the present invention, it is possible to perform effective marketing analysis and the like for promoting sales to event participants at an event venue.

It is a figure which shows the structural example of the whole system containing an event management system as an example which performs the information processing by one embodiment of this invention. It is a block diagram which shows the mode of the process at the time of giving an identifier with respect to a performance ticket purchaser terminal etc. FIG. It is a block diagram which shows the mode of the process at the time of purchasing a performance ticket using an identifier with a performance ticket purchaser terminal. It is a block diagram which shows the mode of the process at the time of purchasing with the product sales management system outside a performance hall using an identifier with a performance ticket purchaser terminal. It is a block diagram which shows the mode of a process at the time of purchasing with the product sales management system in a performance hall using an identifier with a performance ticket purchaser terminal. It is a block diagram which shows the mode of a process at the time of the performance ticket purchaser's terminal etc. recording visit information to a performance hall using an identifier. It is a flowchart figure which shows the flow of a segment data creation process. It is a figure which shows the example of 1 structure of the member list narrowed down by action history and a member attribute. It is a flowchart figure which shows the flow of a purchase tendency prediction process. It is a flowchart figure which shows the flow of a process in the expected visit number calculation part for every segment. It is a flowchart figure which shows the flow of a calculation process of a sales tendency. It is a figure which shows the example of a data structure of the member attribute information table which manages the attribute information of a member produced | generated by the process shown in FIG. It is a figure which shows the example of the data structure (FIG.10 (c), FIG.10 (d)) which manages the attribute information (FIG.10 (b)) of a performance, and a consumer's action history. Management of attribute information (store information: FIG. 11 (b)) of stores and the like related to performances inside and outside the performance venue, and behavior history of goods (members) of members (consumers) acquired by the processing of FIG. It is a figure which shows the example of a data structure (product sales purchase history information: FIG.11 (c)). It is a figure which shows the example of 1 structure of segment information (FIG.12 (b)) and segmentation object information (FIG.12 (c)). It is a functional block diagram which shows one structural example of an analyzer. It is a functional block diagram which shows the example of 1 structure of a segment data preparation part. It is a functional block diagram which shows one structural example of a purchase prediction part. It is a functional block diagram which shows the detailed structural example of a visitor number calculation part for every segment. It is a functional block diagram which shows the detailed structural example of a segment purchase tendency calculation part.

  Hereinafter, an information processing technique according to an embodiment of the present invention will be described in detail with reference to the drawings.

  The information processing according to the present embodiment improves the sales of goods at the performance venue based on segmented consumer information, for example, when the organizer of events such as performances sells tickets via the Internet. The present invention relates to a technique for rotating a PDCA cycle for promoting the above.

  In the following, the event will be described by taking a performance as an example. However, the event is not limited to only a performance, but includes all forms of gathering people for a certain purpose, such as industry, carnival, and festival. In this specification, segmenting members (consumers) is referred to as segmentation.

  In the following, we will explain the case of membership registration for the system as an example, but consumers who are not registered using email address, name, nickname, etc. can also be used. is there. In addition, when the ID is presented by a member using a mobile terminal such as a smartphone by wired or wireless communication (including LAN, WAN, near field communication, etc.), the input to the terminal, All cases may be included, such as bar code input and presentation using a membership card or credit card. That is, the method for presenting the member ID or the like is arbitrary.

  FIG. 1 is a diagram illustrating a configuration example of the entire system including an event management system that manages events as an example of performing information processing according to an embodiment of the present invention.

  The system A shown in FIG. 1 includes an event management system 5 having a process for registering a member to purchase a performance ticket, and a client PC (member) 1 or a client portable terminal 2 used by the performance ticket purchaser. At least one of them is connected via the Internet 3a.

  The event management system 5 is connected to a client PC (administrator) 4 possessed by an administrator (entertainer) via the Internet 3b.

In addition, the event management system 5 includes, for example, a visit information registration terminal 15 for registering visit information for a performance such as a tablet-type terminal disposed in the performance hall, and a POS installed in, for example, a store in the performance hall. The system is connected to the in-venue sales management system 17 in the performance hall such as the system via the Internet 3a. Furthermore, the event management system 5 is also connected to the external sales management system 11 outside the performance venue via the Internet 3a.

  The network configuration is not limited to that shown in FIG. 1, and any connection medium such as a connection form or a wired / wireless / public line may be used. In addition, the inside of the performance hall includes the case where it is adjacent to the performance hall.

  The event management system 5 includes a member information management device (server) 5-1 for managing member information, a ticket sales management device (server) 5-2 for managing ticket sales, a visit information registration terminal 15, and sales in the venue. An external data linkage device (server) 5-3 for data linkage with the management system 17 or the external sales management system 11, a database 5-4 for storing various data described later, and information processing such as data analysis And an analysis device (server) 7 to be performed.

  The event management system 5 includes an information processing unit (CPU) that performs various information processing based on data in the database 5-4. The database 5-4 may be provided outside the event management system.

  The external data linkage apparatus (server) 5-3 performs processing for storing the attribute information and action history information of the performance ticket purchaser in this system, and stores the attribute information and action history information in the database 5-4. .

The analysis apparatus 7 in FIG. 1 is connected to the database 5-4 storing the attribute information and the action history information described above, and is connected via the Internet 3b. The analysis result is output for.

  FIG. 2 shows a process in which a performance ticket purchaser registers as a member in the event management system 5 via the Internet 3a using the client PC (member) 1 or client portable terminal (member) 2 and registers individual attribute information. Connected to the member information management apparatus (server) 5-1, registering the member's personal attribute information in the member attribute information DB 5-4a in the database 5-4 and identifying the individual from the event management system 5 It is the figure which showed a mode that ID information for this was provided.

  9 is a diagram showing an example of the data structure of a member attribute information table for managing member attribute information generated by the process shown in FIG. 2 (FIGS. 9A and 9B). The attribute information is registered by the cooperation process. The member attribute information table shown in FIG. 9B includes a member ID for uniquely identifying a member, for example, name, gender, date of birth, member type code (member type depending on the presence / absence of benefits), and membership. Member attribute information items such as date (member registration date) and residence (area).

  FIG. 3 shows that the performance ticket purchaser's client PC 1 or client portable terminal 2 purchases a performance ticket by connecting to the ticket sales management device (server) 5-2 using the ID information given by the processing of FIG. Then, it is the figure which showed a mode that the ticket sales management apparatus (server) 5-2 registers the purchase action log | history of the performance ticket into the ticket purchase log | history information database 5-4b.

  FIG. 4 shows an external sales management system 11 represented by an EC site on the Internet, which is performed by the client PC 1 or the client portable terminal 2 of the performance ticket purchaser using the ID information or the like given in FIG. It is the figure which showed a mode that the external data cooperation apparatus (server) 5-3 received and registered in the goods sales purchase history information database 5-4c.

  The external sales management system 11 manages the sale of goods at a fan club or the like of a certain idol group, for example, which has no relation to the performance itself or has little relation to the performance itself. As the member ID, a name, an e-mail address, or the like may be used. By this processing, for example, it is possible to obtain a tendency to purchase goods or the like of members of different regions including cases that do not depend on the attribute of the performance.

  FIG. 5 shows purchase history information acquired using the in-venue sales management system 17 using a POS system at a store in the performance hall via the external data linkage server 5-3 in the event management system 5. It is the figure which showed a mode that it registers in the product sales purchase history information database 5-4c. Basically, the purchase history of goods etc. by the terminal of the performance ticket purchaser who visited the performance venue is acquired and registered.

  The in-venue sales management system 17 manages, for example, sales of articles, pamphlets, goods, and the like in the performance hall, and includes a case where the performance does not depend on (or differs from) the operating entity of the performance.

  FIG. 6 shows that the performance ticket purchaser who visited the performance hall uses the ID information (member ID) assigned to the visit history information and performance information through the visit information registration terminal 15 as external data. It is the figure which showed a mode that it registers into visit history information and performance information database 5-4d via cooperation apparatus (server) 5-3. If the ticket is an electronic ticket, information on ticket presentation by the client portable terminal 2 may be acquired.

  FIG. 10 is a diagram illustrating an example of performance information (FIG. 10B) and a data structure (FIGS. 10C and 10D) for managing consumer behavior history. Performance ticket purchase history information obtained by performing the process shown in FIG. 3 (FIG. 10 (c)), visit history information obtained by performing the process shown in FIG. 6 (FIG. 10 (d)). have.

  In the performance attribute information shown in FIG. 10 (b), in addition to the performance ID for uniquely identifying the performance and the attribute information such as the performance date, venue ID, performer ID, etc., in the performance venue obtained from the weather forecast etc. It is desirable to include performance status information such as before start, during performance, and end of performance regarding climate information and performance of the performance date.

  As shown in FIG. 10C, the performance ticket purchase history information includes information such as a ticket purchaser ID, performance ID, ticket type (S seat, A seat, etc.), purchase price, purchase date and time.

  As shown in FIG. 10 (d), the performance visit information includes a performance ID, a visit date and time, and a visitor ID. In general, the purchaser ID matches the visitor ID, but may not match when resold in the middle.

  FIG. 11 shows the attribute information (store information: FIG. 11 (b)) of a store or the like related to the performance inside and outside the performance hall, and the external sales management system 11 or inside the hall acquired by the processing of FIGS. It is a figure which shows the example of the data structure (product sales purchase history information: FIG.11 (c)) which manages the action history, such as a member (consumer) goods, etc. by the sales management system 17. FIG.

  As shown in FIG. 11B, the store information includes, for example, a store code (or store ID), a store type that identifies the type of store, a store type such as a fixed store or a mobile store, and a venue ID. And a position code and a category code.

  The venue ID is the ID of the performance venue, the position code is the location in the area where the performance venue is located, and the category code is the goods sold such as the sale of goods, the sale of food and drinks, etc. However, other distinctions, for example, distinctions depending on store names, brand names, etc., may be used. In the case where there is no position code (none), for example, the store type is a mobile store, and the salesperson visits the performance venue and sells ice cream or the like, or so-called mobile sales, or the like. It indicates that the item is an article or the like purchased by the process indicated by.

  The product sales purchase history information shown in FIG. 11C includes a purchaser ID, a performance ID, a purchase store code, a purchase product code, a purchase date and time, and the like. The performance ID “none” may indicate a purchase form as shown in FIG. The purchased product code indicates, for example, goods such as idol A.

  In the following, based on the information obtained as described above, a configuration for creating segment data for planning a sales strategy and an example of information processing therefor, and then planning a sales strategy using it. A configuration for making a purchase forecast by performing data analysis and an information processing example therefor will be described.

  FIG. 13 is a functional block diagram showing a configuration example of the analysis apparatus (server) 7 in FIG. The analysis device 7 includes a segment data creation unit 7-1 that creates segment data, and a purchase prediction unit 7-2 that performs purchase prediction based on the segment data.

FIG. 14 is a functional block diagram illustrating a configuration example of the segment data creation unit 7-1. FIG. 7A is a flowchart showing the flow of segment data creation processing. FIG. 12 is a diagram illustrating a data configuration example of segment information and segmentation target person information. As appropriate
Reference is also made to the data configuration examples of FIGS.

  As shown in FIG. 14, the segment data creation unit 7-1 includes a member attribute reception unit 7-1-1, a designated member attribute holding / member list acquisition (creation) unit 7-1-2, and a behavior information reception unit. 7-1-3, history information reference unit 7-1-4, narrowed member list acquisition (creation) unit 7-1-5, segment information / segmentation target information recording processing unit 7-1-6, Have

  First, in FIG. 7A, when the process is started (Start), in step S1, the member attribute receiving unit 7-1-1 specifies, for example, a plurality of items of segment narrowing conditions (member attributes) from the client terminals 1 and 2 In step S2, the designated member attribute holding / member list acquisition (creation) unit 7-1-2 refers to the member attribute information (table) shown in FIG. 9 and acquires a list of the corresponding members. For example, if the segment narrowing conditions are “male”, “Tokyo”, and “age is 30's”, only a list of members that match the three conditions is included as shown in FIG. 9C. Member list is created (narrowed down).

  Next, in step S3, when the behavior information receiving unit 7-1-3 receives designation of a plurality of items for segment narrowing conditions (behavior information), in step S4, the history information reference unit 7-1-4 performs a performance ticket. Refer to at least one of the purchase history information (FIG. 10 (c)), the performance visit information (FIG. 10 (d)), and the product sales purchase history information (FIG. 11 (c)) (information corresponding to acceptance), In step S5, the narrowed-down member list acquisition (creation) unit 7-1-5 creates a narrowed-down member list and displays it on the screen, for example.

Here, if the narrowing-down conditions in step S3 are, for example, performer ID = 100 (FIG. 10B) and purchased product code “1” (FIG. 11C), the first line of FIG. You can create a narrow list of members as shown in.

  Here, in step S6, the segment information storage process in step S5 is selected. In step S7, when an input of a segment name and an outline is accepted, in step S8, the segment information / segmentation target information recording processing unit 7-1- 6 records the narrowed list of members in the segment information and segmentation target person information, and ends the processing (End).

  FIG. 12 is a diagram illustrating a configuration example of segment information and segmentation target person information. The segment information shown in FIG. 12B includes a segment ID that uniquely identifies the segment, a segment name that represents the characteristics of the segment, a creation date and time, and an overview. The segment information shown in FIG. The conversion target person information has a segment ID, a target person ID that is an ID of a member included in the segment, and an addition date when the target person is added to the segment ID.

  If necessary, specify multiple attribute information common to the target member group to be segmented, narrow down the member group, use the member attribute information table, create a list of members with the specified attribute information, necessary Any desired segment can be created by specifying a plurality of action history information common to the target member group to be segmented in accordance with and narrowing down the member group. The segment information includes a segment name that specifies attribute information shared by the segment specified by the segment ID, or may be associated with a table of attribute information as described below.

More specifically, as shown in FIG. 7B, for example, the segment identified by the segment ID = 1 is a performer ID = 100 based on performance ticket purchase history information, a 30's based on member attribute information, a male, Tokyo, a group that matches the narrowing-down conditions of purchasers with purchase item code “1” based on product sales history information. Generalizing this, as shown in FIG.
Segment information is segmented into XXXX group that is a fan of XXXX and YYYY group that likes YYYY, etc., and the ID of the target member is specified for each segment ID by segmentation target person information Can do.

  As described above, based on the narrowed member list created by the narrowed member list acquisition unit 7-1-5, the segment having the member attribute information and the behavior information shared by the narrowed member group is uniquely identified. Segment information having a segment ID, a segment name for identifying the member attribute information and the behavior information shared by the segment identified by the segment ID, a segment ID, and a segment identified by the segment ID Segment information / segmentation target information recording processing unit 7-1-6 stores the segmentation target person information including the included member ID in the storage unit.

  In the segment information shown in FIG. 12 (b), by describing data indicating the characteristics of the segment (representative attribute name, etc.) such as “XXXX fan” in the summary column, what kind of characteristics the segment has. You can know at a glance whether it is a segment you have.

  The segment information and segmentation target person information shown in FIG. 12 are updated by the segment information creation process shown in FIG. 7A.

  Next, the configuration and processing contents of the purchase prediction unit 7-2 that performs purchase prediction for sales strategy planning based on the segment information will be described.

  FIG. 15 is a functional block diagram illustrating a configuration example of the purchase prediction unit 7-2. The purchase forecasting unit 7-2 includes an event date / time designation receiving unit 7-2-1, an expected visit number calculation unit 7-2-2 for each segment, a purchase trend calculation unit 7-2-3 for each segment, and an estimated sales amount. It has a calculation unit 7-2-4 and a segment-by-segment purchase prediction unit 7-2-5.

  FIG. 8A is a flowchart showing a flow of purchase prediction processing by the purchase prediction unit 7-2. First, when the process is started (Start), in step S11, when the event date / time designation receiving unit 7-2-1 receives designation of a performance date such as an event from the client terminals 1 and 2, for example, in step S12, The predicted number of visitors per segment 7-2-2 calculates the expected number of visitors for each segment using the attribute information of the performance date.

  FIG. 16 is a functional block diagram illustrating a detailed configuration example of the predicted number of visitors per segment 7-2-2. Expected number of visitors per segment 7-2-2 includes a segment ID acquisition unit 7-a, a segment ID acquisition unit 7-b, a performance information history reference unit 7-c, and a ticket purchase number calculation unit 7 -D and a designated event (performance) date and time predicted visitor number estimation unit 7-e.

  FIG. 8B is a flowchart showing the flow of processing in the predicted number of visitors per segment 7-2-2. In step S12, first, in step S12-1, the segment ID acquisition unit 7-a obtains the performance attribute information obtained by referring to the performance attribute information of FIG. 10B according to the performance date specified in step S11. Based on this, as long as the segment IDs of the segment information in FIG.

  For each segment ID acquired in step S12-1, in step S12-2, the segment-by-segment member ID acquisition unit 7-b includes the target person included in the segment based on the segmentation target person information in FIG. Search for an ID. In step S12-3, the performance information history reference unit 7-c refers to the performance ticket purchase history information (FIG. 10C), and the ticket purchase number calculation unit 7-d identifies the person who purchased the ticket in the past. The number of past ticket purchasers is calculated. In step S12-4, the designated event (performance) date / time predicted visitor number estimation unit 7-e is based on the past ticket purchase history and performance visit information (FIG. 10D) obtained in step S12-3. The number of visitors (predicted value) for each segment on the performance date designated in step S11 is estimated. For example, for segment ID = 1, the expected number of visitors is 100, ID = 2 is 10, and ID = 3 is 300.

  Next, if the expected number of visitors is output to the screen in step S13, the expected number of visitors can be known for each segment. Steps S14 and S15 are repeated for the created segment. In step S <b> 14, the segment-by-segment purchase tendency calculation unit 7-2-3 calculates a purchase tendency for the segment by using the product sales purchase history information of the members in the segment for the saved segment. FIG. 17 is a functional block diagram illustrating a configuration example of the segment-specific purchase tendency calculation unit 7-2-3. The segment-by-segment purchase trend calculation unit 7-2-3 includes a segment ID acquisition unit 7-f, a segment-by-segment member ID acquisition unit 7-g, a product sales purchase history reference unit 7-h, and a segment-by-segment purchase trend prediction unit 7 -I. FIG. 8C is a flowchart showing the flow of processing.

  First, in step S14-1, the segment ID obtaining unit 7-f obtains one segment ID from the segment group for which the expected number of visitors is obtained in step S12, which is a target for calculating the purchase tendency, and then the segment Each member ID acquisition part 7-g calculates | requires member ID contained in segment ID acquired by step S14-1 as object person ID, referring segmentation object person information (FIG.12 (c)).

  Next, in step S14-2, the product sales purchase history reference unit 7-h refers to the product sales purchase history information (FIG. 11C) and obtains a purchased product (for example, a purchased product code). Next, in step S14-3, the segment-by-segment purchase trend prediction unit 7-i obtains a purchase trend for each segment that does not depend on the member ID.

  With the above processing, for example, the purchase tendency in the segment ID = 1 can be predicted to be 10 products with the product code 1 and 3 products with the product code 2. If the number of members at this time is determined to be 50, for example, based on the member ID, the number of purchases of the product code 1 per person is 10/50 = 1/5.

  Next, in step S15, the segment purchase prediction unit 7-2-5 estimates the number of visits for each segment obtained in step S12 and the purchase trend for each segment obtained in step S14 (the number of purchase predictions for each product etc.). ) And the sales forecast on the designated performance date is calculated by the number (number), amount, etc. For example, in segment ID = 1, if the expected number of visitors is 100 and the purchase tendency of the product “1” is 1/5, the sales forecast for the product “1” in the segment ID = 1 is 20. This may be output to the screen.

  By repeating the above processing for each segment, it is possible to predict the number of products sold on the designated performance date and the sales amount obtained by multiplying the unit price by that, which can be useful when planning a sales strategy.

  As described above, the analysis device 7 calculates the purchase tendency for the segment using the product sales history information of the members in the segment for the stored segment, and uses the purchase tendency and the expected number of visitors for each segment. Thus, the sales forecast amount for each segment can be calculated and output on the screen.

When the person in charge of data analysis designates the seat position for confirming the details in order to confirm the purchasing tendency in the performance hall (step S16), in step S17, the analyzer 7
It is possible to output each segment's expected visits and products to be purchased on the screen at stores in the venue (including the case where the sales management system 17 in the venue is held). After confirming the output information, sales at the performance Strategies can be formulated for each store.

  In addition, the recommended information on purchased products can be attached to a performance ticket and transmitted by e-mail to the target terminal for each segment.

  As described above, according to the present embodiment, an event owner who sells an event ticket divides visitors to the event venue into various segments in order to improve sales at the event venue. The behavior of the event ticket purchaser can be predicted, and effective marketing analysis and the like for performing sales promotion at the event venue of the event participant can be performed.

  In this specification, processing and control are performed by CPU (Central Processing Unit) or GPU (Graphics Processing Unit) software processing, ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Hardware processing). Can do.

  In the above-described embodiment, the configuration and the like illustrated in the accompanying drawings are not limited to these, and can be changed as appropriate within the scope of the effects of the present invention. In addition, various modifications can be made without departing from the scope of the object of the present invention.

  Each component of the present invention can be arbitrarily selected, and an invention having a selected configuration is also included in the present invention.

  In addition, a program for realizing the functions described in the present embodiment is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed to execute processing of each unit. May be performed. The “computer system” here includes an OS and hardware such as peripheral devices.

A ... system, 1 ... client PC (member), 2 ... client portable terminal, 3a, 3b ... internet, 4 ... client PC (administrator), 5 ... event management system, 5-1 ... member information management device (server) 5-2 ... Ticket sales management device (server), 3-3 ... External data linkage device (server), 5-4 ... Database, 7 ... Analysis device, 11 ... External sales management system, 15 ... Visit information registration terminal, 17 ... Sales management system in the venue.

Claims (7)

Member attribute information of members,
Behavior information including at least one of member event ticket purchase history information, product sales purchase history information at member event venue, and visit history information of member event venue;
An information processing apparatus having an information processing unit for processing data in a database having
The information processing unit includes a segment data creation unit that creates segment data;
The segment data creation unit
A member list creation unit that receives designation of a plurality of member attributes, searches the member attribute information, and creates a member list having the designated member attributes;
In response to the designation of a plurality of behavior information, the member list is designated by referring to at least one of the event ticket purchase history information, the product sales purchase history information, and the visit history information. A refined member list creation unit that creates a refined member list narrowed down by behavior information,
Based on the narrowed-down member list created by the narrowed-down member list creation unit, a segment ID that uniquely identifies a segment having the member attribute information and the behavior information shared by the narrowed-down members, and the segment ID Segment information having a segment name for identifying the attribute information of the member and the behavior information shared by the segment identified by, the segment ID, and the member included in the segment identified by the segment ID An information processing apparatus comprising: a storage processing unit that performs a process of storing segmentation target person information including an ID in a storage unit. The database further includes event attribute information including a schedule of events,
The information processing unit
Having a purchase forecasting unit for making a purchase forecast based on the segment data;
The purchase forecasting unit has a predicted number of visitors per segment,
The predicted number of visitors per segment is
In response to the designation of the event date, refer to the event attribute information of the event specified by the event date, and search for the segment information sharing the attribute information matching the attribute information of the event,
As long as the segment ID of the segment information is matched, the member ID included in the segmentation target person information is obtained for each segment ID, the event ticket purchase history information is referred to, the past from the member ID The information processing apparatus according to claim 1, wherein the number of visitors to the designated event is predicted by identifying a member who purchased a performance ticket having an event attribute similar to. The purchase forecasting unit has a purchase trend calculation unit for each segment,
The segment purchase tendency calculation unit
A segment ID acquisition unit that acquires one segment ID of the segment group for which the expected number of visitors to be calculated is a purchase tendency;
A member ID acquisition unit for each segment that obtains a member ID included in the acquired segment ID as a target person ID while referring to segmented target person information;
A purchase trend prediction unit for each segment that obtains a purchase purchased by the member ID with reference to the product purchase history information and obtains a trend of the purchase for each segment that does not depend on the member ID. The information processing apparatus according to claim 2. 4. A segment-by-segment purchase prediction unit that predicts sales of purchased items at an event on a specified date based on an expected number of visitors for each segment and a purchase tendency for each segment. The information processing apparatus described in 1.   The information processing apparatus according to claim 4, further comprising a process of repeating the prediction of the purchase prediction unit for each segment for each segment.   The information processing apparatus according to any one of claims 1 to 5, wherein the recommended information on the purchased product is attached to the event target person's terminal and transmitted by e-mail. Member attribute information of members,
Behavior information including at least one of the member's event ticket purchase history information, the member's event sales history information, and the member's event history information,
An information processing program for processing data in a database having
A member list creation process for receiving a plurality of member attribute designations, searching the member attribute information, and creating a member list having the designated member attributes;
In response to the designation of a plurality of behavior information, the member list is designated by referring to at least one of the event ticket purchase history information, the product sales purchase history information, and the visit history information. A refined member list creation process for creating a refined member list narrowed down by action information,
Based on the narrowed-down member list created by the narrowed-down member list creation process, a segment ID that uniquely identifies the segment having the member attribute information and the behavior information shared by the narrowed-down members, and the segment ID Segment information having a segment name for identifying the attribute information of the member and the behavior information shared by the segment identified by, the segment ID, and the member included in the segment identified by the segment ID An information processing program for causing a computer to execute a storage process for storing a segmentation target person information including an ID in a storage unit.

Images