CN114003272B - Buried point parameter and trigger condition collocation method - Google Patents
Buried point parameter and trigger condition collocation method Download PDFInfo
- Publication number
- CN114003272B CN114003272B CN202111281816.2A CN202111281816A CN114003272B CN 114003272 B CN114003272 B CN 114003272B CN 202111281816 A CN202111281816 A CN 202111281816A CN 114003272 B CN114003272 B CN 114003272B
- Authority
- CN
- China
- Prior art keywords
- buried point
- variable
- value
- point
- dsl
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 33
- 230000006870 function Effects 0.000 claims description 45
- 230000001960 triggered effect Effects 0.000 claims description 6
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 230000010485 coping Effects 0.000 abstract description 3
- 238000011161 development Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000011800 void material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a buried point parameter and trigger condition collocation method, which is characterized by comprising the following steps of 1, pulling and updating DSL codes; step 2, DSL code execution; step 3, creating a variable management unit; step 4, creating a target hook function, and step 5, configuring preset buried point conditions, and analyzing specific contents of the buried point condition constraint according to the buried point conditions; step 6, embedding point data are assembled, and embedding point data are assembled and reported according to the structure of the tips; if the reporting condition is not met, the flow is ended. By integrating DSL at the APP end to execute SDK and transmitting DSL codes by a remote server, the embedded point is dynamic, and the operation deployment capability can be transmitted to the APP as patches at any time and can be dynamically executed. The capability of coping with complex services and demands is stronger and is closer to the actual application scene.
Description
Technical Field
The invention relates to the field of APP data acquisition, in particular to a buried point parameter and trigger condition configuration method in an APP complex service scene.
Background
When the number of users and daily activities of the APP reach a certain scale, the user behavior data collection of the APP will become very important. Some existing buried point acquisition analysis products such as Growing IO, god strategy and the like in the market at present, the acquisition layer at the APP end is usually used for intercepting the behavior operation of a user or the life cycle of some controls, so that the effect of 'full buried point' is achieved. However, the condition that the buried point needs to be triggered is endless in the case of complex service scenes or the condition that complex service data needs to be reported is weak, for example, when the condition A is met, one buried point is triggered, and when the condition B is met, the other buried point is triggered. Or when the A page comes from the B page, the data carried by the buried point of a triggering event needs an assembly mode; when the A page comes from the C page, another assembly method is needed for the data carried by the buried point. The development technology of the APP terminal is complex and various, development languages are different, and the problem of universality exists; the operation deployment capability needs to be achieved, can be issued to the APP as a patch at any time, and can be dynamically executed. A more sophisticated solution is needed.
Therefore, a method for configuring the embedded point parameters and the triggering conditions in the complex APP service scene is needed.
Disclosure of Invention
The invention aims to overcome the defect of the existing business scheme on the support of complex business scenes and provides a buried point parameter and trigger condition collocation method under the APP complex business scene based on DSL. DSL is commonly known as Domain Specified Language, domain specific language.
In order to solve the technical problems, the invention provides a buried point parameter and trigger condition collocation method, and a variable template is provided in a designed DSL grammar for supporting access to all variables in an APP; the conditional logic judgment grammar capable of combining the variable templates is designed, the effect of comprehensively replacing the original APP buried point template codes is achieved, and the method is characterized by comprising the following steps:
step 1, DSL code pulling and updating; the method comprises the following steps: reading a local embedded point configuration version number when the APP is started, and initiating a request to an embedded point configuration management service to obtain the latest configuration and configuration version number; the configuration comprises DSL codes, wherein the DSL codes comprise contracted 6 grammar keywords: module, function, buried point type, buried point name, buried point condition, buried point data; when the function in the module is called, if the function meets the embedded point condition, reporting the corresponding embedded point type, embedded point name and embedded point data of one embedded point, and transmitting the DSL code into an executor by an APP and updating the local embedded point configuration version number;
step 2, DSL code execution; the method comprises the following steps: based on the Json character string, analyzing corresponding modules, functions, buried point types, buried point names, buried point conditions and buried point data in DSL codes according to the 6 grammar keywords agreed by DSL;
step 3, creating a variable management unit; the method comprises the following steps: the variable management unit is a key-value memory and is used for associating a variable template in the DSL code with a variable in the APP; designating a key in a variable template in the DSL code so as to enable a variable in the APP to be assigned to the key, and obtaining a value through the key when the buried point is triggered; the variable templates are defined as: { "IAMValeCapture": "valueCaptureKey" }, wherein valueCaptureKey is the unique identifier of the variable in the APP;
step 4, creating a hook function of the target, specifically: analyzing the type and function of the target according to the buried point type and function field in DSL, and creating a hook function of the function; entering the hook function when the objective function is called, and assembling and reporting the corresponding embedded point type, embedded point name and embedded point data of the embedded point;
step 5, configuring preset buried point conditions, and analyzing specific contents of the buried point condition constraint according to the buried point conditions;
step 6, embedding point data assembly, specifically: according to buried point data in DSL, removing variable management unit value according to variable template, and finally assembling buried point data according to the structure of propes and reporting; if the reporting condition is not met, the flow is ended.
In the step 1, the buried point configuration management service includes a remote server, and the description rule of the buried point is configured by 6 grammar keywords in the DSL code, specifically:
[{"ModuleName":"",
"FuncName":"",
"EventType":"",
"EventName":"",
"Conditions":[{"l":"","opt":"","r":""}],
"Props":{}}]
wherein, modulenname refers to a module; funcName refers to a function; eventType refers to the type of buried point event; eventName refers to the buried point name; conditions refer to buried point Conditions; tips refers to buried data that contains business parameters.
In the step 3, in the variable management unit, the variable in the APP is assigned to the valueCaptureKey through a variable capturing syntax sugar, where the variable capturing syntax sugar includes: packaging an addValueForKey function of a variable management unit by using a macro definition or a global function; the addValueForKey function is used for associating variables in the APP with valueCaptureKey, carrying out deep copying on the input variables, and storing the deep copied variables into the variable management unit; if the value CaptureKey is the same, the old value is covered, and if the value is the object with the closure property, the object with the closure property is deeply copied and then stored in the variable management unit.
In the step 3, the variable management unit further includes a valueForKey, where the valueForKey is used to obtain a specific variable through a valueCaptureKey. The value is obtained from the variable management unit by the incoming value capturekey. If value is an object of the closure property, then the object of the closure property is executed and the value of return is returned to the variable management unit.
In the step 5, the buried point condition is an array, and includes a plurality of condition units; each condition unit contains a left value, a condition symbol, a right value, and for each object, each condition unit sets the left value to 1 and the right value to r, the l and r support constant and variable templates, and the condition symbol to opt, including: equal, regular matching, greater than, less than, greater than or equal to, less than or equal to.
In the step 5, the value of opt is specifically:
1, equality;
2, regular matching;
4, larger than;
8 is smaller than;
5, more than or equal to;
9, less than or equal to.
The invention has the beneficial effects that:
by means of DSL-based mode, buried point semantezation is achieved. And the conditional description grammar and the variable template grammar are created for describing the triggering condition of the buried point and reporting data. By accessing the variables in the program through DSL, any variable can be accessed, and the method is not limited by the context of the program and the scope of the variable, and is not limited by the scope of the development language; based on the conditional description grammar, variables in the APP program can be directly used for participating in conditional judgment, and the conditional description grammar is more close to the scene where the buried point actually occurs. After the DSL language is used, the 'template' codes related to the buried points are not required to be inserted into all ends of the APP, so that the buried point maintenance cost and the code invasiveness are reduced.
The invention realizes the dynamic embedding point by integrating DSL to execute SDK at APP end and transmitting DSL code by remote server, and needs no re-release APP when embedding point is needed to be adjusted, and the operation deployment capability can be transmitted to APP as patch at any time and can be dynamically executed.
Compared with the common buried point acquisition scheme in the prior art, the method has stronger capability of coping with complex services and requirements and is closer to actual application scenes.
Drawings
FIG. 1 is a method flow diagram of an exemplary embodiment of the present invention;
FIG. 2 is a workflow diagram of a variable template in an exemplary embodiment of the invention.
Detailed Description
The invention is further described below with reference to the drawings and exemplary embodiments:
as shown in fig. 1, in the embodiment, finally, a json-format character string is adopted as a description language, and a fixed key or a template is matched to describe a specific trigger time and a specific service scene, which is specifically as follows:
step 1-1, DSL code pulling and updating; the method comprises the following steps: reading a local embedded point configuration version number when the APP is started, and initiating a request to a remote server in embedded point configuration management service to obtain the latest configuration and configuration version number; the configuration comprises DSL codes, wherein the DSL codes comprise contracted 6 grammar keywords: module, function, buried point type, buried point name, buried point condition, buried point data; and when the function in the module is called, reporting the corresponding embedded point type, the embedded point name and the embedded point data of one embedded point if the embedded point condition is met, and transmitting the DSL code into an executor by the APP and updating the local embedded point configuration version number.
In the step 1-1, the grammar key words in the DSL code are configured in description rules of buried points, where the description rules specifically are:
[{"ModuleName":"",
"FuncName":"",
"EventType":"",
"EventName":"",
"Conditions":[{"l":"","opt":"","r":""}],
"Props":{}}]
wherein ModuleName refers to a module or class name; funcName refers to the notation of the method/function; eventType refers to the type of buried point event; eventName refers to a unique name customized in a buried point event; can be defined by the business party by himself; conditions are Conditions for triggering buried points, and the Conditions are an array and comprise a plurality of condition units; each condition unit contains a left value, a condition symbol, a right value, and for each object, each condition unit sets a left value of l and a right value of r, where l and r support constant and variable templates, and sets the condition symbol as opt, which may include: equal, regular matching, greater than, less than, greater than or equal to, less than or equal to; tips is buried data that contains business parameters.
Step 1-2, DSL code execution; the method comprises the following steps: analyzing the DSL code according to the standard json format character string to obtain 6 corresponding grammar keywords in the DSL code: module, function, buried point type, buried point name, buried point condition, buried point data.
Step 1-3, creating a variable management unit; the method comprises the following steps: the variable management unit is a key-value memory and is used for associating a variable template in the DSL code with a variable in the APP; designating a key in a variable template in the DSL code so as to enable a real variable in the APP to be assigned to the key, and obtaining a value through the key when the buried point is triggered; the variable templates are defined as: { "IAMValeCapture": "valueCaptureKey" }, wherein valueCaptureKey is the unique identification of the variable in the APP.
The DSL of the invention designs a grammar template for matching variables in the APP program. The core idea is to use a "key" to obtain a "value". The DSL code declares this key and the APP creates a "key-value" management module that uses the variable capture syntax sugar to assign the correct variable value to the "key" at the appropriate time.
The variable in the APP is assigned to the valueCaptureKey through a variable capture syntax sugar, and the variable capture syntax sugar comprises: packaging an addValueForKey function of a variable management unit by using macro definition (iOS) or global function (android, RN);
the realization principle of the variable management unit is as follows:
the addValueForKey function is used for associating variables in the APP with valueCaptureKey, carrying out deep copying on the input variable assignment, and storing the deep copied variable assignment into a variable management unit key-value memory; so as to avoid memory leakage. If the value CaptureKey is the same, the old value is covered, and if the value is an object with closure property, such as block of iOS, lambda of android and arrow function of js, the object with closure property is deeply copied and then stored in a variable management unit key-value memory.
The variable management unit further comprises a value force Key, wherein the value force Key is used for acquiring specific variable assignment through the value captureKey. The value is obtained from the variable management unit by the incoming value capturekey. If value is an object of the closure property, then the object of the closure property is executed and the value of return is returned to the variable management unit.
Step 1-4, creating a hook function of a target, specifically: analyzing the type and function of the target according to the buried point type and function field in DSL, and creating a hook function of the function; entering the hook function when the objective function is called, and assembling and reporting the corresponding embedded point type, embedded point name and embedded point data of the embedded point;
step 1-5, configuring preset buried point conditions, and analyzing specific contents of the buried point condition constraint according to the buried point conditions; memory access convenience of DSL and APP is realized to the greatest extent;
in an exemplary embodiment of the present invention, the value of the condition opt is specifically: 1, equality; 2, regular matching; 4, larger than; 8 is smaller than; 5, more than or equal to; 9, less than or equal to. Namely, 1< <0, 1< <1, 1< <2, 1< <3, 5 are 1 and 4 bitwise AND, which is equivalent to (1 < < 0) & (1 < < 2); 9 is a 1 and 8 bit wise AND.
Then in code
{"ModuleName":"TestClass",
"FuncName":"testFun",
"EventType":"test_event_type",
"EventName":"test_event_name",
"Conditions":[{"l":{"IAMValueCapture":"a"},"opt":4,"r":2}],
"Props":{"userId":{"IAMValueCapture":"b"}}}
For example, the action is described as: when the testFun method in the TestClass is called, if the value of the local variable a is greater than 2, reporting a buried point, wherein the type of the buried point is test_event_type, and the unique identification name of the buried point is test_event_name; the carried data is userId, and the value is the value of the local variable b.
Corresponding to the following pseudo code:
class TestClass{
void testFun(){
int a＝3,b＝2；
If(a>2){
sendDataAnalytics("test_event_type",
"test_event_name",
{"userId",b})；
}
}
}
TestClass.testFun()；
step 1-6, embedding point data assembly, specifically: according to buried point data in DSL, removing variable management unit value according to variable template, and finally assembling buried point data according to the structure of propes and reporting; if the reporting condition is not met, the flow is ended.
As shown in fig. 2, the specific workflow of the variable management unit includes: wrapping a specific business variable by using a variable capturing grammar sugar in a specific business code, and delivering the specific business variable to a variable management unit for key-value storage; after the DSL grammar interpreter recognizes a variable template in DSL, a specific variable value is obtained from a variable management unit according to the value CaptureKey in the variable template in DSL, so that the variable template access program variable is realized.
The patent mainly needs to embody the condition logic judgment that the custom language can replace the source code, such as if (a= =1 & & b > 2), and has a variable template to support the custom language of the set to acquire any variable of APP, so that the custom language can replace scattered buried point 'template' codes everywhere.
The invention is mainly used for providing a buried point parameter and trigger condition collocation method under an APP complex service scene, and the buried point semanteme is realized by a DSL-based mode. And the conditional description grammar and the variable template grammar are created for describing the triggering condition of the buried point and reporting data. By accessing the variables in the program through DSL, any variable can be accessed, and the method is not limited by the context of the program and the scope of the variable, and is not limited by the scope of the development language; based on the conditional description grammar, variables in the APP program can be directly used for participating in conditional judgment, and the conditional description grammar is more close to the scene where the buried point actually occurs. After the DSL language is used, the 'template' codes related to the buried points are not required to be inserted into all ends of the APP, so that the buried point maintenance cost and the code invasiveness are reduced.
The invention realizes the dynamic embedding point by integrating DSL to execute SDK at APP end and transmitting DSL code by remote server, and needs no re-release APP when embedding point is needed to be adjusted, and the operation deployment capability can be transmitted to APP as patch at any time and can be dynamically executed.
Compared with the common buried point acquisition scheme in the prior art, the method has stronger capability of coping with complex services and requirements and is closer to actual application scenes.
The above embodiments are not intended to limit the present invention in any way, and all other modifications and applications of the above embodiments which are equivalent to the above embodiments fall within the scope of the present invention.
Claims (6)
1. The method for configuring the buried point parameters and the triggering conditions is characterized by comprising the following steps:
step 1, DSL code pulling and updating; the method comprises the following steps: reading a local embedded point configuration version number when the APP is started, and initiating a request to an embedded point configuration management service to obtain the latest configuration and configuration version number; the configuration comprises DSL codes, wherein the DSL codes comprise contracted 6 grammar keywords: module, function, buried point type, buried point name, buried point condition, buried point data; when the function in the module is called, if the function meets the embedded point condition, reporting the corresponding embedded point type, embedded point name and embedded point data of one embedded point, and transmitting the DSL code into an executor by an APP and updating the local embedded point configuration version number;
step 2, DSL code execution; the method comprises the following steps: based on the Json character string, analyzing corresponding modules, functions, buried point types, buried point names, buried point conditions and buried point data in DSL codes according to the 6 grammar keywords agreed by DSL;
step 3, creating a variable management unit; the method comprises the following steps: the variable management unit is a key-value memory and is used for associating a variable template in the DSL code with a variable in the APP; designating a key in a variable template in the DSL code so as to enable a variable in the APP to be assigned to the key, and obtaining a value through the key when the buried point is triggered; the variable templates are defined as: { "IAMValeCapture": "valueCaptureKey" }, wherein valueCaptureKey is the unique identifier of the variable in the APP;
step 4, creating a hook function of the target, specifically: analyzing the type and function of the target according to the buried point type and function field in DSL, and creating a hook function of the function; entering the hook function when the objective function is called, and assembling and reporting the corresponding embedded point type, embedded point name and embedded point data of the embedded point;
step 5, configuring preset buried point conditions, and analyzing specific contents of the buried point condition constraint according to the buried point conditions;
step 6, embedding point data assembly, specifically: according to buried point data in DSL, removing variable management unit value according to variable template, and finally assembling buried point data according to the structure of propes and reporting; if the reporting condition is not met, the flow is ended.
2. The method for configuring buried point parameters and triggering conditions according to claim 1, wherein: in the step 1, the buried point configuration management service includes a remote server, and the description rule of the buried point is configured by 6 grammar keywords in the DSL code, specifically:
[{"ModuleName":"",
"FuncName":"",
"EventType":"",
"EventName":"",
"Conditions":[{"l":"","opt":"","r":""}],
"Props":{}}]
wherein, modulenname refers to a module; funcName refers to a function; eventType refers to the type of buried point event; eventName refers to the buried point name; conditions refer to buried point Conditions; tips refers to buried data that contains business parameters.
3. The method for configuring the buried point parameters and the triggering conditions according to claim 2, wherein: in the step 3, in the variable management unit, the variable in the APP is assigned to the valueCaptureKey through a variable capturing syntax sugar, where the variable capturing syntax sugar includes: packaging an addValueForKey function of a variable management unit by using a macro definition or a global function; the addValueForKey function is used for associating variables in the APP with valueCaptureKey, carrying out deep copying on the input variables, and storing the deep copied variables into the variable management unit; if the value CaptureKey is the same, the old value is covered, and if the value is the object with the closure property, the object with the closure property is deeply copied and then stored in the variable management unit.
4. A method of configuring a buried point parameter and a trigger condition as defined in claim 3, wherein: in the step 3, the variable management unit further includes a value force key, where the value force key is used to obtain a specific variable through a value capturekey, and obtain a value from the variable management unit through an incoming value capturekey; if value is an object of the closure property, then the object of the closure property is executed and the value of return is returned to the variable management unit.
5. The method for configuring buried point parameters and triggering conditions according to claim 4, wherein: in the step 5, the buried point condition is an array, and includes a plurality of condition units; each condition unit comprises a left value, a condition symbol and a right value, for each object, each condition unit is provided with a left value of l, a right value of r, the l and r support constant and variable templates, the condition symbol is provided with opt, and the method comprises the following steps: equal, regular matching, greater than, less than, greater than or equal to, less than or equal to.
6. The method for configuring buried point parameters and triggering conditions as recited in claim 5, wherein in said step 5, the value of opt is specifically:
1, equality;
2, regular matching;
4, larger than;
8 is smaller than;
5, more than or equal to;
9, less than or equal to.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111281816.2A CN114003272B (en) | 2021-11-01 | 2021-11-01 | Buried point parameter and trigger condition collocation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111281816.2A CN114003272B (en) | 2021-11-01 | 2021-11-01 | Buried point parameter and trigger condition collocation method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114003272A CN114003272A (en) | 2022-02-01 |
| CN114003272B true CN114003272B (en) | 2024-04-16 |
Family
ID=79925973
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111281816.2A Active CN114003272B (en) | 2021-11-01 | 2021-11-01 | Buried point parameter and trigger condition collocation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114003272B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109241080A (en) * | 2018-09-29 | 2019-01-18 | 焦点科技股份有限公司 | A kind of the building application method and its system of FQL query language |
| WO2019100614A1 (en) * | 2017-11-22 | 2019-05-31 | 平安科技（深圳）有限公司 | Buried point data processing method, device, computer device and storage medium |
| CN110489597A (en) * | 2018-05-10 | 2019-11-22 | 华为技术有限公司 | A kind of method and terminal device obtaining data |
| WO2020082558A1 (en) * | 2018-10-26 | 2020-04-30 | 深圳壹账通智能科技有限公司 | Function name-based breakpoint setting method, device, computer apparatus, and storage medium |
| CN112230903A (en) * | 2020-10-12 | 2021-01-15 | 上海赛可出行科技服务有限公司 | Lightweight decoupling type point burying method and device based on iOS application |
| CN112256701A (en) * | 2020-10-22 | 2021-01-22 | 广东万唯计算机服务有限公司 | Dynamic buried point data acquisition system and use method thereof |
| CN112506492A (en) * | 2020-09-02 | 2021-03-16 | 上海赛可出行科技服务有限公司 | Visual point burying method supporting dynamic scene configuration |
| CN112905944A (en) * | 2021-04-06 | 2021-06-04 | 成都新希望金融信息有限公司 | Page online dynamic generation method and device, electronic equipment and readable storage medium |
-
2021
- 2021-11-01 CN CN202111281816.2A patent/CN114003272B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019100614A1 (en) * | 2017-11-22 | 2019-05-31 | 平安科技（深圳）有限公司 | Buried point data processing method, device, computer device and storage medium |
| CN110489597A (en) * | 2018-05-10 | 2019-11-22 | 华为技术有限公司 | A kind of method and terminal device obtaining data |
| CN109241080A (en) * | 2018-09-29 | 2019-01-18 | 焦点科技股份有限公司 | A kind of the building application method and its system of FQL query language |
| WO2020082558A1 (en) * | 2018-10-26 | 2020-04-30 | 深圳壹账通智能科技有限公司 | Function name-based breakpoint setting method, device, computer apparatus, and storage medium |
| CN112506492A (en) * | 2020-09-02 | 2021-03-16 | 上海赛可出行科技服务有限公司 | Visual point burying method supporting dynamic scene configuration |
| CN112230903A (en) * | 2020-10-12 | 2021-01-15 | 上海赛可出行科技服务有限公司 | Lightweight decoupling type point burying method and device based on iOS application |
| CN112256701A (en) * | 2020-10-22 | 2021-01-22 | 广东万唯计算机服务有限公司 | Dynamic buried point data acquisition system and use method thereof |
| CN112905944A (en) * | 2021-04-06 | 2021-06-04 | 成都新希望金融信息有限公司 | Page online dynamic generation method and device, electronic equipment and readable storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 埋点管理系统分析与设计;廖爱红;罗铭涛;;办公自动化;20200815(第16期);35-37 * |
| 大数据分析在商业银行零售业务创新中的实践;曹嘉欣;童蕙;;信息技术与标准化;20200510(第05期);29-33 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114003272A (en) | 2022-02-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107870933B (en) | Method, device and system for counting android application page browsing behaviors | |
| CN109446069A (en) | Compatibility test method, device, computer equipment and medium | |
| CN111984228B (en) | Interface document processing method and device, computer equipment and storage medium | |
| CN110309029A (en) | Acquisition method, device, computer equipment and the storage medium of abnormal data | |
| Domingos et al. | Using BPMN to model Internet of Things behavior within business process | |
| CN109558304B (en) | Component association analysis method and device and electronic equipment | |
| CN102164045A (en) | Parameterized computer monitoring system | |
| CN112084040B (en) | Container resource planning system and method based on application mirror image data identification | |
| CN104536819A (en) | Task scheduling method based on WEB service | |
| CN104461531A (en) | Implementing method for self-defined functions of reporting system | |
| WO2011032072A1 (en) | System and method of substituting parameter sets in self-contained mini-applications | |
| CN110069259A (en) | Analytic method, device, electronic equipment and storage medium based on idl file | |
| CN114978940A (en) | Link monitoring and alarming method, device, computer equipment and storage medium | |
| CN111240772B (en) | Block chain-based data processing method, device and storage medium | |
| CN112667287A (en) | Method, device and equipment for creating rule file and computer readable storage medium | |
| CN104598619A (en) | Service compositional verification method based on constraint solver | |
| CN113709187B (en) | Multi-server data request method, device, equipment and storage medium | |
| CN103186463A (en) | Method and system for determining testing range of software | |
| CN116661756A (en) | Object analysis method and device based on low-code DSL | |
| CN114003272B (en) | Buried point parameter and trigger condition collocation method | |
| CN112783791B (en) | Interface test case generation method and device | |
| CN112115041A (en) | Dynamic point burying method and device for application program, storage medium and computer equipment | |
| CN103677842A (en) | Software tool configuration type integrated expansion calling method and system | |
| CN111813816A (en) | Data processing method, data processing device, computer readable storage medium and computer equipment | |
| CN109522293B (en) | Low-power-consumption Bluetooth 4.2 protocol stack attribute protocol database pre-generation system and method |
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 |