JP7473922B2 - PROGRAM, INFORMATION PROCESSING APPARATUS AND INFORMATION PROCESSING METHOD - Google Patents

Description

This disclosure relates to a program, an information processing device, and an information processing method.

As a measure to acquire trial customers for new products, etc., there is a technology that allows customers to apply for campaigns or provide incentives on the condition that they post and spread information about advertisements. As a measure to acquire channels with customers for existing products, there is a technology that allows customer users to apply for campaigns by following a company's SNS (Social Network Service) account, or by posting a specific keyword with a hashtag. There is also a technology that links different services with a common ID (Patent Document 1).

Patent Document 1 discloses a technology in which a first service providing unit transmits to a user terminal a first individual ID for identifying a user in a first service, which is associated with a common ID included in an ID information provision request, and a second service providing unit receives from the user terminal a service ID for identifying the first service, the first individual ID, and a common ID, and transmits to the user terminal the service ID and first individual ID received together with the common ID associated with a second individual ID for identifying a user in a second service, which is included in an ID information acquisition request.

International Publication No. 2012/004916

There are SNSs (e.g., SNSs such as Twitter (registered trademark)) in which an unspecified number of users create accounts and can view each other's posts without having to form specific relationships with other users, such as by becoming friends or following them. In such SNSs, the posts of various users, centering on the posts of other users whom each user follows, can be arranged and viewed based on the posting date and time of each post and other users' reactions to each post (engagement, such as the number of "likes" and the number of times the details of the post were displayed) (also known as a "timeline" or "feed").

In such SNS, posts from not only users the user follows but also users who the user does not follow (e.g., corporate accounts) may appear on the user's timeline, which is expected to have the effect of spreading the posts.

The present disclosure has been made to solve the above problem, and its purpose is to provide a program, information processing device, and information processing method that can increase the diffusion effect of a campaign that spans multiple services.

According to one embodiment, a program for operating a computer having a processor is provided. The program causes the processor to execute a first step of posting an advertiser's campaign using the advertiser's account in a first service in which only one account is available on a user terminal owned by a user for one user's authentication information; a second step of detecting an input operation made by a user using the first service in response to the posting of the campaign; a third step of providing the user with the posted content including first information that can identify the user's account in the first service in a second service in which one user's authentication information can be used by switching between one or more accounts on a user terminal owned by the user, if the input operation is detected in the second step; and a fourth step of detecting that the user has posted in the second service using his/her own account based on the posted content, identifying the account of the user who posted the content including the first information based on the detection result, and granting a campaign-related benefit to the account.

According to the present disclosure, when a campaign is implemented across multiple services, the spreading effect of the campaign can be increased.

1 is a diagram showing an overview of a campaign management system according to a first embodiment. 1 is a block diagram showing a hardware configuration of a campaign operation system according to a first embodiment. 1 is a block diagram showing a hardware configuration of a campaign management device according to a first embodiment. FIG. 2 is a block diagram showing a hardware configuration of a user terminal according to the first embodiment. FIG. 2 is a diagram illustrating a functional configuration of a campaign management device according to the first embodiment. FIG. 2 is a diagram illustrating a functional configuration of a user terminal according to the first embodiment. 4 is a diagram showing a data structure of a campaign participation history DB stored in the campaign management device according to the first embodiment. FIG. 3 is a diagram showing a data structure of a user information DB stored in the campaign management device according to the first embodiment. FIG. 3 is a diagram showing a data structure of an advertiser information DB stored in the campaign management device according to the first embodiment. FIG. 4 is a diagram showing a data structure of a campaign implementation DB stored in the campaign management device according to the first embodiment. FIG. 4 is a diagram showing a data structure of a campaign result DB stored in the campaign management device according to the first embodiment. FIG. FIG. 2 is a sequence diagram for explaining the operation of the campaign management system according to the first embodiment. 13 is a sequence diagram for explaining the operation of the campaign management system according to the first embodiment, showing a continuation of the operation shown in FIG. 12 . 11 is a flowchart for explaining a posting screen generating operation in the campaign management system according to the first embodiment. 11 is a flowchart for explaining a post search operation in the campaign management system according to the first embodiment. FIG. 2 is a diagram showing an example of a post display screen displayed on a user terminal in the campaign management system according to the first embodiment. FIG. 2 is a diagram showing an example of a campaign screen displayed on a user terminal in the campaign management system according to the first embodiment. 1 is a diagram showing an example of an application screen displayed on a user terminal in the campaign management system according to the first embodiment; FIG. FIG. 2 is a diagram showing an example of a posting screen displayed on a user terminal in the campaign management system according to the first embodiment. FIG. 2 is a diagram showing an example of a post display screen displayed on a user terminal in the campaign management system according to the first embodiment. 13 is a diagram showing an example of a lottery result screen displayed on a user terminal in the campaign management system according to the first embodiment. FIG. FIG. 11 is a diagram showing an overview of a campaign management system according to a second embodiment. FIG. 11 is a sequence diagram illustrating the operation of the campaign management system according to the second embodiment. FIG. 24 is a sequence diagram for explaining the operation of the campaign management system according to the second embodiment, showing a continuation of the operation shown in FIG. 23 . FIG. 11 is a diagram showing an example of an application screen displayed on a user terminal in the campaign management system according to the second embodiment. FIG. 11 is a diagram showing an example of an authentication screen displayed on a user terminal in the campaign management system according to the second embodiment. FIG. 11 is a diagram showing an example of a post display screen displayed on a user terminal in the campaign management system according to the second embodiment. FIG. 13 is a diagram showing an example of a screen displayed on a user terminal in a campaign management system according to a modified example. FIG. 13 is a diagram showing an example of a screen displayed on a user terminal in a campaign management system according to a modified example. FIG. 13 is a diagram showing an example of a screen displayed on a user terminal in a campaign management system according to a modified example. FIG. 13 is a diagram showing an example of a screen displayed on a user terminal in a campaign management system according to a modified example. FIG. 13 is a diagram showing an example of a screen displayed on a user terminal in a campaign management system according to a modified example. FIG. 13 is a diagram showing an example of a screen displayed on a user terminal in a campaign management system according to a modified example. FIG. 13 is a diagram showing an example of a screen displayed on a user terminal in a campaign management system according to a modified example. FIG. 13 is a diagram showing an example of a screen displayed on a user terminal in a campaign management system according to a modified example. FIG. 13 is a diagram showing an example of a screen displayed on a user terminal in a campaign management system according to a modified example.

Embodiments of the present disclosure will be described below with reference to the drawings. In all figures describing the embodiments, common components are given the same reference numerals, and repeated explanations will be omitted. Note that the following embodiments do not unduly limit the contents of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are necessarily essential components of the present disclosure. Furthermore, each figure is a schematic diagram, and is not necessarily a precise illustration.

In the following description, a "processor" refers to one or more processors. The at least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may be another type of processor such as a GPU (Graphics Processing Unit). The at least one processor may be a single-core or multi-core.

In addition, at least one processor may be a processor in the broad sense, such as a hardware circuit (e.g., an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit)) that performs some or all of the processing.

In the following explanation, information that produces an output for an input may be described using expressions such as "xxx table," but this information may be data of any structure, or may be a learning model such as a neural network that produces an output for an input. Therefore, a "xxx table" may be called "xxx information."

In addition, in the following description, the configuration of each table is an example, and one table may be divided into two or more tables, or all or part of two or more tables may be one table.

In the following explanation, the processing may be described with the "program" as the subject, but since the program is executed by a processor to perform a predetermined process using a memory unit and/or an interface unit as appropriate, the subject of the processing may be the processor (or a device such as a controller having the processor).

The program may be installed on a device such as a computer, or may be, for example, on a program distribution server or a computer-readable (e.g., non-transitory) recording medium. In addition, in the following description, two or more programs may be realized as one program, and one program may be realized as two or more programs.

In addition, in the following description, identification numbers are used as identification information for various objects, but other types of identification information (e.g., identifiers including letters or codes) may also be used.

In the following description, when elements of the same type are described without distinction, reference signs (or common signs among reference signs) are used, and when elements of the same type are described with distinction, the identification numbers (or reference signs) of the elements are used.

In addition, in the following explanation, the control lines and information lines are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. All components may be connected to each other.

<Summary of the Disclosure>
In the present disclosure, a user performs some input operation based on a campaign posted by an advertiser in a first service, and this input operation is detected to prompt the user to post through a second service, thereby further spreading the campaign. The first service is a service that can be used with only one account on a user terminal owned by a user for authentication information of one user. For example, the first service may include the following.
A messenger application that includes business and consumer accounts and functions as a social networking service (e.g., LINE (registered trademark))
・Payment applications that allow prepaid or postpaid payments (point services, payment services such as PayPay (registered trademark))

For example, in a messenger application, only one account may be available per phone number.

When a user accesses the first service using authentication information related to an account and is authenticated by the authentication information, the user can make posts as the account related to the user. Posts here can include not only text information but also image information, URLs (Uniform Resource Locators) for accessing information on the Internet including web pages stored on a server, and the like.

In the first service, a specific account can view posts from accounts that have a specific relationship with the account (sometimes called a friend relationship). However, in the first service, a specific account can only view posts from friends and present these posts to other friends using a URL or the like, and cannot post from a friend account in its original form to other friends. Also, friend relationships are one-to-one. Therefore, even if an account is in a friend relationship, it is not possible to know which accounts it is friends with.

The second service is a service that can be used by switching between one or more accounts on the user terminal owned by a user for authentication information of one user. The second service can also be a service that allows users who use the second service to view each other's posted content. For example, the second service is a social networking service such as Twitter (registered trademark).

In the second service, a user accesses the second service using authentication information related to the account, and once authenticated by the authentication information, can make posts as the account related to the user. Posts here can include not only text information but also image information, URLs (Uniform Resource Locators) for accessing information on the Internet, including web pages stored on a server, and the like.

The second service allows a particular account to view posts from accounts that have a particular relationship with it (sometimes called a following/follower relationship).

Here, "following" refers to, for example, a specified relationship being set in which one account (account "A") follows the other account (account "B") by one account (account "A") specifying the other account (account "B") and accepting an input operation from the other user to set a specified relationship. In this case, the other account (account "B") becomes a follower of the other account. The one account (account "A") can display the posts of the other account (user "B") that it is following on a timeline or the like. Timeline, feeds Posts from accounts that are followed may be more likely to be displayed on the timeline (post display screen) or the like.

A following/follower relationship can exist with multiple accounts. Therefore, an account's timeline may display posts including those from multiple accounts that it follows.

In the second service, an account can post a post from an account in a following/following relationship with its followers in the same form as the post. This is called a repost. Also, in the second service, an account can identify a post from an account in a following/following relationship with its followers and reply to the account in the following/following relationship with its followers (sometimes called a mention). Only this reply can be identified and displayed on the timeline, etc. of the account that received the reply.

Furthermore, in the second service, messages can be sent and received between specific paired accounts using a message sending and receiving method (direct messages) that is not disclosed to other accounts.

First Embodiment
Overview of the First Embodiment
With reference to FIG. 1, an overview of a campaign management system to which a campaign management device, which is an information processing device according to a first embodiment, is applied will be described.

The campaign management system 1 according to the first embodiment includes a campaign management device 10, which is an information processing device, a user terminal 20, a first server 30, and a second server 40.

The campaign management device 10 is a device for executing processes such as generating and displaying a posting screen in the first service that allows a user who is an applicant for an advertiser's campaign to post a post including campaign information in the second service, allowing the user to apply for the campaign by posting on this posting screen, and providing a special benefit related to the campaign to the user who posted the post including campaign information in the second service.

The campaign management device 10 accepts settings from an advertiser (not shown in Fig. 1) that permit posting to the advertiser's account in the first service, viewing messages, etc. As a result, the campaign management device 10 can perform the following in the first service.
Implementing and managing a campaign in the first service as an account of the advertiser. Specifically, posting including information related to the campaign can be performed in the first service as an account of the advertiser. In addition, a screen including campaign information can be prepared in the first service (screen data can be uploaded to the first server 30), and this screen can be made viewable by users of the first service who have an account that is in a friend relationship with the advertiser.
Sending a message to a user in the first service as an account of the advertiser Obtaining information (such as an ID for identifying an account) regarding an account that has performed a specific operation input to a post related to the campaign

Furthermore, the campaign management device 10 can perform the following in the second service. At this time, it is preferable that the campaign management device 10 accepts a setting from the advertiser that allows posting, etc., to the advertiser's account in the second service.
Allowing a user who has an account for the second service to post to the second service using the user's account. Preferably, the format (including the interface such as a screen) of posts to the second service using the user's account is substantially the same as that of posts normally made by the user using the user's account to the second service.
・ Viewing information posted, replied to, or reposted by a user, and obtaining information related to the account of the user who made the post (such as an ID for identifying the account) ・ Sending and receiving messages using a message sending and receiving method (direct messages) that are sent and received between an advertiser's account and a user and are viewable by the advertiser's account and the user, but are not made public to other users.
Acquiring analysis results such as the number of times a post was viewed on a user's timeline, engagement with the post (the number of times users of the second service responded to the post, the number of times the profile of the advertiser's account was viewed, the number of likes given to the post, the number of times an operation was performed to view the details of the post), etc. An entity providing the second service may provide each account of the second service with analysis results such as the number of views and engagement with the posts made by each account.
When a user sends a message, the text sentences that make up the message are analyzed using language processing or other methods according to the content of the message, and whether the message contains a specific keyword (for example, a keyword related to a campaign) is determined.

The campaign management device 10 aggregates information about campaign posts in these second services for the advertiser, and presents the analysis results to the advertiser, etc.

The user terminal 20 is a terminal owned by a user, and is, for example, a portable and communicable information processing terminal such as a smartphone or a tablet terminal. The user who owns the user terminal 20 has an account for each of the first service and the second service. In addition, the account of the user who owns the user terminal 20 is in a friend relationship with the advertiser's account at least in the first service, and preferably follows the advertiser's account in the second service as well.

The first server 30 is a server that operates a first service, and the second server 40 is a server that operates a second service.

With reference to Figure 1, we will explain an overview of the operation of the campaign management system 1, which is the first embodiment.

First, the campaign management device 10 posts information about the campaign to the first server 30 (1). As already explained, this posting is made under the account of the advertiser. Posting information about the campaign includes uploading screen data including information about the campaign to the first server 30 (hereinafter, the screen displayed by this data is referred to as "campaign screen A").

As an example, if the first service is LINE (registered trademark), LINE provides a platform called LIFF (LINE Front-end Framework) as a web app (LIFF app) to users who use LINE commercially. By using this LIFF app, the user ID of the first service (LINE) and other information can be obtained. In addition, a LIFF browser is provided as a browser dedicated to LIFF apps, and when a LIFF URL is opened on the LINE app screen, the LIFF app opens in the LIFF browser. This LIFF browser runs on the LINE app, and the LIFF app can access user data (such as LINE ID) without logging in. By launching the LIFF app from an external browser via a URL and performing the login process (LIFF authentication), the user's profile (such as LINE ID) can be obtained.

Therefore, when the first service is LINE, the campaign screen A is a LIFF app screen displayed on the LIFF browser, and the campaign management device 10 uploads the LIFF app screen to the first server 30.

When a user who owns the user terminal 20 is viewing a posting screen of the first service provided by the first server 30, the user views a campaign post made by an advertiser's account and becomes interested in the campaign. The user then performs a specific operation input on the campaign post made by the advertiser's account via the user terminal 20 (usually clicking a button or the like displayed on the campaign post).

In response to this operational input, the first server 30 displays the uploaded campaign screen A on the display screen of the user terminal 20. As described above, if the first service is LINE, the first server 30 displays the campaign screen A on the display screen of the user terminal 20 using the LIFF browser. The campaign screen A has a button B for applying to the campaign, and the user who owns the user terminal 20 applies to the campaign by performing a specific operational input on this button B (usually by clicking button B displayed on the campaign screen A, etc.) (2).

When a user performs a specific operation input on button B on campaign screen A, the fact that the operation input has been performed and information regarding the account of the first service of the user who performed the operation input (at least an ID for identifying the account) are transmitted to the campaign management device 10 (3).

When the campaign management device 10 receives information from the first server 30, it transmits to the user terminal 20 a posting screen C for the user to post to the second service (4). This posting screen C contains predetermined posting content, and the campaign management device 10 generates this posting content. The predetermined posting content includes information about the campaign (a URL for transitioning to a homepage screen containing content related to the included campaign) and information that can identify which campaign it is (a hashtag, as an example). In particular, the URL includes information linked to an ID that can identify the user's account for the first service.

The user who receives the posting screen 200 uses this posting screen C to post to the second service (second server 40) (5). This completes the application procedure for the campaign by the user.

Then, the campaign management device 10 searches the posts on the second server 40 (second service) and searches for posts related to campaign applications (6). This post search may be performed based on information that is included in the post screen C and that can identify the campaign. The second server 40 transmits the search results to the campaign management device 10 (7). The campaign management device 10 can measure the effectiveness of the campaign based on the search results.

<Basic configuration of campaign management system 1>
As already explained using Fig. 1, the campaign management system 1 of this embodiment has a campaign management device 10, a user terminal 20, a first server 30, and a second server 40, which are connected via a network N, as shown in Fig. 2. The hardware configuration of the campaign management device 10 is shown in Fig. 3, and the hardware configuration of the user terminal 20 is shown in Fig. 4. The campaign management device 10, the user terminal 20, the first server 30, and the second server 40 are each composed of an information processing device.

The information processing device is configured by a computer having an arithmetic unit and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. Note that for each of the campaign management device 10, the user terminal 20, the first server 30, and the second server 40, explanations that overlap with the basic hardware configuration and basic functional configuration of the computer described later will not be repeated.

The network N is composed of the Internet, LAN, various mobile communication systems constructed by wireless base stations, etc. For example, the network includes 3G, 4G, 5G mobile communication systems, LTE (Long Term Evolution), wireless networks that can connect to the Internet via a specified access point (e.g., Wi-Fi (registered trademark)), etc. In the case of a wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), etc. In the case of a wired connection, the network also includes those directly connected by a USB (Universal Serial Bus) cable, etc.

The configuration and operation of each device are explained below.

<Hardware Configuration of Campaign Management Device 10>
3 is a block diagram showing the basic hardware configuration of the campaign management device 10. The campaign management device 10 has at least a processor 101, a main memory device 102, an auxiliary memory device 103, a communication IF (Interface) 104, an input IF 105, and an output IF 106. These are electrically connected to each other by a communication bus 107. In addition, an input device 110 is connected to the campaign management device 10 via the input IF 105, and an output device 111 is connected to the campaign management device 10 via the output IF 106.

The processor 101 is hardware for executing a set of instructions written in a program. The processor 101 is composed of an arithmetic unit, registers, peripheral circuits, etc.

The main memory device 102 is used to temporarily store programs and data processed by the programs. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

The auxiliary storage device 103 is a storage device for saving data and programs. For example, it is a flash memory, a solid state drive (SSD), a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, etc.

The communication IF 104 is an interface for inputting and outputting signals for communicating with other computers over a network using wired or wireless communication standards.

The input IF 105 functions as an interface with the input device 110 for accepting input operations from the operator of the campaign management device 10. The output IF 106 functions as an interface with the output device 111 for presenting information to the operator. The input device 110 is an input device (e.g., a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.) for accepting input operations from the operator. The output device 111 is an output device (a display, a speaker, etc.) for presenting information to the operator.

The campaign management device 10 can be virtually realized by distributing all or part of each hardware configuration among multiple computers and connecting them via a network. In this way, the campaign management device 10 is a concept that includes not only a computer housed in a single housing or case, but also a virtualized computer system.
<Hardware Configuration of User Terminal 20>

Figure 4 is a block diagram showing the basic hardware configuration of the user terminal 20. The user terminal 20 is a device operated by each user. The user terminal 20 is realized by a mobile terminal such as a smartphone or tablet compatible with a mobile communication system. In addition, the user terminal 20 may be, for example, a stationary PC (Personal Computer) or a laptop PC. The user terminal 20 has at least a processor 201, a main memory device 202, an auxiliary memory device 203, a communication IF (Interface) 204, an input device 205, and an output device 206.

The user terminal 20 is connected to the campaign management device 10, the first server 30, the second server 40, etc., so as to be able to communicate with them via the network N shown in FIG. 2. The user terminal 20 is connected to the network N by communicating with communication devices such as a wireless base station compatible with communication standards such as 5G and LTE (Long Term Evolution), and a wireless LAN router compatible with wireless LAN (Local Area Network) standards such as IEEE (Institute of Electrical and Electronics Engineers) 802.11.

The input device 205 is an input device (e.g., a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.) for receiving input operations from a user. The output device 206 is an output device (a display, a speaker, etc.) for presenting information to the user.

<Functional configuration of the campaign management device 10>
5 shows a functional configuration realized by the hardware configuration of the campaign management device 10. The campaign management device 10 includes a memory unit 120 and a control unit 130. The memory unit 120 is configured from the main memory unit 102 and the auxiliary memory unit 103 of the campaign management device 10, and the control unit 130 is mainly configured from the processor 101 of the campaign management device 10.

<Configuration of the storage unit 310 of the campaign management device 10>
The storage unit 120 of the campaign management device 10 has a campaign participation history DB (DataBase) 122 , a user information DB 123 , an advertiser information DB 124 , campaign screen data 125 , posting screen data 126 , a campaign implementation DB 127 , and a campaign performance DB 128 .

Of these campaign participation history DB122 etc., all but campaign screen data 125 and post screen data 126 are databases. The database referred to here refers to a relational database, which is used to manage data sets called tables in tabular format structurally defined by rows and columns, by associating them with each other. In a database, a table is called a table, a column in a table is called a column, and a row in a table is called a record. In a relational database, relationships between tables can be set and associated.

Typically, each table has a column that serves as a primary key to uniquely identify a record, but setting a primary key to a column is not essential. The control unit 130 can cause the processor 101 to add, delete, or update records in a specific table stored in the storage unit 120 according to various programs.

Figure 7 is a diagram showing the data structure of the campaign participation history DB 122. The campaign participation history DB 122 is a database that manages the participation history of users who applied to campaigns managed and administered by the campaign management device 10.

Campaign participation history DB122 is a table that has a campaign ID as a primary key to identify each campaign, and columns for user ID, lottery results, date and time, and bonus awards.

"Campaign ID" is information for identifying the campaign. "User ID" is information for identifying the user who applied for the campaign. "Lottery result" is information indicating the result of a lottery to determine whether or not a bonus will be awarded for the application for the campaign. "Date and time" is the date and time when the user applied for the campaign. "Bonus provided" is information indicating whether or not the winning user was provided with a bonus.

Figure 8 shows the data structure of user information DB 123. User information DB 123 is a database that manages information on users who have applied to campaigns managed and administered by the campaign management device 10.

User information DB123 is a table that has a user ID as a primary key for identifying individual users, and columns for the account ID of the first service, the account ID of the second service, a specific ID, and a relationship with the advertiser.

"User ID" is information for identifying a user. "First service account ID" is the user's account ID in the first service. If there are multiple first services, the user information DB 123 can prepare multiple items of "first service account ID" for each first service. "Second service account ID" is the user's account ID in the second service. "Second service account ID" is configured to hold multiple account IDs. If there are multiple second services, the user information DB 123 can prepare multiple items of "second service account ID" for each second service. "Specific ID" is an ID uniquely generated by the posting screen generation unit 135, which will be described later, based on the account ID of the first service. "Relationship with advertiser" is information indicating the relationship between the advertiser's account in the first service and the user's account in the first service.

Figure 9 is a diagram showing the data structure of the advertiser information DB 124. The advertiser information DB 124 is a database that manages information on advertisers of campaigns managed and operated by the campaign management device 10.

The advertiser information DB124 is a table having an advertiser ID as a primary key for identifying individual advertisers, and columns for an account ID for the first service and a password for the first service.

"Advertiser ID" is information for identifying the advertiser. "First service account ID" is the account ID for the advertiser in the first service. "First service password" is the password for the advertiser in the first service.

Figure 10 is a diagram showing the data structure of the campaign implementation DB 127. The campaign implementation DB 127 is a database that manages the implementation history of campaigns operated and managed by the campaign management device 10.

Campaign implementation DB127 is a table that has a campaign ID as a primary key for identifying each campaign, and columns for start date/time, end date/time, and hashtag.

"Campaign ID" is information for identifying a campaign. "Start date and time" is the date and time when the campaign identified by the campaign ID started. "End date and time" is the date and time when the campaign identified by the campaign ID ended. "Hashtag" is a hashtag linked to the campaign identified by the campaign ID. It is preferable that this hashtag be unique to each individual campaign. In other words, it is preferable that the same hashtag is not used in multiple campaigns. This "hashtag" information is included in the post content on the post screen C provided to the user.

Figure 11 is a diagram showing the data structure of the campaign performance DB 128. The campaign performance DB 128 is a database that manages the performance of campaigns operated and managed by the campaign management device 10.

Campaign performance DB128 is a table with a campaign ID as a primary key for identifying each campaign, and columns for the total number of applications, number of posts on the second service, number of reposts, number of mentions, number of winners, and number of winners via the second service.

"Campaign ID" is information for identifying a campaign. "Total number of applications" is the total number of applications to a campaign identified by the campaign ID. "Number of posts to the second service" is the total number of posts posted by a user to the second service via the campaign management system 1 (more precisely, posts posted by a user to the second service using the posting screen C transmitted from the campaign management device 10). "Number of reposts" is the total number of posts posted by a user to the second service via the campaign management system 1 that have been reposted on the second service. "Number of mentions" is the total number of posts posted by a user to the second service via the campaign management system 1 that have been mentioned on the second service. "Number of winners" is the total number of winners of a campaign identified by the campaign ID. "Number of winners via the second service" is the total number of winners who are selected via the second service, i.e., on the condition that the user has posted on the second service, out of the number of winners of a campaign identified by the campaign ID. The "number of winners" and "number of winners via the second service" are determined in advance by the advertiser or the administrator of the campaign management device 10 and are registered in these columns of the campaign performance DB 128.

The campaign screen data 125 is data for displaying campaign screen A (see FIG. 1) on the user terminal 20 when the user views the posting screen of the advertiser account of the first service via the user terminal 20. This campaign screen data 125 is uploaded to the first server 30 in advance. FIG. 18 shows an example of campaign screen A displayed on the user terminal 20 based on the campaign screen data 125. Details will be described later.

The posting screen data 126 is data for displaying a posting screen C (see FIG. 1) sent to the user terminal 20 when a user performs an operation input on button B (see FIG. 1) on the campaign screen A via the user terminal 20. An example of the posting screen C displayed on the user terminal 20 based on the posting screen data 126 is shown in FIG. 19. Details will be described later.
<Configuration of the control unit 130 of the campaign management device 10>

The control unit 130 of the campaign management device 10 includes a reception control unit 131, a transmission control unit 132, a first posting unit 133, a second posting unit 134, a posting screen generation unit 135, a posting content search unit 136, an identification unit 137, a lottery unit 138, a provision unit 139, and an analysis unit 140. The control unit 130 executes an application program 121 stored in the memory unit 120 to realize these functional units such as the reception control unit 131.

The reception control unit 131 controls the process in which the campaign management device 10 receives signals from external devices according to a communication protocol.

The transmission control unit 132 controls the process in which the campaign management device 10 transmits signals to external devices according to a communication protocol.

The first posting unit 133 posts the advertiser's campaign using the advertiser's account in the first service in which only one account can be used on a user terminal owned by a user for one user's authentication information.

Specifically, the first posting unit 133 first logs in to the first server 30 at any timing using the account ID and password for the first service stored in the advertiser information DB 124. This allows the campaign management device 10 (first posting unit 133) to make various posts, including posts for the advertiser's campaign, in the first service using the advertiser's account. The arbitrary timing is, for example, before the start of the campaign advertisement, at the start, or at a specified timing within the campaign period.

Next, the first posting unit 133 posts an article about the campaign under the name of the logged-in account, that is, under the advertiser's account. The posted article includes information such as the campaign title, period, and benefits. In parallel, the first posting unit 133 uploads the campaign screen data 125 to the first server 30. Note that the campaign screen data 125 may be uploaded to a server other than the first server 30. However, it is preferable to upload the data to a server where the user of the user terminal 20 is unlikely to notice that they have transitioned to another service when transitioning from the first service to the campaign screen A (e.g., where the screen transition is smooth).

A posted article relating to a campaign is configured so that the user can view the posted article on the user terminal 20 and use the posted article as an opportunity to perform a specified operational input in order to apply for the campaign. One example of such a configuration is a configuration in which a clickable button or menu is attached to the posted article, and a screen transition occurs when the user clicks on this button or the like on the user terminal 20. Figure 17 shows an example of a posting screen in which a posted article posted by the first posting unit 133 is displayed on the screen of the user terminal 20.

There are various procedures for applying to a campaign, but the campaign management device 10 of this embodiment is configured to transition to campaign screen A when a user performs a specified operational input in response to a post of an article about the campaign by the first posting unit 133 to apply for the campaign.

However, campaigns managed and administered by the campaign management device 10 of this embodiment may be implemented simultaneously in parallel, with campaigns that go through campaign screen A and those that do not go through campaign screen A. In the following description, it is assumed that the campaign management device 10 implements campaign applications that go through campaign screen A and campaign applications that do not go through campaign screen A simultaneously in parallel during a campaign period. An application form that does not go through campaign screen A may be one in which, when a user performs a predetermined operation input to apply for a campaign in response to a posting of an article about the campaign by the first posting unit 133, the screen transitions to an input screen for user information (such as account information for the second service, address and name are not essential), and the campaign application ends when the user inputs the user information.

An example of the campaign screen A displayed on the user terminal 20 has already been shown in FIG. 18. The campaign screen A has a button B for applying for the campaign, and a user who wishes to apply for the campaign moves to the application procedure by performing a predetermined operation input on this button B (e.g., clicking button B).

When a specific operation input is made to the campaign application button B provided on the campaign screen A, the first posting unit 133 obtains from the first server 30 the account information (mainly the account ID) for the first service of the user who made the specific operation input, and stores this account information in the user information DB 123.

The above-described operation of the first posting unit 133 may be realized by an API (Application Platform Interface) provided by the first service (first server 30).

The second posting unit 134 provides an environment for a user to post based on a posting screen C generated by the posting screen generating unit 135 in a second service in which the user can use one or more accounts by switching between them on the user terminal 20 owned by the user based on the authentication information of the user. This posting screen C includes posting content including first information that can identify the user's account in the first service and third information for identifying the campaign.

Here, the second posting unit 134 is primarily intended to provide the user with an environment for posting on the second service, and posting on the second service is made through the user's account. However, the second posting unit 134 (and the post content search unit 136 described below) may log in to the second service using the advertiser's account information.

When a predetermined operation input is performed on the campaign entry button provided on the campaign screen A, the second posting unit 134 sends posting screen data 126 for the user to post to the second service to the user terminal 20. An example of the posting screen C has already been shown in FIG. 19.

When the second posting unit 134 sends the posting screen data 126 to the user terminal 20, it includes the posting content generated by the posting screen generation unit 135. The operation of the posting screen generation unit 135 will be described in detail later.

Further, the second posting unit 134 can perform operations that are normally performed by a user having an account in the second service, and further provides the posted content search unit 136 with an environment in which various operations performed in the second service by the posted content search unit 136 and the providing unit 139, which will be described later, can be performed. Generally, the following operations can be given as examples of operations normally performed by a user having an account in the second service.
- On the second service, make a post using an account for the second service and reply to a post from another account. - On the second service, repost or repost by quoting a post from another account using an account for the second service.
- (preferably as an account of the advertiser's second service) send a specified message (a message sent and received between the account of the user applying for the campaign and the account of the advertiser, which is not expected to be viewed by other users, such as a direct message) to other accounts - In the second service, as an account of the second service, rate posted articles (good, bad, liked, etc.). The ratings of the posted articles (for example, the number of "good" ratings, etc.) can be held for each posted article by the second server 40, etc.

The above-described operation of the second posting unit 134 may be realized by an API (Application Platform Interface) provided by the second service (second server 40).

When a specific operational input is made to a button for applying to the campaign provided on the campaign screen A, the posting screen generation unit 135 generates posting content to be included in the posting screen C, generates posting screen data 126 including the posting content, and provides it to the second posting unit 134.

Here, the posting screen generating unit 135 includes in the posting content first information that can identify the user's account in the first service, that is, information that can identify the account information (mainly the account ID) in the first service of the user who performed a specified operational input on the campaign application button provided on the campaign screen A, and also includes third information that can identify an individual campaign in the posting content.

There are no particular limitations on the first information as long as it is information that can identify the user's account information in the first service, but in the campaign management device 10 of this embodiment, the posting screen generation unit 135 uses a unique ID generated based on the user's account ID in the first service and linked to this account ID as the first information. The posting screen generation unit 135 adds this ID to the end of the URL of the campaign promotion site managed by the advertiser (or the operator of the campaign management device 10) and includes it in the posting content. In addition, the posting screen generation unit 135 stores the generated unique ID in the "specific ID" of the user information DB 123.

The third information is also not particularly limited as long as it is information that can identify an individual campaign, but in the campaign management device 10 of this embodiment, the posting screen generation unit 135 uses a hashtag that corresponds to the ID of each campaign among the hashtags stored in the campaign implementation DB 127. The posting screen generation unit 135 may create the hashtag when the first application is made for the campaign, or may create the hashtag in advance so that it is unique to each campaign (so that there are no duplicates).

It is preferable to avoid hashtags that are expected to be generally used by users of the second service. This makes it possible to eliminate as many posts as possible other than those related to campaign applications (which may become noise during analysis by the analysis unit 140) in the post search and analysis work by the post content search unit 136, the identification unit 137, and the analysis unit 140 described below. For this reason, the post screen generation unit 135 can use as hashtags irregular character strings other than characters whose meaning the user can guess, or characters whose meaning the user can guess plus an irregular character string unique to each campaign. The post screen generation unit 135 includes this hashtag in the post content.

In addition, when a specified operational input is made to the campaign entry button B provided on the campaign screen A, the posting screen generation unit 135 not only generates the posting content to be included in the posting screen C immediately, but also generates the posting content to be included in the posting screen C on the condition that the user has input specified information in the first service, and generates posting screen data 126 including this posting content and provides it to the second posting unit 134.

As an example of such a technique, a quiz may be included in a post posted by the campaign management device 10 on the account of an advertiser, and, on condition that the user enters the correct answer to the quiz, the post screen generating unit 135 may display button B on campaign screen A, or transition to a screen displaying button B.

The post content search unit 136 searches for posts made by users to the second service using the post screen data 126 provided by the post screen generation unit 135 based on the environment provided by the second posting unit 134. In other words, the post content search unit 136 searches for posts made by users to apply to the campaign, related to a campaign managed and operated by the campaign management device 10, among the posts posted to the second service.

There are no particular limitations on the method used by the post content search unit 136 to search for posted articles, but in the campaign management device 10 of this embodiment, the post content search unit 136 assumes that an article that contains a hashtag generated by the post screen generation unit 135 is an article posted to apply for a campaign, and performs a search based on the presence or absence of a hashtag.

In addition, the post content search unit 136 stores the number of posts, reposts, and mentions of the second service in the campaign results DB 128 based on the post article search results.

The identification unit 137 extracts information (mainly the account ID of the first service) for identifying the account in the first service of the user who applied for the campaign based on the posted content of the article posted by the user to apply for the campaign, which is extracted by the search of the posted content search unit 136, and identifies the user based on the extracted information.

There are no particular limitations on the method of user identification by the identification unit 137, but in the campaign management device 10 of this embodiment, the identification unit 137 extracts from the posted content an ID associated with the user's account ID in the first service generated by the posting screen generation unit 135, and identifies the user's account ID in the first service by referring to the "identification ID" in the user information DB 123. In addition, the identification unit 137 obtains the account ID in the second service of the user who posted the posted article from the posted article extracted by the search of the posted content search unit 136, and stores this account ID in the user information DB 123. Furthermore, the identification unit 137 obtains information related to the posting date and time of the posted article extracted by the search of the posted content search unit 136, and stores this information in the "date and time" column of the campaign participation history DB 122.

The lottery unit 138 draws a prize for the user identified by the identification unit 137. Preferably, the lottery unit 138 draws a prize after the campaign period ends. Of course, the lottery unit 138 may draw a prize during the campaign period.

Specifically, the lottery unit 138 first searches the campaign participation history DB 122 for the identified user and determines whether or not the user satisfies the participation conditions for the campaign. The participation conditions are, for example, that the date and time when the application information is received is within the application period for the campaign, that the user has not already received the benefit, etc. If the identified user does not satisfy the participation conditions, the lottery unit 138 does not hold a lottery for the user and determines that the user is ineligible to participate or has lost the lottery.

The lottery unit 138 draws prizes for identified users who meet the participation conditions. Any method of drawing the prizes may be used. In this case, the lottery unit 138 calculates the probability of winning the campaign via the second service based on the "number of posts via the second service" and the "number of winners via the second service" in the campaign results DB 128, and draws prizes to satisfy this probability of winning.

Meanwhile, the lottery unit 138 manages the personal information of people (not necessarily users of the first service or the second service) who applied to the campaign without going through the posting screen C generated by the posting screen generation unit 135, counts the total number of applications, and stores them in the campaign results DB 128. People who applied to the campaign "without going through the posting screen C" here also include people who viewed the campaign screen A via the first service and performed a specified operation input on the campaign application button B provided on the campaign screen A, but did not post using the posting screen C.

The lottery unit 138 also draws prizes for those who applied to the campaign without going through the posting screen C. At this time, the lottery unit 138 calculates the probability of winning the campaign for those who applied to the campaign without going through the posting screen C based on the "total number of applications" and "number of winners" in the campaign results DB 128, and draws prizes so as to satisfy this winning probability. This winning probability can be made lower than the winning probability of the campaign via the second service. This makes it possible to guide users to apply to the campaign via the second service, and makes it possible to measure the effectiveness of the campaign more accurately and precisely.

Alternatively, when multiple posts are made to the second service using the same account ID for the first service, the lottery unit 138 may create a ranking of the number of posts made to the second service, and treat all account IDs that rank highly (e.g., the top 100) as winners (this is also a type of lottery).

The lottery unit 138 stores information regarding the lottery results and date and time in the campaign participation history DB 122.

The providing unit 139 provides the benefits related to the campaign to the accounts of users who win the lottery drawn by the lottery unit 138.

Specifically, the providing unit 139 transmits access information to the winning user's account for the second service as the account of the advertiser of the second service. For example, the providing unit 139 transmits the access information to the user's account by message or the like by logging in to the account of the advertiser of the second service. The access information may include a URL to a homepage managed by the advertiser that can only be accessed by the winning user.

Alternatively, the providing unit 139 may send a post (message) to the user's account in the first service via the first server 30.

The benefit may be, for example, a gift, points for any service, virtual currency, a coupon, etc. The providing unit 139 also stores information indicating whether or not a benefit has been provided in the campaign participation history DB 122.

The benefit may also be an object, service, or right that can only be experienced by users who participate in the campaign. Examples include participation in a chatbot that allows users to enjoy conversations with characters related to the campaign, and image files that are only provided to campaign participants. In particular, image files that incorporate user-specific information (such as the user's account name) are also included. Benefits also include changing the user's profile image in the first service or the second service. Although changing the profile image is usually performed with user authority, in this embodiment (and the second embodiment described next), the campaign management device 10 holds authentication information for the first service and/or the second service as appropriate, so that the providing unit 139 can change the profile image, etc. Of course, the profile image, etc. can be restored to its original state when the campaign implementation period ends.

For example, in the case where a user is offered the privilege of chatting with a chatbot, the user may participate in a campaign by operating the user terminal 20 to post to the second service in an application corresponding to the first service. As a result, for example, when sending and receiving direct messages (messages are sent and received between the user's account in the second service and the account of an advertiser related to the campaign) the advertiser's account may be able to send messages to the user via the chatbot, or receive messages from the user's account and respond to them via the chatbot. The privilege of being able to use the chatbot may also be offered to users in the first service.

For example, when providing an image file with user-specific information superimposed thereon as a privilege to the user, messages may be sent and received between the advertiser's account and the user's account in the first service or the second service, and information to be embedded in the image may be accepted from the user. Information accepted as input from the user in the advertiser's account (e.g., a user name, etc.), or a user name associated with the user's account in the second service or the first service, may be superimposed on the image, and the superimposed image may be provided to the user through the first service or the second service, etc. For example, an image with a user name superimposed on a character image may be received as a privilege.

For example, when a privilege to be offered to a user is the ability to change a profile picture, the profile pictures of each user who receives the privilege in the first service or the second service may be changed simultaneously in response to the arrival of a specified timing. This allows the profile pictures of multiple users participating in the campaign to be changed simultaneously to pictures related to the campaign, making it even easier for other users who use the first service or the second service to recognize the campaign. When changing the profile pictures in this way, the profile pictures of each user may be changed simultaneously in accordance with the period during which the campaign is implemented, and then all of them may be reverted to their original state at the end of the period. This may increase the effectiveness of the campaign without requiring each user to take the trouble of changing their profile picture.

In addition, the providing unit 139 may provide a bonus not only to the account of the user who wins the lottery drawn by the lottery unit 138, but also to all user accounts who applied for the campaign.

The analysis unit 140 analyzes the information stored in the campaign implementation DB 127 and the campaign performance DB 128, and reports the analysis results to the advertiser. The analysis unit 140 also analyzes the information stored in the user information DB 123, and analyzes the diffusion effect of the campaign information in the second service. The diffusion effect may also be determined by referring to the information stored in the campaign performance DB 128.

<Functional configuration of user terminal 20>
6 shows a functional configuration realized by the hardware configuration of the user terminal 20. The user terminal 20 includes a memory unit 210, a control unit 220, a microphone 231, a speaker 232, a position information sensor 233, a touch panel 234, a camera 237, a motion sensor 238, a wireless communication unit 239, and an antenna 240. The touch panel 234 includes a touch-sensitive device 235 and a display 236. The memory unit 210 is configured by the main memory unit 202 and the auxiliary memory unit 203 of the user terminal 20, the control unit 220 is mainly configured by the processor 201 of the user terminal 20, the wireless communication unit 239 and the antenna 240 are configured by the communication IF 204, the microphone 231, the position information sensor 233, the touch-sensitive device 235, the camera 237, and the motion sensor 238 are configured by the input device 205, and the speaker 232 and the display 236 are configured by the output device 206.

<Configuration of the storage unit of the user terminal 20>
The storage unit 210 of the user terminal 20 stores a user ID 211 for identifying a user who uses the user terminal 20 and an application program 212 .

The user ID 211 is the user's account ID. The user transmits the user ID 211 from the user terminal 20 to the server. The server identifies the user based on the user ID 211 and provides services to the user. The user ID includes information such as a session ID that is temporarily assigned by the server when identifying the user who is using the user terminal 20.

In particular, in the campaign management system 1 of this embodiment, the user ID 211 stored in the memory unit 210 of the user terminal 20 includes account information of the user of the first service and account information of the user of the second service. The first posting unit 223 and the second posting unit 224 described below use the user ID 211 to access the first service and the second service, and use these first service and second service.

The application program 212 may be pre-stored in the storage unit 210, or may be configured to be downloaded from a web server operated by the service provider via a communication IF. The application program 212 includes an interpreter-type programming language that is executed on a web browser application stored in the user terminal 20.

<Configuration of the control unit of the user terminal 20>
The control unit 220 of the user terminal 20 includes an input control unit 221, an output control unit 222, a first posting unit 223, and a second posting unit 224. The control unit 220 executes an application program 212 stored in the storage unit 210, thereby realizing the functional units of the input control unit 221, the output control unit 222, the first posting unit 223, and the second posting unit 224.

The input control unit 221 acquires information output from the input device 205, such as the user's operation on the touch-sensitive device 235 of the touch panel 234, voice input to the microphone 231, the position information sensor 233, the camera 237, and the motion sensor 238, and executes various processes.

The output control unit 222 executes control processing of the display content of the display 236 and the audio output content of the speaker 232 based on user operations on the input device 205.

The first posting unit 223 logs in to the first server 30 using the user ID 211, and while logged in, transmits and receives various information to and from the first server 30 to use the first service. Similarly, the second posting unit 224 logs in to the second server 40 using the user ID 211, and while logged in, transmits and receives various information to and from the second server 40 to use the second service.

<Operation of campaign management system 1>
The processing of the campaign management system 1 will be described below with reference to the sequence diagrams of Figures 12 and 13 and the flowcharts of Figures 14 and 15. In the following description, it is assumed that a user who owns a user terminal 20 has already logged in to the first service and the second service with his/her own account, and that the campaign management device 10 has already logged in to the first service with the advertiser's account.

First, the campaign management device 10 transmits the campaign screen data 125 to the first server 30 and uploads the campaign screen data 125 to the first server 30 (S1200). Next, the campaign management device 10 posts information about the campaign as the advertiser's account (S1201).

Next, the user who owns the user terminal 20 accesses the first server 30 and views the posting screen for the first service (S1202).

Figure 16 shows an example of a posting screen displayed on the display 236 of the user terminal 20. Posts 1601 from multiple accounts (Xo, Advertiser A, Advertiser B) are displayed in sequence on the posting screen 1600. Here, the following explanation will be given assuming that the advertiser who has entrusted the operation and management of the campaign by the campaign operation system 1 of this embodiment is Advertiser A.

When a user becomes interested in the content posted by advertiser A and performs a predetermined operation input on advertiser A's post 1601 in order to view the details (typically by clicking on this post 1601), the first server 30 sends data to the user terminal 20 to display the content of post 1601 (actually posted by the campaign management device 10) with the account name of advertiser A, as shown in FIG. 17 (S1203). This content was posted by the campaign management device 10 in S1201.

As shown in FIG. 17, a screen 1700 showing the contents of posts relating to a campaign, for which advertiser A is the account, has an area 1701 showing the contents of the campaign. When a user who wishes to apply for the campaign performs a predetermined operation input on screen 1700 shown in FIG. 17 (typically clicking somewhere on screen 1700), information indicating that the operation input has been performed is sent to the first server 30 (S1204).

When the user performs a specified operation input, the first server 30 sends the uploaded campaign screen A to the user terminal 20 (S1205).

Figure 18 shows an example of a campaign screen A displayed on the screen of the user terminal 20. Campaign screen A has an area 1801 that shows the contents of the campaign, similar to the screen in Figure 17, and also has a button B that prompts the user to enter a specified operation when applying for the campaign.

The user views campaign screen A displayed on the user terminal 20, and if the user decides to apply for the campaign, performs a predetermined operation input on button B on campaign screen A (S1206). If an operation input is made, the campaign management device 10 obtains information about the account of the user who performed this operation input in the first service from the first server 30 (S1207), and performs a posting screen generation operation (S1208).

The details of the posting screen generation operation by the campaign management device 10 will be described with reference to the flowchart in FIG. 14. Note that some of the operations shown in the flowchart in FIG. 14 overlap with the operations already described in the sequence diagram in FIG. 12.

The campaign management device 10 waits for the user to input an operation on button B (YES in S1400), and obtains information about the account of the user who performed this operation input in the first service from the first server 30 (S1401).

Next, the campaign management device 10 acquires the hashtag of the relevant campaign from the campaign implementation DB 127 (S1402). Next, the campaign management device 10 generates a unique ID linked to the information about the account of the user in the first service acquired in S1401 (S1403).

Then, the campaign management device 10 generates a post content including the hashtag acquired in S1402, the ID generated in S1403, and information for spreading the campaign in the second service (S1404), and generates a post screen for posting the post content to the second service and presents it to the user (S1405).

Figure 19 shows an example of the posting screen C generated by the campaign management device 10 in S1405.

The posting screen C has a common interface and the like with a posting screen generally used when a user posts some content to the second service. The posting screen C displays information 1900 indicating which account the post will be made from (in the example shown in FIG. 19, the post is made from an account named "Xhara Yko"). An area 1901 on the posting screen C indicating the content of the post to be made contains information 1902 indicating the content of the campaign, a hashtag 1903, and a URL 1904 with a unique ID added to the end. The posting screen C also has a button 1905 that accepts a predetermined operational input for posting the content of area 1901 to the second service (second server 40).

When the user performs a predetermined operation input on this button 1905 to apply for the campaign, the content displayed on the posting screen C is posted to the second server 40 (S1209). FIG. 20 shows an example of a posting display screen 2000 that is displayed on the user terminal 20 of a user whose account is following the user who posted on the second service as a result of the user using the posting screen C to post on the second service.

Moving on to the sequence diagram of FIG. 13, after the end of the campaign period or at a predetermined time interval during the campaign period, the campaign management device 10 searches for posted articles related to campaign applications among the posted articles posted to the second service (second server 40), in other words, posted articles posted to the second service by users using the posting screen C (S1300), and obtains the search results from the second server 40, which are stored and managed in the DB (S1301, S1302).

The details of the post search operation by the campaign management device 10 are explained with reference to the flowchart in FIG. 15.

First, the campaign management device 10 refers to the campaign implementation DB 127 to acquire a hashtag associated with the campaign to be searched (S1500). Then, the campaign management device 10 searches the second service (second server 40) for posted articles whose posted content includes the hashtag acquired in S1500, and obtains the search results from the second server 40 (S1501).

Next, the campaign management device 10 counts the number of posts, reposts, and mentions based on the search results obtained in S1501, and stores them in the campaign performance DB 128 (S1502). Furthermore, based on the search results obtained in S1501, the campaign management device 10 extracts a URL from the posted article in which the post content includes the hashtag, and identifies the account information in the second service of the user who posted the posted article related to the campaign application by matching the ID contained in the URL with the ID stored in the user information DB 123 (S1503). Then, the account information in the second service is stored in the user information DB 123 (S1504).

Then, the campaign management device 10 conducts a lottery after the campaign period ends (S1303), and notifies the users who win the lottery (S1304). An example of a lottery result screen 2100 sent to the user terminal 20 of the user as a winning notification (lottery result notification) is shown in FIG. 21.

<Effects of the First Embodiment>
As described in detail above, according to the campaign management system 1 of this embodiment, information relating to the account of a user who has applied for a campaign in the first service can be associated with and managed with information relating to the account of a user who has posted to apply for the campaign in the second service.

As a result, it is expected that the content posted by users on the second service, i.e., information about the campaign, will be spread by reposting, mentioning, etc. This spreading effect is expected to be greater than when the advertiser's account provides the campaign information only on the first service.

In addition, since information about the account of a user who applied to a campaign on the first service can be associated with information about the account of a user who posted to apply to the campaign on the second service and managed in association with each other, it is possible to obtain quantitative indicators of the diffusion effect, such as the number of reposts and the number of mentions, compared to simply applying to a campaign using the first service, and it is possible to measure the effectiveness of the campaign more precisely.

As described above, the campaign management system 1 of this embodiment can increase the effectiveness of spreading a campaign when implementing a campaign that spans multiple services.

Second Embodiment
<Overview of the second embodiment>
With reference to FIG. 22, an overview of a campaign management system to which a campaign management device, which is an information processing device according to a second embodiment, is applied will be described.

The campaign management system 1 according to the second embodiment also has a campaign management device 10, which is an information processing device, a user terminal 20, a first server 30, and a second server 40. The configuration of the campaign management device 10 and other components of the second embodiment are almost the same as those of the first embodiment, so the following explanation focuses on the differences. The contents of the first service and the second service are also the same as those of the first embodiment, so detailed explanations will be omitted.

The campaign management system 1 of this embodiment is characterized in that the campaign management device 10 uses so-called OAuth-based authentication (hereinafter simply referred to as "OAuth authentication") as a method for obtaining information about the user's accounts for the first service and the second service. OAuth is a protocol for "authorization of authority" between Web services.

In the campaign management system 1 of this embodiment, the first service (first server 30) permits the second service (second server 40) to perform a predetermined operation using the user's account in the second service for the account of a user who has been authenticated (logged in) using authentication information in the first service. The user gives prior consent as to what operation is permitted.

With reference to Figure 22, an overview of the operation of the campaign management system 1, which is the second embodiment, will be described.

First, the campaign management device 10 posts information about the campaign to the first server 30 (1). As already explained, this posting is made under the account of the advertiser. The posting about the campaign includes the act of uploading data to the first server 30 for displaying the campaign screen A on the user terminal 20.

When a user who owns the user terminal 20 is viewing a posting screen of the first service provided by the first server 30, the user views a campaign post made by an advertiser's account and becomes interested in the campaign. The user then performs a specific operational input on the campaign post made by the advertiser's account via the user terminal 20.

In response to this operational input, the first server 30 displays the uploaded campaign screen A on the display screen of the user terminal 20. The campaign screen A has a button B for applying for the campaign, and the user who owns the user terminal 20 applies for the campaign by performing a specific operational input on this button B (2).

When a user performs a specific operation input on button B on campaign screen A, information indicating that the operation input has been performed and information regarding the accounts of the first service and the second service of the user who performed the operation input is transmitted to the campaign management device 10 (3).

In the campaign management system 1 of this embodiment, when the user performs a specific operation input on button B on campaign screen A as a result of OAuth authentication, it is assumed that the first service, the second service, and the user have given prior consent to reposting under the user's account an article about campaign information that was posted under the advertiser's account name on the second service and that was uploaded to the first server 30.

When the user performs a specific operation input on button B on campaign screen A, the first server 30 causes the user's account in the second service to repost, under the user's account in the second service, the article about the campaign information posted under the advertiser's account in the second service (4). This completes the user's application procedure for the campaign.

<Configuration of the storage unit 310 of the campaign management device 10>
Since the campaign management device 10 of this embodiment does not perform post search using a user-specific ID and hashtag, the specific ID column can be omitted in the user information DB 123, and the hashtag column can be omitted in the campaign implementation DB 127.

<Operation of campaign management system 1>
The processing of the campaign management system 1 will be described below with reference to the sequence diagrams of Figures 23 and 24. In the following description, it is assumed that a user who owns a user terminal 20 has already logged in to the first service and the second service with his/her own account, and that the campaign management device 10 has already logged in to the first service with the advertiser's account.

The operations from S2300 to S2305 are substantially the same as S1200 to S1205 in the first embodiment.

Figure 25 shows an example of campaign screen A sent to the user terminal 20 of the user in S2305. Campaign screen A shown in Figure 25 has the same configuration as the screen in Figure 17. That is, campaign screen A has an area 2501 showing the contents of the campaign, and also has button B which prompts the user to input a specified operation when applying for the campaign. However, button B simply displays "Apply", indicating that the user can immediately apply for the campaign by inputting a specified operation to button B.

When the user views campaign screen A displayed on the user terminal 20 and decides to apply for the campaign, the user performs a predetermined operation input on button B on campaign screen A (S2306). When an operation input is performed, the campaign management device 10 acquires information about the accounts of the user who performed this operation input in the first service and the second service from the first server 30 (S2307). After this, the campaign management device 10 stores the account information in the first service and the second service in the user information DB 123.

After this, as a result of the OAuth authentication, the campaign management device 10 instructs the first server 30 to repost the post made under the advertiser's account name regarding the campaign application in the second service under the user's account name in the second service (S2308).

If the user has not given permission for OAuth authentication regarding the linkage between the first service and the second service, a screen such as the one shown as an example in FIG. 26 is displayed on the user terminal 20, and permission regarding the linkage between the first service and the second service is requested. In FIG. 26, the display screen 2600 has an area 2601 in which detailed contents of the linkage are displayed, a button 2602 for receiving a predetermined operation input for authenticating the linkage, and a button 2603 for receiving a predetermined operation input for not authenticating the linkage.

As a result of the instruction in S2308, an example of a post display screen 2700 that is displayed on the user terminal 20 of a user whose account is following the user who made the repost in the second service is shown in FIG. 27. A post about applying for a campaign, whose account is advertiser A, is reposted under the name of the user's account.

Moving on to the sequence diagram of FIG. 24, after the end of the campaign period or at a predetermined time interval during the campaign period, the campaign management device 10 searches for posted articles related to campaign applications among the posted articles posted to the second service (second server 40), i.e., posts under the advertiser's account name related to campaign applications that have been reposted under the user's name (S2400), obtains the search results from the second server 40, and stores and manages them in the DB (S2401, S2402).

The method of searching for posts in S2400 is arbitrary, but one example is a method in which the campaign management device 10 logs into the second service (second server 40) as the advertiser's account, and counts the number of reposts and mentions of the posted article related to the campaign application using an analysis function (analytics function) related to the advertiser's own posts that is provided as a function of the second service.

The operations from S2403 to S2404 are substantially the same as S1303 to S1304 in the first embodiment.

<Effects of the Second Embodiment>
Therefore, according to the campaign management system 1 of this embodiment, it is possible to obtain the same effects as those of the campaign management system 1 of the above-mentioned first embodiment.

In particular, in the campaign management system 1 of this embodiment, by using the OAuth authentication mechanism, information regarding the accounts of the user who applied for the campaign in the first service and the second service can be obtained, so there is no need to prepare a hashtag or an ID for identifying the user's account in the first service. This makes it possible to simplify the device configuration and operation of the campaign management device 10 more than the campaign management device 10 in the first embodiment.

<Modification>
In the first and second embodiments described above, the posting screen (1700 in FIG. 17) showing the campaign information in the first service is transitioned to the campaign screen A (FIGS. 18 and 25). However, a screen showing the campaign information may be provided on an external site, and the screen may be transitioned to the campaign screen A of the first service via this screen. In addition, if the user can apply for the campaign on the condition of purchasing a product, the user may apply for the campaign on the condition of purchasing a product that is the target of the campaign and inputting a campaign code (serial code) written on the product. Such a modified example will be described with reference to FIGS. 28 to 36. Note that the modified examples shown in FIGS. 28 to 32 are modified examples of the first embodiment, and the modified examples shown in FIGS. 33 to 36 are modified examples of the second embodiment, but similar modified examples can be applied to either embodiment.

<Modification 1>
28 is a diagram showing an example of a screen notifying a user of a campaign that is displayed when the user who owns the user terminal 20 accesses an external site (i.e., a site that is not a site within the services operated by the first service or the second service). A screen 2800 displayed on the user terminal 20 displays the contents of the campaign, similar to that of FIG. 17, and also displays an "Apply" button 2801. When a user views this screen 2800 and wishes to apply for the campaign, the user performs an input operation on the button 2801.

When the user operates button 2801, the first server 30 displays an authentication screen 2900 as shown in FIG. 29. The authentication screen 2900 shown in FIG. 29 is an authentication screen for logging in to the first service (first server 30). If the user wishes to log in to the first service (perform authentication), the user operates the "Allow" button 2901, and if the user does not wish to log in, the user operates the "Cancel" button 2902.

If an input operation is performed on the "Allow" button 2901 and the user is already using the first service using the user terminal 20, it is determined that the user is already logged in to the first service, authentication is permitted, and information such as the user's account ID for the first service is sent from the first server 30 to the campaign management device 10. On the other hand, if an input operation is performed on the "Cancel" button 2902, the screen returns to (transitions to) the screen shown in FIG. 28. Note that, depending on the user terminal 20, authentication operation for the first service may be performed without displaying the authentication screen 2900 shown in FIG. 29. In this case, when an input operation is performed on the button 2801, information such as the user's account ID for the first service is sent from the first server 30 to the campaign management device 10.

Next, instead of displaying campaign screen A shown in FIG. 18, the campaign management device 10 causes the user terminal 20 to display a user's My Page screen 3000 shown in FIG. 30, which is prepared for each user (more precisely, for each user's account ID in the first service). The My Page screen 3000 displays the number of points 3001 registered in the campaign management device 10 at the time the user enters the serial code, a button 3002 for transitioning to a screen where the serial code can be entered, and a button 3003 for transitioning to a gift application (campaign application) screen. The screen where the serial code can be entered is a known one, so it will not be described here.

When the user performs an input operation on button 3003, the campaign management device 10 displays screen 3100 shown in FIG. 31 on the user terminal 20. Screen 3100 displays buttons 3101 and 3102 for campaign application according to the number of points registered by the user (registered in the campaign management device 10). More specifically, if one point or more is registered in the campaign management device 10, the user can apply for a campaign in which a prize (e.g., a prize) corresponding to one point can be drawn by inputting button 3101, and if three points or more are registered in the campaign management device 10, the user can apply for a campaign in which a prize (e.g., a prize) corresponding to three points can be drawn by inputting button 3101.

At this time, the campaign management device 10 compares the number of points registered at that time with the number of points required for the campaign to which the user has applied, and if the number of registered points is less than the number of points required for the campaign application, it notifies the user via the user terminal 20 that the user cannot apply for the campaign, and causes screen 3100 shown in FIG. 31 to be displayed again. On the other hand, if the number of registered points is equal to or greater than the number of points required for the campaign application, the campaign management device 10 processes the user's application for the campaign, and enters the specified information in the campaign participation history DB 1012 shown in FIG. 7. In addition, when the campaign application process is completed, the campaign management device 10 subtracts the number of points required for the campaign application from the number of points registered by the user.

When the campaign application process is completed, the campaign management device 10 causes the user terminal 20 to display a screen 3200 as shown in FIG. 32. The screen 3200 shown in FIG. 32 replaces the campaign screen A shown in FIG. 18, and similar to the "Submit and apply" button B displayed on the campaign screen A in FIG. 18, in addition to the "Submit" button 3202 for transitioning to the submission screen C shown in FIG. 19, a "Thank you for applying" button 3201 and a "Back" button 3203 are displayed.

When the "Thank you for applying" button 3201 is operated by the user, the campaign application process ends without posting to the second service. In this case, the participation history remains in the campaign participation history DB 1012, and the "total number of applications" in the campaign results DB 1018 is also incremented, but the "number of posts to the second service" is not incremented. In other words, the probability of winning in this case is lower than the probability of winning for a campaign application via the second service.

Similarly, when the "Back" button 3203 is operated by the user, the campaign management device 10 causes the My Page screen 3000 shown in FIG. 30 to be displayed on the user terminal 20. In this case, too, the campaign application process ends without posting to the second service.

<Modification 2>
As in the above-mentioned modified example 1, a campaign announcement screen 2800 of an external site shown in Fig. 28 is displayed on the user terminal 20, and when the user performs an input operation on the application button 2801, an authentication screen 2900 shown in Fig. 29 is displayed, an authentication operation for the first service is performed, authentication is permitted, and information such as the user's account ID in the first service is sent from the first server 30 to the campaign management device 10. In modified example 2, when information such as the user's account ID in the first service is sent from the first server 30 to the campaign management device 10, the campaign management device 10 determines that the user has applied to the campaign.

As described above, depending on the user terminal 20, authentication for the first service may be performed without displaying the authentication screen 2900 shown in FIG. 29. In this case, when an input operation of the button 2801 is performed, information such as the user's account ID for the first service is sent from the first server 30 to the campaign management device 10.

When the authentication operation in the first service is performed and the authentication is permitted, the campaign management device 10 causes the user terminal 20 to display a screen (first service screen) 3300 shown in FIG. 33. This screen 3300 is a screen provided on an external site, similar to the campaign announcement screen 2800 shown in FIG. 28. The screen 3300 shown in FIG. 33 displays a button 3301 provided on the first server 30 for transitioning to a screen for explaining the details of the campaign, and a button 3302 for performing an operation for linking with the second service. In the second modification example, a competition is held to see who can post the most in the second service, and rewards are awarded to those ranked high in the number of posts after the campaign implementation period.

If the user wishes to link with the second service in order to participate in the rankings, the user performs an input operation on button 3302 displayed on the screen of the user terminal 20. When there is an input operation on button 3302, the campaign management device 10 displays a display screen (authentication screen) 2600 for the second service shown in FIG. 26 on the user terminal 20, and requests linkage with the second service. Then, when the user performs an input operation on button 2602 that accepts a predetermined operational input for authenticating the linkage, OAuth authentication is performed and permission for OAuth authentication regarding the linkage between the first service and the second service is obtained.

When a user applies for a campaign and performs a linked operation with the second service, that is, when the user performs an input operation on button 2602 in FIG. 26, the campaign management device 10 causes the user terminal 20 to display the user's My Page prepared in the first server 30. This My Page is provided in the account of advertiser A, who is the campaign implementer in the first service. When the user displays a screen displaying advertiser A's account on the user terminal 20, a menu for transitioning to My Page is displayed on the user terminal 20, and the user can access My Page at any time via this menu.

Figure 34 is a diagram showing a top screen 3400 of a user's My Page prepared on the first server 30. Top screen 3400 displays button 3401 (first object) for transitioning to a screen for posting to the second service, button 3403 (second object) for transitioning to a screen for posting to the first service, and button 3403 (third object) for transitioning to a screen for checking the current ranking.

When the user performs an input operation on the button 3401 via the user terminal 20, a posting screen similar to the screen shown in FIG. 19 in the first embodiment is displayed, and the campaign management device 10 displays the posting screen on the user terminal 20. After that, when the user performs a posting operation to the second service using the posting screen, the campaign management device 10 obtains the user's account information for the second service. The posting screen to the second service is similar to the screen shown in FIG. 19 in the first embodiment, so it will not be described here. However, as described above, since OAuth authentication has already been performed in the second modification, it is not necessary to include the URL 1904 in the posting content. As for the hashtag 1903, since OAuth authentication has also already been performed, it is not necessary, but from the viewpoint of increasing the effectiveness of the campaign or making it easier to search in the campaign management device 10, a specific hashtag 1903 is included in the posting content in the second modification.

On the other hand, when the user performs an input operation on button 3402 via the user terminal 20, the campaign management device 10 causes the user terminal 20 to display a screen (not shown) for selecting other users with whom to share information about the campaign in the first service (a post containing information about the campaign is made on a screen displaying conversations with other users who are registered as friends by the user in the user's account in the first service).

When the user selects and inputs another user via the user terminal 20, the campaign management device 10 posts a message including the campaign information that has already been prepared to the first server 30 under the user's account (using the account information). Figure 35 shows a screen 3500 that shows other users viewing the content posted by the user (Xhara Yko) in the first service. This screen 3500 shows a post 3501 by the user (Xhara Yko) regarding campaign information.

Figure 36 is a diagram showing a ranking screen 3600 for a campaign. The ranking screen 3600 in Figure 36 is displayed on the user terminal 20 by the campaign management device 10 when the user performs an input operation on the button 3403 via the user terminal 20 on the user's My Page shown in Figure 34.

As already explained, in variant 2, a ranking is taken of the number of posts of campaign content to the second service, and after the campaign implementation period, rewards are given to those at the top of this ranking. In variant 2, since the user has obtained OAuth authentication, the campaign management device 10 can obtain account information for the second service each time the user posts to the second service through the campaign management device 10 and count the number of posts of campaign content to the second service. Therefore, the campaign management device 10 can create a current ranking based on this number of posts.

The ranking screen 3600 shown in FIG. 36 displays areas 3601-3603 that display the current position for each ranking, account information, and the number of posts to the second service. For the account information, a user name may be registered on My Page or when registering for a campaign, and this user name may be displayed. Also, instead of the number of posts to the second service, the campaign management device 10 may calculate points linked to the number of posts (e.g., 10 points per post) and display these points.

In variant example 2, a button 3302 is provided on screen 3300 on the external site to link with a second service and authenticate the second service. Also, when transitioning from FIG. 28 to FIG. 33, authentication of the first service is performed if necessary. In this way, authentication operations for the first and second services are performed from the external site. This allows the user to perform authentication operations for the first and second services without having the impression that they have transitioned to multiple sites, improving user convenience.

In addition, on the top screen 3400 shown in FIG. 34, a "Post to second service" button 3401, a "Post to first service" button 3402, and a "Check ranking" button 3403 are displayed in a series, so that the user can smoothly carry out a series of actions, such as posting to the second service and posting to the first service, while checking the ranking. This can increase the user's motivation to participate in the campaign. In addition, the series of actions described above can be easily performed within a single screen 3400, making user operation easier.

In the second variant, the rankings are generated based on the number of posts to the second service, but the basis for calculating the rankings is not limited to the number of posts to the second service. As an example, there are no particular limitations as long as it provides an incentive for users to participate in the campaign, such as the number of shares of a campaign post on the first service described above or the number of visits to the ranking site.

<Additional Notes>
In addition, the above-described embodiments are described in detail to clearly explain the present disclosure, and are not necessarily limited to those including all of the described configurations. In addition, some of the configurations of each embodiment can be added to, deleted from, or replaced with other configurations.

The above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example by designing them as integrated circuits. The present invention can also be realized by software program code that realizes the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor of the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-mentioned embodiments, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media for supplying such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs, optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, and ROMs.

In addition, the program code that realizes the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C/C++, perl, Shell, PHP, Java (registered trademark), etc.

Furthermore, the program code of the software that realizes the functions of the embodiment may be distributed over a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the processor of the computer may read and execute the program code stored in the storage means or storage medium.

The matters explained in each of the above embodiments are noted below.

(Appendix 1)
A program (121) for operating a computer (10) having a processor (101), the program (121) causes the processor (101) to perform a first step (S1201) of posting an advertiser's campaign using an advertiser's account in a first service in which only one account can be used on a user terminal owned by a user for authentication information of one user, a second step (S1206) of detecting an input operation performed by a user using the first service in response to the posting of the campaign, and, when the input operation is detected in the second step (S1206), a third step (S1209) of providing a user with posted content including first information (1904) capable of identifying the user's account in the first service in a second service in which the user can use the second service by switching between one or more accounts on a user terminal owned by the user in response to the information; and a fourth step (S1301-S1304) of detecting that the user has made a post in the second service using his/her own account based on the posted content, identifying the account of the user who made the post including the first information based on the detection result, and granting a benefit related to the campaign to the account.

(Appendix 2)
The program described in Appendix 1, wherein the operation of identifying the account that made the post including the first information in the fourth step (S1301 to S1304) includes the operation of obtaining second information capable of identifying the user's account in the second service (S1301).

(Appendix 3)
The program according to claim 2, further comprising a fifth step (S1302) of linking and managing the first information and second information for a user who has made a post including the first information.

(Appendix 4)
The program according to claim 3, wherein in a fifth step (S1302), a table (123) linking the first information and the second information is created and stored.

(Appendix 5)
A program described in any one of appendices 1 to 4, wherein the posted content includes third information (1903) that can identify the campaign.

(Appendix 6)
The program according to claim 5, wherein the third information (1903) is information unique to each campaign.

(Appendix 7)
The program described in Appendix 5 or 6, wherein the third information (1903) is included in the post content only during the campaign period.

(Appendix 8)
In a fourth step (S1301 to S1304), the task of detecting that a user has made a post on the second service based on the posted content is performed by checking whether or not the posted content includes third information (1903).

(Appendix 9)
A program described in any of appendices 1 to 8, wherein in the second service, a user with an account can view posts made by one or more other accounts that have a specific relationship with the account.

(Appendix 10)
In the second service, a user with an account can make posts from other accounts viewable to accounts that can view posts from the account, based on the user's operation.

(Appendix 11)
A program described in any of Appendices 1 to 10, in which in a fourth step (S1301 to S1304), a lottery is held to award a benefit based on the identified user's account, and the benefit is awarded to the user of the account that wins the lottery.

(Appendix 12)

The program described in Appendix 11, in which in the fourth step (S1301 to S1304), the account of the user who posted is identified based on the post of the advertiser's campaign in the second service, and the winning probability is made different between the account of the user who posted the post including the first information (1904) and the account of the user who posted the post not including the first information (1904).

(Appendix 13)
A program (121) for operating a computer (10) having a processor (101), the program (121) causes the processor (101) to execute a sixth step (S2301) of posting an advertiser's campaign using an advertiser's account in a first service in which only one account can be used on a user terminal owned by a user for authentication information of one user, a seventh step (S2306) of detecting an input operation performed by a user using the first service in response to the posting of the campaign, and, when the input operation is detected in the seventh step (S2306), the program causes the user to make a specified posting from his/her own account in a second service in which the user can use one or more accounts by switching between them on a user terminal owned by the user in response to the information; and a ninth step (S2307, S2400 to S2404) of obtaining first information capable of identifying the account in the first service of the user who made the posting in the second service and second information capable of identifying the account in the second service of the user who made the posting, and granting a benefit related to the campaign to the account of the user who made the posting.

(Appendix 14)
The program described in Appendix 13, comprising a tenth step (S2402) of linking and managing first information and second information for a user who has posted on the second service.

(Appendix 15)
The program described in Appendix 14, in which in a tenth step, a table (123) linking the first information and the second information is created and stored.

(Appendix 16)
A program described in any of Appendices 13 to 15, wherein in the second service, a user with an account can view posts made by one or more other accounts that have a specific relationship with the account.

(Appendix 17)
In the second service, a user with an account can make posts from other accounts viewable to accounts that can view posts from the account, based on the user's operation.

(Appendix 18)
The program described in Appendix 17, wherein the user's post on the second service is a post by an advertiser that makes the post on the second service about a campaign viewable to one or more other accounts that have a particular relationship with the user's account on the second service.

(Appendix 19)
A program described in any of Appendices 13 to 18, which executes an eleventh step in which, when an input operation is detected in a seventh step (S2306), a first object for allowing the user to post a campaign post using the user's own account in a first service, and a second object for allowing the user to post a specified post in a second service using their own account, are displayed on the same screen of a user terminal.

(Appendix 20)
The program described in Appendix 19, in an eleventh step, displays on the same screen of the user terminal a third object for displaying a ranking of the number of times a user has made posts on the second service using their own account through a specified post.

(Appendix 21)
An information processing device (10) having a processor (101), the information processing device executing a first step (S1201) of posting an advertiser's campaign using an advertiser's account in a first service in which only one account can be used on a user terminal owned by a user for authentication information of one user; a second step (S1206) of detecting an input operation made by a user using the first service in response to the posting of the campaign; a third step (S1209) of providing the user with posted content including first information (1904) capable of identifying the user's account in a first service in a second service in which one user's authentication information can be used by switching between one or more accounts on a user terminal owned by the user, if the input operation is detected in the second step (S1206); and a fourth step (S1301 to S1304) of detecting that the user has made a post in the second service using his/her own account based on the posted content, identifying the account of the user who made the post including the first information based on the detection result, and granting a benefit related to the campaign to the account.

(Appendix 22)
An information processing device (10) including a processor (101), the processor (101) performs a sixth step (S2301) of posting an advertiser's campaign using an advertiser's account in a first service in which only one account can be used on a user terminal owned by a user for authentication information of one user, a seventh step (S2306) of detecting an input operation performed by a user using the first service in response to the posting of the campaign, and, when the input operation is detected in the seventh step (S2306), detecting the user account owned by the user for the authentication information of one user. an eighth step (S2308) of causing a user to make a post on the second service from his/her own account by making a specified post in a second service that can be used by switching between one or more accounts on the user's terminal; and a ninth step (S2307, S2400 to S2404) of obtaining first information capable of identifying the account in the first service of the user who made the post on the second service and second information capable of identifying the account in the second service of the user who made the post, and granting a campaign-related benefit to the account of the user who made the post.

(Appendix 23)
An information processing method in which the processor (101) of a computer (10) having a processor (101) executes a first step (S1201) of posting an advertiser's campaign using an advertiser's account in a first service in which only one account can be used on a user terminal owned by a user for authentication information of one user; a second step (S1206) of detecting an input operation performed by a user using the first service in response to the posting of the campaign; a third step (S1209) of providing the user with posted content including first information (1904) capable of identifying the user's account in a first service in a second service in which one user's authentication information can be used by switching between one or more accounts on a user terminal owned by the user, if the input operation is detected in the second step (S1206); and a fourth step (S1301-S1304) of detecting that the user has posted on the second service using his/her own account based on the posted content, identifying the account of the user who posted the content including the first information based on the detection result, and granting a benefit related to the campaign to the account.

(Appendix 24)
In a first service in which only one account can be used on a user terminal owned by a user for authentication information of one user, the processor (101) of the computer (10) performs a sixth step (S2301) of posting an advertiser's campaign using the advertiser's account, a seventh step (S2306) of detecting an input operation performed by a user using the first service in response to the posting of the campaign, and when the input operation is detected in the seventh step (S2306), The information processing method includes an eighth step (S2308) of causing a user to make a specified post on a second service using his or her own account in the second service, where the second service can be used by switching between one or more accounts at a terminal, and a ninth step (S2307, S2400 to S2404) of obtaining first information capable of identifying the account in the first service of the user who made the post on the second service and second information capable of identifying the account in the second service, and granting a campaign-related benefit to the account of the user who made the post.

LIST OF SYMBOLS 1 Campaign management system, 10 Campaign management device, 20 User terminal, 30 First server, 40 Second server, 120 Memory unit, 121 Application program, 122 Campaign participation history DB, 123 User information DB, 124 Advertiser information DB, 125 Campaign screen data, 126 Post screen data, 127 Campaign implementation DB, 128 Campaign performance DB, 130 Control unit, 131 Reception control unit, 132 Transmission control unit, 133 First posting unit, 134 Second posting unit, 135 Post screen generation unit, 136 Post content search unit, 137 Identification unit, 138 Lottery unit, 139 Provision unit, 140 Analysis unit, A Campaign screen, B Button, C Post screen, N Network,

Claims (14)

A program for operating a computer having a processor, the program causing the processor to:
A first service is operated by a first server, and only one account can be used on a user terminal owned by the user for authentication information of the user. In the first service, a first step is to post an advertiser's campaign using the advertiser's account;
A second step of detecting an input operation performed by the user who uses the first service in response to the post of the campaign;
a third step of providing the user with posted content that explicitly includes first information that enables the computer to identify the account of the user in the first service in a second service that allows the user to switch between one or more accounts on the user terminal owned by the user in response to authentication information of the user, the second service being operated by a second server different from the first server, when the input operation is detected in the second step;
a fourth step of detecting that the user has made a post on the second service using the user's own account based on the content of the post, identifying the account of the user who made the post including the first information based on a result of this detection, and granting a benefit related to the campaign to the account;
In the third step, the program provides the user with posted content including the first information, generates a unique value as the first information, and associates the generated first information with fourth information capable of identifying the user's account in the first service. In the fourth step, the operation of identifying the account that posted the post including the first information includes an operation of obtaining second information capable of identifying the account of the user in the second service.
The program according to claim 1. The program according to claim 2, further comprising a fifth step of managing the first information and the second information in association with each other for the user who posted the first information. The program according to claim 3, wherein in the fifth step, a table linking the first information and the second information is created and stored. The program according to claim 1, wherein the post content includes third information that can identify the campaign. The program according to claim 5, wherein the third information is information unique to each of the campaigns. The program according to claim 5, wherein the third information is included in the post content only during the campaign period. The program according to claim 5, wherein in the fourth step, the task of detecting that the user has posted on the second service based on the posted content is performed by determining whether the posted content includes the third information. The program according to claim 1, wherein in the second service, a user having an account can view posts made by one or more other accounts that have a specific relationship with the account. The program according to claim 9, wherein in the second service, a user having a certain account makes the posts by the other accounts viewable to the accounts that can view the posts of the certain account based on the operation of the user. The program according to claim 1, wherein in the fourth step, a lottery is held to award the benefit based on the account of the identified user, and the benefit is awarded to the user of the account that wins the lottery. The program according to claim 11, wherein in the fourth step, the account of the user who posted the post is identified based on the post of the campaign of the advertiser in the second service, and the winning probability is made different between the account of the user who posted the post including the first information and the account of the user who posted the post not including the first information. An information processing device including a processor, the processor comprising:
A first service is operated by a first server, and only one account can be used on a user terminal owned by the user for authentication information of the user. In the first service, a first step is to post an advertiser's campaign using the advertiser's account;
A second step of detecting an input operation performed by the user who uses the first service in response to the post of the campaign;
a third step of providing the user with posted content that explicitly includes first information that enables the information processing device to identify the account of the user in the first service, in a second service that allows one user to use one or more accounts by switching between them on the user terminal owned by the user in response to authentication information of the user, the second service being operated by a second server different from the first server, when the input operation is detected in the second step;
a fourth step of detecting that the user has made a post on the second service using the user's own account based on the content of the post, identifying the account of the user who made the post including the first information based on a result of this detection, and granting a benefit related to the campaign to the account;
In the third step, the information processing device provides the user with posted content including the first information, generates a unique value as the first information, and associates the generated first information with fourth information capable of identifying the user's account in the first service. The processor of a computer including a processor
A first service is operated by a first server, and only one account can be used on a user terminal owned by the user for authentication information of the user. In the first service, a first step is to post an advertiser's campaign using the advertiser's account;
A second step of detecting an input operation performed by the user who uses the first service in response to the post of the campaign;
a third step of providing the user with posted content that explicitly includes first information that enables the computer to identify the account of the user in the first service in a second service that allows the user to switch between one or more accounts on the user terminal owned by the user in response to authentication information of the user, the second service being operated by a second server different from the first server, when the input operation is detected in the second step;
a fourth step of detecting that the user has made a post on the second service using the user's own account based on the content of the post, identifying the account of the user who made the post including the first information based on a result of this detection, and granting a benefit related to the campaign to the account;
In the third step, the information processing method includes providing the user with posted content including the first information, generating a unique value as the first information, and associating the generated first information with fourth information capable of identifying the user's account in the first service.