Advertisement behavior reporting method and device, electronic device, and storage medium

Abstract

The embodiment of the application discloses an advertisement behavior reporting method, comprising: obtaining landing page information and user conversion events of an application; determining target configuration parameters from a preset rule configuration file based on the landing page information and the user conversion events; wherein the rule configuration file comprises advertisement behavior configuration parameters of different landing page information placed in different carrier information types of different advertisement platforms; the target configuration parameters comprise target carrier information, a target advertiser ID, a target click ID and a target user event type; determining the content of the advertisement behavior to be filled from a preset interface configuration file based on the target carrier information; each target carrier information corresponds to an interface configuration file; writing the target advertiser ID, the target click ID and the target user event type into the content of the advertisement behavior; and reporting the content of the advertisement behavior after writing. The embodiment of the application also simultaneously provides an advertisement behavior reporting device, an electronic device and a storage medium.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of information technology in financial technology (Fintech), and relates to, but is not limited to, methods and devices for reporting advertising behavior, electronic devices, and storage media. Background Technology

[0002] With the development of computer technology, more and more technologies are being applied in the financial field, and the traditional financial industry is gradually transforming into Fintech. However, due to the security and real-time requirements of the financial industry, Fintech also places higher demands on technology. In the Fintech field, advertising performance analysis is mainly achieved through two methods: front-end tracking and back-end monitoring and reporting. Front-end tracking: When a user clicks on an ad, navigates to a landing page, and completes the corresponding action, the system captures the user's behavior and click ID (identity document) on the page, directly initiating an ad conversion behavior report to the advertising platform. Back-end monitoring and reporting: When a user clicks on an ad, navigates to a landing page, and completes the corresponding action, the front-end transmits the user information and the landing page's Uniform Resource Locator (URL) to the back-end for persistence, and the back-end then initiates an ad conversion behavior report to the advertising platform.

[0003] However, among the related technologies, front-end event tracking and reporting only supports landing page event tracking and does not support reporting of deep conversion behavior. Although back-end monitoring and reporting supports reporting of deep conversion behavior, it requires development in a specific language, and specific development languages ​​are less agile in dealing with new features of advertiser application programming interfaces (APIs). Summary of the Invention

[0004] This application provides a method and apparatus for reporting advertising behavior, an electronic device, and a storage medium.

[0005] The technical solution of this application embodiment is implemented as follows:

[0006] On one hand, this application provides an advertising behavior reporting method, the method comprising: obtaining landing page information and user conversion events of an application; determining target configuration parameters from a preset rule configuration file based on the landing page information and the user conversion events; wherein the rule configuration file includes advertising behavior configuration parameters for different landing page information placed on different advertising platforms with different carrier information types; the target configuration parameters include target carrier information, target advertiser ID, target click ID, and target user event type; determining the content of the advertising behavior to be filled from a preset interface configuration file based on the target carrier information; each target carrier information corresponds to one interface configuration file; writing the target advertiser ID, target click ID, and target user event type into the content of the advertising behavior; and reporting the content of the advertising behavior after writing.

[0007] In another aspect, embodiments of this application provide an advertising behavior reporting device, the device comprising an acquisition module, a first determination module, a second determination module, a first filling module, and a reporting module, wherein: the acquisition module is used to acquire landing page information and user conversion events of an application; the first determination module is used to determine target configuration parameters from a preset rule configuration file based on the landing page information and the user conversion events; wherein the rule configuration file includes advertising behavior configuration parameters for different landing page information placed on different advertising platforms with different carrier information types; the target configuration parameters include target carrier information, target advertiser ID, target click ID, and target user event type; the second determination module is used to determine the content of the advertising behavior to be filled from a preset interface configuration file based on the target carrier information; each target carrier information corresponds to one interface configuration file; the first filling module is used to write the target advertiser ID, target click ID, and target user event type into the content of the advertising behavior; the reporting module is used to report the content of the advertising behavior after it has been written.

[0008] In another aspect, embodiments of this application provide an electronic device, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and the processor executes the program to implement the steps in the above-described method.

[0009] In another aspect, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the above-described method.

[0010] The beneficial effects of the technical solutions provided in this application include at least the following:

[0011] In this embodiment, target configuration parameters are determined from a preset rule configuration file based on the landing page information and the user conversion event. The rule configuration file includes advertising behavior configuration parameters for different landing page information placed on different advertising platforms with different carrier information types. The target configuration parameters include target carrier information, target advertiser ID, target click ID, and target user event type. Based on the target carrier information, the content of the advertising behavior to be filled is determined from a preset interface configuration file. Each target carrier information corresponds to one interface configuration file. The target advertiser ID, target click ID, and target user event type are written into the content of the advertising behavior. In this way, the configuration parameters of the advertising behavior to be reported can be determined through different landing page information and different carrier information types, and the configuration parameters are filled into the advertising behavior content of the preset interface configuration file. The advertising behavior is reported by reporting the advertising behavior content. Thus, regardless of the programming language used by the application, the reporting of advertising behavior can be achieved by transmitting two parameters: landing page information and user conversion event. Furthermore, since the configuration file allows applications to be flexibly configured according to different business needs, for newly derived landing page information, advertising behavior can be reported simply by configuring the configuration file as needed, resulting in good scalability. Attached Figure Description

[0012] 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 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, wherein:

[0013] Figure 1A A schematic diagram of the structure of a rule configuration file provided in an embodiment of this application;

[0014] Figure 1B This application provides a schematic diagram of the structure of an interface configuration file.

[0015] Figure 1C A schematic diagram of the network architecture for an advertising behavior reporting method provided in this application embodiment;

[0016] Figure 1D A flowchart illustrating an advertising behavior reporting method provided in this application embodiment;

[0017] Figure 2 A flowchart illustrating an advertising behavior reporting method provided in this application embodiment;

[0018] Figure 3A flowchart illustrating an advertising behavior reporting method provided in this application embodiment;

[0019] Figure 4 A flowchart illustrating an advertising behavior reporting method provided in this application embodiment;

[0020] Figure 5 A schematic diagram of the network architecture for an advertising behavior reporting method provided in this application embodiment;

[0021] Figure 6 A flowchart illustrating an advertising behavior reporting method provided in this application embodiment;

[0022] Figure 7 A flowchart illustrating an advertising behavior reporting method provided in this application embodiment;

[0023] Figure 8 A schematic diagram of the composition structure of an advertising behavior reporting device provided in this application embodiment;

[0024] Figure 9 This is a schematic diagram of the hardware entity of an electronic device provided in an embodiment of this application. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. The following embodiments are used to illustrate this application, but are not intended to limit the scope of this application. 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.

[0026] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0027] It should be noted that the terms "first, second, and third" used in the embodiments of this application are merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, and third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0028] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiments of this application pertain. It should also be understood that terms such as those defined in general dictionaries should be understood to have a meaning consistent with their meaning in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.

[0029] To aid in understanding this application, the following sections introduce several concepts involved in this application:

[0030] 1. Landing Page

[0031] A landing page is the webpage displayed to a user after a potential user clicks on an advertisement or uses a search engine. This page typically displays supplementary content related to the clicked advertisement or search result link.

[0032] 2. Reporting of Advertising Activities

[0033] Advertisers place landing page ads on advertising platforms and push them to target customers. After customers click on the ads, they are redirected to the landing page and complete the specified actions. Advertisers monitor user actions and report the corresponding conversion behaviors to the advertising platform for ad performance analysis.

[0034] 3. Rule configuration file

[0035] This rule configuration file can also be called a rule pattern file. Let's take HTML5-based advertising behavior as an example. Figure 1A As shown, depending on the different portals, the login page generates multiple landing page URLs, which are then displayed on different advertising platforms. Each of these multiple landing page URLs includes at least information about the advertising platform on which the page is displayed. For example, after the login page 11 generates multiple landing page URLs, these URLs are then displayed on different advertising platforms.

[0036] Therefore, it is evident that different landing pages can be placed on different advertising platforms based on advertising behavior. In order to analyze the effectiveness of advertising behavior, it is necessary to report advertising behavior. The rule configuration file (Rule pattern file) defines a rule for advertising behavior reporting.

[0037] 4. Interface configuration file

[0038] This interface configuration file can also be called the API schema file. The API schema file defines several elements for reporting advertising behavior. For example... Figure 1BAs shown, the API pattern file includes interface configuration block 12 and account configuration block 13. By adding keywords to interface configuration block 12, the API pattern file can be flexibly extended to support the API of the new advertising platform without requiring the caller (application) to make changes and redeploy, thus maintaining the openness of accessing the new advertising platform.

[0039] 5. Click ID

[0040] Click IDs are issued by advertisers and are used to trace the advertisement corresponding to the click.

[0041] For example, advertiser A places three ads on advertising platform B, such as AD1, AD2, and AD3. Each ad corresponds to a landing page URL, and each landing page URL is a webpage implemented based on HTML5. Advertiser A places ad AD1 on advertising platform B to be displayed to users. For example, advertiser A places ad AD1 on the Toutiao advertising platform. When a user opens Toutiao and browses content, they come across ad AD1, click on ad AD1, and are redirected to the corresponding landing page URL. The landing page URL includes a click ID at the end to uniquely identify this click.

[0042] 6. Non-deep conversion and deep conversion

[0043] Taking fintech businesses as an example, placing fintech advertisements involves multiple processes, including filling in basic information and real-name authentication in some embodiments.

[0044] 1) The process of filling in basic information can be implemented on the landing page, and the conversion that occurs on the landing page is not a deep conversion. For example, users fill in basic information on the landing page, such as mobile phone number and verification code; after completion, a form submission action is triggered. On the one hand, the above basic information is reported to the advertising platform; on the other hand, the number of times the basic information filling button is triggered and the number of users who leave information are counted and reported to the advertising platform.

[0045] 2) The real-name authentication process requires interaction between the front-end and back-end, and the conversion that occurs after the interaction is a deep conversion. For example, real-name authentication achieved through interaction between the landing page and the business server implementing fintech-related services is a deep conversion.

[0046] For example, after filling in the basic information, the business process of fintech business needs to be continued to enter the real-name authentication stage. In the above stage, personal information such as ID card number and bank card number needs to be filled in. The above information related to user real-name authentication will be stored in the data server that interacts with the business server through the business server for persistence. Therefore, the real-name authentication process is a deep conversion process.

[0047] When a user clicks on the landing page, the click ID is retrieved from the landing page URL. This click ID identifies the corresponding ad. However, the click ID is lost during the interaction between the landing page and the business service. Therefore, the click ID needs to be stored in a local database table. This allows subsequent deep conversions to retrieve the click ID from this table and perform the conversion. Deep conversions rely on the conversion ID in the database, and the data is reported only after the deep conversion is performed in the backend.

[0048] 7. Bury points

[0049] Event tracking is a common data collection method in website analytics, and it's a privately deployed data collection approach. Event tracking collects information within specific processes of an application to track product usage and provide data support for further product optimization. Event tracking includes at least basic and intermediate levels, among which:

[0050] Basic tracking: Embedding statistical code at key points of product and service conversion. For example, statistical code is embedded at the key point of triggering the purchase button to track the click-through rate of the purchase button and ensure that data collection is not duplicated based on the purchase button ID.

[0051] Intermediate tracking: This involves embedding multiple code snippets into the product platform to track a series of user behaviors on each interface. For example, multiple code snippets track the user's actions of opening a product details page → selecting a product → adding the target product to the shopping cart → clicking to purchase the product.

[0052] Ad performance analysis can be achieved in two ways: front-end tracking and back-end monitoring. Front-end tracking: When a user clicks on an ad, navigates to a landing page, and completes a corresponding action, the user's behavior and click ID are captured by tracking on the page, and the ad conversion behavior is directly reported to the ad platform. Back-end monitoring: When a user clicks on an ad, navigates to a landing page, and completes a corresponding action, the front-end sends the user information and landing page URL to the back-end for persistence, and the back-end then reports the ad conversion behavior to the ad platform. However, front-end tracking only supports landing page tracking and does not support reporting of deeper conversion behaviors. While back-end monitoring supports reporting of deeper conversion behaviors, it requires development in a specific programming language, which is less agile in adapting to new features of advertiser APIs.

[0053] To address the aforementioned issues, this application provides a method for reporting advertising behavior. This method pre-defines a rule configuration file and an interface configuration file, and implements the reporting of advertising behavior based on these two configuration files. This method supports invocation by applications deployed on specific operating system environments, and these applications can be implemented using any programming language.

[0054] Before introducing the advertising behavior reporting method provided in the embodiments of this application, we will first introduce a network architecture for an advertising behavior reporting method. Figure 1C A network architecture diagram of an advertising behavior reporting method provided in this application embodiment is shown below. Figure 1C As shown, the network architecture includes: computer 10, tablet 20, mobile phone 30, business server 40, advertising platform 50, advertising platform 60, and advertising platform 70, wherein:

[0055] Computer 10, tablet 20 and mobile phone 30 include an application that is used to issue advertising behavior reporting instructions and call script tools;

[0056] The business server 40 includes a script tool, which is used to report the content of advertising behavior in the application to the advertising platform;

[0057] Advertising platform 50, advertising platform 60 and advertising platform 70 are used to receive the content of advertising behavior sent by the script tool and return the execution result to the script tool;

[0058] In one possible implementation, the business server 40 also includes a log file for recording the execution results of the scripting tools.

[0059] In one possible implementation, the business server 40 also includes an advertising behavior pattern file, used to send the rule configuration file to the script tool; and to populate the interface configuration file according to the content sent by the script tool.

[0060] based on Figure 1C The network architecture of the advertising behavior reporting method shown is as follows: Figure 1D This is a flowchart illustrating an advertising behavior reporting method provided in an embodiment of this application, as shown below. Figure 1D As shown, the method includes at least the following steps:

[0061] Step S101: Obtain the application's landing page information and user conversion events;

[0062] In some embodiments, the landing page information may include a landing page URL, which may include parameters such as advertising platform information and click information.

[0063] For example, the landing page URL is a URL that includes advertising platform information parameters and click information parameters: https: / / sss.com / mesp-wpm / h5 / r1s / # / user / login?portal=1454&click_id=EJ-Yn7-B0PoCGIeAnYPp8vkCKIy186Do-_kC. Here, "portal" represents the advertising platform information parameter, and "click_id" represents the click information parameter.

[0064] In some embodiments, the user conversion event can be code.

[0065] For example, user conversion event = 1001 is used to indicate the event of a user entering a mobile phone number; user conversion event = 1003 indicates the event of a user registration.

[0066] Step S102: Based on the landing page information and the user conversion event, determine the target configuration parameters from the preset rule configuration file; wherein, the rule configuration file includes advertising behavior configuration parameters for different landing page information placed on different advertising platforms with different carrier information types; the target configuration parameters include target carrier information, target advertiser ID, target click ID, and target user event type;

[0067] In some embodiments, the preset rule configuration file defines a rule for reporting advertising behavior, which is applicable to advertising behavior based on different carrier information and different advertising platforms. The rule configuration file includes multiple different keywords.

[0068] 1) The keywords configuration specifies the advertising platforms on which the landing page is placed by advertisers.

[0069] For example, Figure 1A This is a schematic diagram illustrating an application scenario of a rule configuration file provided in an embodiment of this application; for example... Figure 1A As shown, the landing pages portal=1454 and portal=1455 were placed by advertiser 1382 on advertising platform A.

[0070] 2) The `click` keyword is configured to parse the click field after the landing page is clicked.

[0071] For example, such as Figure 1A As shown, when a landing page placed on advertising platform A is clicked, the click_id field needs to be parsed; when a landing page placed on advertising platform B is clicked, the bd_vid field needs to be parsed.

[0072] 3) The `event_map` keyword configures the types of user events that should be reported when a user conversion event occurs. A user conversion event refers to a user clicking an ad on the advertising platform, being redirected to a landing page, and completing a series of page clicks on that landing page. The `event_map` keyword can be configured globally across any advertising platform, or on a specific landing page. If both global and specific landing page configurations exist, the specific landing page configuration will take precedence.

[0073] For example, such as Figure 1A As shown, when the landing page of the advertising platform A detects a user conversion event of 1001, the name of the user conversion event is "Micro-business Loan Retention". Find the event_id: 1001, determine that the user event type event_type_val is REGISTER, and the "registration" behavior should be reported.

[0074] 4) The event_type keyword identifies the field used for the reported behavior.

[0075] For example, such as Figure 1A As shown, when reporting to advertising platform A, the action_type field is used to report the user event type. When reporting user events of the registration type, {"action_type":"REGISTER"} is used.

[0076] 5) The `output` keyword specifies the information that should be output after the landing page is matched by the rule configuration file. The information output by `output` can be used as input to the interface configuration file.

[0077] For example, such as Figure 1A As shown, the output information includes: carrier information, target advertiser ID, target click ID, and user event type.

[0078] In some embodiments, the carrier information can be HTML, a public account, or a mini-program; the advertiser ID can include a number used to represent different advertisers; the user event type can be the value of event_type_val, for example, it can be REGISTER, representing the "register" behavior.

[0079] In some embodiments, determining the target configuration parameters from a preset rule configuration file based on the landing page information and the user conversion event may include: matching at least one keyword in the preset rule configuration file based on the landing page information and the user conversion event, obtaining a parameter value for each keyword, and combining the at least one parameter value to obtain the target matching parameters.

[0080] Step S103: Based on the target carrier information, determine the content of the advertising behavior to be filled from the preset interface configuration file; each target carrier information corresponds to one interface configuration file;

[0081] In some embodiments, the preset interface configuration file defines several elements for reporting advertising behavior. Different carrier information types correspond to different configuration files: HTML5 carrier information corresponds to ad_api_h5.yml (HTML5 landing page configuration file), WeChat Official Account carrier information corresponds to ad_api_official.yml (WeChat Official Account landing page configuration file), and WeChat Mini Program carrier information corresponds to ad_api_mina.yml (WeChat Mini Program landing page configuration file).

[0082] Taking ad_api_h5.yml as an example, the APIs of different advertising platforms vary, but all advertising platforms share five common keywords: URL, method, header, content of the advertising action, and advertiser information (account). Taking advertising platform A as an example, where T identifies advertising platform A, the API configuration reporting elements are: URL, method, header, content, and account. The account can include user_action_set_id and access_token.

[0083] In some embodiments, different types of profiles include content for different advertising activities. A WeChat Official Account landing page profile may include the content of advertising activities and advertiser information, but may not include a message header.

[0084] Step S104: Write the target advertiser ID, target click ID, and target user event type into the content of the advertising behavior;

[0085] In some embodiments, keywords corresponding to the target advertiser ID, target click ID, and target user event type are matched in the content of the advertising behavior, and parameter values ​​are filled into the keywords one by one.

[0086] Step S105: Report the content of the advertising behavior after it has been written.

[0087] In one possible implementation, step S105, reporting the content of the written advertising behavior, includes:

[0088] Step S1051: Determine the reporting command based on the content of the written advertising behavior;

[0089] In some embodiments, the reporting command can be a script command, such as a CURL command. The CURL command includes at least three parameters: URL, content, and Method. The URL can be the URL of the advertising platform being reported; the content can be the content of the advertising action after it has been written; and the Method can be the method for transmitting the content of the advertising action, such as the GET method or the POST method.

[0090] For example, the CURL command can be: CURL{URL}-X{method}-H. "Content-Type:application / json"-d{content}.

[0091] Step S1052: Execute the reporting command to report the content of the written advertising behavior to the target server.

[0092] In some embodiments, the target server can be a target advertising platform. For example, if advertising platform A wants to obtain the performance of an advertisement placed on platform A, it needs to report the advertising behavior of the advertisement to platform A.

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

[0094] Step S106: Receive the execution result of the reporting command sent by the target server;

[0095] In some embodiments, different advertisers may have different message bodies. The execution results may be stored in different message body formats.

[0096] Step S107: Write the execution result to a log file.

[0097] In some embodiments, the log file may include the following: the reported advertising platform, the target user event type, the target click ID, and the execution result.

[0098] For example, the log file includes: T|1454|1001|RECISTER|https: / / smewyd.webank.com / mesp-wpm / h5 / rls / # / user / login?portal=1454&click_id=EJ-Vn7-B0PoCGIeAnYPp8vkCKIyI86Do-_kcC|success|202108182137, indicating that the event of user 1001 entering their mobile phone number was reported to advertising platform A. This corresponds to the registered advertising behavior, and the behavior and click ID are reported to advertising platform A. The reported result is a successful result.

[0099] In this embodiment, on one hand, based on the landing page information and the user conversion event, target configuration parameters are determined from a preset rule configuration file. The rule configuration file includes advertising behavior configuration parameters for different landing page information placed on different advertising platforms with different carrier information types. The target configuration parameters include target carrier information, target advertiser ID, target click ID, and target user event type. Based on the target carrier information, the content of the advertising behavior to be filled is determined from a preset interface configuration file. Each target carrier information corresponds to one interface configuration file. The target advertiser ID, target click ID, and target user event type are written into the content of the advertising behavior. In this way, the configuration parameters of the advertising behavior to be reported can be determined through different landing page information and different carrier information types, and the configuration parameters are filled into the advertising behavior content of the preset interface configuration file. The advertising behavior is reported by reporting the advertising behavior content. Thus, regardless of the programming language used by the application, the reporting of advertising behavior can be achieved by transmitting two parameters: landing page information and user conversion event. Furthermore, since the configuration file allows applications to be flexibly configured according to different business needs, for newly derived landing page information, advertising behavior can be reported simply by configuring the configuration file as needed, resulting in good scalability.

[0100] On the other hand, it receives the execution result of the reporting command sent by the target server; writes the execution result to a log file, which can archive the execution result for easy statistics; and can promptly report compensation in case of execution failure.

[0101] based on Figure 1C The network architecture of the advertising behavior reporting method shown is as follows: Figure 2 This is a flowchart illustrating an advertising behavior reporting method provided in an embodiment of this application, as shown below. Figure 2 As shown, the method includes at least the following steps:

[0102] Step S201: Obtain the application's landing page information and user conversion events;

[0103] Step S202: Based on the prefix of the landing page information, determine the target rule configuration block from the rule configuration file; wherein, the rule configuration file includes advertising behavior configuration parameters for different landing page information placed on different advertising platforms with different carrier information types;

[0104] In some embodiments, the rule configuration file includes configuration blocks for multiple URLs. The prefix for the landing page information can be the landing page URL without parameters. For example... Figure 4 As shown, the landing page information includes a prefix 31, and the rule configuration file includes configuration blocks 32 and 33 for multiple URLs. Based on the comparison between prefix 31 and configuration blocks 32 and 33, it is determined that the URL of prefix 31 is the same as the URL of configuration block 32, and configuration block 32 is identified as the target rule configuration block.

[0105] Step S203: Obtain the target carrier information from the configuration information of the target rule configuration block;

[0106] In some embodiments, the configuration information of the target rule configuration block includes carrier information, which is target carrier information. For example... Figure 4 As shown, configuration block 32 includes a keyword representing carrier information: carrier, and the parameter value h5 of this keyword is the target carrier information.

[0107] Step S204: Based on the landing page information and the configuration information of the target rule configuration block, determine the target click ID and the target advertiser ID;

[0108] Step S205: Based on the user conversion event, locate the target rule configuration block to obtain the target user event type;

[0109] In some embodiments, the data in the target rule configuration block may be stored in the form of multiple arrays.

[0110] like Figure 4 As shown, the event_map keyword is an array, and the elements in the array include: event_ID, event name, event_type_val, and event_type_desc.

[0111] Step S206: Based on the target carrier information, determine the content of the advertising behavior to be filled from the preset interface configuration file; each target carrier information corresponds to one interface configuration file;

[0112] Step S207: Write the target advertiser ID, target click ID, and target user event type into the content of the advertising behavior;

[0113] Step S208: Report the content of the advertising behavior after it has been written.

[0114] In one possible implementation, step S204, determining the target click ID and the target advertiser ID based on the landing page information and the configuration information of the target rule configuration block, includes:

[0115] Step S2041: Using the keyword of the target rule configuration block as the parameter name, parse the landing page information to obtain the advertising platform ID;

[0116] like Figure 4 As shown, the parameter value `protal` for keyword 38 in the target rule configuration block represents the parameter name of the advertising platform ID in the landing page information. By parsing the landing page information using the obtained `protal` identifier, the advertising platform ID is found to be 1454.

[0117] Step S2042: Using the keyword of the advertising platform ID as the parameter name, search the target rule configuration block to obtain the advertising platform identifier to which the landing page information belongs and the target advertiser ID;

[0118] In some embodiments, the advertising platform identifier may be the name of the advertising platform, and the target advertiser ID may be the advertiser's number.

[0119] For example, using 1454 as the parameter name, searching the target rule configuration block 32 can yield the advertising platform identifier T, and under T, keys34 can be found. Based on 1454 in 34, the target advertiser ID is determined to be 1382.

[0120] Step S2043: Using the advertising platform identifier as the key name, retrieve the value, search the target rule configuration block, and obtain the parameter value of the clicked keyword;

[0121] For example, by searching the configuration information under the advertising platform identifier T, the parameter value click_id of the click keyword in click 35 can be obtained.

[0122] Step S2044: Obtain the value by using the parameter value of the clicked keyword as the key name, parse the landing page information, and obtain the target click ID.

[0123] For example, the value is obtained by using the parameter value click_id as the key name, parsing the landing page information, and obtaining the target click ID as EJ-Yn7-B0PoCGIeAnYPp8vkCKIyI86Do-_kC.

[0124] In this embodiment, on one hand, the target rule configuration block is determined from the rule configuration file based on the prefix of the landing page information. Thus, when new landing page information is obtained, the target rule configuration block can be determined by adding a new configuration block to the rule configuration file, enhancing the extensibility of the rule configuration file, avoiding secondary development and updates to the application when adding new landing pages, saving manpower costs, and demonstrating strong versatility.

[0125] On the other hand, by using the parameter value of the clicked keyword as the key name to obtain the value, the landing page information is parsed to obtain the target click ID. In this way, the target click ID can be obtained based on different clicked keywords. This allows for accurate identification of the target click ID even when different advertising platforms or different carrier information correspond to different clicked keywords, increasing the accuracy of click ID identification and thus improving the accuracy of tracing the source of clicks to corresponding advertisements, thereby improving the accuracy of advertising behavior reporting.

[0126] based on Figure 1C The network architecture of the advertising behavior reporting method shown is as follows: Figure 3 This is a flowchart illustrating an advertising behavior reporting method provided in an embodiment of this application, as shown below. Figure 3 As shown, the method includes at least the following steps:

[0127] Step S301: Obtain the application's landing page information and user conversion events;

[0128] Step S302: Based on the prefix of the landing page information, determine the target rule configuration block from the rule configuration file; wherein, the rule configuration file includes advertising behavior configuration parameters for different landing page information placed on different advertising platforms with different carrier information types;

[0129] Step S303: Obtain the target carrier information from the configuration information in the target rule configuration block;

[0130] Step S304: Using the keyword of the target rule configuration block as the parameter name, parse the landing page information to obtain the advertising platform ID;

[0131] Step S305: Using the keyword of the advertising platform ID as the parameter name, search the target rule configuration block to obtain the advertising platform identifier to which the landing page information belongs and the target advertiser ID;

[0132] Step S306: Using the advertising platform identifier as the key name, retrieve the value, search the target rule configuration block, and obtain the parameter value of the clicked keyword;

[0133] Step S307: Obtain the value by using the parameter value of the clicked keyword as the key name, parse the landing page information, and obtain the target click ID;

[0134] Step S308: Using the advertising platform identifier as the key name, retrieve the value, search the target rule configuration block, and obtain the array corresponding to the event mapping keywords;

[0135] For example, such as Figure 4 As shown, the value is obtained by using the advertising platform identifier T as the key, resulting in an array of event_map.

[0136] Step S309: Based on the user conversion event and the landing page information, determine the target user event type from the array;

[0137] For example, based on the value 1003 of user conversion event 36, the event_id is matched in the event_map array to determine the array with event_id = 1003. Furthermore, based on the advertising platform ID of 1454 in the landing page information, the array with key = 1454 is determined, resulting in array 37. In array 37, event_type_val is retrieved as REGISTER. Therefore, the target user event type for user conversion event 1003 is registration.

[0138] Step S310: Based on the target carrier information, determine the content of the advertising behavior to be filled from the preset interface configuration file; each target carrier information corresponds to one interface configuration file;

[0139] Step S311: Write the target advertiser ID, target click ID, and target user event type into the content of the advertising behavior;

[0140] Step S312: Report the content of the advertising behavior after it has been written.

[0141] In one possible implementation, step S305 involves searching the target rule configuration block using the keyword of the advertising platform ID as the parameter name to obtain the advertising platform identifier to which the landing page information belongs and the target advertiser ID, including:

[0142] Step S3051: In the target rule configuration block, find the grandparent node of the advertising platform ID keyword;

[0143] For example, such as Figure 4 As shown, the parent node of identifier 34 corresponding to the advertising platform ID keyword is keys, and the grandparent node is T, which is used to represent the identifier of the advertising platform.

[0144] Step S3052: The grandfather node is identified as the advertising platform identifier.

[0145] In one possible implementation, step S310 involves determining the content of the advertising behavior to be filled from a preset interface configuration file based on the target carrier information; each target carrier information corresponds to an interface configuration file, including: searching for the target configuration block corresponding to the advertising platform identifier from the preset interface configuration file according to the target carrier information; the target configuration block includes at least the content of the advertising behavior to be filled.

[0146] In some embodiments, the configuration file corresponding to the target carrier information is determined from multiple interface configuration files based on the target carrier information; and the target configuration block corresponding to the advertising identifier is determined from the interface configuration file based on the advertising identifier.

[0147] For example, such as Figure 5 As shown, among the multiple configuration files, the carrier information for HTML5 type corresponds to ad_api_h5.yml (HTML5 landing page configuration file), the carrier information for WeChat Official Account type corresponds to ad_api_official.yml (WeChat Official Account landing page configuration file), and the carrier information for Mini Program type corresponds to ad_api_mina.yml (Mini Program landing page configuration file). Based on the carrier information, the ad_api_h5.yml configuration file is selected. The target configuration block 39 is located in the interface configuration file based on the advertising identifier T. The target configuration block 39 includes the interface configuration block and the account configuration block.

[0148] In one possible implementation, the preset interface configuration file includes an interface configuration block and an account configuration block, the interface configuration block including the content of the advertising behavior, and the method further includes;

[0149] Step S313: Locate the access token information and access data source information corresponding to the target advertiser ID in the account configuration block;

[0150] For example, such as Figure 4 As shown, the target advertiser ID is 1382. Find the line corresponding to 1382 in the interface configuration block, and find the access token information 42 and access data source information 41 in this line.

[0151] Step S314: Fill the access token information into the target server URL;

[0152] For example, such as Figure 4 As shown, the access token information 42 is filled into position 43 of the target server URL to obtain access permissions when accessing the target server.

[0153] Step S315: Write the access data source information into the content of the advertising behavior.

[0154] For example, such as Figure 4 As shown, the access data source information 41 is filled into the range data source information field in content 40.

[0155] In some embodiments, the action_type and click_id in content 40 are populated based on the target user event type and target click ID in output 44. The target advertiser ID is then populated into account_id, completing the population of all information in content 40.

[0156] It should be understood that during implementation, steps S313 to S315 are not sequential with step S311. Step S311 can be executed first to write the target advertiser ID, target click ID, and target user event type into the content of the advertising behavior. Alternatively, steps S313 to S315 can be executed first to write the access data source information into the content of the advertising behavior. No limitation is made here.

[0157] It should be understood that during the reporting process, a connection needs to be established through the target server URL, and the content 40 is reported to the target server through the connection.

[0158] In this embodiment, on one hand, the value is obtained by using the advertising platform identifier as the key name, and the target rule configuration block is searched to obtain an array corresponding to the event mapping keywords. Thus, even when an advertising platform is added, the reporting of advertising behavior can be achieved by adding the configuration information of the new advertising platform to the configuration file, simplifying the change process and improving the versatility of the advertising behavior reporting method.

[0159] On the other hand, in the target rule configuration block, the grandparent node of the advertising platform ID keyword is searched; the grandparent node is identified as the advertising platform identifier. In this way, the advertising platform identifier can be accurately determined through the relationship between nodes, increasing the accuracy of the method.

[0160] On the other hand, the access token information corresponding to the target advertiser ID is retrieved from the account configuration block; the access token information is then populated into the target server URL. This decouples the access token information from the target server URL, allowing the target server URL to be used with different access token information. When accessing different permissions, there is no need to change the target server URL; only the range token information needs to be populated into the target server URL, enhancing the method's versatility.

[0161] Figure 5A network architecture diagram of an advertising behavior reporting method provided in this application embodiment is shown below. Figure 5 As shown, the network architecture includes an application 501, a script tool 502, an advertising platform 503, a log file 504, and an advertising behavior pattern file 505, wherein:

[0162] Application 501 is used to issue an advertising behavior reporting command to call script tool 502;

[0163] Script tool 502 is used to report the content of advertising behavior in application 501 to advertising platform 503;

[0164] Advertising platform 503 is used to receive the content of advertising behavior sent by script tool 502 and return the execution result to script tool 502;

[0165] Log file 504 is used to record the execution results of script tool 502;

[0166] The advertising behavior pattern file 505 is used to send the rule configuration file to the script tool 502 and populate the interface configuration file according to the content sent by the script tool 502.

[0167] based on Figure 5 The network architecture of the advertising behavior reporting method shown below, taking the landing page information as the landing page URL as an example, Figure 6 This is a flowchart illustrating an advertising behavior reporting method provided in an embodiment of this application, as shown below. Figure 6 As shown, the method includes at least the following steps:

[0168] Step S601: Obtain the configuration blocks of multiple URLs in the preset rule configuration file and perform prefix matching with the landing page URL to obtain the target rule configuration block corresponding to the landing page URL;

[0169] It should be understood that step S601 is implemented by script tool 502, for example, by a Linux script in ad_tool.linux. In some embodiments, before implementing step S601, the script tool receives two parameters sent by application 501: the landing page URL and the user conversion event.

[0170] For example, such as Figure 4 As shown, the landing page URL includes the parameter values ​​of the target click ID and click_ID; the user conversion event is 1003.

[0171] Step S602: Using the keyword of the target rule configuration block as the parameter name, parse the landing page information to obtain the advertising platform ID;

[0172] For example, the value of key (portal) in the configuration block is taken as the parameter name to parse the landing page URL parameter value, resulting in 1454. The parameter value uniquely identifies the derived landing page.

[0173] Step S603: Using the keyword of the advertising platform ID as the parameter name, search the target rule configuration block to obtain the advertising platform identifier to which the landing page information belongs and the target advertiser ID;

[0174] For example, the configuration block is searched using parameter value 1454 to locate the advertising platform identifier T; the target advertiser ID is 1382.

[0175] Step S604: Using the advertising platform identifier as the key name, retrieve the value, search the target rule configuration block, and obtain the parameter value of the clicked keyword;

[0176] For example, the value is obtained by using the advertising platform as the key name, taking the click key value, and parsing the URL parameter value with click_id as the parameter name, resulting in EJ-Yn7-B0PoCGIeAnYPp8vkCKIyI86Do-_kC.

[0177] Step S605: Using the advertising platform identifier as the key name, retrieve the value, search the target rule configuration block, and obtain the array corresponding to the event mapping keywords;

[0178] like Figure 4 As shown, the value is obtained by using the advertising platform identifier T as the key, resulting in an array of event_map.

[0179] After step S605, the method further includes: determining the target user event type from the array based on the user conversion event and the landing page information; and obtaining the target carrier information from the configuration information of the target rule configuration block.

[0180] For example, such as Figure 6 As shown, the script input parameter (1003) and the landing page URL parameter value 1454 are used to locate the array element, and the event_type_val key is stored in action_type(event_type). At this point, the script has obtained carrier=h5 and account_id=1382 from the rule configuration file based on the landing page URL and the user conversion event.

[0181] Step S606: Based on the target carrier information, search for the target configuration block corresponding to the advertising platform identifier in the preset interface configuration file; the target configuration block includes an interface configuration block and an account configuration block;

[0182] For example, the ad_api_h5.yml schema file is located for h5 based on the carrier, and the target configuration block is located based on T; the target configuration block includes the api block and the account configuration block.

[0183] Step S607: Fill the access token information into the target server URL;

[0184] For example, the URL value is retrieved from the API key-value map, the value to be filled is detected, and if it exists, the account key-value map is traversed and filled. For example, a connection can be established between the script tool 502 and the advertising platform 503 through the target server URL.

[0185] Step S608: Fill in the content of the advertising behavior in the interface configuration block.

[0186] For example, the content value is retrieved from the API key-value map, which is a behavior template with no parameters. The account key-value map is iterated and populated. The output key-value map is then used to continue populating the content parameter.

[0187] After step S608, the method further includes step S609, determining a reporting command based on the content of the written advertising behavior.

[0188] For example, a CURL command is assembled, and a CURL command is created based on the obtained URL, method, and content. The result is then written to a log file 504.

[0189] based on Figure 5 The network architecture of the advertising behavior reporting method shown below, taking the landing page information as the landing page URL as an example, Figure 7 This is a flowchart illustrating an advertising behavior reporting method provided in an embodiment of this application, as shown below. Figure 7 As shown, the method includes at least the following steps:

[0190] Step S701, script tool 502 obtains the parameters transmitted by the application;

[0191] For example, the script tool is a piece of code under the Linux operating system that has the function of reporting advertising behavior, and receives two parameters from the Linux command: user conversion event and landing page URL.

[0192] Step S702: Connect the script tool to the rule configuration file;

[0193] For example, the `cat` command in the Linux operating system connects to the rule configuration file, and the `shyml` command in the Linux operating system retrieves the first-level keywords in the rule configuration file, such as... Figure 4 The URLs listed are https: / / smewyd:webank:com / mesp-wpm / h5 / rls / # / user / login, https: / / s...editentry, and / pages / lo....eUserInfo.

[0194] Step S703: The script tool obtains the first-level keywords in the rule configuration file; the first-level keywords include at least one URL to be matched;

[0195] For example, the first-level keywords are obtained and at least one URL is sent to an executable script tool.

[0196] Step S704: The script tool performs prefix matching between the landing page URL and each URL to be matched to obtain the target rule configuration block corresponding to the landing page URL.

[0197] For example, these URLs are received, and prefix matching is performed between the landing page URL and multiple URLs to be matched to obtain the target rule configuration block corresponding to the landing page URL;

[0198] Step S705: The script tool obtains the configuration information in the target rule configuration block;

[0199] Step S706: The script tool obtains the second-level keywords in the configuration block;

[0200] In some embodiments, the second-level keywords include at least carrier information, advertising platform keywords, and rules.

[0201] Step S707: The script tool parses the landing page URL to obtain the advertising platform ID corresponding to the advertising platform keyword;

[0202] For example, the parameter value (portal) with the key name of the advertising platform keyword in the configuration block is obtained, and the landing page URL parameter value is parsed as the parameter name to obtain 1454. The parameter value uniquely identifies the derived landing page.

[0203] Step S708: The script tool searches for the grandparent node of the advertising platform parameter value in the configuration block;

[0204] Step S709: The script tool obtains the advertising platform identifier corresponding to the grandparent node returned by the configuration block; the advertising platform identifier is the third-level keyword in the configuration block.

[0205] For example, the grandparent node is returned to an executable script tool.

[0206] Step S710: The script tool obtains the configuration information under the advertising platform identifier; the configuration information is the fourth-level keyword in the configuration block;

[0207] For example, obtain the configuration information under the advertising platform identifier.

[0208] Step S711: The script tool receives the fourth-level keyword from the configuration block; the fourth-level keyword includes at least the target advertiser ID, target click ID, and target user event type corresponding to the advertising platform identifier;

[0209] Step S712: The script tool parses the landing page URL to obtain the parameter value of the click ID; the parameter value of the click ID, the carrier information, the parameter value of the advertiser, and the parameter value of the event type are combined to obtain the output parameter value;

[0210] Step S713: The script tool determines the target configuration block based on the carrier information in the output parameter values;

[0211] For example, based on the carrier information in the output parameter values, an interface configuration file is determined; based on the advertising platform identifier, a target configuration block is determined in the interface configuration file; the target configuration block includes first-level keywords, and the first-level keywords include at least an interface configuration block and an account configuration block; the target interface configuration block is determined from the carrier, for example, if it is h5, the ad_api_h5.yml configuration file is read; and the configuration blocks under this configuration file are read.

[0212] Step S714: The script tool obtains the second-level keywords under the target configuration block; the second-level keywords include at least the target server URL, request method, and content; the second-level key is the first-level keyword key under the interface configuration block.

[0213] Step S715: Obtain the account configuration block;

[0214] Step S716: The script tool obtains the parameter values ​​(account_id) of the target advertiser, the parameter values ​​(user_action_set_id) of the access data source, and the parameter values ​​(access_token) of the access token from the account configuration block.

[0215] Step S717: The script tool fills the parameter value of the access token into the target server URL; and fills the parameter value of the advertiser, the parameter value of the access data source, the parameter value of the clicked ID, and the parameter value of the event type into the content.

[0216] Step S718: Combine the content and the target server URL to obtain a CURL command; send the CURL command to the CURL tool;

[0217] Assemble and execute CURL commands;

[0218] Step S719: The advertising platform obtains the content of the reported advertising behavior and returns a response; the response is sent to the script tool (ad_tool.linux); the script tool (ad_tool.linux) receives the response;

[0219] For example, different advertising platforms return different message bodies.

[0220] In step S720, the script tool sends the response to the application;

[0221] For example, the execution result is returned after execution, indicating success or failure.

[0222] Step S721: The script tool writes this execution to the log.

[0223] In this embodiment, the preset rule configuration file allows application parties to configure it flexibly as needed, and it remains open to new landing pages and new carriers for reporting advertising behavior. The preset interface configuration file remains open to new advertising platforms and new advertisers, offering good scalability. The advertising behavior reporting method based on this rule configuration file and interface file supports applications based on multiple programming languages ​​and can achieve advertising behavior reporting by adding call commands, demonstrating strong versatility.

[0224] Based on the foregoing embodiments, this application further provides an advertising behavior reporting device. The control device includes various modules and units included in each module, which can be implemented by a processor in an electronic device; of course, it can also be implemented by specific logic circuits. In the implementation process, the processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP), or a field programmable gate array (FPGA), etc.

[0225] Figure 8 This application provides a schematic diagram of the composition of an advertising behavior reporting device, as shown in the embodiments of the present application. Figure 8 As shown, the device 800 includes an acquisition module 801, a first determination module 802, a second determination module 803, a first filling module 804, and a reporting module 805, wherein:

[0226] The acquisition module 801 is used to acquire the application's landing page information and user conversion events;

[0227] The first determining module 802 is used to determine target configuration parameters from a preset rule configuration file based on the landing page information and the user conversion event; wherein, the rule configuration file includes advertising behavior configuration parameters for different landing page information placed on different advertising platforms with different carrier information types; the target configuration parameters include target carrier information, target advertiser ID, target click ID, and target user event type;

[0228] The second determining module 803 is used to determine the content of the advertising behavior to be filled from a preset interface configuration file based on the target carrier information; each target carrier information corresponds to one interface configuration file;

[0229] The first filling module 804 is used to write the target advertiser ID, target click ID and target user event type into the content of the advertising behavior;

[0230] The reporting module 805 is used to report the content of the advertising behavior after it has been written.

[0231] In some possible embodiments, the first determining module 802 includes a first determining unit, an acquiring unit, a second determining unit, and a searching unit, wherein: the first determining unit is used to determine a target rule configuration block from the rule configuration file based on the prefix of the landing page information; the acquiring unit is used to acquire the target carrier information from the configuration information of the target rule configuration block; the second determining unit is used to determine the target click ID and the target advertiser ID based on the landing page information and the configuration information of the target rule configuration block; and the searching unit is used to search the target rule configuration block based on the user conversion event to obtain the target user event type.

[0232] In some possible embodiments, the second determining unit includes a first parsing subunit, a first search subunit, a second search subunit, and a second parsing subunit, wherein: the first parsing subunit is used to parse the landing page information using the keywords of the target rule configuration block as parameter names to obtain the advertising platform ID; the first search subunit is used to search the target rule configuration block using the keywords of the advertising platform ID as parameter names to obtain the advertising platform identifier to which the landing page information belongs and the target advertiser ID; the second search subunit is used to retrieve the value using the advertising platform identifier as the key name and search the target rule configuration block to obtain the parameter value of the click keyword; the second parsing subunit is used to retrieve the value using the parameter value of the click keyword as the key name and parse the landing page information to obtain the target click ID.

[0233] In some possible embodiments, the search unit includes a third search subunit and a determination subunit, wherein: the third search subunit is used to obtain a value by using the advertising platform identifier as the key name, search the target rule configuration block, and obtain an array corresponding to the event mapping keywords; the determination subunit is used to determine the target user event type from the array based on the user conversion event and the landing page information.

[0234] In some possible embodiments, the first search subunit is further configured to find the grandparent node of the advertising platform ID keyword in the target rule configuration block and identify the grandparent node as the advertising platform identifier.

[0235] In some possible embodiments, the preset interface configuration file includes an interface configuration block and an account configuration block. The interface configuration block includes the content of the advertising behavior. The device 800 further includes a lookup module, a second fill module, and a third fill module, wherein: the lookup module is used to look up the access token information and access data source information corresponding to the target advertiser ID in the account configuration block; the second fill module is used to fill the access token information into the target server URL; and the third fill module is used to write the access data source information into the content of the advertising behavior.

[0236] In some possible embodiments, the reporting module 805 includes a third determining unit and an execution unit, wherein: the third determining unit is used to determine a reporting command based on the content of the written advertising behavior; and the execution unit is used to execute the reporting command to report the content of the written advertising behavior to the target server.

[0237] In some possible embodiments, the device 800 further includes a receiving module and a recording module, wherein: the receiving module is used to receive the execution result of the reporting command sent by the target server; and the recording module is used to write the execution result into a log file.

[0238] It should be noted that the descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0239] It should be noted that, in the embodiments of this application, if the above-mentioned advertising behavior reporting method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a smartphone, tablet computer, etc. with a camera) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0240] Correspondingly, embodiments of this application provide a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps in any of the advertising behavior reporting methods described in the above embodiments.

[0241] Correspondingly, in this embodiment of the application, a chip is also provided, the chip including programmable logic circuits and / or program instructions, which, when the chip is running, are used to implement the steps in any of the advertising behavior reporting methods described in the above embodiments.

[0242] Correspondingly, in this application embodiment, a computer program product is also provided. When the computer program product is executed by the processor of an electronic device, it is used to implement the steps in any of the advertising behavior reporting methods described in the above embodiments.

[0243] Based on the same technical concept, this application provides an electronic device for implementing the advertising behavior reporting method described in the above method embodiments. Figure 9 This is a hardware entity diagram of an electronic device provided in an embodiment of this application, such as... Figure 9As shown, the electronic device 900 includes a memory 910 and a processor 920. The memory 910 stores a computer program that can run on the processor 920. When the processor 920 executes the program, it implements the steps in any of the advertising behavior reporting methods described in the embodiments of this application.

[0244] The memory 910 is configured to store instructions and applications executable by the processor 920, and can also cache data to be processed or already processed by the processor 920 and various modules in the electronic device (e.g., image data, audio data, voice communication data and video communication data), which can be implemented by flash memory or random access memory (RAM).

[0245] When the processor 920 executes the program, it implements the steps of the advertising behavior reporting method described above. The processor 920 typically controls the overall operation of the electronic device 900.

[0246] The aforementioned processor can be at least one of the following: Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), Central Processing Unit (CPU), Controller, Microcontroller, and Microprocessor. It is understood that other electronic devices can also implement the functions of the aforementioned processor, and this application does not specifically limit the specific implementation.

[0247] The aforementioned computer storage media / memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; or it can be various electronic devices that include one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0248] It should be noted that the descriptions of the storage medium and device embodiments above are similar to those of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0249] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0250] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus 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 apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0251] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0252] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0253] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0254] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause the device automatic test line to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0255] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0256] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0257] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for reporting advertising behavior, characterized in that, The method includes: Retrieve application landing page information and user conversion events; Based on the landing page information and the user conversion event, target configuration parameters are determined from a preset rule configuration file; wherein, the rule configuration file includes advertising behavior configuration parameters for different landing page information placed on different advertising platforms with different carrier information types; the target configuration parameters include target carrier information, target advertiser ID, target click ID, and target user event type; Based on the target carrier information, the content of the advertising behavior to be populated is determined from the preset interface configuration file; each target carrier information corresponds to one interface configuration file. Write the target advertiser ID, target click ID, and target user event type into the content of the advertising behavior; The content of the advertising behavior after it has been written shall be reported; The step of determining the target configuration parameters from a preset rule configuration file based on the landing page information and the user conversion event includes: determining a target rule configuration block from the rule configuration file based on the prefix of the landing page information; obtaining the target carrier information from the configuration information of the target rule configuration block; determining the target click ID and the target advertiser ID based on the landing page information and the configuration information of the target rule configuration block; and finding the target user event type by searching the target rule configuration block based on the user conversion event. The step of determining the target click ID and the target advertiser ID based on the landing page information and the configuration information of the target rule configuration block includes: parsing the landing page information using the keywords of the target rule configuration block as parameter names to obtain the advertising platform ID; searching the target rule configuration block using the keywords of the advertising platform ID as parameter names to obtain the advertising platform identifier to which the landing page information belongs and the target advertiser ID; obtaining the parameter value of the click keyword using the advertising platform identifier as the key name to retrieve the value; and parsing the landing page information using the parameter value of the click keyword as the key name to obtain the target click ID. The step of finding the target user event type based on the user conversion event includes: obtaining the value by using the advertising platform identifier as the key name, searching the target rule configuration block to obtain an array corresponding to the event mapping keywords; and determining the target user event type from the array based on the user conversion event and the landing page information.

2. The method as described in claim 1, characterized in that, The step of searching the target rule configuration block using the keyword of the advertising platform ID as the parameter name to obtain the advertising platform identifier to which the landing page information belongs and the target advertiser ID includes: In the target rule configuration block, find the grandparent node of the advertising platform ID keyword; The grandfather node is identified as the advertising platform identifier.

3. The method as described in claim 1, characterized in that, The preset interface configuration file includes an interface configuration block and an account configuration block. The interface configuration block includes the content of the advertising behavior. Before the content of the advertising behavior is reported and written, the method further includes: Search the account configuration block for the access token information and access data source information corresponding to the target advertiser ID; The access token information is then populated into the target server URL; The access data source information is written into the content of the advertising behavior.

4. The method according to any one of claims 1 to 3, characterized in that, The content of the advertising behavior reported and written includes: The reporting command is determined based on the content of the written advertising behavior; Execute the reporting command to report the content of the written advertising behavior to the target server.

5. The method as described in claim 4, characterized in that, The method further includes: Receive the execution result of the reporting command sent by the target server; Write the execution results to a log file.

6. An advertising behavior reporting device, used to implement the method according to any one of claims 1-5, characterized in that, The device includes an acquisition module, a first determination module, a second determination module, a first filling module, and a reporting module, wherein: The acquisition module is used to acquire the application's landing page information and user conversion events; The first determining module is used to determine target configuration parameters from a preset rule configuration file based on the landing page information and the user conversion event; wherein, the rule configuration file includes advertising behavior configuration parameters for different landing page information placed on different advertising platforms with different carrier information types; the target configuration parameters include target carrier information, target advertiser ID, target click ID, and target user event type; The second determining module is used to determine the content of the advertising behavior to be filled from a preset interface configuration file based on the target carrier information; each target carrier information corresponds to one interface configuration file; The first filling module is used to write the target advertiser ID, target click ID, and target user event type into the content of the advertising behavior; The reporting module is used to report the content of the advertising behavior after it has been written. The first determining module is specifically used to determine the target rule configuration block from the rule configuration file based on the prefix of the landing page information; obtain the target carrier information from the configuration information of the target rule configuration block; determine the target click ID and the target advertiser ID based on the landing page information and the configuration information of the target rule configuration block; and find the target rule configuration block based on the user conversion event to obtain the target user event type. The first determining module is specifically used to parse the landing page information using the keywords of the target rule configuration block as parameter names to obtain the advertising platform ID; to search the target rule configuration block using the keywords of the advertising platform ID as parameter names to obtain the advertising platform identifier to which the landing page information belongs and the target advertiser ID; to retrieve the value using the advertising platform identifier as the key name and search the target rule configuration block to obtain the parameter value of the clicked keyword; and to parse the landing page information using the parameter value of the clicked keyword as the key name to obtain the target click ID. The first determining module is specifically used to obtain a value by using the advertising platform identifier as the key name, search the target rule configuration block, and obtain an array corresponding to the event mapping keywords; based on the user conversion event and the landing page information, determine the target user event type from the array.

7. An electronic device comprising a memory and a processor, the memory storing a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method according to any one of claims 1 to 5.

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

Images