JP5782171B2 - Application management method, application management server, and application management program - Google Patents

Description

  The present invention relates to an application management method, an application management server, and an application management program for guiding a user of a specific application to another application.

  In recent years, various games have been provided via networks. Some of these games are social games offered on a social networking service (SNS).

  And in such a game, the technique for preventing the fall of a user's willingness to continue a game is also examined (for example, refer patent document 1). The server device described in this document advances a game while communicating with a terminal. When a first event occurs during the progress of the game, the parameter value of the game target is decreased, corresponding first display data is created, and the number of occurrences of the first event is counted. The winning probability of the second event occurrence is set based on the number of occurrences of the first event and the parameter value, and the presence or absence of the second event is determined based on the lottery according to the winning probability. When the occurrence of the second event is determined, the parameter value is decreased, corresponding second display data is created, and the first display data and the second display data are transmitted to the terminal.

  Also, a technique for enabling access to related sites related to objects in a game has been studied (for example, see Patent Document 2). The online game server described in this document displays an object selectably on a game display screen of an online game played on a player terminal. When this object is selected, game progress information necessary for the progress of this online game is included, and related site designation information for accessing the related site of the object is transmitted to the player terminal. Then, the player terminal accesses the related site and displays the advertisement site screen of the object on the display screen of the display device.

  Further, in the promotion activities of products and services, there are cases where cross promotion is performed to provide products and services of other companies as rewards for good customers.

JP2013-128781A (first page, FIG. 1) JP 2008-295775 A (first page, FIG. 1)

  Many applications are provided even on the Internet, but these applications may be managed independently. For example, when the provider (provider) of each application is different, it is impossible to grasp the status of the application managed by another provider.

  Further, when sending customers to other applications in the cross promotion, it is necessary to consider activation in the application of the customer. That is, when only the customer destination application is activated, it is not possible to activate the customer activity.

  The present invention has been made in view of the above-described problems, and an object thereof is an application management method, an application management server, and an application management for efficiently guiding a user of a specific application to another application. To provide a program.

(1) An application management method for solving the above problem manages a plurality of applications using a storage unit and a control unit connected to a user terminal via a network. The storage unit stores information associating a customer source and a customer destination application and achievement status information of at least one mission in association with a user ID of a participating user. When the control unit detects selection of a customer application stored in the storage unit in the user terminal, the control unit outputs a link capable of transitioning to a customer application associated with the customer source, When the link is selected, as a participating user, the user terminal is transitioned to the customer destination application, and mission achievement status information in the customer destination application associated with the user ID of the participant user If the predetermined condition is satisfied, the incentive provided by the customer source application is given to the participating user in the customer source application.
(2) An application management method that solves the above problem manages a plurality of applications using a storage unit and a control unit connected to a user terminal via a network. The storage unit stores a user ID of a participating user and at least one mission achievement status information for a plurality of applications including at least one application managed by an independent application provider, Among the applications, an application serving as a customer sending source and an application serving as a customer sending destination managed by a separate and independent application provider different from the application provider of the application serving as the customer sending source are stored. When the control unit detects selection of a customer application stored in the storage unit in the user terminal, the control unit outputs a link capable of transitioning to a customer application associated with the customer source, When the link is selected, as a participating user, the user terminal is transitioned to the customer destination application, and mission achievement status information in the customer destination application associated with the user ID of the participant user If the predetermined condition is satisfied, the incentive provided by the customer source application is given to the participating user in the customer source application.
As a result, the customer application can be guided to the customer application, and the incentive can prompt the use of the customer application until the predetermined condition is achieved. Then, the customer destination application can be activated and a return to the customer source application can be promoted.

  (3) In the application management method, a game to be used is registered in the storage unit in association with the user ID. When the control unit detects selection of a customer application from the user terminal, whether or not the customer application is registered for use with the user ID acquired from the user terminal in the storage unit. It is preferable to check the usage status of the customer and output the link when the application at the customer's destination is not used. As a result, if the customer application is already used and the customer effect cannot be expected, the customer can be suppressed.

  (4) In the application management method, when the link is selected, the control unit stores the user ID as a participating user in the storage unit, and from the customer application, the storage unit It is preferable to acquire the achievement status of the user IDs of the participating users registered in. Thereby, an incentive can be provided according to the achievement status information of only the participating users who have selected the link.

  (5) In the application management method, when the control unit stores a user group in which user IDs of a plurality of participating users are associated with each other in the storage unit, and the achievement status information satisfies a predetermined condition, the control unit further determines In the storage unit, it is determined whether the user ID of the user who satisfies the conditions is a group user of the user group. When the user ID is determined to be a group user, the achievement status information is given to all users belonging to the user group. It is preferable to store in the storage unit. Thereby, the customer sending of a plurality of users can be promoted.

  ADVANTAGE OF THE INVENTION According to this invention, the user of a specific application can be guide | induced efficiently with respect to another application.

The system schematic of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. It is explanatory drawing of the example of a screen of this embodiment, (a) is a campaign display in a customer's origin application screen, (b) is a game in a customer's destination application screen, (c) is mission achievement in a customer's destination application screen. (D) is a mission confirmation on the customer application screen, (e) is an explanatory diagram of incentive acquisition on the customer application screen. Explanatory drawing of the process sequence of this embodiment. It is explanatory drawing of the process sequence of other embodiment, Comprising: (a) is a group registration process, (b) is explanatory drawing of a mission achievement management process. Explanatory drawing of the process sequence of other embodiment.

  Hereinafter, an embodiment of an application management method will be described with reference to FIGS. This embodiment assumes the case where a cross promotion is performed with respect to the user who uses a some application (for example, game).

As shown in FIG. 1, in this embodiment, a user terminal 10, a management server 20, and a plurality of game servers 30 connected via a network such as the Internet are used.
The user terminal 10 is a user's registered computer terminal (information processing terminal such as a smartphone). This user terminal 10 is used when participating in a game provided from the game server 30. Moreover, it is used also when managing a local calendar in the user terminal 10 or participating in various SNSs (social network services). In this embodiment, the case where the applications A and B about a game are utilized for the user terminal 10 is assumed.

  The management server 20 is a computer system that manages users who use a plurality of applications for the user terminal 10. Specifically, the management server 20 functions as a platform system (platform) that manages users and manages game services provided from various game servers 30. The management server 20 includes a control unit 21 including a CPU, a RAM, a ROM, and the like, a user information storage unit 22, a campaign information storage unit 23, a participation situation information storage unit 24, and an achievement situation information storage unit 25.

The control unit 21 functions as a user management unit 211, a campaign management unit 212, a redirector 213, and a mission management unit 214 by executing a management program.
The user management unit 211 executes processing for managing users who use various applications.

The campaign management unit 212 executes processing for managing a campaign for cross promotion.
The redirector 213 executes processing for reconnecting (redirecting) the user terminal 10 connected to the game server 30 that provides the customer application to the game server 30 that provides the customer application.
The mission management unit 214 executes a process for managing the achievement status of the mission in the game.

  The user information storage unit 22 records user management information for authenticating the user and managing the game used by the user. This user management information is recorded when a user is registered on the platform, and is updated when a use registration of the game is performed. In the user management information, a user ID, a login password, and data relating to the game used are recorded.

In the user ID data area, data relating to an identifier for specifying each user is recorded.
In the login password data area, data for authenticating the user when the user logs in to the management server 20 is recorded.
In the use game data area, data relating to an identifier (game ID) for specifying a game used by the user is recorded.

  The campaign information storage unit 23 stores campaign management information for managing a campaign for cross promotion and mission management information regarding achievement conditions according to the mission. Campaign management information and mission management information are registered when cross promotion is executed.

In this campaign management information, data on a campaign ID, a customer source, a customer destination, a mission, an incentive, and a campaign period are recorded.
In the campaign ID data area, data relating to an identifier for specifying each campaign for cross promotion is recorded. Here, a campaign is assumed in which a customer is sent from a predetermined customer (for example, application A) to a predetermined customer (for example, application B).

In the customer source data area, data relating to an identifier (game ID) for specifying an application as a customer source in this campaign is recorded.
In the customer data area, data relating to an identifier (game ID) for specifying an application serving as a customer in this campaign is recorded.

  In the mission data area, data relating to an identifier (mission ID) for specifying a mission (mission) to be achieved by the user in order to acquire an incentive is recorded.

In the incentive data area, data related to a privilege (incentive) provided to a user who has achieved the mission is recorded.
In the campaign period data area, data related to the campaign period is recorded.

In the mission management information, data relating to the mission ID, mission content, and achievement conditions is recorded.
In the mission ID data area, data relating to an identifier for identifying each mission is recorded.

  In the mission content data area, data relating to the content of this mission is recorded. In the present embodiment, the mission includes “installation”, “login for a predetermined period (for example, two days)”, “invite friends”, “clear a predetermined stage”, and the like.

  In the achievement condition data area, data relating to conditions for achieving the mission is recorded. The achievement conditions include “can be achieved only once”, “can be achieved up to the number of times within a predetermined period (for example, one day)”, “can be achieved without any number of times”, and the like.

  Participation status management information for managing the participation status of each user in the campaign is recorded in the participation status information storage unit 24. This participation status management information is recorded when the user wishes to participate in the campaign. In this participation status information, data relating to the user ID and the campaign ID is recorded.

In the user ID data area, data relating to an identifier for identifying a user who wishes to participate in the campaign is recorded.
In the campaign ID data area, data relating to an identifier for identifying a campaign that the user desires to participate is recorded.

  The achievement status information storage unit 25 records achievement status management information for managing the mission achievement status of each user. This achievement status management information is registered when the mission progress status is acquired from the game server 30 that manages each application. In this achievement status management information, data relating to a user ID, a campaign ID, and a mission ID are recorded.

In the user ID data area, data relating to an identifier for identifying a user participating in the campaign is recorded.
In the campaign ID data area, data relating to an identifier for specifying a campaign in which the user participates is recorded.
In the mission ID data area, data relating to an identifier for identifying a mission achieved by the user in this campaign is recorded.

  The game server 30 is a server computer that provides various applications (here, games) on the Internet. In the present embodiment, the game server 30 is managed by a separate and independent application provider, and provides an application (game) to each user terminal 10. Furthermore, in a plurality of games, cross-promotion planning and management for promoting the use of other games is performed.

The game server 30 includes a promotion information storage unit 32 for managing cross promotions for users.
In the promotion information storage unit 32, promotion management information about missions and incentives provided in the cross promotion is recorded. This promotion management information is registered when the application provider decides to execute cross promotion. In the promotion management information, data on a campaign ID, a mission ID, mission contents, achievement conditions, and incentives are recorded.

In the campaign ID data area, data relating to an identifier for specifying a campaign related to the game server 30 is recorded.
In the mission ID data area, data relating to an identifier for identifying a mission to be achieved in order for the user to obtain an incentive at the customer destination is recorded.
In the mission content data area, data relating to the content of this mission is recorded.

In the achievement condition data area, data relating to conditions for accomplishing the mission at the customer is recorded.
In the incentive data area, data relating to a privilege (incentive) provided to the user who has achieved the mission at the customer source is recorded.

Hereinafter, each process in the application management method will be described with reference to FIGS.
(Application management process)
Next, application management processing will be described with reference to FIG.
Here, first, the user terminal 10 executes a login process (step S1-1). Specifically, when playing a game, the management server 20 is accessed using the user terminal 10. In this case, the user management unit 211 of the control unit 21 of the management server 20 outputs a login screen on the display of the user terminal 10. And a user inputs user ID and a login password in this login screen.

  Next, the control part 21 of the management server 20 performs a user authentication process (step S1-2). Specifically, the user management unit 211 of the control unit 21 acquires the user ID and login password input on the login screen of the user terminal 10. Then, when the user ID and login password acquired from the user terminal 10 are registered in the user information storage unit 22, the user management unit 211 completes login authentication. When the login authentication is completed, the user ID of the login user is specified.

  Next, the user terminal 10 executes application selection processing (step S1-3). Specifically, the user terminal 10 outputs a selection screen in which a list of games used by the logged-in user is displayed on the display. Here, it is assumed that application A is selected as a game. In this case, the user terminal 10 transmits the selected application selection information to the management server 20. This application selection information includes data related to the game ID.

  Next, the control part 21 of the management server 20 performs the determination process about whether it has campaign participation qualification (step S1-4). Specifically, the campaign management unit 212 of the control unit 21 uses the campaign information storage unit 23 to check whether there is campaign management information in which the game ID of the application selection information is recorded in the customer source data area. To do. Here, campaign management information in which the current date and time is included in the campaign period is used. As a result, it is determined whether or not the selected game is a target of a campaign customer. When there is campaign management information in which the game ID is recorded in the customer source data area, it is determined that the target is the customer source.

  When it is determined that the selected game is a target of the customer source application, the campaign management unit 212 identifies the game ID recorded in the customer destination data area of this campaign management information. Next, the campaign management unit 212 confirms whether or not the game ID of the customer destination application is registered as a use game in the user management information of the login user in the user information storage unit 22. Thereby, it is determined whether or not the login user is using the customer destination application.

  In the user management information, when the game ID of the customer destination application is registered as a use game and the customer destination application is used, it is determined that there is no eligibility to participate in the campaign. On the other hand, if it is not registered as a game to be used and the customer destination application is not used, it is determined that there is a campaign participation qualification.

  When it is determined that there is no campaign participation qualification (“NO” in step S1-4), the control unit 21 of the management server 20 executes a login notification process (step S1-5). Specifically, the user management unit 211 of the control unit 21 notifies the game server 30 of the application A of login.

  In this case, the game server 30 of the application A executes a game screen providing process (step S1-6). Specifically, the game server 30 of the application A transmits a game screen to the display of the user terminal 10.

  And the user terminal 10 performs a game screen display process (step S1-7). Specifically, the user terminal 10 outputs the game screen of the application A on the display. And when a user plays a game using a game screen, the game server 30 of the application A performs the game progress management process with respect to a login user (step S1-8).

  On the other hand, if it is determined that there is a campaign participation qualification (in the case of “YES” in step S1-4), the control unit 21 of the management server 20 executes a campaign notification process (step S1-9). Specifically, the campaign management unit 212 of the control unit 21 transmits a campaign target notification to the game server 30 of the application A. This campaign target notification includes data relating to the campaign ID recorded in the campaign management information in the campaign information storage unit 23.

  In this case, the game server 30 of the application A executes a campaign banner generation process (step S1-10). Specifically, the game server 30 of the application A extracts promotion management information in which the campaign ID included in the campaign target notification is recorded from the promotion information storage unit 32. Then, the game server 30 generates a campaign banner including the information recorded in the promotion management information. This campaign banner includes a link to the management server 20 and data relating to the campaign ID.

  Next, the user terminal 10 performs a game screen display process with a banner (step S1-11). Specifically, the game server 30 of the application A transmits a game screen including a campaign banner to the user terminal 10. Then, the user terminal 10 outputs a game screen including a campaign banner on the display.

In this case, as shown in FIG. 4A, a customer source application screen 500 is output on the display of the user terminal 10. The customer application screen 500 includes a campaign summary display 501, a mission explanation display 502, and a campaign banner 503 as an advertisement link. The campaign summary display 501 includes a description of the main point of the campaign. The mission explanation display 502 includes a mission achievement method and achievement conditions. This campaign banner 503 includes data relating to a link to the management server 20 and a campaign ID.
Here, when the user plays a game using the game screen, the game server 30 of the application A performs a game progress management process for the login user (step S1-8).

  On the other hand, when using a campaign, a campaign banner displayed on the display of the user terminal 10 is selected. In this case, the user terminal 10 performs a banner selection process (step S1-12). Specifically, the user terminal 10 transmits a campaign selection notification to the management server 20. This campaign selection notification includes data related to the campaign ID.

  Next, the control unit 21 of the management server 20 executes a destination information transmission process (step S1-13). Specifically, the redirector 213 of the control unit 21 includes a redirect URL for accessing the application B for the user terminal 10.

  Furthermore, the control part 21 of the management server 20 performs a campaign participation registration process (step S1-14). Specifically, the campaign management unit 212 of the control unit 21 generates participation situation management information in which the user ID of the login user and the campaign ID are associated with each other, and records them in the participation situation information storage unit 24. If the participation status management information in which the user ID and the campaign ID are associated is already recorded in the participation status information storage unit 24, this process is skipped.

  Next, the user terminal 10 performs a redirect process (step S1-15). Specifically, the user terminal 10 uses the redirect URL acquired from the management server 20 to access the game server 30 of the application B that is a customer destination.

  In this case, as shown in FIG. 4B, a customer destination application screen 510 is output on the display of the user terminal 10. The customer destination application screen 510 includes a game screen 511 of application B, which is a customer destination.

Next, the case where the game of the application B which is a customer destination is played is demonstrated using FIG.
Here, the user terminal 10 performs a game use process (step S2-1). Specifically, the user terminal 10 plays a game using the game screen of the application B output on the display.

  In this case, the game server 30 of the application B executes a game progress management process (step S2-2). Specifically, the game server 30 of the application B manages the progress of the game on the user terminal 10.

  Next, the game server 30 of the application B executes a determination process as to whether or not the mission is achieved (step S2-3). Specifically, the game server 30 of the application B compares the mission and achievement conditions recorded in the promotion information storage unit 32 with the game progress status of the user. If the mission is satisfied under the achievement conditions, it is determined that the mission is achieved.

  If it is determined that the game progress has not reached the mission and the mission has not been achieved ("NO" in step S2-3), the game server 30 of the application B continues the game progress management process (step S2- 2).

  On the other hand, when the game progress status has reached the mission achievement and it is determined that the mission is achieved (in the case of “YES” in step S2-3), the game server 30 of the application B executes the mission achievement notification process (step S2-4). ). Specifically, the game server 30 transmits a mission achievement notification to the management server 20. This mission completion notification includes data regarding campaign ID, mission ID, and user ID.

  Next, the control unit 21 of the management server 20 executes a mission achievement management process (step S2-5). Specifically, the mission management unit 214 of the control unit 21 records the mission achievement status in the achievement status information storage unit 25 based on the mission achievement notification acquired from the game server 30. This process will be described later with reference to FIG. Then, the mission management unit 214 returns the mission achievement processing result to the game server 30.

  Next, the game server 30 of the application B executes a mission achievement result notification process (step S2-6). Specifically, the game server 30 of the application B transfers the mission achievement processing result from the management server 20 to the user terminal 10 of the login user.

  Next, the user terminal 10 executes a mission achievement result output process (step S2-7). Specifically, the user terminal 10 outputs the mission achievement result on the display. In this case, as shown in FIG. 4C, a mission completion display 521 is output to the customer destination application screen 520.

  After that, in the state of logging in to the management server 20, the user terminal 10 executes a selection process for the application A that is a customer sending source (step S3-1). Specifically, the user terminal 10 accesses the game server 30 of the application A.

  In this case, the game server 30 of the application A executes a mission achievement confirmation link display process (step S3-2). Specifically, the game server 30 of the application A transmits a game screen including a mission achievement confirmation link to the user terminal 10. The mission achievement confirmation link includes data related to the campaign ID related to the application A. In this case, as shown in FIG. 4D, a mission achievement confirmation link 531 is output on the customer-source application screen 530 on the display of the user terminal 10.

  Next, in the user terminal 10, a mission achievement confirmation link selection process is executed (step S3-3). Specifically, when confirming the mission achievement status, the mission achievement confirmation link is selected. In this case, the user terminal 10 transmits a mission achievement confirmation request to the management server 20.

  Next, the game server 30 of the application A executes a mission achievement confirmation process (step S3-4). Specifically, the game server 30 of the application A transmits a mission achievement status request to the management server 20. The mission achievement status request includes data related to the campaign ID recorded in the promotion information storage unit 32 and the user ID of the login user.

  Next, the control unit 21 of the management server 20 executes achievement status information provision processing (step S3-5). Specifically, the mission management unit 214 of the control unit 21 extracts achievement status management information associated with the campaign ID and the user ID included in the mission achievement status request from the achievement status information storage unit 25. Next, the mission management unit 214 specifies the achieved mission ID using the extracted achievement status management information. Then, the mission management unit 214 transmits the mission achievement status including the identified mission ID to the game server 30 of the application A.

  Next, the game server 30 of the application A executes incentive provision processing according to the achievement status (step S3-6). Specifically, the game server 30 of the application A uses the promotion information storage unit 32 to identify an incentive according to the mission ID included in the mission achievement status. Then, the game server 30 gives an incentive to the login user when the achievement condition of the promotion management information is satisfied. Furthermore, the game server 30 transmits an incentive provision result to the user terminal 10.

  Next, the user terminal 10 performs a result output process (step S3-7). Specifically, the user terminal 10 outputs an incentive provision result on the display. In this case, as shown in FIG. 4E, an incentive acquisition display 541 is output on the customer-source application screen 540 on the display of the user terminal 10. Here, the incentive acquisition display 541 outputs a message indicating that an item as an incentive has been acquired.

(Mission achievement management process)
Next, the mission achievement management process will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes a mission achievement information acquisition process (step S4-1). Specifically, the mission management unit 214 of the control unit 21 acquires a mission achievement notification from the game server 30 (here, the game server 30 of the application B).

  Next, the control part 21 of the management server 20 performs an achievement user specific process (step S4-2). Specifically, the mission management unit 214 of the control unit 21 identifies an achieved user based on the user ID included in the mission completion notification.

  Next, the control part 21 of the management server 20 performs the determination process about whether it is a cross promotion object (step S4-3). Specifically, the mission management unit 214 of the control unit 21 determines whether or not the participation status management information in which the user ID of the mission achievement notification and the game ID of the customer is recorded is registered in the participation status information storage unit 24. Confirm. If the participation status management information is registered in the participation status information storage unit 24, it is determined to be a cross promotion target.

  If the participation status management information in which the user ID of the mission achievement notification and the game ID of the customer is recorded is not registered and it is determined that it is not subject to cross promotion (in the case of “NO” in step S4-3), the mission The achievement management process is terminated.

On the other hand, if the participation status management information in which the user ID of the mission achievement notification and the game ID of the customer is recorded is registered and it is determined that it is a cross-promotion target (in the case of “YES” in step S4-3), management is performed. The controller 21 of the server 20 executes a mission achievement status recording process (step S4-4). Specifically, the mission management unit 214 of the control unit 21 generates achievement status management information including a user ID, a campaign ID, and a mission ID, and records them in the achievement status information storage unit 25.
Then, as shown in FIG. 3, the game server 30 of the customer origin executes an incentive provision process according to the achievement status (step S3-6).

According to the above embodiment, the following effects can be obtained.
(1) In the above embodiment, the management server 20 is used as a platform for managing users who use a plurality of applications for the user terminal 10. The management server 20 includes a control unit 21, a user information storage unit 22, a campaign information storage unit 23, a participation situation information storage unit 24, and an achievement situation information storage unit 25. The campaign information storage unit 23 in the platform allows the user to grasp the participation status of campaigns related to a plurality of applications. Further, the achievement status information storage unit 25 in the platform can grasp the achievement status of the mission set in the customer application in the customer application. Therefore, even if the application providers are different, cross promotion can be performed to promote activation of overall application usage.

  (2) In the said embodiment, the control part 21 of the management server 20 performs the determination process about whether there exists campaign participation qualification (step S1-4). If it is determined that there is a campaign participation qualification (“YES” in step S1-4), the control unit 21 of the management server 20 executes a campaign notification process (step S1-9). Then, the game server 30 of the application A executes a campaign banner generation process (Step S1-10). Thereby, in a specific application, cross promotion which introduces other applications can be performed.

  When the campaign banner is selected, the control unit 21 of the management server 20 executes a campaign participation registration process (step S1-14). Thereby, in the participation status information storage part 24, the customer sending status in the cross promotion can be grasped.

  (3) In the above embodiment, when a campaign banner is selected, the control unit 21 of the management server 20 executes a destination information transmission process (step S1-13). And the user terminal 10 performs a redirect process (step S1-15). Thereby, it can guide to the game server 30 of another application from a specific application.

  (4) In the above embodiment, the game server 30 of the application B executes a determination process as to whether or not the mission is achieved (step S2-3). When it is determined that the mission is achieved (in the case of “YES” in step S2-3), the game server 30 of the application B executes a mission achievement notification process (step S2-4). And the control part 21 of the management server 20 performs a mission achievement management process (step S2-5). Thereby, the achievement status of the mission in cross promotion can be grasped.

  When the mission achievement confirmation link selection process (step S3-3) is executed in the user terminal 10, the game server 30 of the application A executes the mission achievement confirmation process (step S3-4). And the control part 21 of the management server 20 performs the provision process of achievement status information (step S3-5). Thereby, in each customer origin, the incentive according to the mission achievement situation can be provided to the user.

  (5) In the above embodiment, the control unit 21 of the management server 20 executes a determination process as to whether or not there is a campaign participation qualification (step S1-4). Here, when it is registered as a use game in the user management information and the customer destination application is used, it is determined that there is no campaign participation qualification. When the promotion effect cannot be expected, provision of the campaign can be suppressed.

In addition, you may change the said embodiment as follows.
In the above embodiment, the case where cross promotion is performed in a game as an application has been described. However, the target application for cross promotion is not limited to a game. Cross promotion can be performed in a plurality of applications provided in the platform.

  In the above embodiment, the game server 30 of the application B executes a determination process as to whether or not the mission is achieved (step S2-3). This determination may be executed in the management server 20. In this case, the progress status information of the application B is acquired from the game server 30. Then, the mission management unit 214 of the control unit 21 collates the progress status information with the campaign management information and the mission management information recorded in the campaign information storage unit 23 to determine mission achievement. When the mission management unit 214 determines that the mission has been achieved, the mission management unit 214 records the achievement status management information in the achievement status information storage unit 25.

  In the above embodiment, a cross promotion in which a customer is transferred from the application A to the B is assumed. Here, cross promotion may be performed mutually. In this case, in the campaign information storage unit 23, campaign management information related to the customer from application B to A is recorded for the customer from application A to B. As a result, it is possible to encourage users who use individual applications to mutually use a plurality of applications.

  In the above embodiment, a cross promotion in which a customer is sent from the application A to the application B is assumed. Here, the management server 20 may specify an application for cross promotion. In this case, the number a of users who use the application A who does not use the application B is compared with the number of people who use the application B but does not use the application A. Then, the incentive is changed based on the comparison result. For example, the incentive provided in an application with a smaller number of people is increased. As a result, it is possible to send the customer to the other application and prompt the user to return to the application that is the customer.

  In the above embodiment, promotion is performed in which one user is sent from the customer source application to the customer destination application. Instead of this, a promotion may be performed for a plurality of group users. In this case, the management server 20 executes group registration processing and mission achievement management processing.

(Group registration process)
First, the group registration process will be described with reference to FIG.
Here, when the campaign selection notification is acquired from the user terminal 10, the control unit 21 of the management server 20 executes a group user registration process (step S5-1). Specifically, the campaign management unit 212 of the control unit 21 outputs a group registration screen on the display of the user terminal 10. On this group registration screen, a user who is a friend or friend of the logged-in user and is recorded in the user information storage unit is designated. Then, the campaign management unit 212 acquires the user ID of the group user designated on the group registration screen from the user terminal 10.

  Next, the control unit 21 of the management server 20 executes campaign participation qualification determination processing (step S5-2). Specifically, the campaign management unit 212 of the control unit 21 acquires user management information from the user information storage unit 22 based on the user ID of the group user. And the campaign management part 212 confirms a use game in the user management information of the designated group user using the user information storage part 22. FIG. Here, it is determined that the group user who is registered for use of the customer-source application and is not registered for use of the customer-destination application has a campaign participation qualification.

  Next, the control part 21 of the management server 20 performs the registration process of the group user who has participation qualification (step S5-3). Specifically, the campaign management unit 212 of the control unit 21 registers the user ID of the group user who is eligible to participate in the campaign in the participation status information storage unit 24 in association with the ID of the login user.

  Next, the control unit 21 of the management server 20 executes a registration notification process for the group user (step S5-4). Specifically, the campaign management unit 212 of the control unit 21 transmits a campaign participation request to the user terminal 10 of the group user.

(Mission achievement management process)
Next, the mission achievement management process in the group will be described with reference to FIG.
First, the control part 21 of the management server 20 performs the acquisition process of mission achievement information similarly to step S4-1 (step S6-1).

  Next, similarly to steps S4-2 and S4-3, the control unit 21 of the management server 20 identifies the achievement user (step S6-2), and determines whether or not it is a cross promotion target (step S6-3). ).

If it is determined that it is not a cross promotion target (in the case of “NO” in step S6-3), the mission achievement management process is terminated.
On the other hand, when it determines with cross promotion object (in the case of "YES" in step S6-3), the control part 21 of the management server 20 performs the determination process about whether it is a group user (step S6-4). Specifically, the mission management unit 214 of the control unit 21 confirms whether or not the user ID is group-registered in the participation status information storage unit 24. If the user ID is associated with other user IDs and registered as a group, the user ID is determined as a group user.

  When it is determined that the user ID is registered alone and is not a group user (in the case of “NO” in step S6-4), the control unit 21 of the management server 20 performs a process of recording the mission achievement status to the achievement user. Execute (Step S6-5). Specifically, the mission management unit 214 of the control unit 21 generates achievement status management information including a user ID, a campaign ID, and a mission ID, and records them in the achievement status information storage unit 25.

On the other hand, when it determines with a group user (in the case of "YES" in step S6-4), the control part 21 of the management server 20 performs a mission achievement status recording process with respect to a group user (step S6-6). Specifically, the mission management unit 214 of the control unit 21 extracts other user IDs registered in the group in association with the user ID of the login user in the participation status information storage unit 24. Then, the mission management unit 214 generates achievement status management information including the campaign ID and the mission ID in association with all the user IDs of the login user and the group user, and records it in the achievement status information storage unit 25.
Thereby, the mission can be achieved by the group. And a cross promotion can be implemented with respect to a some user.

  In the above embodiment, the control unit 21 of the management server 20 executes a determination process as to whether or not there is a campaign participation qualification (step S1-4). Here, it is possible to limit the number of people participating in the campaign. In this case, data relating to the number of people who can participate is recorded in the campaign information storage unit 23. And the control part 21 of the management server 20 performs a banner output determination process.

(Banner output judgment processing)
Next, banner output determination processing will be described with reference to FIG.
Here, first, the control unit 21 of the management server 20 executes a determination process as to whether or not there is a campaign participation qualification, similarly to step S1-4 (step S7-1). ).

  When it is determined that there is no qualification to participate in the campaign (in the case of “NO” in step S7-1), the control unit 21 of the management server 20 executes login notification processing in the same manner as in step S1-5 (step S7-2). ).

  On the other hand, when it is determined that there is a campaign participation qualification (in the case of “YES” in step S7-1), the control unit 21 of the management server 20 executes a determination process as to whether or not there is a limit on the number of people in the cross promotion. (Step S7-3). Specifically, the mission management unit 214 of the control unit 21 checks whether or not the number of people who can participate is recorded in the campaign information storage unit 23 in association with the campaign ID. Here, when the possible number of participants is recorded, it is determined that there is a limit on the number of people.

  In the cross promotion, when it is determined that there is a limit on the number of persons (in the case of “YES” in step S7-3), the control unit 21 of the management server 20 executes a campaign participation number calculation process (step S7-4). Specifically, the campaign management unit 212 of the control unit 21 calculates the number of participants in the cross promotion by counting the user ID associated with the campaign ID of the cross promotion in the participation status information storage unit 24. .

  Next, the control part 21 of the management server 20 performs the determination process about whether a campaign participation is possible (step S7-5). Specifically, the campaign management unit 212 of the control unit 21 compares the calculated number of participants with the number of people who can participate. When the number of participants is less than the number of participants, it is determined that the campaign can participate.

  When the number of participants is equal to or greater than the number of participants and it is determined that the campaign cannot be participated (in the case of “NO” in step S7-5), the control unit 21 of the management server 20 executes a login notification process (step S7). -2).

  On the other hand, when it is determined that the number of participants is less than the possible number of participants and the campaign can be participated (in the case of “YES” in step S7-5), the control unit 21 of the management server 20 notifies the campaign notification as in step S1-9. Processing is executed (step S7-6). In this case, the campaign management unit 212 of the control unit 21 includes data on the remaining number of people until the number of participants reaches the number of people who can participate in the campaign notification.

  Even when it is determined that the number of people who can participate is not recorded and there is no limit on the number of people in the cross promotion (in the case of “NO” in step S7-3), the control unit 21 of the management server 20 performs the campaign notification. Processing is executed (step S7-6).

  And as shown in FIG. 2, the game server 30 of the application A performs a campaign banner production | generation process (step S1-10). Here, information about the remaining number of people is included in the campaign banner.

  As a result, the number of participants in the campaign can be limited. Furthermore, prompt participation in the campaign can be promoted by displaying the remaining number of people in the campaign banner.

  DESCRIPTION OF SYMBOLS 10 ... User terminal, 20 ... Management server, 21 ... Control part, 211 ... User management part, 212 ... Campaign management part, 213 ... Redirector, 214 ... Mission management part, 22 ... User information storage part, 23 ... Campaign information storage part 24 ... Participation status information storage unit, 25 ... Achievement status information storage unit, 30 ... Game server, A, B ... Application.

Claims (7)

A method for managing a plurality of applications using a storage unit and a control unit connected to a user terminal via a network,
The storage unit
Stores information relating the customer source and customer destination applications, and at least one mission achievement information associated with the user ID of the participating user,
The control unit is
In the user terminal, when the selection of the customer application stored in the storage unit is detected, a link that can be transited to the customer application associated with the customer source is output,
When the link is selected, as a participating user, the user terminal is transitioned to the customer application,
When the mission achievement status information in the customer destination application associated with the user ID of the participating user satisfies a predetermined condition, the customer source application provides the customer source application. An application management method characterized in that an incentive is given to the participating user. A method for managing a plurality of applications using a storage unit and a control unit connected to a user terminal via a network,
The storage unit
For a plurality of applications including at least one application managed by a separate and independent application provider, the user ID of the participating user and at least one mission achievement information are stored,
Among the plurality of applications, an application as a Okukyakumoto, and said feed Kyakumoto become an application application managed by the application provider and different independently application provider of the customer guiding destination application Remember,
The control unit is
In the user terminal, when the selection of the customer application stored in the storage unit is detected, a link that can be transited to the customer application associated with the customer source is output,
When the link is selected, as a participating user, the user terminal is transitioned to the customer application,
When the mission achievement status information in the customer destination application associated with the user ID of the participating user satisfies a predetermined condition, the customer source application provides the customer source application. An application management method characterized in that an incentive is given to the participating user. In the storage unit, a use game is registered in association with the user ID,
The control unit is
When detecting the selection of the application of the customer from the user terminal, in the storage unit, for the user ID acquired from the user terminal, confirm the usage status of the use registration of the application of the customer destination,
3. The application management method according to claim 1, wherein the link is output when the customer application is not used. The control unit is
When the link is selected, the user ID is stored in the storage unit as a participating user,
The application management method according to any one of claims 1 to 3, wherein achievement status information of user IDs of the participating users registered in the storage unit is acquired from the application of the customer destination. The control unit is
Storing a user group associated with user IDs of a plurality of participating users in the storage unit;
When the achievement status information satisfies a predetermined condition, it is further determined whether the user ID of a user who satisfies the predetermined condition is a group user of a user group in the storage unit,
The application management method according to claim 1, wherein when it is determined as a group user, achievement status information is stored in the storage unit for all users belonging to the user group. . Using the storage unit and the control unit connected to the user terminal via the network, manage a plurality of applications,
The storage unit
Stores information relating the customer source and customer destination applications, and at least one mission achievement information associated with the user ID of the participating user,
The control unit is
In the user terminal, when the selection of the customer application stored in the storage unit is detected, a link that can be transited to the customer application associated with the customer source is output,
When the link is selected, as a participating user, the user terminal is transitioned to the customer application,
When the mission achievement status information in the customer destination application associated with the user ID of the participating user satisfies a predetermined condition, the customer source application provides the customer source application. An application management server characterized in that an incentive is given to the participating user. A program for managing a plurality of applications using a storage unit and a control unit connected to a user terminal via a network,
The storage unit
Stores information relating the customer source and customer destination applications, and at least one mission achievement information associated with the user ID of the participating user,
The control unit
In the user terminal, when the selection of the customer application stored in the storage unit is detected, a link that can be transited to the customer application associated with the customer source is output,
When the link is selected, as a participating user, the user terminal is transitioned to the customer application,
When the mission achievement status information in the customer destination application associated with the user ID of the participating user satisfies a predetermined condition, the customer source application provides the customer source application. An application management program that functions as means for giving an incentive to the participating user.

Images