JP7728641B2 - User traffic tracking method and system - Google Patents

Description

The following description relates to a user traffic tracking method and system.

Technology exists in which a single platform registers and provides multiple external services. For example, by registering multiple external game services on a single game platform and providing common functions, developers of the external game services can focus on developing core game services. For example, Patent Document 1 (Patent Document 1) relates to a network-based game platform system, and discloses a network-based game platform system including a platform server, multiple game company servers connected to the platform server via a network and registering game content to the server, multiple game terminals connected to the platform server via a network and playing online games using the registered game content, advertiser servers connected to the platform server via a network and registering advertising content, and a currency management server that issues currency used by the game company servers, game terminals, and advertiser servers.

Korean Patent Publication No. 10-2018-0115561

We provide a method and system for tracking user traffic that generates reward URLs corresponding to predefined conditions in relation to external services registered on the platform, and can provide rewards to users who access the platform via the reward URL depending on whether the predefined conditions are met.

A user flow tracking method for a computer device including at least one processor is provided, the method comprising the steps of: registering an external service by the at least one processor; generating a reward URL (Uniform Resource Locator) corresponding to predefined conditions associated with the external service by the at least one processor; receiving a user key associated with the external service from an electronic device that accesses the external service via the reward URL; and determining a reward for the user identified by the user key depending on whether the user satisfies the predefined conditions by the at least one processor.

According to one aspect, the step of generating the reward URL may be characterized by recording conditions related to a target of use of the reward URL in association with the reward URL as the predefined conditions , and the step of determining the reward may be characterized by comparing profile information of the user with the conditions related to a target of use of the reward URL to determine the reward for the user identified by the user key.

According to another aspect, the conditions related to the target of use of the reward URL may include at least one of a user personal information-related condition including age, gender, or location, a group-related condition regarding whether the user is included in a specific group among groups into which users are divided on the platform implemented by the computer device, or an item-related condition regarding whether there is a purchase history of a specific item related to the platform.

According to another aspect, the generating of the reward URL may include recording, as the predefined condition, a condition related to a predefined activity performed in connection with the external service in association with the reward URL , and the determining of the reward may include receiving, using the received user key, activity information of the user identified by the user key from the external service associated with the reward URL , and comparing the received activity information with the predefined activity condition recorded in association with the reward URL to determine a reward for the user identified by the user key.

According to another aspect, the predefined activity may include at least one of an access activity to the external service and a predefined activity within the external service.

According to another aspect, the generating of the reward URL may include recording, as the predefined condition , a condition related to a predefined mission performed in connection with the external service in association with the reward URL; the user inflow tracking method may further include, by the at least one processor, granting the mission to a user identified by the user key; and determining the reward may include, using the received user key, monitoring whether the user completes the mission in the external service associated with the reward URL, and determining a reward for the user if the user completes the mission.

According to another aspect, the generating of the reward URL may include recording application-related information related to the external service in association with the reward URL as the predefined condition; the receiving of the user key may further receive, from the electronic device, application information installed on the electronic device in association with the external service; and the providing of the reward may include comparing the received application information with the application-related condition recorded in association with the reward URL to determine the reward for the user identified by the user key.

In another aspect, the application-related information may include information regarding at least one of whether an application related to the external service is installable, when the application is executed, and the number of times the application is executed.

In another aspect, the step of generating the reward URL may be characterized in that the reward URL is generated as a continuously usable type or a single-use type, and the step of determining the reward may be characterized in that, if the reward URL is a single-use type reward URL, the reward URL is recorded as having been used, and the re-use of the single-use type reward URL is restricted.

According to another aspect, the step of receiving the user key may include providing a landing page corresponding to the reward URL to the electronic device of the user who accesses the electronic device via the reward URL, and receiving a user key associated with the application from the electronic device by executing an application for the external service installed on the electronic device in response to input on the landing page.

A computer program is provided that is recorded on a computer-readable recording medium and that, when combined with a computer device, causes the computer device to execute the method.

A program for causing a computer device to execute the user flow tracking method is provided.
A computer-readable recording medium is provided, on which a program for causing a computer device to execute the user inflow tracking method is recorded.

A computer device is provided, comprising at least one processor implemented to execute computer-readable instructions, wherein the at least one processor registers an external service, generates a reward URL (Uniform Resource Locator) corresponding to a predefined condition associated with the external service, receives a user key associated with the external service from a user's electronic device that accesses the external service via the reward URL, and determines a reward for the user identified by the user key depending on whether the predefined condition is met.

Reward URLs corresponding to predefined conditions are generated in relation to external services registered on the platform, and rewards can be provided to users who access the external service corresponding to the reward URL by accessing it via the reward URL depending on whether the predefined conditions are met.

By setting predefined conditions related to the use of the reward URL, users can be targeted in real time.

The predefined conditions may be set to conditions related to predefined activities performed in connection with an external service, and the platform may provide rewards to the user based on the user's activities in the external service by receiving the user's activity information from the external service using a user key associated with the user's external service accessed via a reward URL.

As the predefined conditions, conditions regarding a predefined mission to be performed in connection with an external service are set, and the mission is granted to a user who accesses via a reward URL. After that, by monitoring whether the user completes the mission in the external service using a user key, a reward can be provided depending on whether the user completes the mission.

As predefined conditions, application-related conditions related to external services can be set, and information about the application can be received from users who access the application via a reward URL and compared with the set conditions , thereby providing rewards based on the user's usage record in the application.

FIG. 1 illustrates an example of a network environment in accordance with an embodiment of the present invention. FIG. 1 is a block diagram illustrating an example of a computing device according to an embodiment of the present invention. 1 is an exemplary diagram illustrating the overall structure of a user inflow tracking system according to an embodiment of the present invention; 1 is a flowchart illustrating an example method for tracking user inflows, according to one embodiment of the present invention. FIG. 10 illustrates an example of a user interface displaying a generated reward URL in accordance with one embodiment of the present invention.

The following describes the embodiments in detail with reference to the attached drawings.

A user inflow tracking system according to an embodiment of the present invention may be realized by at least one computer device, and a user inflow tracking method according to an embodiment of the present invention may be executed by at least one computer device included in the user inflow tracking system. In this case, a computer program according to an embodiment of the present invention may be installed and executed in the computer device, and the computer device may execute the user inflow tracking method according to an embodiment of the present invention under the control of the executed computer program. The above-mentioned computer program may be recorded on a computer-readable recording medium in combination with the computer device to cause the computer to execute the user inflow tracking method.

Figure 1 is a diagram showing an example of a network environment in one embodiment of the present invention. The network environment in Figure 1 shows an example including multiple electronic devices 110, 120, 130, 140, multiple servers 150, 160, and a network 170. Figure 1 is merely an example for explaining the invention, and the number of electronic devices and the number of servers are not limited to those shown in Figure 1. Furthermore, the network environment in Figure 1 is merely an example of an environment applicable to this embodiment, and the environment applicable to this embodiment is not limited to the network environment in Figure 1.

The electronic devices 110, 120, 130, and 140 may be fixed or mobile terminals implemented as computer devices. Examples of the electronic devices 110, 120, 130, and 140 include smartphones, mobile phones, navigation systems, personal computers (PCs), notebook PCs, digital broadcasting terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), and tablets. While FIG. 1 illustrates a smartphone as an example of the electronic device 110, in embodiments of the present invention, the electronic device 110 may refer to one of a variety of physical computer devices capable of communicating with other electronic devices 120, 130, and 140 and/or servers 150 and 160 via a network 170 using substantially wireless or wired communication methods.

The communication method is not limited, and may include not only communication methods using communication networks (for example, mobile communication networks, wired Internet, wireless Internet, and broadcast networks) that network 170 can include, but also short-range wireless communication between devices. For example, network 170 may include one or more of the following networks: a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BBN), and the Internet. Furthermore, network 170 may include any one or more of the following network topologies, including, but not limited to, a bus network, a star network, a ring network, a mesh network, a star-bus network, a tree network, or a hierarchical network.

Each of the servers 150, 160 may be realized by one or more computing devices that communicate with multiple electronic devices 110, 120, 130, 140 via the network 170 to provide instructions, code, files, content, services, etc. For example, the server 150 may be a system that provides services (e.g., gaming services, group calling services (or audio conferencing services), messaging services, email services, social networking services, map services, translation services, financial services, payment services, search services, content provision services, etc.) to multiple electronic devices 110, 120, 130, 140 connected via the network 170.

Figure 2 is a block diagram showing an example of a computer device in one embodiment of the present invention. Each of the multiple electronic devices 110, 120, 130, and 140 and each of the servers 150 and 160 described above may be realized by the computer device 200 shown in Figure 2.

As shown in FIG. 2, such a computer device 200 may include a memory 210, a processor 220, a communication interface 230, and an input/output interface 240. The memory 210 is a computer-readable recording medium and may include RAM (random access memory), ROM (read only memory), and a persistent mass storage device such as a disk drive. Here, a persistent mass storage device such as a ROM or a disk drive may be included in the computer device 200 as a separate persistent storage device distinct from the memory 210. The memory 210 may also store an operating system and at least one program code. Such software components may be loaded into the memory 210 from a computer-readable recording medium separate from the memory 210. Such separate computer-readable recording medium may include a computer-readable recording medium such as a floppy drive, a disk, a tape, a DVD/CD-ROM drive, or a memory card. In other embodiments, software components may be loaded into memory 210 through a communication interface 230 that is not a computer-readable recording medium. For example, software components may be loaded into memory 210 of computer device 200 based on a computer program that is installed by a file received over network 170.

Processor 220 may be configured to process computer program instructions by performing basic arithmetic, logic, and input/output operations. The instructions may be provided to processor 220 by memory 210 or communication interface 230. For example, processor 220 may be configured to execute instructions received according to program code stored in a storage device such as memory 210.

The communication interface 230 may provide a function for the computer device 200 to communicate with other devices (such as the above-mentioned storage device) via the network 170. For example, requests, instructions, data, files, etc. generated by the processor 220 of the computer device 200 in accordance with program code stored in a storage device such as the memory 210 may be transmitted to other devices via the network 170 under the control of the communication interface 230. Conversely, signals, instructions, data, files, etc. from other devices may be received by the computer device 200 via the communication interface 230 of the computer device 200 via the network 170. For example, signals, instructions, data, etc. received via the communication interface 230 may be transmitted to the processor 220 or the memory 210, and files, etc. may be recorded on a storage medium (such as the above-mentioned permanent storage device) that the computer device 200 may further include.

The input/output interface 240 may be a means for interfacing with the input/output devices 250. For example, the input devices may include devices such as a microphone, keyboard, and mouse, while the output devices may include devices such as a display and speakers. As another example, the input/output interface 240 may be a means for interfacing with a device that integrates input and output functions into one, such as a touchscreen. At least one of the input/output devices 250 may be configured as a single device together with the computer device 200. For example, like a smartphone, the touchscreen, microphone, speaker, and other components may be included in the computer device 200.

Also, in other embodiments, the computing device 200 may include fewer or more components than those shown in FIG. 2. However, it is not necessary to explicitly illustrate most of the prior art components. For example, the computing device 200 may be implemented to include at least some of the input/output devices 250 described above, and may further include other components such as a transceiver, a database, etc.

Figure 3 is an exemplary diagram showing the overall structure of a user inflow tracking system in one embodiment of the present invention. Figure 3 shows a service platform 310, a client 320, and an external service server 330. In reality, the service platform 310 can communicate with multiple clients and multiple external service servers, but for convenience of explanation, the embodiment of Figure 3 shows only one client 320 and one external service server 330. The explanations for the client 320 and the external service server 330 may be applied in the same or similar manner to multiple clients and multiple external service servers communicating with the service platform 310.

In this specification, "external services" may refer to services other than those directly provided by service platform 310. For example, external services may include services operated by an entity other than the entity that operates service platform 310, as well as other services provided by the entity that operates service platform 310.

The service platform 310 may provide various services to the client 320, and may register external services in conjunction with the external service server 330 to provide the external services to the client 320. For example, a service platform 310 that provides game services may create an environment in which games (external services) created by multiple game companies can be used by a large number of users (clients) over a network.

In each of the user's electronic devices in which the client 320 is implemented, an external service application 321 can be installed and executed to receive external services from the external service server 330. While receiving external services, the client can link with the service platform 310 via the service platform SDK 322 and use the functions of the service platform 310.

The external service server 330 may be implemented to provide a corresponding external service to a user who accesses it via the external service application 321. In this case, the system for identifying a user in the service platform 310 and the system for identifying a user in the external service server 330 may be different. As a result, it has been difficult for existing service platforms to understand how a user has accessed an external service provided by the external service server 330, what activities the user has performed, or what activities the user has performed in the external service.

As a result, the service platform 310 according to this embodiment can use the reward URL (Uniform Resource Locator) to track how a user accesses an external service provided by the external service server 330 and what activities the user performs on the external service, and provide rewards accordingly.

In the first step 341, the service platform 310 may generate a reward URL. Such a reward URL may be linked to a specific external service among multiple external services registered with the service platform 310, and may be generated in response to predefined conditions associated with the specific external service. The predefined conditions may be used to determine whether to provide a reward to a user who accesses the service platform 310 via the reward URL.

Meanwhile, the reward URL may be generated as a public type that can be used by any user of the external service, or as a unique type that can be used by only a portion of users of the external service. The reward URL may also be generated as a continuous use type or a single use type. A continuous use type reward URL may mean a reward URL that can be used by multiple users by sharing the URL, and a single use type reward URL may mean a reward URL that cannot be used by other users after one user has used the reward URL.

Furthermore, reward URLs may be generated for a certain period of time. In other words, reward URLs that have exceeded the set period may be processed so that the user is no longer able to use the corresponding reward URL. For example, if a particular user clicks on a reward URL that has exceeded the set period of time, the service platform 310 may notify the user that the usage period for the corresponding reward URL has expired and the URL can no longer be used.

Meanwhile, the reward URL may be implemented in the form of a deep link. A deep link is a common term for a link that can reach a specific page, and is a URL format consisting of a scheme and a host. As it is a type of link, it can be easily adapted to and used in a web environment like other links.

In the second step 342, the service platform 310 may distribute the reward URL. The service platform 310 may distribute the reward URL through a predetermined medium, but it should be readily understood that, depending on the characteristics of the URL, the reward URL can also be freely distributed via SNS (Social Network Service), instant messaging, etc.

In the third step 343, the client 320 provided with the reward URL may select the reward URL. If the client 320 is provided with a reward URL distributed through various media or routes and selects the reward URL through user input, the client 320 can access the service platform 310 via the address included in the reward URL.

In a fourth step 344, the service platform 310 may receive URL information. In this case, the service platform may identify the reward URL through which the client 320 accessed. As described above, the reward URL may be generated in association with a specific external service and may correspond to predefined conditions associated with the external service. In this case, the service platform 310 may identify the external service associated with the identified reward URL from among multiple external services, and the predefined conditions associated with the external service, by identifying the reward URL identified by the URL information.

In a fifth step 345, the service platform 310 may provide a landing page to the client 320. The landing page may be associated with the reward URL used by the client 320 to access the service platform 310 and, in some embodiments, may include information related to the reward URL. For example, the landing page may include information about conditions associated with the reward URL and rewards to be provided when such conditions are met. It may also include a function for launching an external service associated with the reward URL. Furthermore, the landing page may be set by the external service or may be a page for connecting to the external service server 330. Here, providing a landing page is merely one embodiment. As described below, the external service application 321 may be executed directly as a deep link without providing a landing page, or an application store for installation of the external service application 321 may be provided. Alternatively, a page for the external service application 321 in an application store may be provided instead of a landing page.

In a sixth step 346, the client 320 may display the landing page.

In the seventh step 347, the client 320 may start an external service. For example, based on a user's input to a function for starting an external service associated with a reward URL included in the displayed landing page, the client 320 may execute the external service application 321 to start the external service. At this time, the client 320 may transmit a user key associated with the external service to the service platform 310 via the started external service application 321.

If the reward URL is implemented as a deep link, the client 320 may be controlled to determine whether a Universal Link or App Link is operational on the operating system of the user's electronic device via the deep link. For example, the Universal Link may operate on iOA 9.0 or higher, and the App may operate on Android 6.0 or higher. If the operating system version requirements are met and the external service application 321 is installed on the user's electronic device, the external service application 321 can be immediately executed via the deep link. On the other hand, if the operating system version requirements are not met or the external service application 321 is not installed on the user's electronic device, a landing page may be provided via the deep link, as in step 5 (345). The landing page may first identify the operating system of the user's electronic device using JavaScript. If the operating system is iOS, the landing page may receive a document ready event and execute the external service application 321 using a URL scheme. If the external service application 321 is not installed, the landing page may navigate to an application store and prompt the user to download and install the external service application 321. If the operating system is Android, the landing page may request a user click event. If the user clicks the "Run" button on the landing page, the landing page may check whether a Chrome Intent is running. The Chrome Intent may be executed if the user's browser is Chrome and the browser version is 25 or higher. If these conditions are met and the external service application 321 is installed, the landing page may execute the external service application 321; otherwise, the landing page may use a URL scheme. By using such a deep link, the service platform 310 can direct the user to an external service provided by the external service server 330 via the external service application 321 and track the process.

Alternatively, a deferred deep link (Deeplink) may be used as the reward URL. A deferred deep link is a deep link that is executed deferred. Use of such a deferred deep link can prevent the deep link from being lost when transitioning to an application store to install the external service application 321. Such a deferred deep link can count users who have newly installed the external service application 321 via content linked to the deep link, or can provide content desired by the user simultaneously with the installation of the external service application 321.

In an eighth step 348, the service platform 310 may receive a user key. As described above, the system for identifying a user on the service platform 310 may differ from the system for identifying a user on the external service. Therefore, the service platform 310 can identify the user on the external service by receiving a user key associated with the external service from the client 320.

In a ninth step 349, the service platform 310 may request user activity information from the external service server 330. At this time, the request for user activity information may be made using the user key received from the client 320. Furthermore, the service platform 310 may request only activity information that meets a predefined condition corresponding to the reward URL, rather than requesting all of the user's activity information. For example, if the predefined condition corresponding to the reward URL is that the user achieves level 10, the service platform 310 may request activity information regarding whether the user has achieved level 10 from the external service server 330. In some embodiments, the ninth step 349 may be omitted. For example, assume that the external service server 330 is running a participation reward event in conjunction with the service platform 310. In this case, each time the user participates in an external service, the external service server 330 sends user activity information related to the user's participation to the service platform 310 via an API call. Therefore, in such a case, the service platform 310 can obtain the required user activity information without making a separate request to the external service server 330.

In a tenth step 350, the external service server 330 may send user activity information to the service platform 310. For example, the external service server 330 may identify a user by a user key included in the request from the service platform 310, search for user activity information corresponding to the identified user, and send it to the service platform 310. In this case, the external service server 330 may send specific activity information requested by the service platform 310 to the service platform 310 , among the user activity information.

In an eleventh step 351, the service platform 310 may receive user activity information.

In a twelfth step 352, the service platform 310 may determine a reward for the user. At this time, the service platform 310 may compare the user activity information with predefined conditions and determine a reward for the user identified by the user key depending on whether the user satisfies the predefined conditions.

In the embodiment of FIG. 3, an example was described in which the predefined conditions included information about the user's activities in the external service. As a more specific example, the predefined conditions may be set to include access activities to the external service, such as the number of times the external service was accessed or the time of access, and/or predefined activities in the external service, such as achieving a level in the external service, purchasing a specific item, completing a tutorial, or clearing a specific stage. In this case, whether the predefined conditions are met may be determined by determining whether there is a record of the user having already performed such activities.

In another embodiment, the predefined conditions may include a predefined mission associated with an external service. In this case, whether the predefined conditions are met may be determined by monitoring whether the user has completed the corresponding mission in the external service. In this case, the service platform 310 may monitor whether the user corresponding to the user key has completed the mission via the external service server 330, and may determine a reward for the user according to the mission if the mission has been completed.

In another embodiment, the predefined condition may be a condition related to the use of the reward URL, such as a user personal information-related condition including age, gender, and/or location , a group-related condition regarding whether the user belongs to a specific group among groups into which users are classified on the service platform 310, and/or an item- related condition regarding whether a purchase history exists for a specific item related to the service platform 310. In this case, whether the predefined condition is satisfied may be determined by analyzing profile information of the user accessed via the reward URL. The user profile information may include profile information on the service platform 310 and/or profile information on an external service. The profile information on the external service may be obtained by the service platform 310 communicating with the external service server 330 using the user key.

In another embodiment, the predefined conditions may include whether the user has installed the external service application 321, the time when the external service application 321 is executed, and/or the number of times the external service application 321 is executed. In this case, whether the predefined conditions are met may be determined by receiving and analyzing related information from the user's electronic device. For example, the service platform 310 may determine whether the predefined conditions are met by receiving and analyzing information related to the external service application 321 from the user's electronic device at the time of receiving the user key.

FIG. 4 is a flowchart illustrating an example of a user inflow tracking method according to one embodiment of the present invention. The user inflow tracking method according to this embodiment may be executed by a computer device 200 that implements the above-described service platform 310. In this case, the processor 220 of the computer device 200 may be implemented to execute control instructions from the operating system code and at least one program code contained in the memory 210. Here, the processor 220 may control the computer device 200 to perform steps 410 to 440 of the method of FIG. 4 according to the control instructions provided by the code recorded in the computer device 200.

In step 410, the computer device 200 may register an external service. The computer device 200 may be included in at least one computer device that implements the above-described user platform 310, and may register multiple external services. The computer device 200 may also provide an environment in which a user can use the registered external services via the network 170.

In step 420, the computer device 200 may generate a reward URL corresponding to predefined conditions in association with the external service. For example, the computer device 200 may generate a reward URL in association with a specific external service from among a number of registered external services. In this case, the reward URL may correspond to predefined conditions, and the computer device 200 may record the predefined conditions in association with the corresponding reward URL.

In step 430, the computer device 200 may receive a user key associated with the external service from the electronic device that accesses the external service via the reward URL. Here, the user key may be the same as the user identifier of the user identification system used in the service platform 310, but if different from the user identifier, it may be managed in association with the user identifier. In other words, the computer device 200 can identify both the user of the service platform 310 and the user of the external service using the received user key.

Meanwhile, as one embodiment for directing an electronic device to an external service, the computer device 200 may provide a landing page corresponding to the reward URL to the electronic device that accesses the electronic device via the reward URL, and may execute an application for the external service installed on the electronic device by inputting information on the landing page, directing the user to the external service. In this case, the computer device 200 may receive a user key associated with the application from the electronic device.

In step 440, the computer device 200 may determine a reward for the user identified by the user key depending on whether the user satisfies predefined conditions. Various embodiments may exist depending on the type of predefined conditions, but basically, a reward is provided to a user who accesses the service platform 310 via the reward URL and enters the external service if the user satisfies certain conditions. In other words, the service platform 310 may determine whether the user has entered the external service via the reward URL and whether the conditions are met, and may provide a reward to the user depending on whether the conditions are met. Here, determining the reward for the user may include determining the reward content for the user at the relevant time, or may include linking the reward content preset for the reward URL with the user. In this case, the reward is provided based on marketing at the service platform 310 level, and the reward resource is the service platform 310, not the external service server 330.

In one embodiment, the computer device 200 may associate target -related conditions for use of the reward URL with the reward URL as predefined conditions in step 420. For example, the target-related conditions for use of the reward URL may include user personal information- related conditions, such as age, gender, and/or location; group -related conditions regarding whether the user belongs to a specific group among groups into which users are classified in the service platform 310 implemented by the computer device 200; and/or item-related conditions regarding whether there is a purchase history for a specific item associated with the service platform 310. In this case, the computer device 200 may compare the user's profile information with the target- related conditions for use of the reward URL in step 440 and determine a reward for the user identified by the user key. In other words, the computer device 200 can target users with specific conditions by providing a reward to users with specific conditions. For example, a user who meets the criteria of being a male in his 30s may be provided with a reward by accessing an external service via a reward URL, or a user who purchases a specific item on the service platform 310 may be provided with a reward by accessing an external service via a reward URL.

In another embodiment, the computer device 200 may record, as the predefined condition, a condition related to a predefined activity performed in connection with an external service in association with the reward URL in step 420. For example , the predefined activity may include at least one of accessing the external service and a predefined activity within the external service. More specifically, the predefined condition may be set to activities such as accessing the external service a certain number of times or more, accessing the external service within a certain time period, achieving a level in the external service, purchasing a specific item, completing a tutorial, or clearing a specific stage. In this case, the computer device 200 may receive activity information of the user identified by the user key from the external service associated with the reward URL using the received user key in step 440, and may compare the received activity information with the predefined activity conditions recorded in association with the reward URL to determine a reward for the user identified by the user key. For example, if the activity of achieving level 10 in a game service, which is an external service, is set as a predefined condition, the computer device 200 may check with the external service server 330 whether the corresponding user has achieved level 10 and determine a reward for the user based on the confirmation result. As another example, if the predefined condition is set as accessing the external service 10 or more times, the computer device 200 may check with the external service server 330 whether the corresponding user has accessed the external service 10 or more times and determine a reward for the user based on the confirmation result.

In another embodiment, the computer device 200 may record, as the predefined condition, a condition related to a predefined mission performed in connection with an external service in association with the reward URL in operation 420. In this case, the computer device 200 may dynamically grant the mission to a user identified by the user key. In other words, when a user accesses the reward URL and enters the external service, the computer device 200 may grant the mission to the user. In this case, the computer device 200 may monitor whether the user completes a mission in the external service associated with the reward URL using the received user key in operation 440, and may determine a reward for the user if the user completes the mission. For example, the computer device 200 may transmit user mission information to the external service server 330, and if the user completes the mission in the external service server 330, may transmit information regarding the completion of the mission to the computer device 200. In this case, the computer device 200 may determine a reward for the user in response to the completion of the mission.

In still another embodiment, the computing device 200 may record application-related conditions associated with the external service as predefined conditions in association with the reward URL in operation 420. Here, the application associated with the external service may correspond to the external service application 321 described above, and the application-related information constituting the application-related conditions may include information regarding whether the application associated with the external service is installed, the time at which the application is executed, and/or the number of times the application is executed. In this case, the computing device 200 may further receive information regarding the application installed on the electronic device in association with the external service from the electronic device in operation 430. Here, the further received information regarding the application may include information regarding whether the application is installed, the time at which the application is executed, and/or the number of times the application is executed. In this case, the computing device 200 may compare the further received information regarding the application with the application-related conditions recorded in association with the reward URL in operation 440, and determine a reward for the user identified by the user key. For example, the computing device 200 may provide a reward to a user if there is a record of the application being run on the electronic device 10 or more times, or if there is a record of the application being run on the electronic device within the last day.

As described above, the computer device 200 may generate a reward URL as a continuously usable type or a single-use type. In this case, if the reward URL is a single-use type reward URL, the computer device 200 may record that the reward URL has been used and restrict the reuse of the single-use type reward URL.

Furthermore, the computer device 200 may generate a reward URL as a public type or a unique type. In this case, if the reward URL is a unique type reward URL, the computer device 200 may restrict reuse of the reward URL if it determines that the reward URL has been used by a user who is not eligible for the reward of the corresponding reward URL.

Figure 5 illustrates an example user interface for displaying generated reward URLs in one embodiment of the present invention. Figure 5 illustrates an example user interface 500 that provides information about generated reward URLs for a particular external service.

In the user interface 500, the first column 510 shows examples of the names of generated reward URLs, and the second column 520 shows the identifiers of reward packages. The second column 520 may contain information about rewards to be provided to users who access the corresponding external service via the reward URL and meet the conditions set by the reward URL. The content of the reward may be predetermined in accordance with the reward package identifier, or may be dynamically determined for users who meet the conditions.

The third column 530 lists the language (ja:Japanese, ko:
The fourth column 540 indicates the URL type, ie, the unique type and the public type.

The fifth column 550 indicates the user type. The user type may correspond to the conditions for eligibility to use the corresponding reward URL. For example, "201911_VIP" may mean that users who were set as VIPs in November 2019 are eligible to use the reward URL. As another example, "201912_New" may mean that users who joined in December 2012 are eligible to use the reward URL.

The sixth column 560 indicates the period during which the reward URL can be used, and the seventh column 570 indicates the current status of the reward URL, indicating whether the reward URL is currently usable or unavailable.

The eighth column 580 provides functionality for downloading the corresponding reward URL, and the ninth column 590 provides a link to a page providing more detailed information about the corresponding reward URL.

In one embodiment, the user interface 500 of FIG. 5 may include functionality for an administrator of the service platform 310 to review, manage, and distribute generated reward URLs.

According to an embodiment of the present invention, a reward URL corresponding to a predefined condition may be generated in association with an external service registered on the platform, and a reward may be provided to a user who accesses the external service corresponding to the reward URL via the reward URL depending on whether the user satisfies the predefined condition. Furthermore, by setting a condition related to a target for use of the reward URL as the predefined condition, users may be targeted in real time. Furthermore, by setting a condition related to a predefined activity performed in association with an external service as the predefined condition , and receiving user activity information from the external service using a user key associated with the external service of the user accessed via the reward URL, the platform may provide a reward to the user based on the user's activity in the external service. Furthermore, by setting a condition related to a predefined mission performed in association with an external service as the predefined condition, the platform may assign a mission to a user who accesses the external service via the reward URL, and then monitor whether the user completes the mission in the external service using the user key, thereby providing a reward based on whether the user completes the mission. Furthermore, application-related conditions related to external services can be set as predefined conditions, and application information from users who access the service via a reward URL can be received and compared with the set conditions , thereby providing rewards based on the user's application usage record.

The systems or devices described above may be implemented using hardware components or a combination of hardware and software components. For example, the devices and components described in the embodiments may be implemented using one or more general-purpose or special-purpose computers, such as a processor, controller, arithmetic logic unit (ALU), digital signal processor, microcomputer, field programmable gate array (FPGA), programmable logic unit (PLU), microprocessor, or various devices capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications that run on the OS. The processing device may also access, record, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, descriptions may be provided assuming the use of a single processing device; however, those skilled in the art will recognize that a processing device may include multiple processing elements and/or multiple types of processing elements. For example, a processing unit may include multiple processors or one processor and one controller. Other processing configurations, such as parallel processors, are also possible.

Software may include computer programs, code, instructions, or a combination of one or more of these, and may configure a processing device to operate as desired or may independently or collectively instruct the processing device. The software and/or data may be embodied in any type of machine, component, physical device, virtual device, computer storage medium, or device to be interpreted by the processing device or to provide instructions or data to the processing device. The software may be distributed, stored, and executed in a distributed manner on computer systems connected by a network. The software and data may be stored on one or more computer-readable storage media.

Methods according to embodiments may be implemented in the form of program instructions executable by various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The medium may continuously record a computer-executable program or temporarily record it for execution or download. Furthermore, the medium may be a variety of recording or storage means, including a single or multiple hardware devices, and is not limited to media directly connected to a computer system but may also be distributed over a network. Examples of media include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical media such as CD-ROMs and DVDs; magneto-optical media such as floptical disks; ROM, RAM, flash memory, and the like, configured to record program instructions. Other examples of media include recording media or storage media managed by application stores that distribute applications, or by sites or servers that provide or distribute various software. Examples of program instructions include not only machine code, such as that produced by a compiler, but also high-level language code that is executed by a computer using an interpreter or the like.

While the embodiments have been described above based on limited examples and drawings, those skilled in the art will appreciate that various modifications and variations may be made in light of the above description. For example, the techniques described may be performed in an order different from that described, and/or the components of the described systems, structures, devices, circuits, etc. may be coupled or combined in a manner different from that described, or may be substituted or replaced by other components or equivalents, and still achieve suitable results.

Therefore, even if there are different embodiments, if they are equivalent to the scope of the claims, they fall within the scope of the appended claims.

310: Service platform 320: Client 330: External service server

Claims (14)

1. A method for tracking user inflows in a computer device including at least one processor, comprising:
the at least one processor registering an external service;
generating, by the at least one processor, a reward URL corresponding to a predefined condition associated with the external service;
the at least one processor receiving a user key associated with the external service from an electronic device of a user who accesses the external service via the reward URL; and the at least one processor determining a reward for the user identified by the user key depending on whether the user satisfies the predefined condition,
The predefined condition is:
A condition related to the use of the reward URL for a user who accesses the external service via the reward URL ;
The step of generating a reward URL includes:
As the predefined conditions, conditions related to the use of the reward URL are recorded in association with the reward URL;
The step of determining the reward comprises:
A method for tracking user traffic, comprising: comparing the user profile information with conditions related to the use of the reward URL to determine a reward for the user identified by the user key . 2. The method of claim 1, wherein the conditions related to the target of use of the reward URL include at least one of a user personal information-related condition including age, gender, or location, a group-related condition related to whether the user is included in a specific group among groups into which users are divided on the platform implemented by the computer device, or an item-related condition related to whether there is a purchase history of a specific item related to the platform . 1. A method for tracking user inflows in a computer device including at least one processor, comprising:
the at least one processor registering an external service;
generating, by the at least one processor, a reward URL corresponding to a predefined condition associated with the external service;
receiving, by the at least one processor, a user key associated with the external service from a user's electronic device that connects to the external service via the reward URL; and
the at least one processor determining a reward for the user identified by the user key depending on whether the user satisfies the predefined condition.
Including,
The predefined condition is:
The condition is related to a predefined activity performed by a user who enters the external service via the reward URL in relation to the external service,
The step of generating a reward URL includes:
As the predefined condition, a condition regarding a predefined activity performed in relation to the external service is recorded in association with the reward URL;
The step of determining the reward comprises:
receiving activity information of the user identified by the user key from an external service associated with the reward URL using the received user key; and comparing the received activity information with predefined activity-related conditions recorded in association with the reward URL to determine a reward for the user identified by the user key. The method for tracking user inflow according to claim 3 , wherein the predefined activity includes at least one of an access activity to the external service and a predefined activity within the external service. 1. A method for tracking user inflows in a computer device including at least one processor, comprising:
the at least one processor registering an external service;
generating, by the at least one processor, a reward URL corresponding to a predefined condition associated with the external service;
receiving, by the at least one processor, a user key associated with the external service from a user's electronic device that connects to the external service via the reward URL; and
the at least one processor determining a reward for the user identified by the user key depending on whether the user satisfies the predefined condition.
Including,
The predefined condition is:
A condition regarding a predefined mission that a user who accesses the external service via the reward URL performs in relation to the external service,
The step of generating a reward URL includes:
As the predefined condition, a condition regarding a predefined mission to be performed in relation to the external service is recorded in association with the reward URL;
The user inflow tracking method includes:
the at least one processor granting the mission to a user identified by the user key;
The step of determining the reward comprises:
monitoring whether the user completes the mission in an external service associated with the reward URL using the received user key; and determining a reward for the user if the user completes the mission. 1. A method for tracking user inflows in a computer device including at least one processor, comprising:
the at least one processor registering an external service;
generating, by the at least one processor, a reward URL corresponding to a predefined condition associated with the external service;
receiving, by the at least one processor, a user key associated with the external service from a user's electronic device that connects to the external service via the reward URL; and
the at least one processor determining a reward for the user identified by the user key depending on whether the user satisfies the predefined condition.
Including,
The predefined condition is:
Application-related conditions related to the external service for users who enter the external service via the reward URL;
The step of generating a reward URL includes:
As the predefined condition, an application-related condition related to the external service is recorded in association with the reward URL;
The step of receiving the user key comprises:
Further receiving application information installed on the electronic device in association with the external service from the electronic device;
The step of determining the reward comprises:
A method for tracking user inflow, comprising: comparing the received application information with application-related conditions recorded in association with the reward URL to determine a reward for the user identified by the user key. The user flow tracking method of claim 6 , wherein the application information includes information regarding at least one of whether an application related to the external service is installed, when the application is executed, or the number of times the application is executed. The step of generating a reward URL includes:
The reward URL is generated as a continuous use type or a single use type,
The step of determining the reward comprises:
2. The method of claim 1, wherein, if the reward URL is the one-time use type reward URL, the fact that the reward URL has been used is recorded, and reuse of the one-time use type reward URL is restricted. The step of receiving the user key comprises:
2. The method of claim 1, further comprising: providing a landing page corresponding to the reward URL to an electronic device of a user who enters via the reward URL; and receiving a user key associated with the application from the electronic device by executing an application for the external service installed in the electronic device in response to an input on the landing page. A program that causes a computer device to execute the user inflow tracking method according to any one of claims 1 to 9 . at least one processor implemented to execute computer-readable instructions;
the at least one processor:
Register an external service,
generating a reward URL corresponding to a predefined condition in association with the external service;
receiving a user key associated with the external service from an electronic device of the user who accesses the external service via the reward URL;
determining a reward for the user identified by the user key depending on whether the user satisfies the predefined condition;
The predefined condition is:
A condition related to the use of the reward URL for a user who accesses the external service via the reward URL ;
the at least one processor:
As the predefined conditions, conditions related to the use of the reward URL are recorded in association with the reward URL;
A computer system that compares the user's profile information with conditions related to the use of the reward URL to determine a reward for the user identified by the user key . At least one processor implemented to execute computer-readable instructions
Including,
the at least one processor:
Register an external service,
generating a reward URL corresponding to a predefined condition in association with the external service;
receiving a user key associated with the external service from an electronic device of the user who accesses the external service via the reward URL;
determining a reward for the user identified by the user key depending on whether the user satisfies the predefined condition;
The predefined condition is:
The condition is related to a predefined activity performed by a user who enters the external service via the reward URL in relation to the external service,
the at least one processor:
As the predefined condition, a condition regarding a predefined activity performed in connection with the external service is recorded in association with the reward URL;
receiving activity information of the user identified by the user key from an external service associated with the reward URL using the received user key;
and comparing the received activity information with predefined activity-related conditions recorded in association with the reward URL to determine a reward for the user identified by the user key . At least one processor implemented to execute computer-readable instructions
Including,
the at least one processor:
Register an external service,
generating a reward URL corresponding to a predefined condition in association with the external service;
receiving a user key associated with the external service from an electronic device of the user who accesses the external service via the reward URL;
determining a reward for the user identified by the user key depending on whether the user satisfies the predefined condition;
The predefined condition is:
A condition regarding a predefined mission that a user who accesses the external service via the reward URL performs in relation to the external service,
the at least one processor:
As the predefined condition, a condition regarding a predefined mission to be performed in relation to the external service is recorded in association with the reward URL;
granting the mission to a user identified by the user key;
Using the received user key, monitor whether the user completes the mission in an external service associated with the reward URL;
A computer device that determines a reward for the user if the user completes the mission. At least one processor implemented to execute computer-readable instructions
Including,
the at least one processor:
Register an external service,
generating a reward URL corresponding to a predefined condition in association with the external service;
receiving a user key associated with the external service from an electronic device of the user who accesses the external service via the reward URL;
determining a reward for the user identified by the user key depending on whether the user satisfies the predefined condition;
The predefined condition is:
Application-related conditions related to the external service for users who enter the external service via the reward URL;
the at least one processor:
As the predefined condition, an application-related condition related to the external service is recorded in association with the reward URL;
receiving, from the electronic device, application information associated with the external service and installed on the electronic device;
and comparing the received application information with application-related conditions recorded in association with the reward URL to determine a reward for the user identified by the user key .