CN116263679A

CN116263679A - Data processing method, device, computer equipment and storage medium

Info

Publication number: CN116263679A
Application number: CN202111538912.0A
Authority: CN
Inventors: 青子晋; 徐媛; 李胜刚; 许清华; 梁旭飞; 徐凯鹏; 张梁; 梁宇轩
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2021-12-15
Filing date: 2021-12-15
Publication date: 2023-06-16

Abstract

The application discloses a data processing method, a device, a computer device and a storage medium, wherein the method comprises the following steps: acquiring at least one page component of an application program and component elements contained in each page component; adding a target event to the component elements contained in each page component; if the target event corresponding to the target component element in the application page of the application program is triggered, creating target information according to the application page, the target component element and the page component to which the target component element belongs. By adopting the method and the device, the efficiency and the accuracy for creating the target information can be improved.

Description

Data processing method, device, computer equipment and storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a data processing method, apparatus, computer device, and storage medium.

Background

With the continuous development of computer networks, the data volume of data in the networks is increasing, and for subsequent analysis and processing of related data generated in the networks, the technology of generating related target information for acquiring the data is also important.

In the existing application, related technicians are usually required to manually create target information in a system, so that corresponding data can be acquired through the target information later, and the manual creation of the target information can result in low efficiency and high cost of creating the target information, and can also result in inaccurate or incomplete created target information and the like.

Disclosure of Invention

The application provides a data processing method, a data processing device, computer equipment and a storage medium, which can improve the efficiency and accuracy of creating target information.

In one aspect, the present application provides a data processing method, including:

acquiring at least one page component of an application program and component elements contained in each page component;

adding a target event to the component elements contained in each page component;

if the target event corresponding to the target component element in the application page of the application program is triggered, creating target information according to the application page, the target component element and the page component to which the target component element belongs.

Optionally, the method further comprises:

acquiring page link information of an application page;

and extracting the page identification of the application page from the page link information.

In one aspect, the present application provides a data processing apparatus, the apparatus comprising:

the acquisition module is used for acquiring at least one page component of the application program and component elements contained in each page component;

the adding module is used for adding a target event to the component elements contained in each page component;

the creation module is used for creating target information according to the application page, the target component element and the page component to which the target component element belongs if the target event corresponding to the target component element in the application page of the application program is triggered.

Alternatively, the above apparatus may be applied to a target device where an application program is located;

the method for acquiring at least one page component of the application program and the component elements contained in each page component by the acquisition module comprises the following steps:

acquiring an application folder of an application program in target equipment;

traversing the files in the application folder;

at least one page component is determined from the traversed component file, and component elements contained by each page component are determined from the traversed element file.

Optionally, if the target component element belongs to the component element of the exposure type, the target event added to the target component element is an event that the exposure frequency reaches the exposure frequency threshold; if the target component element is a component element of the trigger type, the target event added for the target component element is an event whose trigger number reaches a trigger number threshold.

Optionally, if the target event corresponding to the target component element in the application page of the application program is triggered, the creating module creates the target information according to the application page, the target component element, and the page component to which the target component element belongs, including:

if the target component element belongs to the page component of the exposure type and the exposure times of the target component element in the application page reach the exposure times threshold, determining that a target event corresponding to the target component element is triggered;

if the target event corresponding to the target component element is triggered, creating target information according to the page identification of the application page, the element attribute information of the target component element and the component identification of the page component to which the target component element belongs.

Optionally, the target component element belongs to a page element in the application page; the device is also used for:

acquiring page elements in a screen visualization area of an application page in the display process of the application page;

if the page element in the screen visualization area includes the target component element, it is determined that the target component element is exposed.

Optionally, the target information is used for indicating that the data reporting is performed when the target component element is exposed in the application page;

The device is also used for:

when an exposure instruction for the target component element is acquired in the application page, acquiring exposure data for the target component element according to target information;

the exposure data for the target component element is sent to a data storage device.

if the target component element belongs to the page component of the trigger type and the trigger frequency of the target component element in the application page reaches the trigger frequency threshold, determining that a target event corresponding to the target component element is triggered;

Optionally, the target component element belongs to a page control in the application page; the device is also used for:

when a trigger instruction for the target component element is acquired in the application page, the target component element is determined to be triggered.

Optionally, the device is further configured to:

when a trigger instruction aiming at the target component element is acquired in the application page, acquiring trigger data aiming at the target component element according to target information;

trigger data for the target component element is sent to the data storage device.

Optionally, the device is further configured to:

acquiring page link information of an application page;

Optionally, the device is further configured to:

generating at least one piece of initial information according to each page component and component elements contained in each page component; any initial information records the component identification of a page component and the element attribute information of a component element contained in the page component;

if the target event corresponding to the target component element is triggered, creating target information according to the page identifier of the application page, the element attribute information of the target component element and the component identifier of the page component to which the target component element belongs, including:

if the target event corresponding to the target component element in the application page is triggered, integrating the page identification of the application page in the initial information containing the element attribute information of the target component element to obtain target information.

Optionally, the device is further configured to:

acquiring a data query request; the data query request carries the component identifier of the page component to which the target component element belongs;

if the target component element belongs to the page component of the exposure type, inquiring exposure data for the target component element acquired based on the indication information according to the component identifier carried by the data inquiry request;

if the target component element belongs to the page component of the trigger type, inquiring trigger data for the target component element acquired based on the indication information according to the component identifier carried by the data inquiry request;

the indication information is target information recorded with a component identifier carried by the data query request.

In one aspect, the present application provides a computer device including a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform a method in one aspect of the present application.

In one aspect, the present application provides a computer readable storage medium storing a computer program comprising program instructions which, when executed by a processor, cause the processor to perform the method of one of the aspects described above.

According to one aspect of the present application, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the methods provided in the various alternatives of the above aspect and the like.

The method comprises the steps that at least one page component of an application program and component elements contained in each page component are obtained; adding a target event to the component elements contained in each page component; if the target event corresponding to the target component element in the application page of the application program is triggered, creating target information according to the application page, the target component element and the page component to which the target component element belongs. Therefore, the method can add the target event to the component element, and further can intelligently create the target information through the condition that the target event is triggered, thereby improving the efficiency and accuracy of creating the target information.

Drawings

In order to more clearly illustrate the technical solutions of the present application or the prior art, the following description will briefly introduce the drawings that are required to be used in the embodiments or the prior art descriptions, it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic structural diagram of a network architecture according to an embodiment of the present application;

FIG. 2 is a schematic view of a scenario of data processing provided herein;

FIG. 3 is a flow chart of a data processing method provided in the present application;

FIG. 4 is a schematic flow chart of a file traversal provided herein;

FIG. 5 is a schematic view of a file traversal scenario provided herein;

FIG. 6 is a page schematic diagram of an application page provided herein;

FIGS. 7 a-7 b are schematic flow diagrams of creating target information provided herein;

FIG. 8 is a schematic diagram of a scenario featuring a page component provided herein;

FIG. 9 is a schematic flow chart of page information acquisition provided in the present application;

FIG. 10 is a schematic page view of a data management platform provided herein;

FIG. 11 is a schematic diagram of a data processing apparatus provided herein;

fig. 12 is a schematic structural diagram of a computer device provided in the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The present application also relates to techniques related to blockchains. The blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. The Blockchain (Blockchain), which is essentially a decentralised database, is a string of data blocks that are generated by cryptographic means in association, each data block containing a batch of information of network transactions for verifying the validity of the information (anti-counterfeiting) and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer. The blockchain comprises a series of blocks (blocks) which are mutually connected according to the sequence of the generated time, the new blocks are not removed once being added into the blockchain, and record data submitted by nodes in the blockchain system are recorded in the blocks. In the method, the target information of the created application program can be stored in a uplink mode, accuracy of the target information is guaranteed, and the target information cannot be tampered.

First, it should be noted that the present application complies with relevant national and regional laws and regulations when collecting relevant data (such as data regarding triggering/exposure of component elements, etc.), and complies with relevant national and regional laws and regulations when collecting relevant data for subsequent use and processing of the relevant data.

The following explains the related concepts referred to in this application:

and (3) groupwise: the assembly is to split a page into small functional modules (namely page assemblies), and each functional module completes the independent function belonging to the part of the functional module, so that the management and maintenance of the whole page are very easy.

Referring to fig. 1, fig. 1 is a schematic structural diagram of a network architecture according to an embodiment of the present application. As shown in fig. 1, the network architecture may include a server 200 and a cluster of terminal devices, which may include one or more terminal devices, the number of which will not be limited here. As shown in fig. 1, the plurality of terminal devices may specifically include a terminal device 100a, a terminal device 101a, terminal devices 102a, …, a terminal device 103a; as shown in fig. 1, the terminal device 100a, the terminal device 101a, the terminal devices 102a, …, and the terminal device 103a may be connected to the server 200 through a network, so that each terminal device may interact with the server 200 through the network connection.

The server 200 shown in fig. 1 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligence platforms, and the like. The terminal device may be: intelligent terminals such as intelligent mobile phones, tablet computers, notebook computers, desktop computers, intelligent televisions, vehicle-mounted terminals and the like. A specific description of the embodiment of the present application will be made below taking communication between the terminal device 100a and the server 200 as an example.

Referring to fig. 2, fig. 2 is a schematic view of a scenario of data processing provided in the present application. As shown in fig. 2, the terminal device 100a may have an application program therein, that is, the terminal device 100a may access the application program, the application program may be any one of the application programs, and the server 200 may be a background server of the application program. The application program in the terminal device 100a can intelligently create the target information, and particularly, see the following description.

It will be appreciated that the operations performed by the terminal device described below may be performed by an application program in the terminal device. The terminal device 100a may obtain several page components of the application, where the several page components may include a page component 1, a page component 2, and a page component 3. The terminal device 100a may also acquire the component elements included in each page component, for example, the terminal device 100a may acquire the component element 1, the component element 2, and the component element 3 included in the page component 1, may also acquire the component element 4 and the component element 5 included in the page component 2, and may also acquire the component element 6 and the component element 7 included in the page component 3.

Moreover, the terminal device 100a may further add a corresponding target event to each component element, specifically, the terminal device 100a may create corresponding target events for the component element 1, the component element 2, the component element 3, the component element 4, the component element 5, the component element 6, and the component element 7, where the target events indicate conditions for creating corresponding target information for the component element, where the target information is used by an application program to acquire relevant data (such as exposed relevant data and triggered relevant data) for the component element when acquiring relevant program instructions for the component element.

Any one of the above-described

component elements

1, 2, 3, 4, 5, 6, and 7 may be expressed as a component element n, and thus, when the terminal device 100a detects that a target event corresponding to the component element n is triggered in an application page of the application program, the application program in the terminal device 100a may create target information corresponding to the component element n, which is used to acquire relevant data for the component element n when relevant program instructions for the component element n are acquired in the application page, and the target information may include a page identifier of the application page, a component identifier of a page component to which the component element n belongs, and element attribute information of the component element n. Wherein, how to create the target information specifically and relevant explanation of the target information can also be referred to the relevant description in the corresponding embodiment of fig. 3 below.

Further, when the terminal device 100a receives a related program instruction (e.g., a trigger instruction or an exposure instruction, etc.) for the component element n by the user, the terminal device 100a may acquire related data for the component element n through the created target information for the component element n, and may transmit the acquired related data to the server 200, so that the server 200 may further perform analysis processing on the related data for the component element n, such as acquiring related exposure data for commodity data (the commodity data may be the component element n), may perform related commodity recommendation by analyzing the related exposure data pair for the commodity data, and so on.

According to the method and the device, the page component and the component elements included in the page component are identified, and then the target information corresponding to the component elements is intelligently created through the related program data (such as the exposed related data and the triggered related data) of the component elements in the application page, so that the accuracy and the efficiency of creating the target information can be improved.

Referring to fig. 3, fig. 3 is a flow chart of a data processing method provided in the present application. As shown in fig. 3, the method may include:

Step S101, at least one page component of the application program and component elements included in each page component are acquired.

Alternatively, the execution subject in the present application may be a target device, where the target device refers to a device with an application program (such as a device with a client of the application program), and the application program may be any program that can be accessed by a user, and the application program may be an application program in a web page form, or may be an application program in an app (mobile phone software) form, or may be an application program in an applet form, which is specifically determined according to an actual application scenario, and is not limited. For example, the target device may be a terminal device of the user, which may access the application, i.e. a client that may access the application. It will be appreciated that all of the operations performed by the target device in this application may be performed by an application in the target device.

Firstly, the assembly is explained, namely, a page is split into small functional modules, each functional module completes the independent function of the part of the functional module, so that the management and maintenance of the whole page are very easy, and the page can be understood to be displayed by a plurality of components respectively through the assembly of the page, and one component can be used for displaying the content in one display area of the page.

The resulting assembly of pages of an application may be referred to as a page assembly. The target device may acquire at least one page component of the application program and the acquired component element contained in each page component, where the at least one page component may be all page components contained in the application program, and the number of the at least one page component may be determined according to an actual application scenario, which is not limited.

A page component may include one or more component elements that belong to page elements in an application page of an application (which may be any page of the application), which may be displayed in the application page of the application. For example, a component element included in a page component may be a page control, such as a button, or a page list, or the like.

Optionally, the manner in which the target device obtains at least one page component of the application program and the component element included in each page component may be: the target device may obtain an application folder for the application in the target device, the application folder may include a relevant configuration file for the application in the target device, and the application folder is used for storing relevant application data for the application in the target device. For example, if the application is an app, the application folder may be a folder that can store application data of the application program stored after the application program is installed.

Therefore, the target device can acquire the application folder of the application program in the target device, and further, the target device can traverse the files in the application folder, and the target device can traverse all the files contained in the application folder. Therefore, the target device can acquire the at least one page component of the application program through the traversed component file, the component file refers to the configuration file of the page component in the application folder, the application program in the target device can identify the configuration file, and then a plurality of page components configured by the application program are acquired through the configuration file.

The target device can also acquire the component elements of each page component through the traversed element file, wherein the element file refers to the configuration file of the component elements in the application folder, and an application program in the target device can identify the configuration file, so that a plurality of component elements configured by the page component of the application program are acquired through the configuration file.

Referring to fig. 4, fig. 4 is a schematic flow chart of file traversal provided in the present application. As shown in fig. 4, S201: the target device may input an initial value, which may be a component folder in the application folder, which may include a component file and an element file. S202: the target device may read the directory (i.e., file directory) in the outputted initial value and may acquire each file under the directory. S203: the target device may traverse each file under the directory. S204: the target device may determine whether each file is still a path by traversing each file in the directory, where the path may be a component path of the page component to which the input component folder belongs, if yes, then the target device may start a new round of traversal to re-execute S202, and start the new round of traversal may be traversing a subfolder (the subfolder may include an element file) in the component folder, that is, continuing traversing files in the subfolder to traverse to obtain component elements included in the page component; if not, step S205 may be performed. Step S205: the target device may determine whether the path is not a file ending in a video file format (e.g., vai) that is possibly a file that is manually newly added to the component folder, and thus, the path may be different from the paths of other files in the component folder, and if so, step S206 may be performed. Step S206: files ending in a video file format (e.g., vai) are removed from the component folder and added to the new path because the file in the video file format (e.g., a video file) can be considered to belong to an unrelated component element in the page component (i.e., without acquiring relevant data for the video file by the user), the component element can be removed. By the aid of the process, all files in the component folder of each page component can be traversed, and by traversing the component folder of each page component, each page component and component elements included in each page component can be traversed.

Referring to fig. 5, fig. 5 is a schematic view of a file traversal scenario provided in the present application. Here, A may be represented as a component folder, and the target device may be from aboveTraversing the files in the component folder in turn down until traversing to a single file (e.g

I.e., not folders), folder B and folder C may both be subfolders in folder a, folder D may be subfolders in folder B, and folder E and folder F may be subfolders in folder C. Through the process, each file in the component folder can be traversed to obtain the page component and the component elements included in the page component.

Step S102, adding a target event to the component elements contained in each page component.

Optionally, the target device may add a target event to a component element included in each page component, and specifically, what target event to add to each component element may be pre-written in the application program (for example, may be written in an installation package of the application program, so after the application program is installed, the target event corresponding to each component element may be obtained by parsing. A component element may correspond to a target event, where the target event may be used to indicate a trigger condition for creating corresponding target information for the corresponding component element, where the target information is used to obtain relevant program data for the component element (e.g., relevant exposure data or trigger data for the component element) when relevant program instructions (e.g., exposure instructions or trigger instructions, etc.) for the corresponding component element are obtained, which may be described in detail below.

Alternatively, any one of all the component elements included in all the page components may be referred to as a target component element, i.e., the target component element may be any one component element, and the process of creating target information for the target component element will be described below as an example, and it will be understood that the principle of creating corresponding target information for each component element is the same.

Optionally, the component elements may be classified, and further, corresponding target events may be added to each group value element according to the type of the component element.

For example, the types of the component elements may include an exposure type and a trigger type, and if the type of the target component element is an exposure type, an index indicating whether the target component element is exposed is important, and thus, the target event added to the target component element may be an event in which the exposure number reaches the exposure number threshold.

Further, if the type of the target component element is a trigger type, an indicator indicating whether the target component element is triggered is important, so that the target event added to the target component element may be that the trigger number reaches the trigger number threshold. The exposure time threshold and the trigger time threshold may be set according to the actual application scenario, which is not limited, for example, the exposure time threshold and the trigger time threshold may be 10 times, etc.

Optionally, whether the type of one component element is an exposure type or a trigger type may also be set according to the actual application scenario, which is not limited.

Wherein, the explanation is made when the target component element is exposed: the target component element belongs to a page element in an application page of the application program, and the page element can be displayed in the application page. The target device may acquire, during the display process of the application page (for example, during the process of the user clicking on the application page to browse the application page), a page element in a screen visualization area of the application page, where the screen visualization area refers to an area of the application page displayed in a screen of the target device, and content displayed in the screen visualization area is what can be seen by the user. For example, one application page is relatively long, and can be viewed in a sliding manner up and down in the screen of the target device, so that the area displayed in the screen of the target device that slides out in the application page can be understood as a screen visualization area, and the area that does not slide out in the application page, i.e., is not displayed in the screen of the target device, i.e., is not visible to the user, is not a screen visualization area.

Thus, if the page element in the screen visualization area includes the target component element, it indicates that an exposure instruction is received for the target component element by the user, so that the target component element is exposed in the application page, i.e., the target component element is seen by the user in the screen visualization area. Every time a user opens an application page for 1 time in the target device, and the target component element is exposed in the opened application page (i.e. every time an exposure instruction of the user for the target component element is received for 1 time), the target component element can be considered to be exposed for 1 time, if the user closes the application page in the target device, and then the application page is opened again, and the target component element is exposed again in the reopened application page (i.e. an exposure instruction of the user for the target component element is acquired again), the target component element can be considered to be totally exposed for 2 times. In other words, in a process of displaying an application page once (i.e., a process of opening one time) which is a continuous display of the application page, the target component element may be exposed 1 time or not, and if exposed, the number of exposure times (historically accumulated number of exposure times) of the target component element may be increased by 1.

It will be appreciated that for an application, an application page (e.g. a financial product recommendation page or a personal information management page, etc.) of the application is opened and then closed and then reopened, or a terminal device is replaced to reopen the application page, and for the application, the application page is the same application page that is opened. Thus, alternatively, the number of exposures of a target component element may refer to the total cumulative number of exposures of all users of the application (e.g., users with user accounts in the application, which may be referred to as objects) to the target component element in the application page in which the target component element is located. After exposing the target component element in the application page of the terminal equipment of the user, the application programs of the terminal equipment of the user update the exposure times of the target component element, namely update the total exposure times of all the users aiming at the target component element.

Optionally, a description is given of when the target component element is triggered: the target component element may be a page control in the application page, and may be considered to be triggered in the application page when the target device obtains a trigger instruction for the target component element in the application page (e.g., an instruction generated by a click, double click, long press, or voice trigger operation on the target component element). Similarly, the number of triggers of the target component element may be the sum of the number of triggers of all users of the application program for the target component element.

After different users trigger the target component element in the application page where the target component element is located in the application program of their own terminal equipment, the trigger times of the target component element in the application program of the terminal equipment of each user are updated, that is, the trigger times of all the current users for the target component element are updated. It will be appreciated that, when each pair of target component elements is triggered 1 time, the number of times of triggering the target component elements is increased by 1 time, and the target component elements may be triggered multiple times during one (i.e. one) display of the application page.

Alternatively, the exposure instruction or the trigger instruction for the target component element may also be referred to as a user instruction or a program instruction.

The target event corresponding to one component element may be used to indicate when the target information may be created for the component element, in other words, if the target event corresponding to one component element is triggered, the corresponding target information may be created for the component element, which may be described below.

Step S103, if the target event corresponding to the target component element in the application page of the application program is triggered, creating target information according to the application page, the target component element and the page component to which the target component element belongs.

Optionally, if the target event corresponding to the target component element in the application page of the application program is triggered, the target information for the target component element may be created according to the application page (i.e. the page where the target component element is located), the target component element, and the page component to which the target component element belongs.

Referring to fig. 6, fig. 6 is a schematic page diagram of an application page provided in the present application. As shown in fig. 6, the application page may include a page area displayed by the page component 1, a page area displayed by the page component 2, and a page area displayed by the page component 3, where the page area displayed by the page component 3 may include a "view more" button belonging to a component element included in the page component 3. When the target event corresponding to the "view more" button is triggered, target information for the "view more" button can be created.

Optionally, if the target component element is a component element belonging to an exposure type, and the exposure frequency of the target component element in the application page reaches the exposure frequency threshold, it may be considered that a target event corresponding to the target component element is triggered, and then the target device may create corresponding target information according to the page identifier of the application page where the target component element is located, the element attribute information of the target component element, and the component identifier of the page component where the target component element belongs, where the target information records the page identifier of the application page where the target component element is located, the element attribute information of the target component element, and the component identifier of the page component where the target component element belongs.

Similarly, optionally, if the target component element is a component element belonging to the trigger type, and the trigger frequency of the target component element in the application page reaches the trigger frequency threshold, it may be considered that the target event corresponding to the target component element is triggered, and then the target device may create corresponding target information according to the page identifier of the application page where the target component element is located, the element attribute information of the target component element, and the component identifier of the page component to which the target component element belongs, where the target information records the page identifier of the application page where the target component element is located, the element attribute information of the target component element, and the component identifier of the page component to which the target component element belongs.

The target device may obtain url (i.e. a link, which may be referred to as page link information) of an application page where the target component element browsed by the user is located, where the page link information includes a page identifier (e.g. a page name) of the application page, so that the target device may extract the page identifier of the application page from the page link information.

In addition, the element attribute information of the target component element may be obtained by the target device after traversing the application folder, where the element attribute information may include element type information of the target component element and an element identifier (such as an element name of the component element), and the element name may be, for example, a file name of a configuration file of the target component element. The component identifier (e.g., component name) of the page component to which the target component element belongs may also be obtained by the target device when traversing the application folder, e.g., the component name may be a file name of a configuration file of the component.

Optionally, the target device may further generate at least one (a plurality of) initial information in advance according to each acquired page component and component elements included in each page component, where any one initial information may record a component identifier of one page component and element attribute information of one component element included in the page component. The target device may store the plurality of initial information in the component file in advance, and subsequently, when a target event corresponding to the target component element is triggered in the application page, the corresponding target information may be quickly and conveniently created directly based on the corresponding initial information.

Therefore, when the target event corresponding to the target component element in the application page is triggered, the target device can acquire initial information containing the element attribute information of the target component element, and integrate (e.g. add) the page identifier of the application page in the initial information, so as to obtain target information created for the target component element, where the target information is obtained after integrating the page identifier of the application page in the initial information. The page identifier of the application page may be denoted as a, the component identifier of the page component to which the target component element belongs is denoted as B, and the element attribute information of the target component element is denoted as C, and then the initial information may include B-C, and the target information created according to the initial information may include a-B-C.

Alternatively, for example, the component identifier of the page component may be obtained by scanning a component path of the page component obtained by the application folder, and for example, the component path of one page component may be: "packages/lct-components/compositions/fund/c-fundlist-step/c-fundlist-st eady. Js", then the component identifier of the page component obtained through the component path may be "c-fundlist-step", and the component element may include "list" and "button", so that two pieces of initial information, one being "c-fundlist-step. List", and one being "c-fundlist-step. Button", may be obtained. Furthermore, when the page link information url of the application page accessed by the user is 'https:// www.tencentwm.com/h5/v 6/pages/entry/index/index', and the target event corresponding to the target component element in the application page is triggered, the page link information may be extracted to obtain the page identifier of the application page, for example, the page identifier of the application page may be 'entry-index-index', the page identifier may be integrated with the two initial information, two target information may be obtained, one target information may be 'entry-index-index. C-fundamental-step. List', one target information may be 'entry-index-index. C-fundamental-step. Button', and the two created target information may be recorded in the data management platform of the application program.

Referring to fig. 7 a-7 b, fig. 7 a-7 b are schematic flow diagrams of creating target information provided in the present application. As shown in fig. 7a, first, the background may submit a component folder to the front end (e.g., an application in the target device), which may be submitted in the form of an update package or an installation package for the application, and thus the application in the target device may have the component folder therein.

The target device may scan the component folder, and use the folder name of the component folder as B for creating the target information, where B is the component identifier of the page component. The target device may also scan a logical file in the component folder, where the logical file includes a configuration file (e.g., an element file) of the component element, and by scanning the logical file, element information may be obtained as C for creating the target information, where C is element attribute information of the component element, and further, an application in the target device may automatically write B and C in the file element (e.g., an application folder).

Then, as shown in fig. 7b, S1: the user may access the application through the target device. S2: when a user accesses an application program and browses application pages of the application program, the target device may acquire url addresses (i.e., the page link information) of the application pages browsed by the user. S3: the target device may extract the page identity of the application page from url as a. S4: when the related program data for the component element (e.g., the target component element) in the application page meets the condition for creating the target information (e.g., the target event corresponding to the target component element is triggered), step S5 is performed. S5: the target device may splice a (component identification of the page component to which the target component element belongs) and C (element attribute information of the target component element) written in advance as data for creating the target information. S6: the target device may invoke a corresponding interface to create corresponding target information from the A, B and C. S7: after the target information is created, the related program data for the target component element can be acquired through the created target information and reported.

Referring to fig. 8, fig. 8 is a schematic view of a scenario describing a page component provided in the present application. As shown in FIG. 8, in a component project of an application program, one application page may have several page components, and different application pages may have the same page components. As here, the application pages that the application program has may include page 1, page 2, and page 3, where page 1 has page component 1 and page component 2, page 2 has page component 2, page component 3, and page component 4, and page 3 has page component 4, page component 5, and page component 6. It can be seen that page 1 and page 2 have in common page component 2, and that page 2 and page 3 have in common page component 4.

Referring to fig. 9, fig. 9 is a schematic flow chart of page information acquisition provided in the present application. As shown in fig. 9, the front end may refer to an application in the target device, and the background may refer to a background device of the application. When a user accesses an application page in an application program, the front end can request to perform page layout configuration to the background, then the background can return configuration json (a global configuration file) for performing page configuration to the front end, the front end can perform corresponding data processing (such as data validity verification (such as verifying that the configuration information is legal and performing corresponding page rendering) on the obtained configuration information (such as verifying that the configuration information is legal and performing corresponding page rendering) and data processing and distribution (such as issuing the configuration information to a corresponding component and performing page rendering) on the obtained configuration information, and further the application page can be rendered and displayed according to the configuration information for performing data processing, and the configuration information can also have page link information of the application page, so that information such as page identification of the application page can be obtained from the configuration information.

Referring to fig. 10, fig. 10 is a schematic page diagram of a data management platform provided in the present application. As shown in fig. 10, the data management platform may be a platform that manages relevant user data of an application program, and after B (identification information of a page component) and C (element attribute information) are written in the application program, component items of BC (which may be understood as the above initial information) may exist in the data management platform.

As shown in fig. 10, in the function field of component management of the data management platform, there are already 3 component items created, and IDs of the three component items are 1, 2, 3, respectively. Wherein each component item may have recorded a corresponding data source, component code, component description, classification, creator, etc. As here, the creator of the 3 component items may be "Jerry". B of the 1 st component item is a robust financial module, and C may include a product list item (element type in element attribute information). The 2 nd component item B is a guess you like module and C may include a product list item (element type in element attribute information). The 3 rd component item B is an advanced financial module, and C may include a product list item (element type in element attribute information). Clicking on "view" in the column behind the component item may also view more detailed information for the component item (e.g., more detailed information about B and C).

The present application may use a mixins function (a combination function) to trigger the creation of target information for a trigger type component element and the creation of target information for an exposure type component element in the onLoad lifecycle hook of a page.

According to the method, loader capability of a weback (module packer) can be utilized, before cli (command line interface) is started, vue-loader (vue (progressive framework for constructing a user interface) file loader) is compiled, all component nodes (namely page components) are scanned, corresponding event functions (namely corresponding target events) are added to component elements of the page components, meanwhile, the functions are exposed to each application page of an application program as a global minimum method (a method using the minimum function), target events for current component elements are acquired, target information corresponding to the component elements can be created if the target events of the component elements are triggered, and data reporting (such as reporting of program data of the component elements) can be triggered subsequently through the created target information when corresponding user instructions of the component elements are acquired.

For the creation of the target information of the exposure type component element, the application program interface (api) can be used to implement encapsulation of the exposure function, where the api provides a method for asynchronously detecting the intersection change of the target element and the ancestor element or viewport, after the page is initialized, a node (i.e., a user-visible component element) where the page element (i.e., a page element in an application page) and the screen visible area (i.e., a screen visible area) generate an intersection can be obtained through the api, and a callback is triggered to execute exposure reporting, i.e., report the exposure data of the intersection component element.

More, after the target device creates the target information corresponding to the target component element, the target information may be in the application program, and when the related program instruction for the target component element is acquired, the application program in the target device may perform data acquisition according to the target information, which specifically includes:

if the target component element is a component element of an exposure type, the data acquired from the target information may be exposure data for the target component element. For example, after the above-mentioned target information is created, when the target device obtains the exposure instruction for the target component in the application page, the application program in the target device may obtain the exposure data for the target component element according to the created target information, and the page component to which the target component element belongs may be denoted as page component a, so that the exposure data may be used to indicate that the target component element of the page component a is exposed in the application page to which the target component element belongs, and the exposure data may further include information such as a time stamp for exposing the target component element. The target device may also send the acquired exposure data for the target component element to a data storage device, which may further analyze and process the exposure data for the target component element. The data storage device may be a background device of the application.

If the target component element is a component element of the trigger type, the data acquired from the target information may be trigger data for the target component element. For example, after the target information is created, when the target device obtains the trigger instruction for the target component element in the application page, the application program in the target device may obtain trigger data for the target component element according to the created target information, and may mark the page component to which the target component element belongs as the page component b, so that the trigger data may be used to indicate that the target component element of the page component b is triggered in the application page to which the target component element belongs, and the trigger data may further include information such as a timestamp for triggering the target component element. The target device may also send the acquired trigger data for the target component element to the data storage device, where the data storage device may further analyze and process the trigger data for the target component element.

More, after the target device obtains the related program instruction (such as the exposure instruction or the trigger instruction) and obtains the related program data for the target component element through the target information, the target device may also obtain a data query request, where the data query request may carry the component identifier of the page component to which the target component element belongs. If the target component element belongs to the page component of the exposure type, acquiring and reporting exposure data of the target component element, and then inquiring the exposure data of the target component element acquired through the indication information by the target device according to the component identifier carried in the data inquiry request. If the target component element belongs to the page component of the trigger type, acquiring and reporting trigger data for the target component element, the target device can query the data storage device for the trigger data for the target component element acquired through the indication information according to the component identifier carried in the data query request. The indication information refers to the target information recorded with the component identifier carried by the data query request, namely the indication information refers to the target information recorded with the component identifier of the page component to which the target component element belongs.

From the foregoing, the application may query program data related to the component element (may also be referred to as application data or element data, such as exposure data or trigger data, as described above) acquired through the target information by the component identifier. More, the application can also query the related program data for the component element acquired through the target information through page identification or element attribute information of the component element on the same principle as the related program data of the corresponding component element is queried through the component identification. Alternatively, the application may also query the relevant program data for the component element acquired through the target information through the combination of the component identifier, the page identifier or the element attribute information of the component element.

According to the method and the device, the page component and the component elements included in the page component are automatically acquired, the relevant page identification, the component identification and the element attribute information are intelligently integrated through accumulated data (such as accumulated exposure times or trigger times for the component elements) of the component elements in the application page, corresponding target information is further created, multi-dimensional analyticity and integrated polymorphism of the created target information are realized, intelligent target information creation can be realized, efficiency of creating the target information is improved, the created target information is free, the target information corresponding to the component elements of all page components in the application page can be created, more complete and rich data acquisition (such as acquisition of relevant program data for the component elements) can be performed through the target information, and the acquired data can be queried through a rich data query mode (such as query of relevant program data for the component elements through combination of the component identification, the page identification or the element attribute information of the component elements).

Referring to fig. 11, fig. 11 is a schematic structural diagram of a data processing apparatus provided in the present application. The data processing apparatus may be a computer program (comprising program code) running in a computer device, for example the data processing apparatus is an application software, which may be used to perform the corresponding steps in the methods provided in the embodiments of the present application. The data processing apparatus may be applied to the above-described target device. As shown in fig. 11, the data processing apparatus 1 may include:

an obtaining module 11, configured to obtain at least one page component of an application program and component elements included in each page component;

An adding module 12, configured to add a target event to a component element included in each page component;

the creating module 13 is configured to create the target information according to the application page, the target component element, and the page component to which the target component element belongs if the target event corresponding to the target component element in the application page of the application program is triggered.

Alternatively, the apparatus 1 may be applied to a target device where an application program is located;

the acquiring module 11 acquires at least one page component of the application program and a component element contained in each page component, including:

acquiring an application folder of an application program in target equipment;

traversing the files in the application folder;

Optionally, if the target event corresponding to the target component element in the application page of the application program is triggered, the creating module 13 creates the target information according to the application page, the target component element, and the page component to which the target component element belongs, including:

Optionally, the target component element belongs to a page element in the application page; the above device 1 is also used for:

The above device 1 is also used for:

Optionally, the target component element belongs to a page control in the application page; the above device 1 is also used for:

Optionally, the above device 1 is further configured to:

acquiring page link information of an application page;

Optionally, the above device 1 is further configured to:

if the target event corresponding to the target component element is triggered, the creating module 13 creates the target information according to the page identifier of the application page, the element attribute information of the target component element, and the component identifier of the page component to which the target component element belongs, where the method includes:

Optionally, the above device 1 is further configured to:

if the target component element belongs to the page component of the exposure type, inquiring exposure data for the target component element acquired based on the indication information according to the component identifier carried in the data inquiry request;

According to one embodiment of the present application, the steps involved in the data processing method shown in fig. 3 may be performed by respective modules in the data processing apparatus 1 shown in fig. 11. For example, step S101 shown in fig. 3 may be performed by the acquisition module 11 in fig. 11, and step S102 shown in fig. 3 may be performed by the addition module 12 in fig. 11; step S103 shown in fig. 3 may be performed by the creation module 13 in fig. 11.

The method comprises the steps that at least one page component of an application program and component elements contained in each page component are obtained; adding a target event to the component elements contained in each page component; if the target event corresponding to the target component element in the application page of the application program is triggered, creating target information according to the application page, the target component element and the page component to which the target component element belongs. Therefore, the device provided by the application can add the target event to the component element, and further can intelligently create the target information through the condition that the target event is triggered, so that the efficiency and the accuracy of creating the target information are improved.

According to an embodiment of the present application, each module in the data processing apparatus 1 shown in fig. 11 may be separately or completely combined into one or several units to form a structure, or some (some) of the units may be further split into a plurality of sub-units with smaller functions, so that the same operation may be implemented without affecting the implementation of the technical effects of the embodiments of the present application. The above modules are divided based on logic functions, and in practical applications, the functions of one module may be implemented by a plurality of units, or the functions of a plurality of modules may be implemented by one unit. In other embodiments of the present application, the data processing device 1 may also comprise other units, and in practical applications, these functions may also be implemented with assistance from other units, and may be implemented by cooperation of a plurality of units.

According to one embodiment of the present application, the data processing apparatus 1 as shown in fig. 11 may be constructed by running a computer program (including program code) capable of executing the steps involved in the respective methods as shown in fig. 3 on a general-purpose computer device such as a computer including a processing element such as a Central Processing Unit (CPU), a random access storage medium (RAM), a read only storage medium (ROM), and the like, and a storage element, and the data processing method of the embodiments of the present application may be implemented. The computer program may be recorded on, for example, a computer-readable recording medium, and loaded into and executed by the computing device via the computer-readable recording medium.

Referring to fig. 12, fig. 12 is a schematic structural diagram of a computer device provided in the present application. As shown in fig. 12, the computer device 1000 may include: processor 1001, network interface 1004, and memory 1005, in addition, computer device 1000 may further comprise: a user interface 1003, and at least one communication bus 1002. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display (Display), a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface, among others. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 1005 may also optionally be at least one storage device located remotely from the processor 1001. As shown in fig. 12, an operating system, a network communication module, a user interface module, and a device control application program may be included in the memory 1005, which is one type of computer storage medium.

In the computer device 1000 shown in fig. 12, the network interface 1004 may provide network communication functions; while user interface 1003 is primarily used as an interface for providing input to a user; and the processor 1001 may be used to invoke a device control application stored in the memory 1005 to implement:

It should be understood that the computer device 1000 described in the embodiment of the present application may perform the description of the data processing method described above in the embodiment corresponding to fig. 3, and may also perform the description of the data processing apparatus 1 described above in the embodiment corresponding to fig. 11, which is not repeated herein. In addition, the description of the beneficial effects of the same method is omitted.

Furthermore, it should be noted here that: the present application further provides a computer readable storage medium, in which the aforementioned computer program executed by the data processing apparatus 1 is stored, and the computer program includes program instructions, when executed by a processor, can execute the description of the data processing method in the embodiment corresponding to fig. 3, and therefore, a detailed description will not be given here. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the computer storage medium related to the present application, please refer to the description of the method embodiments of the present application.

As an example, the above-described program instructions may be executed on one computer device or on a plurality of computer devices disposed at one site, or alternatively, on a plurality of computer devices distributed at a plurality of sites and interconnected by a communication network, which may constitute a blockchain network.

The computer readable storage medium may be the data processing apparatus provided in any one of the foregoing embodiments or an internal storage unit of the computer device, for example, a hard disk or a memory of the computer device. The computer readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a flash card (flash card) or the like, which are provided on the computer device. Further, the computer-readable storage medium may also include both internal storage units and external storage devices of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.

The present application provides a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device performs the description of the data processing method in the foregoing corresponding embodiment of fig. 3, and therefore, a detailed description will not be given here. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the computer-readable storage medium according to the present application, please refer to the description of the method embodiments of the present application.

The terms first, second and the like in the description and in the claims and drawings of the embodiments of the present application are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the term "include" and any variations thereof is intended to cover a non-exclusive inclusion. For example, a process, method, apparatus, article, or device that comprises a list of steps or elements is not limited to the list of steps or modules but may, in the alternative, include other steps or modules not listed or inherent to such process, method, apparatus, article, or device.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The methods and related devices provided in the embodiments of the present application are described with reference to the method flowcharts and/or structure diagrams provided in the embodiments of the present application, and each flowchart and/or block of the method flowcharts and/or structure diagrams may be implemented by computer program instructions, and combinations of flowcharts and/or blocks in the flowchart and/or block diagrams. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or structural diagram block or blocks. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or structures.

The foregoing disclosure is only illustrative of the preferred embodiments of the present application and is not intended to limit the scope of the claims herein, as the equivalent of the claims herein shall be construed to fall within the scope of the claims herein.

Claims

1. A method of data processing, the method comprising:

if a target event corresponding to a target component element in an application page of the application program is triggered, creating target information according to the application page, the target component element and a page component to which the target component element belongs.

2. The method of claim 1, wherein the method is performed by a target device on which the application is located;

the acquiring at least one page component of the application program and component elements contained in each page component comprises the following steps:

acquiring an application folder of the application program in the target equipment;

traversing the files in the application folder;

and determining the at least one page component according to the traversed component file, and determining the component elements contained in each page component according to the traversed element file.

3. The method according to claim 1, wherein if the target component element belongs to a component element of an exposure type, the target event added to the target component element is an event in which the exposure times reach an exposure times threshold; and if the target component element is a component element of a trigger type, the target event added for the target component element is an event of which the trigger frequency reaches a trigger frequency threshold.

4. The method according to claim 3, wherein if the target event corresponding to the target component element in the application page of the application program is triggered, creating the target information according to the application page, the target component element, and the page component to which the target component element belongs includes:

if the target component element belongs to a page component of an exposure type and the exposure times of the target component element in the application page reach the exposure times threshold, determining that a target event corresponding to the target component element is triggered;

if the target event corresponding to the target component element is triggered, creating the target information according to the page identifier of the application page, the element attribute information of the target component element and the component identifier of the page component to which the target component element belongs.

5. The method of claim 4, wherein the target component element belongs to a page element in the application page; the method further comprises the steps of:

acquiring page elements in a screen visualization area of the application page in the display process of the application page;

and if the page element in the screen visualization area comprises the target component element, determining that the target component element is exposed.

6. The method according to claim 4, wherein the method further comprises:

when an exposure instruction for the target component element is acquired in the application page, acquiring exposure data for the target component element according to the target information;

and transmitting the exposure data for the target component element to a data storage device.

7. The method according to claim 3, wherein if the target event corresponding to the target component element in the application page of the application program is triggered, creating the target information according to the application page, the target component element, and the page component to which the target component element belongs includes:

if the target component element belongs to a trigger type page component and the trigger frequency of the target component element in the application page reaches the trigger frequency threshold, determining that a target event corresponding to the target component element is triggered;

8. The method of claim 7, wherein the target component element belongs to a page control in the application page; the method further comprises the steps of:

when a trigger instruction for the target component element is acquired in the application page, determining that the target component element is triggered.

9. The method of claim 7, wherein the method further comprises:

when a trigger instruction aiming at the target component element is acquired in the application page, acquiring trigger data aiming at the target component element according to the target information;

and sending the trigger data for the target component element to a data storage device.

10. The method according to claim 4 or 7, characterized in that the method further comprises:

generating at least one initial message according to the assembly elements contained in each page assembly; any initial information records the component identification of a page component and the element attribute information of a component element contained in the page component;

If the target event corresponding to the target component element is triggered, creating the target information according to the page identifier of the application page, the element attribute information of the target component element and the component identifier of the page component to which the target component element belongs, including:

if the target event corresponding to the target component element in the application page is triggered, integrating the page identification of the application page in the initial information containing the element attribute information of the target component element to obtain the target information.

11. The method according to claim 6 or 9, characterized in that the method further comprises:

if the target component element belongs to a page component of a trigger type, inquiring trigger data for the target component element acquired based on indication information according to a component identifier carried by the data inquiry request;

The indication information is the target information recorded with the component identifier carried by the data query request.

12. A data processing apparatus, the apparatus comprising:

the creation module is used for creating target information according to the application page, the target component element and a page component to which the target component element belongs if a target event corresponding to the target component element in the application page of the application program is triggered.

13. A computer program product comprising computer programs/instructions which, when executed by a processor, implement the steps of the method of any of claims 1-11.

14. A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method of any of claims 1-11.

15. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program adapted to be loaded by a processor and to perform the method of any of claims 1-11.