Cross-application advertisement behavior and crowd audience information backup method, device and equipment

Abstract

The application relates to a cross-application advertisement behavior and crowd audience information backup method, device and equipment, which comprises the following steps: obtaining an application program with advertisement delivery and a target advertisement playing page; determining a plurality of first target application programs with advertisement behavior and crowd audience information backup demand, and obtaining pixel codes of the first target application program advertisement behavior and crowd audience information backup; determining a to-be-added code application program with cross-application backup authority, and determining second target application programs to be cross-application backed up by the to-be-added code application program; calling pixel codes of the second target application programs and adding the pixel codes into a hypertext transfer protocol of a target advertisement playing page of the to-be-added code application program to obtain a cross-application backup application program; and cross-application backing up advertisement behavior and crowd audience information through the pixel codes of the second target application programs added to the cross-application backup application program. Different application information islands are connected, and advertisement behavior and crowd audience information can be cross-application backed up.

Description

Technical Field

[0001] This disclosure relates to the field of information backup technology, and in particular to a method, apparatus and device for backing up cross-application advertising behavior and audience information. Background Technology

[0002] Pixel is a piece of JavaScript code that allows you to track visitor activity on a website. Pixel collects the following data: HTTP headers, Pixel-specific data, button click data, optional values, and form field names. The HTTP headers are a standard network protocol sent between a browser request and a server on the internet. These headers can contain data such as IP address, information about the web browser, page location, document, source of access, and the user using the website. Pixel-specific data includes the Pixel ID and cookies. Button click data includes any buttons clicked by the website visitor, the labels of those buttons, and any pages visited after clicking the button. Optional values ​​are additional information about the visit sent via custom data events. Custom data events can include, for example, conversion value, page type, etc. Form field names include website field names such as email, address, quantity, etc., applicable to purchasing products or services.

[0003] However, user data generated by each platform only records user behavior through its own Pixel code and sends it to its own data platform, storing it corresponding to the account. This results in user behavior recorded by Pixel codes from different platforms and accounts becoming information silos, with user data not being shared between them. Summary of the Invention

[0004] The purpose of this invention is to provide a method, apparatus, and device for backing up advertising behavior and audience information across applications, aiming to break down information silos between different applications, thereby enabling cross-application backup of advertising behavior and audience information.

[0005] To achieve the above objectives, a first aspect of this disclosure provides a method for backing up advertising behavior and audience information across applications, the method comprising:

[0006] Obtain the application where ads are being displayed, and obtain the target ad playback page in the application used for ad playback;

[0007] From the application, identify multiple first target applications that require backup of advertising behavior and audience information for the advertisement, and obtain pixel code corresponding to each first target application for backup of advertising behavior and audience information for the advertisement;

[0008] From the application, determine the application to be added that has the permission to back up advertising behavior and audience information for the advertisement across applications from the first target application, and determine the second target application from the multiple first target applications that each application to be added can back up advertising behavior and audience information for the advertisement across applications;

[0009] For each of the applications to be added with code, the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement is called and added to the hypertext transfer protocol of the target advertisement playback page of the application to be added with code, thereby obtaining the cross-application backup application;

[0010] In response to an ad playback operation on the target ad playback page of the cross-application backup application, the cross-application backup provides ad behavior and audience information for the ad by adding pixel code of the second target application to the hypertext transfer protocol of the target ad playback page of the cross-application backup application.

[0011] In one possible implementation, for each of the applications to which code is to be added, the pixel code of a second target application that performs cross-application backup of advertising behavior and audience information for the advertisement is invoked and added to the Hypertext Transfer Protocol of the target advertisement playback page of the application to which code is to be added, thereby obtaining cross-application backup applications, including:

[0012] For each of the applications to be added with code, obtain the start and end markers in the Hypertext Transfer Protocol of the target ad playback page of each application to be added with code, which are used to back up the advertising behavior and audience information for the ad.

[0013] The pixel code of the second target application, which performs cross-application backup of advertising behavior and audience information for the advertisement, is invoked. The corresponding pixel code of the second target application is added between the start tag and the end tag in the Hypertext Transfer Protocol of the target advertisement playback page of each application to be added with code, to obtain the cross-application backup application.

[0014] In one possible implementation, the pixel code of the second target application, which is called by the application to be added to back up the advertising behavior and audience information of the advertisement across applications, is added between the start and end tags of the corresponding second target application in the Hypertext Transfer Protocol of the target advertisement playback page of each application to be added to, thereby obtaining the cross-application backup application, including:

[0015] Call the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement, and generate the pixel code software development kit corresponding to the second target application;

[0016] The pixel code software development kit of the second target application is added between the start tag and the end tag in the Hypertext Transfer Protocol of the target advertisement playback page of each application to which code is to be added, to obtain the cross-application backup application.

[0017] In one possible implementation, the step of calling the pixel code of the second target application, which performs cross-application backup of advertising behavior and audience information for the advertisement, and generating a pixel code software development kit corresponding to the second target application, includes:

[0018] Call the pixel code of the second target application, which is the application to be added to perform cross-application backup of advertising behavior and audience information for the advertisement, and generate an XML file;

[0019] The XML file is read into memory using Java code and becomes target data that matches the data structure of the code generation engine of the application to which the code is to be added;

[0020] The target data is passed to the code generation engine to generate the SDK interface code corresponding to the pixel code of the second target application;

[0021] Use Java code to generate the corresponding Ant packaging script from the SDK interface code corresponding to the pixel code of the second target application;

[0022] The ant packaging script is executed by sending instructions through Java code, and the code contained in the SDK architecture of the application to be added is compiled by the ant packaging script to generate the pixel code software development kit corresponding to the second target application. The code contained in the SDK architecture includes the code of the SDK interface part, the protocol layer code, and the data verification layer code.

[0023] In one possible implementation, the ad playback operation in response to the target ad playback page of the cross-application backup application, via pixel code of a second target application added to the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application, includes the following:

[0024] In response to an ad playback operation on the target ad playback page of the cross-application backup application, the pixel code of the second target application added to the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application is executed;

[0025] Download the corresponding function library by adding the pixel code of the second target application in the Hypertext Transfer Protocol of the target ad playback page to the cross-application backup application;

[0026] Each time a user's advertising behavior is loaded in response to the advertisement, the corresponding function library is used to track the advertising behavior, generate an advertising behavior log, and obtain the user account information logged in on the cross-application backup application.

[0027] Based on the tracked advertising behavior logs and user account information, advertising behavior and audience information for the advertisement are generated and backed up across applications.

[0028] In one possible implementation, the step of tracking the advertising behavior using the corresponding function library and generating an advertising behavior log each time a user's advertising behavior for the advertisement is loaded includes:

[0029] Each time a user's advertising behavior towards the advertisement is loaded, the fbq function in the function library is called as the Page View event manager to track the events corresponding to the advertising behavior and generate an advertising behavior log.

[0030] In one possible implementation, the method further includes:

[0031] On the cross-application backup application, the target advertisement is determined based on the advertising behavior and audience information of the advertisement backed up across applications by the cross-application backup application, and the advertising behavior and audience information of the advertisement backed up in the cross-application backup application through the pixel code corresponding to this application but not across applications.

[0032] The target advertisement is played on the target advertisement playback page corresponding to the cross-application backup application.

[0033] A second aspect of this disclosure provides a cross-application advertising behavior and audience information backup device, comprising:

[0034] The acquisition module is configured to acquire applications where advertisements are being displayed, and to acquire the target advertisement playback page in the application used for advertisement playback;

[0035] The first determining module is configured to determine from the application that there are multiple first target applications that require backing up advertising behavior and audience information for the advertisement, and to obtain pixel code corresponding to each first target application for backing up advertising behavior and audience information for the advertisement.

[0036] The second determining module is configured to determine, from the application, a code application to be added that has cross-application permissions to perform advertising behavior and audience information backup for the advertisement in the first target application, and to determine, from the multiple first target applications, a second target application for each of the code applications to be added to perform cross-application advertising behavior and audience information backup for the advertisement.

[0037] The calling and adding module is configured to, for each of the applications to be added to the code application, call the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement, and add it to the hypertext transfer protocol of the target advertisement playback page of the application to be added to the code application, thereby obtaining the cross-application backup application;

[0038] The cross-application backup module is configured to respond to an ad playback operation on the target ad playback page of the cross-application backup application by backing up the ad behavior and audience information for the ad through pixel code of a second target application added to the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application.

[0039] A third aspect of this disclosure provides a computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the steps of the method described in any of the first aspects.

[0040] A fourth aspect of this disclosure provides an electronic device, comprising:

[0041] A memory on which computer programs are stored;

[0042] A processor for executing the computer program in the memory to implement the steps of the method of any one of the first aspects.

[0043] This invention provides a method, apparatus, and device for backing up advertising behavior and audience information across applications. Compared with existing technologies, it has the following advantages:

[0044] The process involves: acquiring the applications where ads are being placed and the target ad playback page; identifying multiple first-target applications that require backup of ad behavior and audience information, and obtaining the pixel code for backing up the ad behavior and audience information of the first-target applications; identifying the application with cross-application backup permissions to be backed up, and identifying the second-target application for cross-application backup of the application to be backed up; adding the pixel code of the second-target application to the hypertext transfer protocol of the target ad playback page of the application to be backed up, thus obtaining the cross-application backup application; and backing up ad behavior and audience information across applications using the pixel code of the second-target application added to the cross-application backup application. This addresses the shortcoming of multiple applications' pixel codes not being able to collect user information interoperably. By embedding multiple pixel codes and backing up the same user behavior in the corresponding applications, a single behavior can be backed up and stored in multiple applications or multiple accounts, enabling cross-application and cross-account backup and sharing of ad behavior and audience information.

[0045] Other features and advantages of this disclosure will be described in detail in the following detailed description section. Attached Figure Description

[0046] The accompanying drawings are provided to further illustrate the present disclosure and form part of the specification. They are used together with the following detailed description to explain the present disclosure, but do not constitute a limitation thereof. In the drawings:

[0047] Figure 1 This is a flowchart illustrating a cross-application advertising behavior and audience information backup method according to an embodiment of the specification.

[0048] Figure 2 This is a block diagram illustrating a cross-application advertising behavior and audience information backup device according to an embodiment of the specification.

[0049] Figure 3 This is a block diagram illustrating another cross-application advertising behavior and audience information backup device according to an embodiment of the specification. Detailed Implementation

[0050] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0051] The specific embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit this disclosure.

[0052] To achieve the above objectives, this disclosure provides a method for backing up advertising behavior and audience information across applications. Figure 1 This is a flowchart illustrating a method for backing up cross-application advertising behavior and audience information according to an embodiment. The method includes:

[0053] In step S11, the application where advertising is being delivered is obtained, and the target advertising playback page in the application for advertising playback is obtained;

[0054] The advertising application is an application software that integrates advertising functionality and can display advertisements. The target ad playback page is a page or area within the application specifically designed for displaying advertisements.

[0055] In this embodiment of the disclosure, applications that are subject to advertising are identified by scanning the application's code, monitoring network requests, or analyzing the application's behavior. For example, it can be checked whether the application sends requests to known advertising servers, or whether the application's interface contains typical advertising elements.

[0056] In this embodiment of the disclosure, after identifying the application containing the advertisement, the next step is to locate the specific ad playback page. This typically involves element analysis of the application's user interface (UI) to identify the area or page where the advertisement is displayed. In some cases, it may also be necessary to identify the URL or API endpoint used to load the advertisement by monitoring the application's network activity. Once the ad playback page is located, relevant information such as the page's URL, detailed information about the ad content, and the duration of the ad display can be extracted and recorded. This data can be used for subsequent ad performance analysis, user behavior research, etc.

[0057] In step S12, from the applications, a plurality of first target applications that require backup of advertising behavior and audience information for the advertisement are determined, and pixel code corresponding to each first target application for backup of advertising behavior and audience information for the advertisement is obtained.

[0058] The first target application is one that needs to track and back up its advertising behavior and audience information. Pixel code is a small piece of code embedded in a webpage or application, typically used to track user behavior, collect data, or trigger certain functions.

[0059] In this embodiment of the disclosure, automated tools can be used to scan a large number of applications in an app store, identify applications containing advertisements, and further locate the ad playback page. The ad playback page of the application can be obtained, and metrics such as ad impressions, click-through rates, and conversion rates can be analyzed to evaluate the effectiveness of the advertising campaign. For example, by obtaining the ad playback page and analyzing user behavior data (such as clicks, scrolling, and dwell time), user perception and reactions to the advertisement can be studied.

[0060] In step S13, from the applications, we determine the application to be added that has the permission to back up advertising behavior and audience information for the advertisement across applications from the first target application, and from the multiple first target applications, we determine the second target application for each of the applications to be added that can back up advertising behavior and audience information for the advertisement across applications.

[0061] The first target application is one that can add tracking code to allow other applications to collect advertising data across applications. The second target application is one that, in a cross-application tracking scenario, adds its own pixel code to other applications to track advertising behavior and back up audience information.

[0062] In this embodiment of the disclosure, backup can be understood as multiple storage backups. Since each application can track and store advertising behavior and audience information across applications from a single application, multiple copies of the same advertising behavior and audience information exist, which can be considered a form of backup.

[0063] In this embodiment of the disclosure, by examining the communication protocols, API calls, or ContentProviders between applications, a second target application is determined for each of the applications to which code is to be added to perform cross-application backups of advertising behavior and audience information for the advertisement.

[0064] In step S14, for each of the applications to be added with code, the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement is called and added to the hypertext transfer protocol of the target advertisement playback page of the application to be added with code, thereby obtaining the cross-application backup application.

[0065] In this embodiment, the extracted pixel code is integrated into the "Application to Add Code" to ensure that the code is triggered when the advertisement is played. The HTTP requests or responses related to the target advertisement playback page in the "Application to Add Code" are modified to embed the pixel code, resulting in a cross-application backup application.

[0066] In this embodiment of the disclosure, the pixel code of a second target application that performs cross-application advertising behavior and audience information backup for the advertisement can be added to the persistent header of the application to which the code is to be added.

[0067] In step S15, in response to the ad playback operation of the target ad playback page of the cross-application backup application, the cross-application backup provides the ad behavior and audience information for the ad by adding the pixel code of the second target application in the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application.

[0068] In this embodiment of the disclosure, an event listener is set in the cross-application backup application, which is triggered when an ad playback operation is performed on the target ad playback page. Upon listening for the ad playback event, user behavior data is collected through previously embedded pixel code, and this data is sent to a designated server for backup and analysis via a network request.

[0069] The method described above obtains the application where advertising is being placed and the target advertising playback page; identifies multiple first target applications that require backup of advertising behavior and audience information, and obtains the pixel code for backing up the advertising behavior and audience information of the first target applications; identifies the application with cross-application backup permissions to be added with code, and identifies the second target application for cross-application backup of the application to be added with code; calls the pixel code of the second target application and adds it to the hypertext transfer protocol of the target advertising playback page of the application to be added with code, thus obtaining the cross-application backup application; and backs up advertising behavior and audience information across applications using the pixel code of the second target application added to the cross-application backup application. This solves the problem that pixel codes from multiple applications cannot be shared to collect user information. By embedding multiple pixel codes and backing up the same user behavior in the corresponding applications, a behavior can be backed up and stored in multiple applications or multiple accounts, enabling cross-application and cross-account backup and sharing of advertising behavior and audience information.

[0070] In one possible implementation, in step S14, for each of the applications to which code is to be added, the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement is called and added to the Hypertext Transfer Protocol of the target advertisement playback page of the application to which code is to be added, thereby obtaining cross-application backup applications including:

[0071] In step S141, for each of the applications to be added with code, the start and end markers of the Hypertext Transfer Protocol of the target advertisement playback page of each application to be added with code are obtained, which are used to back up the advertising behavior and audience information for the advertisement.

[0072] This involves analyzing the Hypertext Transfer Protocol (HTTP) to determine start and end tags, for example, by accessing the HTTP content of a target ad playback page in an application where code is to be added. Within the HTTP content, predefined start and end tags are located. These tags are used to pinpoint ad interactions that need to be monitored.

[0073] For example, suppose there is an application called "AppA" whose target ad playback page contains a specific start tag in its HTTP.<!-- START_PIXEL_CODE --> and end marker<!-- END_PIXEL_CODE --> Identify and locate these markers so that pixel codes can be added between them.

[0074] In step S142, the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement is called. The pixel code of the second target application is added between the start mark and the end mark in the Hypertext Transfer Protocol of the target advertisement playback page of each application to be added with code, thereby obtaining the cross-application backup application.

[0075] In a specific implementation, this may include obtaining pixel codes: obtaining pixel codes from a second target application that backs up advertising behavior and audience information across applications. These pixel codes are typically used to track user behavior and information.

[0076] Inserting Pixel Code: Between the start and end tags obtained in the previous step, insert the pixel code retrieved from the second target application. Continuing with the example of "AppA," a specific pixel code is retrieved from a second target application named "BackupApp." This code is then inserted into the HTTP of the target ad playback page for "AppA," specifically at...<!-- START_PIXEL_CODE --> and<!-- END_PIXEL_CODE --> Between the two markers.

[0077] Following the steps described above, each application to which code is to be added embeds pixel code from the second target application in the HTTP of its target ad playback page. This way, when a user views these ads, the pixel code is triggered, enabling cross-application backup of ad behavior and audience information. Continuing with the previous example, "AppA" and all other applications processed in this way will be able to track and back up this information via the "BackupApp" pixel code as users interact with their ads.

[0078] The above technical solution places the code within the `<script>` tag, which reduces the likelihood that browsers or third-party applications will block the execution of Pixel code that is not part of the application. Furthermore, it allows for faster code execution, thereby increasing the likelihood that visitors will be tracked before leaving the page.

[0079] In one possible implementation, in step S142, the pixel code of the second target application, which is called to perform cross-application backup of advertising behavior and audience information for the advertisement, is added between the start and end tags in the Hypertext Transfer Protocol of the target advertisement playback page of each application to be backed up, to obtain the cross-application backup application, including:

[0080] In step S1421, the pixel code of the second target application for which the code to be added is called to back up the advertising behavior and audience information of the advertisement across applications, and the pixel code software development kit corresponding to the second target application is generated.

[0081] In this embodiment of the disclosure, calling the pixel code involves: First, obtaining the pixel code used for backing up advertising activities and audience information from the second target application. Then, encapsulating this pixel code into a software development kit (SDK) facilitates integration and use across multiple applications, while providing better maintainability and scalability.

[0082] For example, suppose there's a second-target application called "AnalyticsApp" that provides ad tracking and audience analytics. The relevant pixel code is extracted from "AnalyticsApp" and packaged into an SDK named "AnalyticsSDK". This SDK can be easily integrated into other applications to achieve ad behavior tracking and information backup capabilities.

[0083] In step S1422, the pixel code software development kit of the second target application is added between the start mark and the end mark in the Hypertext Transfer Protocol of the target advertisement playback page of each application to which code is to be added, to obtain the cross-application backup application.

[0084] In this embodiment of the disclosure, the positioning markers are: in the Hypertext Transfer Protocol (HTTP) of the target advertisement playback page of each application to which code is to be added, preset start and end markers are found.

[0085] Insert SDK: Insert “AnalyticsSDK” generated in step S1421 between the start mark and the end mark.

[0086] Using the above example, suppose there is an application "AdPlayerApp" for which code needs to be added, and its target ad playback page contains a specific start tag in the HTTP.<!-- PIXEL_CODE_START --> and end marker<!-- PIXEL_CODE_END --> An "AnalyticsSDK" will be inserted between these tags. This way, whenever the "AdPlayerApp" ad playback page loads, the "AnalyticsSDK" will be triggered, thus beginning to track and back up ad behavior and audience information.

[0087] After completing the above steps, you will have a cross-application backup application. This application can share ad behavior and audience information across multiple applications, providing advertisers with more comprehensive data analysis and optimization suggestions. For example, "AdPlayerApp" and other applications integrated with "AnalyticsSDK" will be able to share and analyze ad behavior and audience data. This helps advertisers understand ad performance more accurately, optimize ad placement strategies, and improve ROI. Meanwhile, "AnalyticsApp," as a secondary target application, can also enhance its own value and influence by providing these data services.

[0088] In one possible implementation, in step S1421, the pixel code of the second target application, which is called by the application to be added to perform cross-application backup of advertising behavior and audience information for the advertisement, is used to generate a pixel code software development kit corresponding to the second target application, including:

[0089] Call the pixel code of the second target application, which is the application to be added to perform cross-application backup of advertising behavior and audience information for the advertisement, and generate an XML file;

[0090] First, the pixel code of the second target application needs to be retrieved, and an XML file needs to be generated based on this code. This XML file will contain relevant information about the pixel code, such as code snippets and trigger conditions. Assume there is a second target application called "TrackingApp" that is responsible for tracking advertising behavior across applications. First, the pixel code is extracted from this application, and its relevant information is compiled into an XML file named "tracking_pixel_code.xml".

[0091] The XML file is read into memory using Java code and becomes target data that matches the data structure of the code generation engine of the application to which the code is to be added;

[0092] Next, Java code reads the XML file generated in the previous step and loads its contents into memory. This data is then transformed into a data structure compatible with the code generation engine of the application to which the code is to be added; we call this the target data. A Java XML parsing library, such as DOM or SAX, is used to read the "tracking_pixel_code.xml" file. After parsing, the data in the XML is converted into a data structure that the application to which the code is to be added can understand, such as a specific object or data model.

[0093] The target data is passed to the code generation engine to generate the SDK interface code corresponding to the pixel code of the second target application;

[0094] The transformed target data is passed to the code generation engine. This engine then generates SDK interface code corresponding to the pixel code of the second target application. This interface code defines the SDK's main functions and interaction methods. The code generation engine receives the transformed target data and automatically generates the interface code for "TrackingAppSDK" based on it. These interfaces may include methods for initializing the SDK, sending tracking events, etc.

[0095] Use Java code to generate the corresponding Ant packaging script from the SDK interface code corresponding to the pixel code of the second target application;

[0096] This script uses Java code to generate an Ant build script based on the SDK interface code. Ant is a popular Java build tool used to automate tasks such as compilation and packaging. This script will be used in the subsequent SDK compilation and packaging process. Write Java code to automatically generate an Ant script named "build_sdk.xml". This script defines how to compile the SDK source code, how to package the compiled class files into a distributable JAR file, and other tasks.

[0097] The ant packaging script is executed by sending instructions through Java code, and the code contained in the SDK architecture of the application to be added is compiled by the ant packaging script to generate the pixel code software development kit corresponding to the second target application. The code contained in the SDK architecture includes the code of the SDK interface part, the protocol layer code, and the data verification layer code.

[0098] Finally, the Ant packaging script generated in the previous step is run via Java code. This script is responsible for compiling all the code included in the SDK architecture (including the SDK interface code, protocol layer code, and data validation layer code), and ultimately generating the pixel code software development kit (SDK) for the second target application. The "build_sdk.xml" script is executed using Java's `Runtime.exec()` method. After the script runs, it automatically compiles and packages all necessary code, ultimately generating a software development kit named "TrackingAppSDK.jar". This SDK can be integrated with other applications to achieve the tracking and backup of advertising behavior and audience information.

[0099] In one possible implementation, in step S15, the ad playback operation in response to the target ad playback page of the cross-application backup application, via pixel code of the second target application added to the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application, includes the following:

[0100] In step S151, in response to an ad playback operation on the target ad playback page of the cross-application backup application, pixel code of the second target application added to the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application is executed.

[0101] In this embodiment of the disclosure, when the target ad playback page of the cross-application backup application performs an ad playback operation, the pixel code of the second target application embedded in the HTTP is triggered and executed. Assuming a user visits an ad page of a "cross-application ad player" that integrates pixel code, when the page starts playing an ad, the "AnalyticsPixelCode" embedded in the HTTP will automatically run.

[0102] In step S152, the corresponding function library is downloaded by adding the pixel code of the second target application in the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application;

[0103] After the pixel code is executed, it will download the corresponding function libraries as needed. These function libraries typically contain functions and methods for tracking, recording, and analyzing advertising behavior and user information. After “AnalyticsPixelCode” runs, it will automatically download the necessary tracking and analysis function libraries from “AnalyticsServer”, such as “TrackingLib.js”.

[0104] In step S153, each time a user's advertising behavior towards the advertisement is loaded, the corresponding function library is used to track the advertising behavior, generate an advertising behavior log, and obtain the user account information logged in on the cross-application backup application.

[0105] In this embodiment of the disclosure, whenever a user performs a certain action (such as clicking, watching, or lingering) on ​​an advertisement, functions from the downloaded function library are used to track these actions and record them as an advertisement behavior log. Simultaneously, user account information logged into the cross-application backup application is also obtained. For example, when a user clicks or watches an advertisement on the "Cross-application Ad Player," "TrackingLib.js" is invoked to track and record these actions, such as "User A watched Ad B for 30 seconds," and this information is stored as an advertisement behavior log. If the user is logged in, their account information is also recorded.

[0106] In step S154, based on the tracked advertising behavior logs and the user account information, advertising behavior and audience information for the advertisement are generated and backed up across applications.

[0107] In this embodiment of the disclosure, based on the tracked advertising behavior logs and user account information, the system generates detailed information about advertising behavior and audience demographics, and backs up this information across applications to a second target application or a related data analytics platform. For example, the collected advertising behavior logs and user account information are sent across applications to "AnalyticsServer". On the server, this information is further analyzed and processed to generate detailed reports on ad viewing time, user interaction, audience characteristics, etc., and stored in a database for use by advertisers and analysts.

[0108] This allows for a more comprehensive understanding of how ads perform in different applications and how different audiences react, thereby optimizing advertising strategies and improving advertising effectiveness.

[0109] In one possible implementation, step S153, which involves tracking the advertising behavior using the corresponding function library and generating an advertising behavior log each time a user's advertising behavior for the advertisement is loaded, includes:

[0110] Each time a user's advertising behavior towards the advertisement is loaded, the fbq function in the function library is called as the Page View event manager to track the events corresponding to the advertising behavior and generate an advertising behavior log.

[0111] In this embodiment of the disclosure, when a user triggers an advertising action (such as clicking an ad, watching an ad video, etc.) in a cross-application backup application, the system calls a specific function from a pre-downloaded function library to track these actions. In this example, the fbq function in the function library is used as a Page View event manager, responsible for tracking events corresponding to advertising actions and recording these events as an advertising action log.

[0112] Calling the fbq function: Whenever a user performs an action related to an advertisement, such as loading an advertisement page or clicking an advertisement link, the system will automatically call the fbq function.

[0113] Event tracking: The fbq function records detailed information about advertising behavior, such as behavior type (click, view, etc.), behavior time, and advertising content, and tracks this information as event data.

[0114] Generate advertising behavior logs: The tracked event data will be compiled into advertising behavior logs, which can be used for subsequent data analysis and report generation.

[0115] For example, suppose there's an online shopping platform that integrates advertising into its mobile application and uses the cross-application backup technology mentioned above to track and analyze ad performance. User behavior triggers: When a user browses products on the platform, relevant ads are displayed. Clicking on an ad or watching an ad video triggers the ad tracking mechanism. fbq function call: Simultaneously with the user's ad-related action, the system automatically calls the fbq function in the function library. This function acts as a Page View event manager, starting to track the user's ad behavior. Event data logging: The fbq function records detailed aspects of the user's ad behavior, such as which ad was clicked, the click time, and the ad's display duration. Log generation and storage: The tracked event data is compiled into ad behavior logs and stored in the platform's database. These logs can be used for subsequent ad performance analysis, helping the platform optimize ad delivery strategies and improve ad conversion rates.

[0116] This allows for the acquisition of detailed data on user advertising behavior, leading to a better understanding of user interests and needs, optimized ad delivery, and improved user experience and ad effectiveness.

[0117] In one possible implementation, the method further includes:

[0118] On the cross-application backup application, the target advertisement is determined based on the advertising behavior and audience information of the advertisement backed up across applications by the cross-application backup application, and the advertising behavior and audience information of the advertisement backed up in the cross-application backup application through the pixel code corresponding to this application but not across applications.

[0119] A cross-application backup application is software capable of backing up data across different applications. In this scenario, it specifically refers to an application that can back up advertising behavior and audience information. Pixel code is a small piece of code embedded in a webpage or application, typically used to track user behavior, collect data, or trigger specific functions. In advertising technology, pixel code is often used to track events such as ad impressions and clicks. Advertising behavior and audience information: This refers to data on user interactions with ads (such as clicks, viewing time, etc.) and information about the user group (such as age, gender, interests, etc.). Targeted advertising: Based on collected user behavior and data analysis, determining which ads to show to specific users.

[0120] In this embodiment of the disclosure, the cross-application backup application collects two parts of data: one part is advertising behavior and audience information backed up across applications, and the other part is information from non-cross-application backups via pixel code within this application. This data is analyzed, for example through machine learning algorithms or user profiling matching, to determine the most suitable advertisements to show to specific users, i.e., targeted advertisements.

[0121] For example, suppose a user frequently browses content in fitness apps and searches for sports equipment in shopping apps. A cross-app backup application collects this information and combines it with the user's browsing and search history within the shopping app (collected through the app's pixel code). Based on this data, the system determines that the user is interested in sports equipment and selects a sneaker ad as the target advertisement.

[0122] The target advertisement is played on the target advertisement playback page corresponding to the cross-application backup application.

[0123] In this embodiment of the disclosure, a target advertisement is identified, and the cross-application backup application displays this advertisement on its target advertisement playback page. This typically involves loading, rendering, and playing the advertisement content to ensure that the advertisement is presented to the user in the best possible way. Continuing the example above, when a user opens the shopping app and browses to a certain page, the cross-application backup application plays the previously identified sneaker advertisement in the advertisement slot on that page. In this way, the advertisement content is highly relevant to the user's interests, improving the advertisement conversion rate and user satisfaction.

[0124] In this way, cross-application backup applications can effectively utilize cross-application and in-application data to provide users with more personalized and precise advertising content.

[0125] This disclosure also provides a cross-application advertising behavior and audience information backup device, see [link to relevant documentation]. Figure 2 As shown, it includes:

[0126] The acquisition module 210 is configured to acquire an application where advertising is being delivered, and to acquire the target advertising playback page in the application used for advertising playback;

[0127] The first determining module 220 is configured to determine from the application that there are multiple first target applications that require backing up advertising behavior and audience information for the advertisement, and to obtain the pixel code corresponding to each first target application for backing up advertising behavior and audience information for the advertisement.

[0128] The second determining module 230 is configured to determine from the application a code application to be added that has cross-application permissions to back up advertising behavior and audience information for the advertisement from the first target application, and to determine from the multiple first target applications a second target application for each code application to be added to back up advertising behavior and audience information for the advertisement from the first target application.

[0129] The calling and adding module 240 is configured to, for each of the applications to be added, call the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement, and add it to the hypertext transfer protocol of the target advertisement playback page of the application to be added, thereby obtaining the cross-application backup application;

[0130] The cross-application backup module 250 is configured to, in response to an ad playback operation on the target ad playback page of the cross-application backup application, back up the ad behavior and audience information for the ad by adding pixel code of the second target application in the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application.

[0131] In one possible implementation, the calling and adding module 240 is configured as follows:

[0132] For each of the applications to be added with code, obtain the start and end markers in the Hypertext Transfer Protocol of the target ad playback page of each application to be added with code, which are used to back up the advertising behavior and audience information for the ad.

[0133] The pixel code of the second target application, which performs cross-application backup of advertising behavior and audience information for the advertisement, is invoked. The corresponding pixel code of the second target application is added between the start tag and the end tag in the Hypertext Transfer Protocol of the target advertisement playback page of each application to be added with code, to obtain the cross-application backup application.

[0134] In one possible implementation, the calling and adding module 240 is configured as follows:

[0135] Call the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement, and generate the pixel code software development kit corresponding to the second target application;

[0136] The pixel code software development kit of the second target application is added between the start tag and the end tag in the Hypertext Transfer Protocol of the target advertisement playback page of each application to which code is to be added, to obtain the cross-application backup application.

[0137] In one possible implementation, the calling and adding module 240 is configured as follows:

[0138] Call the pixel code of the second target application, which is the application to be added to perform cross-application backup of advertising behavior and audience information for the advertisement, and generate an XML file;

[0139] The XML file is read into memory using Java code and becomes target data that matches the data structure of the code generation engine of the application to which the code is to be added;

[0140] The target data is passed to the code generation engine to generate the SDK interface code corresponding to the pixel code of the second target application;

[0141] Use Java code to generate the corresponding Ant packaging script from the SDK interface code corresponding to the pixel code of the second target application;

[0142] The ant packaging script is executed by sending instructions through Java code, and the code contained in the SDK architecture of the application to be added is compiled by the ant packaging script to generate the pixel code software development kit corresponding to the second target application. The code contained in the SDK architecture includes the code of the SDK interface part, the protocol layer code, and the data verification layer code.

[0143] In one possible implementation, the cross-application backup module 250 is configured as follows:

[0144] In response to an ad playback operation on the target ad playback page of the cross-application backup application, the pixel code of the second target application added to the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application is executed;

[0145] Download the corresponding function library by adding the pixel code of the second target application in the Hypertext Transfer Protocol of the target ad playback page to the cross-application backup application;

[0146] Each time a user's advertising behavior is loaded in response to the advertisement, the corresponding function library is used to track the advertising behavior, generate an advertising behavior log, and obtain the user account information logged in on the cross-application backup application.

[0147] Based on the tracked advertising behavior logs and user account information, advertising behavior and audience information for the advertisement are generated and backed up across applications.

[0148] In one possible implementation, the cross-application backup module 250 is configured as follows:

[0149] Each time a user's advertising behavior towards the advertisement is loaded, the fbq function in the function library is called as the Page View event manager to track the events corresponding to the advertising behavior and generate an advertising behavior log.

[0150] In one possible implementation, the device further includes a push and playback module, configured to:

[0151] On the cross-application backup application, the target advertisement is determined based on the advertising behavior and audience information of the advertisement backed up across applications by the cross-application backup application, and the advertising behavior and audience information of the advertisement backed up in the cross-application backup application through the pixel code corresponding to this application but not across applications.

[0152] The target advertisement is played on the target advertisement playback page corresponding to the cross-application backup application.

[0153] This disclosure also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the methods described in the foregoing embodiments.

[0154] This disclosure also provides an electronic device, including:

[0155] A memory on which computer programs are stored;

[0156] A processor for executing the computer program in the memory to implement the steps of any of the methods described in the foregoing embodiments.

[0157] Figure 3 The cross-application advertising behavior and audience information backup device 100 shown includes a processor 1001 and a memory 1003. The processor 1001 and memory 1003 are connected, for example, via a bus 1002. Optionally, the cross-application advertising behavior and audience information backup device 100 may further include a communication component, which can be used for data interaction between the device 100 and other devices, such as sending and / or receiving data. It should be noted that in actual scheduling, the communication component is not limited to one, and the structure of this cross-application advertising behavior and audience information backup device 100 does not constitute a limitation on the embodiments of this application.

[0158] Processor 1001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 1001 may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0159] Bus 1002 may include a pathway for transmitting information between the aforementioned components. Bus 1002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 1002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 3 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0160] The memory 1003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium capable of carrying or storing program code and capable of being read by a computer, without limitation herein.

[0161] The memory 1003 is used to store program code that executes the embodiments of this disclosure, and its execution is controlled by the processor 1001. The processor 1001 is used to execute the program code stored in the memory 1003 to implement the steps shown in the aforementioned embodiments of the cross-application advertising behavior and audience information backup method.

[0162] This disclosure also provides a computer-readable storage medium storing program code. When the program code is executed by a processor, it can implement the steps and corresponding content of the aforementioned cross-application advertising behavior and audience information backup method embodiments.

[0163] The preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings. However, the present disclosure is not limited to the specific details of the above embodiments. Within the scope of the technical concept of the present disclosure, various changes, modifications, substitutions and variations can be made to these embodiments, and all such changes, modifications, substitutions and variations fall within the protection scope of the present disclosure.

[0164] It should also be noted that the various specific technical features described in the above embodiments can be combined in any suitable manner without contradiction, and such combinations should also be considered as part of this disclosure. To avoid unnecessary repetition, this disclosure will not further describe the various possible combinations. The technical scope of this application is not limited to the contents of the specification, but must be determined according to the scope of the claims.

Claims

1. A method for backing up advertising behavior and audience information across applications, characterized in that, The method includes: Obtain the application where ads are being displayed, and obtain the target ad playback page in the application used for ad playback; From the application, identify multiple first target applications that require backup of advertising behavior and audience information for the advertisement, and obtain pixel code corresponding to each first target application for backup of advertising behavior and audience information for the advertisement; From the application, determine the application to be added that has the permission to back up advertising behavior and audience information for the advertisement across applications from the first target application, and determine the second target application from the multiple first target applications that each application to be added can back up advertising behavior and audience information for the advertisement across applications; For each of the applications to be added with code, the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement is called and added to the hypertext transfer protocol of the target advertisement playback page of the application to be added with code, thereby obtaining the cross-application backup application; In response to an ad playback operation on the target ad playback page of the cross-application backup application, the cross-application backup provides ad behavior and audience information for the ad by adding pixel code of the second target application to the hypertext transfer protocol of the target ad playback page of the cross-application backup application.

2. The method for backing up cross-application advertising behavior and audience information as described in claim 1, characterized in that, For each of the applications to be added to, the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement is called and added to the Hypertext Transfer Protocol of the target advertisement playback page of the application to be added to, resulting in cross-application backup applications including: For each of the applications to be added with code, obtain the start and end markers in the Hypertext Transfer Protocol of the target ad playback page of each application to be added with code, which are used to back up the advertising behavior and audience information for the ad. The pixel code of the second target application, which performs cross-application backup of advertising behavior and audience information for the advertisement, is invoked. The corresponding pixel code of the second target application is added between the start tag and the end tag in the Hypertext Transfer Protocol of the target advertisement playback page of each application to be added with code, to obtain the cross-application backup application.

3. The method for backing up cross-application advertising behavior and audience information according to claim 2, characterized in that, The pixel code of the second target application, which is called by the application to be added to back up the advertising behavior and audience information of the advertisement across applications, is added between the start and end tags of the corresponding second target application in the Hypertext Transfer Protocol of the target advertisement playback page of each application to be added to obtain the cross-application backup application, including: Call the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement, and generate the pixel code software development kit corresponding to the second target application; The pixel code software development kit of the second target application is added between the start tag and the end tag in the Hypertext Transfer Protocol of the target advertisement playback page of each application to which code is to be added, to obtain the cross-application backup application.

4. The method for backing up cross-application advertising behavior and audience information according to claim 3, characterized in that, The step of calling the pixel code of the second target application, which performs cross-application backup of advertising behavior and audience information for the advertisement, and generating a pixel code software development kit corresponding to the second target application includes: Call the pixel code of the second target application, which is the application to be added to perform cross-application backup of advertising behavior and audience information for the advertisement, and generate an XML file; The XML file is read into memory using Java code and becomes target data that matches the data structure of the code generation engine of the application to which the code is to be added; The target data is passed to the code generation engine to generate the SDK interface code corresponding to the pixel code of the second target application; Use Java code to generate the corresponding Ant packaging script from the SDK interface code corresponding to the pixel code of the second target application; The ant packaging script is executed by sending instructions through Java code, and the code contained in the SDK architecture of the application to be added is compiled by the ant packaging script to generate the pixel code software development kit corresponding to the second target application. The code contained in the SDK architecture includes the code of the SDK interface part, the protocol layer code, and the data verification layer code.

5. The method for backing up cross-application advertising behavior and audience information as described in claim 1, characterized in that, The ad playback operation in response to the target ad playback page of the cross-application backup application, through the pixel code of the second target application added to the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application, includes the cross-application backup's ad behavior and audience information for the ad, including: In response to an ad playback operation on the target ad playback page of the cross-application backup application, the pixel code of the second target application added to the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application is executed; Download the corresponding function library by adding the pixel code of the second target application in the Hypertext Transfer Protocol of the target ad playback page to the cross-application backup application; Each time a user's advertising behavior is loaded in response to the advertisement, the corresponding function library is used to track the advertising behavior, generate an advertising behavior log, and obtain the user account information logged in on the cross-application backup application. Based on the tracked advertising behavior logs and user account information, advertising behavior and audience information for the advertisement are generated and backed up across applications.

6. The method for backing up cross-application advertising behavior and audience information as described in claim 5, characterized in that, The step of tracking user behavior towards the advertisement using the corresponding function library and generating an advertisement behavior log each time the advertisement is loaded includes: Each time a user's advertising behavior is loaded, the fbq function in the function library is called as the PageView event manager to track the events corresponding to the advertising behavior and generate an advertising behavior log.

7. The method for backing up cross-application advertising behavior and audience information as described in any one of claims 1-6, characterized in that, The method further includes: On the cross-application backup application, the target advertisement is determined based on the advertising behavior and audience information of the advertisement backed up across applications by the cross-application backup application, and the advertising behavior and audience information of the advertisement backed up in the cross-application backup application through the pixel code corresponding to this application but not across applications. The target advertisement is played on the target advertisement playback page corresponding to the cross-application backup application.

8. A cross-application advertising behavior and audience information backup device, characterized in that, include: The acquisition module is configured to acquire applications where advertisements are being displayed, and to acquire the target advertisement playback page in the application used for advertisement playback; The first determining module is configured to determine from the application that there are multiple first target applications that require backing up advertising behavior and audience information for the advertisement, and to obtain pixel code corresponding to each first target application for backing up advertising behavior and audience information for the advertisement. The second determining module is configured to determine, from the application, a code application to be added that has cross-application permissions to perform advertising behavior and audience information backup for the advertisement in the first target application, and to determine, from the multiple first target applications, a second target application for each of the code applications to be added to perform cross-application advertising behavior and audience information backup for the advertisement. The calling and adding module is configured to, for each of the applications to be added to the code application, call the pixel code of the second target application that performs cross-application backup of advertising behavior and audience information for the advertisement, and add it to the hypertext transfer protocol of the target advertisement playback page of the application to be added to the code application, thereby obtaining the cross-application backup application; The cross-application backup module is configured to respond to an ad playback operation on the target ad playback page of the cross-application backup application by backing up the ad behavior and audience information for the ad through pixel code of a second target application added to the Hypertext Transfer Protocol of the target ad playback page of the cross-application backup application.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the steps of the method described in any one of claims 1-7.

10. An electronic device, characterized in that, include: A memory on which computer programs are stored; A processor for executing the computer program in the memory to implement the steps of the method according to any one of claims 1-7.

Images