CN111797025A - Data processing method and device for application - Google Patents
Data processing method and device for application Download PDFInfo
- Publication number
- CN111797025A CN111797025A CN202010692004.6A CN202010692004A CN111797025A CN 111797025 A CN111797025 A CN 111797025A CN 202010692004 A CN202010692004 A CN 202010692004A CN 111797025 A CN111797025 A CN 111797025A
- Authority
- CN
- China
- Prior art keywords
- target page
- page
- activity
- fragment
- source
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 20
- 238000000034 method Methods 0.000 claims abstract description 144
- 230000000694 effects Effects 0.000 claims abstract description 98
- 239000012634 fragment Substances 0.000 claims abstract description 95
- 238000012545 processing Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 2
- 238000012423 maintenance Methods 0.000 abstract description 5
- 238000004458 analytical method Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 239000011800 void material Substances 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000007943 implant Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
Abstract
The application discloses a data processing method and device for an application, and a first logic process is operated under the condition that a user triggers application use. And according to the Activity life cycle, the Fragment life cycle and the preset corresponding relationship, counting the source of the target page accessed by the user, the source of the target page source and the access duration of the target page to obtain a first statistical result, wherein the preset corresponding relationship comprises a pre-deployed configuration file. And running a second logic process and sending the statistical result to the back end. Therefore, based on the first logic process and the configuration file which are deployed in advance, the source of the target page accessed by the user, the source of the target page and the access duration of the target page can be counted, and a counting process is not required to be implanted into the bottom logic of the target page, so that the code quantity implanted into the bottom logic of the application can be reduced. And the logic of the first logic process and the configuration file is simpler, the later maintenance and upgrading are more convenient, and the applicability is stronger.
Description
Technical Field
The present application relates to the field of programming development technologies, and in particular, to a data processing method and apparatus for an application.
Background
In order to satisfy the tracking analysis of the web page data of an Application (Application), statistics needs to be performed on a source of a page accessed by a user, a source of the page source (i.e., a jump relationship between pages), an access duration of the page, and an event performed in the page (e.g., a user clicks an event in a special column of the page, or a picture link, etc., and a corresponding extension parameter is usually set for the event in a statistical process, i.e., a parameter for recording the event according to a service requirement).
At present, a conventional data processing method for an application is to implant a statistical process in a bottom logic of each page, run the statistical process in a process that a user accesses the page, record a source of the page, a source of the page source, an access duration of the page, and an event performed in the page, count a recorded result of each page, and send the counted result to a back end. Because a statistical process needs to be embedded in the underlying logic of each page, the conventional data processing method for the application has the following disadvantages:
1. there is a lot of process redundancy (i.e. more duplicated code) and memory resources of the application are increased.
2. The number of pages in the application is large, and the statistical process of each page is difficult to maintain.
3. The complexity of the application bottom logic is increased, so that the running performance of the application is reduced.
Disclosure of Invention
The application provides a data processing method and device for an application, and aims to provide a simple data processing scheme for the application.
In order to achieve the above object, the present application provides the following technical solutions:
a data processing method for an application, applied to the application, comprises the following steps:
running a first logic process which is deployed in advance under the condition that a user triggers the application to be used; wherein, the first logic process is used for detecting the life cycle of Activity and the life cycle of Fragment;
according to the life cycle of the Activity, the life cycle of the Fragment and a preset corresponding relation, counting a source of a target page accessed by the user, a source of the target page and the access duration of the target page to obtain a first statistical result; wherein the preset corresponding relationship comprises a corresponding relationship among the target page, the Activity and the Fragment indicated in a pre-deployed configuration file;
running a pre-implanted statistical process in a non-target page, and counting the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result;
running a second logic process which is deployed in advance, and sending the statistical result to the back end; wherein the second logical process is configured to perform request and resolution of network data; the statistical result comprises the first statistical result and the second statistical result.
Optionally, the method further includes:
running an event counting process pre-implanted in a page, and counting the name of an event which occurs in the page accessed by the user, the time of the event generation and the change of an expansion parameter of the event to obtain a third counting result;
the statistical result further comprises:
the third statistical result.
Optionally, the target page includes an Activity page and a Fragment page.
Optionally, the correspondence among the target page, the Activity, and the Fragment indicated in the pre-deployed configuration file includes:
and the correspondence between the name of the Activity and the name of the Activity page.
Optionally, the correspondence among the target page, the Activity, and the Fragment indicated in the pre-deployed configuration file includes:
and the name of the Activity, the name of a preset page calling interface in the Activity and the name of the Activity page are in corresponding relation.
Optionally, the correspondence among the target page, the Activity, and the Fragment indicated in the pre-deployed configuration file includes:
and the corresponding relation among the name of the Fragment, the name of a preset page calling interface in the Fragment and the name of the Fragment page.
Optionally, before the running the first logic process deployed in advance, the method further includes:
pre-configuring a server address;
sending the statistical result to the back end comprises:
and sending the statistical result to the back end according to the corresponding relation between the server address and the back end.
A data processing apparatus for an application, comprising:
the running unit is used for running a first logic process which is deployed in advance under the condition that a user triggers the application to be used; wherein, the first logic process is used for detecting the life cycle of Activity and the life cycle of Fragment;
a first statistical unit, configured to count a source of the target page visited by the user, a source of the target page, and a visit duration of the target page according to the life cycle of the Activity, the life cycle of the Fragment, and a preset corresponding relationship, so as to obtain a first statistical result; wherein the preset corresponding relationship comprises a corresponding relationship among the target page, the Activity and the Fragment indicated in a pre-deployed configuration file;
the second statistical unit is used for running a pre-implanted statistical process in a non-target page, and performing statistics on the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result;
the sending unit is used for running a second logic process which is deployed in advance and sending the first statistical result and the second statistical result to a back end; wherein the second logical process is configured to perform request and resolution of network data.
A computer-readable storage medium, on which a computer program is stored, which, when run on a computer, executes the data processing method for an application.
A data processing apparatus for an application, comprising: a processor, a memory, and a bus; the processor and the memory are connected through the bus;
the memory is used for storing programs, and the processor is used for running programs, wherein the programs execute the data processing method for the application when running.
According to the technical scheme, a first logic process which is deployed in advance is operated under the condition that a user triggers application use, wherein the first logic process is used for detecting the life cycle of Activity and the life cycle of Fragment. And according to the life cycle of the Activity, the life cycle of the Fragment and a preset corresponding relationship, wherein the preset corresponding relationship comprises a corresponding relationship among the target page, the Activity and the Fragment indicated in the pre-deployed configuration file. And counting the source of the target page accessed by the user, the source of the target page and the access duration of the target page to obtain a first statistical result. And running a pre-implanted statistical process in the non-target page, and counting the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result. And running a second logic process which is deployed in advance, and sending the statistical result to the back end, wherein the second logic process is used for executing the request and analysis of the network data, and the statistical result comprises a first statistical result and a second statistical result. Therefore, based on the first logic process and the configuration file which are deployed in advance, the source of the target page accessed by the user, the source of the target page and the access duration of the target page can be counted under the condition that the user triggers the application to use, and the counting process is not required to be implanted into the bottom logic of the target page, so that the code amount implanted into the bottom logic of the application can be reduced, and the memory resource of the application can be reduced. And the logic of the first logic process and the configuration file is simpler, the later maintenance and upgrading are more convenient, and the applicability is stronger. In addition, the application runs the first logic process in the using process, and the running performance of the application is not reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram of a data processing method for an application according to an embodiment of the present application;
fig. 2 is a schematic diagram of another data processing method for an application according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a data processing apparatus for an application according to an embodiment of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
As shown in fig. 1, a schematic diagram of a data processing method for an application provided in an embodiment of the present application includes the following steps:
s101: the application deploys a first logic process, a second logic process, a third logic process, a fourth logic process, a fifth logic process, a sixth logic process and a configuration file in advance based on a preset Software Development Kit (SDK).
The system comprises a first logic process, a second logic process, a third logic process, a fourth logic process, a fifth logic process, a sixth logic process and a configuration file, wherein the first logic process is used for detecting the life cycle of Activity and the life cycle of Fragment, the second logic process is used for executing a request and analysis of network data, the third logic process is used for executing a confusion strategy, the fourth logic process is used for implanting a preset statistical process in a non-target page, the fifth logic process is used for implanting a preset event statistical process in a page, the sixth logic process is used for configuring a server address, information of application equipment and information of a user, and the configuration file is used for recording the corresponding relation among the target page, the Activity and the Fragment.
It should be noted that, in this embodiment, the application is developed based on an Android system, and therefore, most pages in the application are constructed based on Activity (a basic component provided by the Android system is a visual interface operated by a user, and the Activity component provides an interface of a window for completing an operation instruction for the user) and Fragment (a behavior Fragment in the Activity component or an interface Fragment understood as a window), in other words, the pages may be summarized as Activity pages, Fragment pages, and other types of pages.
S102: under the condition that the user triggers the application to use, the application runs a first logic process and acquires the life cycle of Activity and the life cycle of Fragment.
Wherein, the lifecycle of Activity can be used to indicate the source and access duration of the Activity page, and the lifecycle of Fragment can be used to indicate the source and access duration of the Fragment page.
In a specific implementation, base classes, namely, the futalanytics Activity class, the futalanytics Fragment class, and the futalanytics Fragment Activity class, existing data types provided by the Android system, may be called to implement the detection of the life cycle of Activity and the life cycle of Fragment, for example, in a case where a Fragment page is switched from a Fragment page, a viewport component may be called to detect the life cycle of Fragment of a Fragment page.
S103: the application counts the source of the target page accessed by the user, the source of the target page and the access duration of the target page according to the life cycle of the Activity, the life cycle of the Fragment and the preset corresponding relation, and obtains a first statistical result.
The preset corresponding relationship comprises a corresponding relationship among a target page, Activity and Fragment indicated in a pre-deployed configuration file. The target page comprises an Activity page and a Fragment page, and because the type of each page in the application is preset by a developer, the corresponding relation among the target page, the Activity and the Fragment needs to be set by the developer according to the actual situation. In this embodiment, the configuration file may specifically be a json file (for example, a json file mentioned below in terms of futanalytics config).
Specifically, for a case where one Activity corresponds to one Activity page (for example, a home page), the developer may configure a correspondence between the name of the Activity and the name of the Activity page in the futalanytics config.
For a situation that one Activity corresponds to multiple Activity pages, a developer may configure, in a futanalytics config.
For the case that one Activity corresponds to multiple Fragment pages, a developer can configure the corresponding relationship among the name of Fragment, the name of getPageName interface for calling Fragment pages in the Activity, and the name of Fragment pages in the futanalytics config.
It should be noted that the above specific implementation process is only for illustration.
S104: and the application runs a pre-implanted statistical process in the non-target page, and counts the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result.
Wherein the non-target page includes: pages that fail to detect the lifecycle of Activity, or the lifecycle of Fragment.
It should be noted that, for a page that cannot detect the life cycle of Activity or the life cycle of Fragment, for example, a certain page may only know the Activity of the page after the getPageName interface feeds back the request, and thus cannot detect the life cycle of Activity, or a situation that the first page is switched to the second page, but the second page is not a Fragment page, and thus cannot detect the life cycle of Fragment of the second page, or a switching manner between Fragment pages is explicit control, that is, the life cycles of Fragment of two Fragment pages cannot be managed by the viewport component, and thus cannot detect the life cycles of Fragment of the two Fragment pages.
Specifically, in this embodiment, the following logic may be adopted as the statistical process of the non-target page:
recordpagestart (this); // page display time invocation
Record PageEnd (); // Call when Page is hidden
Ontargeparameters (map); the/set map extension parameter is invoked between the above two calls.
It should be noted that the above specific implementation process is only for illustration.
S105: and applying an event counting process pre-implanted in the running page, and counting the name of an event occurring in the page accessed by the user, the time of the event generation and the change of an expansion parameter of the event to obtain a third counting result.
In the business requirement for data processing of the application, not only the source of the page, the source of the page source, and the access duration of the page are counted, but also each event occurring in the page needs to be counted. To do this, an event statistics process needs to be implanted in the underlying logic of the page with event logging requirements.
Specifically, in this embodiment, the following logic may be adopted as the event counting process:
oneevent ("search", futmp); // "search" denotes an event, futmp denotes an extended parameter.
Ontargeparameters (map); v/invoke the extended parameter map after the resume method of Activity or Fragment (i.e., enter page) and before the resume method (i.e., leave page).
It should be noted that the above specific implementation process is only for illustration.
It should be emphasized that the specific execution sequence of S104 and S105 includes, but is not limited to, the sequence described in this embodiment, for example, S102, S104, and S105 may also be executed in parallel.
S106: and the application runs a second logic process and sends the first statistical result, the second statistical result and the third statistical result to the back end.
The application can execute the request and analysis of the network data only after the address of the server, the information of the device to which the application belongs and the information of the user are configured in advance, namely, the first statistical result, the second statistical result and the third statistical result are sent to the back end according to the corresponding relation between the address of the server at the back end and the back end.
Specifically, the server address, the information of the device to which the application belongs, and the information of the user are configured, and the specific implementation logic is as follows:
FUTAnalytics.initialize(this,true,newFUTAnalyticsInterfaceListener(){
@ Override server address for submitting logs
public String getServiceUrl(){
return serviceUrl}
@ Override device and user information
public HashMap<String,String>getHeadMaps(){
returnheadMaps；
}
@ Override device and user information
public HeadModel getHeadModel(){
returnheadModel；
}
Network conditions at @ Override log generation
public String getNetWorkType(){
returnApn.network；
}
@ Override City selected by user when generating Each Log
public String getCity(){
returnUtilsVar.CITY；
}
@ overlaride coordinate x of user when generating each log
public String getX(){
returnUtilsVar.LOCATION_X；
}
@ Override coordinate y of user when generating each log
public String getY(){
returnUtilsVar.LOCATION_Y；
}
@ Override time callback
public void oneventcallback(String category,String action,Stringlabel){
GAAnalytice.trackEvent(category,action,label)；
}
@ Override page callback
public void onpagecallback(Stringpagename){
GAAnalytice.showPageView(pagename)
}
}
It should be noted that the above specific implementation process is only for illustration.
In summary, when the user triggers the application to use, the first logic process deployed in advance is run, where the first logic process is used to detect the life cycle of Activity and the life cycle of Fragment. And counting the source of the target page accessed by the user, the source of the target page and the access duration of the target page according to the life cycle of the Activity, the life cycle of the Fragment and a preset corresponding relationship to obtain a first statistical result, wherein the preset corresponding relationship comprises the corresponding relationship among the target page, the Activity and the Fragment indicated in the pre-deployed configuration file. And running a pre-implanted statistical process in the non-target page, and counting the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result. And running an event counting process pre-implanted in the page, and counting the name of an event which occurs in the page accessed by the user, the time of generating the event and the change of an expansion parameter of the event to obtain a third counting result. And running a second logic process which is deployed in advance, and sending the first statistical result, the second statistical result and the third statistical result to the back end, wherein the second logic process is used for executing a request and analysis of network data. Therefore, based on the first logic process and the configuration file which are deployed in advance, the source of the target page accessed by the user, the source of the target page and the access duration of the target page can be counted under the condition that the user triggers the application to use, and the counting process is not required to be implanted into the bottom logic of the target page, so that the code amount implanted into the bottom logic of the application can be reduced, and the memory resource of the application can be reduced. And the logic of the first logic process and the configuration file is simpler, the later maintenance and upgrading are more convenient, and the applicability is stronger. In addition, the application runs the first logic process in the using process, and the running performance of the application is not reduced.
It should be noted that the flows mentioned in the above embodiments may be summarized as the method shown in fig. 2.
As shown in fig. 2, a schematic diagram of another data processing method for an application provided in the embodiment of the present application includes the following steps:
s201: in the event that a user triggers application usage, a first logical process that is pre-deployed is run.
Wherein, the first logic process is used for detecting the life cycle of Activity and the life cycle of Fragment.
S202: and according to the Activity life cycle, the Fragment life cycle and the preset corresponding relation, counting the source of the target page accessed by the user, the source of the target page source and the access duration of the target page to obtain a first counting result.
The preset corresponding relationship comprises a corresponding relationship among a target page, Activity and Fragment indicated in a pre-deployed configuration file. The destination page includes an Activity page and a Fragment page.
S203: and running a pre-implanted statistical process in the non-target page, and counting the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result.
S204: and running a second logic process which is deployed in advance, and sending the statistical result to the back end.
The second logic process is used for executing the request and analysis of the network data, and the statistical result comprises a first statistical result and a second statistical result.
Optionally, the statistical result further includes a third statistical result. And the third statistical result is obtained by running an event statistical process pre-implanted in the page, and counting the name of an event occurring in the page accessed by the user, the time of the event generation and the change of an expansion parameter of the event.
In summary, when the user triggers the application to use, the first logic process deployed in advance is run, where the first logic process is used to detect the life cycle of Activity and the life cycle of Fragment. And counting the source of the target page accessed by the user, the source of the target page and the access duration of the target page according to the life cycle of the Activity, the life cycle of the Fragment and a preset corresponding relationship to obtain a first statistical result, wherein the preset corresponding relationship comprises the corresponding relationship among the target page, the Activity and the Fragment indicated in the pre-deployed configuration file. And running a pre-implanted statistical process in the non-target page, and counting the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result. And running a second logic process which is deployed in advance, and sending the statistical result to the back end, wherein the second logic process is used for executing the request and analysis of the network data, and the statistical result comprises a first statistical result and a second statistical result. Therefore, based on the first logic process and the configuration file which are deployed in advance, the source of the target page accessed by the user, the source of the target page and the access duration of the target page can be counted under the condition that the user triggers the application to use, and the counting process is not required to be implanted into the bottom logic of the target page, so that the code amount implanted into the bottom logic of the application can be reduced, and the memory resource of the application can be reduced. And the logic of the first logic process and the configuration file is simpler, the later maintenance and upgrading are more convenient, and the applicability is stronger. In addition, the application runs the first logic process in the using process, and the running performance of the application is not reduced.
Corresponding to the data processing method for the application provided by the embodiment of the application, the application also provides a data processing device for the application.
As shown in fig. 3, a schematic structural diagram of a data processing apparatus for an application provided in an embodiment of the present application includes:
a configuration unit 100, configured to pre-configure a server address.
The running unit 200 is configured to run a first logic process deployed in advance when a user triggers application usage. Wherein, the first logic process is used for detecting the life cycle of Activity and the life cycle of Fragment.
The first statistical unit 300 is configured to count a source of a target page accessed by a user, a source of the target page, and an access duration of the target page according to the life cycle of Activity, the life cycle of Fragment, and a preset corresponding relationship, so as to obtain a first statistical result. The preset corresponding relation comprises a corresponding relation among a target page, Activity and Fragment indicated in a pre-deployed configuration file, and the target page comprises an Activity page and a Fragment page. The corresponding relationship among the target page, Activity and Fragment includes: the method comprises the steps of obtaining the corresponding relation between the name of Activity and the name of an Activity page, obtaining the corresponding relation between the name of Activity, the name of a preset page calling interface in Activity and the name of the Activity page, and obtaining the corresponding relation between the name of Fragment, the name of a preset page calling interface in Fragment and the name of a Fragment page.
The second statistical unit 400 is configured to run a pre-embedded statistical process in the non-target page, and perform statistics on a source of the non-target page accessed by the user, a source of the non-target page source, and an access duration of the non-target page to obtain a second statistical result.
The third statistical unit 500 is configured to run an event statistical process pre-embedded in the page, and perform statistics on the name of an event occurring in the page accessed by the user, the time of the event generation, and the change of an extension parameter of the event to obtain a third statistical result.
And a sending unit 600, configured to run a second logic process deployed in advance, and send the statistical result to the back end. The second logic process is used for executing the request and analysis of the network data, and the statistical result comprises a first statistical result, a second statistical result and a third statistical result.
The specific implementation process of the sending unit 600 for sending the statistical result to the back end includes: and sending the statistical result to the back end according to the corresponding relation between the server address and the back end.
In summary, when the user triggers the application to use, the first logic process deployed in advance is run, where the first logic process is used to detect the life cycle of Activity and the life cycle of Fragment. And counting the source of the target page accessed by the user, the source of the target page and the access duration of the target page according to the life cycle of the Activity, the life cycle of the Fragment and a preset corresponding relationship to obtain a first statistical result, wherein the preset corresponding relationship comprises the corresponding relationship among the target page, the Activity and the Fragment indicated in the pre-deployed configuration file. And running a pre-implanted statistical process in the non-target page, and counting the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result. And running a second logic process which is deployed in advance, and sending the statistical result to the back end, wherein the second logic process is used for executing the request and analysis of the network data, and the statistical result comprises a first statistical result and a second statistical result. Therefore, based on the first logic process and the configuration file which are deployed in advance, the source of the target page accessed by the user, the source of the target page and the access duration of the target page can be counted under the condition that the user triggers the application to use, and the counting process is not required to be implanted into the bottom logic of the target page, so that the code amount implanted into the bottom logic of the application can be reduced, and the memory resource of the application can be reduced. And the logic of the first logic process and the configuration file is simpler, the later maintenance and upgrading are more convenient, and the applicability is stronger. In addition, the application runs the first logic process in the using process, and the running performance of the application is not reduced.
The present application also provides a computer-readable storage medium including a stored program, wherein the program executes the data processing method for an application provided in the present application.
The present application also provides a data processing apparatus for an application, comprising: a processor, a memory, and a bus. The processor is connected with the memory through a bus, the memory is used for storing programs, and the processor is used for running the programs, wherein when the programs are run, the data processing method for the application provided by the application is executed, and the method comprises the following steps:
running a first logic process which is deployed in advance under the condition that a user triggers the application to be used; wherein, the first logic process is used for detecting the life cycle of Activity and the life cycle of Fragment;
according to the life cycle of the Activity, the life cycle of the Fragment and a preset corresponding relation, counting the source of the target page accessed by the user, the source of the target page and the access duration of the target page to obtain a first statistical result; wherein the preset corresponding relationship comprises a corresponding relationship among the target page, the Activity and the Fragment indicated in a pre-deployed configuration file;
running a pre-implanted statistical process in a non-target page, and counting the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result;
running a second logic process which is deployed in advance, and sending the statistical result to the back end; wherein the second logical process is configured to perform request and resolution of network data; the statistical result comprises the first statistical result and the second statistical result.
Optionally, the method further includes:
running an event counting process pre-implanted in a page, and counting the name of an event which occurs in the page accessed by the user, the time of the event generation and the change of an expansion parameter of the event to obtain a third counting result;
the statistical result further comprises:
the third statistical result.
Optionally, the target page includes an Activity page and a Fragment page.
Optionally, the correspondence among the target page, the Activity, and the Fragment indicated in the pre-deployed configuration file includes:
and the correspondence between the name of the Activity and the name of the Activity page.
Optionally, the correspondence among the target page, the Activity, and the Fragment indicated in the pre-deployed configuration file includes:
and the name of the Activity, the name of a preset page calling interface in the Activity and the name of the Activity page are in corresponding relation.
Optionally, the correspondence among the target page, the Activity, and the Fragment indicated in the pre-deployed configuration file includes:
and the corresponding relation among the name of the Fragment, the name of a preset page calling interface in the Fragment and the name of the Fragment page.
Optionally, before the running the first logic process deployed in advance, the method further includes:
pre-configuring a server address;
the statistical result is sent to the back end, including:
and sending the statistical result to the back end according to the corresponding relation between the server address and the back end.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A data processing method for an application is characterized in that the method is applied to the application and comprises the following steps:
running a first logic process which is deployed in advance under the condition that a user triggers the application to be used; wherein, the first logic process is used for detecting the life cycle of Activity and the life cycle of Fragment;
according to the life cycle of the Activity, the life cycle of the Fragment and a preset corresponding relation, counting a source of a target page accessed by the user, a source of the target page and the access duration of the target page to obtain a first statistical result; wherein the preset corresponding relationship comprises a corresponding relationship among the target page, the Activity and the Fragment indicated in a pre-deployed configuration file;
running a pre-implanted statistical process in a non-target page, and counting the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result;
running a second logic process which is deployed in advance, and sending the statistical result to the back end; wherein the second logical process is configured to perform request and resolution of network data; the statistical result comprises the first statistical result and the second statistical result.
2. The method of claim 1, further comprising:
running an event counting process pre-implanted in a page, and counting the name of an event which occurs in the page accessed by the user, the time of the event generation and the change of an expansion parameter of the event to obtain a third counting result;
the statistical result further comprises:
the third statistical result.
3. The method of claim 1, wherein the destination page comprises an Activity page and a Fragment page.
4. The method according to claim 3, wherein the correspondence among the target page, the Activity, and the Fragment indicated in the pre-deployed configuration file comprises:
and the correspondence between the name of the Activity and the name of the Activity page.
5. The method of claim 3, wherein the correspondence between the target page, the Activity, and the Fragment indicated in the pre-deployed configuration file comprises:
and the name of the Activity, the name of a preset page calling interface in the Activity and the name of the Activity page are in corresponding relation.
6. The method according to claim 3, wherein the correspondence among the target page, the Activity, and the Fragment indicated in the pre-deployed configuration file comprises:
and the corresponding relation among the name of the Fragment, the name of a preset page calling interface in the Fragment and the name of the Fragment page.
7. The method of claim 1, wherein prior to the running the pre-deployed first logical process, further comprising:
pre-configuring a server address;
sending the statistical result to the back end comprises:
and sending the statistical result to the back end according to the corresponding relation between the server address and the back end.
8. A data processing apparatus for an application, comprising:
the running unit is used for running a first logic process which is deployed in advance under the condition that a user triggers the application to be used; wherein, the first logic process is used for detecting the life cycle of Activity and the life cycle of Fragment;
a first statistical unit, configured to count a source of the target page visited by the user, a source of the target page, and a visit duration of the target page according to the life cycle of the Activity, the life cycle of the Fragment, and a preset corresponding relationship, so as to obtain a first statistical result; wherein the preset corresponding relationship comprises a corresponding relationship among the target page, the Activity and the Fragment indicated in a pre-deployed configuration file;
the second statistical unit is used for running a pre-implanted statistical process in a non-target page, and performing statistics on the source of the non-target page accessed by the user, the source of the non-target page source and the access duration of the non-target page to obtain a second statistical result;
the sending unit is used for running a second logic process which is deployed in advance and sending the first statistical result and the second statistical result to a back end; wherein the second logical process is configured to perform request and resolution of network data.
9. A computer-readable storage medium, on which a computer program is stored, which, when run on a computer, performs the data processing method for an application of claims 1-7.
10. A data processing device for an application, comprising: a processor, a memory, and a bus; the processor and the memory are connected through the bus;
the memory is used for storing a program and the processor is used for running the program, wherein the program executes the data processing method for the application according to the claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010692004.6A CN111797025B (en) | 2020-07-17 | 2020-07-17 | Application-oriented data processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010692004.6A CN111797025B (en) | 2020-07-17 | 2020-07-17 | Application-oriented data processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111797025A true CN111797025A (en) | 2020-10-20 |
| CN111797025B CN111797025B (en) | 2023-11-14 |
Family
ID=72807630
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010692004.6A Active CN111797025B (en) | 2020-07-17 | 2020-07-17 | Application-oriented data processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111797025B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112651012A (en) * | 2020-12-28 | 2021-04-13 | 五八同城信息技术有限公司 | Information processing method and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060085420A1 (en) * | 2004-09-27 | 2006-04-20 | Symphoniq Corp. | Method and apparatus for monitoring real users experience with a website |
| WO2017167042A1 (en) * | 2016-04-01 | 2017-10-05 | 阿里巴巴集团控股有限公司 | Statistical method and apparatus for behaviors of front-end users |
| CN107784065A (en) * | 2017-08-17 | 2018-03-09 | 平安壹钱包电子商务有限公司 | Business datum tracking, device, computer equipment and storage medium |
| CN107797908A (en) * | 2017-11-07 | 2018-03-13 | 南威软件股份有限公司 | A kind of behavioral data acquisition method of website user |
| CN109376322A (en) * | 2018-09-07 | 2019-02-22 | 平安科技（深圳）有限公司 | A kind of grayscale version page access method, apparatus, computer equipment and computer storage medium |
| CN110750744A (en) * | 2019-10-11 | 2020-02-04 | 浙江口碑网络技术有限公司 | Page presentation method and device |
| CN110781372A (en) * | 2019-10-28 | 2020-02-11 | 珠海格力电器股份有限公司 | Method and device for optimizing website, computer equipment and storage medium |
-
2020
- 2020-07-17 CN CN202010692004.6A patent/CN111797025B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060085420A1 (en) * | 2004-09-27 | 2006-04-20 | Symphoniq Corp. | Method and apparatus for monitoring real users experience with a website |
| WO2017167042A1 (en) * | 2016-04-01 | 2017-10-05 | 阿里巴巴集团控股有限公司 | Statistical method and apparatus for behaviors of front-end users |
| CN107784065A (en) * | 2017-08-17 | 2018-03-09 | 平安壹钱包电子商务有限公司 | Business datum tracking, device, computer equipment and storage medium |
| CN107797908A (en) * | 2017-11-07 | 2018-03-13 | 南威软件股份有限公司 | A kind of behavioral data acquisition method of website user |
| CN109376322A (en) * | 2018-09-07 | 2019-02-22 | 平安科技（深圳）有限公司 | A kind of grayscale version page access method, apparatus, computer equipment and computer storage medium |
| CN110750744A (en) * | 2019-10-11 | 2020-02-04 | 浙江口碑网络技术有限公司 | Page presentation method and device |
| CN110781372A (en) * | 2019-10-28 | 2020-02-11 | 珠海格力电器股份有限公司 | Method and device for optimizing website, computer equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112651012A (en) * | 2020-12-28 | 2021-04-13 | 五八同城信息技术有限公司 | Information processing method and device |
| CN112651012B (en) * | 2020-12-28 | 2023-03-24 | 五八同城信息技术有限公司 | Information processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111797025B (en) | 2023-11-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10489283B2 (en) | Software defect reporting | |
| CN109062806B (en) | Program testing method, system, device and computer readable storage medium | |
| US9558055B2 (en) | System level memory leak detection | |
| US20080282233A1 (en) | Rapid application innovation utilizing an orthogonal programming component | |
| CN102880546A (en) | Software integration testing method and system based on extensible markup language (XML) database | |
| JP2009524856A (en) | Qualitatively annotated code | |
| CN104683180A (en) | Performance monitoring method and system as well as application server | |
| US10725893B2 (en) | System and method for determination of code coverage for software applications in a network environment | |
| CN105893061A (en) | Application program development method and system | |
| CN110309029A (en) | Acquisition method, device, computer equipment and the storage medium of abnormal data | |
| CN107608609B (en) | Event object sending method and device | |
| CN110704097A (en) | Data collection method and device, electronic equipment and storage medium | |
| CN111966603B (en) | Memory leakage detection method and device, readable storage medium and electronic equipment | |
| Panigrahi et al. | An approach to prioritize the regression test cases of object-oriented programs | |
| CN114880159B (en) | Data processing method, device, equipment and storage medium | |
| CN110968296B (en) | Data acquisition method, device, equipment and readable storage medium | |
| CN111797025B (en) | Application-oriented data processing method and device | |
| CN113220403B (en) | Method and device for h5 intercepting Android return event and electronic equipment | |
| Liu et al. | NavyDroid: Detecting energy inefficiency problems for smartphone applications | |
| CN111131440B (en) | Resource scheduling method and device and server | |
| CN113157411A (en) | Reliable configurable task system and device based on Celery | |
| CN103699485A (en) | Application program debugging method and device | |
| CN103019927B (en) | A kind of performance test methods and system | |
| CN114003293B (en) | Interface management method, device, electronic equipment and readable storage medium | |
| JP5525658B2 (en) | Computer, resource usage calculation method, and resource usage calculation program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |