Method, system, device and storage medium for processing advertisement page embedding points

Abstract

The embodiment of the present application discloses a method, system, device and storage medium for processing advertising page embedding. The technical solution provided by the embodiment of the present application, by displaying an advertising page and a trigger condition collection page, the advertising page is pre-embedded with a monitoring code, the monitoring code includes a reserved parameter bit, and the reserved parameter bit is configured to set the trigger condition of the page event; in response to the first operation on the advertising page, the trigger condition corresponding to the first operation is determined, and the trigger condition is displayed on the trigger condition collection page; in response to the second operation on the trigger condition collection page, the trigger condition displayed on the trigger condition collection page is transmitted back to the server, so that the trigger condition is written into the reserved parameter bit through the server, so that the monitoring code monitors the corresponding page event according to the trigger condition. By adopting the above technical means, the technical threshold for embedding advertising pages can be lowered, the complicated operations of embedding advertising pages can be simplified, and the monitoring and processing experience of advertising pages by advertisers can be optimized.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a method, system, device and storage medium for processing advertising page embedding points. Background Art

[0002] Currently, in advertising scenarios, to determine user sources and determine information such as the conversion rate and cost of each ad, it is necessary to monitor events such as ad page exposure and button clicks. Data from each generated event is collected for analysis to optimize ad delivery effectiveness and billing operations. To monitor ad page events, a tracking method is typically used: embedding executable code within the ad page. When a page event is detected, this code triggers the collection of tracking data and reports it to the backend server, thereby implementing page event reporting.

[0003] However, for advertisers, applying code for tracking requires certain front-end code design knowledge, and code management is relatively complex. Advertisers without technical expertise typically need to submit their page event monitoring requirements to a service provider, who then performs tracking on their ad pages. This process is relatively complex, requiring significant effort from the service provider's operations staff. Furthermore, due to the high barrier to entry for tracking, advertisers often experience a poor experience monitoring their ad pages. Summary of the Invention

[0004] The embodiments of the present application provide a method, system, device and storage medium for processing advertising page embedding, which can lower the technical threshold for advertising page embedding and solve the technical problem of complicated advertising page embedding operations.

[0005] In a first aspect, an embodiment of the present application provides a method for processing an advertisement page embedding point, comprising:

[0006] Embed monitoring code in the advertisement page. The monitoring code includes reserved parameter bits. The reserved parameter bits are configured to set trigger conditions for page events.

[0007] Get the trigger conditions uploaded by the specified client. The trigger conditions are collected when the specified client operates the advertising page and triggers the page event.

[0008] Write the trigger condition into the reserved parameter bit so that the monitoring code can monitor the corresponding page event according to the trigger condition.

[0009] In a second aspect, an embodiment of the present application provides a method for processing an advertisement page embedding point, including:

[0010] Display the advertising page and the trigger condition collection page. The advertising page has pre-embedded monitoring code. The monitoring code includes reserved parameter bits. The reserved parameter bits are configured to set the trigger conditions of the page events.

[0011] In response to a first operation on the advertisement page, determining a trigger condition corresponding to the first operation, and displaying the trigger condition on a trigger condition collection page;

[0012] In response to the second operation on the trigger condition collection page, the trigger condition displayed on the trigger condition collection page is transmitted back to the server, so that the trigger condition is written into the reserved parameter bit through the server, so that the monitoring code monitors the corresponding page event according to the trigger condition.

[0013] In a third aspect, an embodiment of the present application provides an advertising page embedding processing system, including:

[0014] The embedding module is configured to embed monitoring code in the advertising page. The monitoring code includes reserved parameter bits, and the reserved parameter bits are configured to set the triggering conditions of the page events;

[0015] An acquisition module is configured to acquire trigger conditions uploaded by a specified client. The trigger conditions are collected when the specified client operates the advertisement page and triggers a page event.

[0016] The event configuration module is configured to write the trigger condition into the reserved parameter bit so that the monitoring code monitors the corresponding page event according to the trigger condition.

[0017] In a fourth aspect, an embodiment of the present application provides an advertising page embedding processing system, including:

[0018] A display module is configured to display an advertisement page and a trigger condition collection page. The advertisement page is pre-embedded with a monitoring code. The monitoring code includes a reserved parameter bit. The reserved parameter bit is configured to set the trigger condition of the page event.

[0019] a first response module configured to, in response to a first operation on the advertisement page, determine a trigger condition corresponding to the first operation and display the trigger condition on a trigger condition collection page;

[0020] The second response module is configured to respond to the second operation on the trigger condition collection page, and transmit the trigger condition displayed on the trigger condition collection page back to the server, so that the trigger condition is written into the reserved parameter bit through the server, so that the monitoring code monitors the corresponding page event according to the trigger condition.

[0021] In a fifth aspect, an embodiment of the present application provides an advertising page embedding processing device, including:

[0022] memory and one or more processors;

[0023] The memory is configured to store one or more programs;

[0024] When the one or more programs are executed by the one or more processors, the one or more processors implement the advertising page embedding processing method as described in the first aspect or the second aspect.

[0025] In a sixth aspect, an embodiment of the present application provides a storage medium comprising computer-executable instructions, which, when executed by a computer processor, are configured to execute the advertising page embedding processing method as described in the first aspect or the second aspect.

[0026] The embodiment of the present application displays an advertisement page and a trigger condition collection page, and the advertisement page is pre-buried with a monitoring code, the monitoring code includes a reserved parameter bit, and the reserved parameter bit is configured to set the trigger condition of the page event; in response to the first operation on the advertisement page, the trigger condition corresponding to the first operation is determined, and the trigger condition is displayed on the trigger condition collection page; in response to the second operation on the trigger condition collection page, the trigger condition displayed on the trigger condition collection page is transmitted back to the server, so that the trigger condition is written into the reserved parameter bit through the server, so that the monitoring code monitors the corresponding page event according to the trigger condition. The above technical means can be adopted to enable advertisers to choose to set the trigger condition of the page event in a visual manner, so as to independently configure the page events that need to be monitored, reduce the technical threshold for burying the advertisement page, simplify the complicated operations of burying the advertisement page, optimize the advertiser's monitoring and processing experience of the advertisement page, and improve the flexibility of burying the advertisement page. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 This is a flow chart of a method for processing an advertisement page embedding point provided by an embodiment of the present application;

[0028] Figure 2 This is a flowchart of another advertising page embedding processing method provided by an embodiment of the present application;

[0029] Figure 3 This is a schematic diagram of trigger condition settings provided by an embodiment of the present application;

[0030] Figure 4 This is a schematic diagram of data communication between the server and the advertiser client provided in an embodiment of the present application;

[0031] Figure 5 This is another trigger condition setting diagram provided in an embodiment of the present application;

[0032] Figure 6 This is another data communication diagram between a server and an advertiser client provided in an embodiment of the present application;

[0033] Figure 7This is a structural diagram of an advertising page embedding processing system provided by an embodiment of the present application;

[0034] Figure 8 This is a structural diagram of another advertising page embedding processing system provided in an embodiment of the present application;

[0035] Figure 9 It is a structural diagram of an advertising page embedding processing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] In order to make the purpose, technical solutions and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. It should also be noted that, for ease of description, only parts related to the present application, not all of the contents, are shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow charts describe each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but can also have additional steps not included in the accompanying drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0037] The advertising page burying processing method provided in this application is intended to enhance the advertiser's autonomous monitoring and processing experience of the advertising page by visually configuring the page events that need to be monitored when the advertising page is buried, thereby enhancing the flexibility of the advertising page burying. In the advertising delivery scenario, for advertisers, it is necessary to monitor events such as exposure and button clicks of the advertising page to perform advertising attribution. The purpose of attribution is to determine the source of users and determine the effectiveness of the advertisement, thereby guiding the subsequent advertising delivery. That is, when an application or website brings conversions due to the delivery of advertisements, attribution will be used to determine which platform and which advertisement the conversion comes from, so as to know the conversion rate and conversion cost of each advertisement, so as to continuously improve the quality of advertising delivery. Therefore, for advertising platforms, attribution is mainly used to confirm how many conversion behaviors are brought to advertisers, and then deduct advertising fees based on the bids of conversion behaviors. Advertisement burying is one of the main ways to collect corresponding data for advertising attribution. When burying advertisements on advertising pages, the existing practice is that the server-side operator designs a monitoring code (such as a JS plug-in) and embeds the monitoring code into the advertising page that needs to monitor page events. The monitoring code needs to be pre-configured with the page events that need to be monitored. Generally speaking, the operator will adaptively design the monitoring code according to the page event monitoring requirements fed back by the advertiser, so that the monitoring code can monitor the corresponding page events. Since the monitoring requirements of the advertiser change in real time, the server-side operator must redesign the monitoring code every time the monitoring requirements are modified. The whole process is relatively complicated. For advertisers, their monitoring management of advertising pages lacks flexibility. If the advertiser configures the page events independently, the advertiser is also required to modify the monitoring code. For advertisers, applying code for burying points requires certain front-end code design knowledge, and the management of the code is also relatively complicated. For advertisers without technical foundation, page event configuration is more difficult. Based on this, a method for processing advertising page burying points in an embodiment of the present application is provided to solve the technical problem of complicated advertising page burying point operations.

[0038] Example:

[0039] Figure 1 A flowchart of an advertising page embedding processing method provided in an embodiment of the present application is provided. The advertising page embedding processing method provided in this embodiment can be executed by an advertising page embedding processing device. The advertising page embedding processing device can be implemented by software and / or hardware. The advertising page embedding processing device can be composed of two or more physical entities or a single physical entity. Generally speaking, the advertising page embedding processing device can be a server-side device, a computer, or other computing device.

[0040] The following description takes the server as the main body of the advertising page embedding processing method as an example. Figure 1The specific method for processing the ad page embedding includes:

[0041] S110: embed a monitoring code in the advertisement page, wherein the monitoring code includes a reserved parameter bit, and the reserved parameter bit is configured to set a trigger condition for a page event;

[0042] S120: Acquire trigger conditions uploaded by a designated client, where the trigger conditions are collected when the designated client operates an advertisement page and triggers a page event.

[0043] S130 : Writing the trigger condition into the reserved parameter bit, so that the monitoring code monitors the corresponding page event according to the trigger condition.

[0044] The embodiment of the present application implements the operation of embedding advertisement page points through data communication between the server and the designated client. Among them, the server is the end that provides advertisement page embedding and advertisement attribution services. The designated client is the end that delivers page advertisements and uses advertisement attribution services. The designated client can be the client used by the advertiser, that is, the advertiser client. In order to simplify the operation of embedding advertisement page points, the present application adopts a method of setting visual trigger conditions to facilitate the setting of trigger events by the designated client. By allowing advertisers to independently select trigger events, the configuration of page events that advertisers need to monitor is realized, thereby realizing a simple, flexible and highly personalized advertisement page embedding operation.

[0045] It is understandable that for advertisers, the purpose of attribution is to determine the source of users and the effectiveness of advertisements, thereby guiding subsequent delivery. That is, when an application or website generates a conversion due to the delivery of an advertisement, attribution will be used to determine which platform and which advertisement the conversion originated from, thereby knowing the conversion rate and conversion cost of each advertisement, thereby continuously improving the quality of advertising delivery. In order to facilitate advertisers to independently configure the page events that need to be monitored and define their own monitoring and processing for advertisements, thereby obtaining more effective and accurate attribution data, the server obtains the trigger conditions selected by the advertiser, and then determines the page events that need to be monitored based on the trigger conditions by writing the trigger conditions into the monitoring code.

[0046] Specifically, when embedding an ad page, the server foresees embedding the monitoring code into the ad page that needs to be monitored. At this time, the monitoring code is the basic code, and the page event that needs to be monitored has not yet been set. Because when monitoring page events, the monitoring code needs to detect the relevant triggering operations received by the current ad page (such as clicking on an element on the ad page), and then determine whether the triggering operation corresponds to the pre-stored triggering conditions. If so, the page event monitoring of the current ad page is triggered. Therefore, in order to configure the page events that advertisers need to monitor, it is necessary to set the corresponding triggering conditions in the monitoring code.

[0047] The embodiment of the present application sets a reserved parameter bit in the monitoring code, and the reserved parameter bit is used to write the trigger condition selected by the advertiser. After embedding the monitoring code in the advertising page, the server will collect the trigger conditions uploaded by the designated client and write the trigger conditions into the reserved parameter bit, so that the monitoring code can monitor the corresponding page events according to the trigger conditions. After the advertiser opens the advertising page through the designated client, it triggers the corresponding page event by operating the advertising page according to the page event that needs to be monitored, so that the designated client can collect the trigger conditions for triggering the page event. This trigger condition is then reported to the server, and the server writes the trigger condition into the reserved parameter bit, so that the monitoring code can monitor the corresponding page event according to the trigger condition.

[0048] The designated client loads an ad page for advertisers to browse, allowing them to simply circle the page event they want to monitor. The designated client then tracks the user's triggering actions to determine the triggering conditions for the current page event. This enables visual page event configuration, simplifies ad page tracking operations on the advertiser's end, and improves the advertiser's ad page monitoring experience.

[0049] After the trigger conditions are written into the monitoring code, the monitoring code can monitor relevant page events generated when users browse advertising pages. When the monitoring code detects that the trigger action received by the advertising page matches the trigger conditions, it executes the corresponding page event monitoring operation and reports the generated monitoring information. The monitoring information includes the page event ID, user identification information, and client information.

[0050] For example, when the server executes the ad page embedding, it first uses the native js language to implement a basic monitoring code. This code will then be embedded in the ad page that the advertiser needs to monitor for events on the ad page. The basic monitoring code contains reserved macro parameters, that is, reserved parameter positions. After the advertiser configures the trigger condition by specifying the client visualization, the trigger condition will replace the macro parameters reserved in the basic monitoring code in advance, and finally form a JSON string. After that, the basic code monitors whether the path of the element clicked on the ad page is consistent with the path recorded by the trigger event. If they are consistent, the page event monitoring is triggered. This generates an http request based on the monitoring code, and sends the current page event ID, user identification information (such as user ID, session ID) and client information (such as browser language, resolution and configuration information, as well as page title, URL and traffic source, etc.) to the server through the http request for advertising attribution through the server. Optionally, the server can perform deduplication statistics or not for the same event triggered multiple times by the same user to achieve better advertising attribution effect.

[0051] It is understandable that the trigger condition records the path that triggers the corresponding page event, such as the location of the click on the advertisement page. Then, when the click location detected on the advertisement page matches the trigger condition, the monitoring of the page event corresponding to the trigger condition can be triggered.

[0052] Specifically, refer to Figure 2 , provides a flowchart of another advertising page embedding processing method of the embodiment of the present application, which can be executed by an advertiser client (i.e., the above-mentioned designated client) device, a computer, and other computing devices. The following description is based on the advertiser client as the main body of the advertising page embedding processing method. Figure 2 The specific method for processing the ad page embedding includes:

[0053] S210: Display an advertisement page and a trigger condition collection page. The advertisement page has a monitoring code pre-embedded therein. The monitoring code includes a reserved parameter bit, and the reserved parameter bit is configured to set a trigger condition for a page event.

[0054] S220: In response to a first operation on the advertisement page, determining a trigger condition corresponding to the first operation, and displaying the trigger condition on a trigger condition collection page;

[0055] S230. In response to the second operation on the trigger condition collection page, the trigger condition displayed on the trigger condition collection page is transmitted back to the server, so that the trigger condition is written into the reserved parameter bit through the server, so that the monitoring code monitors the corresponding page event according to the trigger condition.

[0056] On the advertiser client side, when setting the trigger conditions, the trigger conditions can be visually set by displaying the advertising page and the trigger condition collection page. It is understandable that the monitoring code implements the page event configuration by writing the trigger conditions into the reserved parameter bits. In order to determine the page event that the advertiser configures to monitor, the embodiment of the present application displays the trigger conditions set by the advertiser in real time by displaying the advertising page on the advertiser client for trigger condition selection. In a visual form, the advertiser can clearly understand the trigger conditions set by himself, so as to achieve accurate and effective page event monitoring configuration. In this way, when the advertiser triggers the corresponding page event by responding to the trigger operation, the trigger operation is defined as the first operation. By collecting the trigger conditions corresponding to the first operation and displaying them on the trigger condition collection page, a page event monitoring configuration can be completed.

[0057] It is understood that for any page event that an advertiser needs to monitor, the corresponding trigger conditions can be displayed on the trigger condition collection page through the trigger condition settings. Similarly, according to actual needs, the corresponding trigger conditions on the trigger condition collection page can be adaptively deleted to cancel the monitoring configuration of the corresponding page event.

[0058] After setting the trigger conditions, the advertiser returns the trigger conditions to the server by operating the trigger condition collection page. The server then writes the trigger conditions into the reserved parameter bits, causing the monitoring code to monitor the corresponding page events based on the trigger conditions. This operation is defined as the second operation, which can be, for example, clicking the trigger condition report button on the trigger condition collection page. This embodiment of the application does not impose fixed restrictions on the method of reporting trigger conditions on the trigger condition collection page, and will not be elaborated on here.

[0059] By combining the ad page with the trigger condition collection page for visual trigger condition setting and lowering the threshold for ad page tracking, advertisers no longer need to check tracking code one by one. Instead, they can configure page event monitoring through ad page interaction. Furthermore, the visual tracking method can avoid situations where tracking detection is impossible due to business scenario limitations. Based on the ad page and the trigger condition collection page, you can intuitively and accurately obtain the page events currently monitored, thereby improving the data accuracy of ad attribution conversions and optimizing ad attribution effectiveness.

[0060] Optionally, when setting the trigger conditions, the embodiment of the present application provides two page opening methods: opening the advertisement page and the trigger condition collection page based on opening within the site and opening the advertisement page and the trigger condition collection page based on opening outside the site.

[0061] Among them, reference Figure 3 , provides a schematic diagram of trigger condition settings based on the pages opened within the site. Among them, the advertising page is embedded in the trigger condition collection page based on the iframe, and communicates data with the trigger condition collection page by publishing messages.

[0062] Specifically, an ad page embedded with basic monitoring code is loaded onto the trigger condition collection page, with the trigger condition collection page acting as the ad page's parent page. Both are built using the HTML inline frame element, which embeds an HTML page (i.e., the ad page) within the trigger condition collection page. Within this nested frame, the advertiser client can extract the trigger conditions displayed on the trigger condition collection page based on the monitoring code and transmit the trigger conditions back to the server.

[0063] like Figure 4As shown, the monitoring code 13 is used to communicate between the server 11 and the advertiser client 12. The monitoring code will monitor the position of the mouse hovering on the advertising page in real time and obtain the target element corresponding to the mouse click event. By implementing a path function, the ID, type, and tag name of the target element are calculated to obtain a unique path about the target element, and the path is used as the trigger condition and sent to the trigger condition collection page for display. The trigger condition may include the loading of the advertising page and the clicking of the advertising page element, so the trigger condition also needs to record the triggering time of the above-mentioned page event, that is, page loading or clicking. After obtaining this trigger condition, the trigger condition collection page will splice this trigger condition (including the triggering event timing, such as page loading or clicking) into a JSON string array. After completing the trigger condition selection, the advertiser client 12 saves the trigger condition to the server 11 through the monitoring code 13. The server 11 implements the page event configuration by replacing the macro parameter at the reserved parameter position with the JSON string array of the trigger condition.

[0064] It's understandable that when you open a page on the site, you embed the ad page into the trigger collection page provided by the server using frame embedding technology. The ad page and the trigger collection page within the frame are isolated from each other and do not interfere with each other. The ad page and the trigger collection page communicate data by publishing messages.

[0065] For example, when the advertiser selects the trigger condition, the advertiser logs in to the server website and opens the Figure 3 The embedded page is shown. By clicking the "Add to Cart" element on the advertising page a1, the advertiser client determines the trigger condition for clicking the "Add to Cart" element and then displays the trigger condition on the trigger condition collection page a2. After completing the trigger condition selection, the trigger condition recorded on the trigger condition collection page is uploaded to the server, and the trigger condition is set through the server. For each element on the advertising page, the server pre-records the corresponding trigger condition. In this way, when a click operation on the corresponding element is detected, the trigger condition of the element can be determined, improving the efficiency of detecting and setting the trigger condition.

[0066] In one embodiment, the advertiser client further displays the trigger condition collection page based on a pre-installed extension program, and when the advertisement page is opened using a browser, the extension plug-in enables the advertisement page to communicate with the trigger condition collection page.

[0067] It is understandable that since some browsers do not allow opening http links in web pages, or some advertising pages will prevent themselves from being loaded by the parent page, in this case the page cannot be opened normally through the site settings. Therefore, the embodiment of the present application provides a method of opening the page outside the site to perform visual settings of the trigger conditions.

[0068] Specifically, if Figure 5 As shown, an extension program is installed on the advertiser's client, which displays a trigger condition collection page a3 on the advertiser's client. When the advertiser opens ad page a3 in a browser, the extension program's plug-in enables communication between ad page a3 and trigger condition collection page a4. Using the trigger condition detection method described above, the trigger conditions selected by the advertiser on ad page a3 are displayed on trigger condition collection page a4. Once the trigger condition settings are complete, the trigger conditions are uploaded to the server.

[0069] Among them, when uploading the trigger conditions, the advertiser client extracts the trigger conditions displayed on the trigger condition collection page based on the content script of the extension program, and transmits the trigger conditions back to the server based on the transfer script of the extension program.

[0070] For example, Figure 6 As shown, since the advertiser client 12 has installed the extension, the content script 14 (contentScripts.js) is executed when any page is loaded. When the trigger condition is uploaded, the content script extracts the trigger condition and sends it to the server 11 through the transfer cost reduction 15 (background.js). The server 11 also obtains the trigger condition through its own content script 14 and then writes the trigger condition into the preview parameter of the monitoring code, thus completing the page event monitoring configuration.

[0071] By opening the visualization page both on-site and off-site, the visualization configuration of the trigger conditions can meet the configuration environment of different scenarios, optimize the configuration effect of page event monitoring, improve the efficiency of advertising page embedding, and improve the accuracy of advertising attribution.

[0072] As described above, by displaying the advertising page and the trigger condition collection page, the advertising page is pre-buried with a monitoring code, which includes a reserved parameter bit, and the reserved parameter bit is configured to set the trigger condition of the page event; in response to the first operation on the advertising page, the trigger condition corresponding to the first operation is determined, and the trigger condition is displayed on the trigger condition collection page; in response to the second operation on the trigger condition collection page, the trigger condition displayed on the trigger condition collection page is transmitted back to the server, so that the trigger condition is written into the reserved parameter bit through the server, so that the monitoring code monitors the corresponding page event according to the trigger condition. The above technical means can enable advertisers to choose to set the trigger condition of the page event in a visual manner, so as to independently configure the page events that need to be monitored, reduce the technical threshold for burying the advertising page, simplify the complicated operations of burying the advertising page, optimize the advertiser's monitoring and processing experience of the advertising page, and improve the flexibility of burying the advertising page.

[0073] Based on the above embodiments, Figure 7 This is a schematic diagram of the structure of an advertising page embedding processing system provided by this application. Figure 7 The advertising page embedding processing system provided in this embodiment specifically includes: an embedding module 31, an acquisition module 32 and an event configuration module 33.

[0074] The embedding module 31 is configured to embed a monitoring code in the advertisement page. The monitoring code includes a reserved parameter bit, and the reserved parameter bit is configured to set the triggering condition of the page event.

[0075] The acquisition module 32 is configured to acquire the trigger conditions uploaded by the designated client, and the trigger conditions are collected when the designated client operates the advertisement page and triggers a page event;

[0076] The event configuration module 33 is configured to write the trigger condition into the reserved parameter bit, so that the monitoring code monitors the corresponding page event according to the trigger condition.

[0077] Specifically, when the monitoring code detects that the trigger operation received by the advertising page is consistent with the trigger condition, it performs the corresponding page event monitoring operation and reports the generated monitoring information. The monitoring information includes the page event ID, user identification information and client information.

[0078] Based on the above embodiments, Figure 8 This is a schematic diagram of another advertising page embedding processing system provided by this application. Figure 8 The advertising page embedding processing system provided in this embodiment specifically includes: a display module 41, a first response module 42 and a second response module 43.

[0079] The display module 41 is configured to display an advertising page and a trigger condition collection page. The advertising page is pre-embedded with a monitoring code, which includes reserved parameter bits. The reserved parameter bits are configured to set the trigger conditions of the page events; wherein the trigger conditions include advertising page loading and advertising page element clicks.

[0080] The first response module 42 is configured to, in response to a first operation on the advertisement page, determine a trigger condition corresponding to the first operation and display the trigger condition on a trigger condition collection page;

[0081] The second response module 43 is configured to respond to the second operation on the trigger condition collection page, and transmit the trigger condition displayed on the trigger condition collection page back to the server, so that the trigger condition is written into the reserved parameter bit through the server, so that the monitoring code monitors the corresponding page event according to the trigger condition.

[0082] Specifically, the advertisement page is embedded in the trigger condition collection page based on an iframe and communicates with the trigger condition collection page by publishing messages. The second response module 43 extracts the trigger condition displayed on the trigger condition collection page based on the monitoring code and transmits the trigger condition back to the server.

[0083] Specifically, a trigger condition collection page is displayed based on a pre-installed extension program. When an advertisement page is opened in a browser, the extension plug-in enables communication between the advertisement page and the trigger condition collection page. The second response module 43 extracts the trigger condition displayed on the trigger condition collection page based on the extension program's content script and transmits the trigger condition back to the server based on the extension program's relay script.

[0084] As described above, by displaying the advertising page and the trigger condition collection page, the advertising page is pre-buried with a monitoring code, which includes a reserved parameter bit, and the reserved parameter bit is configured to set the trigger condition of the page event; in response to the first operation on the advertising page, the trigger condition corresponding to the first operation is determined, and the trigger condition is displayed on the trigger condition collection page; in response to the second operation on the trigger condition collection page, the trigger condition displayed on the trigger condition collection page is transmitted back to the server, so that the trigger condition is written into the reserved parameter bit through the server, so that the monitoring code monitors the corresponding page event according to the trigger condition. The above technical means can enable advertisers to choose to set the trigger condition of the page event in a visual manner, so as to independently configure the page events that need to be monitored, reduce the technical threshold for burying the advertising page, simplify the complicated operations of burying the advertising page, optimize the advertiser's monitoring and processing experience of the advertising page, and improve the flexibility of burying the advertising page.

[0085] The advertising page embedding processing system provided in the embodiment of the present application can be configured to execute the corresponding advertising page embedding processing method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0086] Based on the above practical example, the embodiment of the present application also provides an advertising page embedding processing device, referring to Figure 9, the advertising page embedding processing device includes: a processor 51, a memory 52, a communication module 53, an input device 54 and an output device 55. The memory 52, as a computer-readable storage medium, can be configured to store software programs, computer executable programs and modules, such as the program instructions / modules corresponding to the advertising page embedding processing method described in any embodiment of the present application (for example, the relevant modules in the advertising page embedding processing system). The communication module 53 is configured to transmit data. The processor 51 executes various functional applications and data processing of the device by running the software programs, instructions and modules stored in the memory, that is, realizes the above-mentioned advertising page embedding processing method. The input device 54 can be configured to receive input digital or character information, and generate key signal input related to the user settings and function control of the device. The output device 55 may include a display device such as a display screen. The advertising page embedding processing device provided above can be configured to execute the advertising page embedding processing method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0087] On the basis of the above embodiments, the embodiments of the present application further provide a storage medium containing computer-executable instructions, wherein the computer-executable instructions are configured to execute a method for processing an advertisement page embedding point when executed by a computer processor, and the storage medium can be any of various types of memory devices or storage devices. Of course, the storage medium containing computer-executable instructions provided in the embodiments of the present application, whose computer-executable instructions are not limited to the advertisement page embedding point processing method described above, can also execute related operations in the advertisement page embedding point processing method provided in any embodiment of the present application.

Claims

1. A method for processing advertisement page embedding points, characterized in that: include: Embedding a monitoring code in the advertisement page, the monitoring code including a reserved parameter bit, the reserved parameter bit being configured to set a triggering condition for a page event; Obtaining the trigger condition uploaded by the designated client, wherein the trigger condition is collected when the designated client operates the advertisement page and triggers the page event, wherein the trigger condition represents a unique path of the target element corresponding to the page event, and the unique path is calculated based on the ID, type, and tag name of the target element based on a path function; The trigger condition is written into the reserved parameter position so that the monitoring code monitors the corresponding page event according to the trigger condition. The trigger condition is recorded using a JSON string array, and the JSON string array is written into the reserved parameter position by replacing the macro parameter of the reserved parameter position.

2. The method for processing advertisement page embedding points according to claim 1, characterized in that: The monitoring code monitors the corresponding page event according to the trigger condition, including: When the monitoring code detects that the trigger operation received by the advertisement page is consistent with the trigger condition, it executes the corresponding monitoring operation of the page event and reports the generated monitoring information.

3. The method for processing advertisement page embedding points according to claim 2, characterized in that: The monitoring information includes page event ID, user identification information and client information.

4. A method for processing advertisement page embedding points, characterized in that: include: Displaying an advertisement page and a trigger condition collection page, wherein the advertisement page is pre-embedded with monitoring code, the monitoring code including reserved parameter bits configured to set a trigger condition for a page event, the trigger condition representing a unique path to a target element corresponding to the page event, the unique path being calculated based on a path function using the ID, type, and tag name of the target element; In response to a first operation on the advertisement page, determining a trigger condition corresponding to the first operation, and displaying the trigger condition on the trigger condition collection page; In response to the second operation on the trigger condition collection page, the trigger condition displayed on the trigger condition collection page is transmitted back to the server, so that the trigger condition is written into the reserved parameter position through the server, so that the monitoring code monitors the corresponding page event according to the trigger condition. The trigger condition is recorded using a JSON string array, and the JSON string array is written into the reserved parameter position by replacing the macro parameter of the reserved parameter position.

5. The method for processing advertisement page embedding points according to claim 4, characterized in that: The advertisement page is embedded in the trigger condition collection page based on an inline frame, and performs data communication with the trigger condition collection page by publishing a message.

6. The method for processing advertisement page embedding points according to claim 5, characterized in that: The trigger condition displayed on the trigger condition collection page is transmitted back to the server, including: The trigger condition displayed on the trigger condition collection page is extracted based on the monitoring code, and the trigger condition is transmitted back to the server.

7. The method for processing advertisement page embedding points according to claim 4, characterized in that: The trigger condition collection page is displayed based on a pre-installed extension program, and when the advertisement page is opened using a browser, the advertisement page communicates with the trigger condition collection page through an extension plug-in.

8. The method for processing advertisement page embedding points according to claim 7, characterized in that: The trigger condition displayed on the trigger condition collection page is transmitted back to the server, including: The trigger condition displayed on the trigger condition collection page is extracted based on the content script of the extension program, and the trigger condition is transmitted back to the server based on the transit script of the extension program.

9. The method for processing an advertisement page embedding point according to any one of claims 4 to 8, characterized in that: The triggering conditions include loading the advertisement page and clicking on an advertisement page element.

10. An advertising page embedding processing system, characterized in that: include: A tracking module is configured to embed a monitoring code in the advertisement page, wherein the monitoring code includes a reserved parameter bit, and the reserved parameter bit is configured to set a triggering condition for a page event; an acquisition module configured to acquire the trigger condition uploaded by a designated client, the trigger condition being collected when the designated client operates the advertisement page and triggers the page event, the trigger condition representing a unique path of a target element corresponding to the page event, the unique path being calculated based on the ID, type, and tag name of the target element based on a path function; An event configuration module is configured to write the trigger condition into the reserved parameter position so that the monitoring code monitors the corresponding page event according to the trigger condition. The trigger condition is recorded using a JSON string array, and the JSON string array is written into the reserved parameter position by replacing the macro parameter of the reserved parameter position.

11. An advertising page embedding processing system, characterized in that: include: A display module is configured to display an advertisement page and a trigger condition collection page, wherein the advertisement page is pre-embedded with a monitoring code, wherein the monitoring code includes a reserved parameter bit, wherein the reserved parameter bit is configured to set a trigger condition for a page event, wherein the trigger condition represents a unique path to a target element corresponding to the page event, wherein the unique path is calculated based on the ID, type, and tag name of the target element based on a path function; a first response module configured to, in response to a first operation on the advertisement page, determine a trigger condition corresponding to the first operation and display the trigger condition on the trigger condition collection page; The second response module is configured to respond to the second operation on the trigger condition collection page, transmit the trigger condition displayed on the trigger condition collection page back to the server, so that the trigger condition is written into the reserved parameter position through the server, so that the monitoring code monitors the corresponding page event according to the trigger condition, and the trigger condition is recorded using a JSON string array, and the JSON string array is written into the reserved parameter position by replacing the macro parameter of the reserved parameter position.

12. An advertising page embedding processing device, characterized in that: include: memory and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the advertising page embedding processing method as described in any one of claims 1-9.

13. A storage medium containing computer-executable instructions, characterized in that: When executed by a computer processor, the computer executable instructions are configured to execute the advertising page embedding processing method as described in any one of claims 1-9.

Images