WO2014077123A1 - サーバ装置およびサーバプログラム - Google Patents
サーバ装置およびサーバプログラム Download PDFInfo
- Publication number
- WO2014077123A1 WO2014077123A1 PCT/JP2013/079300 JP2013079300W WO2014077123A1 WO 2014077123 A1 WO2014077123 A1 WO 2014077123A1 JP 2013079300 W JP2013079300 W JP 2013079300W WO 2014077123 A1 WO2014077123 A1 WO 2014077123A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application program
- application
- user
- banner
- advertisement
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0267—Wireless devices
-
- A—HUMAN NECESSITIES
- A63—SPORTS; GAMES; AMUSEMENTS
- A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
- A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
- A63F13/30—Interconnection arrangements between game servers and game devices; Interconnection arrangements between game devices; Interconnection arrangements between game servers
- A63F13/35—Details of game servers
- A63F13/352—Details of game servers involving special game server arrangements, e.g. regional servers connected to a national server or a plurality of servers managing partitions of the game world
-
- A—HUMAN NECESSITIES
- A63—SPORTS; GAMES; AMUSEMENTS
- A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
- A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
- A63F13/60—Generating or modifying game content before or while executing the game program, e.g. authoring tools specially adapted for game development or game-integrated level editor
- A63F13/61—Generating or modifying game content before or while executing the game program, e.g. authoring tools specially adapted for game development or game-integrated level editor using advertising information
-
- A—HUMAN NECESSITIES
- A63—SPORTS; GAMES; AMUSEMENTS
- A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
- A63F13/00—Video games, i.e. games using an electronically generated display having two or more dimensions
- A63F13/70—Game security or game management aspects
- A63F13/79—Game security or game management aspects involving player-related data, e.g. identities, accounts, preferences or play histories
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0209—Incentive being awarded or redeemed in connection with the playing of a video game
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
Definitions
- the present invention relates to a technique for displaying an advertisement on an application (application program) such as a game on a terminal device via a network.
- Patent Document 1 discloses a system in which an advertisement can be selectively inserted into a specific part of a game screen.
- Non-Patent Document 1 when an advertisement of a different game application B is displayed in a certain game application A and the game application B is downloaded based on the advertisement, an in-game item that can be used in the game application A is given.
- a so-called “rewarded advertisement” system is disclosed.
- Patent Document 1 According to the technologies disclosed in Patent Document 1 and Non-Patent Document 1 described above, an application to be advertised can be downloaded and an opportunity to start using can be provided, but the application to be advertised is continued. It did not lead to the so-called “improvement of user continuity” for use.
- the present invention has been proposed in view of the above-described conventional problems, and an object of the present invention is to improve a continuation rate of use of an application executed on a terminal device.
- a banner request receiving unit that receives a banner request with a user ID that identifies a user of the terminal device from a first application program executed on the terminal device;
- Application program selection means for referring to the use history of an arbitrary application program of the user specified by the user ID based on the user ID and selecting a second application program that has passed a predetermined period from the last activation Advertising information transmission corresponding to the second application program is transmitted to the terminal device to urge the second application program to be used again, and the advertising information is displayed on the screen of the first application program.
- a user who has stopped using an application executed on a terminal device can be recalled, and the continuation rate of using the application can be improved.
- FIG. 1 It is a figure which shows the structural example of the system concerning one Embodiment of this invention. It is a figure which shows the example of a data structure of user management DB. It is a figure which shows the example of a data structure of application priority point DB. It is a figure which shows the example of a data structure of application exclusion list DB. It is a figure which shows the example of a data structure of banner display log
- FIG. 1 which shows the example of the retention banner displayed on the application screen.
- FIG. (2) which shows the example of the retention banner displayed on the application screen.
- FIG. 2 which shows the process example of embodiment.
- FIG. 1 is a diagram showing a configuration example of a system according to an embodiment of the present invention.
- the game application is mainly assumed as an application, it cannot be overemphasized that it can apply also to applications other than a game application.
- the system includes a terminal device 1 such as a smartphone or a mobile phone possessed by a user (player), an access point 2 such as a mobile radio base station or a Wi-Fi station, a network 3 such as the Internet, and various types. Servers 4 to 6 are provided.
- a terminal device 1 such as a smartphone or a mobile phone possessed by a user (player)
- an access point 2 such as a mobile radio base station or a Wi-Fi station
- a network 3 such as the Internet
- Servers 4 to 6 are provided.
- the terminal device 1 includes the application (A) 11 and the application (B) 12, but may include other applications.
- the applications 11 and 12 have a function of executing a predetermined game, for example.
- the applications 11 and 12 also have a function of operating as a browser by an in-app browser function.
- the application download server 4 stores original programs such as the applications 11 and 12 and has a function of causing the terminal device 1 to download and install it. *
- the advertisement / user management server 5 manages a plurality of apps and their users across the board, and does not ask whether other apps (installed in the terminal device 1 or not) are installed on the apps executed on the terminal device 1. ) For controlling the display of advertisements (advertisement banners).
- the application corresponding to the service provided by the advertisement / user management server 5 is installed in the terminal device 1 and is initialized, and internally stores a user ID that is the same as that managed by the advertisement / user management server 5 When the server is accessed, the user ID is transmitted as necessary.
- the advertisement / user management server 5 manages the value of “priority point” for each application, and displays an advertisement of another application (Y) on a certain application (X), and the user is displayed on the other application (Y). Is guided (installed, activated, etc.), the priority point of the application (X) of the display source is added by a predetermined value, and an advertisement for an application with a large priority point is preferentially displayed by another application. , Has built a reasonable advertising system that can be operated without giving and receiving advertising fees with app vendors.
- the advertisement / user management server 5 includes a user management DB 51, an application priority point DB 52, an application exclusion list DB 53, a banner display history DB 54, an application usage history DB 55, a banner selection table 56, and a banner DB 57 as a database (DB) used for processing. It has.
- FIG. 2 is a diagram showing an example of the data structure of the user management DB 51, and has items (fields) such as “user ID” and “terminal ID”.
- “User ID” is information for identifying a user.
- the “terminal ID” is information that identifies the terminal device 1 used by the user.
- FIG. 3 is a diagram showing an example of the data structure of the application priority point DB 52, and has items such as “application ID” and “priority point”.
- App ID is information for identifying an application.
- the “priority point” is a value serving as a reference for determining the priority for displaying the advertisement of the application.
- FIG. 4 is a diagram showing an example of the data structure of the application exclusion list DB 53, in which “application IDs” that are information for identifying applications are listed.
- FIG. 5 is a diagram showing an example of the data structure of the banner display history DB 54, and has items such as “banner ID”, “application ID”, and “display history”. “Banner ID” is information for specifying an advertisement banner. Advertising banners include general regular banners that recommend installing and launching apps, and reusing (launching) apps for users who have not used (launched) for a specified period of time after installing and launching apps ) Is included, but other types of advertising banners may be provided. Retention banners are rewarded with items, points, and the like that can be used to advantageously advance games and the like in the app so that the user is incentive to use the app again.
- the “application ID” is information that identifies an application corresponding to the advertisement banner.
- the “display history” is a history of displaying the advertisement banner, and includes the displayed date / time information and the user ID of the user to be displayed.
- FIG. 6 is a diagram showing an example of the data structure of the application usage history DB 55, and has items such as “application ID” and “usage history”.
- “App ID” is information for identifying an application.
- “Usage history” is a history that the application has been used, and includes whether it is installed or activated, a user ID that identifies the user who has used it, and date and time information that has been used. In the “usage history”, information on the date and time when the application is activated is added each time the application is activated.
- the usage history for the user's application (application ID) may be managed in association with the user (user ID), and the usage history for each application may be acquired therefrom.
- FIG. 7 is a diagram showing an example of the data structure of the banner selection table 56, in which a banner type corresponding to the user status to be displayed is set.
- the “normal banner” is displayed when the application is not installed (not started)
- “retention banner # 1” is displayed when 7 to 14 days have passed since the last activation, and 14 or more days after the last activation.
- “Retention banner # 2” if less than 21 days have passed
- “Retention banner # 3” if more than 21 days to less than 28 days have passed since the last launch
- “Retention banner # 3” if more than 28 days have passed since the last launch 4 "is set.
- “Retention banner # 1”, “Retention banner # 2”, “Retention banner # 3”, and “Retention banner # 4” are set so as to increase the reward. This is because the longer the period since the last launch, the more difficult it will be to use again without giving a high incentive. Note that the number of days in the illustrated example can be arbitrarily changed according to the operation. The contents of the reward can be arbitrarily changed according to the operation.
- FIG. 8 is a diagram showing an example of the data structure of the banner DB 57, and includes items such as “banner ID”, “application ID”, “banner type”, “reward”, and “banner data”.
- “Banner ID” is information for specifying an advertisement banner.
- the “application ID” is information that identifies an application corresponding to the advertisement banner.
- “Banner type” is information indicating the type of the advertisement banner.
- “Reward” is information indicating the content of the reward when the reward is associated with the advertisement banner.
- “Banner data” is reference information of the data body or storage location of the advertisement banner.
- the banner data includes a description for accessing the application download server 4 when an advertisement banner is selected (tapped or clicked), or a description for starting an application already installed in the terminal device 1 (URL to be described later). Scheme).
- FIG. 9 shows an example of a normal banner
- FIG. 9A shows an example of a large normal banner
- FIG. 9B shows an example of a small normal banner.
- FIG. 10 is a diagram showing an example of a retention banner
- FIG. 10 (a) is an example of a large retention banner
- FIG. 10 (b) is an example of a small retention banner.
- the retention banner includes a display for notifying the content of the reward, such as “Now click on this banner and get 1000 CP in game play!”.
- the application priority point DB 52, the application exclusion list DB 53, the banner display history DB 54, the application usage history DB 55, the banner selection table 56, and the banner DB 57 are illustrated as separate databases for convenience. It can be configured as a single or any number of databases.
- the application management server 6 has a function of performing login, status management, and the like for the applications 11, 12 and the like. In particular, when accessed from an application activated in accordance with the selection of the retention banner, it also has a function of performing control such as giving a reward.
- the application management server 6 may be arranged on the same server device.
- the application management server 6 includes a charging history DB 61 that manages charging information for each user.
- FIG. 11 is a diagram showing an example of the data structure of the charging history DB 61, and has items such as “user ID” and “charging information”.
- “User ID” is information for identifying a user.
- “Billing information” is a history of past billing of the user, and includes an application ID that identifies the application used, a billing amount, and billing date / time information.
- FIG. 12 is a diagram illustrating a hardware configuration example of the terminal device 1.
- the terminal device 1 includes a power supply system 101, a main system 102 including a processor 103, a memory controller 104, and a peripheral interface 105, a storage unit 106, an external port 107, a high frequency circuit 108, an antenna 109, Audio circuit 110, speaker 111, microphone 112, proximity sensor 113, display controller 115, optical sensor controller 116, I / O subsystem 114 including input controller 117, touch-responsive display system 118, and optical sensor 119 and an input unit 120.
- a power supply system 101 including a processor 103, a memory controller 104, and a peripheral interface 105
- a storage unit 106 including an external port 107, a high frequency circuit 108, an antenna 109, Audio circuit 110, speaker 111, microphone 112, proximity sensor 113, display controller 115, optical sensor controller 116, I / O subsystem 114 including input controller 117, touch-responsive display system 118, and optical sensor 119 and an input unit 120.
- FIG. 13 is a diagram illustrating a hardware configuration example of the various servers 4 to 6.
- servers 4 to 6 include a CPU (Central Processing Unit) 402, a ROM (Read Only Memory) 403, a RAM (Random Access Memory) 404, and an NVRAM (Non-Volatile Random Access Memory) connected to the system bus 401.
- CPU Central Processing Unit
- ROM Read Only Memory
- RAM Random Access Memory
- NVRAM Non-Volatile Random Access Memory
- I / F Interface
- I / O Input / Output Device
- I / O Input / Output Device
- An HDD (Hard Disk Disk Drive) 408, a NIC (Network Interface Card) 409, and the like are provided.
- FIG. 14 is a sequence diagram showing a processing example of the above embodiment.
- the application 11 corresponds to the advertisement / user management server 5 address preset in the application 11.
- a banner request with an ID is transmitted (step S101).
- the advertisement / user management server 5 When receiving the banner request from the application 11, the advertisement / user management server 5 refers to the application priority point DB 52 and acquires an application list listing application IDs in descending order of priority points (step S102).
- the advertisement / user management server 5 refers to the application exclusion list DB 53 and removes the application ID registered in the application exclusion list DB 53 from the application IDs listed in the application list (step S103).
- the advertisement / user management server 5 refers to the banner display history DB 54 based on the user ID accompanying the banner request, and among the application IDs listed in the application list, for the user specified by the user ID.
- the application ID corresponding to the advertisement banner that has been displayed a predetermined number of times within a predetermined period is removed (step S104).
- the advertisement / user management server 5 refers to the application usage history DB 55 and the banner selection table 56 based on the application ID acquired from the top of the application list and the user ID accompanying the banner request, and the predetermined number (For example, five) advertising banners are selected (step S105). That is, referring to the usage history by the user of the user ID of the highest application ID in the application list and following the banner selection table 56 of FIG.
- the advertisement / user management server 5 acquires banner data from the banner DB 57 based on the selected predetermined number of advertisement banners (application ID, banner type) (step S106), and sends it to the application 11 of the requesting terminal device 1.
- Banner data is transmitted (step S107).
- the advertisement / user management server 5 updates the display history of the banner display history DB 54 for the advertisement banner that has transmitted the banner data (step S108).
- the display history may be updated immediately after banner selection (step S105).
- the application 11 of the terminal device 1 that has received the banner data displays an advertisement banner on the screen of the application 11 (step S109).
- FIG. 15 shows an example in which a large advertisement banner is displayed in the center of the screen.
- FIG. 16 is an example in which a small advertising banner is displayed in the upper left corner of the screen.
- the advertisement banner is a retention banner for the application 12 already installed in the terminal device 1.
- the application 11 transmits a banner selection notification with a banner ID, an application ID, a terminal ID, and the like to a known advertisement / user management server 5 address based on a description of a script or the like included in the retention banner. (Step S111). Upon receiving this, the advertisement / user management server 5 stores it in the internal storage area (step S112).
- the application 11 activates the application 12 based on the description such as the URL scheme included in the retention banner (step S113).
- the URL scheme is provided by the browser function of the terminal device 1, and specifies a URL scheme consisting of an application-specific URL and a character string of parameters added as necessary in the same manner as the URL for Web access. By doing so, it is a mechanism for starting the corresponding application.
- the application download server 4 is accessed by the URL scheme or the like, and after confirmation by the user. After the application is downloaded and installed, the user manually activates the application 11.
- the activated application 12 accesses the advertisement / user management server 5 for login based on an address preset in the application 12 (step S114). This access is accompanied by an application ID and a terminal ID.
- the advertisement / user management server 5 performs authentication by confirming whether the terminal ID is registered in the user management DB 51 (step S115), and responds to that effect if the authentication is successful. (Step S116). *
- the application 12 accesses the application management server 6 for login based on an address preset in the application 12 (step S117).
- the application ID, terminal ID, and login information (user ID, password, etc.) are accompanied.
- the application management server 6 Upon receiving the access, the application management server 6 authenticates the user based on the login information (step S118), and when successfully authenticated, makes a reward inquiry to the advertisement / user management server 5 with the application ID and terminal ID. (Step S119).
- the advertisement / user management server 5 checks whether the combination of the application ID and the terminal ID matches that stored in advance by receiving the banner selection notification (step S111), and then responds from the banner DB 57.
- the reward content to be acquired is acquired (step S120), and the reward content is returned to the application management server 6 (step S121).
- the application management server 6 gives a reward to the application 12 of the terminal device 1 (step S122).
- Rewarding includes generation / acquisition of reward data used to reflect a reward on the terminal device 1 side, and update of recording when the reward is recorded as a user history.
- the application management server 6 transmits the reward data to the application 12 of the terminal device 1 (step S123), and the application 12 reflects the reward based on the received reward data (step S124). For example, an item is added or an ability value is increased by updating the game management information.
- the application 12 displays that the reward has been reflected (step S125).
- the notification that the reward has been reflected may be made by voice or the like.
- the application management server 6 notifies the advertisement / user management server 5 of the activation of the application 12 (step S126).
- the advertisement / user management server 5 receives the application priority point DB 52 and the application usage history DB 55. Is updated (step S127). That is, since the activation of the application 12 can be guided by the display of the retention banner in the application 11, a predetermined priority point is added to the application 11 in the application priority point DB 52.
- the advertisement / user management server 5 updates the latest activation history for the application 12 by adding the time when the notification is received from the application management server 6 to the application usage history DB 55.
- the application download server 4 is accessed by selecting the normal banner, and the application is downloaded and installed after user confirmation.
- the billing history DB 61 of the application management server 6 is referred to and specified by the user of the terminal device 1 (the user ID accompanying the banner request).
- the order of applications (application IDs) in the application list may be changed.
- the ranking is re-determined with the value after adding the value obtained by multiplying the charge amount by a factor to the priority point.
- FIG. 17 is a sequence diagram showing another processing example of the above embodiment. The difference from the process shown in FIG. 14 is that the application priority point DB 52 is not used.
- the application 11 is a user with respect to the address of the advertisement / user management server 5 preset in the application 11.
- a banner request with an ID is transmitted (step S201).
- the advertisement / user management server 5 When receiving the banner request from the application 11, the advertisement / user management server 5 refers to the application usage history DB 55 based on the user ID accompanying the banner request, and the elapsed time after the last activation in the usage history of the user ID is An application list listing application IDs in the longest order is acquired (step S202). When a sufficient number of applications cannot be picked up from the usage history of the user ID, an application list is acquired from an application group prepared in advance as a default.
- the advertisement / user management server 5 refers to the application exclusion list DB 53 and removes the application ID registered in the application exclusion list DB 53 from the application IDs listed in the application list (step S203).
- the advertisement / user management server 5 refers to the banner display history DB 54 based on the user ID accompanying the banner request, and among the application IDs listed in the application list, for the user specified by the user ID.
- the application ID corresponding to the advertisement banner that has been displayed a predetermined number of times within a predetermined period is removed (step S204).
- the advertisement / user management server 5 refers to the application usage history DB 55 and the banner selection table 56 based on the application ID acquired from the top of the application list and the user ID accompanying the banner request, and the predetermined number (For example, five) advertisement banners are selected (step S205). That is, referring to the usage history by the user of the user ID of the highest application ID in the application list and following the banner selection table 56 of FIG.
- the advertisement / user management server 5 acquires banner data from the banner DB 57 based on the selected predetermined number of advertisement banners (application ID, banner type) (step S206), and sends it to the application 11 of the requesting terminal device 1.
- Banner data is transmitted (step S207).
- the advertisement / user management server 5 updates the display history of the banner display history DB 54 for the advertisement banner that has transmitted the banner data (step S208).
- the display history may be updated immediately after banner selection (step S205).
- the application 11 of the terminal device 1 that has received the banner data displays an advertisement banner on the screen of the application 11 (step S209).
- step S210 it is assumed that the user of the terminal device 1 selects an advertisement banner displayed on the screen of the application 11 (step S210), and that the advertisement banner is a retention banner for the application 12 already installed in the terminal device 1. To do.
- the application 11 transmits a banner selection notification with a banner ID, an application ID, a terminal ID, and the like to a known advertisement / user management server 5 address based on a description of a script or the like included in the retention banner. (Step S211). Upon receiving this, the advertisement / user management server 5 stores it in the internal storage area (step S212).
- the application 11 activates the application 12 based on the description of the URL scheme or the like included in the retention banner (step S213).
- the application download server 4 is accessed by the URL scheme or the like, and after confirmation by the user. After the application is downloaded and installed, the user manually activates the application 11.
- the activated application 12 accesses the advertisement / user management server 5 for login based on an address preset in the application 12 (step S214). This access is accompanied by an application ID and a terminal ID.
- the advertisement / user management server 5 performs authentication by confirming whether the terminal ID is registered in the user management DB 51 (step S215), and responds to that effect if the authentication is successful. (Step S216). *
- the application 12 accesses the application management server 6 for login based on an address preset in the application 12 (step S217).
- the application ID, terminal ID, and login information (user ID, password, etc.) are accompanied.
- the application management server 6 Upon receiving the access, the application management server 6 authenticates the user based on the login information (step S218). When the authentication is successful, the application management server 6 makes a reward inquiry to the advertisement / user management server 5 with the application ID and the terminal ID. (Step S219).
- the advertisement / user management server 5 confirms whether the combination of the application ID and the terminal ID matches that stored in advance by receiving the banner selection notification (step S211), and then responds from the banner DB 57.
- the reward content to be acquired is acquired (step S220), and the reward content is returned to the application management server 6 (step S221).
- the application management server 6 gives a reward to the application 12 of the terminal device 1 (step S222).
- Rewarding includes generation / acquisition of reward data used to reflect a reward on the terminal device 1 side, and update of recording when the reward is recorded as a user history.
- the application management server 6 transmits the reward data to the application 12 of the terminal device 1 (step S223), and the application 12 reflects the reward based on the received reward data (step S224). For example, an item is added or an ability value is increased by updating the game management information.
- the application 12 displays that the reward has been reflected (step S225).
- the notification that the reward has been reflected may be made by voice or the like.
- the application management server 6 notifies the advertisement / user management server 5 of activation of the application 12 (step S226), and the advertisement / user management server 5 receives the notification, and the advertisement / user management server 5 receives the application priority point DB 52 and the application usage history DB 55. Is updated (step S227). That is, since the activation of the application 12 can be guided by the display of the retention banner in the application 11, a predetermined priority point is added to the application 11 in the application priority point DB 52. The advertisement / user management server 5 updates the latest activation history for the application 12 by adding the time when the notification is received from the application management server 6 to the application usage history DB 55.
- the application download server 4 is accessed by selecting the normal banner, and the application is downloaded and installed after user confirmation.
- the charging history DB 61 of the application management server 6 is referred to, and the user of the terminal device 1 (by the user ID accompanying the banner request)
- the application list may be acquired in descending order of (specific) billing amount. Thereby, priority can be given to an app that the user has enthusiastically invested in the past as a target app for displaying a retention banner, and an improvement in sales after recalling can be expected.
- the charging history DB 61 of the application management server 6 is referred to, and the charging amount of the user of the terminal device 1 (specified by the user ID accompanying the banner request) is taken into consideration. Then, the order of the applications (application IDs) in the application list may be changed. For example, the order is re-determined with a value after adding a value obtained by multiplying the charge amount by a coefficient to the elapsed period. In this case as well, an app that the user has enthusiastically invested in the past can be given priority as an app to display a retention banner, and an improvement in sales after recalling can be expected.
- the reward is given to the corresponding application 12 only when the retention banner displayed on the terminal device 1 is selected (tapped or clicked). Without the selection, a reward may be given when the corresponding application 12 is activated later (for example, the description of the retention banner is “1000 CP Change to "Get!).
- the terminal device 1 displaying the retention banner on the advertisement / user management server 5 side is stored in association with the banner ID, so that the reward content is returned when the application management server 6 receives a reward inquiry. can do.
- the date and time at which the banner selection notification (steps S111 and S211) is received is stored together (steps S112 and S212), and the above date and time is referred to in the confirmation for the reward inquiry (steps S120 and S220).
- the reward may be given only when the period is within a preset period (for example, 24 hours) from the banner selection.
- FIGS. 14 and 17 have been described mainly with respect to the case where the processing is performed by the advertisement / user management server 5, but the application 11 of the terminal device 1 is the advertisement / user management server 5 or Necessary information (for example, application usage history information, billing history information, etc.) can be acquired from the management server 6 and main processing can be performed in the application 11.
- Necessary information for example, application usage history information, billing history information, etc.
- ⁇ Summary> As described above, according to the present embodiment, a user who has stopped using an app executed on a terminal device can be recalled, and the continuation rate of the use of the app can be improved.
Abstract
Description
図1は本発明の一実施形態にかかるシステムの構成例を示す図である。なお、アプリとしては主にゲームアプリを想定しているが、ゲームアプリ以外のアプリにも適用できることは言うまでもない。
図14は上記の実施形態の処理例を示すシーケンス図である。
以上説明したように、本実施形態によれば、端末装置上で実行されるアプリの利用が途絶えてしまったユーザを呼び戻すことができ、アプリの利用の継続率を向上させることができる。
11、12 アプリ
2 アクセスポイント
3 ネットワーク
4 アプリダウンロードサーバ
5 広告・ユーザ管理サーバ
51 ユーザ管理DB
52 アプリ優先ポイントDB
53 アプリ除外リストDB
54 バナー表示履歴DB
55 アプリ利用履歴DB
56 バナー選択テーブル
57 バナーDB
6 アプリ管理サーバ
61 課金履歴DB
Claims (11)
- 端末装置で実行される第1のアプリケーションプログラムから前記端末装置のユーザを特定するユーザIDを伴うバナー要求を受け付けるバナー要求受付手段と、
前記ユーザIDに基づいて当該ユーザIDにより特定されるユーザの任意のアプリケーションプログラムについての利用履歴を参照し、最終起動から所定期間を経過した第2のアプリケーションプログラムを選択するアプリケーションプログラム選択手段と、
選択した第2のアプリケーションプログラムに対応する、当該第2のアプリケーションプログラムの再度の利用を促す広告情報を前記端末装置に送信し、前記第1のアプリケーションプログラムの画面上に前記広告情報を表示させる広告情報送信手段と
を備えたことを特徴とするサーバ装置。 - 請求項1に記載のサーバ装置において、
前記広告情報の選択により、当該広告情報に含まれる記述により起動された前記第2のアプリケーションプログラムからログインを受け付けた場合に、前記広告情報に対応付けられたリワードの付与を指示する手段
を備えたことを特徴とするサーバ装置。 - 請求項1に記載のサーバ装置において、
前記広告情報の表示の後に、前記第2のアプリケーションプログラムからログインを受け付けた場合に、前記広告情報に対応付けられたリワードの付与を指示する手段
を備えたことを特徴とするサーバ装置。 - 請求項2または3のいずれか一項に記載のサーバ装置において、
前記リワードは、前記第2のアプリケーションプログラムの最終起動からの所定期間が長いほど高い価値が設定される
ことを特徴とするサーバ装置。 - 請求項1乃至4のいずれか一項に記載のサーバ装置において、
アプリケーションプログラム毎の優先ポイントの高い順にアプリケーションプログラムのリストを取得するリスト取得手段
を備え、
前記アプリケーションプログラム選択手段は、前記リストの上位のアプリケーションプログラムから前記第2のアプリケーションプログラムを選択する
ことを特徴とするサーバ装置。 - 請求項1乃至4のいずれか一項に記載のサーバ装置において、
前記ユーザIDにより特定されるユーザによるアプリケーションプログラムの最終起動からの所定期間が長い順にアプリケーションプログラムのリストを取得するリスト取得手段
を備え、
前記アプリケーションプログラム選択手段は、前記リストの上位のアプリケーションプログラムから前記第2のアプリケーションプログラムを選択する
ことを特徴とするサーバ装置。 - 請求項1乃至4のいずれか一項に記載のサーバ装置において、
前記ユーザIDにより特定されるユーザによるアプリケーションプログラムの過去の課金額が大きい順にアプリケーションプログラムのリストを取得するリスト取得手段
を備え、
前記アプリケーションプログラム選択手段は、前記リストの上位のアプリケーションプログラムから前記第2のアプリケーションプログラムを選択する
ことを特徴とするサーバ装置。 - 請求項5または6のいずれか一項に記載のサーバ装置において、
前記ユーザIDにより特定されるユーザによるアプリケーションプログラムの過去の課金額の大きさを前記リストの順位に反映させるリスト変更手段
を備えたことを特徴とするサーバ装置。 - 請求項1乃至8のいずれか一項に記載のサーバ装置において、
前記第2のアプリケーションプログラムの選択元となるアプリケーションプログラムから、広告情報の対象としないアプリケーションプログラムを除外する手段
を備えたことを特徴とするサーバ装置。 - 請求項1乃至9のいずれか一項に記載のサーバ装置において、
前記第2のアプリケーションプログラムの選択元となるアプリケーションプログラムから、前記ユーザIDにより特定されるユーザに対して直近の所定期間内に所定数の表示を行った広告情報の対象としたアプリケーションプログラムを除外する手段
を備えたことを特徴とするサーバ装置。 - サーバ装置を構成するコンピュータを、
端末装置で実行される第1のアプリケーションプログラムから前記端末装置のユーザを特定するユーザIDを伴うバナー要求を受け付けるバナー要求受付手段、
前記ユーザIDに基づいて当該ユーザIDにより特定されるユーザの任意のアプリケーションプログラムについての利用履歴を参照し、最終起動から所定期間を経過した第2のアプリケーションプログラムを選択するアプリケーションプログラム選択手段と、
選択した第2のアプリケーションプログラムに対応する、当該第2のアプリケーションプログラムの再度の利用を促す広告情報を前記端末装置に送信し、前記第1のアプリケーションプログラムの画面上に前記広告情報を表示させる広告情報送信手段
として機能させるサーバプログラム。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/442,423 US20160275560A1 (en) | 2012-11-15 | 2013-10-29 | Server apparatus and server program |
EP13855602.2A EP2922007A4 (en) | 2012-11-15 | 2013-10-29 | SERVER DEVICE AND SERVER PROGRAM |
KR1020157012872A KR101782918B1 (ko) | 2012-11-15 | 2013-10-29 | 서버 장치 및 서버 프로그램이 기록된 기록매체 |
CN201380059954.3A CN104903927A (zh) | 2012-11-15 | 2013-10-29 | 服务器装置及服务器程序 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012251652A JP5522236B2 (ja) | 2012-11-15 | 2012-11-15 | サーバ装置およびサーバプログラム |
JP2012-251652 | 2012-11-15 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014077123A1 true WO2014077123A1 (ja) | 2014-05-22 |
Family
ID=50731041
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2013/079300 WO2014077123A1 (ja) | 2012-11-15 | 2013-10-29 | サーバ装置およびサーバプログラム |
Country Status (6)
Country | Link |
---|---|
US (1) | US20160275560A1 (ja) |
EP (1) | EP2922007A4 (ja) |
JP (1) | JP5522236B2 (ja) |
KR (1) | KR101782918B1 (ja) |
CN (1) | CN104903927A (ja) |
WO (1) | WO2014077123A1 (ja) |
Families Citing this family (46)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101782512B1 (ko) | 2013-03-28 | 2017-09-28 | 가부시키가이샤 코나미 데지타루 엔타테인멘토 | 관리 장치, 관리 방법, 단말 장치, 제어 방법 및 프로그램 |
JP6403148B2 (ja) * | 2013-06-28 | 2018-10-10 | 株式会社コナミデジタルエンタテインメント | 端末装置、制御方法、及びプログラム |
JP6403149B2 (ja) * | 2013-06-28 | 2018-10-10 | 株式会社コナミデジタルエンタテインメント | 管理装置、管理方法、プログラム、及び管理システム |
WO2014207958A1 (ja) | 2013-06-28 | 2014-12-31 | 株式会社コナミデジタルエンタテインメント | 管理装置、管理方法、端末装置、制御方法及びプログラム |
JP6343764B2 (ja) * | 2013-06-28 | 2018-06-20 | 株式会社コナミデジタルエンタテインメント | 端末装置、制御方法、及びプログラム |
JP6402400B2 (ja) * | 2013-06-28 | 2018-10-10 | 株式会社コナミデジタルエンタテインメント | 管理装置、管理方法、プログラム、及び管理システム |
JP5895287B2 (ja) * | 2013-10-15 | 2016-03-30 | カイト株式会社 | 広告配信システム、装置、方法、及びコンピュータプログラム |
US10937062B1 (en) * | 2014-03-12 | 2021-03-02 | Groupon, Inc. | Method and system for facilitating download of application programs on mobile computing device |
US11010793B1 (en) * | 2014-03-12 | 2021-05-18 | Groupon, Inc. | Method and system for determining user profile data for promotion and marketing service using mobile application program information |
US10846749B1 (en) * | 2014-03-12 | 2020-11-24 | Groupon, Inc. | Method and system for offering promotion impressions using application programs |
US10891651B1 (en) * | 2014-03-12 | 2021-01-12 | Groupon, Inc. | Method and system for launching application programs using promotion impressions |
US11042904B1 (en) * | 2014-03-12 | 2021-06-22 | Groupon, Inc. | Method and system for detecting application programs on mobile computing device |
US20150379559A1 (en) * | 2014-06-30 | 2015-12-31 | Google Inc. | Application installation conversion and identification |
JP6413175B2 (ja) * | 2014-08-27 | 2018-10-31 | 株式会社コナミデジタルエンタテインメント | 管理装置、端末装置、管理システム、制御方法、およびプログラム |
KR101717470B1 (ko) * | 2015-01-07 | 2017-03-21 | 엔에이치엔엔터테인먼트 주식회사 | 모바일 어플리케이션의 프로모션 플랫폼 제공 방법 및 시스템 |
JP2016149107A (ja) * | 2015-02-10 | 2016-08-18 | 株式会社アドウェイズ | サ−バ |
JP5884928B1 (ja) * | 2015-02-27 | 2016-03-15 | 株式会社セガゲームス | 端末プログラム、サーバプログラム、端末装置、サーバ装置および情報システム |
JP6043838B2 (ja) * | 2015-06-04 | 2016-12-14 | ヤフー株式会社 | 配信装置、配信方法、及び配信プログラム |
JP6005215B2 (ja) * | 2015-06-04 | 2016-10-12 | ヤフー株式会社 | 配信装置、配信方法、及び配信プログラム |
JP6307044B2 (ja) * | 2015-06-05 | 2018-04-04 | ヤフー株式会社 | 端末装置、選択方法、及び選択プログラム |
JP6087984B2 (ja) * | 2015-06-05 | 2017-03-01 | ヤフー株式会社 | 配信装置、配信方法、及び配信プログラム |
US20170004524A1 (en) * | 2015-06-30 | 2017-01-05 | Yahoo! Inc. | Systems and Methods For Mobile Campaign Optimization Without Knowing User Identity |
JP5996733B1 (ja) * | 2015-07-07 | 2016-09-21 | ヤフー株式会社 | 配信装置、配信方法、及び配信プログラム |
JP6059304B1 (ja) * | 2015-07-23 | 2017-01-11 | Kddi株式会社 | 通信端末、情報提供システム、情報提供方法、及び情報提供プログラム |
TWI707286B (zh) | 2015-08-21 | 2020-10-11 | 新加坡商萬事達卡亞洲/太平洋私人有限公司 | 修改交易憑證的方法及系統,伺服器及非暫時性計算機可讀取媒體 |
CN107924519B (zh) * | 2015-09-17 | 2022-03-08 | 工合线上娱乐株式会社 | 横幅广告信息生成方法、服务器装置及存储介质 |
JP5999396B1 (ja) * | 2015-09-24 | 2016-09-28 | 株式会社セガゲームス | 情報処理システム及びプログラム |
KR101745665B1 (ko) * | 2015-11-23 | 2017-06-20 | 주식회사 테크노블러드코리아 | 모바일 컨텐츠 제공 방법 |
JP6337401B2 (ja) * | 2015-12-24 | 2018-06-06 | カイト株式会社 | 広告配信システム用管理サーバ、広告配信方法、及びコンピュータプログラム |
KR102652003B1 (ko) * | 2015-12-31 | 2024-03-29 | 주식회사 넥슨코리아 | 게임 아이템을 이용한 광고 시스템 및 그 방법 |
JP6069552B2 (ja) * | 2016-02-01 | 2017-02-01 | ヤフー株式会社 | 配信装置、配信方法、及び配信プログラム |
JP6043882B1 (ja) * | 2016-02-01 | 2016-12-14 | ヤフー株式会社 | 配信装置、配信方法、及び配信プログラム |
JP5926872B1 (ja) * | 2016-02-01 | 2016-05-25 | ヤフー株式会社 | 配信装置、配信方法、及び配信プログラム |
JP5996813B1 (ja) * | 2016-02-01 | 2016-09-21 | ヤフー株式会社 | 配信装置、配信方法、及び配信プログラム |
JP6068696B1 (ja) * | 2016-02-01 | 2017-01-25 | ヤフー株式会社 | 配信装置、配信方法、及び配信プログラム |
JP6530363B2 (ja) | 2016-12-09 | 2019-06-12 | 株式会社バンダイナムコエンターテインメント | コンピュータシステム、ゲームシステム及びゲーム装置 |
JP6549089B2 (ja) * | 2016-12-09 | 2019-07-24 | 株式会社バンダイナムコエンターテインメント | コンピュータシステム、ゲームシステム及びゲーム装置 |
JP6393377B1 (ja) * | 2017-07-24 | 2018-09-19 | ユニティガードシステム株式会社 | ロボット、情報提供方法及び情報提供システム |
JP6317022B2 (ja) * | 2017-09-06 | 2018-04-25 | 株式会社コナミデジタルエンタテインメント | 端末装置、管理装置、およびプログラム |
JP6402410B2 (ja) * | 2018-03-27 | 2018-10-10 | 株式会社コナミデジタルエンタテインメント | 端末装置、およびプログラム |
JP6440052B2 (ja) * | 2018-06-25 | 2018-12-19 | 株式会社ドリコム | リソース管理システム、システムの制御方法及びシステム用プログラム |
KR101950001B1 (ko) * | 2018-08-31 | 2019-02-20 | 넷마블 주식회사 | 게임 어플리케이션 이외의 어플리케이션을 통한 제어에 기초하여 게임 서비스를 제공하는 서버 및 방법 |
JP7012636B2 (ja) * | 2018-12-17 | 2022-01-28 | 株式会社バンダイナムコエンターテインメント | コンピュータシステム、ゲームシステム及びゲーム装置 |
KR20210112900A (ko) * | 2020-03-06 | 2021-09-15 | 삼성전자주식회사 | 사용자 정보를 이용한 광고 방법 및 그 장치 |
EP4229580A1 (en) * | 2020-10-16 | 2023-08-23 | Catalina Marketing Corporation | Enabling digital advertising identifier consent conversion for tracking across different applications |
US20230394522A1 (en) * | 2022-06-03 | 2023-12-07 | Apple Inc. | Privacy preserving data sharing for campaigns using hierarchical campaign identifiers |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000029712A (ja) | 1998-07-15 | 2000-01-28 | Sony Corp | アミューズメント機器用広告配信方法とこれを使用した広告配信システム |
JP2002140595A (ja) * | 2000-10-31 | 2002-05-17 | Pfu Ltd | ポイント管理方法、ポイント管理システム、および記録媒体 |
JP2004302759A (ja) * | 2003-03-31 | 2004-10-28 | Masayuki Matsui | ストレージ貸出請求システム、及び記録媒体請求システム、及びプログラム |
JP2005037757A (ja) * | 2003-07-17 | 2005-02-10 | Nec Corp | 広告配信システム、端末およびサーバ |
JP2008036241A (ja) * | 2006-08-08 | 2008-02-21 | Sega Corp | ランキング設定システム |
JP2009070021A (ja) * | 2007-09-12 | 2009-04-02 | Nec Corp | 販売店情報表示システム、携帯情報端末、販売店情報表示方法、および販売店情報表示プログラム |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002109079A (ja) * | 2000-09-29 | 2002-04-12 | Casio Comput Co Ltd | 教育支援方法および支援サーバ |
US20070072676A1 (en) * | 2005-09-29 | 2007-03-29 | Shumeet Baluja | Using information from user-video game interactions to target advertisements, such as advertisements to be served in video games for example |
JP2007244503A (ja) * | 2006-03-14 | 2007-09-27 | Aruze Corp | サーバ及びゲームシステム |
US20080004954A1 (en) * | 2006-06-30 | 2008-01-03 | Microsoft Corporation | Methods and architecture for performing client-side directed marketing with caching and local analytics for enhanced privacy and minimal disruption |
US9959547B2 (en) * | 2008-02-01 | 2018-05-01 | Qualcomm Incorporated | Platform for mobile advertising and persistent microtargeting of promotions |
US20090299817A1 (en) * | 2008-06-03 | 2009-12-03 | Qualcomm Incorporated | Marketing and advertising framework for a wireless device |
CN101383033A (zh) * | 2008-09-23 | 2009-03-11 | 腾讯科技(深圳)有限公司 | 网络游戏中发布网络广告的方法、系统、服务器和客户端 |
JP2012014443A (ja) * | 2010-06-30 | 2012-01-19 | Ntt Docomo Inc | 配信サーバ及び方法 |
JP2012181797A (ja) * | 2011-03-03 | 2012-09-20 | Nec Casio Mobile Communications Ltd | 携帯端末、及びプログラム |
US8688726B2 (en) * | 2011-05-06 | 2014-04-01 | Microsoft Corporation | Location-aware application searching |
-
2012
- 2012-11-15 JP JP2012251652A patent/JP5522236B2/ja active Active
-
2013
- 2013-10-29 KR KR1020157012872A patent/KR101782918B1/ko active IP Right Grant
- 2013-10-29 WO PCT/JP2013/079300 patent/WO2014077123A1/ja active Application Filing
- 2013-10-29 US US14/442,423 patent/US20160275560A1/en not_active Abandoned
- 2013-10-29 CN CN201380059954.3A patent/CN104903927A/zh active Pending
- 2013-10-29 EP EP13855602.2A patent/EP2922007A4/en not_active Withdrawn
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2000029712A (ja) | 1998-07-15 | 2000-01-28 | Sony Corp | アミューズメント機器用広告配信方法とこれを使用した広告配信システム |
JP2002140595A (ja) * | 2000-10-31 | 2002-05-17 | Pfu Ltd | ポイント管理方法、ポイント管理システム、および記録媒体 |
JP2004302759A (ja) * | 2003-03-31 | 2004-10-28 | Masayuki Matsui | ストレージ貸出請求システム、及び記録媒体請求システム、及びプログラム |
JP2005037757A (ja) * | 2003-07-17 | 2005-02-10 | Nec Corp | 広告配信システム、端末およびサーバ |
JP2008036241A (ja) * | 2006-08-08 | 2008-02-21 | Sega Corp | ランキング設定システム |
JP2009070021A (ja) * | 2007-09-12 | 2009-04-02 | Nec Corp | 販売店情報表示システム、携帯情報端末、販売店情報表示方法、および販売店情報表示プログラム |
Non-Patent Citations (2)
Title |
---|
See also references of EP2922007A4 * |
THE STOCK RESEARCH CENTER: "HOLISTIC KIGYO REPORT DRECOM (3793 TOSHO MOTHERS)", 5 June 2012, article SHIGEKI KOSAKA, pages: 3, XP055207108 * |
Also Published As
Publication number | Publication date |
---|---|
JP5522236B2 (ja) | 2014-06-18 |
KR20150086269A (ko) | 2015-07-27 |
EP2922007A4 (en) | 2015-11-25 |
KR101782918B1 (ko) | 2017-09-28 |
JP2014099111A (ja) | 2014-05-29 |
US20160275560A1 (en) | 2016-09-22 |
EP2922007A1 (en) | 2015-09-23 |
CN104903927A (zh) | 2015-09-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5522236B2 (ja) | サーバ装置およびサーバプログラム | |
KR101711520B1 (ko) | 서버 장치 및 서버 프로그램이 기록된 기록매체 | |
JP5931438B2 (ja) | 無線デバイスのためのマーケティング及び広告フレームワーク | |
CN103930871B (zh) | 基于安装历史给移动设备推荐应用 | |
US20140114901A1 (en) | System and method for recommending application resources | |
JP6022215B2 (ja) | 投稿情報共有システム、情報処理システム、情報処理方法、プログラムおよびコンピュータプラットフォーム | |
KR101907120B1 (ko) | 서버 장치, 및 서버 프로그램 및 게임 프로그램의 기록매체 | |
US10410241B1 (en) | Swipe screen advertisement metrics and tracking | |
US20140244762A1 (en) | Application distribution platform for rating and recommending applications | |
WO2011159469A2 (en) | Context-influenced application recommendations | |
US8744971B2 (en) | Dynamic redemption codes | |
CN104871200A (zh) | 游戏奖励提供装置和游戏奖励提供用程序 | |
KR101315861B1 (ko) | 어플리케이션 제공과 보상을 통합 관리하는 모바일 광고 시스템 및 모바일 광고 방법 | |
CN106131614A (zh) | 一种多媒体文件播放处理方法、装置及服务器 | |
CN109861903B (zh) | 一种基于app应用的链接发送方法及装置 | |
KR101398099B1 (ko) | 광고를 제공하는 방법, 서버 및 단말 | |
US20170364966A1 (en) | Determination device, determination method, and non-transitory computer-readable recording medium | |
CN108279915A (zh) | 应用程序的升级方法、装置和终端 | |
US10721319B1 (en) | System and method of targeting internet protocol (IP) notifications to mobile communication devices | |
JP2015053009A (ja) | アプリケーション販促装置、アプリケーション販促システム、アプリケーション販促方法、及びアプリケーション販促プログラム | |
US20240053972A1 (en) | Systems and methods for generating enquiries and responses based on application metadata | |
JP2013250746A (ja) | サーバ装置、情報処理方法、プログラムおよび情報処理システム | |
KR102044745B1 (ko) | 게임 프레즌스 정보를 이용한 게임 제공 방법, 이를 위한 장치 및 이를 위한 시스템 | |
WO2016038989A1 (ja) | サーバ装置およびサーバプログラム | |
CN117298602A (zh) | 一种平台信息的推送方法、装置、电子设备及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13855602 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14442423 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 20157012872 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2013855602 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2013855602 Country of ref document: EP |