Point program management server, service system, point program management method, and program

Abstract

This provides a points program management server that can increase the incentive for users to participate in services that offer points programs. [Solution] The point program management server includes a revenue indicator acquisition unit that acquires revenue indicators for a service based on the usage behavior of multiple users, and a registration unit that registers the revenue indicators for the service and rewards to the users of the service according to the conditions for achieving the revenue indicators for the service.

Description

Technical Field

[0005] ,

[0001] The present invention relates to a point program management server, a service system, a point program management method, and a program.

Background Art

[0002] For example, in an EC (Electronic Commerce) site, rewards such as points are given to users according to their purchase history. Further, in Patent Document 1, a technique for increasing incentives for purchases on an EC site is described by adding rewards such as a privilege of increasing the multiple of points obtained by purchase to users who have achieved conditions such as purchasing at multiple stores of the EC site (going on a shopping spree).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In addition, there are cases where a point program is implemented that gives rewards such as granting points common to the EC site or increasing the point multiplier obtained by purchases on the EC site to users whose usage history in a specific service other than the EC site satisfies a predetermined achievement condition. At this time, in order to obtain the rewards of this point program, users may use the specific service within the minimum range that satisfies the achievement condition. However, users who only perform the minimum usage behavior that satisfies the achievement condition in this way contribute little to the specific service participating in the point program, and the rewards obtained in the point program may also be minimized. Then, the advantages for users to participate in the point program are limited.

[0005] The object of the present invention is to provide a points program management server, a points program management method, and a program that can increase the incentive for users to use services that allow them to participate in a points program. [Means for solving the problem]

[0006] According to one aspect of this disclosure, the points program management server includes a revenue indicator acquisition unit that acquires revenue indicators for a service based on the usage behavior of multiple users, and a registration unit that registers the revenue indicators for the service and rewards to the users of the service according to the conditions for achieving the revenue indicators for the service.

[0007] According to one aspect of the present disclosure, the service system comprises the above-mentioned point program management server and a service server that operates the service, wherein the service server includes a revenue indicator calculation unit that calculates a revenue indicator based on the user's usage behavior in the service it operates, and a transmission unit that transmits the calculated revenue indicator to the point program management server.

[0008] According to one aspect of this disclosure, a point program management method includes the steps of: obtaining a revenue indicator for a service based on the usage behavior of multiple users; and registering the revenue indicator for the service and the rewards corresponding to the achievement conditions of the revenue indicator for the service to the users of the service.

[0009] According to one aspect of this disclosure, the program causes a point program management device to perform the steps of: obtaining a revenue indicator for a service based on the usage behavior of multiple users; and registering the revenue indicator for the service and a reward corresponding to the achievement conditions of the revenue indicator for the service to the users of the service. [Effects of the Invention]

[0010] According to the above configuration, it is possible to increase the incentive for users to use services that allow them to participate in a points program. [Brief explanation of the drawing]

[0011] [Figure 1] This is a schematic diagram showing the overall configuration of the service system according to the first embodiment. [Figure 2] This is a block diagram showing the functional configuration of the point program management server and service server according to the first embodiment. [Figure 3] This is a first flowchart showing an example of processing by a service server according to the first embodiment. [Figure 4] This is a second flowchart showing an example of processing by a service server according to the first embodiment. [Figure 5] This figure shows an example of a contribution table according to the first embodiment. [Figure 6] This is a first flowchart showing an example of processing by the point program management server according to the first embodiment. [Figure 7] This is the first figure illustrating an example of adjusting compensation according to a revenue indicator according to the first embodiment. [Figure 8] This figure shows an example of a reward table according to the first embodiment. [Figure 9] This figure shows an example of compensation registration information according to the first embodiment. [Figure 10] This is a second diagram illustrating an example of adjusting compensation according to a revenue indicator according to the first embodiment. [Figure 11] This is a third flowchart showing an example of processing by the service server according to the first embodiment. [Figure 12] This is a second flowchart showing an example of processing by the point program management server according to the first embodiment. [Figure 13] This figure shows an example of a reward presentation screen according to the first embodiment. [Figure 14] This figure shows an example of a reward table presentation screen according to the first embodiment. [Figure 15] This is a schematic block diagram showing the configuration of a computer according to the first embodiment.

Mode for Carrying Out the Invention

[0012] <First Embodiment> Hereinafter, embodiments will be described in detail with reference to the drawings.

[0013] (Overall Configuration of Service System) FIG. 1 is a schematic diagram showing the overall configuration of a service system according to the first embodiment. The service system 1 is a system for realizing an Internet integrated service that can provide services to users through a network NW such as the Internet. As shown in FIG. 1, the service system 1 includes a point program management server 2, a user management server 3, a plurality of service servers 4, and a plurality of user terminals 5.

[0014] The point program management server 2 operates a point program that gives rewards (points) corresponding to service usage behaviors to service users U. The point program is a program that gives points and increases the point awarding rate (bonus) according to service usage behaviors. The detailed functional configuration of the point program management server 2 will be described later.

[0015] The user management server 3 registers and manages user IDs of users. Users include service providers P who provide services in the Internet integrated service and service users U who use at least one service of the Internet integrated service.

[0016] The service server 4 is a server for operating services provided by the service provider P and is provided for each service, for example. The service server 4 performs, for example, recording of the usage behaviors of service users U, calculation of service revenue indicators, and the like. The detailed functional configuration of the service server 4 will be described later.

[0017] User terminal 5 is a terminal device owned by service user U, such as a smartphone, tablet, or personal computer. User terminal 5 has a browser and applications. Service user U can use various services of the comprehensive internet service through websites displayed in the browser and applications.

[0018] (Regarding comprehensive internet services) An internet comprehensive service may include multiple services. These multiple services may include online services provided using a network. Online services may be provided via websites, applications, etc. Examples of services included in an internet comprehensive service include point programs, mobile communications, carrier billing, fiber optic internet connections, credit cards, app payments, electronic money, cryptocurrency trading or sales, online banking, online securities, online insurance, reservation services for facilities and transportation (accommodation, car rental, transportation tickets, beauty salons, golf courses, etc.), online commerce such as e-commerce sites, receipt and point exchange services, check-in services, social networking services (SNS), advertising distribution or management of posting and publication, campaign measures using coupons and other benefits, marketing agency, marketing research, various media outlets, agency services for local government services, job matching services, real estate-related transactions, medical consultation assistance, childcare and elder care assistance, pet care assistance, and educational support. Mobile communications services may be provided using a core network.

[0019] (Regarding users and user IDs) Each user authenticates using a common user ID (common user ID) across multiple services provided by Service System 1. This allows usage behavior to be linked and recorded under a single common user ID, even if each user uses different services. Furthermore, for some services provided by Service System 1, separate membership registration (assigning an individual user ID, which is a user ID issued independently by the service) may be required, provided the user is a member of Service System 1 (possesses a common user ID). User management server 3 may manage both the common user ID and the individual user ID of Service System 1, linked to the same user, if permitted by the user. If the service is in a platform format, a common user ID may be used for all platform participants. User management server 3 may also assign a user rank to each user's user ID. The user rank may be dynamically changed, for example, based on usage behavior for each service over a predetermined period.

[0020] The users of Service System 1 include service users U who utilize the services provided through Service System 1, and service providers P who provide services to service users U. Mobile communication operators, financial institutions, online commerce merchants, advertisers, etc. are service providers P, while subscribers to mobile communication and financial institutions, online commerce buyers, and advertisers, etc. are service users U. In the following explanation, service users U will also be simply referred to as "user U".

[0021] (Regarding compensation) Rewards include points and perks (coupons, discounts, etc.). This section explains an example where the reward is points. In the following explanation, "points" can be understood as other rewards such as "coupons" or "discounts" as appropriate.

[0022] In a points program, points are awarded to each user U, and each user U can use the awarded points. Point awarding may involve registering a predetermined number of points linked to user U's user ID. Points may be awarded for use of each service of the comprehensive internet service, or for use of services not included in the comprehensive internet service (e.g., purchases at affiliated retail stores). Point awarding may be considered synonymous with point issuance. Issuance and awarding may be treated as the same process or as different processes. The points awarded may be treated as points earned by user U. Points may be awarded for transactions within the service. For example, they may be awarded at a return rate (e.g., 1%) based on the purchase amount of items in online commerce. Points may be treated as a partial return of consideration for purchased items, or as a discount on the consideration. In this sense, the award rate may include the award rate, return rate, and discount rate. The awarded points may be treated as benefits, rewards, or incentives for using each service. The award rate may differ depending on the user rank for the same eligible activity (e.g., the same item purchase amount). Points may be used as a means of payment for end-consumer transactions, B2C and C2C transactions, and B2B transactions for corporations. Points awarded may be defined as usable points. Point usage may refer to the use of points registered to each user U for payments, etc., in each service. Usage is not limited to payments and may be according to the purpose and use set by each service. Services that are eligible for point usage may or may not be included in the comprehensive internet service. Points may be exchangeable for other media of value such as money or currency. Usage is a form of exchange between points and media of value. The exchange rate may be predetermined. For example, 1 point may be equivalent to 1 yen. Media of value may include cryptocurrency, cash, and various tokens. Points may be awarded and used at least in the comprehensive internet service. Usable points may include regular points and limited-time points.Regular points and limited-time points may be linked to each user ID with a separate identifier. Regular points are valid for one period (e.g., 1 year) from the last date of issuance of all points held by each user U, while limited-time points may be valid for a shorter period (e.g., 0.5 years) from the date of issuance to each user U. The last date of issuance of regular points may be the last date of use of the service for which points are awarded in each service. In other words, the validity periods until expiration are different for both types of points. Furthermore, the validity period until expiration of regular points may differ for each user U depending on their service usage. The conditions for issuance of regular points and limited-time points may differ in each service. For example, limited-time points may be issued in specific campaigns, while regular points may be issued for normal item transactions in online commerce, etc. Regular points and limited-time points may be issued simultaneously. For example, for normal item transactions in online commerce, etc., regular points at the normal multiplier (e.g., 1%) may be issued, along with points at an additional multiplier as a campaign multiplier (e.g., +1x, or 2%). This added multiplier may be treated as a reward (perk) for user U. The source of the points to be awarded may be borne by each service, or the source may be distributed as a common burden for the internet comprehensive service. The source may also be borne by the user under certain conditions. If the user is a service provider P who provides each service to service user U, an online commerce merchant, an advertiser, etc., then each of these service providers P may bear the source of the points. If the user is a service user U who is the end consumer, then points may be used as a means of payment in C2C transactions. In this case, the process of moving the holder of already awarded points (the user ID to which the points are linked) may be carried out. The source bearer may or may not possess a common user ID. If the source bearer possesses a common user ID, then the claim for the source of points awarded through a specific campaign may be settled with the points registered and linked to the source bearer's common user ID.

[0023] (Regarding user behavior) User U's actions include purchasing, registering, downloading, installing, sending, visiting, requesting information, making payments, billing, selecting optional content, contracting, reserving, trading, communicating and making calls, browsing information, viewing content such as music and videos, engaging with content such as posting, actions that can be measured for advertising effectiveness such as viewing and clicking on advertisements, financial actions such as deposits, withdrawals, remittances, securities trading, and margin trading, and actions that each service provider P, its affiliates, and the management and operation entity of service system 1 expect from User U. Furthermore, all or part of these actions may be referred to as item transactions.

[0024] (Functional configuration of the points program management server) Figure 2 is a block diagram showing the functional configuration of the point program management server and service server according to the first embodiment. As shown in Figure 2, the point program management server 2 includes a revenue indicator acquisition unit 21, a registration unit 22, an adjustment unit 23, a presentation unit 24, and a reward data storage unit 25.

[0025] The revenue indicator acquisition unit 21 acquires revenue indicators for the service based on the usage behavior of user U.

[0026] The registration unit 22 registers rewards for user U based on service usage. Rewards include campaign rewards given for using the service covered by the campaign during the campaign period, regular points given for service usage regardless of the campaign, and points actually awarded to user U based on the campaign rewards and regular points. In this embodiment, the registration unit 22 registers campaign rewards for the service user U based on the service's revenue indicator and the conditions for achieving the service's revenue indicator. It also registers regular points for service usage to user U regardless of whether a campaign is running or the revenue indicator. In this embodiment, the service includes a first service and a second service, and the campaign rewards registered by the registration unit 22 are point multipliers that increase the regular points awarded based on user U's usage of the second service. Therefore, if campaign rewards are registered, the points actually awarded to user U will be the regular points increased according to the point multiplier. In other embodiments, campaign rewards may be fixed points added to regular points.

[0027] The adjustment unit 23 adjusts the campaign reward (point multiplier) for user U according to user U's contribution to the revenue indicator.

[0028] The presentation unit 24 presents the rewards awarded to user U when user U uses the service. The rewards presented by the presentation unit 24 include the campaign rewards (point multipliers) registered by the registration unit 22 and the points that user U is expected to earn, calculated based on these campaign rewards.

[0029] The reward data storage unit 25 stores the rewards registered for each user U. The reward data storage unit 25 also pre-stores the conditions for achieving the revenue metrics for each service, as well as data used to calculate rewards.

[0030] (Service server functional configuration) As shown in Figure 2, the service server 4 includes a user behavior acquisition unit 41, a revenue indicator calculation unit 42, a contribution level determination unit 43, a transmission unit 44, a user behavior storage unit 45, a revenue indicator storage unit 46, and a contribution level storage unit 47.

[0031] The user activity acquisition unit 41 acquires the service usage activity of each user U. The usage activity includes, for example, the user U's user ID (common user ID or individual user ID), date and time of use, content of use, amount of use, etc.

[0032] The revenue indicator calculation unit 42 calculates the revenue indicator for the service based on the usage behavior of all users U.

[0033] The contribution determination unit 43 determines the contribution of each user U to the service's revenue indicators.

[0034] The transmission unit sends the service's revenue metrics and each user U's contribution to the points program management server 2.

[0035] The user behavior memory unit 45 stores (accumulates) the user behavior of each user U.

[0036] The revenue indicator storage unit 46 stores the revenue indicators for the services calculated by the revenue indicator calculation unit 42.

[0037] The contribution level storage unit 47 stores the contribution level of each user U to the revenue indicators, etc., as determined by the contribution level determination unit 43.

[0038] (Regarding the calculation of profitability indicators) Figure 3 is a first flowchart showing an example of processing by a service server according to the first embodiment. The user behavior acquisition unit 41 of the service server 4 sequentially stores and accumulates the user behavior of user U in the user behavior storage unit 45. Figure 3 shows an example of the process by which each service server 4 calculates a service revenue indicator based on the user behavior stored in the user behavior storage unit 45.

[0039] The revenue indicator calculation unit 42 extracts the usage behavior of each user U during a predetermined aggregation period from the usage behavior storage unit 45 and calculates the revenue indicator for the service during this aggregation period from the usage behavior of all users U (step S101). The calculated revenue indicator is stored in the revenue indicator storage unit 46 for each aggregation period.

[0040] The aggregation period is, for example, a certain period in the past including the month prior to user U's login, or a certain period immediately preceding the login. This period can be set arbitrarily to one month, several months, one year, etc. For example, if user U logs in on August 10th and the period is one month, the past period including the previous month would be set to July 1st to July 31st, and the most recent period would be set to July 9th to August 9th. This aggregation period can be changed arbitrarily by the operator of the points program, and the changed value is distributed, for example, from the points program management server 2 to each service server 4.

[0041] Revenue metrics are indicators that represent the profit generated for a service in response to the use of that service by users (U). Revenue metrics can be expressed as, for example, ARPU (Average Revenue Per Use). ARPU is an indicator that represents the revenue per user and is calculated as "ARPU = Total Service Revenue ÷ Number of Registered Users". Note that the number of registered users may be the total number of users (U) who have registered to use the service, or it may be the number of active users, excluding users (U) who have registered but do not actually intend to use the service (e.g., those who have not used the service for more than X months).

[0042] If the service is a mobile communication service, the ARPU for data communication and the ARPU for voice calls may be calculated separately.

[0043] If a service generates revenue through system usage fees, such as for financial services, the revenue used in calculating ARPU may be determined based on at least one of the following: trading fees, asset management fees, payment processing fees, etc.

[0044] If the service is a physical store service, for example, revenue is generated when a customer makes an online reservation for a hair salon, visits the salon in person, and receives a service. Similarly, for accommodation and golf course reservation services, the APRU (Average Revenue Per User) is calculated based on revenue generated from the use of physical stores. The same applies to purchases made at physical stores.

[0045] If the service is an advertising service and revenue is based on ad exposure (awareness-focused, engagement-focused), ARPU may be calculated as "number of media visits × revenue generated per impression (cost per mille; CPM)". The number of media visits is the number of times a user U visits the media where the ad is displayed, and in the case of a service provided through an application, it may be replaced with the number of times the application is used. The cost per impression (CPM) is the advertising cost spent by the advertiser divided by the number of ad exposures. Alternatively, if revenue is based on ad clicks or installs (conversion-focused), ARPU may be calculated as "revenue generated per click (cost per click; CPC) × click-through rate (CPC)". The cost per click (CPC) is the advertising cost spent by the advertiser divided by the number of clicks on the media or application where the ad is displayed. Furthermore, if the focus is on the final outcome (conversion), such as purchases or requests for information, in terms of advertising revenue (acquisition-oriented), ARPU can be calculated as "sales from the final outcome (cost per action; CPA) × conversion rate." Cost per action (CPA) is the advertising cost spent by the advertiser divided by the number of times an action, such as a purchase, occurs through the advertising medium or application.

[0046] Furthermore, if advertisements are placed on media such as websites or applications that provide each service, the above-mentioned advertising service ARPU may be calculated for each medium providing the service and added to the service ARPU.

[0047] The revenue indicator calculation unit 42 may also calculate ARPPU (Average Revenue Per Paid User) or ARPA (Average Revenue Per Account) as the service's revenue indicator instead of ARPU. Furthermore, the revenue indicator calculation unit 42 may combine two or more of ARPU, ARPPU, and ARPA to calculate the revenue indicator.

[0048] ARPPU is an indicator that represents revenue per paying user and is calculated as "ARPPU = Total Service Revenue ÷ Number of Paying Users". A paying user is a user U who has registered to use the service and has paid the service fee during the reporting period. For example, if a service includes usage-based billing services (such as subscriptions or advertising billing), ARPPU may be calculated for the paying users of that service. Alternatively, the combined (e.g., average) value of ARPU and ARPPU within a service may be used as a revenue indicator.

[0049] ARPA is an indicator that represents revenue per account and is calculated as ARPA = Total Service Revenue ÷ Number of Accounts. The number of accounts is the number of subscribers; for example, in a mobile communication service, if one person subscribes to multiple mobile devices, the number of accounts is "1". If the service is used by a large group of users U, such as a corporation, or if one user U uses it on multiple user devices 5, ARPA may be used instead of ARPU to calculate the revenue indicator. Alternatively, the combined (e.g., averaged) value of ARPU and ARPPU within the service may be used as the revenue indicator.

[0050] Furthermore, a single service may include multiple functions (for example, two or more of the following: telecommunications, finance, online commerce, advertising, etc.). In this case, the sum of the revenue metrics for the multiple functions may be used as the revenue metric for the service.

[0051] Next, the transmission unit 44 reads the revenue indicator for the service stored in the revenue indicator storage unit 46 and transmits it to the point program management server 2 (step S102). The transmission unit 44 may also transmit the revenue indicator to the point program management server 2 when the revenue indicator calculation unit 42 calculates the revenue indicator, or when the point program management server 2 requests it.

[0052] (Regarding the determination of contribution) Figure 4 is a second flowchart showing an example of processing by a service server according to the first embodiment. Figure 4 shows an example of the process by which each service server 4 determines the degree of each user's contribution to the service based on the usage behavior stored in the usage behavior storage unit 45.

[0053] For example, the contribution determination unit 43 extracts the usage behavior of each user U during a predetermined aggregation period from the usage behavior storage unit 45 and determines the contribution of each user U to the service revenue indicator during this aggregation period (step S201). The contribution determination unit 43 may also determine the contribution of a specific user U when requested by the point program management server 2.

[0054] Figure 5 shows an example of a contribution table according to the first embodiment. Figure 5 shows a contribution table T1 that associates usage behavior with contribution when the service is a mobile communication service, for example. The contribution determination unit 43 has a contribution table T1 as shown in Figure 5 in advance and refers to this contribution table T1 to determine the contribution according to the usage behavior of user U (in the example in Figure 5, the amount of data communication used by the user during the aggregation period). For example, if the amount of data communication by a certain user U during the aggregation period is 10GB, the contribution of this user U is "+2". This contribution may be expressed as a reward (the value of the point multiplier added) as in the example in Figure 5, or it may be an ordinal number associated with the reward. The determined contribution is stored in the contribution storage unit 47 for each user U.

[0055] Next, the transmission unit 44 reads the contribution of user U stored in the contribution storage unit 47 and transmits it to the point program management server 2 (step S202). The transmission unit 44 may transmit the contribution of all users U to the point program management server 2 when the contribution determination unit 43 has determined the contribution of each user U, or it may transmit only the contribution of a specific user U to the point program management server 2 when the point program management server 2 requests the contribution of that user U.

[0056] (Regarding registration of rewards) Figure 6 is a first flowchart showing an example of processing by a points program management server according to the first embodiment. Figure 7 is a diagram illustrating an example of adjusting rewards according to a revenue indicator according to the first embodiment. Referring to Figures 6 and 7, the processing flow of a points program in which the points program management server 2 adjusts the campaign rewards for user U in the second service based on the usage behavior of user U as a whole for the first service among multiple services of the Internet comprehensive service will be explained. The first service and the second service may each include multiple services. In the example of Figure 6, the points program management server 2 adjusts the campaign rewards for the second service during the reward grant period based on the usage behavior of user U as a whole for the first service during a predetermined aggregation period. The usage behavior of user U as a whole for the first service is evaluated by the revenue indicator of the first service calculated by the processing shown in Figure 3. As shown in Figure 7, for example, the points program management server 2 adjusts the campaign rewards 2 for the next aggregation period 2 from the revenue indicator 1 for aggregation period 1, and adjusts the campaign rewards 3 for the next aggregation period 3 from the revenue indicator 2 for aggregation period 2. That is, the reward grant period is the next aggregation period, as shown in Figure 7. In this way, the points program management server 2 changes the campaign rewards for each period according to the revenue indicators of the first service. Here, we will explain an example in which the campaign reward for user U, which is adjusted according to the use of the first service, is an additional point multiplier (+x). For example, if the normal point accrual rate is 1% and the additional point multiplier due to the reward is +2x, then 1% × (1 + additional point multiplier of 2x) = 3% of points will be awarded for the usage behavior (amount spent) of the second service. In other embodiments, the campaign reward for user U, which is adjusted according to the use of the first service, may be a fixed amount of points (for example, +100 points) awarded when the second service is used. Note that "when the second service is used" can be arbitrarily set, such as when some usage behavior is performed once in the second service, or when the second service is used for a predetermined amount or more.

[0057] First, the revenue indicator acquisition unit 21 selects an unprocessed first service from among the first services that are subject to the point program (step S301), and acquires the revenue indicator for a certain aggregation period (for example, aggregation period 1) of the selected first service (step S302). At this time, the revenue indicator acquisition unit 21 may request the service server 4 of the selected first service to send the revenue indicator for aggregation period 1, or it may read the revenue indicator for aggregation period 1 of the first service that has been received in advance from each service server 4 and stored in the reward data storage unit 25.

[0058] Next, the registration unit 22 determines the campaign reward for the first service during the target period (next aggregation period 2) based on the revenue indicator of the selected first service and the achievement conditions (reward grant conditions) of the revenue indicator set in advance for this first service (step S303). Here, we will explain an example where the revenue indicator is ARPU.

[0059] Figure 8 shows an example of a reward table according to the first embodiment. For example, as shown in Figure 8, the registration unit 22 has a pre-existing reward table T2 that associates the reward granting conditions for the revenue per user (ARPU) with the rewards, and refers to this reward table T2 to determine the campaign reward according to the ARPU. For example, if the selected first service is service A, and the ARPU becomes 3,000 yen or more, the achievement condition A is met, and a campaign reward of +1x is granted to user U. Therefore, if the ARPU of service A acquired in step S302 is 3,000 yen or more, the registration unit 22 determines that the campaign reward for service A is "+1x". If the ARPU of service A acquired in step S302 is less than 3,000 yen, the registration unit 22 determines that the achievement condition A is not met, and service A is "+0x (no campaign reward)".

[0060] Furthermore, as shown in the example of Service B in Figure 8, the reward granting conditions may have multiple levels of achievement conditions, with higher levels corresponding to larger revenue indicators. Also, the campaign rewards may differ for each achievement condition. For example, the campaign rewards may have multiple point multipliers set so that the higher the level of the achievement condition, the greater the increase in normal points. The registration unit 22 determines, for example, that if the selected first service is Service B, and the ARPU for Service B obtained in step S302 is 1500 yen, then achievement condition B2 is met, and the campaign reward for Service B is "+0.5 times".

[0061] Next, the registration unit 22 registers the campaign rewards determined according to the revenue indicators of the first service. First, the registration unit 22 extracts users U who will receive the campaign rewards for the first service (step S304). For example, suppose the selected first service is service B, and the registration unit 22 decides to award a campaign reward of "+0.5 times" the achievement condition B2 based on the ARPU of service B. In this case, the registration unit 22 extracts users U who use (register as users) both the first service, service B, and the second service as reward recipients.

[0062] Next, the registration unit 22 registers each reward-earning user's user ID and the campaign reward (additional point multiplier) etc. corresponding to the reward granting conditions achieved (step S305).

[0063] Figure 9 shows an example of reward registration information according to the first embodiment. For example, as shown in Figure 9, the registration unit 22 stores reward registration information T3 in the reward data storage unit 25, which is registered by associating the user ID, achieved reward granting conditions and their campaign rewards, and the target period for reward granting for each user U. In the example in Figure 9, for user U with user ID ID01, the point multiplier (+1x) added upon achieving achievement condition A of service A and the point multiplier (+0.5x) added upon achieving achievement condition B2 of service B are registered.

[0064] In Figures 8 and 9, an example is shown in which the registration unit 22 sets the campaign reward for a reward-earning user by referring to a pre-stored reward table T2, but it is not limited to this. In other embodiments, the registration unit 22 may calculate the campaign reward corresponding to the ARPU of the first service using, for example, a pre-set relational expression "campaign reward = f(ARPU)", where f is a function of ARPU. Alternatively, the registration unit 22 may use a relational expression that multiplies the campaign reward by a coefficient set based on past sales and point program performance of the first service so that the amount of campaign reward burden on sales falls within a predetermined range, instead of the function f. Furthermore, the registration unit 22 may use a pre-learned model to determine the optimal campaign reward for the acquired ARPU when the profit and LTV (Life Time Value), etc., are maximized for each value of ARPU.

[0065] Next, the adjustment unit 23 adjusts the campaign reward (additional point multiplier) for each reward-earning user according to the contribution level of the reward-earning user to the selected first service (step S306). At this time, the adjustment unit 23 may request the service server 4 of the selected first service to send the contribution level of the reward-earning user during the aggregation period, or it may extract and read the contribution level of the reward-earning user from the contribution level of user U that has been received in advance from each service server 4 and stored in the reward data storage unit 25. The adjustment unit 23 also adds the point multiplier that is added according to the contribution level of the reward-earning user to the reward registration information T3 and registers it. In the example in Figure 9, the adjustment unit 23 registers a point multiplier (+2x) that is added in accordance with the contribution level of the mobile communication service for user U with user ID ID01, based on the contribution level of user U and the contribution level table T1 (Figure 5).

[0066] In addition, campaign rewards based on contribution may not be set for some of the first services. In this case, the adjustment unit 23 skips the processing in step S306.

[0067] Once the reward registration process for each user U based on the selected first service is complete, it is determined whether the reward registration process for all first services has been completed (step S307). If the reward registration process for all first services has been completed (step S307; YES), the point program management server 2 terminates processing. On the other hand, if there are still first services for which reward registration processing has not been completed, the process returns to step S301 and the above series of processes is executed again.

[0068] Figures 6 and 7 illustrate an example where the point program management server 2 adjusts campaign rewards according to the revenue indicators of each first service at regular intervals (aggregation periods), but the system is not limited to this. In other embodiments, the aggregation period (and the period for which rewards are awarded) may differ for each service, and the point program management server 2 may adjust the campaign rewards of any first service when it obtains the revenue indicators from the service server 4 of any one of the first services. For example, as shown in Figure 10, when the point program management server 2 obtains the revenue indicators 1A for aggregation period 1A from the service server 4A of service A, it adjusts and registers the campaign rewards 2A for the target period of service A (the next aggregation period 2A). At a different time, when it obtains the revenue indicators 1B for aggregation period 1B from the service server 4B of service B, it adjusts and registers the campaign rewards 2B for the target period of service B (the next aggregation period 2B). In other words, in the example of Figure 10, steps S301 and S307 in Figure 6 are omitted, and the point program management server 2 executes the processes of steps S303 to S306 described above each time it obtains a revenue indicator from the service server 4 of each first service to adjust the campaign reward for each first service. Alternatively, as in the example of Figure 10, the service server 4B may calculate the revenue indicator 1B at each point in the aggregation period 1B and send it to the point program management server 2. In this case, the point program management server 2 may compare the revenue indicator 1B with the achievement conditions each time it obtains it, and update the campaign reward 2B if different achievement conditions are met than the previous time.

[0069] The points program management server 2 executes the series of processes shown in Figure 6 during the period in which the campaign is applied. Therefore, for example, the points program management server 2 may first determine whether the campaign is currently in effect, execute the processes shown in Figure 6 if it is, and terminate the process if it is not.

[0070] (Regarding registration of regular points and awarded points) Figure 11 is a third flowchart showing an example of processing by the service server according to the first embodiment. Referring to Figure 11, the process flow in which the point program management server 2 registers regular points for user U in accordance with the use of the second service, and registers the points to be actually awarded to user U based on the regular points and campaign rewards will be explained. Note that the processing in Figure 11 is executed at the time when the points are actually awarded to user U.

[0071] First, the registration unit 22 calculates regular points according to user U's usage of the second service (step S311). For example, if the second service is online commerce, regular points are registered to user U, calculated by multiplying the transaction amount of item transactions (item purchases) by a predetermined point accrual rate (e.g., 1%). Therefore, regular points increase or decrease depending on the transaction amount of item transactions. In addition, regular points are awarded based on the use of the second service, regardless of whether a campaign is being held or whether campaign rewards are applied (whether or not the revenue indicators meet the achievement conditions).

[0072] Furthermore, the registration unit 22 determines whether campaign rewards are applicable to user U (step S312). For example, the registration unit 22 refers to the reward registration information T3 (Figure 9) to determine whether there are any campaign rewards registered for user U, and if so, whether the execution date of the item transaction falls within the reward grant period for any of the campaign rewards. If no campaign rewards are registered, or if the execution date of the item transaction does not fall within any reward grant period, the registration unit 22 determines that campaign rewards are not applicable to user U (step S312; NO), and registers the normal points calculated in step S311 as the points to be actually given to user U (step S315).

[0073] On the other hand, if the date of the item transaction falls within the reward period for any of the campaign rewards, the registration unit 22 determines that the campaign reward will be applied to this user U (step S312; YES). In this case, the registration unit 22 obtains the campaign reward applicable to user U from the reward registration information T3 (step S313). For example, if the date of the item transaction falls within the reward period for both condition A and condition B2 in the reward registration information T3, the campaign reward, which is the sum of these campaign rewards, will be applied to user U. In other words, a point multiplier of +1x for condition A and a point multiplier of +0.5x for condition B2, totaling +1.5x, will be applied to user U.

[0074] Next, the registration unit 22 calculates the points to be actually awarded to user U based on the normal points calculated in step S311 and the campaign rewards obtained in step S312 (step S314). In the example above, a campaign reward of +1.5 times is applied to user U, so the awarded points = normal points × (1 + 1.5). Note that when campaign rewards are applied, the awarded points increase or decrease according to the campaign rewards. In the example in Figure 7, if the revenue indicator in aggregation period 2 is lower than that in aggregation period 1, the point multiplier for campaign reward 3 may be lower than the point multiplier for campaign reward 2. In this case, even if user U makes the same amount of item transactions in aggregation period 2 and aggregation period 3 (i.e., the same value of normal points is registered), the point multiplier applied to aggregation period 3 will be lower than that for aggregation period 2, so the points awarded to user U in aggregation period 3 will also decrease compared to aggregation period 2. In other words, the points actually awarded to user U increase or decrease in each aggregation period in conjunction with the revenue indicator.

[0075] For user U who is eligible for campaign rewards, the registration unit 22 registers the points calculated in step S314 as the points to be actually given to the user (step S315).

[0076] (Regarding the offer of compensation) Figure 12 is a second flowchart showing an example of processing by the points program management server according to the first embodiment. Referring to Figure 12, the process flow by which the points program management server 2 presents to a user U using the second service the rewards registered for this user U (additional point multiplier) and the rewards that user U is expected to earn (expected points) for using the second service will be explained. The second service is, for example, online commerce, and the user U's usage of the second service is the purchase of goods.

[0077] When user U logs into the second service, which is online commerce, and indicates an intention to purchase an item, the display unit 24 reads the reward registration information T3 linked to user U's user ID from the reward data storage unit 25 and obtains the point multiplier to be added to user U's score (S401). When user U indicates an intention to purchase an item, it is when user U displays the product listing screen or when user U performs an operation to purchase an item and the shopping cart screen is displayed, etc.

[0078] The presentation unit 24 calculates the points that user U is expected to earn based on the point multiplier (+x) added to user U and the purchase amount (= item price × quantity purchased) (step S402). For example, if the point multiplier added to user U is +2x, the user's final point multiplier will be 1 + 2 = 3x. In this case, if the normal point accrual rate is 1%, the point accrual rate for user U will be the normal point accrual rate of 1% × 3 = 3%. In other words, 3% of the purchase amount of the item will be the points that user U is expected to earn. If multiple rewards (point multipliers added) are registered due to fulfilling different achievement conditions for the first service, the presentation unit 24 calculates the points to be earned by adding the sum of these point multipliers. The sum of the point multipliers is the multiplier without rewards (1x) plus the rewards (point multipliers added) for each achievement condition.

[0079] Next, the presentation unit 24 presents user U with at least one of the user U's point multiplier and the points expected to be earned (step S403).

[0080] Figure 13 shows an example of a reward presentation screen according to the first embodiment. The reward presentation screen D1 shown in Figure 13 is, for example, a product listing screen or a shopping cart screen. The reward presentation screen D1 includes at least one of point multiplier information D11 and expected points to be earned information D12. The point multiplier information D11 includes the total point multiplier of user U and a breakdown of the point multiplier. The breakdown of the point multiplier includes the reward granting conditions achieved in each first service and the reward (additional point multiplier). The expected points to be earned information D12 includes the expected points to be earned calculated in step S402. The expected points to be earned information D12 may also include the total point multiplier.

[0081] Furthermore, when user U actually purchases an item, the point program management server 2 will award points to user U, taking into account the total of the point multipliers calculated as described above. The process of calculating and awarding points while taking into account the point multipliers is the same as in the conventional technology, so a detailed explanation will be omitted.

[0082] (Regarding the presentation of the reward table) Figure 14 shows an example of a reward table presentation screen according to the first embodiment. In addition to the reward presentation screen D1 (Figure 13) for logged-in users U, the presentation unit 24 of the point program management server 2 may display a reward table presentation screen D2 for all users, including unlogged-in users, as shown in Figure 14. The reward table presentation screen D2 includes the contents of the reward table T2 for each service and reward table information D21 that identifies the rewards that the user can currently earn. For example, an example will be described in which an online commerce service server 4 receives a request for display information regarding the purchase of a product (item transaction) from a user terminal 5 and responds with display information including the reward table presentation screen D2. The display information regarding the item transaction is, for example, a listing screen for products that are normally eligible for point accrual. When the service server 4 receives a request to display the listing screen D2, it requests the reward table information D21 from the point program management server 2. The point program management server 2 (presentation unit 24) obtains the latest reward table information D21 and sends it to the requesting service server 4. The service server 4 adds the reward table information D21 received from the point program management server 2 to the display screen D2 and displays it on the user terminal 5. Alternatively, the point program management server 2 itself may accept the display request for the display screen D2 and display the display screen D2 with the reward table information D21 added to it on the user terminal 5.

[0083] The reward table information D21 includes information indicating the reward granting conditions and rewards for each service, and information D22 indicating the rewards currently available for each service. For example, suppose that the current revenue indicators for service A satisfy achievement condition A, and the revenue indicators for service B satisfy achievement condition B4. In this case, the point program management server 2 (display unit 24) creates reward table D information 21, as shown in Figure 14, which includes information D22 indicating that the reward "+1x" corresponding to achievement condition A for service A is currently available, and information D22 indicating that the reward "+1.5" corresponding to achievement condition B4 for service B is currently available. When the information D22 indicating the available rewards is displayed on the display screen D2, for example, it is displayed in a way that allows the user to identify it by highlighting the corresponding item on the reward table information D21. This highlighting can take any form as long as the user can identify which reward is available, and may include frames, marks, highlighting, or changes in text color. This allows users to easily find out what rewards are currently available for each service, whether rewards will increase with increased usage, and so on.

[0084] Furthermore, if a service acquires revenue metrics multiple times during the aggregation period, and the newly acquired revenue metrics meet different achievement conditions than the previous time, the point program management server 2 updates the reward table information D21 by changing the information D22 that indicates the rewards that can be earned for this service. For example, suppose service B newly meets achievement condition B5 with the latest revenue metrics. In this case, the point program management server 2 updates the reward table information D21 by setting the reward "+2x" corresponding to achievement condition B5 in the information D22 that indicates it is newly available. The point program management server 2 also notifies the user when the reward table information D21 is updated. Notification to the user may be done by updating the display of the reward table information D21 on the posting screen D2 and displaying a message, or by using email or the notification function of an application.

[0085] By presenting the reward table information D21 to all users, including non-logged-in users, it is possible to inform them that the more they use each service, the higher the rewards they can earn, thereby encouraging them to use the services and increasing their motivation to use them. Furthermore, by including information D22, which shows the rewards currently available, in the reward table information D21, it is possible to encourage users who want to increase their rewards even further to use more services. As a result, it becomes possible for each user to earn more rewards, and it is also possible to increase the revenue of each service.

[0086] While the example of displaying a product listing screen as the reward table display screen D2 has been described, this is not the only example. Other screens, such as the screen displayed when an operation related to product purchase (item transaction) (e.g., product selection, product order, etc.) is received from the user terminal 5 (e.g., the shopping cart screen, order confirmation screen, etc.), may also be used as the reward table display screen D2. Note that these product listing screens, shopping cart screens, order confirmation screens, etc., are all forms of display information related to item transactions.

[0087] (Effects and Benefits) As described above, the point program management server 2 according to this embodiment includes a revenue indicator acquisition unit 21 that acquires revenue indicators for a service based on the usage behavior of multiple users U, and a registration unit 22 that registers the revenue indicators for the service and the rewards for the users U of the service according to the conditions for achieving the revenue indicators for the service.

[0088] In this way, the points program management server 2, unlike conventional systems that award different rewards to individual users based on their individual usage behavior, can reflect the overall contribution of all users U who use the service in the incentives for each user U. This allows for setting appropriate rewards according to the overall contribution of all users U, thereby improving the sustainability of the service.

[0089] Furthermore, the service includes a first service and a second service, and the registration unit 22 registers rewards to user U who uses both the first service and the second service, in accordance with the achievement conditions of the revenue indicators for the first service.

[0090] In this way, the points program management server 2 can provide user U with an incentive to use both the first and second services. Furthermore, user U can earn more rewards by using both the first and second services.

[0091] Furthermore, the reward is a point multiplier that increases the points awarded based on the user's actions in using the second service.

[0092] In this way, the points program management server 2 can provide user U with an incentive to use both the first and second services and to increase their use of the second service. By using the first service and increasing their use of the second service, user U can earn more rewards.

[0093] Furthermore, the service has multiple achievement conditions for revenue metrics, and different rewards are set depending on each of these achievement conditions.

[0094] For example, the points program management server 2 may set achievement conditions such that the reward increases as the service's revenue indicator increases. In this way, all users U receive more rewards the more they use the service, thus improving the incentive for users U to use the service. Furthermore, the service provider P can appropriately adjust the rewards according to the service's revenue indicator. For example, if the revenue indicator has decreased compared to the previous aggregation period and only the minimum achievement conditions are met, the service provider P only needs to provide users U with a reward commensurate with these minimum conditions, thus only bearing the cost of rewards commensurate with the service's profitability. In other words, the burden of the points program becoming too large relative to the actual benefits of the service, as has been the case in the past, is suppressed, increasing the sustainability of the service and allowing users to continue using the service with peace of mind.

[0095] Furthermore, revenue metrics are one or a combination of the following: ARPU (Average Revenue Per User), ARPPU (Average Revenue Per Paying User), and ARPA (Average Revenue Per Account).

[0096] In this way, the points program management server 2 can determine the reward for each service usage behavior using an appropriate revenue indicator according to the nature of the service.

[0097] Furthermore, the service system 1 includes the point program management server 2 described above and a service server 4 that operates the service. The service server 4 has a revenue indicator calculation unit 42 that calculates a revenue indicator based on the usage behavior of user U in the service it operates, and a transmission unit 44 that transmits the calculated revenue indicator to the point program management server 2.

[0098] In this way, the service system 1 calculates revenue metrics at the service servers 4 that operate each service, and the point program management server 2 determines the rewards according to the revenue metrics. In this way, for example, the point program management server 2 does not need to obtain the history of user U's usage behavior for each service from the service servers 4, so traffic between servers can be kept to the bare minimum.

[0099] (Computer configuration) Figure 15 is a schematic block diagram showing the configuration of a computer according to the first embodiment. The computer 900 comprises a processor 901, main memory 902, auxiliary memory 903, and interface 904. The point program management server 2 and service server 4 described above are implemented in the computer 900, respectively. The operation of each processing unit described above is stored in the auxiliary memory 903 in the form of a program. The processor 901 reads the program from the auxiliary memory 903, expands it into the main memory 902, and executes the above processing according to the program. The processor 901 also allocates memory area in the main memory 902 to be used for the above processing according to the program.

[0100] The program may be for implementing a part of the functions to be performed by the computer 900. For example, the program may perform functions in combination with other programs already stored in the auxiliary storage device 903, or in combination with other programs implemented in other devices. In other embodiments, the computer may be equipped with a custom LSI (Large Scale Integrated Circuit) such as a PLD (Programmable Logic Device) in addition to, or in place of, the above configuration. Examples of PLDs include PAL (Programmable Array Logic), GAL (Generic Array Logic), CPLD (Complex Programmable Logic Device), FPGA (Field Programmable Gate Array), etc. In this case, some or all of the functions implemented by the processor may be implemented by the integrated circuit.

[0101] Examples of auxiliary storage devices 903 include HDDs (Hard Disk Drives), SSDs (Solid State Drives), magnetic disks, magneto-optical disks, CD-ROMs (Compact Disc Read Only Memory), DVD-ROMs (Digital Versatile Disc Read Only Memory), and semiconductor memory. The auxiliary storage device 903 may be an internal medium directly connected to the bus of the computer 900, or it may be an external medium (external storage device 910) connected to the computer 900 via an interface 904 or a communication line. Furthermore, if this program is distributed to the computer 900 via a communication line, the computer 900 that receives the distribution may expand the program into the main memory 902 and execute the above processing. In at least one embodiment, the auxiliary storage device 903 is a tangible storage medium that is not temporary.

[0102] Note that the above-mentioned servers (point program management server 2, user management server 3, and service server 4) may be virtual servers.

[0103] <Other Embodiments> Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to that described above, and various design changes are possible. In other embodiments, the order of the above-described processes may be changed as appropriate. Also, some processes may be executed in parallel.

[0104] <Note> The above-described embodiment can be understood, for example, as follows:

[0105] (Note 1) A point program management server comprising: a revenue indicator acquisition unit that acquires revenue indicators for a service based on the usage behavior of multiple users; and a registration unit that registers campaign rewards given to users of a service subject to a campaign, the campaign rewards corresponding to the revenue indicators of the service and the conditions for achieving the revenue indicators of the service.

[0106] (Note 2) The service includes a first service and a second service, and the registration unit registers campaign rewards to users who use both the first service and the second service, as described in Appendix 1.

[0107] (Note 3) The registration unit further registers regular points to users of the second service in accordance with their usage of the second service, regardless of the revenue indicators of the first service, and increases or decreases the points actually awarded to the user at regular intervals based on the campaign rewards and regular points registered to the user, as described in Appendix 2, for the point program management server.

[0108] (Note 4) The usage behavior of the second service is an item transaction, and the registration unit registers the normal points corresponding to the item transaction of the second service to the user of the second service, as described in Appendix 3, for the point program management server.

[0109] (Note 5) The aforementioned regular points increase or decrease according to the transaction amount of the aforementioned item transaction, as described in Appendix 4, on the point program management server.

[0110] (Note 6) The aforementioned campaign reward is a fixed point to be added to the aforementioned regular points, as specified in any one of the items 3 to 5 of the points program management server.

[0111] (Note 7) The campaign reward is a point multiplier that increases the regular points, as described in any one of the items in Appendix 3 to Appendix 5, for the point program management server.

[0112] (Note 8) The points program management server described in any one of the appendices 1 to 7, wherein the achievement conditions have multiple achievement conditions that become higher in level as the revenue indicator increases, and the campaign rewards are set such that the regular points increase significantly as the level of the achievement conditions increases.

[0113] (Note 9) A points program management server according to any one of the appendices 1 to 8, further comprising an adjustment unit that adjusts the user's reward according to the user's contribution to the service.

[0114] (Note 10) The revenue indicator is one or a combination of the following: an indicator representing revenue per user of the service, an indicator representing revenue per paying user of the service, and an indicator representing revenue per account of the service, as described in any one of the points program management servers described in any one of the appendices 1 to 9.

[0115] (Note 11) The point program management server as described in Appendix 10, wherein the service includes a first service and a second service, the first service being a mobile communication service, and the revenue indicator is an indicator representing sales based on at least one of data usage and call usage per user in the mobile communication service.

[0116] (Note 12) A point program management server according to any one of the appendices 1 to 11, further comprising a display unit that presents to the user reward table information, including rewards that can be registered according to the current revenue indicators of the service.

[0117] (Note 13) The aforementioned display unit is a points program management server as described in Appendix 12, which automatically updates the reward table information according to the revenue indicators of the service.

[0118] (Note 14) The presentation unit is a point program management server as described in Appendix 12 or 13, which updates the reward table information when the reward registered by the registration unit according to the revenue indicator of the service is updated.

[0119] (Note 15) The presentation unit is a point program management server as described in Appendix 12, which updates the rewards that can be registered for one of the services in the reward table information when the rewards registered by the registration unit according to the revenue indicator of one of the multiple services are updated.

[0120] (Note 16) A point program management server according to any one of the appendices 1 to 15, further comprising a display section that displays information indicating the rewards registered with the user and that the user can earn by using the service, on a service usage screen displayed when the user is logged into the service.

[0121] (Note 17) A service system comprising a point program management server described in any one of the appendices 1 to 16, and a service server that operates the service, wherein the service server includes a revenue indicator calculation unit that calculates a revenue indicator based on the user's usage behavior in the service it operates, and a transmission unit that transmits the calculated revenue indicator to the point program management server.

[0122] (Note 18) The service server includes a first service server that operates the first service and a second service server that operates the second service, wherein the second service server receives a request from the user's terminal for display information relating to item transactions, which are the user actions of the second service, obtains campaign rewards registered with the user from the point program management server according to the achievement conditions of the revenue indicators of the first service, and transmits the display information including the campaign rewards to the user terminal as a response to the request, as described in Appendix 17.

[0123] (Note 19) A point program management method comprising the steps of: obtaining a revenue indicator for a service based on the usage behavior of multiple users; and registering campaign rewards to users of a service that are subject to a campaign, the campaign rewards being given in accordance with the revenue indicator for the service and the conditions for achieving the revenue indicator for the service.

[0124] (Note 20) A program that causes a point program management device to perform the following steps: obtaining revenue metrics for a service based on the usage behavior of multiple users; and registering campaign rewards, which are given in accordance with the use of a service covered by a campaign, to users of the service, the campaign rewards corresponding to the revenue metrics of the service and the conditions for achieving the revenue metrics of the service. [Explanation of Symbols]

[0125] 1. Service System 2. Point Program Management Server 21. Revenue Indicator Acquisition Department 22 Registration Department 23 Adjustment part 24 Presentation section 25 Reward data storage unit 3. User Management Server 4. Service Server 41 Usage behavior acquisition department 42. Revenue Indicator Calculation Section 43. Contribution Determination Department 44 Transmitter 45 Usage behavior memory section 46 Revenue indicator storage unit 47 Contribution Memory Unit 5. User terminals T1 Contribution Table T2 Reward Table T3 Reward Registration Information P Service Provider U Service Users

Claims

1. A revenue indicator acquisition unit that acquires revenue indicators for a service based on the usage behavior of multiple users, A campaign reward is given in accordance with the use of the service covered by the campaign, and a registration unit registers the campaign reward to the user of the service according to the revenue indicator of the service and the conditions for achieving the revenue indicator of the service. A points program management server equipped with the following features.

2. The aforementioned service includes a first service and a second service, The registration unit registers campaign rewards to users who use both the first and second services, in accordance with the conditions for achieving the revenue indicators of the first service. The point program management server according to claim 1.

3. The aforementioned registration unit is Regardless of the revenue indicators for the first service, regular points corresponding to the usage behavior of the second service are further registered to the users of the second service. Based on the campaign rewards and regular points registered with the user, the points actually awarded to the user are increased or decreased at each period. The point program management server according to claim 2.

4. The usage behavior of the second service described above is item trading, The registration unit registers the regular points corresponding to the item transactions of the second service to the users of the second service. The point program management server according to claim 3.

5. The aforementioned regular points increase or decrease depending on the transaction amount of the aforementioned item transaction. The point program management server according to claim 4.

6. The aforementioned campaign reward is a fixed point that is added to the aforementioned regular points. The point program management server according to claim 3.

7. The aforementioned campaign reward is a point multiplier that increases the aforementioned regular points. The point program management server according to claim 3.

8. The aforementioned achievement conditions include multiple conditions that become higher as the profit indicator increases. The campaign rewards are set up such that the higher the level of the achievement conditions, the greater the increase in the normal points. A point program management server according to any one of claims 3 to 7.

9. The system further includes an adjustment unit that adjusts the campaign rewards of the user according to the user's contribution to the service. A point program management server according to any one of claims 1 to 7.

10. The aforementioned revenue indicator is one or a combination of the following: an indicator representing revenue per user of the service, an indicator representing revenue per paying user of the service, and an indicator representing revenue per account of the service. A point program management server according to any one of claims 1 to 7.

11. The aforementioned service includes a first service and a second service, The first service is a mobile communication service, The aforementioned revenue indicator is an indicator that represents revenue based on at least one of the data usage and call usage per user in the mobile communication service. The point program management server according to claim 10.

12. The system further includes a display unit that presents the user with reward table information, including campaign rewards that can be registered according to the current revenue metrics of the service. A point program management server according to any one of claims 1 to 7.

13. The display unit automatically updates the reward table information according to the revenue indicator of the service. The point program management server according to claim 12.

14. The display unit updates the reward table information when the campaign rewards registered by the registration unit according to the revenue indicators of the service are updated. The point program management server according to claim 12.

15. The display unit updates the rewards that can be registered for one of the services in the reward table information when the campaign rewards registered by the registration unit according to the revenue indicator of one of the multiple services are updated. The point program management server according to claim 14.

16. The service usage screen displayed when the user is logged into the service further includes a display section that shows information indicating campaign rewards registered for the user that the user can earn by using the service. A point program management server according to any one of claims 1 to 7.

17. A point program management server according to any one of claims 1 to 7, The service server that operates the service, A service system that includes, The aforementioned service server, A revenue indicator calculation unit calculates revenue indicators based on the user behavior in the service being operated, A transmission unit that transmits the calculated revenue indicator to the points program management server, A service system having the following features.

18. The service server includes a first service server that operates the first service and a second service server that operates the second service. The second service server receives a request from the user's terminal for display information regarding item transactions, which are a usage behavior of the second service. The second service server retrieves the campaign rewards registered with the user from the point program management server according to the achievement conditions of the revenue indicators for the first service, and transmits the display information, including the campaign rewards, to the user terminal as a response to the request. The service system according to claim 17.

19. Steps to obtain service revenue metrics based on the usage behavior of multiple users, A campaign reward is given in accordance with the use of the service covered by the campaign, and the step of registering the campaign reward to the user of the service according to the revenue indicator of the service and the conditions for achieving the revenue indicator of the service, A point program management method having

20. Steps to obtain service revenue metrics based on the usage behavior of multiple users, A campaign reward is given in accordance with the use of the service covered by the campaign, and the step of registering the campaign reward to the user of the service according to the revenue indicator of the service and the conditions for achieving the revenue indicator of the service, A program that causes the point program management device to execute.

Images