Page interaction system, method and device, electronic equipment and storage medium

By configuring the mapping between user behavior and service operations on the server side and directly determining the service operations on the front-end page, the problem of slow page interaction speed is solved, and a more efficient interaction process is achieved.

CN119025392APending Publication Date: 2024-11-26DUXIAOMAN TECH (BEIJING) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410991817.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-23
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In existing technologies, the interaction speed is low because data uploading, storage, and analysis take a long time.

Method used

Configure the mapping between user behavior and service operation on the server side and send it to the front-end page. The front-end page can directly determine the service operation based on the user behavior, reducing data communication between the front-end and the server.

Benefits of technology

It improves page interaction speed, reduces data communication time between the front-end page and the server, and enhances interaction efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119025392A_ABST
    Figure CN119025392A_ABST
Patent Text Reader

Abstract

The invention provides a page interaction system, method and device, electronic equipment and a storage medium, the system comprises a server side and a front-end page, and the server side is used for obtaining behavior configuration information and issuing the behavior configuration information to the front-end page; the front-end page monitors a target user behavior of a user on the front-end page, wherein the user behavior comprises page refreshing and page backspacing; and determining and executing a target service operation corresponding to the target user behavior. By applying the embodiment of the invention, the corresponding relationship between the user behavior and the service operation is configured at the server side and is issued to the front-end page, and the front-end page determines the corresponding service operation based on the user behavior to interact with the user; according to the method, the front-end page does not need to determine the service operation corresponding to the user behavior after data communication with the server side, the process can be completed on the front-end page, time consumption caused by data communication between the front-end page and the server side is reduced, and the page interaction speed is increased.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data processing, and in particular to a page interaction system, method, device, electronic device and storage medium. Background Art

[0002] At present, many web pages will have corresponding service operations based on user operations, such as popping up coupons to users when monitoring users browsing specific content, popping up intelligent customer service when monitoring users clicking specific buttons, etc. In related technologies, point-of-sale technology is usually used to capture user interaction behaviors on the page.

[0003] Specifically, in the related art, a tracking code is inserted into the page to monitor changes in elements in the page, including changes in text and images in the page, etc. When elements in the page change, the tracking code will capture these events and send the corresponding user behavior data to the background server. After receiving the data, the background server stores the data in the database and establishes a real-time data warehouse to clean, process and aggregate the user behavior data, judge the user's current behavior, and trigger corresponding interactive operation instructions as needed.

[0004] Since the entire process involves data uploading, storing and analyzing, the interactive response takes a long time, resulting in a low page interaction speed. Summary of the invention

[0005] In view of this, embodiments of the present invention provide a page interaction system, method, device, electronic device and storage medium to improve the page interaction speed.

[0006] According to one aspect of the present invention, a page interaction system is provided, the system comprising: a front-end page and a server;

[0007] The server is used to obtain behavior configuration information, which includes the corresponding relationship between user behavior and service operation; and send the behavior configuration information to the front-end page;

[0008] The front-end page is used to monitor the target user behavior of the user on the front-end page, wherein the user behavior includes refreshing the page and rolling back the page; based on the behavior configuration information, determine the target service operation corresponding to the target user behavior; and execute the target service operation.

[0009] In a possible embodiment, the front-end page includes a buried event listener and a page behavior listener;

[0010] The front-end page is used to register the preset embedding events contained in the behavior configuration information to the embedding event listener based on the behavior configuration information, and register the preset page behavior events contained in the behavior configuration information to the page behavior listener; the preset embedding events include page element change events, and the preset page behavior events include refresh page and rollback page;

[0011] The embedding event listener is used to monitor the user behavior in the front-end page based on the preset embedding event;

[0012] The page behavior listener is used to monitor the user behavior in the front-end page based on the preset page behavior event.

[0013] In a possible embodiment, the page behavior listener includes an end event listener or an H5 page listener, wherein the end event listener is used to monitor the preset page behavior in the APP, and the H5 page listener is used to monitor the preset page behavior in the H5 page.

[0014] In a possible embodiment, the behavior configuration information also includes a correspondence between a user behavior sequence and a service operation;

[0015] The front-end page is used to continue monitoring the target user behavior of the user when the target user behavior is in the target behavior sequence in the behavior configuration information until the target behavior sequence is executed; and determine that the service operation corresponding to the target behavior sequence is the target service operation.

[0016] In a possible embodiment, the server is further used to obtain a behavior blacklist, which includes preset abnormal behaviors; and send the behavior blacklist to the front-end page;

[0017] The front-end page is further used to report the abnormal behavior information of the user to the server when the target user behavior belongs to the behavior blacklist;

[0018] The server is used to push the abnormal behavior information to a preset client.

[0019] In a possible embodiment, the front-end page is also used to send the user's response to the target service operation to the server; the server is used to adjust the behavior configuration information based on the user's response to the target service operation and the user tag, and the user tag is a preset AB experiment tag.

[0020] According to another aspect of the present invention, a page interaction method is provided, which is applied to a front-end page in a page interaction system, wherein the page interaction system also includes a server, and the method includes:

[0021] Obtaining behavior configuration information, wherein the behavior configuration information includes a correspondence between user behavior and service operation; the behavior configuration information is sent from the server to the front-end page;

[0022] Monitor the target user behavior of the user on the front-end page, wherein the user behavior includes refreshing the page and returning to the page;

[0023] Based on the behavior configuration information, determining a target service operation corresponding to the target user behavior;

[0024] The target service operation is executed.

[0025] In a possible embodiment, the front-end page includes a buried event listener and a page behavior listener; the method includes:

[0026] Based on the behavior configuration information, the preset embedding events contained in the behavior configuration information are registered to the embedding event listener, and the preset page behavior events contained in the behavior configuration information are registered to the page behavior listener; the preset embedding events include page element change events, and the preset page behavior events include refresh page and rollback page;

[0027] The user behavior in the front-end page is monitored based on the preset embedding event by the embedding event listener;

[0028] The page behavior listener monitors the user behavior in the front-end page based on the preset page behavior event.

[0029] In a possible embodiment, the behavior configuration information also includes a correspondence between a user behavior sequence and a service operation; and the method further includes:

[0030] When the target user behavior is in the target behavior sequence in the behavior configuration information, continue to monitor the target user behavior of the user until the target behavior sequence is completed;

[0031] The service operation corresponding to the target behavior sequence is determined as the target service operation.

[0032] In a possible embodiment, the method further includes:

[0033] Obtaining a behavior blacklist, wherein the behavior blacklist includes preset abnormal behaviors; the behavior blacklist is sent by the server to the front-end page;

[0034] In the case that the target user behavior belongs to the behavior blacklist, the abnormal behavior information of the user is reported to the server; so that the server pushes the abnormal behavior information to the preset client.

[0035] In a possible embodiment, the method further includes:

[0036] The user's response to the target service operation is sent to the server; so that the server adjusts the behavior configuration information based on the user's response to the target service operation and the user tag, where the user tag is a preset AB experiment tag.

[0037] According to another aspect of the present invention, a page interaction method is provided, which is applied to a server in a page interaction system, wherein the page interaction system also includes a front-end page, and the method includes:

[0038] Acquire behavior configuration information, wherein the behavior configuration information includes a correspondence between user behavior and service operation;

[0039] The behavior configuration information is sent to the front-end page; so that the front-end page monitors the target user behavior of the user on the front-end page, and the user behavior includes refreshing the page and rolling back the page; based on the behavior configuration information, the target service operation corresponding to the target user behavior is determined; and the target service operation is executed.

[0040] In a possible embodiment, the method further includes:

[0041] Obtaining a behavior blacklist, wherein the behavior blacklist includes preset abnormal behaviors;

[0042] Sending the behavior blacklist to the front-end page; so that the front-end page reports the abnormal behavior information of the user to the server when the behavior of the target user belongs to the behavior blacklist;

[0043] The abnormal behavior information is pushed to a preset client.

[0044] In a possible embodiment, the method further includes:

[0045] The behavior configuration information is adjusted based on the user's response to the target service operation sent by the front-end page and the user tag, where the user tag is a preset AB experiment tag.

[0046] According to another aspect of the present invention, a page interaction device is provided, which is applied to a front-end page in a page interaction system, wherein the page interaction system also includes a server, and the device includes:

[0047] A first acquisition module is used to acquire behavior configuration information, wherein the behavior configuration information includes a correspondence between user behavior and service operation; the behavior configuration information is sent from the server to the front-end page;

[0048] A monitoring module, used to monitor the target user behavior of the user on the front-end page, wherein the user behavior includes refreshing the page and returning to the page;

[0049] A determination module, configured to determine a target service operation corresponding to the target user behavior based on the behavior configuration information;

[0050] An execution module is used to execute the target service operation.

[0051] According to another aspect of the present invention, a page interaction device is provided, which is applied to a server in a page interaction system, wherein the page interaction system also includes a front-end page, and the device includes:

[0052] A second acquisition module, used to acquire behavior configuration information, wherein the behavior configuration information includes a correspondence between user behaviors and service operations;

[0053] The sending module is used to send the behavior configuration information to the front-end page; so that the front-end page monitors the target user behavior of the user on the front-end page, and the user behavior includes refreshing the page and rolling back the page; based on the behavior configuration information, determine the target service operation corresponding to the target user behavior; and execute the target service operation.

[0054] According to another aspect of the present invention, there is provided an electronic device, comprising:

[0055] Processor; and

[0056] Memory for storing programs,

[0057] Wherein, the program includes instructions, and when the instructions are executed by the processor, the processor executes any of the above-mentioned page interaction methods.

[0058] According to another aspect of the present invention, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable a computer to execute any of the above-mentioned page interaction methods.

[0059] One or more technical solutions provided in the embodiments of the present invention configure the correspondence between user behavior and service operation on the server side and send it to the front-end page, which determines the corresponding service operation based on the user behavior to interact with the user. In the process of interacting with the user, the front-end page does not need to communicate data with the server side before determining the service operation corresponding to the user behavior. Instead, the process can be completed on the front-end page, thereby reducing the time consumption caused by data communication between the front-end page and the server side and improving the page interaction speed. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Further details, features and advantages of the invention are disclosed in the following description of exemplary embodiments in conjunction with the accompanying drawings, in which:

[0061] Figure 1 A schematic diagram of the structure of a page interaction system provided by an embodiment of the present invention;

[0062] Figure 2 A schematic diagram of a process for configuring behavior configuration information in a page interaction system provided by an embodiment of the present invention;

[0063] Figure 3 A schematic diagram of a process of initializing SDK in an embodiment of the present invention;

[0064] Figure 4a as well as Figure 4b A schematic diagram of a process for matching user behaviors in an embodiment of the present invention;

[0065] Figure 5 A user do not disturb mechanism in an embodiment of the present invention;

[0066] Figure 6 A schematic diagram of a life cycle of a page interaction system provided by an embodiment of the present invention;

[0067] Figure 7 An interactive schematic diagram of a page interactive system provided by an embodiment of the present invention;

[0068] Figure 8 An architecture diagram of a page interaction system provided by an embodiment of the present invention;

[0069] Fig. 9 A schematic diagram of a flow chart of a page interaction method provided by an embodiment of the present invention;

[0070] Fig.10 A schematic diagram of another flow chart of the page interaction method provided by an embodiment of the present invention;

[0071] Fig.11 A structural intention of a page interaction device provided by an embodiment of the present invention;

[0072] Fig.12 Another structural intention of the page interaction device provided by the embodiment of the present invention;

[0073] Fig.13 A block diagram of an exemplary electronic device that can be used to implement an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0074] Embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present invention. It should be understood that the drawings and embodiments of the present invention are only for exemplary purposes and are not intended to limit the scope of protection of the present invention.

[0075] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0076] The term "including" and its variations used in this document are open inclusions, that is, "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one other embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the following description. It should be noted that the concepts of "first", "second", etc. mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0077] It should be noted that the modifications of "one" and "plurality" mentioned in the present invention are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0078] The names of the messages or information exchanged between multiple devices in the embodiments of the present invention are only used for illustrative purposes, and are not used to limit the scope of these messages or information.

[0079] In order to improve the page interaction speed, the present invention provides a page interaction system, method, device, electronic device and storage medium. The following describes the solution of the present invention with reference to the accompanying drawings:

[0080] like Figure 1 As shown, Figure 1A schematic diagram of the structure of the page interaction system provided by the present invention is shown in FIG. 1 . The page interaction system 100 may include a server 101 and a front-end page 102, wherein:

[0081] The server 101 is used to obtain behavior configuration information, which includes the correspondence between user behavior and service operation; and send the behavior configuration information to the front-end page;

[0082] The front-end page 102 is used to monitor the target user behavior of the user on the front-end page, wherein the user behavior includes refreshing the page and rolling back the page; based on the behavior configuration information, determine the target service operation corresponding to the target user behavior; and execute the target service operation.

[0083] By applying the embodiment of the present invention, the correspondence between user behavior and service operation is configured on the server side and sent to the front-end page, and the front-end page determines the corresponding service operation based on the user behavior to interact with the user. In the process of interacting with the user, the front-end page does not need to communicate data with the server side before determining the service operation corresponding to the user behavior, but the process can be completed on the front-end page, thereby reducing the time consumption caused by data communication between the front-end page and the server side and improving the page interaction speed.

[0084] The page interaction system 100 is described below as an example:

[0085] The front-end page can be a web page in a network platform or a page in an APP. The present invention does not specifically limit this. The server can send instructions to the front-end page. In a possible embodiment, the front-end page can be an H5 page (a web page developed based on HTML5 technology (a language description method for building Web content)).

[0086] The service operation corresponding to the user behavior sent by the server to the front-end page can be pre-configured according to actual needs, and the present invention does not specifically limit this. As a possible implementation, when the front-end page is an online shopping page, it can be set that when the user enters the product page, a coupon collection prompt will pop up to the user, and when the user clicks the add to cart button, the product price change curve will be displayed to the user, etc.

[0087] In a possible embodiment, additional parameters may be configured based on the user behavior as trigger conditions for the corresponding service operation. The parameters may include the channel, product line, electronic device information, status, etc. to which the front-end page belongs, and may be set according to actual needs, which is not specifically limited in the present invention. For ease of description, in the embodiments of the present invention, the corresponding relationship between the configured user behavior and the service operation is referred to as behavior configuration information.

[0088] In a possible embodiment, the triggering condition of a service operation may be multiple user behaviors, that is, a user behavior group consisting of multiple user behaviors may correspond to one service, and the user behavior group may include multiple user behaviors. In some embodiments, the user behavior group may also include the execution order of multiple user behaviors, that is, it may be a user behavior sequence, which can be set according to actual needs, and the present invention does not make specific limitations on this.

[0089] In a possible embodiment, Figure 2 As shown, user behavior configuration can be performed through the following process.

[0090] S201. First, create rules and configure behavior nodes. The behavior node configuration includes existing tracking behaviors, special events, and manual tracking behaviors.

[0091] The above-mentioned tracking behaviors and special events can be set according to the actual business scenarios. Existing tracking behaviors refer to the tracking behaviors written when developing the APP, manual tracking behaviors refer to the behaviors written in the front-end page event listener, and special behaviors can be rollback, refresh, etc.

[0092] S202, configure node attributes, including the configuration of the number of hits, hit time, and whether an event is hit. The above-mentioned node refers to an event, and a hit event refers to an event hit that needs to be hit.

[0093] S203, configuring the relationship between nodes, including similar nodes and dependent nodes, wherein a similar node refers to that any one of the two nodes can occur, and a dependent node refers to that the two nodes must occur at the same time.

[0094] S204: Configure a specific behavior sequence.

[0095] S205: Select a service action corresponding to the behavior, including a service component of the business or an associated usability platform.

[0096] In a possible embodiment, after configuring the behavior configuration information, the server can send the behavior configuration information to the front-end page for storage. As a possible implementation method, the behavior configuration information can be stored in correspondence with the corresponding front-end page identifier, which can be the address, number, etc. of the front-end page. The above-mentioned behavior configuration information can be stored in correspondence with a single front-end page or with multiple front-end pages, and the front-end page can be determined according to the specific user behavior. For example, for a service operation set by a user to switch between two front-end pages, the behavior configuration information can be stored in correspondence with the two front-end pages.

[0097] In another possible embodiment, the above-mentioned behavior configuration information may be sent to the front-end page when the front-end page is opened.

[0098] In a possible embodiment, the server can send the behavior configuration information to the SDK (Software Development Kit) of the front-end page. The SDK can determine the corresponding service operation based on the user behavior and / or page element changes monitored by the front-end page. The above-mentioned page elements refer to the text, images, boxes, etc. in the front-end page.

[0099] In a possible embodiment, the front-end page may include an event listener, which is used to monitor various behaviors occurring in the page, including page element changes and user behaviors, etc. After receiving the above behavior configuration information, the front-end page may register the behavior configuration information with the event listener.

[0100] In a possible embodiment, the behavior configuration information in the server is in the form of instructions, and the behavior configuration information in the form of instructions cannot be directly executed by the machine. Therefore, after receiving the behavior configuration information, the above-mentioned SDK can integrate the behavior configuration information in the form of instructions, convert it into a machine-executable code form, and register the behavior configuration information in the code form to the event listener.

[0101] In a possible embodiment, since different front-end pages may use different fields to store different user behaviors or page element information, before registering the behavior configuration information to the event listener, the front-end page can replace the corresponding fields in the behavior configuration information according to the fields that store page elements or user behaviors in the front-end page.

[0102] After the behavior configuration information is registered to the event listener, the event listener can monitor the front-end page according to the behavior included in the behavior configuration information, and after monitoring the corresponding user behavior, the corresponding behavior can be triggered.

[0103] In a possible embodiment, the above event listener may include a buried event listener and a page behavior listener;

[0104] The front-end page is used to register the preset embedding events contained in the behavior configuration information to the embedding event listener based on the behavior configuration information, and register the preset page behavior events contained in the behavior configuration information to the page behavior listener; the preset embedding events include page element change events, and the preset page behavior events include refresh page and rollback page;

[0105] The embedding event listener is used to monitor the user behavior in the front-end page based on the preset embedding event;

[0106] The page behavior listener is used to monitor the user behavior in the front-end page based on the preset page behavior event.

[0107] As a possible implementation method, the page element change event in the behavior configuration information can be registered in a buried event listener, and the buried event listener can be based on the page changes in the behavior configuration information. Specifically, the buried event listener can monitor page element changes through the DOM tree (Document Object Model Tree) of the front-end page. The DOM tree refers to the hierarchical structure of all elements in a web document. Each HTML tag, text node, and attribute is represented as a node in the DOM tree. They are all objects that can be accessed and operated through JavaScript or other scripting languages. In an embodiment of the present invention, buried points can be performed on the nodes corresponding to the page element changes contained in the behavior configuration information, and when the changes of these nodes are monitored, the corresponding behavior is triggered.

[0108] As mentioned above, the front-end page can be a web page or a page in the APP. Therefore, in a possible embodiment, the above-mentioned page behavior listener can be an end event listener or an H5 page listener, wherein the end event listener is used to monitor the preset page behavior in the APP, and the H5 page listener is used to monitor the preset page behavior in the H5 page. As a possible implementation method, the user behavior in the behavior configuration information can be registered in the end event listener, and the APP's own capabilities can be used to monitor various user behaviors in the APP web page. The H5 event listener refers to the event listener in the H5 web page. As a possible implementation method, the user behavior contained in the behavior configuration information can be written into the H5 event listener.

[0109] The behaviors written into the page behavior listener may include backing off, refreshing, and scrolling of a web page.

[0110] In a possible embodiment, for the above-mentioned web page rollback behavior, the popstate event, vuerouter event and page hashchange event in the H5 page can be monitored simultaneously when the SDK is running. If the above events are detected, they can be intercepted to determine that the rollback event is monitored.

[0111] In a possible embodiment, in order to avoid repeated interception, an interception cache can be set. Specifically, if a page is intercepted by any of the above three events, the page ID and page status of the page can be recorded. When the fallback behavior related event is subsequently triggered, it can be determined whether the cache exists. If it exists, the fallback behavior related to the event can be not recorded to avoid multiple records of the same behavior. As a possible implementation method, the page ID and page status can be cached through sessionstrage, and each page ID and corresponding page status correspond to a pagesessionId. When the page is closed, the above cache can be automatically deleted. If the page is entered repeatedly, the cached pagesessionId can be updated.

[0112] In a possible embodiment, for the above web page refresh behavior, when running the SDK, you can listen to the beforeunload event before the page is refreshed, and listen to the window.performace.navigation.type property after the page is re-entered. If both are triggered, it is considered that a refresh behavior has occurred.

[0113] The behavior configuration information may include executing certain user behaviors within a preset time period. Therefore, in a possible embodiment, the event monitored by the event listener may include a timestamp, which may be provided by a timer in the front-end page.

[0114] In a possible embodiment, Figure 3 As shown, you can initialize the SDK by following the steps below:

[0115] S301. Load JsSDK.

[0116] S302: Load configuration data, that is, load the above behavior configuration information.

[0117] S303, data processing, including page multi-hash conversion, configuration field replacement, data structure conversion, acquaintance node processing, and mutually exclusive node processing. Among them, data structure conversion refers to converting configuration data into a monitoring data structure, and the configuration data includes whether it is hit, the time from the last node trigger, the similar node list, the concurrent node list, the matching type is sequential matching or fuzzy matching, the additional data list, the matching status, and the matching behavior data.

[0118] Page multi-hash conversion refers to converting page attributes into corresponding hash values. Determining a unique behavior node usually requires multiple attribute association combinations, and the amount of stored data is large. By converting the corresponding matching attributes into a unique hash value, memory usage can be reduced.

[0119] S304, the service action registers a hook, that is, it is set as a hook function, and the service action can be triggered when the function condition is met.

[0120] S305: Configure action binding, that is, bind the behavior with the service operation.

[0121] S306: Register the instruction and transform the behavior sequence.

[0122] S307: Start an event listener, which includes a page behavior listener and a buried event listener.

[0123] S308. Perform sequential matching or fuzzy matching on the behavior sequence, wherein the scope of sequential matching is the first behavior sequence, and the scope of fuzzy matching is all sequences, and write the matching rules into the page behavior listener and the embedded event listener.

[0124] In a possible embodiment, when the event listener listens to the user behavior in the behavior configuration information, the corresponding service operation can be triggered.

[0125] In a possible embodiment, the behavior configuration information also includes the correspondence between the user behavior sequence and the service operation; the front-end page is used to continue to monitor the target user behavior of the user when the target user behavior is in the target behavior sequence in the behavior configuration information until the target behavior sequence is executed; and determine that the service operation corresponding to the target behavior sequence is the target service operation.

[0126] For user behavior groups, when the event listener monitors user behavior, it can determine whether the user behavior is registered to the event listener. If the user behavior is registered to the event listener, it can determine whether all behaviors in the user behavior group to which the user behavior belongs have been executed. If all behaviors in the user behavior group to which the user behavior belongs have been executed, the service operation corresponding to the user group is triggered.

[0127] In a possible embodiment, the Figure 4a as well as Figure 4b The process shown is to match the behavior configuration information with the user behavior in JsSDK:

[0128] S401. Register the instruction to the event listener. Only pre-registered events will be listened to by the listener. One instruction may include multiple user behavior events.

[0129] S402: Monitor user behavior through an event listener.

[0130] S403: Obtain a user behavior event queue, and send the user behavior event queue to a monitoring event processor.

[0131] S404: The monitoring event processor obtains the user behavior event queue and processes it.

[0132] S405: For each event in the user behavior event queue, find the instruction corresponding to the current event.

[0133] S406, determine whether the instruction has been completed, if the instruction has been completed, execute S407, if the instruction has not been completed, perform matching end processing and continue to monitor events.

[0134] S407: Determine whether the user status satisfies the additional data. If yes, execute S408; if not, continue matching.

[0135] S408: Determine the current event trigger type. If it is triggered by user behavior, execute S409; if it is triggered by a timer, execute S410.

[0136] S409, determine whether the behavior sequence is a hit event, if the current event is a miss event, determine that the match fails, update the instruction state, and destroy the timer at the same time, if the current event is a hit event, execute S411. Here, a hit event refers to an event that needs to be hit, and a miss event refers to an event that does not need to be hit.

[0137] S410, determine whether the behavior event is a hit event, if it is a hit event, determine that the match fails, and update the instruction status. If it is a miss event, execute S412. Here, a hit event refers to a miss of an event that needs to be hit, and a miss event refers to a miss of an event that does not need to be hit.

[0138] S411, determine whether the number of matching behaviors in the instruction is greater than 1, if so, reduce the number of matching behaviors by 1 and continue matching, if not, execute S412.

[0139] S412: Determine whether the behavior sequence matches successfully.

[0140] S413, determine whether there is a concurrent or similar behavior sequence, if so, execute S429, if not, execute S414.

[0141] S429: Determine whether the behavior sequence that needs to be concurrent is completed. If so, execute S414; if not, continue matching.

[0142] S414, update the current behavior sequence state, then execute Figure 4b Step S415 in .

[0143] S415: Delete the monitoring of the current behavior sequence.

[0144] S416: Whether the node is a special behavior event, if so, execute S417, if not, execute S418.

[0145] S417. Stop the current special event.

[0146] S418: Determine whether it is a sequential match, if so, execute S419, if not, execute S420.

[0147] S419, determine whether the node is the last node in the sequential matching, if so, execute S420, if not, execute S421.

[0148] S420: Determine that the match is successful and update the instruction status.

[0149] S421. Calculate the subsequent behavior sequence.

[0150] S422: Whether the subsequent behavior sequence is a behavior sequence group, if so, execute S423, if not, execute S424.

[0151] S423. Analysis of the nature of behavioral sequences.

[0152] S424. Register the next behavior sequence.

[0153] S425. Add the behavior sequence to the event listener.

[0154] S426: Determine whether to wait for the node, if so, execute S427, if not, execute S428.

[0155] S427: Add the behavior sequence to the timer and return to the timer monitoring.

[0156] S428: Determine whether the behavior sequence attribute is matched. If not, register the next behavior sequence. If yes, repeat the above process.

[0157] In a possible embodiment, the LRU strategy (Least Recently Used, cache elimination algorithm) can be used in the matching process to manage the cache of the user's analysis behavior records. When certain continuous behaviors of the user reach a certain threshold, they are reported through the embedding point, and when the trigger interval reaches a certain threshold, the current behavior record can be cleared. As a possible implementation method, a bidirectional linked list can be used, that is, user behavior and time are used as primary keys respectively, and the corresponding relationship between user behavior and time is stored. In this way, it can support the LRU strategy record location while reducing the time complexity of the query to 1, and at the same time reduce the computational overhead caused by data operations.

[0158] In a possible embodiment, only the matching range of the minimum behavior sequence can be monitored and processed according to the issued behavior sequence to improve the matching efficiency. After the relevant behavior is monitored, the corresponding listener and data memory are cleared. The above minimum behavior sequence can be set according to actual needs.

[0159] In a possible embodiment, a user behavior blacklist may be preset, and the user behavior blacklist may include abnormal user behaviors, and the abnormal user behaviors may be single user behaviors or abnormal user behavior groups composed of multiple user behaviors.

[0160] As a possible implementation mode, the server is further used to obtain a behavior blacklist, which includes preset abnormal behaviors; and send the behavior blacklist to the front-end page;

[0161] The front-end page is further used to report the abnormal behavior information of the user to the server when the target user behavior belongs to the behavior blacklist;

[0162] The server is used to push the abnormal behavior information to a preset client.

[0163] The user behavior blacklist can also be operated according to the above registration and matching process, which will not be repeated here. When the user behavior is identified as belonging to the user behavior blacklist, the user behavior can be reported. Specifically, the user behavior and user information can be sent to the server, and the server can push the user behavior and user information to relevant personnel through email, instant messaging, etc.

[0164] In a possible embodiment, the front-end page is also used to send the user's response to the target service operation to the server; the server is used to adjust the behavior configuration information based on the user's response to the target service operation and the user tag, and the user tag is a preset AB experiment tag.

[0165] The above-mentioned response conditions may include click conditions, purchase conditions, etc., which can be set according to actual needs. The above-mentioned user labels can be set according to actual needs. For example, different service operations can be performed for the same user behavior, and label A is set for the user corresponding to service operation A, and label B is set for the user corresponding to service operation B. Then, the service operation corresponding to the user behavior can be determined according to the response of users with different labels to the service operation. Exemplarily, for the behavior of users clicking on the product details page, a voucher pop-up window can be pushed to user A with label A, and a price reduction pop-up window can be pushed to user B with label B. If user A makes a purchase for the product and user B does not make a purchase, it can be determined that the service operation corresponding to the behavior of clicking on the product details page is to push a voucher pop-up window.

[0166] In a possible embodiment, when the front-end page is closed, the behavior configuration information in the front-end page may be deleted to release the corresponding storage space, thereby preventing useless behavior configuration information from occupying too much storage space.

[0167] In a possible embodiment, in order to avoid excessive disturbance to the user, Figure 5 As shown, the service operation corresponding to the user behavior can be triggered by the following steps:

[0168] S501, the event listener monitors user behavior.

[0169] S502: Match the user behavior and the corresponding relationship between the preset behavior sequence and the service operation through the above matching algorithm.

[0170] S503, determine whether multiple instructions are triggered. If multiple instructions are triggered, it can be determined that the user behavior triggers the instruction group, so the following steps S504-S510 can be executed according to the registration order of each instruction.

[0171] S504, determine whether the current instruction has been triggered, if not, determine that the current instruction service triggering fails, and execute S510, if yes, execute S505.

[0172] S505, determine whether the current service has been triggered, if so, execute S506, if not, determine that the current instruction service triggering fails, and execute S510.

[0173] S506: Determine the current service type. If it is an external registration type, execute S507; if it is an SDK monitoring behavior, execute S508.

[0174] S507, determine whether the service is registered, if not, determine that the current execution of the service trigger fails, and execute S510, if yes, execute S508.

[0175] S508: Service triggering.

[0176] S509: Record the triggered service and determine whether the current instruction trigger is completed.

[0177] S510, determine whether there are other instructions to be triggered, if so, return to S503, if not, execute S509.

[0178] As a user service matcher and trigger, this function will issue multiple identical or different user services when connected to multiple systems. At the same time, due to the uncertainty of the user behavior trigger time, the service action priority cannot be defined. Through the above process, the same page and the same component will only be triggered once to avoid excessive disturbance to the user.

[0179] like Figure 6 As shown, Figure 6 A schematic diagram of a life cycle of a page interaction system provided in an embodiment of the present invention may specifically include three stages: loading, matching, and destroying:

[0180] During the loading phase, the front-end page obtains the behavior configuration information sent by the server, integrates the behavior configuration information, obtains the behavior configuration information in code form, and achieves tracking point compatibility through field replacement, and registers the user behavior contained in the behavior configuration information in the event listener. During the loading phase, the front-end page can also divide similar user behavior sequences in the behavior configuration information into the same user behavior group, and customize the user behaviors to be monitored, including refresh, rollback, and mouse scrolling, etc.

[0181] During the matching stage, the front-end page can monitor events through event listeners and match the monitored user behaviors. The matching process includes single user behavior matching, multiple user behavior matching, and additional attribute matching. The additional attributes may include product lines, channels, etc. After a successful match, the corresponding service action can be triggered. When abnormal user behavior is monitored, the abnormal user behavior information can be reported to the server.

[0182] In the destruction phase, the behavior configuration information sent from the server to the front-end page can be deleted, and the event listener can be unbound from the user behavior in the behavior configuration information, and the timer can be cleared.

[0183] like Figure 7 As shown, Figure 7 A schematic diagram of an interaction process of a page interaction system provided by an embodiment of the present invention, the process may include:

[0184] S701. When a user accesses an H5 page, the SDK of the H5 page obtains a data source, namely, behavior configuration information, from a configuration platform.

[0185] S702, SDK assembles configuration instructions, including data integration, configuration action binding and configuration field replacement, to obtain behavior configuration information in the form of code executable by SDK.

[0186] S703, SDK registers configuration instructions, including registering behavior configuration information in code form to the event listener, which may include a point-of-view event listener and a page behavior listener, wherein the point-of-view event listener may generate point-of-view data, specifically, the point-of-view data is the change data of the page elements. The page behavior listener includes an end capability event listener and an H5 event listener, specifically, the user behavior contained in the behavior configuration information may be written into the APP, so that the APP uses the end function to monitor the user behavior, and for the H5 event listener, the events that need to be monitored may be written, which may include rollback, refresh, and mouse scrolling, etc.

[0187] S704. When the SDK receives user behavior data, it determines whether the event type is a tracking type or an event type through the event listener, and determines in the corresponding listener whether there is a related event registration. If there is a related event registration, it determines whether the corresponding instruction of the registration has been executed. If there is no related event registration or the corresponding instruction has not been executed, it continues to listen.

[0188] S705, triggering the command service and sending the command data to the H5 page.

[0189] S706, the service component of the H5 page triggers the corresponding service based on the obtained instruction data. The services here include user service category and business service category. Among them, the user service category refers to service operations related to improving user experience, such as operation guidance, and business services are service operations related to purchasing behavior, such as coupon issuance pop-up windows, price adjustment pop-up windows, questionnaires, etc.

[0190] Figure 8 A schematic diagram of the architecture of a page interaction system provided by an embodiment of the present invention. The page interaction system may include a configuration layer, an analysis layer, and a data layer.

[0191] Among them, the configuration layer is used to configure the behavior sequence, the touch action, and the correspondence between the behavior sequence and the touch action, and send these configuration information to the analysis layer. The data layer is used to obtain the user's behavior data, user information data and abnormal data in the front-end page. The above-mentioned user information data may include page status data (i.e., page element data), user tags and experimental tags. The above-mentioned abnormal data may include relevant data such as page blank pages, long stay time and interface errors. The analysis layer is used to parse the configuration information and perform real-time analysis based on the user behavior data to obtain the service operation corresponding to the user behavior. The service operation includes customer service guidance, content guidance, coupon pop-up window, price adjustment pop-up window and difference survey questionnaire, etc.

[0192] By applying the embodiments of the present invention, it is possible to identify a series of operations such as user entry within a page, display of page elements, waiting time, click, scroll, refresh, and rollback, and then intelligently provide real-time services to users with specific behavior sequences on the front-end page, including but not limited to: guiding clicks on specific page elements, pop-up guidance, customer service push, etc., to provide users with personalized and real-time services, improve user experience, and intelligently analyze possible abnormal user behaviors, and report and subsequently analyze these behaviors.

[0193] Based on the same inventive concept, an embodiment of the present invention further provides a page interaction method, which can be applied to any electronic device with a page interaction function, such as a computer, a mobile terminal, etc. In a possible embodiment, the page interaction method can be applied to the front-end page in the above-mentioned page interaction system, wherein the page interaction system also includes a server, such as Fig. 9 As shown, the method may include:

[0194] S901, obtaining behavior configuration information, wherein the behavior configuration information includes a correspondence between user behavior and service operation; the behavior configuration information is sent from the server to the front-end page;

[0195] S902, monitoring the target user behavior of the user on the front-end page, wherein the user behavior includes refreshing the page and returning to the page;

[0196] S903, determining a target service operation corresponding to the target user behavior based on the behavior configuration information;

[0197] S904: Execute the target service operation.

[0198] In a possible embodiment, the front-end page includes a buried event listener and a page behavior listener; the method includes:

[0199] Based on the behavior configuration information, the preset embedding events contained in the behavior configuration information are registered to the embedding event listener, and the preset page behavior events contained in the behavior configuration information are registered to the page behavior listener; the preset embedding events include page element change events, and the preset page behavior events include refresh page and rollback page;

[0200] The user behavior in the front-end page is monitored based on the preset embedding event by the embedding event listener;

[0201] The page behavior listener monitors the user behavior in the front-end page based on the preset page behavior event.

[0202] In a possible embodiment, the behavior configuration information also includes a correspondence between a user behavior sequence and a service operation; and the method further includes:

[0203] When the target user behavior is in the target behavior sequence in the behavior configuration information, continue to monitor the target user behavior of the user until the target behavior sequence is completed;

[0204] The service operation corresponding to the target behavior sequence is determined as the target service operation.

[0205] In a possible embodiment, the method further includes:

[0206] Obtaining a behavior blacklist, wherein the behavior blacklist includes preset abnormal behaviors; the behavior blacklist is sent by the server to the front-end page;

[0207] In the case that the target user behavior belongs to the behavior blacklist, the abnormal behavior information of the user is reported to the server; so that the server pushes the abnormal behavior information to the preset client.

[0208] In a possible embodiment, the method further includes:

[0209] The user's response to the target service operation is sent to the server; so that the server adjusts the behavior configuration information based on the user's response to the target service operation and the user tag, where the user tag is a preset AB experiment tag.

[0210] According to another aspect of the present invention, a page interaction method is provided, which is applied to a server in a page interaction system, wherein the page interaction system further includes a front-end page, such as Fig.10 As shown, the method may include:

[0211] S1001, obtaining behavior configuration information, wherein the behavior configuration information includes a correspondence between user behaviors and service operations;

[0212] S1002. Send the behavior configuration information to the front-end page; so that the front-end page monitors the target user behavior of the user on the front-end page, and the user behavior includes refreshing the page and rolling back the page; based on the behavior configuration information, determine the target service operation corresponding to the target user behavior; and execute the target service operation.

[0213] In a possible embodiment, the method further includes:

[0214] Obtaining a behavior blacklist, wherein the behavior blacklist includes preset abnormal behaviors;

[0215] Sending the behavior blacklist to the front-end page; so that the front-end page reports the abnormal behavior information of the user to the server when the behavior of the target user belongs to the behavior blacklist;

[0216] The abnormal behavior information is pushed to a preset client.

[0217] In a possible embodiment, the method further includes:

[0218] The behavior configuration information is adjusted based on the user's response to the target service operation sent by the front-end page and the user tag, where the user tag is a preset AB experiment tag.

[0219] According to another aspect of the present invention, a page interaction device is provided, which is applied to a front-end page in a page interaction system. The page interaction system also includes a server, such as Fig.11 As shown, the device 1100 may include:

[0220] The first acquisition module 1101 is used to acquire behavior configuration information, wherein the behavior configuration information includes a correspondence between user behavior and service operation; the behavior configuration information is sent from the server to the front-end page;

[0221] A monitoring module 1102 is used to monitor the target user behavior of the user on the front-end page, wherein the user behavior includes refreshing the page and returning to the page;

[0222] A determination module 1103 is used to determine a target service operation corresponding to the target user behavior based on the behavior configuration information;

[0223] The execution module 1104 is used to execute the target service operation.

[0224] According to another aspect of the present invention, a page interaction device is provided, which is applied to a server in a page interaction system, wherein the page interaction system further includes a front-end page, such as Fig.12 As shown, the apparatus 1200 may include:

[0225] The second acquisition module 1201 is used to acquire behavior configuration information, wherein the behavior configuration information includes a correspondence between user behaviors and service operations;

[0226] The sending module 1202 is used to send the behavior configuration information to the front-end page; so that the front-end page monitors the target user behavior of the user on the front-end page, and the user behavior includes refreshing the page and rolling back the page; based on the behavior configuration information, determine the target service operation corresponding to the target user behavior; and execute the target service operation.

[0227] Among them, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved in the present invention are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0228] The exemplary embodiment of the present invention further provides an electronic device, comprising: at least one processor; and a memory connected to the at least one processor in communication. The memory stores a computer program that can be executed by the at least one processor, and the computer program is used to enable the electronic device to perform a method according to an embodiment of the present invention when executed by the at least one processor.

[0229] Exemplary embodiments of the present invention also provide a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to perform a method according to an embodiment of the present invention.

[0230] An exemplary embodiment of the present invention further provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor of a computer, the computer is used to enable the computer to perform a method according to an embodiment of the present invention.

[0231] refer to Fig.13, a block diagram of an electronic device 1300 that can be used as a server or client of the present invention will now be described, which is an example of a hardware device that can be applied to various aspects of the present invention. The electronic device is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0232] like Fig.13 As shown, the electronic device 1300 includes a computing unit 1301, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 1302 or a computer program loaded from a storage unit 1308 into a random access memory (RAM) 1303. In the RAM 1303, various programs and data required for the operation of the electronic device 1300 can also be stored. The computing unit 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. An input / output (I / O) interface 1305 is also connected to the bus 1304.

[0233] A plurality of components in the electronic device 1300 are connected to the I / O interface 1305, including: an input unit 1306, an output unit 1307, a storage unit 1308, and a communication unit 1309. The input unit 1306 may be any type of device capable of inputting information to the electronic device 1300, and the input unit 1306 may receive input digital or character information, and generate key signal inputs related to user settings and / or function control of the electronic device. The output unit 1307 may be any type of device capable of presenting information, and may include but is not limited to a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. The storage unit 1308 may include but is not limited to a disk, an optical disk. The communication unit 1309 allows the electronic device 1300 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks, and may include but is not limited to a modem, a network card, an infrared communication device, a wireless communication transceiver, and / or a chipset, such as a Bluetooth™ device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.

[0234] The computing unit 1301 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 1301 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 1301 performs the various methods and processes described above. For example, in some embodiments, the above-mentioned page interaction method may be implemented as a computer software program, which is tangibly included in a machine-readable medium, such as a storage unit 1308. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 1300 via the ROM 1302 and / or the communication unit 1309. In some embodiments, the computing unit 1301 may be configured to perform the above-mentioned page interaction method by any other appropriate means (e.g., by means of firmware).

[0235] The program code for implementing the method of the present invention can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or entirely on a remote machine or server.

[0236] In the context of the present invention, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0237] As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0238] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0239] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0240] A computer system may include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other.

Claims

1. A page interaction system, characterized in that: The system includes: a front-end page and a server; The server is used to obtain behavior configuration information, which includes the corresponding relationship between user behavior and service operation; and send the behavior configuration information to the front-end page; The front-end page is used to monitor the target user behavior of the user on the front-end page, wherein the user behavior includes refreshing the page and rolling back the page; based on the behavior configuration information, determine the target service operation corresponding to the target user behavior; and execute the target service operation.

2. The system according to claim 1, characterized in that The front-end page includes a buried event listener and a page behavior listener; The front-end page is used to register the preset embedding events contained in the behavior configuration information to the embedding event listener based on the behavior configuration information, and register the preset page behavior events contained in the behavior configuration information to the page behavior listener; the preset embedding events include page element change events, and the preset page behavior events include refresh page and rollback page; The embedding event listener is used to monitor the user behavior in the front-end page based on the preset embedding event; The page behavior listener is used to monitor the user behavior in the front-end page based on the preset page behavior event.

3. The system according to claim 2, characterized in that The page behavior listener includes an end event listener or an H5 page listener, wherein the end event listener is used to monitor the preset page behavior in the APP, and the H5 page listener is used to monitor the preset page behavior in the H5 page.

4. The system according to claim 1, characterized in that The behavior configuration information also includes the corresponding relationship between the user behavior sequence and the service operation; The front-end page is used to continue monitoring the target user behavior of the user when the target user behavior is in the target behavior sequence in the behavior configuration information until the target behavior sequence is executed; and determine that the service operation corresponding to the target behavior sequence is the target service operation.

5. The system according to claim 1, characterized in that The server is further used to obtain a behavior blacklist, which includes preset abnormal behaviors; and send the behavior blacklist to the front-end page; The front-end page is further used to report the abnormal behavior information of the user to the server when the target user behavior belongs to the behavior blacklist; The server is used to push the abnormal behavior information to a preset client.

6. The system according to claim 1, characterized in that The front-end page is also used to send the user's response to the target service operation to the server; the server is used to adjust the behavior configuration information based on the user's response to the target service operation and the user tag, and the user tag is a preset AB experiment tag.

7. A page interaction method, characterized in that: The method is applied to a front-end page in a page interaction system, wherein the page interaction system also includes a server, and the method includes: Obtaining behavior configuration information, wherein the behavior configuration information includes a correspondence between user behavior and service operation; the behavior configuration information is sent from the server to the front-end page; Monitor the target user behavior of the user on the front-end page, wherein the user behavior includes refreshing the page and returning to the page; Based on the behavior configuration information, determining a target service operation corresponding to the target user behavior; The target service operation is executed.

8. The method according to claim 7, characterized in that The front-end page includes a buried event listener and a page behavior listener; the method includes: Based on the behavior configuration information, the preset embedding events contained in the behavior configuration information are registered to the embedding event listener, and the preset page behavior events contained in the behavior configuration information are registered to the page behavior listener; the preset embedding events include page element change events, and the preset page behavior events include refresh page and rollback page; The user behavior in the front-end page is monitored based on the preset embedding event by the embedding event listener; The page behavior listener monitors the user behavior in the front-end page based on the preset page behavior event.

9. The method according to claim 8, characterized in that The behavior configuration information also includes a correspondence between a user behavior sequence and a service operation; the method further includes: When the target user behavior is in the target behavior sequence in the behavior configuration information, continue to monitor the target user behavior of the user until the target behavior sequence is completed; The service operation corresponding to the target behavior sequence is determined as the target service operation.

10. The method according to claim 7, characterized in that The method further comprises: Obtaining a behavior blacklist, wherein the behavior blacklist includes preset abnormal behaviors; the behavior blacklist is sent by the server to the front-end page; In the case that the target user behavior belongs to the behavior blacklist, the abnormal behavior information of the user is reported to the server; so that the server pushes the abnormal behavior information to the preset client.

11. The method according to claim 7, characterized in that The method further comprises: The user's response to the target service operation is sent to the server; so that the server adjusts the behavior configuration information based on the user's response to the target service operation and the user tag, where the user tag is a preset AB experiment tag.

12. A page interaction method, characterized in that: The method is applied to a server in a page interaction system, wherein the page interaction system also includes a front-end page, and the method includes: Acquire behavior configuration information, wherein the behavior configuration information includes a correspondence between user behavior and service operation; The behavior configuration information is sent to the front-end page; so that the front-end page monitors the target user behavior of the user on the front-end page, and the user behavior includes refreshing the page and rolling back the page; based on the behavior configuration information, the target service operation corresponding to the target user behavior is determined; and the target service operation is executed.

13. A page interaction device, characterized in that: The front-end page is applied to a page interaction system, wherein the page interaction system also includes a server, and the device includes: A first acquisition module is used to acquire behavior configuration information, wherein the behavior configuration information includes a correspondence between user behavior and service operation; the behavior configuration information is sent from the server to the front-end page; A monitoring module, used to monitor the target user behavior of the user on the front-end page, wherein the user behavior includes refreshing the page and returning to the page; A determination module, configured to determine a target service operation corresponding to the target user behavior based on the behavior configuration information; An execution module is used to execute the target service operation.

14. A page interaction device, characterized in that: The server end is applied to a page interaction system, wherein the page interaction system also includes a front-end page, and the device includes: A second acquisition module is used to acquire behavior configuration information, wherein the behavior configuration information includes a correspondence between user behaviors and service operations; The sending module is used to send the behavior configuration information to the front-end page; so that the front-end page monitors the target user behavior of the user on the front-end page, and the user behavior includes refreshing the page and rolling back the page; based on the behavior configuration information, determine the target service operation corresponding to the target user behavior; and execute the target service operation.

15. An electronic device, comprising: processor; as well as Memory for storing programs, The program comprises instructions which, when executed by the processor, cause the processor to perform the method according to any one of claims 7-11 or 12.

16. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to make a computer execute the method according to any one of claims 7-11 or 12.