Project rule analysis method and device and computing equipment

Abstract

Embodiments of the invention provide a project rule analysis method and apparatus, and a computing device. The project rule analysis method comprises the steps of obtaining a target analysis link of a target project; a target rule process corresponding to the target analysis link is determined from preset rule processes, any rule process comprises at least one node divided based on the operation process of the target project, and any node has a corresponding project rule; dividing the user operation data of the target project based on at least one node in the target rule process to obtain the user operation data of at least one node; and generating an item rule analysis result of the target analysis link based on the user operation data and the item rule of the at least one node. The project rule action mechanism is deeply understood, which links are influenced by which project rules are clearly displayed, and therefore data support is provided for optimization of subsequent operation processes or project rules and effective improvement of the execution efficiency and effect of projects.

Description

Technical Field

[0001] The embodiments of this specification relate to the technical field of quantitative analysis, and particularly to a project rule analysis method, apparatus, and computing device. Background Art

[0002] With the development of quantitative analysis technology, the project has been quantitatively analyzed by means of statistical methods, machine learning algorithms, etc. to guide project optimization.

[0003] Currently, by adopting the method of refining the quantitative analysis dimension, the multi-dimensional analysis of the project can be completed, and the multi-dimensional project quantitative analysis results can be obtained. For example, according to different user types, the quantitative analysis of the product placement project under multiple user types can be completed, and the advertising placement volume for specific user types can be increased.

[0004] However, the multi-dimensional analysis method often does not combine with the operation process of the project itself, lacks a clear understanding of the action mechanism of project rules, resulting in that the project quantitative analysis results cannot clearly show which links are affected by which project rules, and it is difficult to complete the optimization of the operation process or project rules according to the project quantitative analysis results, and thus it is impossible to effectively improve the execution efficiency and effect of the project. For example, it is not clear which link (such as target positioning, creative design, placement time selection, etc.) in the advertising placement process for different user types generates different response rates or conversion rates, so it is difficult to adjust the placement strategy targeted to improve the advertising placement effect. Summary of the Invention

[0005] In view of this, the embodiments of this specification provide a project rule analysis method. One or more embodiments of this specification also relate to a project rule analysis apparatus, a computing device, a computer-readable storage medium, and a computer program product to solve the technical defects existing in the prior art.

[0006] According to the first aspect of the embodiments of this specification, a project rule analysis method is provided, including: Obtain the target analysis link of the target project; Determine the target rule process corresponding to the target analysis link from the preset rule processes, where any rule process includes at least one node divided based on the operation process of the target project, and any node has a corresponding project rule; Based on at least one node in the target rule process, divide the user operation data of the target project to obtain the user operation data of at least one node; Generate the project rule analysis result of the target analysis link based on the user operation data and project rules of at least one node.

[0007] According to a second aspect of the embodiments of the present specification, there is provided an item rule analysis device, including: An acquisition module, configured to acquire a target analysis link of a target item; A determination module, configured to determine, from a preset rule process, a target rule process corresponding to the target analysis link, where any rule process includes at least one node divided based on an operation process of the target item, and any node has a corresponding item rule; A division module, configured to divide user operation data of the target item based on at least one node in the target rule process to obtain user operation data of at least one node; A generation module, configured to generate an item rule analysis result of the target analysis link based on the user operation data of at least one node and the item rule.

[0008] According to a third aspect of the embodiments of the present specification, there is provided a computing device, including: A memory and a processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the above method are implemented.

[0009] According to a fourth aspect of the embodiments of the present specification, there is provided a computer-readable storage medium storing computer-executable instructions, and when the instructions are executed by a processor, the steps of the above method are implemented.

[0010] According to a fifth aspect of the embodiments of the present specification, there is provided a computer program product, where when the computer program product is executed on a computer, the computer is made to execute the steps of the above method.

[0011] In an embodiment of the present specification, a target analysis link that needs to be quantitatively analyzed for a target item is acquired, and a target rule process corresponding to the target analysis link is determined from a preset rule process. Since the rule process divides multiple nodes based on the operation process of the target item itself, and each node corresponds to a specific item rule of the target item, therefore, by dividing the user operation data based on at least one node of the target rule process, user operation data of each node that can accurately reflect the influence of the node rule can be obtained. Based on this, a detailed item rule analysis result is generated based on the user operation data of at least one node and the corresponding item rule. The mechanism of action of the item rule is deeply understood, and it is clearly shown which links are affected by which item rules, thereby providing data support for the subsequent optimization of the operation process or item rules and effectively improving the execution efficiency and effect of the item. Description of the Drawings

[0012] Figure 1One of the schematic diagrams of the project rule analysis result of a project rule analysis method; Figure 2 Another schematic diagram of the project rule analysis result of a project rule analysis method; Figure 3 A schematic flow diagram of a project rule analysis method; Figure 4 A flowchart of a project rule analysis method provided by an embodiment of this specification; Figure 5 A schematic diagram of the project rule analysis result of a project rule analysis method provided by an embodiment of this specification; Figure 6 A schematic diagram of the analysis link of a project rule analysis method provided by an embodiment of this specification; Figure 7 One of the schematic diagrams in chart format of the project rule analysis result of a project rule analysis method provided by an embodiment of this specification; Figure 8 Another schematic diagram in chart format of the project rule analysis result of a project rule analysis method provided by an embodiment of this specification; Figure 9 A schematic structural diagram of a project rule analysis device provided by an embodiment of this specification; Figure 10 A structural block diagram of a computing device provided by an embodiment of this specification. Detailed implementation manners

[0013] Many specific details are set forth in the following description in order to provide a thorough understanding of this specification. However, this specification can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the connotation of this specification. Therefore, this specification is not limited by the specific implementations disclosed below.

[0014] The terms used in one or more embodiments of this specification are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of this specification. The singular forms "a", "the", and "said" used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly dictates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0015] It should be understood that although the terms first, second, etc. may be used in one or more embodiments of this specification to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "when" or "while" or "in response to determining".

[0016] In addition, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data that have been authorized by the user or fully authorized by all parties. And the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0017] First, the noun terms involved in one or more embodiments of this specification are explained.

[0018] Moving line: Also known as process or information flow, it refers to the route and path of information flow.

[0019] Operation process: Also known as the user behavior moving line, it refers to the process of users using the project.

[0020] Strategy analysis: It refers to a means of making the project strategy transparent by using quantitative analysis of the rules and specific logics involved in the project strategy of the project.

[0021] With the development of quantitative analysis technology, the project has been quantitatively analyzed by means of statistical methods, machine learning algorithms, etc. to guide project optimization.

[0022] Currently, by adopting the method of refining the quantitative analysis dimension, multi-dimensional analysis of the project can be completed, and multi-dimensional project quantitative analysis results can be obtained. Taking risk quantification as an example, Figure 1 Fig. shows one of the schematic diagrams of the project rule analysis results of a project rule analysis method, as shown in the figure: The product conversion leakage in the risk quantification platform only focuses on the admitted customer groups, and then the admitted customer groups are classified into different types according to different admission types, such as credit base admission, application admission, credit non-admission & request non-admission, etc. Further, it can be refined into weak operation requiring self-certification, potential operation requiring self-certification, only resource quota improvement admission, pre-credit admission, marketing resource quota admission, credit information solidification admission, resource quota improvement admission.

[0023] For different access types, it is possible to further view the specific leakage situations of each type. For example, when viewing the credit limit increase access, it is possible to analyze the specific visiting users, the number of users with different credit limit increase types, and various subsequent operation links of different users. As Figure 2 shown Figure 2 Figure 2 shows the second schematic diagram of the project rule analysis result of a project rule analysis method: Among the visiting users, some are credit limit increase access, some are basic credit granting access, and some are not allowed access.

[0024] Figure 3 Figure 1 shows the schematic flowchart of a project rule analysis method, as Figure 3 shown: Based on Figure 2 , click on "Details" to view the specific leakage types, and then click on "View Reasons" to see the list of specific policy rejection codes.

[0025] The above Figure 1 - Figure 3 The above solutions can, to a certain extent, show the impact of risk strategies on the project operation process, but there are the following problems: 1. It is too technical in perspective; 2. The customer group view is separated from the core operation link of the project, and it is impossible to clearly see the whole link, and the experience is not optimized enough; 3. It is not combined with the operation process of the project itself, only focusing on a small number of core operations on the core links such as credit granting access, credit limit increase, and utilization, resulting in a high understanding cost for users and insufficient convenience; 4. The reasons for leakage can only be seen at the rejection code level, without understanding the specific project rules and reasons, and there is no direction for optimization.

[0026] In summary, since the multi-dimensional analysis method often fails to combine with the operation process of the project itself and lacks a clear understanding of the action mechanism of project rules, the project quantitative analysis results cannot clearly show which links are affected by which project rules, making it difficult to optimize the operation process or project rules based on the project quantitative analysis results, and thus unable to effectively improve the execution efficiency and effect of the project.

[0027] To address the above problems, this specification provides a project rule analysis method. This specification also relates to a project rule analysis device, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail one by one in the following embodiments.

[0028] See Figure 4 , Figure 4 Figure 3 shows the flowchart of a project rule analysis method provided according to an embodiment of this specification, including the following specific steps: Step 402: Obtain the target analysis link of the target project.

[0029] This specification applies to websites, applications, or system platforms with quantitative analysis functions. For example, an e-commerce platform uses a quantitative analysis platform to optimize its product recommendation algorithm to increase the user purchase rate. Another example is that a social media website uses a quantitative analysis platform to analyze user interaction behaviors to enhance user stickiness. Still another example is that an online advertising placement system uses a quantitative analysis platform to increase the ad click-through rate and conversion rate. Also, a content sharing application uses a quantitative analysis platform to increase the click-through rate and completion rate of multimedia content. Additionally, a risk quantification platform for a resource application optimizes its project rules and the number of resource projects successfully applied for by users.

[0030] The target project is a product or activity that requires quantitative analysis. The target project usually involves a project strategy composed of a large number of project rules and needs to improve the rationality of its project rules and / or the user experience of the project through quantitative analysis. For example, the product recommendation algorithm of an e-commerce platform, the interaction function of a social media website, the advertising placement strategy, the multimedia content recommendation algorithm, and the resource projects of a resource application.

[0031] The analysis link is an analysis path that can be used for quantitative analysis of the target project. It can be a specific operation process in the target project, a combination of a series of key nodes defined according to user behavior or project requirements, or multiple sub-paths obtained by dividing the operation process based on different dimensions (such as time, user type, geographical location, etc.). For example, for the resource projects of a resource application, the application for user resources includes 8 different access operation processes such as non-approval for credit, pre-approved access, marketing quota access, potential business self-certification, and solidified credit access, corresponding to 3 analysis links: non-branching type, single-branching type, and multi-branching type.

[0032] The target analysis link of the target project is an analysis path that needs to be used for quantitative analysis of the target project. It can be a specific operation process in the target project, a combination of a series of key nodes defined according to user behavior or project requirements, or multiple sub-paths obtained by dividing the operation process based on different dimensions (such as time, user type, geographical location, etc.).

[0033] One optional way to obtain the target analysis link of the target project is to receive the target analysis link of the target project input by the front end.

[0034] For example, on a risk quantification platform of a resource platform, it is necessary to conduct a quantitative analysis on the user application of a resource project of the resource platform to analyze why the user credit success rate of the current resource project is not high and the resource expenditure success rate is not high, and which project rules are specifically affected. The operator of the resource platform selects the multi-branch type as the target analysis link from the three analysis links of the non-branch type, the single-branch type and the multi-branch type on the risk quantification platform.

[0035] Obtain the target analysis link of the target project, providing data support for the subsequent determination of the corresponding target rule process.

[0036] Step 404: Determine the target rule process corresponding to the target analysis link from the preset rule process, wherein any rule process includes at least one node divided based on the operation process of the target project, and any node has a corresponding project rule.

[0037] The operation process of the target project is the time sequence of operations that need to be performed in order to achieve the project objectives of the target project, including at least one link, arranged in a certain logical order, and covering the key steps and / or activities from the start to the completion of the target project. For example, the rule process of the resource project includes the following nodes: user access, qualification review, risk assessment, credit review and other links.

[0038] The project rules of the target project are conditions used to guide or constrain the operation of the target project. Based on the project goals and execution logic settings of the target project, it ensures that all aspects of the target project can operate in the expected manner, thereby achieving the project goals. For example, the project rules of the resource project include a risk strategy composed of multiple risk rules to review user qualifications and complete user credit for the resource project.

[0039] The rule flow is the logical flow of the project rules of the target project arranged according to the operation flow of the target project, including at least one node. Any node represents a link in the operation flow of the target project, and the project rules of the target project correspond to this link. There are multiple rule flows preset to correspond to the analysis links that need to perform quantitative analysis on the target project. For example, the rule flow of the resource project includes the following nodes: user access, qualification review, risk assessment, credit review and other links. Each link corresponds to a node and has its corresponding project rules. For example, on the "qualification review" node, the project rule is "there are no resource usage record entries with the label "major bad record" in the user's resource records in the past two years." The target rule flow corresponding to the target analysis link is the rule flow corresponding to the target analysis link among the preset multiple rule flows.

[0040] From the preset rule process, determine the target rule process corresponding to the target analysis link. One optional way is: adopt the method of template matching to determine the target rule process corresponding to the target analysis link from the preset rule process. Another optional way is: adopt a machine learning algorithm to determine the target rule process corresponding to the target analysis link from the preset rule process, which is not limited here.

[0041] Exemplarily, adopt the method of template matching to determine the target rule process corresponding to the multi-branch type from the preset rule processes corresponding to 3 types: non-branch type, single-branch type, and multi-branch type, including 3 nodes: user information verification, credit history assessment, and resource status review. Each node represents a link of a resource item, and there is a risk rule of the target item corresponding to this link.

[0042] Determine the target rule process corresponding to the target analysis link from the preset rule process. Since the rule process divides multiple nodes based on the operation process of the target item itself, and each node corresponds to a specific item rule of the target item, it provides data support for accurately dividing the target rule process subsequently.

[0043] Step 406: Based on at least one node in the target rule process, divide the user operation data of the target item to obtain the user operation data of at least one node.

[0044] The user operation data of the target item is a set of record data that directly or indirectly generates interaction operations with the user during the execution of the target item. The user operation data reflects how the user completes the interaction through controls or page elements on the page of the target item, and is the object of quantitative analysis. The user operation data includes, but is not limited to, the user's click behavior, browsing history, purchase records, filled form information, submitted application materials, etc. By collecting and analyzing these data, the user's preferences, needs, and behavior patterns can be understood, so as to provide a basis for optimizing project rules and improving the user experience.

[0045] The user operation data of the node is the record data that directly or indirectly generates interaction operations with the user during the execution of the link corresponding to the node of the target item. The user operation data of the node reflects how the user completes the interaction through controls or page elements on the page of the link corresponding to the node of the target item. Each link corresponding to the node represents an important step or decision point in the operation process of the target item, and is the direct object of quantitative analysis. The user operation data of the node includes, but is not limited to, the user's click behavior, browsing history, purchase records, filled form information, submitted application materials, etc. By combining the project rules with the operation process of the target item, the impact of the project rules on each link in the operation process can be seen clearly.

[0046] Exemplarily, based on three nodes of the target rule process (user information verification, credit history assessment, resource status review), the user operation data of the resource project in the past day is divided to obtain the user operation data of the three nodes: For the "user information verification" node, the user operation data includes the user's registration time, login frequency, and information accuracy (such as whether the name and identity match); For the "credit history assessment" node, the user operation data includes the details of the credit report submitted by the user, the trend of credit score changes, and historical behavior records related to credit (such as resource usage records, etc.); For the "resource status review" node, the user operation data includes the user's resource certification situation, the change in the user's positive resource level, and the change in the proportion of the user's negative resources, etc.

[0047] Dividing the user operation data based on at least one node of the target rule process can obtain the user operation data of each node that accurately reflects the influence of the node rules, deeply understand the action mechanism of the project rules, clearly show which links are affected by which project rules, and provide data support for generating the project rule analysis results of the target analysis link subsequently.

[0048] Step 408: Generate the project rule analysis results of the target analysis link based on the user operation data and project rules of at least one node.

[0049] The project rules of the node are the conditions for guiding or restricting the operations in the links of the target project, and are set based on the project objectives and execution logics of this link to ensure that this link of the target project can operate in the expected manner, thereby achieving the project objectives.

[0050] The project rule analysis results of the target analysis link are the results obtained by quantitatively analyzing the project rules of the target project using the target analysis link. The project rule analysis results can be in formats such as visual charts, text reports, interactive dashboards, etc.

[0051] Based on the user operation data and project rules of at least one node, to generate the project rule analysis results of the target analysis link, one optional method is: according to at least one node, respectively integrate the user operation data and project rules of at least one node to obtain the project rule analysis results of the target analysis link. Another optional method is: count the user operation results of at least one node to obtain the operation statistical data of at least one node, and generate the project rule analysis results of the target analysis link based on the operation statistical data and project rules of at least one node. This is not limited here.

[0052] Exemplarily, the user operation results of three nodes are statistically analyzed to obtain the number and proportion of successful users and the number and proportion of failed users for the three nodes. Based on the number and proportion of successful users, the number and proportion of failed users for the three nodes, and the risk rules of the three nodes, a project rule analysis result in a visual chart format for the target analysis link of the multi-branch type is generated. The operation personnel can interact with this project rule analysis result. For each node, the operation personnel can click to view the reasons for interception, and can deeply view the models, judgment rules, hit conditions, and other risk rules associated with the rejection code from the dimension of the rejection code, clearly see the impact of the risk rules on the operation process of the resource project, and clearly see the specific risk rules for non-admission, failure to increase the resource quota, failure to use the resource quota, etc., enabling the operation personnel to take the next optimization actions. Figure 5 The figure shows a schematic diagram of the project rule analysis result of a project rule analysis method provided by an embodiment of this specification, as Figure 5 shown: Top settings: Analysis date, analysis user group, analysis link: The analysis date is used to determine the time range of the data, the analysis user group is used to specify the target user group for analysis, and the analysis link is used to define the specific analysis path.

[0053] Target analysis link: The target analysis link refers to the specific path that needs to be quantitatively analyzed. Here, the number of users is specified as the key indicator.

[0054] Real-time project rules: Real-time project rules are obtained from the target analysis link, and these rules are used to guide the operation process of the project.

[0055] Project entry page: The project entry page is a web window used to display the entry interface of the project.

[0056] Project entry invisible: Some users cannot see the project entry, and the number of these users is listed separately.

[0057] Real-time grading rules: The real-time grading rules are also a web window used to display the real-time grading rules.

[0058] Pre-credit: Includes the number of users and the credit limit, used to evaluate the credit status of this part of users.

[0059] Marketing resource quota credit: Also includes the number of users and the credit limit, used to evaluate the credit status of this part of users.

[0060] Request success page: Displays the page of successful requests, and the number of users with successful requests is also listed separately.

[0061] Request failure page: Displays the page of failed requests, and the number of users with failed requests is listed separately.

[0062] In the embodiments of this specification, a target analysis link that needs to perform quantitative analysis on a target project is obtained, and a target rule process corresponding to the target analysis link is determined from a preset rule process. Since the rule process divides multiple nodes based on the operation process of the target project itself, and each node corresponds to a specific project rule of the target project, therefore, based on at least one node of the target rule process, the user operation data can be divided to obtain the user operation data of each node that accurately reflects the influence of the node rules. Based on this, based on the user operation data of at least one node and the corresponding project rules, a detailed project rule analysis result is generated. By deeply understanding the action mechanism of the project rules, it clearly shows which links are affected by which project rules, thereby providing data support for the optimization of subsequent operation processes or project rules, and effectively improving the execution efficiency and effect of the project.

[0063] In an alternative embodiment of this specification, any node includes at least one of a user group sub-node, a project rule sub-node, a page sub-node, and a request sub-node.

[0064] The user group sub-node is a sub-node in the node that represents the user group that needs to be quantitatively analyzed. For example, the node corresponding to the analyzed customer group.

[0065] The project rule sub-node is a sub-node in the node that represents the conditions and logics that restrict the operations of specific links. For example, the nodes corresponding to each risk rule in the risk rule set. For the project rule sub-node, the distribution of rejection code reasons can be viewed, the involved models, judgment rules, and hit conditions can be viewed, and more detailed reasons can be seen for targeted optimization.

[0066] The page sub-node is a sub-node in the node that represents the interactive page. For example, the set of each product page.

[0067] The request sub-node is a sub-node in the node that represents the processing requests triggered by the user on the page. For example, various operation buttons on the page.

[0068] In an alternative embodiment of this specification, before step 404, the following specific steps are further included: Obtain the operation process of the target project and the project rules corresponding to the operation process; Set the analysis link of the target project based on the project entry type of the target project; Based on the operation process of the target project, divide the analysis link to obtain at least one node, and determine the project rules corresponding to at least one node to obtain the rule process corresponding to the analysis link.

[0069] The project entry type of the target project is the trigger type for interacting with the target project. The project entry is the first step in the operation process for users to enter the target project, and it is designed according to different project requirements, user behaviors, and project characteristics. The project entry type determines how users first come into contact with the project and the way to participate in the subsequent processes of the project. For example, in a resource project, according to the user access types, there are 8 types in total, including non-approved credit access, pre-approved credit access, marketing quota access, potential business self-certification, and solidified credit access, etc.

[0070] Based on the operation process of the target project, divide the analysis link to obtain at least one node, and determine the project rules corresponding to at least one node. An optional way is: based on at least one link in the operation process of the target project, make a corresponding division of the analysis link to obtain at least one node, and determine the project rules corresponding to at least one node.

[0071] Exemplarily, obtain the operation process of the resource project and the risk rules corresponding to the operation process. Based on the 8 types of project entry types such as non-approved credit access, pre-approved credit access, marketing quota access, potential business self-certification, and solidified credit access in the resource project, set 3 analysis links for the resource project. Based on multiple links in the operation process of the resource project, make a corresponding division of the 3 analysis links to obtain 3 analysis links including multiple nodes, and determine the risk rules corresponding to each node to obtain the rule processes corresponding to the 3 analysis links.

[0072] In the embodiments of this specification, based on the project entry type of the target project in advance, set the analysis link of the target project, and based on the operation process of the target project and the project rules corresponding to the operation process, realize the process division of the analysis link of the target project, accurately understand the action mechanism of the project rules, and provide data support and framework foundation for subsequent quantitative analysis.

[0073] In an optional embodiment of this specification, the analysis link includes a non-branching type link; Based on the operation process of the target project, divide the analysis link to obtain at least one node, including the following specific steps: Based on the project entry and the entry page of the target project, divide the non-branching type link to obtain non-branching nodes.

[0074] The non-branching type link is a quantitative analysis path with no branches from the project entry to the completion in the project operation process, which is single-linear. This kind of link is usually used to describe a simple and direct operation process, where users or systems must execute each link in sequence until the process ends.

[0075] The project entry of the target project is the part of the trigger entry for the user to interact with the target project. The project entry is the first step in the operation process for the user to enter the target project, and it is designed according to different project requirements, user behaviors, and project characteristics.

[0076] The entry page of the target project is the part of the trigger page for the user to interact with the target project. The entry page is the first page displayed when the user enters the target project. It not only provides the main entry to the target project but also can contain basic information about the target project, usage guide information, etc.

[0077] A non-branching node is a process node in the non-branching link used to represent the rules and processes of the operation process.

[0078] Exemplarily, based on the project entry (admission type) and entry page (visiting page) of the resource project, non-branching type links such as non-credit admission (both credit and application are not admitted), marketing quota admission, pre-credit admission, etc. are divided to obtain non-branching nodes.

[0079] In the embodiments of this specification, based on the project entry and entry page of the target project, the non-branching type link is divided to obtain non-branching nodes, realizing the process division of the non-branching analysis link of the target project, accurately understanding the action mechanism of the project rules, and providing data support and framework basis for the subsequent quantitative analysis of the non-branching link.

[0080] In an optional embodiment of this specification, the analysis link includes a single-branching type link; Based on the operation process of the target project, the analysis link is divided to obtain at least one node, including the following specific steps: Based on the project entry, entry page, submission request, request success page, and request failure page of the target project, the single-branching type link is divided to obtain at least one single-branching node.

[0081] The single-branching type link is a quantitative analysis path with a single branch from the project entry to the completion in the project operation process. It is single and non-linear. This kind of link is usually used to describe a relatively complex operation process, and the user or system can selectively execute some links until the process ends.

[0082] The submission request of the target project is the part of a specific action or instruction triggered by the user on the page. According to different scenarios and requirements, the submission request may involve various content information such as filling out forms, uploading files, selecting options, etc.

[0083] The request success page of the target project is a part of the confirmation page shown to the user after the submitted request has been processed. The request success page is used to confirm that the operation of submitting the request has been successfully completed and may also contain useful information such as the order number, estimated completion time, and next step operation guide.

[0084] The request failure page of the target project is a part of the confirmation page shown to the user when the submitted request has not been processed. The request failure page is used to confirm that the operation of submitting the request has not been successfully completed, may also contain the reason for the failure, and may provide solutions or suggestions.

[0085] A single-branch node is a process node in the rule process that represents the links of the operation process in a single-branch link.

[0086] Exemplarily, based on the project entry (admission type), entry page (visited page), submitted request, request success page, and request failure page of the resource project, single-branch type links such as quota admission, user pre-admission, weak business self-certification, and potential business self-certification are divided to obtain single-branch nodes.

[0087] In the embodiments of this specification, based on the project entry, entry page, submitted request, request success page, and request failure page of the target project, single-branch type links are divided to obtain at least one single-branch node, realizing the process division of the single-branch analysis link of the target project, accurately understanding the action mechanism of the project rules, and providing data support and framework foundation for the subsequent quantitative analysis of the single-branch link.

[0088] In an optional embodiment of this specification, the analysis link includes a multi-branch type link; Based on the operation process of the target project, the analysis link is divided to obtain at least one node, including the following specific steps: Based on the project entry, entry page branches, submitted request, request success page, and request failure page of the target project, the multi-branch type link is divided to obtain at least one multi-branch node.

[0089] The multi-branch type link is a quantitative analysis path in the project operation process where the path from the project entry to the completion has multiple branches and is multi-directional and non-linear. Such a link is usually used to describe a complex operation process, and users or systems can selectively execute some links until the process ends.

[0090] The entry page branches of the target project are part of the multiple trigger pages for the user to interact with the target project. Any one of the entry page branches is the first page shown when the user enters the target project, which not only provides different entrances to the target project but may also contain basic information about the target project, usage guide, etc.

[0091] A multi-branch node is a process node of a rule process for characterizing a link in a multi-branch link that represents a link in an operation process.

[0092] Exemplarily, based on the project entry (admission type) of a resource project, the entry page branches (visiting page A and visiting page B), the submitted request, the request success page, and the request failure page of a credit solidification admission branch type link are divided to obtain multi-branch nodes.

[0093] In the embodiments of this specification, based on the project entry, the entry page branches, the submitted request, the request success page, and the request failure page of a target project, a multi-branch type link is divided to obtain at least one multi-branch node, realizing the process division of the multi-branch analysis link of the target project, accurately understanding the action mechanism of the project rules, and providing data support and a framework basis for the subsequent quantitative analysis of the multi-branch link.

[0094] For the above-mentioned multiple embodiments, Figure 6 shows a schematic diagram of an analysis link of a project rule analysis method provided by an embodiment of this specification, as Figure 6 shown: Branchless type: Project entry type: Represents the trigger type for a user to enter a project. Entry page: The page where the user first contacts the project.

[0095] Single-branch type: Project entry type: Represents the trigger type for a user to enter a project. Entry page: The page where the user first contacts the project. Submitted request: The specific action or instruction triggered by the user on the page. Request success page: Represents the confirmation page after the request is successful. Request failure page: Represents the confirmation page after the request fails.

[0096] Multi-branch type: Project entry type: Represents the trigger type for a user to enter a project. Entry page A: One of the first pages where the user first contacts the project. Entry page B: Another of the first pages where the user first contacts the project. Submitted request: The specific action or instruction triggered by the user on the page. Request success page: Represents the confirmation page after the request is successful. Request failure page: Represents the confirmation page after the request fails.

[0097] In an optional embodiment of this specification, the user operation data includes multiple types of user operation results; step 408 includes the following specific steps: According to multiple types, count the user operation results of at least one node to obtain operation statistical data of at least one node; Based on the operation statistical data of at least one node and the project rules, generate a project rule analysis result of the target analysis link.

[0098] The user operation results of multiple types are the operation results of multiple types that directly or indirectly interact with the user during the execution of the target project. Each type represents a specific type of user behavior feedback, used to distinguish the success or failure and status changes of different operation results, and serve as the basis for subsequent project optimization. For example, the user operation data of a resource project includes 2 types of user operation results: application success and application failure. Another example, the user operation data of a resource project includes 3 types of user operation results: available resource quota, unavailable resource quota, and frozen resource quota.

[0099] The user operation results of a node are the operation results of multiple types that directly or indirectly interact with the user during the execution of the corresponding link of the node in the target project.

[0100] According to multiple types, count the user operation results of at least one node to obtain the operation statistics data of at least one node. A feasible way is: according to multiple types, count the type extreme values of the user operation results of at least one node to obtain the operation statistics data of at least one node. Another optional way is: according to multiple types, count the type mean values of the user operation results of at least one node to obtain the operation statistics data of at least one node. Another optional way is: according to multiple types, count the type quantity distribution of the user operation results of at least one node to obtain the operation statistics data of at least one node. Another optional way is: according to multiple types, count the type frequency of the user operation results of at least one node to obtain the operation statistics data of at least one node, which is not limited here.

[0101] Exemplarily, according to 3 types (1. Available resource quota: can be directly used; 2. Unavailable resource quota: see the reason for the unavailable resource quota, cannot be used, but can supplement relevant materials; 3. Frozen resource quota: can apply for thawing. After the user clicks the thaw button, due to risk strategies, some users will thaw successfully and some users will thaw fail), count the type quantity distribution of the user operation results of 3 nodes to obtain operation statistics data such as the number of users, credit limit, and proportion of 3 nodes. Integrate the operation statistics data of 3 nodes and risk rules to generate the project rule analysis result in a visual chart format for the target analysis link of the multi-branch link, Figure 5 For example, among them, one of the two request success pages is the available resource quota page, and the other is the frozen resource quota page. The request failure page is the unavailable resource quota page. The operation can click to view the reason and can view the risk rules such as the model, judgment rules, and hit conditions associated with the rejection code in depth from the dimension of the rejection code, clearly see the impact of the risk rules on the operation process of the resource project, and see clearly the specific risk rules for available resource quota, unavailable resource quota, frozen resource quota, etc., which can enable the operation personnel to have the next optimization action.

[0102] In the embodiments of this specification, according to multiple types, the user operation results of at least one node are statistically analyzed to obtain the operation statistical data of at least one node. Based on the operation statistical data of at least one node and the project rules, the project rule analysis results of the target analysis link are generated, which enables a deeper understanding of the action mechanism of the project rules. From a statistical perspective, it clearly shows which links are susceptible to which project rules, thereby providing more accurate data support for optimizing subsequent operation processes or project rules, effectively improving the execution efficiency and effect of the project.

[0103] In an alternative embodiment of this specification, the project rule analysis results are in the form of a chart; Generating the project rule analysis results of the target analysis link based on the operation statistical data of at least one node and the project rules includes the following specific steps: Integrate the operation statistical data of at least one node and the project rules to obtain the node data of at least one node; According to the connection relationship between at least one node, render the node data of at least one node to obtain the project rule analysis results of the target analysis link in the form of a chart.

[0104] The node data of a node is composed of the user operation data collected on a specific node and the corresponding project rules in the operation process of the target project. The node data is completely rendered as a unit in the subsequent chart format rendering, enabling the user to view the corresponding node data node by node.

[0105] The project rule analysis results in the form of a chart display the operation statistical data of each node and its corresponding project rules in the operation process of the target project through a visual chart (such as a bar chart, line chart, pie chart, interactive dashboard, etc.). The results in this format are convenient for intuitively understanding the user behavior pattern, identifying key problem points, and providing data support for optimizing project rules. For example, through an interactive dashboard, it can be clearly seen which links have a low success rate and which risk rules lead to user failures, etc. This helps to discover potential problems and take corresponding improvement measures.

[0106] The connection relationship between at least one node is the sequential connection relationship between each node in the operation process of the target project. This connection relationship describes the data flow or the transfer path of the operation process from one node to another.

[0107] Render the node data of at least one node according to the connection relationship between at least one node, and obtain the project rule analysis result in the form of a chart for the target analysis link. An optional method is: render the node data of at least one node with corresponding styles according to the connection relationship between at least one node, and obtain the project rule analysis result in the form of a chart for the target analysis link.

[0108] Exemplarily, integrate the operation statistics data and project rules of 3 nodes to obtain the node data of 3 nodes. According to the connection relationship between the 3 nodes, render the node data of the 3 nodes with corresponding styles (root node: user group sub-node; blue folder-shaped node: project rule sub-node; picture node: page sub-node; green rectangle node: request sub-node for various operation buttons on the page), and obtain the project rule analysis result in the form of a chart for the target analysis link.

[0109] In the embodiments of this specification, by integrating the rule process into the project operation process in the form of a visual chart, users can intuitively understand the specific impact of project rules on the nodes corresponding to each link. Use a comprehensive visual chart to display the entire project rule analysis result, and intuitively view the user operation data and project rules of each node on each node, which not only clearly presents complex project rules and operation processes, but also greatly improves the efficiency and accuracy of quantitative analysis. Compared with the traditional report analysis method, it is closer to the user's usage habits and thinking mode, making it more direct and effective to identify key problem points and optimization directions. It not only enhances the transparency and controllability of the project, but also provides a more intuitive data value for optimizing the operation process or project rules, thereby effectively improving the execution efficiency and effect of the project.

[0110] For the above embodiments, Figure 7 Fig. 1 shows one of the schematic diagrams of the project rule analysis result in the form of a chart of a project rule analysis method provided by an embodiment of this specification; This chart visually shows the operation statistics data of each node and its corresponding project rules in the project operation process. Specifically, the chart sequentially shows the user group node, real-time project rule node, project rule sub-node, page sub-node, and request sub-node from top to bottom. Each node contains corresponding user data and project rule information, and is connected by arrows, clearly indicating the sequential connection relationship between each node. For example, the user group node shows the operation data of a specific user group, while the real-time project rule node shows the project rules related to these operations. This chart format result is convenient for intuitively understanding user behavior patterns, identifying key problem points, and providing data support for optimizing project rules.

[0111] Figure 8Schematic diagram II of the project rule analysis result of a project rule analysis method provided by an embodiment of this specification, shown in a chart format: Based on Figure 7 After the cursor clicks on the "risk rule" area, a detailed window pops up on the right, showing: View reason: Provide further explanations and background information. Number of people rejected and not allowed to enter / proportion: Specifically list the number of people rejected and their proportion in the total number of people. Number not allowed to enter: Rejection code: Specific codes identify the reasons for rejection. Quantity: Quantity corresponding to the rejection code. Proportion: Proportion of the quantity corresponding to the rejection code in the total number of rejections.

[0112] The results in this chart format facilitate intuitive understanding of user behavior patterns, identification of key problem points, and provide data support for optimizing project rules.

[0113] Corresponding to the above method embodiment, this specification also provides an embodiment of a project rule analysis device. Figure 9 Schematic diagram of the structure of a project rule analysis device provided by an embodiment of this specification is shown. As Figure 9 shown, the device includes: An acquisition module 902, configured to acquire the target analysis link of the target project; A determination module 904, configured to determine, from the preset rule processes, the target rule process corresponding to the target analysis link, where any rule process includes at least one node divided based on the operation process of the target project, and any node has a corresponding project rule; A division module 906, configured to divide the user operation data of the target project based on at least one node in the target rule process to obtain the user operation data of at least one node; A generation module 908, configured to generate the project rule analysis result of the target analysis link based on the user operation data of at least one node and the project rules.

[0114] Optionally, the device further includes a preset module, configured to acquire the operation process of the target project and the project rules corresponding to the operation process; set the analysis link of the target project based on the project entry type of the target project; divide the analysis link based on the operation process of the target project to obtain at least one node, and determine the project rules corresponding to at least one node to obtain the rule process corresponding to the analysis link.

[0115] Optionally, the analysis link includes a non-branching type link; the preset module is further configured to: Divide the non-branching type link based on the project entry and entry page of the target project to obtain non-branching nodes.

[0116] Optionally, the analysis link includes a single-branch type link; the preset module is further configured to: Based on the project entry, entry page, submission request, request success page, and request failure page of the target project, divide the single-branch type link to obtain at least one single-branch node.

[0117] Optionally, the analysis link includes a multi-branch type link; the preset module is further configured to: Based on the project entry, entry page branch, submission request, request success page, and request failure page of the target project, divide the multi-branch type link to obtain at least one multi-branch node.

[0118] Optionally, the user operation data includes multiple types of user operation results; the generation module 908 is further configured to: According to multiple types, count the user operation results of at least one node to obtain operation statistical data of at least one node; Based on the operation statistical data of at least one node and the project rules, generate a project rule analysis result of the target analysis link.

[0119] The project rule analysis result is in the form of a chart; the generation module 908 is further configured to: Integrate the operation statistical data of at least one node and the project rules to obtain node data of at least one node; According to the connection relationship between at least one node, render the node data of at least one node to obtain a project rule analysis result in the form of a chart of the target analysis link.

[0120] Optionally, any node includes at least one of a user group sub-node, a project rule sub-node, a page sub-node, and a request sub-node.

[0121] In the embodiments of this specification, the acquisition module is configured to acquire a target analysis link that needs to be quantitatively analyzed for a target project, and the determination module is configured to determine a target rule process corresponding to the target analysis link from a preset rule process. Since the rule process divides at least one node based on the operation process of the target project itself, and each node corresponds to a specific project rule of the target project, the division module is configured to divide the user operation data based on at least one node of the target rule process, and can obtain the user operation data of each node that accurately reflects the influence of the node rules. Based on this, the generation module is configured to generate a detailed project rule analysis result based on the user operation data of at least one node and the corresponding project rules. Deeply understanding the action mechanism of the project rules clearly shows which links are affected by which project rules, thereby providing data support for the optimization of subsequent operation processes or project rules, and effectively improving the execution efficiency and effect of the project.

[0122] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other, and the key point of each embodiment is to illustrate the differences from other embodiments. In particular, for the project rule analysis device, since it is basically similar to the embodiment of the project rule analysis method, the description is relatively simple, and for the relevant parts, reference can be made to the partial description of the embodiment of the project rule analysis method.

[0123] Figure 10 The block diagram of a computing device provided by an embodiment of this specification is shown. The components of the computing device 1000 include, but are not limited to, a memory 1010 and a processor 1020. The processor 1020 is connected to the memory 1010 through a bus 1030, and a database 1050 is used to store data.

[0124] The computing device 1000 further includes an access device 1040, which enables the computing device 1000 to communicate via one or more networks 1060. Examples of these networks include the Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or a combination of communication networks such as the Internet. The access device 1040 may include one or more of any type of wired or wireless network interfaces (e.g., a Network Interface Controller (NIC)), such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface.

[0125] In an embodiment of this specification, the above components of the computing device 1000 and Figure 10 other components not shown in the figure may also be connected to each other, for example, through a bus. It should be understood that Figure 10The block diagram of the computing device shown is for illustrative purposes only and is not a limitation on the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0126] The computing device 1000 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 1000 can also be a mobile or stationary server.

[0127] Among them, the processor 1020 is used to execute the following computer program / instructions, and when the computer program / instructions are executed by the processor, the steps of the above-mentioned item rule analysis method are implemented.

[0128] The above is a schematic solution of a computing device in this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the above-mentioned item rule analysis method belong to the same concept. For the details not described in detail in the technical solution of the computing device, reference can be made to the description of the technical solution of the above-mentioned item rule analysis method.

[0129] An embodiment of this specification also provides a computer-readable storage medium that stores computer program / instructions, and when the computer program / instructions are executed by a processor, the steps of the above-mentioned item rule analysis method are implemented.

[0130] The above is a schematic solution of a computer-readable storage medium in this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the above-mentioned item rule analysis method belong to the same concept. For the details not described in detail in the technical solution of the storage medium, reference can be made to the description of the technical solution of the above-mentioned item rule analysis method.

[0131] An embodiment of this specification also provides a computer program product, including computer program / instructions, and when the computer program / instructions are executed by a processor, the steps of the above-mentioned item rule analysis method are implemented.

[0132] The above is a schematic solution of a computer program product in this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the above-mentioned item rule analysis method belong to the same concept. For the details not described in detail in the technical solution of the computer program product, reference can be made to the description of the technical solution of the above-mentioned item rule analysis method.

[0133] The specific embodiments of this specification are described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require the particular order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0134] The computer instructions include computer program code, which may be in source code form, object code form, executable file, or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, removable hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content included in the computer-readable medium can be appropriately increased or decreased according to the requirements of patent practice. For example, in some regions, according to patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0135] It should be noted that the specific embodiments of this specification are described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require the particular order or sequential order shown to achieve the desired result. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential for the embodiments of this specification.

[0136] In the above embodiments, the descriptions of each embodiment have their own focuses. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0137] The preferred embodiments of the present specification disclosed above are only used to help explain the present specification. The alternative embodiments do not describe all the details in detail, nor do they limit the invention to the specific embodiments described. Obviously, many modifications and variations can be made according to the content of the embodiments of the present specification. These embodiments are selected and specifically described in this specification in order to better explain the principles and practical applications of the embodiments of the present specification, so that those skilled in the art can well understand and utilize this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. A project rule analysis method, comprising: Get the target analysis link of the target project; Determine a target rule process corresponding to the target analysis link from the preset rule processes, wherein any rule process includes at least one node divided based on the operation process of the target project, and any node has a corresponding project rule; Based on at least one node in the target rule process, dividing the user operation data of the target item to obtain the user operation data of the at least one node; Based on the user operation data and project rules of the at least one node, a project rule analysis result of the target analysis link is generated.

2. The method according to claim 1, before determining the target rule process corresponding to the target analysis link from the preset rule process, further comprises: Obtaining the operation process of the target project and the project rules corresponding to the operation process; Based on the project entry type of the target project, setting an analysis link of the target project; Based on the operation flow of the target project, the analysis link is divided to obtain at least one node, and the project rule corresponding to the at least one node is determined to obtain the rule flow corresponding to the analysis link.

3. The method according to claim 2, wherein the analysis link comprises a branchless type link; The step of dividing the analysis link based on the operation flow of the target project to obtain at least one node includes: Based on the project entry and entry page of the target project, the non-branch type link is divided to obtain non-branch nodes.

4. The method according to claim 2, wherein the analysis link comprises a single branch type link; The step of dividing the analysis link based on the operation flow of the target project to obtain at least one node includes: Based on the project entry, entry page, submission request, request success page and request failure page of the target project, the single branch type link is divided to obtain at least one single branch node.

5. The method according to claim 2, wherein the analysis link comprises a multi-branch type link; The step of dividing the analysis link based on the operation flow of the target project to obtain at least one node includes: Based on the project entry, entry page branch, submission request, request success page and request failure page of the target project, the multi-branch type link is divided to obtain at least one multi-branch node.

6. The method according to any one of claims 1 to 5, wherein the user operation data comprises multiple types of user operation results; The generating the project rule analysis result of the target analysis link based on the user operation data and the project rule of the at least one node includes: According to the multiple types, counting the user operation results of the at least one node to obtain operation statistics of the at least one node; Based on the operation statistics data and the project rules of the at least one node, a project rule analysis result of the target analysis link is generated.

7. The method according to claim 6, wherein the project rule analysis result is in a chart format; The generating the project rule analysis result of the target analysis link based on the operation statistics data and the project rule of the at least one node comprises: Integrate the operation statistics data and the project rules of the at least one node to obtain the node data of the at least one node; According to the connection relationship between the at least one node, the node data of the at least one node is rendered to obtain the project rule analysis result of the target analysis link in a graph format.

8. According to the method of claim 1, any node includes at least one of a user group sub-node, a project rule sub-node, a page sub-node, and a request sub-node.

9. A project rule analysis device, comprising: An acquisition module configured to acquire a target analysis link of a target project; A determination module is configured to determine a target rule flow corresponding to a target analysis link from preset rule flows, wherein any rule flow includes at least one node divided based on the operation flow of the target project, and any node has a corresponding project rule; a division module, configured to divide the user operation data of the target item based on at least one node in the target rule flow, and obtain the user operation data of the at least one node; A generation module is configured to generate a project rule analysis result of the target analysis link based on the user operation data and project rules of the at least one node.

10. The device according to claim 9 further includes a preset module, which is configured to obtain the operation process of the target project and the project rules corresponding to the operation process; set the analysis link of the target project based on the project entry type of the target project; divide the analysis link based on the operation process of the target project to obtain at least one node, and determine the project rules corresponding to the at least one node to obtain the rule process corresponding to the analysis link.

11. The device according to claim 10, wherein the analysis link comprises a branchless type link; and the preset module is further configured to: Based on the project entry and entry page of the target project, the non-branch type link is divided to obtain non-branch nodes.

12. The device according to claim 10, wherein the analysis link comprises a single-branch type link; and the preset module is further configured to: Based on the project entry, entry page, submission request, request success page and request failure page of the target project, the single branch type link is divided to obtain at least one single branch node.

13. The apparatus according to claim 10, wherein the analysis link comprises a multi-branch type link; and the preset module is further configured to: Based on the project entry, entry page branch, submission request, request success page and request failure page of the target project, the multi-branch type link is divided to obtain at least one multi-branch node.

14. The apparatus according to any one of claims 9 to 13, wherein the user operation data comprises multiple types of user operation results; and the generating module is further configured to: According to the multiple types, counting the user operation results of the at least one node to obtain operation statistics of the at least one node; Based on the operation statistics data and the project rules of the at least one node, a project rule analysis result of the target analysis link is generated.

15. The device according to claim 14, wherein the project rule analysis result is in a chart format; and the generating module is further configured to: Integrate the operation statistics data and the project rules of the at least one node to obtain the node data of the at least one node; According to the connection relationship between the at least one node, the node data of the at least one node is rendered to obtain the project rule analysis result of the target analysis link in a graph format.

16. The device according to claim 9, any node includes at least one of a user group sub-node, a project rule sub-node, a page sub-node, and a request sub-node.

17. A computing device comprising: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer program / instructions are executed by the processor, the steps of the method according to any one of claims 1 to 8 are implemented.

18. A computer-readable storage medium storing a computer program / instruction, wherein the computer program / instruction, when executed by a processor, implements the steps of the method according to any one of claims 1 to 8.

19. A computer program product, comprising a computer program / instruction, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 8.

Images