Page source determination method, system and equipment and storage medium
By searching for query parameters in the Uniform Resource Locator, Referer field, and Hypertext Transfer Protocol tracking information text during multi-level H5 page jumps, the problem of inaccurate page source determination caused by URL character length limitations is solved, achieving higher reliability and success rate.
Patent Information
- Application Number
- CN202510783937.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-12
- Publication Date
- 2025-09-16
AI Technical Summary
In the prior art, during the multi-level H5 page jump process, due to the URL character length limitation, query parameters are easily lost or incomplete, which reduces the reliability of determining the page source.
By searching for query parameters in the uniform resource locator of the target page, the Referer field of the page jump request, and the Hypertext Transfer Protocol tracking information text, it ensures that when query parameters do not exist in the URL, the page source identifier is obtained from other sources, thereby increasing the probability of obtaining query parameters.
The reliability of page source determination is enhanced, the success rate of obtaining query parameters during multi-level page jumps is improved, and the accurate positioning of page sources is ensured.
Smart Images

Figure CN120653853A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a method, system, device and storage medium for determining a page source. Background Art
[0002] Existing Internet platforms generally adopt multi-level H5 page jump technology, which determines the page source (order source, traffic source, user behavior tracking, etc.) in multi-level page jump scenarios by parsing the source identification parameters (such as query parameters, Query) in the Uniform Resource Locator (URL).
[0003] However, since the character length of the URL is fixed, for H5 pages with multi-level configuration, it is very easy for the URL character length to exceed the fixed value during the jump process, resulting in the risk of query parameters being lost or incomplete, reducing the reliability of determining the source of the page. Summary of the Invention
[0004] In view of the above problems, this application provides a method, system, device and storage medium for determining the source of a page, so as to achieve the purpose of improving the reliability of determining the source of a page. The specific solution is as follows:
[0005] In a first aspect, the present application provides a method for determining a page source, comprising:
[0006] searching for a query parameter from the uniform resource locator of the target page, and if the query parameter exists in the uniform resource locator, determining the page identifier corresponding to the query parameter as the page source identifier of the target page;
[0007] If the query parameter does not exist in the uniform resource locator, searching for the query parameter in the Referer field of the page jump request to the target page;
[0008] When the query parameter exists in the Referer field, determining the page identifier corresponding to the query parameter as the page source identifier of the target page;
[0009] When the query parameter does not exist in the Referer field, the query parameter is searched for in the hypertext transfer protocol tracking information text associated with the target page, and the page identifier corresponding to the searched query parameter is determined as the page source identifier of the target page.
[0010] In one possible implementation, the method further includes:
[0011] When the query parameter does not exist in the hypertext transfer protocol tracking information text, the query parameter is searched from the page access log based on the uniform resource locator of the target page, and the page identifier corresponding to the query parameter is determined as the page source identifier of the target page.
[0012] In one possible implementation, the method further includes:
[0013] When the query parameter and the page identifier corresponding to the query parameter are obtained, the hypertext transfer protocol tracking information text is newly created, and the query parameter and the page identifier are correspondingly stored in the newly created hypertext transfer protocol tracking information text.
[0014] In one possible implementation, the method further includes:
[0015] In the case of creating a new multi-level jump page, creating the hypertext transfer protocol tracking information text;
[0016] The page identifier and query parameter corresponding to each newly created page in the newly created multi-level jump page are correspondingly stored in the newly created hypertext transfer protocol tracking information text.
[0017] In a possible implementation, searching for the query parameter from the hypertext transfer protocol tracking information text associated with the target page includes:
[0018] From a plurality of candidate hypertext transfer protocol tracking information texts, determine the candidate hypertext transfer protocol tracking information text whose text is identified as the uniform resource locator of the target page as the hypertext transfer protocol tracking information text associated with the target page;
[0019] The query parameter field content in the hypertext transfer protocol tracking information text is extracted as the query parameter.
[0020] In a possible implementation, searching for the query parameter from the hypertext transfer protocol tracking information text associated with the target page includes:
[0021] parsing a request header of the page jump request to obtain a text identifier of at least one hypertext transfer protocol tracking information text in the page jump request, and determining a plurality of candidate hypertext transfer protocol tracking information texts based on the text identifier;
[0022] extracting the business data identifier of the target page, and determining the candidate hypertext transfer protocol tracking information text storing the business data identifier as the hypertext transfer protocol tracking information text associated with the target page;
[0023] The query parameter field content in the hypertext transfer protocol tracking information text is extracted as the query parameter.
[0024] A second aspect of the present application provides a system for determining a page source, the system comprising:
[0025] a first search unit configured to search for a query parameter from a uniform resource locator of a target page, and if the query parameter exists in the uniform resource locator, determine a page identifier corresponding to the query parameter as a page source identifier of the target page;
[0026] a second searching unit, configured to search for the query parameter in a Referer field of a page jump request to the target page when the query parameter does not exist in the uniform resource locator;
[0027] a first determining unit, configured to, when the query parameter exists in the Referer field, determine the page identifier corresponding to the query parameter as the page source identifier of the target page;
[0028] The third search unit is used to search for the query parameter from the hypertext transfer protocol tracking information text associated with the target page when the query parameter does not exist in the Referer field, and determine the page identifier corresponding to the found query parameter as the page source identifier of the target page.
[0029] In a possible implementation, the system for determining the page source further includes:
[0030] The fourth search unit is used to search for the query parameter from the page access log based on the uniform resource locator of the target page when the query parameter does not exist in the hypertext transfer protocol tracking information text, and determine the page identifier corresponding to the query parameter as the page source identifier of the target page.
[0031] In a possible implementation, the system for determining the page source further includes:
[0032] The first creating unit is used to create the hypertext transfer protocol tracking information text when the query parameter and the page identifier corresponding to the query parameter are obtained, and store the query parameter and the page identifier in the newly created hypertext transfer protocol tracking information text accordingly.
[0033] In a possible implementation, the system for determining the page source further includes:
[0034] The second new creation unit is used to create the hypertext transfer protocol tracking information text when creating a new multi-level jump page; and store the page identifier and query parameters corresponding to each new page in the new multi-level jump page into the newly created hypertext transfer protocol tracking information text.
[0035] In a possible implementation, the third search unit is configured to:
[0036] From a plurality of candidate hypertext transfer protocol tracking information texts, determine the candidate hypertext transfer protocol tracking information text whose text is identified as the uniform resource locator of the target page as the hypertext transfer protocol tracking information text associated with the target page;
[0037] The query parameter field content in the hypertext transfer protocol tracking information text is extracted as the query parameter.
[0038] In a possible implementation, the third search unit is configured to:
[0039] parsing a request header of the page jump request to obtain a text identifier of at least one hypertext transfer protocol tracking information text in the page jump request, and determining a plurality of candidate hypertext transfer protocol tracking information texts based on the text identifier;
[0040] extracting the business data identifier of the target page, and determining the candidate hypertext transfer protocol tracking information text storing the business data identifier as the hypertext transfer protocol tracking information text associated with the target page;
[0041] The query parameter field content in the hypertext transfer protocol tracking information text is extracted as the query parameter.
[0042] A third aspect of the present application provides a computer program product comprising computer-readable instructions, which, when executed on an electronic device, enables the electronic device to implement the method for determining the page source of the first aspect or any implementation of the first aspect.
[0043] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:
[0044] The memory is used to store computer programs;
[0045] The processor is used to execute the computer program so that the electronic device can implement the method for determining the page source of the above-mentioned first aspect or any implementation manner of the first aspect.
[0046] In a fifth aspect, the present application provides a computer program product comprising computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device is enabled to implement the method for determining the page source of the first aspect or any implementation of the first aspect.
[0047] By means of the above technical solution, the present application provides a method, system, device and storage medium for determining the source of a page, which configures the Referer field of the page jump request of the target page and the hypertext transfer protocol tracking information text as the search objects of the query parameters, and configures that when the query parameters do not exist in the Referer field, the query parameters are searched from the hypertext transfer protocol tracking information text, thereby realizing multi-level query of query parameters. Compared with the existing method of determining the source of a page only based on the URL, the present application increases the probability of obtaining the query parameters and improves the reliability of determining the source of the page. Subsequently, by configuring the page identifier corresponding to the query parameter to be determined as the page source identifier of the target page, the source of the page is determined. It can be seen that the present application improves the reliability of determining the source of the page. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] The above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale.
[0049] Figure 1 A flowchart of a method for determining the source of a page provided in this application;
[0050] Figure 2 A flowchart for finding query parameters provided by this application;
[0051] Figure 3 A schematic diagram of the execution flow of a method for determining the source of a page provided in this application;
[0052] Figure 4 A block diagram of a system for determining the source of a page provided by this application;
[0053] Figure 5 This is a schematic diagram of the structure of an electronic device provided in this application. DETAILED DESCRIPTION
[0054] The following describes the embodiments of the present application in conjunction with the accompanying drawings. The terms used in the implementation methods of the present application are only used to explain the specific embodiments of the present application and are not intended to limit the present application.
[0055] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
[0056] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, and this is merely a way of distinguishing the objects of the same attributes when describing them in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.
[0057] It should be noted that, in actual application scenarios, the present application improves the reliability of determining the source of a page compared to the prior art. Specifically, since the page URL can uniquely represent the page address, the existing method for determining the source of the page is to parse and identify only the query parameters carried in the URL of the page to determine the source of the page. However, during the jump process of multi-level pages, in addition to the query parameters, the URL of each page also stores information about each page in the process of jumping to the current page, which causes the character length of the URL to gradually increase. When the character length of the URL of the page exceeds the limit, there is a risk of character loss in the URL, which in turn increases the risk of query parameters being lost (such as the query parameter content is empty) or defects (abnormal query parameter format) during the interaction process. At this time, the existing method will feedback a prompt message indicating that the determination failed, so that the backend personnel can manually query, which reduces the reliability of the automated page source determination. However, the present application configures the uniform resource locator of the target page, the Referer field of the page jump request of the target page, and the hypertext transfer protocol tracking information text as multi-level search objects, and configures that when the query parameters do not exist in the uniform resource locator, the query parameters are searched in the Referer field, and when the query parameters do not exist in the Referer field, the query parameters are searched from the hypertext transfer protocol tracking information text, thereby realizing the query of downgraded query parameters. Compared with the existing method of determining the source of a page only based on the URL, the present application increases the probability of obtaining the query parameters and improves the reliability of determining the source of the page. Subsequently, by configuring the page identifier corresponding to the query parameter to be determined as the page source identifier of the target page, the source of the page is determined. It can be seen that the present application improves the reliability of determining the source of the page.
[0058] The first aspect of the present application provides a method for determining the source of a page, such as Figure 1 As shown, the method for determining the source of the page includes:
[0059] S101: Searching for a query parameter in the uniform resource locator of a target page. If the query parameter exists in the uniform resource locator, determining a page identifier corresponding to the query parameter as a page source identifier of the target page.
[0060] It should be noted that in actual application scenarios, since the page jump request and the Hypertext Transfer Protocol tracking information text store more additional information (such as page information) compared to the uniform resource locator of the target page, and the uniform resource locator is usually stored in the cache, while the above-mentioned page jump request and the Hypertext Transfer Protocol tracking information text are stored in a set storage area, there is a problem of reduced search efficiency when searching for query parameters from the page jump request and the Hypertext Transfer Protocol tracking information text. Therefore, the present application is configured to first search for query parameters from the uniform resource locator of the target page, and if the query parameters do not exist in the uniform resource locator, perform the operation steps of searching for query parameters from the Referer field of the page jump request that jumps to the target page, thereby improving the reliability of determining the source of the page while improving the determination rate.
[0061] It should be noted that, in actual application scenarios, the above-mentioned search for query parameters from the uniform resource locator of the target page can be implemented by a "parse qs" function, which is used to extract the content of the query parameter field, ie, the query parameter, from the URL.
[0062] It should be noted that in actual application scenarios, the target page can be any page in a multi-level H5 page configuration. Taking a three-level order page as an example, including a first-level guide page, a second-level details page, and a third-level order generation page, in different application scenarios, the target page can be any level of the three-level pages. For example, in the scenario of determining the source of the order generation page, the third-level order generation page is the target page. For another example, in the scenario of statistical delivery pages, the first-level guide page is the target page. For another example, in the scenario of traffic statistics, the second-level details page is the target page.
[0063] It should be noted that, in actual application scenarios, the query parameter is the query string part in the URL and HTTP request, which is a string used to represent the source address of the page jump.
[0064] S102: When the query parameter does not exist in the uniform resource locator, the query parameter is searched for in the Referer field of the page jump request to jump to the target page.
[0065] It should be noted that in actual application scenarios, the above-mentioned page jump request can be an HTTP (Hypertext Transfer Protocol) request generated by the page that jumps to the target page in a multi-level H5 page. Since the request header of the HTTP request carries a Referer field, the Referer field is used to represent the source address (i.e., query parameter) of the request, and the source address is transmitted in each jump request of the multi-level jump page by passthrough, which makes the Referer in each page jump request involved in the jump include the query parameters of the source page that triggered the jump. Therefore, the present application improves the reliability of successfully obtaining the query parameters by configuring the query parameters to be searched in the Referer field of the page jump request that jumps to the target page.
[0066] It should be noted that, in actual application scenarios, there are many implementation methods of the above step S102, and an exemplary implementation method is provided here, including: Figure 2 Steps A1 to A5 are shown.
[0067] In step A1, the request header acquisition function is called to extract the Referer field content from the page jump request header of the target page, and step A2 is triggered.
[0068] In a possible implementation, the request header acquisition function in the above step A1 can be edited and set by the developer using a programming language, or a function selected from a function library, such as "request.headers.get('Referer')", which represents extracting the field content of the Referer field from headers (page jump request header).
[0069] In step A2, a preset parsing function is called to extract query parameters from the Referer field, triggering step A3.
[0070] In one possible implementation, the preset parsing function in the above step A2 can be a function edited and set by a developer using a programming language, or selected from a function library, such as a "urlparse" function, which is used to parse the URL from the field content, and a "parse qs" function, which is used to extract the content of the query parameter field, i.e., the query parameter, from the URL.
[0071] Step A3: Determine whether the content of the query parameter field extracted in step A2 is not empty and meets the preset format requirements. If yes, step A4 is triggered; if not, step A5 is triggered.
[0072] Step A4: Output query parameters.
[0073] Step A5: Output the judgment result that the query parameter does not exist in the Referer field.
[0074] S103: When a query parameter exists in the Referer field, the page identifier corresponding to the query parameter is determined as the page source identifier of the target page.
[0075] It should be noted that in actual application scenarios, the above-mentioned query parameters (Query Parameter, Query) refer to the parameters to be used by the function or method when performing a query operation. The above-mentioned query parameters do not directly represent the source address, but represent the detailed request information of the page jump request generated by the page corresponding to the source address, including the source address information, which uniquely represents a source page. Since the above-mentioned query parameters exist in the form of strings, it is not conducive to subsequent statistical analysis. Therefore, this application pre-establishes the correspondence between the page identifier and the query parameter through configuration, and when the query parameter is obtained, the page identifier corresponding to the query parameter is determined as the page source identifier of the target page, thereby improving the convenience of subsequent statistical analysis and intuitively determining the page source.
[0076] S104: When the Referer field does not contain a query parameter, the query parameter is searched for in the Hypertext Transfer Protocol tracking information text associated with the target page, and the page identifier corresponding to the searched query parameter is determined as the page source identifier of the target page.
[0077] It should be noted that in actual application scenarios, the above-mentioned Hypertext Transfer Protocol tracking information (Cookie) text is a data fragment used to track and record user browsing behavior. Specifically, when a user jumps to a triggered page through a multi-level configured H5 page, the browser will track and record the jump information of each page (including the query parameters of each page), and configure it to be stored in the Cookie in the form of a key-value pair. Among them, since the page jump path is relatively fixed, the key name in the above-mentioned key-value pair can be the page identifier of each page in the page jump path set by the developer (such as a string in natural language form), and the value can be the query parameter of the page that triggers the page jump path to start jumping, or the query parameters of each page in the page jump path arranged in sequence in the jump order. Due to factors such as automatic browser restrictions, malicious tampering, and server security restrictions, the Referer field is at risk of being filtered and tampered with. Therefore, this application searches for query parameters from the Hypertext Transfer Protocol tracking information text associated with the target page when there are no query parameters in the Referer field. This avoids the risk of returning a null value when no query parameters are found in the Referer field of the page jump request, resulting in failure to determine the source page. It improves the success rate of extracting query parameters, and thereby improves the reliability of determining the source of the page.
[0078] This application is configured to search for query parameters from the uniform resource locator of the target page. If the query parameters do not exist in the uniform resource locator, the query parameters are searched from the Referer field of the page jump request to the target page. If the query parameters exist in the Referer field, the page identifier corresponding to the query parameters is determined as the page source identifier of the target page. In addition, if the query parameters do not exist in the Referer field, the query parameters are searched from the hypertext transfer protocol tracking information text associated with the target page. Compared with the existing method of determining the page source based only on the URL, this application realizes multi-level and multiple page source determination, thereby improving the reliability of determining the page source. Moreover, by configuring the page identifier corresponding to the found query parameter to be determined as the page source identifier of the target page, accurate positioning of the page source is achieved. It can be seen that this application improves the reliability of determining the page source.
[0079] In one possible implementation, the method for determining the page source provided by the first aspect of the present application and any possible implementation thereof further includes:
[0080] When there is no query parameter in the HTTP tracking information text, the query parameter is searched from the page access log based on the uniform resource locator of the target page, and the page identifier corresponding to the query parameter is determined as the page source identifier of the target page.
[0081] It should be noted that in actual application scenarios, due to factors such as scope mismatch of the Hypertext Transfer Protocol tracking information text, Cross-Origin Resource Sharing (CORS) configuration errors, and browser security policies, there is still a risk of missing query parameters in the Hypertext Transfer Protocol tracking information text. However, since page access logs are usually generated directly by the operating system, web server, or application, they are independent of the user-configured security policy and are decoupled from the application service. They have independent storage and permission control, so there is no risk of data missing due to related configurations. Therefore, this application searches for query parameters from the page access log based on the Uniform Resource Locator of the target page when there are no query parameters in the Hypertext Transfer Protocol tracking information text, thereby ensuring that the query parameters are found and further improving the reliability of determining the source of the page.
[0082] It should be noted that, in actual application scenarios, there are multiple implementation methods for searching for query parameters from page access logs based on the uniform resource locator of the target page. Two examples are provided here:
[0083] Method 1: Use the URL parsing library to compare the URL with the entry strings of each log in the page access log, and extract the query parameters from the log corresponding to the entry string that passes the consistency comparison.
[0084] Method 2: Use regular expressions to filter out logs whose entry strings are consistent with the URL from page access logs, and extract query parameters from them.
[0085] In one possible implementation, the method for determining the page source provided by the first aspect of the present application and any possible implementation thereof further includes:
[0086] When the query parameter and the page identifier corresponding to the query parameter are obtained, a new hypertext transfer protocol tracking information text is created, and the query parameter and the page identifier are correspondingly stored in the newly created hypertext transfer protocol tracking information text.
[0087] It should be noted that in actual application scenarios, determining the page source of the target page is a repetitive operation (performed multiple times based on different business needs). Therefore, this application configures the system to create a new Hypertext Transfer Protocol tracking information text when obtaining the query parameters and the page identifier corresponding to the query parameters, and stores the query parameters and the page identifier in the newly created Hypertext Transfer Protocol tracking information text accordingly. This ensures that when the operation of determining the page source of the target page is repeatedly performed, the query parameters can be found through the Hypertext Transfer Protocol tracking information text, thereby improving the reliability of subsequent repeated operations to determine the page source.
[0088] It should be noted that, in actual application scenarios, there are multiple ways to execute the method for determining the page source provided by the first aspect of the present application and any possible implementation thereof. Here, an exemplary method is provided:
[0089] like Figure 3 The figure shows a flowchart of a method for determining the page source of a business order, with the target order generation page as the target page. The specific steps are as follows:
[0090] Step S301: Determine a target order generation page for generating a target business order, and trigger step S302.
[0091] Step S302: Determine whether there is a query parameter in the uniform resource locator of the target order generation page. If yes, step S306 is triggered; if not, step S303 is triggered.
[0092] Step S303: Determine whether there is a query parameter in the Referer field of the page jump request to jump to the target order generation page. If so, step S307 is triggered; if not, step S304 is triggered.
[0093] Step S304: Determine whether there is a query parameter in the hypertext transfer protocol tracking information text associated with the target order generation page. If yes, step S308 is triggered; if not, step S305 is triggered.
[0094] Step S305: Based on the uniform resource locator of the target order generation page, query parameters are searched from the page access log, and step S309 is triggered.
[0095] Step S306, the page identifier corresponding to the query parameter is determined as the page source identifier of the target order generation page; the query parameter and its corresponding page identifier are stored in the newly created hypertext transfer protocol tracking information text, and the hypertext transfer protocol tracking information text is sent to the server for storage.
[0096] Step S307, the page identifier corresponding to the query parameter is determined as the page source identifier of the target order generation page; the query parameter and its corresponding page identifier are stored in the newly created hypertext transfer protocol tracking information text, and the hypertext transfer protocol tracking information text is sent to the server for storage.
[0097] Step S308, the page identifier corresponding to the query parameter is determined as the page source identifier of the target order generation page; the query parameter and its corresponding page identifier are stored in the newly created hypertext transfer protocol tracking information text, and the hypertext transfer protocol tracking information text is sent to the server for storage.
[0098] Step S309, the page identifier corresponding to the query parameter is determined as the page source identifier of the target order generation page; the query parameter and its corresponding page identifier are stored in the newly created hypertext transfer protocol tracking information text, and the hypertext transfer protocol tracking information text is sent to the server for storage.
[0099] It should be noted that, in actual application scenarios, the query parameters in the aforementioned Referer field, Uniform Resource Locator, and Hypertext Transfer Protocol tracking information text can be query parameters representing a single page, set based on the redirect logic of a multi-level H5 page, or can be query parameters specific to each page involved in the redirect. If the query parameters include query parameters specific to each page involved in the redirect, the query parameters found by the first aspect of this application and any possible implementation thereof are the query parameters of the page that triggers the redirect, among the pages involved in the redirect.
[0100] In one possible implementation, when the query parameters include the query parameters of each page involved in the jump, the method for filtering the query parameters of the page that triggers the jump from the pages involved in the jump can be: according to the arrangement order of the query parameters, select the query parameter with the highest priority in the arrangement order as the query parameter of the page that triggers the jump. The above arrangement order can be set by the developer according to the actual application scenario. For example, suppose the current multi-level jump pages are A, B, and C in the jump order from first to last, where page B can also be accessed separately and trigger a jump to page C. After the page jump occurs, the arrangement order of the query parameters of the multi-level jump pages includes A, B, C and B, C. Then, when the jump is triggered by page A, the query parameters ultimately filtered are the query parameters of page A. When the jump is triggered by page B, the query parameters ultimately filtered are the query parameters of page B.
[0101] In one possible implementation, for scenarios where the query parameters include the query parameters of each page involved in the redirect, since the query parameters of each page involved in the redirect are included, this application can also collect the query parameters of each page to restore the user's access link, ensuring the completeness and accuracy of the page redirect path, thereby providing accurate data for subsequent impact evaluation and optimization. At the same time, it also provides reliable data for optimizing delivery strategies and resource utilization.
[0102] In one possible implementation, the method for determining the page source provided by the first aspect of the present application and any possible implementation thereof further includes:
[0103] In the case of creating a new multi-level jump page, create a new Hypertext Transfer Protocol tracking information text;
[0104] The page identifier and query parameters corresponding to each newly created page in the newly created multi-level jump page are correspondingly stored in the newly created hypertext transfer protocol tracking information text.
[0105] It should be noted that in actual application scenarios, for a newly created multi-level jump page, since the multi-level jump page has not been put into use, the multi-level jump page does not have corresponding cookies and page access logs. This makes it possible that when the newly created multi-level jump page is used for the first time and the page source of the newly created multi-level jump page is determined for the first time, there is a risk that the page source cannot be completed due to the absence of the above data, thereby reducing the reliability of determining the page source. Therefore, the present application configures a new hypertext transfer protocol tracking information text when a new multi-level jump page is created, stores the query parameters corresponding to the newly created pages at each level, and the newly created page identifiers corresponding to the query parameters, in the newly created hypertext transfer protocol tracking information text, and stores the newly created hypertext transfer protocol tracking information text, thereby ensuring that the corresponding query parameters can be found and the page source can be determined when the page source of the newly created multi-level jump page is determined for the first time, thereby improving the reliability of determining the page source.
[0106] It should be noted that in actual application scenarios, due to differences in the timeliness and periodicity of page source statistics for different businesses (for example, page source statistics for page orders are short-term, while page source statistics for promotion channel evaluation scenarios are long-term), to reduce the long-term occupation of browser storage space, after each HTTP tracking information text is generated, an expiration time can be configured for each HTTP tracking information text. After the expiration time is reached, the HTTP tracking information text will be automatically deleted.
[0107] In one possible implementation, searching for query parameters from a hypertext transfer protocol tracking information text associated with a target page includes:
[0108] From a plurality of candidate hypertext transfer protocol tracking information texts, determining the candidate hypertext transfer protocol tracking information text whose text is identified as the uniform resource locator of the target page as the hypertext transfer protocol tracking information text associated with the target page;
[0109] Extract the query parameter field content in the hypertext transfer protocol tracking information text as the query parameter.
[0110] It should be noted that in actual application scenarios, since the HTTP tracking information text is data stored on the browser side, and the browser side generates a large amount of HTTP tracking information text, the present application configures a candidate HTTP tracking information text that identifies the text as the uniform resource locator of the target page from multiple candidate HTTP tracking information texts, thereby filtering the HTTP tracking information text associated with the target page and improving the accuracy of determining the query parameters and page source.
[0111] In one possible implementation, searching for query parameters from a hypertext transfer protocol tracking information text associated with a target page includes:
[0112] Parsing a request header of the page jump request to obtain a text identifier of at least one hypertext transfer protocol tracking information text in the page jump request, and determining a plurality of candidate hypertext transfer protocol tracking information texts based on the text identifier;
[0113] Extracting the business data identifier of the target page, and determining the candidate hypertext transfer protocol tracking information text storing the business data identifier as the hypertext transfer protocol tracking information text associated with the target page;
[0114] Extract the query parameter field content in the hypertext transfer protocol tracking information text as the query parameter.
[0115] It should be noted that in actual application scenarios, since the Hypertext Transfer Protocol tracking information text is data that exists on the browser side, and the browser side generates a large amount of Hypertext Transfer Protocol tracking information text. Therefore, this application obtains the text identifier of at least one Hypertext Transfer Protocol tracking information text in the page jump request by configuring the request header parsing of the page jump request, and determines multiple alternative Hypertext Transfer Protocol tracking information texts based on the text identifier; extracts the business data identifier of the target page, and stores the alternative Hypertext Transfer Protocol tracking information text with the business data identifier, thereby realizing the screening of the Hypertext Transfer Protocol tracking information text associated with the target page, and improving the accuracy of determining the query parameters and page source.
[0116] The second aspect of the present application provides a system for determining the source of a page, such as Figure 4 As shown, the system for determining the source of the page includes:
[0117] The first search unit 401 is configured to search for a query parameter in the uniform resource locator of the target page, and if the query parameter exists in the uniform resource locator, determine the page identifier corresponding to the query parameter as the page source identifier of the target page;
[0118] The second search unit 402 is configured to search for the query parameter in the Referer field of the page jump request to the target page when the query parameter does not exist in the uniform resource locator;
[0119] The first determining unit 403 is configured to, when a query parameter exists in the Referer field, determine the page identifier corresponding to the query parameter as the page source identifier of the target page;
[0120] The third search unit 404 is used to search for query parameters from the hypertext transfer protocol tracking information text associated with the target page when there is no query parameter in the Referer field, and determine the page identifier corresponding to the found query parameter as the page source identifier of the target page.
[0121] In a possible implementation, the system for determining the page source provided in the second aspect of the present application further includes:
[0122] The fourth search unit is used to search for query parameters from the page access log based on the uniform resource locator of the target page when there are no query parameters in the hypertext transfer protocol tracking information text, and determine the page identifier corresponding to the query parameters as the page source identifier of the target page.
[0123] In a possible implementation, the system for determining the page source provided in the second aspect of the present application further includes:
[0124] The first creating unit is used to create a new hypertext transfer protocol tracking information text when obtaining the query parameter and the page identifier corresponding to the query parameter, and store the query parameter and the page identifier in the newly created hypertext transfer protocol tracking information text accordingly.
[0125] In a possible implementation, the system for determining the page source provided in the second aspect of the present application further includes:
[0126] The second new creation unit is used to create a new hypertext transfer protocol tracking information text when creating a new multi-level jump page; and store the page identifier and query parameters corresponding to each new page in the new multi-level jump page into the new hypertext transfer protocol tracking information text.
[0127] In a possible implementation, the third search unit 404 is configured to search for query parameters in the hypertext transfer protocol tracking information text associated with the target page:
[0128] From a plurality of candidate hypertext transfer protocol tracking information texts, determining the candidate hypertext transfer protocol tracking information text whose text is identified as the uniform resource locator of the target page as the hypertext transfer protocol tracking information text associated with the target page;
[0129] Extract the query parameter field content in the hypertext transfer protocol tracking information text as the query parameter.
[0130] In a possible implementation, the third search unit 404 is configured to search for query parameters in the hypertext transfer protocol tracking information text associated with the target page:
[0131] Parsing a request header of the page jump request to obtain a text identifier of at least one hypertext transfer protocol tracking information text in the page jump request, and determining a plurality of candidate hypertext transfer protocol tracking information texts based on the text identifier;
[0132] Extracting the business data identifier of the target page, and determining the candidate hypertext transfer protocol tracking information text storing the business data identifier as the hypertext transfer protocol tracking information text associated with the target page;
[0133] Extract the query parameter field content in the hypertext transfer protocol tracking information text as the query parameter.
[0134] A third aspect of the present application provides a computer program product comprising computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device is enabled to implement the method for determining the page source of the first aspect or any implementation of the first aspect.
[0135] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:
[0136] Memory is used to store computer programs;
[0137] The processor is used to execute a computer program so that the electronic device can implement the method for determining the page source of the first aspect or any implementation of the first aspect.
[0138] In a fifth aspect, the present application provides a computer program product comprising computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device is enabled to implement the method for determining the page source of the first aspect or any implementation of the first aspect.
[0139] The structural diagram of the electronic device provided in the fourth aspect of this application is as follows Figure 5 The electronic devices in the embodiments of the present application may include, but are not limited to, fixed terminals such as mobile phones, laptop computers, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, and the like. Figure 5 The electronic device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.
[0140] like Figure 5 As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes based on programs stored in a read-only memory (ROM) 502 or programs loaded from a storage device 508 into a random access memory (RAM) 503. When the electronic device is powered on, the RAM 503 also stores various programs and data required for the operation of the electronic device. The processing device 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.
[0141] Typically, the following devices may be connected to the I / O interface 505: an input device 506 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 508 including, for example, a memory card, a hard disk, etc.; and a communication device 509. The communication device 509 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Figure 5 The electronic device is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.
[0142] A computer-readable storage medium is also provided in an embodiment of the present application. The storage medium carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement any method for determining the source of a page order provided in an embodiment of the present application.
[0143] It should also be noted that the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, in the drawings of the device embodiments provided in this application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.
[0144] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course can also be implemented by special hardware including application-specific integrated circuits, special CPUs, special memories, special components, etc. In general, all functions performed by computer programs can be easily implemented with corresponding hardware, and the specific hardware structures used to implement the same function can also be diverse, such as analog circuits, digital circuits or special circuits, etc. However, for the present application, software program implementation is a better implementation method in most cases. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer's floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., and includes a number of instructions to enable a computer device (which can be a personal computer, training equipment, or network equipment, etc.) to execute the methods described in each embodiment of the present application.
[0145] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.
[0146] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, a computer, a training device or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website, a computer, a training device or a data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).
Claims
1. A method for determining the source of a page, characterized in that: include: searching for a query parameter from the uniform resource locator of the target page, and if the query parameter exists in the uniform resource locator, determining the page identifier corresponding to the query parameter as the page source identifier of the target page; If the query parameter does not exist in the uniform resource locator, searching for the query parameter in the Referer field of the page jump request to the target page; When the query parameter exists in the Referer field, determining the page identifier corresponding to the query parameter as the page source identifier of the target page; When the query parameter does not exist in the Referer field, the query parameter is searched for in the hypertext transfer protocol tracking information text associated with the target page, and the page identifier corresponding to the searched query parameter is determined as the page source identifier of the target page.
2. The method for determining the page source according to claim 1, wherein: The method further comprises: When the query parameter does not exist in the hypertext transfer protocol tracking information text, the query parameter is searched from the page access log based on the uniform resource locator of the target page, and the page identifier corresponding to the query parameter is determined as the page source identifier of the target page.
3. The method for determining the page source according to any one of claims 1 or 2, characterized in that: The method further comprises: When the query parameter and the page identifier corresponding to the query parameter are obtained, the hypertext transfer protocol tracking information text is newly created, and the query parameter and the page identifier are correspondingly stored in the newly created hypertext transfer protocol tracking information text.
4. The method for determining the page source according to any one of claims 1 to 3, characterized in that: The method further comprises: In the case of creating a new multi-level jump page, creating the hypertext transfer protocol tracking information text; The page identifier and query parameter corresponding to each newly created page in the newly created multi-level jump page are correspondingly stored in the newly created hypertext transfer protocol tracking information text.
5. The method for determining the page source according to claim 1, wherein: The step of searching for the query parameter from the hypertext transfer protocol tracking information text associated with the target page includes: From a plurality of candidate hypertext transfer protocol tracking information texts, determine the candidate hypertext transfer protocol tracking information text whose text is identified as the uniform resource locator of the target page as the hypertext transfer protocol tracking information text associated with the target page; The query parameter field content in the hypertext transfer protocol tracking information text is extracted as the query parameter.
6. The method for determining the page source according to claim 1, wherein: The step of searching for the query parameter from the hypertext transfer protocol tracking information text associated with the target page includes: parsing a request header of the page jump request to obtain a text identifier of at least one hypertext transfer protocol tracking information text in the page jump request, and determining a plurality of candidate hypertext transfer protocol tracking information texts based on the text identifier; extracting the business data identifier of the target page, and determining the candidate hypertext transfer protocol tracking information text storing the business data identifier as the hypertext transfer protocol tracking information text associated with the target page; The query parameter field content in the hypertext transfer protocol tracking information text is extracted as the query parameter.
7. A system for determining the source of a page, characterized in that: The page source determination system includes: a first search unit configured to search for a query parameter from a uniform resource locator of a target page, and if the query parameter exists in the uniform resource locator, determine a page identifier corresponding to the query parameter as a page source identifier of the target page; a second searching unit, configured to search for the query parameter in a Referer field of a page jump request to the target page when the query parameter does not exist in the uniform resource locator; a first determining unit, configured to, when the query parameter exists in the Referer field, determine the page identifier corresponding to the query parameter as the page source identifier of the target page; The third search unit is used to search for the query parameter from the hypertext transfer protocol tracking information text associated with the target page when the query parameter does not exist in the Referer field, and determine the page identifier corresponding to the found query parameter as the page source identifier of the target page.
8. A computer program product, characterized in that The method comprises computer-readable instructions, which, when executed on an electronic device, enable the electronic device to implement the method for determining the source of a page as claimed in any one of claims 1 to 6.
9. An electronic device, characterized in that: comprising at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is configured to execute the computer program so that the electronic device can implement the method for determining the page source as described in any one of claims 1 to 6.
10. A computer program product, characterized in that It includes computer-readable instructions, which, when executed on an electronic device, enable the electronic device to implement the method for determining the source of a page order as described in any one of claims 1 to 6.