A method for recommending a buried point and an electronic device

Abstract

A kind of burying point recommendation method and electronic equipment, it is related to computer technical field, can guide application developer to set burying point by recommended burying point related information, reduce the problem that user behavior data collection is unreasonable, not comprehensive due to setting burying point unreasonable, not comprehensive in application operation stage.Burying point recommendation method is applied in electronic equipment, and electronic equipment includes burying point knowledge base.This method includes: obtaining burying point knowledge base;For the target page to be recommended burying point, the target industry characteristics of target application to which target page belongs and the target scene characteristics of target page are obtained;According to target industry characteristics and target scene characteristics, the target burying point event corresponding to target page is obtained from burying point knowledge base.Industry characteristics corresponding to target burying point event match target industry characteristics, and the scene characteristics of target burying point event match target scene characteristics.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method for recommending data points and an electronic device. Background Technology

[0002] Currently, applications (APPs) need to collect various user behavior data during operation to analyze user interests and preferences, enabling more accurate and efficient user operations and content operations for APP products. To more accurately analyze user interests and preferences, it's necessary to use event tracking within the APP to collect user behavior data at different locations on the page.

[0003] Currently, commonly used data tracking methods include visual tracking and full tracking. However, these methods all have certain problems, resulting in incomplete collection of user behavior data. In app operation, issues such as unreasonable or incomplete tracking often arise. For example, tracking points should be set at some target locations, but developers may not have actually set them. Therefore, even if a user performs actions such as clicking at those target locations, user behavior data cannot be collected. Summary of the Invention

[0004] This application provides a method and electronic device for recommending event tracking points, which can guide APP developers to set up event tracking points through recommended event tracking information, thereby reducing the problem of unreasonable or incomplete collection of user behavior data caused by unreasonable or incomplete event tracking point settings during the APP operation phase.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, a method for recommending event tracking is provided. This method includes: acquiring an event tracking knowledge base; the knowledge base includes at least one event tracking point, and the correspondence between the event tracking point and the industry characteristics of the application and the scene characteristics of the page; for a target page to be tracked, acquiring the target industry characteristics of the target application to which the target page belongs and the target scene characteristics of the target page; based on the target industry characteristics and the target scene characteristics, acquiring the target event tracking point corresponding to the target page to be tracked from the knowledge base; the industry characteristics corresponding to the target event tracking point match the target industry characteristics, and the scene characteristics of the target event tracking point match the target scene characteristics; the target event tracking point is used to guide the user to set up event tracking for the target page.

[0007] The method provided in this application can obtain the corresponding event tracking points for a target page from a pre-built event tracking knowledge base based on the industry characteristics of the target application and the scenario characteristics of the target page on the target application. During the target application development phase, suggestions for event tracking on the target application pages can be provided to the first type of users, such as the target application's administrators and developers. This event tracking recommendation method enables the first type of users to set up event tracking points more comprehensively during the target application development phase, thereby reducing the problem of unreasonable and incomplete user behavior data collection caused by incomplete event tracking points during the target application operation phase.

[0008] Especially for inexperienced first-time users, this event tracking recommendation method can also reduce the problem of incomplete event tracking caused by their lack of experience.

[0009] Specifically, the basic information includes application information of the target application and page information of at least one application page within the target application. Furthermore, the application information includes one or more of the following: application name, application identifier, application description, application version number, and application type; the page information includes one or more of the following: page screenshot, page identifier, page name, and page description information.

[0010] In other words, the above methods can determine target industry characteristics and scenario characteristics based on only one piece of information from the application information and one piece of information from the page information. Alternatively, they can determine target industry characteristics and scenario characteristics based on several pieces of information from the application information and several pieces of information from the page information, and the target industry characteristics and scenario characteristics determined by combining multiple pieces of information are more accurate.

[0011] In one possible design approach of the first aspect, before obtaining the target industry characteristics of the target application to which the target page belongs and the target scene characteristics of the target page for the target page to be recommended, the above method may also obtain basic information of the target application; wherein, the target application includes at least one application page, and the at least one application page includes the target page; then, based on the basic information of the target application, the target industry characteristics of the target application are determined, and the scene characteristics of each application page in the at least one application page are determined; the scene characteristics of each application page in the at least one application page include the target scene characteristics of the target page.

[0012] In this design approach, the first type of user inputs page information from multiple pages on the target application, thereby obtaining the scene characteristics corresponding to each of the multiple application pages.

[0013] In one possible design approach of the first aspect, when the above method obtains the target industry characteristics of the target application to which the target page belongs and the target scene characteristics of the target page for the target page to be recommended, it can obtain the target industry characteristics and the target scene characteristics of the target page from the determined target industry characteristics of the target application and the scene characteristics of each page in at least one application page.

[0014] In this design approach, when the first type of user obtains the target event, they can specify a target page from multiple application pages, and then obtain the target scene features corresponding to the current target page from the scene features of at least one application page.

[0015] In one possible design approach of the first aspect, when determining the target industry characteristics of the target application, the above method can first perform semantic recognition on the application information in the basic information to obtain the application semantic content. Then, based on the application semantic content, the target industry characteristics of the target application are determined. For example, if the recognized semantic content is "WeChat",... TM "Then the tracking recommendation platform can determine the target industry characteristics of the target application as social communication type."

[0016] In this design approach, the semantic content of the application can be identified through automatic recognition, thereby determining the characteristics of the target industry. This automated recognition method can speed up the feature recognition process, thus saving the overall time of the event tracking and recommendation process.

[0017] In one possible design approach of the first aspect, when determining the scene characteristics of an application page, the above method can first perform semantic and image recognition on the page information to obtain the semantic content and UI elements of the application page. Then, based on the semantic content and UI elements, the scene characteristics of the application page are determined. For example, if the identified semantic content is specific product description content, and the identified UI element is an "Add to Cart" button, then the scene characteristics of the application page can be determined as a product details page.

[0018] In this design approach, the semantic content and UI elements of the page can be identified automatically to determine the characteristics of the target scene. This automated identification method can speed up the feature identification process, thereby saving the overall time of the event tracking and recommendation process.

[0019] In one possible design approach of the first aspect, the application information may further include only pre-set first identification information, which indicates the target industry characteristics corresponding to the target application. The pre-set first identification information is user-inputted information. That is, the first type allows direct input of the target industry characteristics of the target application. In this case, when determining the target industry characteristics of the target application, the above method can directly obtain the target industry characteristics from the application information within the basic information.

[0020] This design approach eliminates the need for automatic identification of target industry characteristics, thus avoiding the problem of inaccurate identification results caused by automatic feature identification.

[0021] In one possible design approach of the first aspect, the page information may further include only pre-set second identification information, which indicates the scene characteristics corresponding to each application page in at least one application page. The pre-set second identification information is user-inputted information. That is, the first type allows direct input of the page's scene characteristics. In this case, when determining the scene characteristics of an application page, the above method can directly obtain the scene characteristics from the page information within the basic information.

[0022] This design approach eliminates the need for automatic identification of target scene features, thus avoiding the problem of inaccurate identification results caused by automatic feature identification.

[0023] In one possible design approach of the first aspect, when retrieving target event information corresponding to the target page from the event tracking knowledge base based on target industry characteristics and target scenario characteristics, the above method can first retrieve at least one target event tracking event that matches the target industry characteristics and target scenario characteristics from the event tracking knowledge base. Then, the at least one target event tracking event is sorted from high to low according to the matching degree between the target event tracking event and the target page to obtain the target event tracking event.

[0024] In this design approach, if a large number of target event tracking points are matched from the event tracking knowledge base, these events can be sorted according to their matching degree. When displaying target event tracking points to the first type of user, the target event tracking point with the highest matching degree can be displayed first. This allows the first type of user to more intuitively see the target event tracking points that are more closely matched to the current target page, and thus set the event tracking points more accurately based on the more closely matched target event tracking points.

[0025] The industry characteristics of the target event tracking include at least one level of classification items, and the scenario characteristics of the target event tracking include at least one feature item. The industry characteristics are used to represent the industry type of the business involved in the application, and the scenario characteristics are used to represent the page type and the UI elements displayed on the page, etc.

[0026] The above method can match target event tracking events with the same category items in the tracking knowledge base based on the category item content of each level of the target industry characteristics. When the tracking event to be matched in the tracking knowledge base only includes a first-level category item, it is only necessary to match the content of this first-level category item with the corresponding level of category item content in the target industry characteristics. If they are the same, the scene features in the tracking event are then matched. When the scene features in the tracking event only include one feature item, only the content of this one feature item can be matched with the corresponding feature item content in the target scene. If they are the same, the tracking event can be identified as the target tracking event.

[0027] When the industry characteristics of the event to be matched in the event tracking knowledge base include multi-level classification items, the content of each level of classification item can be matched with the corresponding level of classification item content in the target industry characteristics. If at least one of the classification item contents is the same, then the scene characteristics in the event tracking can be matched. When the scene characteristics in the event tracking include multiple feature items, the content of each feature item can be matched with the feature item content corresponding to the target scene characteristics. If at least one of the feature item contents is the same, then the event tracking can be identified as the target event tracking.

[0028] In one possible design approach of the first aspect, after obtaining at least one target tracking event matching the target industry characteristics and target scenario characteristics from the tracking knowledge base, the method further includes: determining the number of category items in the target tracking event that are identical to the target industry characteristics, and the number of feature items in the target tracking event that are identical to the target scenario characteristics. The matching degree between the target tracking event and the target page is determined based on the sum of the number of category items and the number of feature items.

[0029] In this design approach, a higher degree of matching between the target event and the target page indicates that the industry characteristics of the target application and the scenario characteristics of the target page are more similar to or closer to the industry and scenario characteristics of the target event. This means the target event is also more likely to meet the current target page's event tracking requirements or rules. The target event with a higher degree of matching is recommended to the first type of user, allowing them to set up event tracking more accurately based on the more relevant recommendations.

[0030] In one possible design approach of the first aspect, when acquiring the event tracking knowledge base in the above method, user behavior data from applications with different industry characteristics can also be collected. This user behavior data includes UI elements interacting with the application pages by users of the second type. Then, user behavior data belonging to the same industry characteristic is categorized according to the scenario characteristics of the application pages, determining event tracking events for the same industry characteristic and the same scenario characteristic, and ensuring that these event tracking events correspond to the UI elements in the user behavior data. Finally, the event tracking events are used to construct the event tracking knowledge base.

[0031] This design approach allows for the construction of a global event tracking knowledge base based on all applications across various industries and scenarios, along with user behavior data from those applications. This knowledge base provides a more comprehensive range of event tracking events, covering a broad spectrum of industries and scenarios, enabling the creation of more accurate tracking suggestions for target pages within target applications.

[0032] In one possible design approach of the first aspect, when obtaining basic information about the target application, the above method can first display the application management page. Then, it can obtain the application information of the target application entered by the first type of user on the application management page.

[0033] In this design approach, the first type of user can clearly and intuitively understand what application information needs to be entered on this application management page, obtain more application information, and thus more accurately determine the target industry characteristics of the target application.

[0034] In one possible design approach of the first aspect, when obtaining basic information about the target application, the method can also respond to the action of the first type of user clicking the application page management entry on the application management page, and display the application page management page. Then, it obtains the page information of each application page in at least one application page of the target application entered by the first type of user on the application page management page.

[0035] In this design approach, the first type of user can clearly and intuitively understand what page information needs to be entered on this application page management page, obtain more page information, and thus more accurately determine the target scene characteristics of the target page.

[0036] In one possible design approach of the first aspect, after obtaining the target event, the above method can also display the target event to guide the user to set up event tracking for the target page.

[0037] In this design approach, the first type of user can determine the location where the tracking points need to be set on the target page based on the displayed target tracking events, thereby improving the accuracy of tracking point settings.

[0038] In one possible design approach of the first aspect, after retrieving the target tracking events corresponding to the target page from the tracking knowledge base based on the characteristics of the target industry and the target scenario, the method can also retrieve the target user interface (UI) elements on the target page specified by the user. Then, it retrieves the target tracking events corresponding to the target UI elements from the target tracking events. Finally, it displays the target tracking events corresponding to the target UI elements to guide the user in setting up tracking points for the target application interface (UI) elements on the target page.

[0039] In this design approach, the first type of user can obtain the target event tracking corresponding to the target user interface UI element on the target page, and thus set the tracking points more accurately on the target page.

[0040] In one possible design approach of the first aspect, the obtained target event includes an event description and event parameters, and the target event is used to enable the first type of user to generate corresponding event configuration information for the target user interface UI element on the target page based on the event description and event parameters.

[0041] In this design approach, the target event tracking can not only indicate to the first type of user the UI elements on the target page where tracking can be performed, but also explain to the first type of user the conditions under which tracking can be performed, and provide specific parameters for the tracking operation. Based on the event description and parameters, the first type of user can more accurately set up tracking and generate tracking configuration information.

[0042] In a second aspect, an electronic device is provided, comprising: a memory and one or more processors; the memory and the processors are coupled; wherein the memory stores computer program code, the computer program code including computer instructions, and when the computer instructions are executed by the processor, the electronic device performs the tracking recommendation method described in any of the first aspects above.

[0043] Thirdly, a computer-readable storage medium is provided, including computer instructions that, when executed on an electronic device, cause the electronic device to perform the tracking point recommendation method described in any of the first aspects above.

[0044] Fourthly, a computer program product is provided, which, when run on a computer, causes the computer to execute the tracking recommendation method described in any of the first aspects above.

[0045] It is understood that the beneficial effects achieved by the electronic device described in the second aspect, the computer-readable storage medium described in the third aspect, and the computer program product described in the fourth aspect can be referred to in the beneficial effects of the first aspect and any of its possible design embodiments, and will not be repeated here. Attached Figure Description

[0046] Figure 1 This illustration shows a structural schematic diagram of an electronic device provided in an embodiment of this application;

[0047] Figure 2 A schematic diagram of a first partitioning method for the software system of the electronic device 100 in an embodiment of this application is shown;

[0048] Figure 3 A schematic diagram of a second partitioning method for the software system of the electronic device 100 in an embodiment of this application is shown;

[0049] Figure 4 A flowchart illustrating a method for recommending event tracking points provided in an embodiment of this application is shown.

[0050] Figure 5 This illustration shows a structural diagram of a tracking event in the tracking knowledge base provided in an embodiment of this application;

[0051] Figure 6 This illustration shows a schematic diagram of an application management page on the tracking display platform provided in an embodiment of this application;

[0052] Figure 7 This illustration shows a schematic diagram of an application page management page on the tracking display platform provided in an embodiment of this application;

[0053] Figure 8 A flowchart illustrating another method for recommending event tracking points provided in an embodiment of this application is shown.

[0054] Figure 9 This illustration shows another application management page on the tracking point display platform provided in this application embodiment;

[0055] Figure 10 This illustration shows another application page management page on the tracking display platform provided in this application embodiment;

[0056] Figure 11 This illustration shows a schematic diagram of an element marker page provided in an embodiment of this application;

[0057] Figure 12 This illustration shows a target page provided in an embodiment of this application;

[0058] Figure 13 This illustration shows a schematic diagram of the target event obtained through the event tracking recommendation platform according to an embodiment of this application;

[0059] Figure 14 This illustration shows a schematic diagram of a tracking point recommendation page on the tracking point display platform provided in an embodiment of this application. Detailed Implementation

[0060] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0061] Currently, apps need to collect various user behavior data during operation to analyze user interests and preferences. This allows for more accurate and efficient user operations and content management. To more accurately analyze user interests and preferences, it's necessary to use event tracking within the app to collect user behavior data at different locations on the page.

[0062] Currently, commonly used methods for data collection include visual data collection methods and full data collection methods.

[0063] In the visual event tracking method, a visual event tracking tool is first pre-configured on the mobile device. Then, after the server sends the event tracking rules to the mobile device, the device uses the visual event tracking tool to collect user behavior data according to these rules. This method can collect user behavior data in different locations. However, during app operation, if it's discovered that some locations requiring event tracking are not being tracked, the server can modify the event tracking rules for those locations. After the rules are modified, the event tracking on the mobile device needs to be reconfigured according to the new rules.

[0064] In the full-tracking method, tracking points are first implemented on various UI elements of the mobile app, and tracking rules are defined. Then, user click behavior data on UI elements is collected at each tracking point according to the tracking rules and reported to the server. This full-tracking method can also collect user behavior data in different locations, but when the tracking rules change, the app needs to be recompiled and re-released. The new tracking rules can only be applied after mobile users upgrade the app.

[0065] Based on the above, it's clear that current commonly used event tracking methods often fail to include event tracking at certain target locations during app operation. This means that even if users generate behavioral data at these locations, the mobile app cannot collect this data. Furthermore, if event tracking is reset or the rules are changed, the mobile app will also be unable to collect user behavioral data during the reset or rule change period. Therefore, current event tracking methods easily lead to incomplete event tracking within apps, resulting in an inability to comprehensively collect user behavioral data during app operation.

[0066] This application provides a method for recommending event tracking points. During the app development phase, it can combine app application information, page information on app pages, and a pre-built event tracking knowledge base to provide suggestions for setting event tracking points on app pages to app developers and other users. These users then set event tracking points on app pages based on these suggestions. This method ensures more comprehensive event tracking point setup during app development, thereby reducing the problem of incomplete user behavior data collection during app operation due to incomplete event tracking.

[0067] This application provides a method for recommending event tracking points, which can be applied to an electronic device 100. Specifically, the electronic device 100 can be a server, a personal computer (PC), or other such device or apparatus. Taking an electronic device 100 as a server as an example... Figure 1As shown, the electronic device 100 may include one or more processors 1001, memory 1002 and communication interface 1003.

[0068] The memory 1002, communication interface 1003, and processor 1001 are coupled together. For example, the memory 1002, communication interface 1003, and processor 1001 can be coupled together via bus 1004.

[0069] The communication interface 1003 is used for data transmission with other devices. The memory 1002 stores computer program code. The computer program code includes computer instructions, which, when executed by the processor 1001, cause the server to perform the data tracking recommendation method described in this embodiment.

[0070] The aforementioned memory 1002 can also be used to store basic information about the application obtained by the tracking recommendation method, such as application information and page information.

[0071] The processor 1001 can be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), 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 invention. The processor can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0072] Bus 1004 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Bus 1004 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 1 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.

[0073] For example, the server may include one or more processors 1001, that is, the server may include a multi-core processor.

[0074] In some embodiments, the server may also include a display. Specifically, the display is used to show basic information about the application. The display may be integrated with other components of the server; alternatively, it may not be integrated with other components of the server, but may be connected to them.

[0075] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0076] In this embodiment of the application, the software system of the electronic device 100 can be divided in two ways.

[0077] Figure 2 This diagram illustrates a first partitioning method for the software system of the electronic device 100 in an embodiment of this application. For example... Figure 2 As shown, the software system includes an application management module 201, a tracking knowledge base 203, a tracking recommendation module 202, a semantic recognition module 204, an image recognition module 205, etc.

[0078] The application management module 201 can be used to obtain basic information such as application information and page information of the target application input by the first type of user, and send the basic information to the tracking recommendation module 202; in addition, the application management module 201 can also be used to save the basic information of each version of the APP, and can also bind and save the APP with its corresponding industry characteristics and scenario characteristics, so as to manage different versions of the APP. When the APP is updated, the first type of user can also obtain the basic information, industry characteristics and scenario characteristics of the old version of the APP from the application management module 201.

[0079] The event tracking recommendation module 202 can be used to construct an event tracking knowledge base 203 based on the behavior data of the second type of users on the global APP and the APP page information associated with the behavior data; and the event tracking recommendation module 202 can also obtain event tracking recommendation information of the target page in the target application from the event tracking knowledge base 203 based on the basic information of the target application obtained by the application management module 201.

[0080] Specifically, the tracking recommendation module 202 can identify semantic content from the application information in the basic information through the semantic recognition module 204, and determine the industry characteristics of the target application based on the semantic content; and the tracking recommendation module 202 can also identify semantic content from the page information in the basic information through the semantic recognition module 204, and determine the page characteristics of the target page of the target application based on the semantic content; and the image recognition module 205 can identify UI elements from the page screenshots in the page information, and determine the UI element characteristics of the target page based on the UI elements.

[0081] Figure 3 A schematic diagram illustrating a second partitioning method for the software system of the electronic device 100 in an embodiment of this application is shown. For example... Figure 3 As shown, the software system includes a tracking point recommendation platform 301 and a tracking point display platform 302. The tracking point display platform 302 can provide peripheral or front-end pages to the first type of users, such as APP developers and administrators. These users input basic information about the APP on the peripheral or front-end pages, and the tracking point display platform 302 sends this information to the tracking point recommendation platform 301 for processing. This basic information includes application information for the APP and page information for pages within the APP.

[0082] The event tracking recommendation platform 301 can pre-build a global event tracking knowledge base based on user behavior data (including user and experience data of the second type of users) and information and UI elements on the app pages when these users generate behavior data. The platform then determines relevant app features based on the basic information input by the first type of users and retrieves event tracking recommendation information for a specific page on the app from the event tracking knowledge base. These relevant features include industry characteristics of the app and scene characteristics of the pages on the app.

[0083] Finally, the event tracking recommendation platform 301 sends the acquired event tracking recommendation information to the event tracking display platform 302, which then displays the event tracking recommendation information to the first type of users on the outer page or front-end page of the event tracking display platform 302. The event tracking recommendation information is used to provide event tracking suggestions to the first type of users. For example, event tracking can be set at a certain location on the page or at a certain UI element location to collect behavioral data generated by the second type of users at that event tracking location and page information related to the behavioral data.

[0084] For example, after a first-type user enters basic information about the app on the tracking display platform 302, the tracking recommendation platform 301 determines that the app is a shopping app and that the page for which tracking information needs to be recommended is the product details page. The tracking recommendation platform 301 then determines the corresponding tracking recommendation information for the product details page in the shopping app from the tracking knowledge base. Specifically, the tracking recommendation information may include adding tracking points at the first UI element position at the bottom of the product details page, setting tracking points at the second UI element position, and setting tracking points at the third UI element position, etc. The first-type user can refer to the tracking recommendation information based on the actual content and information of the page on the app and choose whether to set tracking points at the corresponding positions on the page of the app.

[0085] The methods of this application are described below with reference to the accompanying drawings and specific embodiments.

[0086] Figure 4 This diagram illustrates a flowchart of a tracking point recommendation method provided in an embodiment of this application. Figure 4 As shown, the method for recommending event tracking points may include the following steps S401-S407.

[0087] S401, Electronic device 100 acquires the knowledge base of data collection points.

[0088] Specifically, step S401 can be executed by the event tracking recommendation module 202 in the electronic device 100, or by the event tracking recommendation platform 301 in the electronic device 100. In the following embodiments, the method of constructing the event tracking knowledge base is described using the event tracking recommendation platform 301 executing step S401 as an example. Both the operations performed by the event tracking recommendation module 202 and the operations performed by the event tracking recommendation platform 301 are operations performed by the electronic device 100.

[0089] The tracking knowledge base is a global knowledge base built by the tracking recommendation platform 301 based on the behavioral data of the second type of users across all apps and the app page information associated with that behavioral data. Here, "global apps" refers to all apps covering various industries and scenarios; the behavioral data of the second type of users refers to the click, drag, and touch operations performed by them on a specific page of an app within a specific industry; and the app page information associated with that behavioral data refers to the UI elements clicked, dragged, or touched by the second type of users on the app page, the positions of those UI elements, and the associated information.

[0090] For example, e-commerce apps fall under the category of price comparison shopping apps. Given these characteristics, the data collection and recommendation platform 301 needs to collect behavioral data on user behaviors such as searching for products, viewing results, placing orders, adding items to carts, sharing products, and sharing the app. If a user shares a product within the app, the platform also needs to obtain the UI elements clicked by that user, their locations, and associated information. Specifically, if a user clicks the "share" button, the "share" button becomes the UI element the platform needs to acquire, and its location represents the UI element's position. Furthermore, if the user chooses to share the product to other chat applications, those other chat applications become the associated information for the UI element.

[0091] Furthermore, if the second type of user claims a coupon on the app, then the 301 tracking platform also needs to obtain information such as the UI elements clicked by the second type of user when claiming the coupon, the location of the UI elements, and the association information of the UI elements. Specifically, if the second type of user clicks the "Claim Coupon" button, then the "Claim Coupon" button is the UI element that the 301 tracking platform needs to obtain; the location of the "Claim Coupon" button is the location of the UI element; and the specific coupon content obtained after the second type of user clicks the "Claim Coupon" button is the association information of the UI element.

[0092] The event tracking knowledge base can be built using the event tracking recommendation platform 301. When building the knowledge base, the platform can define the business industry types involved in the app as the app's industry characteristics, and the business scenario types involved in each page of the app as the page's scenario characteristics. Industry characteristics can also be categorized in a multi-level manner; that is, a broad industry characteristic can include multiple more specific industry characteristics with smaller industry scopes.

[0093] For example, the industry types involved in an app can include primary, secondary, and tertiary categories. Correspondingly, the industry characteristics of an app can also include multi-level categories such as the aforementioned primary, secondary, and tertiary categories. Primary categories can include non-game app types and game app types, etc. Secondary categories under the non-game app category level might include shopping comparison apps, social communication apps, etc., and tertiary categories under the shopping comparison app category level might include discount apps, online stores, group buying apps, etc.

[0094] For example, the scene characteristics of an app page can include multiple features such as page features and UI element features. Page features can be determined based on the page type; for instance, in an e-commerce application, page features could include product detail pages, search pages, and settings pages. UI element features can be determined based on the functions of the UI elements displayed on the page; for example, on a product detail page, UI elements that can be displayed include "share" buttons and "add to cart" buttons, so the characteristics of these UI elements could include "share" and "add to cart."

[0095] The event tracking recommendation platform 301 first categorizes collected user behavior data based on the industry characteristics of the application to which the user behavior data belongs. Then, it further categorizes user behavior data belonging to the same industry based on the scenario characteristics of the page to which the user behavior data belongs. In this way, the event tracking recommendation platform 301 can identify event tracking points belonging to a specific industry characteristic and a specific scenario characteristic for user behavior data belonging to both the same industry and scenario characteristics. Finally, the event tracking recommendation platform 301 uses all the event tracking points to build an event tracking knowledge base.

[0096] In the event tracking knowledge base, each event has identifiers such as industry characteristics, scenario characteristics, event name, and event parameters. Specifically, the event name can be used to represent the function of a UI element, and the event parameters can be used to specify the standards or rules used when setting up event tracking.

[0097] For example, Figure 5 This illustration shows a structural diagram of a tracking event in the tracking knowledge base provided in an embodiment of this application. For example... Figure 5 As shown, in the event tracking knowledge base, the industry characteristics corresponding to a certain event tracking point are: the first-level category is "non-game applications" and the second-level category is "shopping price comparison"; the scene characteristics are: the page characteristic is "product details page" and the UI element characteristic is "sharing"; the event name of this event tracking point is "Share", and the event parameters corresponding to this event tracking point include type (content type) and name (content name), etc.

[0098] In some embodiments, after collecting and analyzing user behavior data and UI element association information, the event recommendation platform 301 can also configure corresponding event descriptions for each event to provide reference opinions on event tracking for the first type of users.

[0099] For example, the above Figure 5The event tracker named "Share" shown in the image could have a description such as "Add this tracker when sharing content." When the first type of user sees this event description, they can consider whether to set a tracker at the location of that UI element based on the actual UI element on the currently developed app page and the function of that UI element.

[0100] In the above embodiments, the event tracking recommendation platform 301 can construct a global event tracking knowledge base based on all apps across various industries and scenarios, and the user behavior data on these apps. In such an event tracking knowledge base, event tracking events are more comprehensive, and the industries and scenarios involved are quite broad, enabling the provision of more accurate event tracking suggestions for target pages on target applications.

[0101] Furthermore, the aforementioned event tracking knowledge base can be updated. When the business content or requirements of an industry change, or when the structure or content of a page on an app within that industry changes, the behavior of the second type of user on the corresponding app may also change. Consequently, the collected behavioral data of the second type of user and related information will differ from previously collected behavioral data and information. After collecting the changed behavioral data and related information, new event tracking points can be determined based on the new behavioral data and related information, thereby updating the event tracking knowledge base.

[0102] In some embodiments, the event tracking knowledge base may also be built by other devices or apparatuses. In this case, the electronic device 100 can obtain the event tracking knowledge base from other devices or apparatuses. Specifically, when other devices or apparatuses build the event tracking knowledge base, they can also refer to the construction process described above.

[0103] S402, Electronic device 100 acquires basic information about the target application.

[0104] Specifically, step S402 can be executed by the application management module 201 of the electronic device 100, or by the tracking point display platform 302 in the electronic device 100. In the following embodiments, the method of obtaining basic information is described by taking the tracking point display platform 302 executing step S402 as an example. The operations performed by the application management module 201 and the tracking point display platform 302 are both operations performed by the electronic device 100.

[0105] The event tracking display platform 302 can obtain basic information about the target application so that the event tracking recommendation platform 301 can obtain the target industry characteristics of the target application and the scene characteristics of the application page in the target application based on the basic information.

[0106] In some embodiments, the basic information of the target application may be input by a first type of user on the event tracking display platform 302. In this case, the event tracking display device 302 can collect the basic information of the target application input by the first type of user.

[0107] The target application refers to the app that the first type of user wants to develop or an app that has already been developed and is operating. The target application includes at least one application page, and its basic information includes both application details and page information for at least one application page. The first type of user inputs page information from multiple pages within the target application, thereby obtaining the scene characteristics corresponding to each of these application pages.

[0108] In some embodiments, the tracking display platform 302 provides a display page (i.e., the peripheral page or front-end page mentioned in the foregoing embodiments) for a first type of user to input basic information. The first type of user inputs application information and page information at the corresponding positions on the display page.

[0109] Specifically, application information may include the target application's application name, application ID (identity document), application description, version number, and application type. The application name and application ID can be used to distinguish apps; the application description describes the app's features, industry information, etc.; the version number is used to categorize and manage screenshots uploaded by users (the first category); and the application type identifies the platform on which the app runs, such as Android. TM Platform, iOS TM Platform, HarmonyOS TM Platforms, etc.

[0110] Page information may include screenshots of the application page in the target application, page identifier (or page ID), page name, and page description. The page screenshot corresponds to the application version number; both the page ID and page name can be used to distinguish pages, and the page name can also describe the page's function and purpose; the page description describes the page's features, contextual information, and other relevant details.

[0111] In some embodiments, the event tracking platform 302 can provide an application management page for a first type of user, used to collect application information input by the first type of user. Furthermore, the application management page includes an entry point for application page management. When a first type of user clicks this entry point on the application management page, the event tracking platform 302 responds to the click operation and continues to display the application page management page to collect page information input by the first type of user.

[0112] For example, Figure 6This diagram illustrates an application management page on a data tracking display platform provided according to an embodiment of this application. For example... Figure 6 As shown, in addition to the area for entering application information, the application management page also displays screenshots of pages within the application at the bottom of the page, and provides entry points for application page management, such as the "Add Page" button. After the first type of user clicks the "Add Page" button, the event tracking platform further displays the application page management page.

[0113] For example, Figure 7 This diagram illustrates an application page management page on a tracking display platform provided according to an embodiment of this application. For example... Figure 7 As shown, on the application page management page, the first type of user can choose to upload a screenshot of the corresponding page and enter the relevant information for the screenshot. After entering the screenshot information, the first type of user clicks the "Submit" button, and the event tracking platform displays a 302 error again. Figure 6 The application management page shown will now display a screenshot at the location indicated by the screenshot.

[0114] In the above embodiments, the tracking display platform 302 can provide an external page or a front-end page. On this page, the first type of user can clearly and intuitively understand which application information and / or which page information needs to be entered, enabling the tracking display platform 302 to obtain more application information and / or page information, thereby enabling the tracking recommendation platform 301 to more accurately determine the target industry characteristics of the target application and the scene characteristics of the application page.

[0115] It is worth noting that in this embodiment, the page screenshots and page information added to the application management page corresponding to a specific target application are all part of that target application. That is, if a first-type user account wants to obtain the tracking recommendation information of a certain page on the target application during the APP development stage, it needs to first enter the application information of the target application, and then enter the page information of the target page in the target application.

[0116] S403, Electronic device 100 determines the target industry characteristics of the target application and the scene characteristics of each page in the target application based on the collected basic information of the target application.

[0117] Specifically, step S403 can be executed by the event tracking recommendation module 202 in the electronic device 100, or by the event tracking recommendation platform 301 in the electronic device 100. In the following embodiments, the method of obtaining target industry features and target scenario features is described using the event tracking recommendation platform 301 executing step S403 as an example. Both the operations performed by the event tracking recommendation module 202 and the operations performed by the event tracking recommendation platform 301 are operations performed by the electronic device 100.

[0118] In this embodiment, the basic information of the target application includes application information and page information of at least one page within the target application. First, the event tracking recommendation platform 301 can determine the target industry characteristics of the target application based on its application information, and determine the scene characteristics of each page based on the page information of each page within the at least one page. Then, the event tracking recommendation platform 301 determines the target page for event tracking selected by the first type of user from the at least one page. Finally, the event tracking recommendation platform 301 obtains the target scene characteristics corresponding to the target page from the scene characteristics of the at least one page.

[0119] Specifically, the first type of user can enter one or more of the following application information on the tracking display platform 302: application name, application ID, application description, version number, application type, etc.

[0120] Industry characteristics are used to indicate the industry type of the business involved in the APP, and can include multiple categories. For example, the categories include, but are not limited to: primary categories (such as non-game type, game type, etc.), secondary categories (such as social communication type, shopping comparison type, etc.), and tertiary categories (such as discount type, e-commerce type, group buying type, etc.).

[0121] When the first type of user inputs only one item of application information, the event tracking recommendation platform 301 can determine the target industry characteristics of the target application based solely on this single item. For example, for some popular and widely used target applications, the first type of user only needs to input the application name, and the event tracking recommendation platform 301 can accurately determine the target industry characteristics of the target application. For example, WeChat. TM Applications, Weibo TM Applications, QQ TM Applications, etc., the 301 tracking recommendation platform can determine the target industry characteristics of the application simply by these application names: the primary category is non-game application type, and the secondary category is social communication type.

[0122] For some target applications with a small audience and limited usage scope, the tracking recommendation platform 301 cannot accurately determine the target industry characteristics based solely on the application name. Therefore, in some embodiments, the tracking recommendation platform 301 can also determine the target industry characteristics of the target application based on multiple or all of the aforementioned application information, thereby making the determined industry characteristics more accurate.

[0123] Scene features are used to represent page types and UI element characteristics displayed on pages within an app, and can include multiple feature items. For example, feature items include, but are not limited to, page features (such as product detail pages) and UI element features (such as "share").

[0124] In some embodiments, the first type of user can also input one or more of the following page information on the event tracking display platform 302: a screenshot of the application page, a page identifier, a page name, and a page description. The event tracking recommendation platform 301 can determine the scene characteristics of the application page based on any one of the page information items. However, this method may result in inaccurate scene characteristics due to the limited amount of information used. Therefore, in some embodiments, the event tracking recommendation platform 301 can also determine the scene characteristics of the application page based on multiple or all of the aforementioned page information items, thereby making the determined scene characteristics more accurate.

[0125] In practical applications, the event tracking recommendation platform 301 may determine multiple industry features corresponding to the target application based on the application information; or it may determine multiple scene features corresponding to the application page based on the page information. When a target application corresponds to multiple industry features, or an application page corresponds to multiple scene features, the event tracking recommendation platform 301 has difficulty determining which specific industry feature or scene feature to use to ultimately obtain the corresponding event tracking recommendation information.

[0126] Therefore, in some embodiments, when the tracking recommendation platform 301 determines that the target application corresponds to more than one industry feature, the tracking recommendation platform 301 can send all the determined industry features to the tracking display platform 302 for display, thereby prompting the first type of user to select the target industry feature from all the candidate industry features. Alternatively, when the tracking recommendation platform 301 obtains that the target page corresponds to more than one target scene feature, the tracking recommendation platform 301 can send all the determined target scene features to the tracking display platform 302 for display, thereby prompting the first type of user to select the target scene feature that meets the requirements from all the candidate target scene features.

[0127] In some embodiments, when determining target industry characteristics and target scenario characteristics based on the basic information of the target application, the event tracking recommendation platform 301 can utilize content recognition to identify specific content from the basic information of the target application, thereby determining the target industry characteristics and target scenario characteristics based on the identified content. Based on this, see [link to relevant documentation]. Figure 8 The above step S403 may also specifically include the following steps S403a-S403d.

[0128] S403a and the tracking recommendation platform 301 perform semantic recognition on the application information in the basic information to obtain the application semantic content.

[0129] Specifically, the 301 tracking recommendation platform can identify application name, application ID, application description, version number, application type, etc. in entity application information. The specific content identified is the application semantic content.

[0130] S403b and the tracking recommendation platform 301 determine the target industry characteristics of the target application based on the semantic content of the application.

[0131] Specifically, the event tracking recommendation platform 301 can analyze the semantic content of the application to determine the target user group, the application's function, its features, and its application domain. Then, based on the analyzed content, the event tracking recommendation platform 301 determines the industry characteristics of the target application.

[0132] For example, the event tracking recommendation platform 301 identified the target application's application name as "WeChat". TM If the tracking point recommendation platform 301 identifies the target application's industry characteristics as follows: the primary category is non-game application type, and the secondary category is social communication type. Alternatively, if the tracking point recommendation platform 301 identifies the target application's description as "used for publishing information and images, and for instant communication with other users," then based on this identified description, the target application's function can be determined as "communication and content publishing." Based on this function, the tracking point recommendation platform 301 can determine the target application's industry characteristics as follows: the primary category is non-game application type, and the secondary category is social communication type.

[0133] S403c and the tracking recommendation platform 301 perform semantic and image recognition on the page information in the basic information to obtain the page's semantic content and image content.

[0134] Specifically, the tracking point recommendation platform 301 performs image recognition on page screenshots in the page information. The recognized image content can include UI elements and other content on the image. Furthermore, the tracking point recommendation platform 301 performs semantic recognition on content other than page screenshots in the page information, such as page identifiers, page names, and page descriptions. The specific content identified is the semantic content of the page.

[0135] S403d and the tracking recommendation platform 301 determine the scene characteristics of the page in the target application based on the semantic content and image content of the page.

[0136] It's worth noting that when the target application includes more than one page, the event tracking recommendation platform 301 also needs to perform semantic and image recognition on each page to obtain the semantic and image content corresponding to each page. Then, the event tracking recommendation platform 301 determines the scene features of each page based on the semantic and image content corresponding to each page.

[0137] Specifically, the scene characteristics of a page include page features and UI element features. The 301 tracking recommendation platform can determine page features based on the semantic content of the page, then determine UI elements based on the image recognition results of the page screenshots, and finally determine UI element features based on the function or content of the UI elements.

[0138] For example, if the tracking and recommendation platform 301 identifies the page name as "product details page," then the tracking and recommendation platform 301 can directly determine the page's characteristics as a product details page. Alternatively, if the tracking and recommendation platform 301 identifies the page description as "used to specifically describe product information," then based on this identified description, the page's function can be determined as "publishing detailed product information," and based on this function, the tracking and recommendation platform 301 can determine the page's characteristics as a product details page.

[0139] For example, the tracking recommendation platform 301 identifies buttons such as "Share," "Get Coupon," "Add to Cart," and "Buy Now" on a page screenshot. These buttons can all be considered UI elements on the page. Therefore, the UI element characteristics that the tracking recommendation platform 301 can determine are "Share," "Get Coupon," "Add to Cart," and "Buy Now," respectively.

[0140] In the above embodiments, the tracking recommendation platform 301 can automatically identify application semantic content, page semantic content and image content, and then determine the target industry characteristics and target scene characteristics. This automated identification method can speed up the feature identification process, thereby saving the overall time of the tracking recommendation process.

[0141] It is worth noting that the semantic recognition process in steps S403a and S403c can also be performed by the semantic recognition module 204 in the electronic device 100, and the image recognition process in step S403c can also be performed by the image recognition module 205 in the electronic device 100. The operations performed by the semantic recognition module 204 and the operations performed by the image recognition module 205 are both operations performed by the electronic device 100.

[0142] In some embodiments, the application information in the first type of user-input basic information of the target application may also include the target industry characteristics of the target application, or only the target industry characteristics. Furthermore, the page information in the first type of user-input basic information may also include the scene characteristics of the page in the target application, or only the scene characteristics.

[0143] In this system, the target industry characteristics input by the first user can be represented by first identifier information, and the scenario characteristics input by the first type of user can be represented by second identifier information. The first type of user can directly input the content of the first identifier information (i.e., the target industry characteristics) and the content of the second identifier information (i.e., the scenario characteristics) on the event tracking display platform 302. Then, the event tracking recommendation platform 301 can directly retrieve the corresponding event tracking recommendation information from the event tracking knowledge base based on the target industry characteristics and target scenario characteristics collected on the event tracking display platform 302. This method avoids the problem of inaccurate recognition results caused by the event tracking recommendation platform 301 automatically recognizing industry characteristics and scenario characteristics.

[0144] In some embodiments, the first identification information input by the first type of user may be selected by the first type of user from preset identification information, or it may be input by the first type of user in a custom manner. Similarly, the second identification information input by the first type of user may be selected by the first type of user from preset identification information, or it may be input by the first type of user in a custom manner.

[0145] For example, Figure 9 This illustration shows a schematic diagram of another application management page on the event tracking display platform provided in an embodiment of this application. For example... Figure 9 As shown, the application management page also displays a category selection bar based on the application's industry characteristics. First-class users can select primary, secondary, and tertiary categories within this category on the application management page. Specifically, by clicking the "▽" button on each category selection bar, first-class users can view a drop-down list below the category selection bar. The drop-down list displays the various options for each category, such as "Mall" and "Shopping Guide" in the tertiary category options.

[0146] For example, Figure 10This illustration shows a schematic diagram of another application page management page on the tracking display platform provided in this application embodiment. For example... Figure 10 As shown, the application page management page also displays a feature selection bar for page features. Users of the first type can select specific page features on this page management page. Specifically, by clicking the "▽" button on the feature selection bar, users can view a drop-down list below the feature selection bar. The drop-down list displays specific feature selection items, such as "Product Details Page" or "Search Page".

[0147] Additionally, the application page management page can provide an entry point for the first type of user to select UI element features, such as a "Mark UI Element" button. When the first type of user clicks the "Mark UI Element" button, the event tracking display platform 302 will continue to display the element marking page, where the first type of user can then input the UI element features on the page.

[0148] For example, Figure 11 This illustration shows a schematic diagram of an element marker page provided in an embodiment of this application. For example... Figure 11 As shown, this is a screenshot of the page displayed on the element marking page. The first type of user can select UI elements by clicking on them on this element marking page. For example, clicking the "Share" button selects it. Then, the first type of user can continue to select the element type of the "Share" button, enter text content, and specify the action to be performed, thus marking the "Share" button. Furthermore, the text content of the "Share" button constitutes its UI element characteristics.

[0149] In the above embodiments, the event tracking platform 302 provides industry features and scenario features to the first type of user, who can select them based on the actual situation of the target application and page. However, in some cases, the industry features or scenario features provided by the event tracking platform 302 are not comprehensive, and the first type of user cannot find the target industry features or scenario features they want to select on the event tracking platform 302. Therefore, in some embodiments, the event tracking platform 302 can also support the first type of user to define the target industry features of the target application and the scenario features of the page themselves.

[0150] Based on this, in some embodiments, on the aforementioned application management page, the input box corresponding to the industry characteristic can be set to a typeable state, so that the first type of user can define the target industry characteristic of the target application in the input box. Also, on the aforementioned application page management page, the input box corresponding to the page characteristic can be set to a typeable state, so that the first type of user can define the page characteristic of the page in the input box.

[0151] Then, the electronic device 100 can recommend tracking information for the target page (i.e., the application page to be recommended for tracking) in at least one of the above application pages.

[0152] S404, Electronic device 100 determines the target page for the recommendation tracking point selected by the first type of user in at least one application page of the target application.

[0153] Specifically, step S404 can be executed by the event tracking recommendation module 202 in the electronic device 100, or by the event tracking recommendation platform 301 in the electronic device 100. In the following embodiments, the method for determining the target page is described using the event tracking recommendation platform 301 executing step S404 as an example. Both the operations performed by the event tracking recommendation module 202 and the operations performed by the event tracking recommendation platform 301 are operations performed by the electronic device 100.

[0154] In some embodiments, the first type of user may select the target page by entering the application type, application version number, page name, page ID, etc. of the target application on the tracking display platform 302.

[0155] For example, a first type of user can log in to the event tracking recommendation system in the aforementioned embodiments. In this case, the event tracking display platform 302 within the event tracking recommendation system provides a display page for the first type of user to select a target page. The first type of user enters the application type, application version number, and page name of the target application on the display page. The event tracking recommendation platform 301 filters all application pages in the target application based on the application type, application version number, and page name, thereby determining the target page corresponding to the application type, application version number, and page name of the target application.

[0156] S405, Electronic device 100 obtains the target scene features of the target page from the scene features of each application page in at least one application page.

[0157] Specifically, step S405 can be executed by the event tracking recommendation module 202 in the electronic device 100, or by the event tracking recommendation platform 301 in the electronic device 100. In the following embodiments, the method for determining the target page is described using the event tracking recommendation platform 301 executing step S405 as an example. Both the operations performed by the event tracking recommendation module 202 and the operations performed by the event tracking recommendation platform 301 are operations performed by the electronic device 100.

[0158] Through step S404 above, the event tracking recommendation platform 301 has determined the target page to be recommended for event tracking. After determining the target page, the event tracking recommendation platform 301 can obtain the target scene features corresponding to the target page from the scene features corresponding to each application page of the target application.

[0159] In the above embodiments, when the first type of user obtains the target event, they can specify a target page from multiple application pages, and then obtain the target scene features corresponding to the current target page from the scene features of at least one application page.

[0160] S406. Electronic device 100 obtains the tracking point recommendation information of the target page in the target application from the tracking point knowledge base based on the target industry characteristics of the target application and the target scenario characteristics of the target page in the target application.

[0161] Specifically, step S406 can be executed by the event tracking recommendation module 202 in the electronic device 100, or by the event tracking recommendation platform 301 in the electronic device 100. In the following embodiments, the method of obtaining event tracking events is described using the event tracking recommendation platform 301 executing step S406 as an example. Both the operations performed by the event tracking recommendation module 202 and the operations performed by the event tracking recommendation platform 301 are operations performed by the electronic device 100.

[0162] In this embodiment, corresponding event tracking information is obtained for a target page. However, the target page may contain more than one UI element, and each UI element can be tracked. Therefore, the event tracking information for a target page should include at least one target event tracking event corresponding to a UI element.

[0163] For example, the UI element features corresponding to the UI elements on the target page of the target application are "Share," "Get Coupon," "Add to Cart," and "Buy Now." Therefore, the event tracking information for this target page should include at least four event tracking points. Since the UI elements corresponding to these UI element features are all located on the same target page of the same target application, the industry features corresponding to these UI element event tracking points are the same, and the page features in the scene features are also the same, while the UI element features, event names, and event parameters in the scene features are different.

[0164] See Figure 12 On a specific target page of a shopping app, UI elements including "Share," "Get Coupon," "Buy Now," and "Add to Cart" buttons are displayed.

[0165] In some embodiments, the event tracking recommendation platform 301 targets Figure 12The target event tracking data obtained from the target page of the shopping app shown can include at least four. See also Figure 13 These target event tracking events are all categorized as follows: first-level category: "Non-game Applications"; second-level category: "Shopping Price Comparison"; and page feature: "Product Details Page". Specifically, the first target event, "Share," has the UI element feature "Share," indicating a recommended event tracking the "Share" button UI element on this target page. The second target event, "Pick up the coupons," has the UI element feature "Claim coupons," indicating a recommended event tracking the "Claim coupons" button UI element on this target page. The third target event, "Buy," has the UI element feature "Buy now," indicating a recommended event tracking the "Buy now" button UI element on this target page. The fourth target event, "Add to cart," has the UI element feature "Add to cart," indicating a recommended event tracking the "Add to cart" button UI element on this target page.

[0166] Each tracking event in the tracking knowledge base has corresponding industry characteristics and scenario characteristics. Therefore, when the tracking recommendation platform 301 retrieves a target tracking event from the knowledge base, it can search for target tracking events that match the target industry characteristics and the target scenario characteristics. Specifically, among the tracking events to be matched in the knowledge base, the industry characteristics should include at least one first-level category item (e.g., only first-level category content), and the scenario characteristics should include at least one feature item (e.g., only page features). The tracking recommendation platform 301 can match the content of this first-level category item with the corresponding level of category item content in the target industry characteristics, and match the content of this single feature item with the corresponding feature item content in the target scenario. If the corresponding category item content is the same and the corresponding feature item content is the same, then the tracking event can be identified as the target tracking event.

[0167] In addition, among the event tracking data to be matched in the event tracking knowledge base, industry features can include multi-level category items, and scene features can include multiple feature items such as page features and UI element features. In this case, the event tracking recommendation platform 301 matches the content of each level of category item with the corresponding level of category item content in the target industry features, and matches the content of each feature item with the feature item content corresponding to the target scene features. If there are at least one identical category item and at least one identical feature item, then the event tracking data can be identified as the target event tracking data.

[0168] That is, the target event matched by the event tracking recommendation platform 301 in the event tracking knowledge base has at least one category content in the multi-level classification of its industry features that is the same as the category content in the target industry features, and at least one feature item in the scene features that is the same as the feature item content in the target scene features.

[0169] For example, if the target industry characteristics of the first type of user input include the primary category "non-game application" and the secondary category "shopping comparison", and the target scenario characteristics of the target page include the page feature "product details page" and the UI element feature "share", then the target event matched by the 301 tracking recommendation platform in the tracking knowledge base could be:

[0170] ① Target event tracking for primary category "non-game applications" and page features "product details page";

[0171] ②Target event tracking for secondary categories of "shopping price comparison" and page features of "product details page";

[0172] ③ Target event tracking for primary categories of "non-game applications" and UI elements with the characteristic of "sharing";

[0173] ④ Target event tracking with the secondary category of "shopping price comparison" and the UI element feature of "sharing";

[0174] ⑤ Target event tracking for categories with the primary category "non-game applications", the secondary category "shopping comparison", and the page feature "product details page";

[0175] ⑥ Target event tracking for applications with a primary category of "non-game applications", a secondary category of "shopping price comparison", and a UI element feature of "sharing";

[0176] ⑦ Target event tracking for applications with the primary category of "non-game applications", the page feature of "product details page", and the UI element feature of "sharing";

[0177] ⑧ Target event tracking for categories with the secondary category "shopping price comparison", page features "product details page", and UI element features "sharing";

[0178] ⑨ Target event tracking with the primary category "non-game applications", the secondary category "shopping price comparison", the page feature "product details page", and the UI element feature "sharing".

[0179] In the example above, if the target page only contains the UI element "Share" button, then the target event tracking points obtained for the target page can be ①-⑨. However, if the target page also includes other UI elements, such as "Claim Coupon" button, "Buy Now" button, "Add to Cart" button, etc., then the event tracking recommendation platform 301 can continue to obtain the corresponding target event tracking points for the characteristics of UI elements such as "Claim Coupon," "Buy Now," and "Add to Cart," and then collectively determine all the obtained target event tracking points as the event tracking recommendation information corresponding to the target page.

[0180] In some embodiments, if the target page of the target application has a large number of UI elements, the number of target event tracking points obtained by the event tracking recommendation platform 301 will also be relatively large. To facilitate providing better and more accurate recommendations to the first type of users, the event tracking recommendation platform 301 can further determine the matching degree between the obtained target event tracking points and the target page, and sort the target event tracking points from high to low according to the matching degree. Then, the event tracking display platform 302 displays the target event tracking points to the first type of users according to the matching degree, so that the first type of users can clearly understand which target event tracking point is more suitable for the current target page, and thus set up event tracking points more accurately on the target page based on the more suitable event tracking recommendation information.

[0181] Specifically, when determining the matching degree, the tracking recommendation platform 301 can determine the matching degree between the target tracking event and the target page based on the characteristics of a certain UI element.

[0182] The matching degree, also known as the number of matches, can be determined based on the number of items in the industry characteristics of the target event that match the same level of category as the target industry characteristics, and the number of items in the scene characteristics of the target event that match the same feature items as the target scene characteristics. Furthermore, if two or more target events have the same matching degree with the target page, the target event that matches the UI element features in the target scene characteristics is identified as the event with the higher matching degree.

[0183] For example, if the target page only contains the UI element "Share" button, among the target event tracking events ①-⑨ mentioned above, event ⑨ has the highest matching degree with the target page of the target application, with a specific number of matches of 4; target events ⑤-⑧ are next, with a specific number of matches of 3; and target events ①-④ have the lowest matching degree, with a specific number of matches of 2. Among target events ⑤-⑧ with the same matching degree, target events ⑥-⑧ share the same UI element feature "Share" on the target page, so the matching degree of target events ⑥-⑧ is higher than that of target event ⑤. Furthermore, among target events ①-④ with the same matching degree, target events ③-④ share the same UI element feature "Share" on the target page, so the matching degree of target events ③-④ is higher than that of target events ①-②.

[0184] In the above embodiments, the higher the matching degree between the target event and the target page, the more similar or close the industry characteristics of the target application to which the target page belongs and the scenario characteristics of the target page are to the industry characteristics and scenario characteristics of the target event. This means the target event is also more likely to meet the current target page's event tracking requirements or rules. The event tracking recommendation platform 301 recommends the target event with a higher matching degree to the first type of user, allowing the first type of user to set up event tracking more accurately based on the more matching recommended event.

[0185] In the above embodiments, if a large number of target event tracking points are matched from the event tracking knowledge base, these target event tracking points can be sorted according to their matching degree. When displaying target event tracking points to the first type of user, the target event tracking point with the highest matching degree can be displayed first. The first type of user can more intuitively see the target event tracking points that are more suitable for the current target page, and thus set the event tracking points more accurately based on the more suitable target event tracking points.

[0186] Furthermore, to facilitate the matching of target event tracking from the event tracking knowledge base by the event tracking recommendation platform 301, in this embodiment, after constructing the event tracking knowledge base, the event tracking recommendation platform 301 can further construct an online retrieval system based on the event tracking knowledge base. The online retrieval system can also retrieve corresponding target event tracking from the event tracking knowledge base based on target industry characteristics and target scenario characteristics. The specific implementation method can refer to the process of matching target event tracking in the aforementioned embodiments, and will not be repeated here.

[0187] S407, the electronic device 100 provides the obtained tracking point recommendation information to the first type of user, so as to prompt the first type of user to set up tracking points on the target page according to the provided tracking point recommendation information.

[0188] Specifically, step S407 can be executed by the event tracking recommendation module 202 in the electronic device 100, or by the event tracking display platform 302 in the electronic device 100. In the following embodiments, the method for displaying target event tracking events is described using the event tracking display platform 302 executing step S407 as an example. Both the operations performed by the event tracking recommendation module 202 and the operations performed by the event tracking display platform 302 are operations performed by the electronic device 100.

[0189] The electronic device 100 can provide the obtained event tracking recommendation information to the first type of user, such as displaying the obtained event tracking recommendation information. The first type of user can then set up event tracking on the target page based on the event tracking recommendation information provided by the electronic device 100, thereby improving the accuracy of the event tracking settings.

[0190] Furthermore, when the target page includes more than one UI element, the electronic device 100 can obtain the target tracking event corresponding to each UI element. The electronic device 100 can also provide the first type of user with the target tracking event corresponding to one of the UI elements (the target UI element), thereby enabling the first type of user to set tracking points more accurately on the target page.

[0191] Specifically, the event tracking display platform 302 can provide a tracking recommendation page for the first type of user, which displays the target tracking events corresponding to each UI element on the target page. Furthermore, when displaying target tracking events, it can also show the event name, event description, event parameters, etc.

[0192] For example, Figure 14 This illustration shows a schematic diagram of a tracking point recommendation page on a tracking point display platform provided in an embodiment of this application. For example... Figure 14 As shown, this event tracking recommendation page can display application information for the specific target application entered by the first type of user, such as the target application's version number, application type, and the name of the target page within the target application. The page can also display a screenshot of the target page.

[0193] The target event displayed on the event tracking recommendation page corresponds to a specific UI element on the target page. The electronic device 100 can display the target event corresponding to the user-specified target UI element to the first type of user. For example, when the first type of user clicks the UI element ("Share" button) at location number 1 on the event tracking recommendation page, the event tracking display platform 302 can display a list of the corresponding target event tracking events, along with the event description and parameters for each event tracking event. For instance, the event description for the event name "ShareContent" is "Add this event tracking point when the user shares content"; the event description for the event name "ShareAPP" is "Add this event tracking point when the user shares the APP." The event parameters for the event name "ShareContent" include "type" and "name," which indicate the parameter type and name that the first type of user needs to use when adding the event tracking point.

[0194] Similarly, when the first type of user clicks the "Claim Coupon" button at position number 2, the "Buy Now" button at position number 3, or the "Add to Cart" button at position number 4 on the event tracking recommendation page, the event tracking display platform 302 can display a list of the target event tracking events corresponding to the UI elements "Claim Coupon", "Buy Now" or "Add to Cart" on the event tracking recommendation page, as well as the event description and event parameters of each target event tracking event.

[0195] The first type of user can refer to the screenshots on the recommended event tracking page to determine the location of the UI elements that need event tracking on the target page. Furthermore, after obtaining the target event tracking information for the UI element, the first type of user can generate corresponding event tracking configuration information for that UI element based on the event description and parameters. Therefore, the target event tracking allows the first type of user to more accurately set up event tracking and generate event tracking configuration information on the target page.

[0196] As can be seen from the foregoing embodiments, the event tracking recommendation method in this application can obtain the corresponding event tracking events for APP pages from a pre-built event tracking knowledge base based on the industry characteristics of the APP and the scene characteristics of the APP pages. During the APP development stage, suggestions for setting event tracking on APP pages can be provided to APP developers and other first-type users. This event tracking recommendation method enables first-type users to set event tracking more comprehensively during the APP development stage, thereby reducing the problem of unreasonable and incomplete user behavior data collection caused by incomplete event tracking during the APP operation stage.

[0197] Especially for inexperienced first-time users, this event tracking recommendation method can also reduce the problem of incomplete event tracking settings caused by their lack of experience.

[0198] It is understood that, in order to achieve the above functions, the electronic device includes hardware and / or software modules that perform the respective functions. Based on the algorithmic steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0199] This embodiment can divide the electronic device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0200] This application also provides an electronic device, including one or more processors and a memory. The memory and processor are coupled; wherein the memory stores computer program code, which includes computer instructions. When the computer instructions are executed by the processor, the electronic device performs the steps in the above embodiments. All relevant content regarding the steps in the above method embodiments can be referenced to the functional description of the corresponding physical device, and will not be repeated here.

[0201] For example, the processor may specifically be Figure 1 The processor 1001 shown may have a memory that is specifically designed to be... Figure 1 The memory 1002 shown.

[0202] This application also provides an electronic device, including one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, including computer instructions. When the one or more processors execute the computer instructions, the electronic device performs the aforementioned method steps to implement the data tracking recommendation method in the above embodiments.

[0203] This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, the server executes the relevant method steps in the above method embodiments to implement the methods in the above embodiments.

[0204] This application also provides a computer program product that, when run on a computer, causes the computer to execute the relevant method steps in the above method embodiments to implement the methods in the above embodiments.

[0205] The electronic devices, computer storage media, or computer program products provided in this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0206] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

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

[0208] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0209] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0210] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps 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, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0211] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope 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 recommending products based on event tracking, characterized in that, The method includes: Obtain a tracking knowledge base; the tracking knowledge base includes at least one tracking event, and the correspondence between the tracking event and the industry characteristics of the application and the scene characteristics of the page; the tracking knowledge base is a global knowledge base built based on user behavior data on the global application and application page information associated with the behavior data; the global application refers to an application involving multiple industries and multiple scenarios; the industry characteristics are used to represent the industry type of the business involved in the application, and the scene characteristics are used to represent the page type and the UI element characteristics displayed on the page in the application; For the target page to be recommended and tracked, obtain the target industry characteristics of the target application to which the target page belongs and the target scenario characteristics of the target page; Based on the target industry characteristics and the target scenario characteristics, target tracking events corresponding to the target page to be recommended are obtained from the tracking knowledge base; the industry characteristics corresponding to the target tracking events match the target industry characteristics, and the scenario characteristics of the target tracking events match the target scenario characteristics; the target tracking events are used to guide users to set up tracking for the target page.

2. The method for recommending data points according to claim 1, characterized in that, Before obtaining the target industry characteristics of the target application to which the target page belongs and the target scene characteristics of the target page for the target page to be recommended, the method further includes: Obtain basic information about the target application; the target application includes at least one application page, and the at least one application page includes the target page; Based on the basic information of the target application, the target industry characteristics of the target application are determined, and the scene characteristics of each application page in the at least one application page are determined; the scene characteristics of each application page in the at least one application page include the target scene characteristics of the target page.

3. The method for recommending data points according to claim 2, characterized in that, For the target page to be recommended, the target industry characteristics of the target application to which the target page belongs and the target scene characteristics of the target page are obtained, including: The target page to be recommended for tracking is determined, and the target industry features and the target scene features of the target page are obtained from the target industry features of the determined target application and the scene features of each page in the at least one application page.

4. The method for recommending data points according to any one of claims 2-3, characterized in that, The basic information includes application information of the target application and page information of at least one application page in the target application; the application information includes one or more of the application name, application identifier, application description, application version number, and application type; and the page information includes one or more of the page screenshot, page identifier, page name, and page description information.

5. The method for recommending event tracking points according to any one of claims 2-3, characterized in that, The step of determining the target industry characteristics of the target application based on the basic information of the target application includes: Semantic recognition is performed on the application information in the basic information to obtain application semantic content; Based on the semantic content of the application, the target industry characteristics of the target application are determined.

6. The method for recommending data points according to any one of claims 2-3, characterized in that, Based on the basic information of the target application, determine the scene characteristics of the application page, including: Semantic and image recognition are performed on the page information of the application page in the basic information to obtain the page semantic content and user interface (UI) elements of the application page; Based on the semantic content of the page and the UI elements of the page, the target scene characteristics of the application page in the target application are determined.

7. The method for recommending data points according to any one of claims 2-3, characterized in that, The application information in the basic information includes preset first identification information, which is used to indicate the target industry characteristics corresponding to the target application. The step of determining the target industry characteristics of the target application based on the basic information of the target application includes: The target industry characteristics of the target application are obtained based on the first identification information.

8. The method for recommending data points according to claim 7, characterized in that, The preset first identification information is information input by the user.

9. The method for recommending data points according to any one of claims 2-3, characterized in that, The page information in the basic information includes preset second identification information, which is used to indicate the scene features corresponding to each application page in the at least one application page; Based on the basic information of the target application, determine the scene characteristics of the application page, including: The scene characteristics of the application page are obtained based on the second identification information.

10. The method for recommending embedded points according to claim 9, characterized in that, The preset second identification information is information input by the user.

11. The method for recommending data points according to any one of claims 1-3, characterized in that, The step of obtaining the target event tracking corresponding to the target page from the event tracking knowledge base based on the target industry characteristics and the target scenario characteristics includes: Obtain at least one target event from the event tracking knowledge base that matches the industry features and scenario features with the target industry features and the target scenario features; The at least one target event is sorted from high to low according to the matching degree between the target event and the target page to obtain the target event.

12. The method for recommending data points according to claim 11, characterized in that, The industry characteristics of the target event include at least one level of classification items, and the scenario characteristics of the target event include at least one feature item; the industry characteristics are used to represent the industry type of the business involved in the application, and the scenario characteristics are used to represent the page type and the UI element characteristics displayed on the page in the application.

13. The embedding point recommendation method according to claim 12, characterized in that, After obtaining at least one target event from the event tracking knowledge base that matches the target industry characteristics and the target scenario characteristics, the method further includes: Determine the number of classification items that are the same in the industry features of the target event and the target industry features, and the number of feature items that are the same in the scene features of the target event and the target scene features; The matching degree between the target event and the target page is determined based on the sum of the number of classification items and the number of feature items.

14. The method for recommending data points according to any one of claims 1-3, characterized in that, The knowledge base for obtaining tracking points includes: Collect user behavior data from applications that exhibit characteristics of different industries; the user behavior data includes user interface (UI) elements that users interact with on application pages; Based on the scenario characteristics of the application page, the user behavior data belonging to the same industry characteristics are classified, and the tracking events for the same industry characteristics and the same scenario characteristics are determined; the tracking events correspond to the user interface UI elements in the user behavior data; The tracking event knowledge base is constructed using the tracking event.

15. The embedding point recommendation method according to claim 2 or 3, characterized in that, The acquisition of basic information about the target application includes: Display the application management page; Obtain the application information of the target application entered by the user on the application management page.

16. The method for recommending embedded points according to claim 15, characterized in that, The process of obtaining the basic information of the target application also includes: In response to the user clicking the application page management entry on the application management page, the application page management page is displayed; Obtain page information for each application page in at least one application page of the target application, as entered by the user on the application page management page.

17. The method for recommending data points according to any one of claims 1-3, characterized in that, After obtaining the target event corresponding to the target page to be recommended from the event tracking knowledge base based on the target industry characteristics and the target scenario characteristics, the method further includes: Display the target event tracking to guide the user in setting up event tracking for the target page.

18. The method for recommending data points according to any one of claims 1-3, characterized in that, After obtaining the target event tracking information corresponding to the target page from the event tracking knowledge base based on the target industry characteristics and the target scenario characteristics, the method further includes: Retrieve the target user interface (UI) element on the target page specified by the user; Retrieve the target event corresponding to the target user interface (UI) element from the target event tracking points; Display target event tracking corresponding to the target user interface (UI) element to guide the user to set up event tracking for the target application UI element on the target page.

19. The method for recommending embedded points according to claim 18, characterized in that, The target event includes an event description and event parameters; the target event is used to enable the user to generate corresponding event configuration information for the target user interface UI element on the target page based on the event description and the event parameters.

20. An electronic device, characterized in that, include: A memory, one or more processors; the memory is coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, which, when executed by the processor, cause the electronic device to perform the data tracking recommendation method as described in any one of claims 1-19.

21. A computer-readable storage medium, characterized in that, It includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the tracking recommendation method as described in any one of claims 1-19.

22. A computer program product, characterized in that, When the computer program product is run on a computer, the computer performs the tracking point recommendation method as described in any one of claims 1-19.

Images