Method for providing nudge and apparatus thereof

Abstract

A method for providing a nudge and an apparatus thereof are provided. A method for providing a nudge according to some embodiments may include the steps of detecting an event associated with a user’s purchasing behavior for a specific product on a webpage, obtaining user status information related to 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 app-related status information. According to this method, the success rate of inducing the user to the app through the nudge can be significantly improved.

Description

Technology Field

[0001] The present disclosure relates to a method and apparatus for providing a nudge, and more specifically, to a method and apparatus for providing a nudge to induce a web user to an app. Background Technology

[0002] Statistically, the purchase conversion rate in apps is higher than that of the mobile web. Accordingly, many shopping (purchase) service providers are making significant efforts to guide users who use the service via the web to their apps. For example, shopping service providers are guiding users to their apps by placing nudge buttons with embedded links to the app on their webpages.

[0003] However, most users have experienced the inconvenience of the device screen moving to an app installation page when clicking a nudge button (e.g., the inconvenience of having to install the app and make a purchase again). Consequently, users who are unaware that the app is installed do not click the nudge button, and as a result, this method has a clear limitation in that the success rate of inducing users to the app (or click rate, CTR) is not high. Prior art literature

[0004] U.S. Patent Publication No. 2022-0318839 (Published Oct. 06, 2022) The problem to be solved

[0005] The technical problem to be solved through some embodiments of the present disclosure is to provide a nudge providing method that can improve the success rate of inducing web users to use an app, and an apparatus for performing the method.

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

[0007] The technical problems of the present disclosure are not limited to those mentioned above, and other unmentioned technical problems will be clearly understood by a person skilled in the art of the present disclosure from the description below. means of solving the problem

[0008] A nudge providing method according to some embodiments of the present disclosure for solving the above-described technical problem may include, in a method performed on at least one computing device, the step of detecting an event associated with a user’s purchasing behavior for a specific product on a webpage; the step of obtaining state information of the user associated with an app corresponding to the webpage in response to the detected event; and the step of providing a nudge to guide the user to the app based on the state information.

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

[0010] In some embodiments, the status information may include information regarding whether a previously registered payment method exists.

[0011] In some embodiments, the step of providing the nudge includes the step of displaying a nudge object including a link to the app, and at least some of the display attributes of the nudge object may be determined based on the state information.

[0012] In some embodiments, the step of providing the nudge includes the step of displaying a nudge object containing a link to the app on a specific webpage, and at least some of the display attributes of the nudge object may be determined based on the state information.

[0013] In some embodiments, the step of providing the nudge may include the step of displaying a first nudge object containing a link to the app on a specific webpage and the step of displaying a second nudge object indicating the state information near the first nudge object.

[0014] In some embodiments, the step of providing the nudge includes the step of displaying a nudge object containing a link to a landing page within the app on a specific webpage, and the landing page may be determined based on the state information.

[0015] In some embodiments, the status information includes information regarding whether the app is installed and whether the app is logged in, 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 as an app login page.

[0016] In some embodiments, the status information includes information regarding whether the app is installed and whether the app is logged in, 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.

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

[0018] In some embodiments, the status information includes information regarding whether the app is installed, whether the app is logged in, and whether a 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 registered payment method exists, the landing page may be determined as a checkout page.

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

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

[0021] A nudge providing device according to some embodiments of the present disclosure for solving the technical problem described above comprises at least one processor and a memory for storing a computer program executed by the at least one processor, and the computer program may include instructions for an operation to detect an event associated with a user’s purchase behavior for a specific product on a webpage, an operation to obtain state information of the user associated with an app corresponding to the webpage in response to the detected event, and an operation to provide a nudge to guide the user to the app based on the state information.

[0022] A computer program according to some embodiments of the present disclosure for solving the technical problem described above may be stored in a computer-readable recording medium to execute the steps of: detecting an event associated with a user’s purchase behavior for a specific product on a webpage in response to the detected event; obtaining state 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 state information. Effects of the invention

[0023] 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 app is logged in, or whether a registered payment method exists. For example, based on the exemplified app-related status information, a specific display attribute of the 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 the user can intuitively perceive their app-related status information (e.g., can perceive that the app is installed through the nudge object), the success rate of inducing the app through the nudge may be significantly improved. Furthermore, the user can also intuitively perceive information regarding remaining actions 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).

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

[0025] The effects according to the technical concept of the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art from the description below. Brief explanation of the drawing

[0026] FIG. 1 illustrates an exemplary environment in which a nudge providing method according to some embodiments of the present disclosure can be performed. FIG. 2 is an exemplary flowchart illustrating a nudge-providing method according to some embodiments of the present disclosure. FIG. 3 illustrates a product webpage that may be referenced in some embodiments of the present disclosure. FIGS. 4 and 5 are exemplary drawings for illustrating a nudge-providing method based on app-related state information according to some embodiments of the present disclosure. FIGS. 6 and 7 are exemplary drawings for illustrating a nudge-providing method based on app-related state information according to some other embodiments of the present disclosure. FIGS. 8 and 9 are exemplary drawings for illustrating a nudge-providing method based on app-related state information according to some other embodiments of the present disclosure. FIG. 10 is an exemplary drawing for illustrating a nudge provision method based on app-related state information according to some other embodiments of the present disclosure. FIG. 11 is an exemplary drawing for explaining a method of providing a popup window according to some embodiments of the present disclosure. 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. FIG. 13 illustrates an exemplary computing device capable of implementing a service server and / or user terminal according to some embodiments of the present disclosure. Specific details for implementing the invention

[0027] 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 the methods for achieving them will become clear by referring to the embodiments described below in detail together with the attached drawings. However, the technical concept of the present disclosure is not limited to the following embodiments but can be implemented in various different forms. The following embodiments are provided merely to complete the technical concept of the present disclosure and to fully inform those skilled in the art of the scope of the present disclosure, and the technical concept of the present disclosure is defined only by the scope of the claims.

[0028] In describing the various embodiments of the present disclosure, if it is determined that a detailed description of related known configurations or functions could obscure the essence of the present disclosure, such detailed description is omitted.

[0029] Unless otherwise defined, terms used in the following embodiments (including technical and scientific terms) may be used in a meaning commonly understood by those skilled in the art to which this disclosure pertains, but this may vary depending on the intent of those skilled in the art, case law, the emergence of new technology, etc. The terms used in this disclosure are for describing the embodiments and are not intended to limit the scope of this disclosure.

[0030] In the following embodiments, singular expressions include plural concepts unless the context clearly specifies them as singular. Additionally, plural expressions include singular concepts unless the context clearly specifies them as plural.

[0031] In addition, terms such as first, second, A, B, (a), (b), etc. used in the following embodiments are used merely to distinguish one component from another, and the essence, order, or sequence of the said component is not limited by such terms.

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

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

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

[0035] The service server (10) is a computing device / system that provides shopping services. For example, the service server (10) can provide shopping services for various products to users through a web browser and / or app.

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

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

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

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

[0040] A computing device may include any device equipped with computing functions, and for an example of such a device, refer to FIG. 13. Since a computing device is a collection of various components (e.g., memory, processor, etc.) that interact with each other, it may be referred to as a 'computing system' depending on the case. Of course, the term computing system may also encompass the concept of a collection of multiple computing devices that interact with each other.

[0041] 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 perform a purchase by accessing a webpage of a specific product (i.e., a webpage of a specific product among the websites provided by the service server (10)) through a web browser installed on the terminal (11), or may perform such a purchase through an app installed on the terminal (11).

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

[0043] In some embodiments, the user terminal (11) may interact with the service server (10) to provide the aforementioned nudge to the user (e.g., displaying the nudge through a web browser). In these embodiments, the user terminal (11) may also be named as a 'nudge providing device', 'nudge providing terminal', etc. That is, depending on the implementation method, perspective, etc., the user terminal (11) may be considered as a device providing the nudge, and the service server (10) may be considered as a device providing the nudge.

[0044] As illustrated in FIG. 1, the service server (10) and the user terminal (11) can communicate through a network. Here, the network can be implemented as any type of wired or wireless network, such as a Local Area Network (LAN), a Wide Area Network (WAN), a mobile radio communication network, or Wibro (Wireless Broadband Internet).

[0045] Up to now, with reference to FIG. 1, exemplary environments in which a nudge providing method according to some embodiments of the present disclosure can be performed have been described. Hereinafter, with reference to FIG. 2 and subsequent drawings, a nudge providing method according to some embodiments of the present disclosure will be described in detail.

[0046] 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), and some steps / operations may be performed by the service server (10) and other steps / operations may be performed by the user terminal (11).

[0047] In the following, for the sake of convenience of understanding, the explanation will continue under the assumption that the service server (10) provides a nudge to the user through the terminal (11) (e.g., displayed in a web browser) and that the service server (10) plays a leading role. Therefore, 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 corresponding step / action depending on the implementation method.

[0048] FIG. 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 necessary.

[0049] As illustrated in FIG. 2, the nudge provision method according to the embodiments may begin at step S21, which detects 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 that occurs in response to an explicit purchase behavior by a user, such as clicking a purchase button, or it may detect an event associated with the purchase behavior of a product by monitoring and analyzing user behaviors occurring on a webpage (e.g., mobile webpage) of a specific product (e.g., analyzing whether a purchase intention is implied in the behavior).

[0050] The aforementioned event may refer to an event that triggers the provision of a nudge, and the conditions for the occurrence of such an event may be defined and set in various ways. For example, the conditions for the occurrence of an event may be defined and set based on the case where a purchase button is clicked (selected), the time spent on the product webpage exceeds a threshold, the case where a product option is selected, the case where an add-to-cart button is clicked, the case where the user's gaze moves toward the purchase button, the case where the user's gaze moves toward a review page (or a product detail page, etc.) and then returns to the product page, or various combinations thereof. However, the scope of the present disclosure is not limited thereto.

[0051] 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 obtained. Here, the app-related status information may include, for example, information regarding whether the app is installed, whether the user is logged into the app, and whether a previously registered payment method exists, but is not limited thereto.

[0052] Meanwhile, the method of obtaining app-related state information (hereinafter abbreviated as 'state information') can be designed and implemented in various ways.

[0053] 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., checking the app login status through communication with the app, checking the app installation status of the user terminal (11)), and may be installed together with the app installation depending on the case. In this example, if there is no agent capable of communication, 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).

[0054] As another example, if the app is implemented to record state 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) and obtain app-related state information. In this example, if app-related state 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).

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

[0056] 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 retrieve the user's app-related status information (e.g., whether a registered payment method exists, etc.) by querying the storage. When the user performs an app login or app logout, the app login-related history (e.g., app login / logout history) will exist in the storage, so the service server (10) can retrieve 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, it is determined that the app is not installed; if there is no logout history after the app login, it is determined that the app is logged in).

[0057] As another example, the service server (10) can run an app in the background state on the user terminal (11) and obtain status information (e.g., whether the app is logged in) through communication with the app. If communication with the app is not possible for reasons such as the app not existing, the service server (10) can determine that the app is not installed on the user terminal (11).

[0058] As another example, the service server (10) can send a silent push to an app on a user terminal (11) and determine app-related status information based on the response thereto. For instance, if the user terminal (11) sends 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), and in the opposite case, determine that the app is not installed.

[0059] As another example, the service server (10) can obtain the IP address of a user terminal (11) that has accessed the webpage and use it to query the storage to obtain app-related status information (e.g., whether the app is logged in, etc.). For instance, if an app login (or logout) history (log) for the same IP address is found in the storage, the service server (10) can determine that the user is in an app login (or logout) state. Additionally, the service server (10) can also check through the storage whether there is a pre-registered payment method for the user.

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

[0061] 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 the nudge through the current webpage (e.g., web login page, product webpage, etc.) of the user terminal (11). Here, providing the nudge through the current webpage may include not only displaying (placing) the nudge within the current webpage but also providing the nudge through a popup window (e.g., floating popup window) on the current webpage. Additionally, the provided nudge may be a visual element, such as a nudge object (e.g., button object, text object, etc.), but the scope of the present disclosure is not limited thereto. In some cases, the nudge may be provided in a manner that the user can perceive auditorily and / or tactilely.

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

[0063] In some embodiments, at least some of the display attributes of the nudge object may be determined based on app-related state information. For example, a specific display attribute of the nudge object (e.g., the text of the object) may be changed based on app-related state information. In this case, the user can intuitively perceive their app-related state information (e.g., recognize that the app is installed), which can significantly improve the success rate of app induction. In some cases, the user can also intuitively perceive information regarding remaining actions until purchase completion (e.g., the type, number / amount, etc. of actions the user must take to complete the purchase after moving to the app), for which reference should be made to the description in FIG. 3 and below. The display attributes may be, for example, the text, size, shape, color of the nudge object, and display attributes of the text (e.g., font, size, color, etc.), but are not limited thereto.

[0064] In some other embodiments, the landing page within the app pointed to by a link included (embedded) in the nudge object may be determined based on app-related state 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 a registered payment method exists, the landing page may be determined as the product option selection page or the checkout page. According to these embodiments, since the user can quickly complete the purchase action after moving to the app, the user's convenience and satisfaction with the shopping service can be significantly improved. Further reference should be made to the description of FIG. 3 and below regarding these embodiments.

[0065] In some other embodiments, a nudge object representing app-related state information may be provided. For example, a text object, an icon object, an image object, etc., representing app-related state information may be further provided to the user. By doing so, the user can more intuitively perceive the app-related state information of the asset. Further reference should be made to the description of FIG. 3 and below regarding these embodiments.

[0066] In some other embodiments, in response to the reception of pre-set user input (e.g., long tap, double tap, press, swipe, etc., user input distinct from a click (tap)) through 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 the user using the shopping service may be further enhanced, and for this, refer to the description in FIG. 11 and FIG. 12.

[0067] In some other embodiments, a nudge may be provided based on various combinations of the embodiments described above.

[0068] Up to this point, a method for providing a nudge according to several embodiments of the present disclosure has been described with reference to FIG. 2. As described above, a nudge can 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 app is logged in, and whether a pre-registered payment method exists. For example, based on the exemplified app-related status information, a specific display attribute of the nudge object (e.g., text of the object) may be changed, or additional nudge objects indicating app-related status information may be provided. In such cases, since the user can intuitively perceive their app-related status information (e.g., can perceive that the app is installed through the nudge object), the success rate of inducing the app through the nudge can be significantly improved. Furthermore, the user can intuitively perceive information regarding remaining actions 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).

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

[0070] Hereinafter, detailed embodiments of a nudge provision method based on app-related state information will be described with reference to FIGS. 3 to 12 for the sake of ease of understanding. Hereinafter, for the sake of ease of understanding, the explanation will continue by assuming that the event occurrence condition is set to 'click the purchase button (see 31)' (except for the embodiment of FIG. 10).

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

[0072] An event that triggers the provision of a nudge may occur when a user clicks (selects) a purchase button (31) on a product webpage (30) as exemplified in FIG. 3, and a service server (10) may detect the event. In some cases, the event may occur when a user clicks a purchase button on a shopping cart webpage or another webpage.

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

[0074] Hereinafter, various embodiments regarding a nudge provision method will be described with reference to FIGS. 4 to 10.

[0075] FIG. 4 is an exemplary drawing illustrating a method for providing nudges based on app-related state information according to some embodiments of the present disclosure. FIGS. 4 through 9 assume a case where 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 through a web login page (40) (i.e., assumes a case where the current webpage is moved (changed) to a web login page (40) as a result of clicking a purchase button (31)).

[0076] The embodiments relate to a nudge provision method in which app-related state information indicates i) that the app is installed and ii) that the user is in a non-logged-in state for the app.

[0077] In the case where the app-related status information is as described above, as illustrated in FIG. 4, the service server (10) may provide (display) a first nudge object (42, e.g., a button with an embedded app link) containing a link to a landing page within the app and a second nudge object (41, e.g., 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).

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

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

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

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

[0082] Up to now, a nudge provision method based on app-related state information according to some embodiments of the present disclosure has been described with reference to FIGS. 4 and 5. Hereinafter, a nudge provision method according to some other embodiments of the present disclosure will be described with reference to FIGS. 6 and 7.

[0083] The embodiments relate to a nudge provision method in which app-related status information indicates i) that the app is installed and ii) that the user is logged in to the app.

[0084] In the case where the app-related status information is as described above, as illustrated in FIG. 6, the service server (10) may provide (display) a first nudge object (62, e.g., a button with an embedded app link) containing a link to a landing page within the app and a second nudge object (61, e.g., a text object) indicating the app-related status information through the web login page (40). At this time, the landing page may be determined to be a product option selection page (71), a product app page (70), or a checkout page (see 90 in FIG. 9) as illustrated in FIG. 7. This is because doing so allows the purchase of the product to be completed quickly.

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

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

[0087] Additionally, in some embodiments, information regarding options, payment methods, etc. of a product selected through a 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 further display such information, or a third nudge object (not shown) may be provided. For this, further reference should be made to the descriptions in FIGS. 4 and 5.

[0088] Up to now, a nudge provision method based on app-related state information according to several other embodiments of the present disclosure has been described with reference to FIGS. 6 and 7. Hereinafter, a nudge provision method based on app-related state information according to several other embodiments of the present disclosure will be described with reference to FIGS. 8 and 9.

[0089] The embodiments relate to a nudge provision method in which app-related status information indicates i) that the app is installed, ii) that the user is logged in to the app, and iii) that a registered payment method exists.

[0090] In the case where the app-related status information is as described above, as illustrated in FIG. 8, the service server (10) may provide (display) a first nudge object (82, e.g., a button with an embedded app link) containing 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 may be determined to be a checkout page (90) as illustrated in FIG. 9 or a product option selection page (see 71 in FIG. 7). This is because doing so allows the purchase of the product to be completed quickly.

[0091] In the embodiments, the first nudge object (82) and / or the second nudge object (81) can function to intuitively convey to the user app-related status information and information on remaining actions until purchase completion (e.g., payment, etc.). For instance, the user can intuitively recognize that they are logged into the app and that a payment method is registered through the text of the second nudge object (81) (i.e., app-related status information). Furthermore, the user can recognize through the text of the nudge objects (e.g., 81, 82) that the purchase action can be completed by simply making a payment in the app.

[0092] Meanwhile, in some embodiments, in response to receiving a pre-set user input (e.g., user input distinct from a click (tap), such as a swipe) 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 launched and moved to the payment completion page within the app). Additionally, depending on the case, a message indicating that such payment processing is possible (e.g., "One-stop payment can be performed by swiping") may be provided in various ways through the web login page (40) (e.g., provided through the second nudge object (81) or the third nudge object (not shown), displayed through a floating pop-up window, etc.).

[0093] Up to now, a nudge provision method based on app-related state information according to some other embodiments of the present disclosure has been described with reference to FIG. 8 and FIG. 9. Hereinafter, a nudge provision method based on app-related state information according to some other embodiments of the present disclosure will be described with reference to FIG. 10.

[0094] FIG. 10 assumes that a user using a product webpage (30) is logged in and the event occurrence condition is set to a condition other than clicking the purchase button (31). For example, the event occurrence condition may be set such as when the user's gaze moves toward the purchase button (31) or when the time spent on the product webpage (30) is greater than a threshold.

[0095] In the embodiments, the service server (10) can detect events associated with purchasing behavior by analyzing user actions that occur on the product webpage (30).

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

[0097] For reference, FIG. 10 assumes that the app-related state information is the same as FIG. 8. Therefore, if the app-related state information is different from FIG. 8, the display properties (e.g., text) of the nudge object (101) and the landing page, etc., can be changed accordingly.

[0098] Various embodiments regarding a nudge provision method based on app-related state information have been described so far with reference to FIGS. 3 to 10. As described above, specific display attributes of a nudge object (e.g., text of the object) may be changed based on app-related state information, or additional nudge objects indicating app-related state information may be provided. In this case, since the user can intuitively recognize their app-related state information (e.g., recognize that the app is installed through the nudge object), the success rate of inducing the app through the nudge can be significantly improved. Furthermore, the user can intuitively recognize information regarding remaining actions 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).

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

[0100] Meanwhile, according to various embodiments of the present disclosure, a pop-up window (or pop-up page) providing additional information and / or functions may be displayed (provided) in response to the reception of pre-set user input through a nudge object. Hereinafter, such embodiments will be described with reference to FIGS. 11 and 12.

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

[0102] As illustrated in FIG. 11, when a pre-configured user input (111) is received through a specific nudge object (82), the service server (10) (or user terminal (11)) may 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 moving to the app, thereby enabling the purchase to be completed quickly within the app.

[0103] Purchase information may include, for example, product name, options of the selected product, shipping address, payment amount, payment method, etc., but is not limited thereto. The popup window (112) may be configured to provide all purchase information to the user, or it may be configured to provide only purchase information regarding some pre-set key items (e.g., shipping address, payment amount, etc.) to the user.

[0104] Additionally, the pre-configured user input (111) may be a gesture input 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.

[0105] In some embodiments, the information (or purchase information) displayed in the popup 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 popup window (112) may be configured to provide the user with information associated with the landing page in advance (e.g., information displayed on the landing page, information that the user must enter on the landing page, etc.). For instance, if the landing page is an app login page, the information displayed in the popup 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 popup window (112) may be information regarding the shipping address, options of the selected product, payment amount, payment method, etc. In this case, the user can check the information associated with the landing page in advance, thereby enabling the user to quickly complete the purchase action in the app.

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

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

[0108] As illustrated in FIG. 12, when a pre-configured user input (121) is received through a specific nudge object (82), the service server (10) (or user terminal (11)) may provide the user with a pop-up window (e.g., floating pop-up window) to receive a selection of a landing page (122, 123, etc.). In this case, the user can directly select the landing page, thereby further enhancing user convenience.

[0109] As described above, the pre-configured user input (121) may be a gesture input 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.

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

[0111] Various embodiments regarding the method of providing a pop-up window have been described so far 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 receiving a pre-set user input, user convenience and the success rate of inducing the app through nudge can be further improved.

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

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

[0114] As illustrated in FIG. 13, the 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, FIG. 13 illustrates only the components related to the embodiments of the present disclosure. Therefore, a person skilled in the art to which the present disclosure belongs will understand that other general-purpose components (e.g., a display, other input / output devices, etc.) may be included in addition to the components illustrated in FIG. 13. That is, the computing device (130) may include various additional components in addition to the components illustrated in FIG. 13. Furthermore, depending on the case, the computing device (130) may be configured in a form in which some of the components illustrated in FIG. 13 are omitted. Each component of the computing device (130) will be described below.

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

[0116] Next, the memory (132) may store various data, commands and / or information. The memory (132) may load a computer program (136) from storage (135) to execute an operation / method 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.

[0118] Next, the bus (133) can provide communication functions 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.

[0119] Next, the communication interface (134) may support wired and wireless internet communication of the computing device (130). Additionally, the communication interface (134) may support various communication methods other than internet communication. To this end, the communication interface (134) may be configured to include a communication module well known in the art of the present disclosure.

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

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

[0122] For example, a computer program (136) may include instructions to perform actions such as detecting an event associated with a user’s purchase behavior for a specific product on a webpage, obtaining user state information related to 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 state 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).

[0123] 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 running 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.

[0124] Up to now, 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.

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

[0126] Furthermore, just because the above embodiments describe a plurality of components being combined into one 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 purpose of the technical concept of the present disclosure, all such components may be selectively combined into one or more combinations to operate.

[0127] The technical concept of the present disclosure described above may be implemented as computer-readable code on a computer-readable recording medium. A computer program recorded on a computer-readable recording medium may be transmitted to another computing device via a network such as the Internet and installed on said computing device, thereby being used on said computing device.

[0128] Although operations are depicted in a specific order in the drawings, it should not be understood that the operations must necessarily be executed in the specific order depicted or in a sequential order, or that all depicted operations must be executed to obtain the desired result. In certain situations, 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 will understand that the technical concept of the present disclosure may be implemented in other specific forms without altering the technical concept or essential features thereof. Therefore, the embodiments described above should be understood as illustrative in all respects and not restrictive. The scope of protection of the present disclosure shall be interpreted by the claims below, and all technical concepts within the equivalent scope shall be interpreted as being included within the scope of rights of the technical concept defined by the present disclosure.

Claims

Claim 1 A nudge providing method performed on at least one computing device, comprising: detecting an event associated with a user’s purchase behavior for a specific product on a webpage; obtaining state information of the user associated with an app corresponding to the webpage in response to the detected event; providing a nudge to guide the user to the app based on the state information, wherein the nudge is a nudge object including a link to a landing page within the app; and providing a popup window that allows the user to select the landing page based on the length of the swipe in response to the receipt of a swipe input through the nudge object. Claim 2 A nudge providing method according to claim 1, wherein the state information includes information regarding whether the app is installed and whether the app is logged in, the state information indicates that the app is installed and the user is logged in to the app, and when the user touches the nudge object and swipes to the right by a first length, the landing page is determined to be an option selection page for the specific product. Claim 3 A nudge providing method according to paragraph 2, wherein when a pre-set condition is satisfied and the user touches the nudge object and swipes to the right by a second length longer than the first length, the landing page is determined to be a checkout page, wherein the pre-set condition includes at least one of the condition that there is no option set for the specific product and the condition that the selection of an option for the specific product is completed through the webpage. Claim 4 A nudge providing method according to paragraph 2, wherein the state information further includes information regarding whether a previously registered payment method exists, and the state information indicates that the app is installed, the user is logged in to the app, and a previously registered payment method exists, and when the user touches the nudge object and swipes to the right by a second length longer than the first length, the landing page is determined to be a checkout page. Claim 5 A nudge provision method according to claim 4, wherein if the user touches the nudge object and swipes to the right by a third length longer than the second length, the landing page is determined to be a payment completion page. Claim 6 A nudge providing method according to claim 1, wherein the step of providing the popup window includes the step of displaying a thumbnail of the landing page corresponding to the length of the swipe near the nudge object. Claim 7 A nudge providing device comprising: at least one processor; and a memory for storing a computer program executed by the at least one processor, wherein the computer program comprises: an action of detecting an event associated with a user’s purchase behavior for a specific product on a webpage; an action of obtaining state information of the user associated with an app corresponding to the webpage in response to the detected event; an action of providing a nudge to guide the user to the app based on the state information, wherein the nudge is a nudge object including a link to a landing page within the app; and instructions for an action of providing a popup window that allows the user to select the landing page based on the length of the swipe in response to the receipt of a swipe input through the nudge object. Claim 8 A computer program stored on a recording medium readable by a computing device to execute the steps of: detecting an event associated with a user’s purchase behavior for a specific product on a webpage on a computing device; obtaining state information of the user associated with an app corresponding to the webpage in response to the detected event; providing a nudge to guide the user to the app based on the state information, wherein the nudge is a nudge object including a link to a landing page within the app; and providing a popup window that allows the user to select the landing page based on the length of the swipe in response to the reception of a swipe input through the nudge object.

Images