Data playback method, apparatus, and storage medium

Abstract

Embodiments of the present application provide a data playback method, device and storage medium, wherein the data playback method comprises: displaying an advertisement display page; listening to a page event corresponding to a page control in the advertisement display page; obtaining page change data and a first timestamp of the page control corresponding to the page event; obtaining traffic data corresponding to the advertisement display page, the traffic data at least including a second timestamp corresponding to the first timestamp; generating page playback data according to the page change data and the first timestamp; and sending the page playback data and the traffic data to a playback terminal, the playback terminal being configured to display the page playback data and the traffic data according to the second timestamp. The method can realize real and comprehensive recording of changes of the advertisement display page, restore the advertisement exposure process, and provide strong visual evidence for advertisement traffic inspection.

Description

Technical Field

[0001] This application relates to the field of data management technology, and in particular to a data playback method, apparatus, and storage medium. Background Technology

[0002] Currently, advertising plays an increasingly important role in the internet world. However, along with the revenue generated from traffic comes rampant advertising fraud and manipulation. Such behavior not only causes huge economic losses to advertisers but also seriously damages the healthy development of the internet advertising market.

[0003] Current anti-fraud systems primarily log traffic risks from different dimensions after the traffic has taken effect, using an SDK (Software Development Kit). These logs include IP address, device platform, system parameters, channel, browser environment parameters, display frequency, behavioral parameters, user history, traffic changes, etc. After the reporting is completed, anomaly judgment is performed using a policy model.

[0004] Existing technologies can generally meet routine data analysis needs, but for digital advertising trading systems, once a dispute arises, log records cannot reconstruct the entire process of ad exposure and provide strong visual evidence for verifying ad traffic. Summary of the Invention

[0005] This application provides a data playback method to solve the problem in the prior art that there is no strong visual credentials and the upload failure rate is high after requesting permission from the application client to record video.

[0006] Accordingly, embodiments of this application also provide a data playback device and a storage medium to ensure the implementation and application of the above method.

[0007] To address the aforementioned problems, this application discloses a data playback method, which includes:

[0008] Display an ad display page; the ad display page includes at least one page control;

[0009] Listen for page events corresponding to page controls in the ad display page;

[0010] Get the page change data and first timestamp of the page control corresponding to the page event. The first timestamp is the timestamp corresponding to the page event.

[0011] Obtain the traffic data corresponding to the current ad display page. The traffic data must include at least the second timestamp corresponding to the first timestamp.

[0012] Generate page replay data based on page change data and the first timestamp;

[0013] Page replay data and traffic data are sent to the replay terminal, which displays the page replay data and traffic data according to the second timestamp.

[0014] Optionally, before displaying the ad display page, the following may also be included:

[0015] Parse the external stylesheets and execution scripts of all external links in the ad display page;

[0016] Convert external stylesheets and executable script files linked from external sources into structured data.

[0017] Optionally, display an ad display page, including:

[0018] Send an advertising request;

[0019] Receive advertising data and advertising materials generated based on advertising requests;

[0020] The target advertisement is rendered based on advertising data and advertising materials;

[0021] Displays an ad display page that includes the targeted ad.

[0022] Optionally, before rendering the target ad based on ad data and ad materials, the following may be included:

[0023] Listen for page events on the registration ad display page;

[0024] Page events include page load completion events, root node change events in the page document object model tree, user click events, and page swipe events;

[0025] The root node change event listener of the page document object model tree is triggered after the corresponding page load completion event is detected.

[0026] Optionally, obtain the page change data and first timestamp of the page control corresponding to the page event, including:

[0027] Get the page change data of the page controls corresponding to the page events; the page change data includes: the full page document object model tree, the change data of the page document object model tree, the user click coordinates and the window offset corresponding to the page scrolling events;

[0028] Obtain the timestamps corresponding to page events as the first timestamp, including the timestamp of the page loading completion event, the timestamp of the root node change event in the page document object model tree, the timestamp of the user click event, and the timestamp of the page swipe event.

[0029] Optionally, after obtaining the page change data and first timestamp of the page control corresponding to the page event, the following are included:

[0030] Page replay data is generated based on page change data and the first timestamp; the page replay data includes the initial page snapshot, page incremental snapshot, target click snapshot, and target page swipe snapshot.

[0031] Optionally, page replay data can be generated based on page change data and the first timestamp, including:

[0032] An initial snapshot of the page is generated based on the full page document object model tree, the external style sheets and executable script files of all structured external links in the ad display page, and the page load completion event timestamp;

[0033] Generate incremental snapshots of the page based on the change data of the page document object model tree and the timestamp of the change event of the root node of the page document object model tree;

[0034] Generate a target click snapshot based on the user's click coordinates and the user's click event timestamp;

[0035] Generate a snapshot of the target page based on the window offset corresponding to the page swipe event and the page swipe event timestamp.

[0036] Optionally, the method also includes:

[0037] The system detects whether the corresponding page playback data displayed on the playback terminal complies with the anti-fraud rules of the ad display page based on the traffic data displayed on the playback terminal. If the page playback data corresponding to the traffic does not comply with the anti-fraud rules, it is determined that there is abnormal traffic on the ad display page.

[0038] This application also discloses a data playback device, the device comprising:

[0039] The display module is used to display the advertisement display page; the advertisement display page includes at least one page control;

[0040] The listening module is used to listen for page events corresponding to page controls in the ad display page;

[0041] The first acquisition module is used to acquire the page change data and the first timestamp of the page control corresponding to the page event. The first timestamp is the timestamp corresponding to the page event.

[0042] The second acquisition module is used to acquire traffic data corresponding to the current ad display page. The traffic data includes at least the second timestamp corresponding to the first timestamp.

[0043] The generation module is used to generate page replay data based on page change data and corresponding timestamps.

[0044] The playback module is used to send page playback data and traffic data to the playback terminal, which is used to display the page playback data and traffic data according to the second timestamp.

[0045] This application also discloses one or more machine-readable media storing executable code thereon, which, when executed, causes a processor to perform one or more data playback methods as described in this application.

[0046] Compared with the prior art, the embodiments of this application have the following advantages:

[0047] In this embodiment, by displaying an advertisement display page, listening to page events corresponding to page controls on the advertisement display page, and obtaining page change data and a first timestamp for the page controls corresponding to the page events, traffic data corresponding to the current advertisement display page is obtained. The traffic data includes at least a second timestamp corresponding to the first timestamp. Page playback data is generated based on the page change data and the first timestamp, and then the page playback data and traffic data are sent to a playback terminal. The playback terminal displays the page playback data and traffic data according to the second timestamp. This achieves a true and comprehensive recording of changes to the advertisement display page, reconstructs the advertisement exposure process, and provides strong visual evidence for advertisement traffic verification. Attached Figure Description

[0048] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0049] Figure 1 This is a flowchart illustrating the steps of an embodiment of a data playback method according to this application;

[0050] Figure 2 This is a structural block diagram of an embodiment of a data playback device according to this application;

[0051] Figure 3 This is a schematic diagram of the structure of a data playback device according to this application;

[0052] Figure 4 This is a network scene diagram of a data playback method according to this application. Detailed Implementation

[0053] To make the above-mentioned objectives, features, and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0054] Reference Figure 1 This is a flowchart illustrating the steps of an embodiment of a data playback method according to this application, including the following steps:

[0055] Step 101: Display the advertisement display page.

[0056] The advertising display page includes at least one page control. When a user is detected accessing the page via a terminal, the advertising display page is shown to the client. Page access can be performed by the client through a media client, browser, or webview on the terminal; this application does not impose specific limitations.

[0057] Step 102: Listen for page events corresponding to the page controls in the advertisement display page.

[0058] Page controls are the UI elements in an ad display page used for user interaction, such as button controls, scrollbar controls, input box controls, selection box controls, form controls, and webbrowser controls. Page events are various events that occur during user interaction with a webpage. These events can be user actions or behaviors of the webpage itself, such as clicking a button, scrolling the page, entering text, selecting options, and loading completion.

[0059] Step 103: Obtain the page change data and first timestamp of the page control corresponding to the page event.

[0060] The first timestamp is the timestamp corresponding to the page event. Page change data refers to data on the webpage that can be updated and changed in real time; this can be data on changes in page structure or data on changes in user behavior.

[0061] Step 104: Obtain the traffic data corresponding to the current advertisement display page.

[0062] Traffic data includes at least a second timestamp corresponding to the first timestamp. A single visit by a user to an ad display page can be counted as one traffic instance. Traffic data can indicate the number of users visiting the ad display page within a certain period, page views, visit duration, bounce rate, and other data, which can be further used for ad traffic evaluation.

[0063] Step 105: Generate page replay data based on the page change data and the first timestamp.

[0064] Among them, the page replay data can record all page changes of the ad display page within a certain period of time, including changes in the page structure and various user operations, and supports replaying these processes at any time.

[0065] Step 106: Send the page replay data and traffic data to the replay terminal, which is used to display the page replay data and traffic data according to the second timestamp.

[0066] The playback terminal can be a computer, smartphone, tablet, smart TV, or other device with a display function.

[0067] This application embodiment achieves the following through the above steps: when a user visits a page, an advertisement display page is shown to the user. By listening to page events corresponding to page controls in the advertisement display page, the page change data of the page controls corresponding to the page events and the first timestamp corresponding to the page events are obtained. Page playback data is then generated based on the page change data and the first timestamp, thus achieving a true and comprehensive record of the changes in the advertisement display page and restoring the complete process of advertisement exposure. Here, one display of the target advertisement on the user's terminal is called one advertisement exposure. The target advertisement in... Figure 4 The ad placements shown are displayed on user terminals, such as ad placements on pages visited by users or ad placements in applications used by users. Then, traffic data corresponding to the current ad display page is obtained. This traffic data can include impressions, clicks, etc., during the ad display process. The data must include at least a second timestamp corresponding to the first timestamp. Finally, the traffic data and page playback data are sent to the playback terminal for display according to the second timestamp. This provides strong visual evidence for ad traffic verification, enabling better judgment of whether abnormal traffic exists during the ad process and improving the accuracy of anti-fraud detection.

[0068] Optionally, in one embodiment of this application, before displaying the advertisement display page, the following may be included:

[0069] Parse the external stylesheets and execution script files of all external links in the advertisement display page;

[0070] Convert the external stylesheets and execution script files of the external links into structured data.

[0071] In this embodiment, the advertising SDK can begin working when a user visits a page, parsing the external style sheets and execution script files of all external links on the current ad display page and converting them into structured data stored in the local cache. The advertising SDK can be a set of tools for media outlets to access advertising platforms and execute business logic such as advertising-related actions. In this application, it primarily uses the SDK to request advertising data and materials, collect some user and environmental data, and send it to the server. External links are links to external resources required for page rendering and can be used to load the necessary external resources for page rendering. External style sheets can be used to manage the appearance and style of the entire webpage. Execution script files can be used to implement dynamic functions of the webpage. Converting all external style sheets and execution script files of external links on the ad display page into structured data facilitates subsequent caching and retrieval.

[0072] Optionally, in one embodiment of this application, displaying an advertisement display page may include:

[0073] Send an advertising request;

[0074] Receive advertising data and advertising materials generated based on the advertising request;

[0075] The target advertisement is rendered based on the advertising data and advertising materials;

[0076] Displays an ad display page that includes the targeted ad.

[0077] An ad request is a request sent by a user through a web browser or other device, containing corresponding request parameters, aimed at obtaining and displaying specific advertising content. Request parameters may include ad placement information, user identifiers, platform parameters, and other environmental parameters. After the user-side ad SDK sends an ad request to the ad platform, the ad platform returns specific ad data and ad materials to the client based on the request parameters. Upon receiving the request, the ad SDK first parses the ad data, then uses the ad data to render the ad materials to obtain the target ad, and finally displays the ad display page containing the target ad to the user. The ad data contains ad rendering logic, which can be used to optimize ad display effects and improve ad click-through rates and conversion rates. Ad materials can refer to media files required for actual presentation on a webpage, including but not limited to audio, video, images, and text. Figure 4 As shown, the advertising display page can contain preset advertising slots, and the target advertisement is displayed in these slots. In this embodiment, by generating advertisements that match user interests based on advertising requests and displaying them to users on the advertising display page, precise targeting of advertising content can be achieved, improving advertising exposure.

[0078] Optionally, in one embodiment of this application, before rendering the target advertisement based on the advertising data and advertising materials, the following may be included:

[0079] Register a page event listener for the aforementioned ad display page;

[0080] The page events include page load completion events, root node change events in the page document object model tree, user click events, and page swipe events;

[0081] The root node change event listener of the page document object model tree is triggered after the corresponding page load completion event is detected.

[0082] In this embodiment, listeners can be registered for corresponding page events before ad rendering. During ad exposure, these listeners are invoked when the corresponding events occur, monitoring page events on the ad display page and obtaining corresponding monitoring data as interaction data records. These page events can be structural change events on the ad display page and / or user behavior events. The page load completion event is triggered when all resources are fully loaded during webpage loading. Detecting the page load completion event triggers subsequent root node change detection in the Document Object Model Tree (DOM). The DOM is a tree-like structure created by the browser based on the document returned by the webpage request, describing the document structure. Changes in the DOM affect the displayed content and display method of the page. The root node of the DOM is also called the document node, which identifies the entire document. Root node change events in the DOM can include the addition, deletion, replacement, and modification of child nodes and attributes. User click events can be mouse clicks or touch clicks. Page swipe events correspond to the user swiping within the browser or client window.

[0083] Optionally, in one embodiment of this application, obtaining the page change data and first timestamp of the page control corresponding to the page event may include:

[0084] Obtain the page change data corresponding to the page control of the page event; the page change data includes: the full page document object model tree, the change data of the page document object model tree, the user click coordinates and the window offset corresponding to the page scrolling event;

[0085] The timestamps corresponding to the page events are obtained as the first timestamps, including the timestamp of the page loading completion event, the timestamp of the root node change event of the page document object model tree, the timestamp of the user click event, and the timestamp of the page swipe event.

[0086] In this embodiment, after registering the listener, different listeners can trigger callback events to obtain interaction data corresponding to different events. The page change data can be data on changes in the page's structure or data on changes caused by user-related behaviors. For example, after listening to the page loading completion event of the ad display page, the corresponding full page document object model tree can be obtained, and then the root node change event listener of the page document object model tree can be triggered. When changes such as additions, deletions, replacements, or modifications to child nodes and attributes of the page document object model tree are detected, the corresponding change data of the page document object model tree can be obtained. When a user click event is detected on the ad display page, the corresponding click coordinates can be recorded. When a page swipe event is detected on the ad display page, the corresponding window offset can be recorded. Simultaneously, the timestamps corresponding to the occurrence of various page events can be obtained as the first timestamp, including the page loading completion event timestamp, the root node change event timestamp of the page document object model tree, the user click event timestamp, and the page swipe event timestamp. Through the above steps, user operations and page structure change data during ad exposure can be recorded accurately and comprehensively.

[0087] The monitoring and acquisition of changes to the page's Document Object Model (DOM) tree can be achieved using the browser's MutationObserver interface. This interface provides the ability to monitor changes made to the DOM tree. Changes such as node additions / removals, attribute changes, and node content changes are all collected by MutationObserver. Furthermore, the MutationObserver's callback function executes asynchronously. After a browser time slice completes, the interface creates an array of all DOM changes recorded within that time slice, with each item in the array representing an independent DOM change. When the ad SDK embedded in the user's terminal's ad display page retrieves ad data from the ad platform, it uses the current page's root node as the DOM object to be observed by MutationObserver, and then executes the ad rendering logic. After the DOM tree changes due to rendering, the SDK retrieves the changed data array, i.e., the changes to the page's Document Object Model (DOM tree), from the MutationObserver interface's callback function.

[0088] Optionally, in one embodiment of this application, after obtaining the page change data and the first timestamp of the page control corresponding to the page event, the following may be included:

[0089] Page replay data is generated based on the page change data and the first timestamp; the page replay data includes the initial page snapshot, the incremental page snapshot, the target click snapshot, and the target page swipe snapshot.

[0090] Generating page change data as snapshots allows for a comprehensive and complete preservation of the page's changes. This data can be used to reconstruct the ad display page's changes over a specific period when needed. Furthermore, the reconstructed ad display page changes can be used as the target ad's exposure process for ad traffic auditing and analysis.

[0091] Optionally, in one embodiment of this application, generating page playback data based on the page change data and the first timestamp may include:

[0092] The initial snapshot of the page is generated based on the full page document object model tree, the external style sheets and execution script files of all structured external links in the ad display page, and the page load completion event timestamp;

[0093] The incremental snapshot of the page is generated based on the change data of the page document object model tree and the timestamp of the root node change event of the page document object model tree;

[0094] Generate the target click snapshot based on the user click coordinates and the user click event timestamp;

[0095] Generate the target page sliding snapshot based on the window offset corresponding to the page sliding event and the page sliding event timestamp.

[0096] In this embodiment, after the advertisement rendering is completed and the advertisement is displayed on the user's advertisement display page, page change data can be obtained by listening to the page events corresponding to the page controls in the advertisement display page, and page playback data can be generated based on the page change data and the corresponding first timestamp.

[0097] For example, an initial snapshot of the page can be generated based on the full document object model tree of the current ad display page, along with the external stylesheets and executable script files of all structured external links in the corresponding ad display page that were previously cached, the page load completion event timestamp, user identifier, and other environmental information. The snapshot ID is then initialized to 0. The generated initial snapshot is then stored in the data cache.

[0098] For example, an incremental snapshot of the page can be generated based on the change data of the current ad display page's Document Object Model (DOM) tree, plus the timestamp of the root node change event in the DOM tree, the user identifier, and other environmental information. An auto-incrementing ID can be set for each incremental snapshot. The generated incremental snapshot is then stored in a data cache. The auto-incrementing ID can start from 1 and increment incrementally, with the value automatically increasing each time a new incremental snapshot record is added. Environmental information may include the user's device's physical information, operating system, browser type, whether touch is used, and whether the device's position or angle has changed.

[0099] For example, a target click snapshot can be generated based on the user's click coordinates, along with the user's click event timestamp, user identifier, auto-incrementing ID, and other environmental information. The generated target click snapshot is then stored in a data cache.

[0100] For example, a target page swipe snapshot can be generated based on the window offset corresponding to the page swipe event, along with the page swipe event timestamp, user identifier, auto-incrementing ID, and other environmental information. The generated target page swipe snapshot is then stored in a data cache.

[0101] By adding corresponding timestamps and auto-incrementing IDs to the page change data through the above steps, the continuity of data records can be guaranteed. After generating the page replay data, it is first cached to ensure that the data is not lost during the upload process.

[0102] Figure 4 This is a network scenario diagram of a data playback method according to this application. Optionally, in one embodiment of this application, the page playback data and traffic data are sent to a playback terminal. The playback terminal is used to display the page playback data and traffic data according to the second timestamp, and may include:

[0103] Within a suitable system timeframe, the page replay data and traffic data stored in the data cache are serialized, encrypted, and sent to the storage server. This suitable system time can be system idle time, a lifecycle, or a user-defined preset time. If data transmission fails within the current timeframe, it can be retained for retransmission in the next cycle, ensuring no data loss during upload. When receiving data, the storage server verifies the continuity between the current data and the previously reported data; if continuous, it returns a correct response. Simultaneously, it decrypts and deserializes the received serialized and encrypted data to obtain the page replay data corresponding to the user's ad display page and the traffic data for the corresponding time period. The page replay data and corresponding traffic data are then sorted according to a second timestamp to ensure data integrity before being stored on the storage server. The page replay data can also be sorted using an auto-incrementing ID. (See reference...) Figure 4The user terminal device, after acquiring page playback data and traffic data, can send them to a storage server for storage via a communication network at a preset time. The user terminal can be a mobile phone, such as user terminal device 1, or a computer, such as user terminal device 2. The storage server can receive the page playback data and traffic data sent by the user terminal device. Upon receiving a playback instruction, it sends the corresponding page playback data and traffic data to the playback terminal device. The playback terminal device, upon receiving a playback instruction, sends the instruction to the storage server, retrieves the page playback data and traffic data sent by the storage server, and displays it according to a second timestamp. These steps ensure the continuity of page playback data, preventing loss or duplication during transmission, achieving a true and comprehensive record of changes in the ad display page, reconstructing the exposure process of the target ad, and providing strong visual evidence for ad traffic verification.

[0104] Optionally, in one embodiment of this application, the method may include:

[0105] Once the target ad has finished rendering and meets the target exposure threshold, release the page event listeners for the current ad display page. This includes releasing the listeners for changes to the root node of the page's document object model tree, user click events, and page swipe events.

[0106] Target exposure metrics can include the number of clicks, exposure time, or the percentage of the window occupied by the target ad. Target exposure metric thresholds are preset values ​​that advertisers aim to achieve based on actual circumstances. Correspondingly, these can be confirmed by tracking the number of clicks, exposure time, and checking the completeness and window percentage of the target ad's display.

[0107] Optionally, in one embodiment of this application, the method may further include:

[0108] The system detects whether the page playback data corresponding to the traffic data displayed by the playback terminal conforms to the anti-fraud rules of the ad display page. If the page playback data corresponding to the traffic does not conform to the anti-fraud rules, it is determined that there is abnormal traffic on the ad display page.

[0109] The anti-fraud rules for ad display pages refer to ad traffic anti-fraud rules that can be used to identify and verify various fraudulent behaviors and filter invalid traffic. Common fraudulent behaviors include repeated IP traffic boosting, traffic hijacking, click fraud, and installation fraud. These fraudulent behaviors can simulate user behavior through technical means to generate a large amount of invalid traffic. After sending page replay data and traffic data to the replay terminal, it is possible to detect whether the page replay data corresponding to the traffic data complies with the anti-fraud rules for ad display pages. If the page replay data corresponding to a certain traffic does not comply with the anti-fraud rules, it can be determined that there is abnormal traffic to the ad display page in this traffic. In this embodiment, after sampling to detect the completeness and interaction rationality of the page replay data, it is possible to determine whether the exposure of the target ad in this traffic complies with the anti-fraud rules for ad display pages based on the reconstructed loading, rendering, and exposure process of the target ad in this traffic. For example, it can be determined by detecting whether there are abnormally high click counts from the same user-identified device in the page replay data within a short period of time, whether the environmental information in the page replay data matches the user's daily attributes, or whether the page replay data corresponding to a certain exposure matches human operation characteristics. The anti-fraud rules for ad display pages may include user behavior feature rules, user device feature rules, etc.

[0110] In another example, ad traffic analysis and auditing can be performed based on stored page replay data and traffic data, using different strategies for traffic verification. For instance, during an audit based on existing anti-fraud rules, if a target ad is determined to be close to a rule threshold, the complete exposure process of the target ad on the ad display page can be reconstructed using page replay data and traffic data to conduct a secondary determination of whether abnormal traffic exists. In advertising platforms, anti-fraud policy detection rules are typically used to detect and prevent fraudulent traffic, order manipulation, and other behaviors, ensuring the platform's fairness and data authenticity. Determining that a target ad is close to an anti-fraud rule threshold means that certain user behaviors or data are approaching the threshold for being judged as abnormal or fraudulent by the system. Reconstructing the complete exposure process of the target ad at this point can improve the accuracy of fraudulent behavior identification.

[0111] Additionally, traffic analysis can be performed by checking whether page replay data matches the corresponding traffic data. If there is a mismatch between page replay data and corresponding traffic data within a certain time period, it can be determined that there is abnormal traffic on the ad display page. For example, it can be determined whether the effective exposure of the target ad within a certain period matches the number of user clicks within the corresponding time period in the page replay data. This achieves a true and comprehensive recording of changes in the ad display page, reconstructs the ad exposure process, and provides strong visual evidence for ad traffic verification.

[0112] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of this application are not limited to the described order of actions, because according to the embodiments of this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of this application.

[0113] Based on the above embodiments, this embodiment also provides a data playback device, which is applied in electronic devices such as terminal devices and servers.

[0114] Reference Figure 2 The diagram shows a structural block diagram of an embodiment of a data playback device according to this application, which may specifically include the following modules:

[0115] Display module 201 is used to display an advertisement display page; the advertisement display page includes at least one page control;

[0116] The listening module 202 is used to listen to page events corresponding to the page controls in the advertisement display page;

[0117] The first acquisition module 203 is used to acquire page change data and a first timestamp of the page control corresponding to the page event, wherein the first timestamp is the timestamp corresponding to the page event;

[0118] The second acquisition module 204 is used to acquire traffic data corresponding to the current advertising display page, wherein the traffic data includes at least a second timestamp corresponding to the first timestamp;

[0119] The generation module 205 is used to generate page replay data based on the page change data and the corresponding timestamp;

[0120] The playback module 206 is used to send the page playback data and traffic data to the playback terminal, and the playback terminal is used to display the page playback data and traffic data according to the second timestamp.

[0121] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0122] This application provides a data playback device that displays an advertisement page to the user when a user visits a page. By listening to page events corresponding to page controls on the advertisement page, it obtains page change data for the corresponding page controls and a first timestamp for each page event. Based on the page change data and the first timestamp, it generates page playback data, thus comprehensively recording the changes to the advertisement page and restoring the complete exposure process of the advertisement. It then acquires traffic data corresponding to the current advertisement page, including impressions, clicks, etc., during the advertisement page display process. The data includes at least a second timestamp corresponding to the first timestamp. Finally, the traffic data and page playback data are sent to a playback terminal for display according to the second timestamp. This provides strong visual evidence for advertisement traffic verification, enabling better judgment of whether abnormal traffic exists during the advertisement process and improving the accuracy of anti-fraud detection.

[0123] Figure 3 This is a schematic diagram illustrating the structure of a data playback device according to an exemplary embodiment. (Refer to...) Figure 3 The client / web page 301 may include an advertising SDK 311. The advertising SDK 311 may include an advertising request module 3111, a page snapshot recording module 3112, and a data upload module 3113. The auditing terminal 302 may include a playback interface 312. The playback interface 312 may include a playback module 3121.

[0124] The advertising request module 3111 can send advertising requests to the advertising platform server 303. The advertising platform server 303 returns the corresponding advertising data and advertising materials to the advertising request module 3111 based on the received advertising requests. The advertising SDK 311 renders the target advertisement based on the returned advertising data and advertising materials, and displays the target advertisement on the client / web page 301.

[0125] After the target advertisement is displayed, the page snapshot recording module 3112 can listen to page events on the advertisement display page on the client / webpage 301 to obtain corresponding page change data and traffic data, and combine them into a page snapshot. The data upload module 3113 uploads the page snapshot obtained by the page snapshot recording module 3112, i.e., page playback data, and traffic data to the advertising platform log server 304 for caching. The advertising platform log server 304 then uploads the cached page playback data and traffic data to the data storage server 305 at a preset time.

[0126] In the event of a dispute during an advertising transaction or during an advertising traffic audit, the corresponding instruction can be sent through the audit terminal / webpage 302 to enable the playback module 3121 to retrieve the corresponding page playback data and traffic data from the data storage server 305, and then display them in the playback interface 312 on the audit terminal / webpage 302.

[0127] This application also provides a data playback device, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, it implements the data playback method described above.

[0128] This application also provides a non-volatile readable storage medium storing one or more modules (programs). When these modules are applied to a device, they enable the device to execute the instructions for the method steps in this application.

[0129] This application provides one or more machine-readable media storing instructions that, when executed by one or more processors, cause an electronic device to perform one or more of the methods described in the above embodiments. In this application, the electronic device includes various types of devices such as terminal devices and servers (clusters).

[0130] The embodiments of this disclosure can be implemented as an apparatus configured as desired using any suitable hardware, firmware, software, or any combination thereof, including electronic devices such as terminal devices, servers (clusters), etc.

[0131] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0132] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data playback terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data playback terminal device, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0133] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data playback terminal device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0134] These computer program instructions can also be loaded onto a computer or other programmable data playback terminal device, causing a series of operational steps to be performed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0135] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present application.

[0136] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0137] The above provides a detailed description of a data playback method and apparatus, an electronic device, and a storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and its core ideas. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A data playback method characterized by, The method comprises: displaying an advertisement display page; the advertisement display page comprises at least one page control; listening to a page event corresponding to the page control in the advertisement display page; obtaining page change data of the page control corresponding to the page event and a first timestamp; the first timestamp is a timestamp corresponding to the page event; obtaining traffic data corresponding to the current advertisement display page; the traffic data at least comprises a second timestamp corresponding to the first timestamp; generating page playback data according to the page change data and the first timestamp; sending the page playback data and the traffic data to a playback terminal; the playback terminal is used for displaying the page playback data and the traffic data according to the second timestamp; detecting whether the page playback data corresponding to the traffic data conforms to an anti-cheating rule of the advertisement display page according to the traffic data displayed by the playback terminal; if the page playback data corresponding to the traffic does not conform to the anti-cheating rule, it is determined that the advertisement display page has abnormal traffic.

2. The method of claim 1, wherein, Before the advertisement display page is displayed, the method further comprises: parsing external style sheets and execution script files of all external links in the advertisement display page; converting the external style sheets and the execution script files of the external links into structured data.

3. The method of claim 1, wherein, The method of displaying the advertisement display page comprises: sending an advertisement request; receiving advertisement data and advertisement materials generated according to the advertisement request; rendering a target advertisement according to the advertisement data and the advertisement materials; displaying the advertisement display page containing the target advertisement.

4. The method of claim 3, wherein, Before the target advertisement is rendered according to the advertisement data and the advertisement materials, the method comprises: registering a page event listener of the advertisement display page; the page event comprises a page loading completion event, a root node change event of a page document object model tree, a user click event and a page sliding event; the root node change event of the page document object model tree is triggered after the corresponding page loading completion event is listened to.

5. The method of claim 1, wherein, The method of obtaining the page change data of the page control corresponding to the page event and the first timestamp comprises: obtaining the page change data of the page control corresponding to the page event; the page change data comprises a full page document object model tree, change data of a page document object model tree, user click coordinates and window offset corresponding to a page sliding event; obtaining a timestamp corresponding to the page event as the first timestamp, which comprises a page loading completion event timestamp, a root node change event timestamp of a page document object model tree, a user click event timestamp and a page sliding event timestamp.

6. The method of claim 5, wherein, After the page change data of the page control corresponding to the page event and the first timestamp are obtained, the method comprises: generating page playback data according to the page change data and the first timestamp; the page playback data comprises a page initial snapshot, a page incremental snapshot, a target click snapshot and a target page sliding snapshot.

7. The method of claim 6, wherein, The method of generating page playback data according to the page change data and the first timestamp comprises: generating the page initial snapshot according to the full page document object model tree, external stylesheets of all structured external links in the advertisement display page, and executed script files, and the page loading completion event timestamp; generating the page incremental snapshot according to the change data of the page document object model tree and the root node change event timestamp of the page document object model tree; generating the target click snapshot according to the user click coordinates and the user click event timestamp; generating the target page sliding snapshot according to the window offset corresponding to the page sliding event and the page sliding event timestamp.

8. A data playback apparatus characterized by comprising: comprising: a display module configured to display an advertisement display page; the advertisement display page comprising at least one page control; a listening module configured to listen to a page event corresponding to the page control in the advertisement display page; a first obtaining module configured to obtain page change data of the page control corresponding to the page event and a first timestamp; the first timestamp being a timestamp corresponding to the page event; a second obtaining module configured to obtain traffic data corresponding to the current advertisement display page; the traffic data at least comprising a second timestamp corresponding to the first timestamp; a generating module configured to generate page playback data according to the page change data and the corresponding timestamp; a playback module configured to send the page playback data and the traffic data to a playback terminal; the playback terminal being configured to display the page playback data and the traffic data according to the second timestamp; detecting whether the page playback data corresponding to the traffic data conforms to an anti-cheating rule of the advertisement display page according to the traffic data displayed by the playback terminal; if the page playback data corresponding to the traffic does not conform to the anti-cheating rule, determining that there is abnormal traffic in the advertisement display page.

9. A computer-readable storage medium having stored thereon executable code to: when the executable code is executed by a processor, the data playback method as claimed in any one of claims 1-7 is implemented.

Images