Method and apparatus for providing nudge

Abstract

Provided are a method and an apparatus for providing a nudge. The method for providing a nudge according to some embodiments comprises the steps of: detecting an event related to a purchasing act by a user of a specific product on a web page; obtaining state information about the user in response to the detected event, the state information being related to an application corresponding to the web page; and providing a nudge for guiding the user to the application on the basis of the state information related to the application. According to the method, the rate of success of guiding to an application by nudging can be greatly improved.

Description

Method and device for providing nudges

[0001] The present disclosure relates to a method and device for providing a nudge, and more particularly, to a method and device for providing a nudge to guide a web user to an app.

[0002] Statistically, app conversion rates are higher than mobile web conversion rates. Consequently, many shopping service providers are investing significant effort to drive users who use their services online to their apps. For example, shopping service providers are guiding users to their apps by placing nudge buttons on their webpages that embed links to the apps.

[0003] However, most users have experienced the inconvenience of having their device screen redirected to the app installation page when clicking the nudge button (e.g., having to install the app and then make a purchase again). Consequently, users who are unaware that the app is installed tend to avoid clicking the nudge button. Consequently, this method has a clear limitation: its success rate in driving users to the app (or click-through rate (CTR)) is low.

[0004] A technical problem to be solved through some embodiments of the present disclosure is to provide a method for providing a nudge that can improve the success rate of inducing an app to a web user and a device for performing the method.

[0005] Another technical problem to be solved through some embodiments of the present disclosure is to provide a nudge providing method and a device for performing the method that can improve a user's convenience and satisfaction with a shopping (or purchasing) service.

[0006] The technical problems of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art of the present disclosure from the description below.

[0007] A method for providing a nudge according to some embodiments of the present disclosure for solving the above-described technical problem may include a method performed on at least one computing device, the method including: detecting an event associated with a user's purchase action for a specific product on a webpage; acquiring, in response to the detected event, status information of the user associated with an app corresponding to the webpage; and providing a nudge for guiding the user to the app based on the status information.

[0008] In some embodiments, the status information may include information regarding whether the app is installed and whether the app is logged in.

[0009] In some embodiments, the status information may include information regarding whether a pre-registered payment method exists.

[0010] In some embodiments, the step of providing the nudge comprises displaying a nudge object that includes a link to the app, wherein at least some of the display properties of the nudge object can be determined based on the state information.

[0011] In some embodiments, the step of providing the nudge comprises displaying a nudge object including a link to the app on a particular webpage, wherein at least some of the display properties of the nudge object can be determined based on the state information.

[0012] In some embodiments, the step of providing the nudge may include displaying a first nudge object on a particular webpage that includes a link to the app and displaying a second nudge object indicating the status information near the first nudge object.

[0013] In some embodiments, the step of providing the nudge comprises displaying a nudge object on a particular webpage that includes a link to a landing page within the app, wherein the landing page can be determined based on the status information.

[0014] In some embodiments, the status information includes information about whether the app is installed and whether the user is logged in to the app, and if the status information indicates that the app is installed but the user is not logged in to the app, the landing page may be determined to be an app login page.

[0015] In some embodiments, the status information includes information about whether the app is installed and whether the user is logged in to the app, and if the status information indicates that the app is installed and the user is logged in to the app, the landing page may be determined as an option selection page for the specific product.

[0016] In some embodiments, the status information includes information about whether the app is installed and whether the user is logged in to the app, and when the status information indicates that the app is installed and the user is logged in to the app, and a preset condition is satisfied, the landing page is determined to be a checkout page, and the preset condition may include at least one of a condition in which there is no option set for the specific product and a condition in which option selection for the specific product is completed through the webpage.

[0017] In some embodiments, the status information includes information about whether the app is installed, whether the user is logged in to the app, and whether a pre-registered payment method exists, and if the status information indicates that the app is installed, the user is logged in to the app, and a pre-registered payment method exists, the landing page may be determined to be a checkout page.

[0018] In some embodiments, the web page is a purchase page or a shopping cart page of the specific product, the event is a click event for a purchase button, and the step of providing the nudge may include a step of providing the nudge through a web login page when the user is not logged in to the web page.

[0019] In some embodiments, the webpage is a purchase page or a shopping cart page for the specific product, and the step of providing the nudge may include a step of providing the nudge through the webpage when the user is logged in to the webpage.

[0020] According to some embodiments of the present disclosure for solving the above-described technical problem, a nudge providing device includes at least one processor and a memory storing a computer program executed by the at least one processor, wherein the computer program may include instructions for an operation of detecting an event related to a user's purchase action for a specific product on a webpage, an operation of acquiring status information of the user related to an app corresponding to the webpage in response to the detected event, and an operation of providing a nudge for guiding the user to the app based on the status information.

[0021] According to some embodiments of the present disclosure for solving the above-described technical problem, a computer program may be stored in a computer-readable recording medium to be combined with a computing device and execute the steps of: detecting an event associated with a user's purchase action for a specific product on a webpage; acquiring status information of the user associated with an app corresponding to the webpage in response to the detected event; and providing a nudge to guide the user to the app based on the status information.

[0022] According to some embodiments of the present disclosure, a nudge may be provided to guide a web user to an app based on app-related status information, such as whether the app is installed, whether the user is logged in to the app, or whether a payment method is already registered. For example, based on the example app-related status information, a specific display property of a nudge object (e.g., the text of the object) may be changed, or an additional nudge object indicating app-related status information may be provided. In this case, since the user can intuitively recognize his or her app-related status information (e.g., the nudge object allows the user to recognize that the app is installed), the success rate of app-related nudge-based nudge guidance may be significantly improved. Furthermore, the user can also intuitively recognize remaining action information until the purchase is completed (e.g., the type, number / amount, etc. of actions the user must take to complete the purchase after moving to the app).

[0023] Additionally, the landing page within the app pointed to by the link embedded in the nudge can be determined based on the user's app-related status information. For example, if the user is logged in to the app and has a pre-registered payment method, the landing page may be determined as a product option selection page or a checkout page. In this case, the user can quickly complete the purchase process after navigating to the app, significantly improving user convenience and satisfaction with the shopping (purchase) service.

[0024] The effects according to the technical idea of ​​the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.

[0025] FIG. 1 illustrates an exemplary environment in which a nudge providing method according to some embodiments of the present disclosure may be performed.

[0026] FIG. 2 is an exemplary flowchart illustrating a nudge provision method according to some embodiments of the present disclosure.

[0027] FIG. 3 illustrates a product webpage that may be referenced in some embodiments of the present disclosure.

[0028] FIG. 4 and FIG. 5 are exemplary drawings for explaining a method of providing a nudge based on app-related status information according to some embodiments of the present disclosure.

[0029] FIG. 6 and FIG. 7 are exemplary drawings for explaining a nudge provision method based on app-related state information according to some other embodiments of the present disclosure.

[0030] FIG. 8 and FIG. 9 are exemplary drawings for explaining a method of providing a nudge based on app-related state information according to some other embodiments of the present disclosure.

[0031] FIG. 10 is an exemplary diagram illustrating a method for providing a nudge based on app-related state information according to some other embodiments of the present disclosure.

[0032] FIG. 11 is an exemplary drawing for explaining a method of providing a pop-up window according to some embodiments of the present disclosure.

[0033] FIG. 12 is an exemplary drawing for explaining a method of providing a pop-up window according to some other embodiments of the present disclosure.

[0034] FIG. 13 illustrates an exemplary computing device that may implement a service server and / or a user terminal according to some embodiments of the present disclosure.

[0035] Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the attached drawings. The advantages and features of the present disclosure, and methods for achieving them, will become clear with reference to the embodiments described in detail below together with the attached drawings. However, the technical idea of ​​the present disclosure is not limited to the following embodiments and may be implemented in various different forms. The following embodiments are provided only to complete the technical idea of ​​the present disclosure and to fully inform those skilled in the art of the present disclosure of the scope of the present disclosure, and the technical idea of ​​the present disclosure is defined only by the scope of the claims.

[0036] In describing various embodiments of the present disclosure, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present disclosure, the detailed description will be omitted.

[0037] Unless otherwise defined, the terms (including technical and scientific terms) used in the following examples may be used with meanings commonly understood by those of ordinary skill in the art to which this disclosure pertains; however, this may vary depending on the intentions of engineers working in the relevant field, precedents, the emergence of new technologies, etc. The terminology used in this disclosure is for the purpose of describing the embodiments and is not intended to limit the scope of this disclosure.

[0038] In the following examples, singular expressions include plural concepts unless the context clearly specifies that they are singular. Furthermore, plural expressions include singular concepts unless the context clearly specifies that they are plural.

[0039] In addition, terms such as first, second, A, B, (a), (b), etc. used in the following embodiments are only used to distinguish certain components from other components, and the nature, order, or sequence of the components are not limited by the terms.

[0040] Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0041] FIG. 1 illustrates an exemplary environment in which a nudge provision method according to some embodiments of the present disclosure may be performed.

[0042] As illustrated in FIG. 1, the nudge provision method according to the embodiments may be performed in an environment where a service server (10) provides a shopping (purchase) service through a user terminal (11). For example, a user may use the shopping service through a web browser and / or app installed on the terminal (11).

[0043] A service server (10) is a computing device / system that provides a shopping service. For example, the service server (10) can provide users with shopping services for various products via a web browser and / or an app.

[0044] In addition, the service server (10) can store and manage various information related to the shopping service (e.g., login information, delivery address, purchase / shopping history, app login history, web login history, payment method, etc.) in a storage.

[0045] In addition, the service server (10) can support and perform various functions (e.g., login, payment, etc.) necessary to provide a smooth shopping service.

[0046] In some embodiments, the service server (10) may provide a nudge to guide a user using a shopping service via the web to the app based on the user's app-related status information. Of course, such a nudge may be provided to the user via a terminal (11). In these embodiments, the service server (10) may be referred to as a "nudge providing device," a "nudge providing system," a "nudge server," etc. Details of the app-related status information and the nudge providing method will be described later with reference to the drawings below, FIG. 2.

[0047] The service server (10) may be implemented by at least one computing device. For example, all functions of the service server (10) may be implemented by a single computing device, or a first function of the service server (10) may be implemented by a first computing device and a second function may be implemented by a second computing device. Alternatively, specific functions of the service server (10) may be implemented by multiple computing devices.

[0048] A computing device may include any device equipped with computing capabilities. For an example of such a device, see FIG. 13. Since a computing device is a collection of interacting components (e.g., memory, processor, etc.), it may sometimes be referred to as a "computing system." Of course, the term "computing system" can also encompass the concept of a collection of interacting computing devices.

[0049] Next, the user terminal (11) is a computing device used by the user to receive shopping services from the service server (10). For example, the user may access a webpage for a specific product (i.e., a webpage for a specific product among the websites provided by the service server (10)) via a web browser installed on the terminal (11) to make a purchase, or may perform such a purchase via an app installed on the terminal (11).

[0050] The user terminal (11) may be a mobile computing device, such as a smartphone or tablet, but the scope of the present disclosure is not limited thereto. In some cases, the user terminal (11) may also be a stationary computing device, such as a desktop. For an example of a computing device, see FIG. 13.

[0051] In some embodiments, the user terminal (11) may provide the aforementioned nudge to the user by linking with the service server (10) (e.g., displaying the nudge via a web browser). In these embodiments, the user terminal (11) may also be referred to as a "nudge providing device" or a "nudge providing terminal." That is, depending on the implementation method, perspective, etc., the user terminal (11) may be considered a device providing a nudge, or the service server (10) may be considered a device providing a nudge.

[0052] As illustrated in Fig. 1, a service server (10) and a user terminal (11) can communicate via a network. Here, the network can be implemented as any type of wired / wireless network, such as a local area network (LAN), a wide area network (WAN), a mobile radio communication network, or Wibro (Wireless Broadband Internet).

[0053] So far, with reference to FIG. 1, an exemplary environment in which a nudge provision method according to some embodiments of the present disclosure can be performed has been described. Below, with reference to FIG. 2 and the following drawings, a nudge provision method according to some embodiments of the present disclosure will be described in detail.

[0054] The nudge provision method described below may be performed by at least one computing device. Here, at least one computing device may be a service server (10) and / or a user terminal (11). That is, all steps / operations of the nudge provision method described below may be performed by the service server (10) or the user terminal (11), or some steps / operations may be performed by the service server (10) and other steps / operations may be performed by the user terminal (11).

[0055] Hereinafter, for the convenience of understanding, the explanation will proceed assuming that the service server (10) provides a nudge to the user through the terminal (11) (e.g., displayed on a web browser) and that the service server (10) plays a leading role. Accordingly, if the subject of a specific step / action is omitted, it can be understood that it is performed by the service server (10). However, even if the subject of a specific step / action is mentioned as the service server (10), the user terminal (11) may perform the step / action depending on the implementation method.

[0056] Figure 2 is an exemplary flowchart illustrating a nudge provision method according to some embodiments of the present disclosure. However, this is merely a preferred embodiment for achieving the purpose of the present disclosure, and it is understood that some steps may be added or deleted as needed.

[0057] As illustrated in FIG. 2, the nudge provision method according to embodiments may begin at step S21 of detecting an event associated with a user's product purchase behavior on a webpage (or website) of a shopping service. For example, the service server (10) may detect an event occurring according to a user's explicit purchase behavior, such as clicking a purchase button, or may detect an event associated with a purchase behavior of a specific product by monitoring and analyzing user behavior occurring on a webpage (e.g., mobile webpage) of the product (e.g., analyzing whether a purchase intention is implied in the behavior).

[0058] The above-described event may refer to an event that triggers the provision of a nudge, and the conditions for such an event can be defined and set in various ways. For example, the event conditions may be defined and set based on the following: clicking (selecting) the purchase button, the dwell time on the product webpage exceeding a threshold, selecting a product option, clicking the add to cart button, moving the user's gaze toward the purchase button, moving the user's gaze to a review page (or product details page, etc.) and then returning to the product page, or various combinations thereof. However, the scope of the present disclosure is not limited thereto.

[0059] In step S22, user status information related to an app corresponding to the webpage (i.e., an app that provides the same shopping service as the webpage by linking with the service server (10)) may be acquired. Here, the app-related status information may include, but is not limited to, information regarding whether the app is installed, whether the user is logged into the app, and whether a previously registered payment method exists.

[0060] Meanwhile, the method of obtaining app-related status information (hereinafter, may be abbreviated as “status information”) can be designed and implemented in various ways.

[0061] For example, the service server (10) can obtain app-related status information (e.g., whether the app is installed, etc.) through an agent (or daemon, background app, etc.) installed on the user terminal (11). Here, the agent is a program implemented to check app-related status information (e.g., check the app login status through communication with the app, check the app installation status of the user terminal (11), etc.), and in some cases, may be installed together when the app is installed. In this example, if there is no agent that can communicate, the service server (10) can determine that the app is not installed on the user terminal (11) (i.e., determine that the app is not installed).

[0062] As another example, if the app is implemented to record status information at a designated location (e.g., inside or outside the terminal (11)) while running (e.g., recording upon app login, recording upon app termination / logout, etc.), the service server (10) can access the designated location through the user terminal (11), etc., to obtain app-related status information. In this example, if the app-related status information does not exist at the designated location, the service server (10) can determine that the app is not installed on the user terminal (11).

[0063] As another example, if the app is implemented to periodically or aperiodically transmit status information to the service server (10) while running, the service server (10) can obtain app-related status information from the app running on the user terminal (11).

[0064] As another example, when a user is logged in to a webpage, the service server (10) can identify the user using the login information of the webpage and obtain the user's app-related status information (e.g., whether a payment method has already been registered, etc.) by searching the storage. When the user logs in to or logs out of the app, the app login-related history (e.g., app login / logout history) will exist in the storage, so the service server (10) can also obtain the user's app-related status information using the app login-related history (log) (e.g., if there is no app login history at all, the app is determined to be not installed, and if there is no logout history after app login, the app is determined to be logged in).

[0065] As another example, the service server (10) can run an app in the background on a user terminal (11) and obtain status information (e.g., whether the app is logged in, etc.) through communication with the app. If communication with the app fails due to the app not existing or other reasons, the service server (10) can determine that the app is not installed on the user terminal (11).

[0066] As another example, the service server (10) can transmit a silent push to an app on a user terminal (11) and determine app-related status information based on the response thereto. For example, if the user terminal (11) transmits a response to the silent push, the service server (10) can determine that the app is installed on the user terminal (11) (i.e., determine that the app is installed). Otherwise, the service server can determine that the app is not installed.

[0067] As another example, the service server (10) can obtain the IP address of the user terminal (11) accessing the webpage and use it to search the storage to obtain app-related status information (e.g., whether the user is logged in to the app, etc.). For example, if the storage searches for app login (or logout) history (log) of the same IP address, the service server (10) can determine that the user is logged in (or logged out) to the app. In addition, the service server (10) can also check whether a payment method has been previously registered for the user through the storage.

[0068] As another example, app-related state information may be obtained based on various combinations of the examples described above.

[0069] In step S23, a nudge may be provided to guide the user to the app based on app-related status information. For example, the service server (10) may provide a nudge through the current webpage (e.g., a web login page, a product webpage, etc.) of the user terminal (11). Here, providing a nudge through the current webpage may include not only displaying (arranging) the nudge within the current webpage, but also providing the nudge through a pop-up window (e.g., a floating pop-up window) on the current webpage. In addition, the provided nudge may be a visual element, such as a nudge object (e.g., a button object, a text object, etc.), but the scope of the present disclosure is not limited thereto. In some cases, the nudge may also be provided in a manner that the user can perceive audibly and / or tactilely.

[0070] Meanwhile, the specific method of providing nudges based on app-related status information may vary depending on the embodiment.

[0071] In some embodiments, at least some of the display properties of a nudge object may be determined based on app-related status information. For example, a specific display property of a nudge object (e.g., the text of the object) may be changed based on app-related status information. In this case, the success rate of app induction may be significantly improved because the user can intuitively recognize the status information related to his or her app (e.g., recognize that the app is installed). In some cases, the user may also intuitively recognize remaining action information until the purchase is completed (e.g., the type, number / amount of actions the user must take to complete the purchase after moving to the app, etc.). Refer to the description below in FIG. 3 for this. The display properties may include, but are not limited to, the text, size, shape, color, and display properties of the text (e.g., font, size, color, etc.) of the nudge object.

[0072] In some other embodiments, the landing page within the app pointed to by the link included (embedded) in the nudge object may be determined based on app-related status information. For example, if the app is installed but the user is not logged in to the app, the landing page may be determined as the app login page. As another example, if the user is logged in to the app, the landing page may be determined as the product app page, the product option selection page, or the checkout page. As yet another example, if the user is logged in to the app and has a pre-registered payment method, the landing page may be determined as the product option selection page or the checkout page. According to the present embodiments, since the user can quickly complete the purchase after moving to the app, the user's convenience and satisfaction with the shopping service may be significantly improved. Further reference is made to the description of FIG. 3 and below regarding the present embodiments.

[0073] In some other embodiments, nudge objects representing app-related status information may be provided. For example, text objects, icon objects, image objects, and the like representing app-related status information may be provided to the user. This allows the user to more intuitively recognize the app-related status information of the asset. For further details on these embodiments, please refer to the descriptions below in FIG. 3.

[0074] In some other embodiments, in response to receiving a preset user input (e.g., a user input distinct from a click (tap), such as a long tap, double tap, press, or swipe) via a nudge object, a pop-up window (or pop-up page) providing additional information and / or additional functions may be displayed (provided) on the user terminal (11). In this case, the convenience of users using the shopping service may be further enhanced. For this purpose, please refer to the descriptions of FIGS. 11 and 12.

[0075] In some other embodiments, nudges may be provided based on various combinations of the embodiments described above.

[0076] Hereinafter, a method for providing a nudge according to some embodiments of the present disclosure has been described with reference to FIG. 2. As described above, nudges can be provided to guide web users to an app based on app-related status information, such as whether the app is installed, whether the app is logged in, and whether a pre-registered payment method exists. For example, based on the exemplified app-related status information, specific display properties of a nudge object (e.g., the text of the object) may be changed, or additional nudge objects indicating app-related status information may be provided. In such cases, since users can intuitively recognize their app-related status information (e.g., they can recognize that the app is installed through the nudge object), the success rate of app induction based on nudges can be significantly improved. Furthermore, users can also intuitively recognize remaining action information until the purchase is completed (e.g., the type, number / amount, etc. of actions the user must take to complete the purchase after moving to the app).

[0077] Additionally, the landing page within the app pointed to by the link embedded in the nudge can be determined based on the user's app-related status information. For example, if the user is logged in to the app and has a pre-registered payment method, the landing page may be determined as the product option selection page or the checkout page. In this case, the user can quickly complete the purchase after navigating to the app, significantly improving user convenience and satisfaction with the shopping (purchase) service.

[0078] Below, for ease of understanding, detailed embodiments of a nudge provision method based on app-related status information will be described with reference to FIGS. 3 to 12. For ease of understanding, the explanation will continue below assuming that the event occurrence condition is set to "clicking the purchase button (see 31)" (excluding the embodiment of FIG. 10).

[0079] FIG. 3 illustrates a product webpage (30) that may be referenced in various embodiments of the present disclosure.

[0080] As illustrated in FIG. 3, an event triggering the provision of a nudge may occur when a user clicks (selects) a purchase button (31) on a product webpage (30), and the service server (10) may detect the event. In some cases, the event may also occur when a user clicks a purchase button on a shopping cart webpage or another webpage.

[0081] When an event is detected, the service server (10) can provide a nudge to guide the user to the app through the terminal (11) based on the user's app-related status information.

[0082] Below, various embodiments of a nudge provision method will be described with reference to FIGS. 4 to 10.

[0083] FIG. 4 is an exemplary diagram illustrating a method for providing a nudge based on app-related status information according to some embodiments of the present disclosure. FIGS. 4 to 9 assume that a user using a product webpage (30) is in a non-logged-in state (i.e., not logged in via the web) and a nudge is provided via a web login page (40) (i.e., it assumes that the current webpage is moved (changed) to the web login page (40) by clicking the purchase button (31).

[0084] The present embodiments relate to a method of providing a nudge when app-related state information indicates that i) the app is installed and ii) the user is not logged in to the app.

[0085] In the case where the app-related status information is as above, as illustrated in FIG. 4, the service server (10) may provide (display) a first nudge object (42, eg, a button with an app link built-in) including a link to a landing page within the app and a second nudge object (41, eg, a text object) indicating the app-related status information through the web login page (40). For example, the service server (10) may display the first nudge object (42) on the web login page (40) and display the second nudge object (41) near the first nudge object (42). However, in some cases, the service server (10) may display only the first nudge object (42) on the web login page (40).

[0086] In the present embodiments, the landing page pointed to by the link included (embedded) in the first nudge object (42) may be determined as the app login page (50) as illustrated in FIG. 5. This is because the purchase action can be completed only when the user logs in to the service server (10).

[0087] Additionally, the first nudge object (42) and / or the second nudge object (41) may function to intuitively convey app-related status information and remaining action information until purchase completion (e.g., login, option selection, payment, etc.) to the user. For example, the user may intuitively recognize that the app is installed on his / her terminal (11) through the text of the second nudge object (41) (i.e., app-related status information).

[0088] Meanwhile, in some embodiments, login information (e.g., ID, password) entered on the web login page (40) may be automatically transferred to a landing page (i.e., an app login page (50)). Specifically, when a user enters login information on the web login page (40) and clicks the first nudge object (42), the app login page (50) with the entered login information may be displayed on the user terminal (11). By doing so, both user convenience and the app induction success rate may be improved.

[0089] In the preceding embodiments, the text (or other display properties) of the second nudge object (41) may automatically change as login information is entered into the web login page (40). For example, the text of the second nudge object (41) may change to further indicate that the entered login information is automatically transferred to the app login page (50) (e.g., text such as "Login information is automatically transferred to the app, so there is no need to re-enter it." may be added). Alternatively, a third nudge object (not shown) indicating such information may be added to the web login page (40).

[0090] So far, a nudge provision method based on app-related status information according to some embodiments of the present disclosure has been described with reference to FIGS. 4 and 5. Below, a nudge provision method according to some other embodiments of the present disclosure will be described with reference to FIGS. 6 and 7.

[0091] The present embodiments relate to a method of providing a nudge when app-related state information indicates that i) the app is installed and ii) the user is logged in to the app.

[0092] In the case where the app-related status information is as above, as illustrated in FIG. 6, the service server (10) can provide (display) a first nudge object (62, eg, a button with an app link built-in) including a link to a landing page within the app and a second nudge object (61, eg, a text object) indicating the app-related status information through a web login page (40). At this time, the landing page can be determined as a product option selection page (71), a product app page (70), or a checkout page (see 90 of FIG. 9) as illustrated in FIG. 7. By doing so, the purchase action for the corresponding product can be completed quickly.

[0093] In the present embodiments, the first nudge object (62) and / or the second nudge object (61) may function to intuitively convey app-related status information and remaining action information until purchase completion (e.g., option selection, payment, etc.) to the user. For example, the user may intuitively recognize that the app is installed on his / her terminal (11) and logged into the app through the text of the second nudge object (61) (i.e., app-related status information).

[0094] Meanwhile, in some embodiments, the landing page may be determined as a checkout page (see 90 of FIG. 9) if a preset condition is satisfied. For example, if there are no options set for a product on the webpage (30) or if option selection for the product has already been completed through the webpage (30), the landing page may be determined as a checkout page.

[0095] Additionally, in some embodiments, information regarding product options, payment methods, etc., selected via the product webpage (30) may be automatically transmitted to a landing page within the app. Furthermore, the display properties of the second nudge object (61) may be changed to display more such information, or a third nudge object (not shown) may be provided. For further details, please refer to the descriptions of FIGS. 4 and 5.

[0096] So far, with reference to FIGS. 6 and 7, a nudge provision method based on app-related status information according to several other embodiments of the present disclosure has been described. Below, with reference to FIGS. 8 and 9, a nudge provision method based on app-related status information according to several other embodiments of the present disclosure will be described.

[0097] The present embodiments relate to a method of providing a nudge when app-related status information indicates that i) the app is installed, ii) the user is logged in to the app, and iii) a pre-registered payment method exists.

[0098] In the case where the app-related status information is as above, as illustrated in FIG. 8, the service server (10) can provide (display) a first nudge object (82, e.g., a button with an app link built-in) including a link to a landing page within the app and a second nudge object (81, e.g., a text object) indicating the app-related status information through a web login page (40). At this time, the landing page can be determined as a checkout page (90) as illustrated in FIG. 9 or a product option selection page (see 71 of FIG. 7). By doing so, the purchase action for the corresponding product can be completed quickly.

[0099] In the present embodiments, the first nudge object (82) and / or the second nudge object (81) may function to intuitively convey app-related status information and remaining action information until purchase completion (e.g., payment, etc.) to the user. For example, the user may intuitively recognize that he or she is logged into the app and has a payment method registered through the text of the second nudge object (81) (i.e., app-related status information). Furthermore, the user may recognize that the purchase can be completed by simply performing a payment in the app through the text of the nudge object (e.g., 81, 82).

[0100] Meanwhile, in some embodiments, in response to receiving a preset user input (e.g., a user input distinct from a click (tap), such as a swipe, etc.) through the first nudge object (81), the service server (10) may perform payment processing and change the landing page to a payment (purchase) completion page (i.e., the app is executed and moved to the payment completion page within the app). In addition, in some cases, a phrase guiding that the above payment processing is possible (e.g., "One-stop payment can be performed when swiping") may be provided through the web login page (40) in various ways (e.g., provided through the second nudge object (81) or the third nudge object (not shown), displayed through a floating pop-up window, etc.).

[0101] So far, with reference to FIGS. 8 and 9 , a nudge provision method based on app-related status information according to some further embodiments of the present disclosure has been described. Below, with reference to FIG. 10 , a nudge provision method based on app-related status information according to some further embodiments of the present disclosure will be described.

[0102] Figure 10 assumes that a user using a product webpage (30) is logged in and that the event trigger condition is set to a condition other than clicking the "Buy" button (31). For example, the event trigger condition may be set to a condition such as when the user's gaze moves toward the "Buy" button (31) or when the dwell time on the product webpage (30) exceeds a threshold.

[0103] In these embodiments, the service server (10) can analyze user actions occurring on a product web page (30) to detect events related to purchase actions.

[0104] When an event is detected, the service server (10) can obtain the user's app-related status information (e.g., identify the user using the login information of the webpage and query the storage to obtain the user's app-related status information), and provide (display) a nudge (see 101) through the product webpage (30) based on the information. For example, the service server (10) can display a nudge object (101) near the purchase button (31) of the product webpage (30) or provide a nudge through a pop-up window. In some cases, the service server (10) can also display a nudge object (not shown) indicating app-related status information on the product webpage (30).

[0105] For reference, Fig. 10 assumes that the app-related status information is the same as Fig. 8. Accordingly, if the app-related status information is different from Fig. 8, the display properties (e.g., text) of the nudge object (101) and the landing page, etc., may be changed accordingly.

[0106] Various embodiments of a nudge provision method based on app-related status information have been described with reference to FIGS. 3 to 10 so far. As described above, based on app-related status information, specific display properties of a nudge object (e.g., object text) may be changed, or additional nudge objects indicating app-related status information may be provided. In this case, since users can intuitively recognize their app-related status information (e.g., recognize that the app is installed through the nudge object), the success rate of app induction based on nudges can be significantly improved. Furthermore, users can also intuitively recognize remaining action information until purchase completion (e.g., type, number / amount, etc. of actions the user must take to complete the purchase after moving to the app).

[0107] Additionally, the landing page within the app pointed to by the link embedded in the nudge can be determined based on the user's app-related status information. For example, if the user is logged in to the app and has a pre-registered payment method, the landing page may be determined as the product option selection page or the checkout page. In this case, the user can quickly complete the purchase after navigating to the app, significantly improving user convenience and satisfaction with the shopping (purchase) service.

[0108] Meanwhile, according to various embodiments of the present disclosure, in response to receiving a preset user input via a nudge object, a pop-up window (or pop-up page) providing additional information and / or functions may be displayed (provided). These embodiments will now be described with reference to FIGS. 11 and 12 .

[0109] FIG. 11 is an exemplary drawing for explaining a method of providing a pop-up window according to some embodiments of the present disclosure.

[0110] As illustrated in FIG. 11, when a preset user input (111) is received via a specific nudge object (82), the service server (10) (or user terminal (11)) can provide the user with a pop-up window (112, e.g., a floating pop-up window) displaying purchase information. In this case, the user can check the purchase information before being transferred to the app, thereby quickly completing the purchase within the app.

[0111] Purchase information may include, but is not limited to, information regarding the product name, selected product options, delivery address, payment amount, and payment method. The pop-up window (112) may be configured to provide the user with all purchase information, or may be configured to provide the user with only purchase information regarding certain preset key items (e.g., delivery address, payment amount, etc.).

[0112] Additionally, the preset user input (111) may be a gesture input that is distinct from a click (tap), such as a long tap, double tap, press, swipe, etc. However, the scope of the present disclosure is not limited thereto.

[0113] In some embodiments, the information (or purchase information) displayed in the pop-up window (112) may be determined based on a landing page within the app (e.g., a landing page pointed to by a link embedded in a specific nudge object (82). In other words, the pop-up window (112) may be configured to provide the user with information related to the landing page in advance (e.g., information displayed on the landing page, information to be entered by the user on the landing page, etc.). For example, if the landing page is an app login page, the information displayed in the pop-up window (112) may be the user's login information (e.g., ID, etc.), and if the landing page is a checkout page, the information displayed in the pop-up window (112) may be information regarding the delivery address, options for the selected product, payment amount, payment method, etc. In this case, the user can check the information related to the landing page in advance, thereby quickly completing the purchase within the app.

[0114] Additionally, in some embodiments, the pop-up window (112) may function as an input interface. For example, the pop-up window (112) may be configured to provide information on various items (e.g., delivery address, payment amount, options for a selected product), while also allowing correction or input of information for specific items (e.g., delivery address, options for a selected product, etc.). Information entered through the pop-up window (112) may, of course, be automatically transmitted to the app.

[0115] Hereinafter, a method of providing a pop-up window according to some other embodiments of the present disclosure will be described with reference to FIG. 12.

[0116] As illustrated in FIG. 12, when a preset user input (121) is received via a specific nudge object (82), the service server (10) (or user terminal (11)) may provide the user with a pop-up window (e.g., a floating pop-up window) for selecting a landing page (122, 123, etc.). In this case, since the user can directly select a landing page, user convenience may be further enhanced.

[0117] As described above, the preset user input (121) may be a gesture input that is distinct from a click (tap), such as a long tap, double tap, press, swipe, etc. However, the scope of the present disclosure is not limited thereto.

[0118] Meanwhile, in some embodiments, if a preset user input (121) for a specific nudge object (82) is a swipe, a landing page may be determined (selected) based on the length of the swipe. In addition, a thumbnail of a landing page corresponding to the current length of the swipe may be displayed near the specific nudge object (82). For example, if a user swipes a specific length to the right while touching a specific nudge object (82), the landing page may be determined to be a product app page, and as the user swipes further to the right, the landing page may change in the order of a product option selection page and a checkout page. In addition, if the user swipes all the way to the right of a specific nudge object (82), payment processing may be performed and the landing page may be determined to be a payment completion page.

[0119] Various embodiments of pop-up window provision methods have been described with reference to FIGS. 11 and 12. As described above, by providing a pop-up window (e.g., 112) that provides additional information and / or additional functions upon receipt of a preset user input, user convenience and the success rate of app induction through nudges can be further improved.

[0120] Hereinafter, an exemplary computing device (130) capable of implementing the above-described service server (10) and / or user terminal (11) will be described with reference to FIG. 13.

[0121] Figure 13 is an exemplary hardware configuration diagram showing a computing device (130).

[0122] As illustrated in FIG. 13, a computing device (130) may include one or more processors (131), a bus (133), a communication interface (134), a memory (132) for loading a computer program (136) executed by the processor (131), and a storage (135) for storing the computer program (136). However, only components related to the embodiment of the present disclosure are illustrated in FIG. 13. Therefore, a person skilled in the art to which the present disclosure pertains will appreciate that, in addition to the components illustrated in FIG. 13, other general components (e.g., a display, other input / output devices, etc.) may be further included. That is, the computing device (130) may further include various components in addition to the components illustrated in FIG. 13. In addition, in some cases, the computing device (130) may be configured in a form in which some of the components illustrated in FIG. 13 are omitted. Hereinafter, each component of the computing device (130) will be described.

[0123] The processor (131) can control the overall operation of each component of the computing device (130). The processor (131) can be configured to include at least one of a CPU (Central Processing Unit), an MPU (Micro Processor Unit), an MCU (Micro Controller Unit), a GPU (Graphics Processing Unit), an NPU (Neural Processing Unit), or any other type of processor well known in the art of the present disclosure. In addition, the processor (131) can perform operations for at least one application or program for executing operations / methods according to embodiments of the present disclosure. The computing device (130) can include one or more processors.

[0124] Next, the memory (132) can store various data, commands, and / or information. The memory (132) can load a computer program (136) from the storage (135) to execute operations / methods according to embodiments of the present disclosure. The memory (132) may be implemented as a volatile memory such as RAM, but the technical scope of the present disclosure is not limited thereto.

[0125] Next, the bus (133) can provide a communication function between components of the computing device (130). The bus (133) can be implemented as various types of buses such as an address bus, a data bus, and a control bus.

[0126] Next, the communication interface (134) can support wired and wireless Internet communication of the computing device (130). Furthermore, the communication interface (134) can also support various communication methods other than Internet communication. To this end, the communication interface (134) can be configured to include a communication module well known in the technical field of the present disclosure.

[0127] Next, the storage (135) can non-temporarily store one or more computer programs (136). The storage (135) can be configured to include non-volatile memory such as Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, a hard disk, a removable disk, or any form of computer-readable recording medium well known in the art to which the present disclosure pertains.

[0128] Next, the computer program (136) may include instructions that, when loaded into the memory (132), cause the processor (131) to perform operations / methods according to various embodiments of the present disclosure. That is, the processor (131) may perform operations / methods according to various embodiments of the present disclosure by executing the loaded instructions.

[0129] For example, the computer program (136) may include instructions for performing an operation of detecting an event associated with a user's purchase of a specific product on a webpage, an operation of acquiring user status information related to an app corresponding to the webpage in response to the detected event, and an operation of providing a nudge to guide the user to the app based on the status information. In such a case, a service server (10) or a user terminal (11) according to some embodiments of the present disclosure may be implemented through a computing device (130).

[0130] Meanwhile, in some embodiments, the computing device (130) illustrated in FIG. 13 may refer to a virtual machine implemented based on cloud technology. For example, the computing device (130) may be a virtual machine operating on one or more physical servers included in a server farm. In this case, at least some of the processor (131), memory (132), and storage (135) illustrated in FIG. 13 may be virtual hardware, and the communication interface (134) may also be implemented as a virtualized networking element, such as a virtual switch.

[0131] So far, with reference to FIG. 13, an exemplary computing device (130) capable of implementing a user terminal (11) and / or a service server (10) according to some embodiments of the present disclosure has been described.

[0132] Various embodiments of the present disclosure and effects according to the embodiments have been described with reference to FIGS. 1 through 13. The effects according to the technical concept of the present disclosure are not limited to the effects described above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.

[0133] Furthermore, even though the above embodiments have described multiple components as being combined or operating in combination, the technical concept of the present disclosure is not necessarily limited to these embodiments. That is, within the scope of the technical concept of the present disclosure, all of the components may be selectively combined and operated one or more times.

[0134] The technical concepts of the present disclosure described so far can be implemented as computer-readable code on a computer-readable recording medium. A computer program recorded on the computer-readable recording medium can be transmitted to another computing device via a network such as the Internet, installed on the device, and used therein.

[0135] Although the operations are depicted in a specific order in the drawings, it should not be understood that the operations must be performed in the specific order depicted, or in a sequential order, or that all depicted operations must be performed to achieve the desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Although various embodiments of the present disclosure have been described above with reference to the attached drawings, those skilled in the art to which the present disclosure pertains will understand that the technical concepts of the present disclosure can be implemented in other specific forms without changing the technical concepts or essential characteristics thereof. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of the technical ideas defined by the present disclosure.

Claims

1. A method performed on at least one computing device, A step of detecting an event associated with a user's purchase behavior for a specific product on a webpage; In response to the detected event, a step of obtaining the user's status information related to the app corresponding to the webpage; and Comprising a step of providing a nudge to guide the user to the app based on the status information, How to provide nudges.

2. In paragraph 1, The above status information includes information about whether the app is installed and whether the app is logged in. How to provide nudges.

3. In paragraph 1, The above status information includes information on whether a previously registered payment method exists. How to provide nudges.

4. In paragraph 1, The step of providing the above nudge is: comprising the step of displaying a nudge object containing a link to the above app on a specific webpage; At least some of the display properties of the nudge object are determined based on the state information, How to provide nudges.

5. In paragraph 1, The step of providing the above nudge is: A step of displaying a first nudge object including a link to the above app on a specific webpage; and comprising a step of displaying a second nudge object indicating the state information near the first nudge object; How to provide nudges.

6. In paragraph 1, The step of providing the above nudge is: A step of displaying a nudge object containing a link to a landing page within the app on a specific webpage, The above landing page is determined based on the above status information. How to provide nudges.

7. In paragraph 6, The above status information includes information about whether the app is installed and whether the app is logged in. If the above status information indicates that the app is installed but the user is not logged in to the app, the landing page is determined to be the app login page. How to provide nudges.

8. In paragraph 6, The above status information includes information about whether the app is installed and whether the app is logged in. If the above status information indicates that the app is installed and the user is logged in to the app, the landing page is determined to be an option selection page for the specific product. How to provide nudges.

9. In paragraph 6, The above status information includes information about whether the app is installed and whether the app is logged in. If the above status information indicates that the app is installed and the user is logged in to the app, and the preset conditions are satisfied, the landing page is determined to be a checkout page. The above preset conditions include at least one of a condition in which there is no option set for the specific product and a condition in which the option selection for the specific product is completed through the webpage. How to provide nudges.

10. In paragraph 6, The above status information includes information on whether the app is installed, whether the app is logged in, and whether there is a previously registered payment method. If the above status information indicates that the app is installed, the user is logged in to the app, and there is a pre-registered payment method, the landing page is determined to be a checkout page. How to provide nudges.

11. In paragraph 1, The above webpage is the purchase page or shopping cart page for the above specific product, The above event is a click event for the purchase button. The step of providing the above nudge is: Including a step of providing the nudge through a web login page when the user is not logged in to the web page. How to provide nudges.

12. In paragraph 1, The above webpage is the purchase page or shopping cart page for the above specific product, The step of providing the above nudge is: Including a step of providing the nudge through the webpage when the user is logged in to the webpage. How to provide nudges.

13. In paragraph 1, The above nudge is a nudge object that contains a link to the above app, In response to receiving a preset user input through the nudge object, the method further comprises the step of providing a pop-up window displaying purchase information for the specific product. How to provide nudges.

14. In paragraph 1, The above nudge is a nudge object that contains a link to a landing page within the app, In response to receiving a preset user input through the nudge object, the method further comprises the step of providing a pop-up window displaying information related to the landing page, The above landing page is determined based on the above status information. How to provide nudges.

15. In paragraph 1, The above nudge is a nudge object, In response to receiving a preset user input through the nudge object, further comprising a step of providing a pop-up window for selecting a landing page within the app. How to provide nudges.

16. At least one processor; and A memory storing a computer program executed by at least one processor, The above computer program: An action that detects events associated with a user's purchase behavior for a specific product on a webpage; In response to the detected event, an action of obtaining the user's status information related to the app corresponding to the webpage; and Including instructions for an operation that provides a nudge to guide the user to the app based on the state information. Nudge provider device.

17. Combined with a computing device, A step of detecting an event associated with a user's purchase behavior for a specific product on a webpage; In response to the detected event, a step of obtaining the user's status information related to the app corresponding to the webpage; and Stored in a computer-readable recording medium to execute a step of providing a nudge to guide the user to the app based on the above status information. Computer program.

Images