CN111309551A - Method and device for determining correct integration of event monitoring SDK - Google Patents
Method and device for determining correct integration of event monitoring SDK Download PDFInfo
- Publication number
- CN111309551A CN111309551A CN202010085218.7A CN202010085218A CN111309551A CN 111309551 A CN111309551 A CN 111309551A CN 202010085218 A CN202010085218 A CN 202010085218A CN 111309551 A CN111309551 A CN 111309551A
- Authority
- CN
- China
- Prior art keywords
- application
- sdk
- event
- identifier
- event monitoring
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
Abstract
The invention provides a method and a device for determining the correct integration of an event monitoring SDK, which relate to the technical field of computers, and the method comprises the following steps: receiving an SDK initialization detection request, wherein the SDK initialization detection request carries an application identifier of a target application of an integrated event monitoring SDK; receiving verification information and event information of a target application corresponding to an application identifier, which are uploaded by a terminal device, wherein the verification information and the event information are acquired through an event monitoring SDK integrated in the target application, the event information comprises information of operation performed on the target application, and the terminal device is a device with the target application installed; and if the fact that the initialization of the event monitoring SDK in the target application is completed is determined according to the verification information, and the uploaded event information is determined to include the information of the target event, the fact that the event monitoring SDK is correctly integrated in the target application is determined. The method can determine whether the event monitoring SDK is integrated correctly in the target application.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for determining correct integration of an event monitoring SDK.
Background
In the related art, in order to monitor an operation event performed by a user for a specific application, a specific Software Development Kit (SDK) is often integrated in the specific application, and the operation event performed by the user for the specific application is monitored through the SDK.
Disclosure of Invention
The embodiment of the disclosure provides a method and a device for determining correct integration of an event monitoring SDK, which are used for at least providing a method for determining correct integration of the event monitoring SDK in a target application.
In a first aspect of the present disclosure, a method for determining that an event monitoring SDK is correctly integrated is provided, including:
receiving a triggered SDK initialization detection request, wherein the SDK initialization detection request carries an application identifier of a target application of an integrated event monitoring SDK;
determining verification information and event information of a target application corresponding to the application identifier and uploaded by a terminal device, wherein the verification information and the event information are acquired through an event monitoring SDK integrated in the target application, the event information comprises information of operation performed on the target application, and the terminal device is a device installed with the target application;
and if the fact that the initialization of the event monitoring SDK in the target application is completed is determined according to the verification information, and the fact that the event information uploaded by the terminal equipment comprises the information of the target event is determined, the fact that the event monitoring SDK is correctly integrated in the target application is determined.
In a possible implementation manner, the step of determining that initialization of the event monitoring SDK in the target application is completed according to the verification information includes:
and if the corresponding relation between the application identifier and the application package name included in the verification information exists in the corresponding relation between the set application identifier and the application package name, determining that the initialization of the event monitoring SDK in the target application is completed.
In a possible implementation manner, the corresponding relationship between the application identifier and the application package name is obtained from the joint tone record corresponding to the terminal device, and before the step of determining that the initialization of the event monitoring SDK in the target application is completed, if the corresponding relationship between the application identifier and the application package name included in the verification information exists in the set corresponding relationship between the application identifier and the application package name, the method further includes:
determining the equipment identifier of the terminal equipment indicated by the newly-built SDK application conversion interface;
and determining the joint tone record corresponding to the equipment identifier as the joint tone record corresponding to the terminal equipment.
In a possible implementation manner, the correspondence between the application identifier and the application package name is set when the application identifier is allocated to the at least one target application through the identifier application interface.
In a possible implementation manner, before the step of receiving the triggered SDK initialization detection request, the method further includes:
and determining the target event indicated by the object by newly building an SDK application conversion interface.
In a second aspect of the present disclosure, an apparatus for determining that an event monitoring SDK is correctly integrated includes a detection request receiving unit, an authentication information receiving unit, and an SDK integration authentication unit, where:
the detection request receiving unit is configured to execute receiving of a triggered SDK initialization detection request, wherein the SDK initialization detection request carries an application identifier of a target application of an integrated event monitoring SDK;
the verification information receiving unit is configured to execute verification information and event information of a target application corresponding to the application identifier and uploaded by a terminal device, wherein the verification information and the event information are acquired through an event monitoring SDK integrated in the target application, the event information comprises information of operation performed on the target application, and the terminal device is a device installed with the target application;
the SDK integration verification unit is configured to determine that the event monitoring SDK is integrated correctly in the target application if the fact that initialization of the event monitoring SDK in the target application is completed is determined according to the verification information and the fact that the event information uploaded by the terminal device includes the information of the target event is determined.
In one possible implementation, the SDK integrated verification unit is specifically configured to perform:
and if the corresponding relation between the set application identifier and the application package name exists in the corresponding relation between the application identifier and the application package name included in the verification information, determining that the initialization of the event monitoring SDK in the target application is completed.
In a possible implementation manner, the correspondence between the application identifier and the application package name is obtained from a joint tone record corresponding to the terminal device, and the SDK integrated verification unit is further configured to perform:
if the corresponding relation between the application identifier and the application package name included in the verification information exists in the corresponding relation between the set application identifier and the application package name, determining the equipment identifier of the terminal equipment indicated by a newly-built SDK application conversion interface before the initialization of the event monitoring SDK in the target application is completed;
and determining the joint tone record corresponding to the equipment identifier as the joint tone record corresponding to the terminal equipment.
In a possible implementation manner, the correspondence between the application identifier and the application package name is set when the application identifier is allocated to the at least one target application through the identifier application interface.
In one possible implementation manner, the detection request receiving unit is further configured to perform:
and before receiving a triggered SDK initialization detection request, determining the target event indicated by the object by newly building an SDK application conversion interface.
In a third aspect of the present disclosure, a computer device is provided, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the program, the method of any one of the first aspect and one possible implementation manner is implemented.
In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, which stores computer instructions that, when executed on a computer, cause the computer to perform the method according to any one of the first aspect and one of the possible embodiments.
The scheme of the present disclosure brings at least the following beneficial effects:
after receiving a triggered SDK initialization detection request, according to verification information and event information uploaded by terminal equipment, determining that the initialization of an event monitoring SDK in a target application is completed, and determining that the event information uploaded by the terminal equipment is correct, determining the event monitoring SDK in the target application, and providing a method for jointly judging the event monitoring SDK by a combined user, the terminal equipment and a server.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
Fig. 1 is a schematic diagram of an application scenario provided in an exemplary embodiment of the present disclosure;
fig. 2 is a flowchart illustrating a method for determining that an event monitoring SDK is correctly integrated according to an exemplary embodiment of the disclosure;
FIG. 3 is a schematic diagram of an SDK application interface provided by an exemplary embodiment of the present disclosure;
FIG. 4 is a schematic diagram of an application identifier management interface according to an exemplary embodiment of the present disclosure;
FIG. 5 is a schematic diagram of an application identification application interface provided by an exemplary embodiment of the present disclosure;
fig. 6 is a schematic diagram of a right added when an event monitoring SDK is integrated according to an exemplary embodiment of the present disclosure;
FIG. 7 is a schematic code diagram for initializing an event monitoring SDK according to an exemplary embodiment of the present disclosure;
FIG. 8 is a schematic diagram of an application transformation interface provided by an exemplary embodiment of the present disclosure;
FIG. 9 is a schematic illustration of an interface provided by an exemplary embodiment of the present disclosure;
fig. 10 is a schematic diagram of a terminal device indication interface provided in an exemplary embodiment of the present disclosure;
FIG. 11 is a schematic diagram of a joint debugging interface provided by an exemplary embodiment of the present disclosure;
fig. 12 is a schematic structural diagram of an apparatus for determining that an event monitoring SDK is correctly integrated according to an exemplary embodiment of the present disclosure;
fig. 13 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present disclosure.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
In order to facilitate better understanding of the technical solutions of the present disclosure by those skilled in the art, the following technical terms related to the present disclosure are explained.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein.
Software development kit SDK: the english is called Software Development Kit, and is generally a set of Development tools for technicians to build application Software for a specific Software package, Software framework, hardware platform, operating system, etc., which may include, but is not limited to, a set of relevant documents, paradigms and tools for developing a certain type of Software, and may also include programs for implementing a certain function, etc.
The following explains the design concept of the present disclosure.
In the related art, in order to monitor an operation event performed by a user for a specific application, a specific SDK is often integrated in the specific application, for example, by integrating an event monitoring SDK in the specific application, an operation event performed by the user for the specific application is monitored, such as downloading, installing, and the like. However, in the process of integrating the event monitoring SDK into the designated application, the developer cannot determine whether the SDK is integrated correctly in the designated application, and thus cannot determine whether the information of the operation event of the user on the designated application is acquired correctly through the SDK.
For example, when advertising various applications through the advertisement platform, especially when advertising some applications that the user wants to download for use, the user may perform some shallow-to-deep operation events, such as downloading, installing, activating, registering and other behaviors, on the advertised applications through the advertisement platform; advertisers (i.e., developers or owners of applications) may wish to obtain users who perform different degrees of operations on applications at different stages of advertising, such as users who download and install applications at the beginning of advertising; the advertiser integrates the event monitoring SDK into the application of the advertiser, and puts the application integrated with the event monitoring SDK into the advertisement platform, so that the information of the operation event of the user aiming at the application of the advertiser can be obtained through the event monitoring SDK, and further advertisement putting and other processing can be carried out according to the obtained information.
There are several problems when an advertiser integrates an event monitoring SDK into its own application:
1) when the event monitoring SDK is integrated into the application, the event monitoring SDK needs to be downloaded from an advertisement platform/advertiser that provides the event monitoring SDK, and further, complex configuration such as adding permissions is required, and after a file is added to a created software project or some file paths are added, the event monitoring SDK can be integrated into the application, which not only is a process complicated, but also needs technical support, but usually an advertiser does not know the technology for integrating the SDK into the application, and further, the advertiser often needs to send a technician to integrate the event monitoring SDK into the application of the advertiser, and thus, the process is complicated, and more manpower and material resources need to be consumed.
2) After an advertiser or a technician integrates the event monitoring SDK in the application, the advertiser or the technician cannot judge whether the integration of the event monitoring SDK in the application is correct, so that whether the information acquired by the SDK is correct cannot be determined.
In view of this, the present disclosure designs a method and an apparatus for determining correct integration of an event monitoring SDK, which are used to at least provide a method for determining correct integration of an event monitoring SDK in a target application. The method comprises the following steps:
receiving an SDK initialization detection request carrying an application identifier of a target application of an integrated event monitoring SDK, further determining verification information and event information of the target application corresponding to the application identifier and uploaded by a terminal device, and determining that the event monitoring SDK is correctly integrated in the target application if the fact that the initialization of the event monitoring SDK in the target application is completed is determined according to the verification information and the fact that the event information uploaded by the terminal device comprises the information of the target event is determined.
The verification information and the event information are acquired through an event monitoring SDK integrated in a target application, the event information includes information of an operation performed on the target application, and the terminal device is a device in which the target application is installed.
The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings:
in order to more clearly understand the design idea of the present disclosure, an application scenario is provided below, please refer to fig. 1, where the application scenario includes at least one terminal device 100 and a server 110, each terminal device 100 may have a target application with an integrated event monitoring SDK installed therein, and the terminal device 100 and the server 110 may communicate with each other.
The terminal device 100 may be a mobile terminal, a fixed terminal, or a portable terminal such as, for example, a mobile handset, a station, a unit, a device, a multimedia computer, a multimedia tablet, an internet node, a communicator, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a Personal Communication System (PCS) device, a personal navigation device, a Personal Digital Assistant (PDA), an audio/video player, a digital camera/camcorder, a positioning device, a television receiver, a radio broadcast receiver, an electronic book device, a gaming device, or any combination thereof, including accessories and peripherals of these devices, or any combination thereof, and is not limited thereto. The terminal device and the server may be directly or indirectly connected through wired or wireless communication, and the disclosure is not limited thereto.
The server 110 may be, but is not limited to, a general server, a cloud server, a blockchain server, and the like.
The server 110 may receive the SDK initialization detection request, the verification information of the target application uploaded by the terminal device, and the event information, and the server 110 is configured to determine whether the initialization of the event monitoring SDK in the target application is completed according to the verification information and determine whether the time information uploaded by the terminal device is the information of the target event.
The embodiment of the present disclosure further provides an event monitoring management platform for determining whether the integration of the event monitoring SDK is correct, where the event monitoring management platform may receive the SDK initialization detection request, the verification information and the event information of the target application uploaded by the terminal device, and may determine whether the initialization of the event monitoring SDK in the target application is completed and determine whether the time information uploaded by the terminal device is the information of the target event according to the verification information.
The client of the event monitoring management platform can run on a terminal such as a computer, an object can trigger an SDK initialization detection request and the like through various interfaces and the like provided by the client, and various functions of the event monitoring management platform can be realized by one or more servers.
Referring to fig. 2, an embodiment of the present disclosure provides a method for determining that an event monitoring SDK is integrated correctly, which may be but is not limited to a server for an application scenario in fig. 1 or a server implementing the function of the event monitoring management platform, and specifically includes the following steps:
step S201, receiving a triggered SDK initialization detection request, where the SDK initialization detection request carries an application identifier of a target application of an integrated event monitoring SDK.
As an embodiment, the SDK initialization detection request may be triggered by an object through a terminal device, or triggered by an associated tone interface provided by an event monitoring management platform, and the following contents of the embodiment of the present disclosure only take the SDK initialization detection request triggered by the associated tone interface as an example.
The target application can be an application in an android system, and can also be an application in other systems.
Step S202, determining verification information and event information of the target application corresponding to the application identifier uploaded by the terminal equipment.
The verification information and the event information are acquired through an event monitoring SDK integrated in a target application, the event information includes information of an operation performed on the target application, and the terminal device is a device in which the target application is installed.
That is, the event monitoring SDK may acquire information of an operation of the object on the target application as the event information.
Step S203, if it is determined that the initialization of the event monitoring SDK in the target application is completed according to the verification information, and it is determined that the event information uploaded by the terminal device includes information of the target event, it is determined that the event monitoring SDK is correctly integrated in the target application.
As an embodiment, the step of determining the initialization completion of the event monitoring SDK in the target application according to the verification information may be, but is not limited to, by the following method:
and if the corresponding relation between the application identifier and the application package name included in the verification information exists in the corresponding relation between the set application identifier and the application package name, determining that the initialization of the event monitoring SDK in the target application is completed.
That is, the server may search, from the stored correspondence between one or more application identifiers and application package names, whether a correspondence between an application identifier uploaded by the terminal device and an application package name exists, that is, if the application identifier uploaded by the terminal device is a and the application package name is B, the server determines that the initialization of the event monitoring SDK is completed if the server determines that the correspondence between a and B exists in the set correspondence between the application identifier and the application package name; if the server determines that the corresponding relation between the A and the B does not exist in the corresponding relation between the set application identifier and the application package name, the fact that the application identifier uploaded by the terminal device does not correspond to the application package name is proved, and at the moment, it is determined that the initialization of the event monitoring SDK is not completed.
As an embodiment, the correspondence between the application identifier and the application package name may be obtained from a joint record corresponding to the terminal device, and before the step of determining that the initialization of the event monitoring SDK in the target application is completed, if the correspondence between the application identifier and the application package name included in the verification information exists in the set correspondence between the application identifier and the application package name, the method further includes:
determining the equipment identifier of the terminal equipment indicated by the newly-built SDK application conversion interface;
and determining the joint tone record corresponding to the equipment identifier as the joint tone record corresponding to the terminal equipment.
It should be noted that the joint tone record is a record that the object determines whether the integration of the event monitoring SDK in the target application is correct through the request of the terminal device and the server, and the record that the object applies for the application identifier for the target application is also a joint tone record, and the form of the joint tone record may be, but is not limited to, a log, and the object in the embodiment of the present disclosure refers to a developer or an owner of the target application.
Here, if the server determines that the terminal device has the joint debugging record and the corresponding relationship between the application identifier of the target application and the application package name is stored in the joint debugging record, it determines that the initialization of the event monitoring SDK in the target application is completed, that is, if the application identifier uploaded by the terminal device is a and the application package name is B, the server determines that the initialization of the event monitoring SDK is completed if it determines that the corresponding relationship between a and B is present in the joint debugging record corresponding to the terminal device; if the server only finds the corresponding relation between the A and the C (C is an application package name different from the B) in the joint debugging record corresponding to the terminal equipment, the fact that the application identifier uploaded by the terminal equipment does not correspond to the application package name is proved, and at the moment, it is determined that the initialization of the event monitoring SDK is not completed.
As an embodiment, the correspondence between the application identifier and the application package name is set when the application identifier is allocated to the at least one target application through the application identifier application interface.
When the object needs to integrate the SDK in the target application, the application package name of the target application may be indicated through an application identifier application interface provided by the monitoring platform, and correspondingly, the server may allocate the corresponding application identifier to the target application according to the received application package name.
Further, after receiving the application package name of the target application through the application identifier application interface, the server may randomly generate an application identifier corresponding to the received application package name as an application identifier allocated to the target application, and store a corresponding relationship between the application package name of the target application and the application identifier.
As an embodiment, the step of receiving the triggered SDK initialization detection request before the step of receiving the triggered SDK initialization detection request when the target event is indicated by the object may be preset or indicated by the object, further includes:
and determining the target event indicated by the object through the newly-built SDK application conversion interface, and further determining whether the event information uploaded by the terminal equipment comprises the information of the target event indicated by the object.
Optionally, a target event detection duration may be set, and if the server does not detect the information of the target event in the event information uploaded by the terminal device within the target event detection duration for receiving the SDK initialization detection request, it is determined that the event information long-transmitted by the terminal device does not include the information of the target event.
The value of the target event detection duration is not limited too much, and can be set by a person skilled in the art according to actual requirements.
Optionally, when determining whether the event information uploaded by the terminal device includes information of a target event indicated by the object, the server may further determine that a corresponding relationship between the application identifier and the application package name included in the verification information is included in the set corresponding relationship between the application identifier and the application package name, determine whether the event information uploaded by the terminal device includes information of the target event if the corresponding relationship between the application identifier and the application package name included in the verification information is included in the set corresponding relationship between the application identifier and the application package name, and if not, send a prompt message to the terminal device to prompt the object to determine that the event information reported by the terminal device is incorrect, where the set corresponding relationship between the application identifier and the application package name may still be stored in an associated record corresponding to the terminal device.
The joint debugging interface, the application identification application interface and the newly-built SDK application conversion interface can be provided for an event monitoring management platform, and the following further explains the scheme of the embodiment of the present disclosure in combination with various interfaces provided by the event monitoring management platform.
As an embodiment, the object may perform interactive operation with the server that realizes various functions of the event monitoring management platform through various interfaces provided by the event monitoring management platform, and integrate the event monitoring SDK into the target application, and the specific process may refer to the following contents:
referring to fig. 3, an SDK application interface 300 is provided, where an object can select to perform new API backhaul or new SDK backhaul for a target application, and the way of the new API backhaul is not described herein; the SDK application interface 300 may include, but is not limited to, a management AppID button 301 and a new SDK return button 302, where the object may apply for an application identifier AppID through the management AppID button 301 and newly create a data return of the event monitoring SDK for the target application through the new SDK return button 302.
Referring to fig. 3 to 5, an object applies for an application identifier app id for a target application through the management app id key 301, the object may enter the application identifier management interface 400 by clicking the management app id key 301, the application identifier management interface 400 may include, but is not limited to, an app id application key 401 and a download SDK key 402, wherein the object may enter the application identifier application interface 500 through the app id application key 401, and apply for and download a corresponding event monitoring SDK through the download SDK key 402.
After entering the application identifier application interface 500 through the application app id key 401, the object may input the application package name of the target application through the application package name input box 501; correspondingly, when the server receives the application package name through the application identifier application interface 500, an application identifier is randomly generated as the application identifier corresponding to the received application package name; the application package name input by the object may include, but is not limited to, one or more of lower case letters, numbers and underlines, and the application package name is not allowed to be modified after the monitoring platform determines the corresponding application identifier for the input application package name.
As an example, the object may also input the Chinese name of the target application through the application Chinese name input box 502 in the application identification application interface 500, which may include but is not limited to Chinese characters, numbers, underlines; if the Chinese name of the target application is the same as the Chinese names of other applications, the object may add a suffix to the Chinese name of the target application when entering the Chinese name of the application, e.g., "application _ 1" when the Chinese name of the target application is "application", the object may enter "application _ 1" in the application Chinese name input box 502.
As an embodiment, the object may also input the english name of the target application through the application english name input box 503 in the application identification application interface 500, where the english name may include, but is not limited to, lower case letters, numbers, and underlines; if the english name of the target application is the same as the english name of another application, the object may be suffixed to the english name of the target application when the object inputs the english name of the application, and if the english name of the target application is "certain application", the object may input "certain application _ 1" in the application english name input box 503.
As an embodiment, after the object inputs the package name of the target application, or inputs the package name and the chinese/english name of the target application, or inputs the package name, the chinese name and the english name of the target application, the object may indicate the input information to the server through the determination key 504, so that the server sets the corresponding application identifier for the input package name.
As an embodiment, the application identifier application interface 500 further includes a page close button 505, and the object may be, but is not limited to, closing the application identifier application interface 500 by clicking the page close button 505.
After the object applies for the application identifier for the target application through the identifier application interface 500, the corresponding event monitoring SDK may be applied and downloaded to the server through the download SDK button 402, and correspondingly, the server may push the event monitoring SDK to the download space indicated by the object, and further, the server may also push the docking operation document of the event monitoring SDK to the download space indicated by the object, where the server may, but is not limited to, push the event monitoring SDK to the download space indicated by the object in an aar manner.
The object may integrate the downloaded event monitoring SDK into the target application as indicated by the docking operation document, wherein the object may integrate the event monitoring SDK into the target application as follows:
the object can access the event monitoring SDK to the target application in an aar packet mode, and can also access the event monitoring SDK to the target application in a jar packet mode after decompressing the aar packet providing the event monitoring SDK.
And then adding dependence for the event monitoring SDK according to any mode as follows:
the first way to add dependencies:
importing Android studio (recommendation mode), finding a libs folder under App engineering, copying an aar package to the directory, adding a local warehouse in a project root build.
The second way to add dependencies:
and (4) importing Eclipse, decompressing aar files, finding classes, copying the classes, and then referring to the libs folder under the project.
After adding a dependency to the event monitoring SDK, a right may be added to the event monitoring SDK, for example, an object may be, but is not limited to, an authority as shown in fig. 6 added to an android manifest.
It should be noted that the minimum system version required by the event monitoring SDK is API 9, and for a target application adapted with android more than 6.0 (API is greater than or equal to 23), the object may apply for a dynamic authority android.
After the event monitoring SDK adds the rights, the object may initialize the event monitoring SDK by, but not limited to:
the code in fig. 7 is debugged to initialize the event monitoring SDK at the App's entry, Application # onCreate or the onCreate () method of Application entry Activity.
After the object initializes the event monitoring SDK, the object may test the target application to determine whether the integration of the event monitoring SDK in the target application is correct, and the specific process is as follows:
referring to fig. 3 and fig. 8, an object may enter a new SDK application translation interface 800 through a new SDK return button 302 to create a data return of the event monitoring SDK for a target application, where the new SDK application translation interface 800 includes a target application selection box 801 and an application identification input box 802, and may further include one or more of a translation target input box 803, a deep translation target input box 804, and a translation name input box 805.
The object may be, but is not limited to, a target application selection box 801 to select a target application for determining whether the event monitoring SDK integration is correct, and an application identifier corresponding to the selected target application is indicated to the server through an application identifier input box 802; the object may also indicate the above target event in a conversion target input box 803 or a depth conversion target input box 804.
As an embodiment, the object may also name the process for determining whether the event monitoring SDK integration is correct by creating the conversion name input box 805 in the SDK application conversion interface 800, so that the process is used to query the record for determining whether the event monitoring SDK integration is correct at a later stage.
After the object indicates one or more information through the SDK application translation interface 800, the completion button 806 may be clicked to send each information input by the object to the event monitoring management platform.
Referring to fig. 9 and fig. 10, when the object enters the interface 900 after clicking the completion button 806, the interface 900 is configured to prompt the object to determine whether the event monitoring SDK integration is correct, where the object determines that the event monitoring SDK is integrated in the target event and the self-test event monitoring SDK is successfully reported, and then the object may enter the terminal device indication interface 1000 through the deactivation button 901 in the interface 900.
With continued reference to fig. 10, the object may select, through the terminal device indication interface 1000, a device identifier type of the terminal device, where for a terminal device using the android system, the device identifier type may be, but is not limited to, an IMEI or an OAID of the terminal device.
After the object selects the device identifier type, the device identifier of the terminal device may be input through the device identifier input box 1001, and then the joint debugging interface 1100 is entered through the determination key 1002 (i.e., an interface where the object and the event monitoring management platform jointly determine whether the event monitoring SDK integration is correct).
Referring to fig. 11, after determining that the verification information displayed by the SDK initialization section in the joint debugging interface 1100 is correct, the object may trigger the SDK initialization detection request through the first detection request trigger key 1101 in the joint debugging interface 1100, where the verification information displayed by the SDK initialization section includes an application identifier, an application package name, an application english name, an application chinese name, or the like.
Correspondingly, after receiving the SDK initialization detection request, the server automatically opens an interface of the event monitoring SDK in the target application, receives the application identifier and the application package name uploaded by the terminal device through the interface, and performs initialization detection on the event monitoring SDK according to the above manner, which is not described repeatedly herein.
After the initialization of the event monitoring SDK in the target application is determined according to the verification information, and the object determines that the verification information displayed by the SDK event reporting part in the joint debugging interface 1100 is correct, the object may request the key 1102 to be triggered through the second detection request in the joint debugging interface 1100 to verify the event information reported by the event monitoring SDK, where the verification information displayed by the SDK event reporting part may be, but is not limited to, including a target event, such as the target event, where the activation of the conversion target and the payment of the deep conversion target shown in fig. 11 are both target events.
Correspondingly, the server may determine whether the event information reported by the terminal device includes the event information of the target event according to the above-mentioned manner, and a description thereof is not repeated here.
After the event monitoring SDK for monitoring the operation of other users on the target application is correctly integrated in the target application that needs to be advertised, the advertisement group may be created through the event monitoring management platform, the target application corresponding to the advertisement group is launched in the event monitoring management platform, and the conversion data condition reported by the event monitoring SDK may be checked in a certain manner, which is not described repeatedly here, and the advertisement group may correspond to one or more advertisements.
The following describes target events of embodiments of the present disclosure, which may include, but are not limited to, one or more of the following:
the method of the EVENT is applied to an ACTIVE EVENT, the method of the EVENT can be Turboagent.
An account EVENT is registered, the method of the EVENT can be Turboagent.
The EVENT is paid, the method of the EVENT can be Turboagent. onPay (), the key value of the EVENT is EVENT _ PAY, the application industry of the EVENT is not limited, the calling opportunity of the EVENT is called when the payment is successful, the parameter of the EVENT is purchasAmount (representing the price, the unit can be set as element), and the EVENT monitoring SDK must report the EVENT.
The method for submitting the FORM EVENT can be Turboagent, onFormSubmit (), the key value of the EVENT is EVENT _ FORM _ SUNMIT, the application industry of the EVENT is not limited, the EVENT is called when the FORM is submitted, no parameter exists, and the EVENT monitoring SDK is recommended to report the EVENT.
Completing an EVENT, wherein the EVENT method can be Turboagent.
The method of the EVENT can be Turboagent onCreditGrant (), the key value of the EVENT is EVENT _ CREDIT _ GRANT, the application industry of the EVENT is finance, the calling time of the EVENT is called by CREDIT time, no parameter exists, and the EVENT monitoring SDK is recommended to report the EVENT.
Browsing a commodity EVENT, wherein the EVENT method can be Turboagent, onGoodsView (double purchaseAmout), the key value of the EVENT is EVENT _ GOODS _ VIEW, the application industry of the EVENT is an e-commerce, the calling opportunity of the EVENT is called when the commodity is browsed, the parameter is purchaseAmount (representing the price, the unit can be set into a member and the like), and the EVENT monitoring SDK is recommended to report the EVENT.
Adding a shopping cart EVENT, wherein the method of the EVENT is Turboagent, on AddShoppengCart (double purchaseAmout), the key value of the EVENT is EVENT _ ADD _ SHOPPINGCAT, the application industry of the EVENT can be e-commerce, the calling time of the EVENT is called when the shopping cart is added, the parameter is purchaseAmount (representing the price, the unit can be set into element and the like), and the EVENT monitoring SDK is suggested to report the EVENT.
The method for submitting the ORDER EVENT comprises the steps of submitting the ORDER EVENT, wherein the method for submitting the ORDER EVENT is Turboagent, onOrderSubmit (double purchaseAmout), the key value of the EVENT is EVENT _ ORDER _ SUBMIT, the application industry of the EVENT can be e-commerce, the calling time of the EVENT is called when the ORDER is submitted, the parameter is purchaseAmount (representing the price, the unit can be set into element and the like), and the EVENT monitoring SDK is recommended to report the EVENT.
The method for paying the success EVENT is Turboagent, onOrderPayed (double purchaseAmout), the key value of the EVENT is EVENT _ ORDER _ PAED, the application industry of the EVENT can be e-commerce, the calling time of the EVENT is called when the payment is successful, the parameter is purchaseAmount (representing the price, the unit can be set to be element and the like), and the EVENT monitoring SDK is recommended to report the EVENT.
The method for creating the ROLE EVENT is Turboagent, onGameCreateRole (String roleName), the key value of the EVENT is EVENT _ GAME _ CREAT _ ROLE, the application industry of the EVENT can be GAMEs, the calling opportunity of the EVENT is reported when the ROLE in the GAME is created, the parameter is roleName (representing the name of the ROLE, such as a legal person, a fighter and the like), and the EVENT monitoring SDK is recommended to report the EVENT.
The method for upgrading the EVENT is TurboAgent, onGameUpdgradRole (int level), the key value of the EVENT is EVENT _ GAME _ UPGRADE _ ROLR, the application industry of the EVENT can be GAMEs, the calling opportunity of the EVENT is reported when the EVENT is upgraded, the parameter is level (representing role level and the like), and the EVENT monitoring SDK is recommended to report the EVENT.
The method for watching the incentive VIDEO EVENT is Turboagent, on GameWatchRewardvideo (), the key value of the EVENT is EVENT _ GAME _ WATCH _ REWARD _ VIDEO, the application industry of the EVENT can be GAMEs, the calling opportunity of the EVENT is reported when the incentive VIDEO is clicked to WATCH, no parameter exists, and the EVENT monitoring SDK is recommended to report the EVENT.
The EVENT consuming method is Turboagent. on GameConsumption (double purchaseAmpount), the key value of the EVENT is EVENT _ GAME _ CONSUMPTION, the application industry of the EVENT can be GAMEs, the calling time of the EVENT is the CONSUMPTION amount (the amount can be converted into equal amount of RMB, the unit can be set into element and the like) brought by the CONSUMPTION behavior generated by reporting the virtual GAME currency, no parameter exists, and the EVENT monitoring SDK is recommended to report the EVENT.
According to the method and the system, the object corresponding to the target application can apply for the application identification for the target application through the event monitoring management platform, and the event monitoring SDK is integrated in the target application according to the provided operation instruction and the interface provided by the event monitoring management platform and the indicated step, so that the integration process of the event monitoring SDK is simplified; and the server can judge whether the integration of the event monitoring SDK in the application is correct according to the verification information uploaded by the terminal equipment and the like, so that the correct information can be conveniently obtained through the SDK.
As shown in fig. 12, based on the same inventive concept, an apparatus 1200 for determining that event monitoring SDK integration is correct is further provided in the embodiments of the present disclosure, and includes a detection request receiving unit 1201, an authentication information receiving unit 1202, and an SDK integration authentication unit 1203, where:
the detection request receiving unit 1201 is configured to execute receiving a triggered SDK initialization detection request, where the SDK initialization detection request carries an application identifier of a target application of an integrated event monitoring SDK;
the authentication information receiving unit 1202 is configured to execute authentication information and event information for determining a target application corresponding to the application identifier, which is uploaded by a terminal device, where the authentication information and the event information are acquired through an event monitoring SDK integrated in the target application, the event information includes information of an operation performed on the target application, and the terminal device is a device in which the target application is installed;
the SDK integration verification unit 1203 is configured to determine that the event monitoring SDK is correctly integrated in the target application if it is determined that the initialization of the event monitoring SDK in the target application is completed according to the verification information and it is determined that the event information uploaded by the terminal device includes information of the target event.
Optionally, the SDK integrated verification unit 1203 is specifically configured to perform:
and if the corresponding relation between the application identifier and the application package name included in the verification information exists in the corresponding relation between the set application identifier and the application package name, determining that the initialization of the event monitoring SDK in the target application is completed.
Optionally, the correspondence between the application identifier and the application package name is obtained from a joint tone record corresponding to the terminal device, and the SDK integrated verification unit is further configured to perform:
if the corresponding relationship between the application identifier and the application package name included in the verification information exists in the corresponding relationship between the set application identifier and the application package name, determining the device identifier of the terminal device indicated by the newly-built SDK application conversion interface before the initialization of the event monitoring SDK in the target application is completed;
and determining the joint tone record corresponding to the equipment identifier as the joint tone record corresponding to the terminal equipment.
Optionally, the correspondence between the application identifier and the application package name is set when the application identifier is allocated to the at least one target application through the identifier application interface.
Optionally, the detection request receiving unit 1201 is further configured to perform:
and before receiving a triggered SDK initialization detection request, determining the target event indicated by the object by newly building an SDK application conversion interface.
As shown in fig. 13, the present disclosure provides an electronic device 1300 comprising a processor 1301, a memory 1302 for storing the processor-executable instructions described above;
wherein, the processor 1301 is configured to perform the following processes:
receiving a triggered SDK initialization detection request, wherein the SDK initialization detection request carries an application identifier of a target application of an integrated event monitoring SDK;
determining verification information and event information of a target application corresponding to the application identifier, which are uploaded by a terminal device, wherein the verification information and the event information are acquired through an event monitoring SDK integrated in the target application, the event information comprises information of operation performed on the target application, and the terminal device is a device installed with the target application;
and if the fact that the initialization of the event monitoring SDK in the target application is completed is determined according to the verification information, and the fact that the event information uploaded by the terminal equipment comprises the information of the target event is determined, the fact that the event monitoring SDK is correctly integrated in the target application is determined.
Optionally, the processor 1301 is specifically configured to perform:
and if the corresponding relation between the application identifier and the application package name included in the verification information exists in the corresponding relation between the set application identifier and the application package name, determining that the initialization of the event monitoring SDK in the target application is completed.
Optionally, the correspondence between the application identifier and the application package name is obtained from the joint tone record corresponding to the terminal device, and the processor 1301 is further specifically configured to execute:
if the corresponding relationship between the application identifier and the application package name included in the verification information exists in the corresponding relationship between the set application identifier and the application package name, determining the device identifier of the terminal device indicated by the newly-built SDK application conversion interface before the initialization of the event monitoring SDK in the target application is completed;
and determining the joint tone record corresponding to the equipment identifier as the joint tone record corresponding to the terminal equipment.
Optionally, the correspondence between the application identifier and the application package name is set when the application identifier is allocated to the at least one target application through the identifier application interface.
Optionally, the processor is configured to perform:
and before receiving a triggered SDK initialization detection request, determining the target event indicated by the object by newly building an SDK application conversion interface.
In an exemplary embodiment, a storage medium comprising instructions, such as a memory comprising instructions, executable by a processor of the electronic device to perform the method is also provided. Alternatively, the storage medium may be a non-transitory computer readable storage medium, for example, which may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A method for determining correct integration of an event monitoring SDK, comprising:
receiving a triggered SDK initialization detection request, wherein the SDK initialization detection request carries an application identifier of a target application of an integrated event monitoring SDK;
determining verification information and event information of a target application corresponding to the application identifier and uploaded by a terminal device, wherein the verification information and the event information are acquired through an event monitoring SDK integrated in the target application, the event information comprises information of operation performed on the target application, and the terminal device is a device installed with the target application;
and if the fact that the initialization of the event monitoring SDK in the target application is completed is determined according to the verification information, and the fact that the event information uploaded by the terminal equipment comprises the information of the target event is determined, the fact that the event monitoring SDK is correctly integrated in the target application is determined.
2. The method of claim 1, wherein the step of determining that initialization of the event monitoring SDK in the target application is complete based on the validation information comprises:
and if the corresponding relation between the application identifier and the application package name included in the verification information exists in the corresponding relation between the set application identifier and the application package name, determining that the initialization of the event monitoring SDK in the target application is completed.
3. The method according to claim 2, wherein the correspondence between the application identifier and the application package name is obtained from a joint record corresponding to the terminal device, and before the step of determining that the initialization of the event monitoring SDK in the target application is completed if the correspondence between the application identifier and the application package name included in the verification information exists in the set correspondence between the application identifier and the application package name, the method further includes:
determining the equipment identifier of the terminal equipment indicated by the newly-built SDK application conversion interface;
and determining the joint tone record corresponding to the equipment identifier as the joint tone record corresponding to the terminal equipment.
4. The method according to claim 2 or 3, wherein the correspondence between the application identifier and the application package name is set when the application identifier is allocated to the at least one target application through an identifier application interface.
5. The method of any of claims 1-3, wherein the step of receiving a triggered SDK initialization detection request is preceded by the step of:
and determining the target event indicated by the object by newly building an SDK application conversion interface.
6. An apparatus for determining correct integration of an event monitoring SDK, comprising a detection request receiving unit, an authentication information receiving unit, and an SDK integration authentication unit, wherein:
the detection request receiving unit is configured to execute receiving of a triggered SDK initialization detection request, wherein the SDK initialization detection request carries an application identifier of a target application of an integrated event monitoring SDK;
the verification information receiving unit is configured to execute verification information and event information of a target application corresponding to the application identifier and uploaded by a terminal device, wherein the verification information and the event information are acquired through an event monitoring SDK integrated in the target application, the event information comprises information of operation performed on the target application, and the terminal device is a device installed with the target application;
the SDK integration verification unit is configured to determine that the event monitoring SDK is integrated correctly in the target application if the fact that initialization of the event monitoring SDK in the target application is completed is determined according to the verification information and the fact that the event information uploaded by the terminal device includes the information of the target event is determined.
7. The apparatus of claim 6, wherein the SDK integrated authentication unit is specifically configured to perform:
and if the corresponding relation between the application identifier and the application package name included in the verification information exists in the corresponding relation between the set application identifier and the application package name, determining that the initialization of the event monitoring SDK in the target application is completed.
8. The apparatus of claim 7, wherein the correspondence between the application identifier and the application package name is obtained from a joint tone record corresponding to the terminal device, and wherein the SDK integrated verification unit is further configured to perform:
if the corresponding relation between the application identifier and the application package name included in the verification information exists in the corresponding relation between the set application identifier and the application package name, determining the equipment identifier of the terminal equipment indicated by a newly-built SDK application conversion interface before the initialization of the event monitoring SDK in the target application is completed;
and determining the joint tone record corresponding to the equipment identifier as the joint tone record corresponding to the terminal equipment.
9. An electronic device comprising a processor, a memory for storing instructions executable by the processor;
wherein the processor is configured to perform the method of any one of claims 1 to 5.
10. A computer-readable storage medium having stored thereon computer instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010085218.7A CN111309551B (en) | 2020-02-10 | 2020-02-10 | Method and device for determining event monitoring SDK integration correctness |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010085218.7A CN111309551B (en) | 2020-02-10 | 2020-02-10 | Method and device for determining event monitoring SDK integration correctness |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111309551A true CN111309551A (en) | 2020-06-19 |
| CN111309551B CN111309551B (en) | 2023-08-08 |
Family
ID=71159224
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010085218.7A Active CN111309551B (en) | 2020-02-10 | 2020-02-10 | Method and device for determining event monitoring SDK integration correctness |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111309551B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113064822A (en) * | 2021-03-29 | 2021-07-02 | 上海酷量信息技术有限公司 | Application joint debugging method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103488489A (en) * | 2013-09-30 | 2014-01-01 | 乐视网信息技术（北京）股份有限公司 | Data processing method and device |
| CN108037989A (en) * | 2017-12-15 | 2018-05-15 | 北京小米移动软件有限公司 | SDK component identification methods and device |
| US20180181482A1 (en) * | 2016-12-22 | 2018-06-28 | SafeDK Mobile Ltd. | Monitoring Activity of Software Development Kits Using Stack Trace Analysis |
| CN110119350A (en) * | 2019-04-02 | 2019-08-13 | 深圳市腾讯信息技术有限公司 | Software Development Kit test method, device and equipment and computer storage medium |
| CN110209381A (en) * | 2019-05-31 | 2019-09-06 | 深圳前海微众银行股份有限公司 | SDK fast integration method, apparatus, equipment and storage medium based on block chain |
-
2020
- 2020-02-10 CN CN202010085218.7A patent/CN111309551B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103488489A (en) * | 2013-09-30 | 2014-01-01 | 乐视网信息技术（北京）股份有限公司 | Data processing method and device |
| US20180181482A1 (en) * | 2016-12-22 | 2018-06-28 | SafeDK Mobile Ltd. | Monitoring Activity of Software Development Kits Using Stack Trace Analysis |
| CN108037989A (en) * | 2017-12-15 | 2018-05-15 | 北京小米移动软件有限公司 | SDK component identification methods and device |
| CN110119350A (en) * | 2019-04-02 | 2019-08-13 | 深圳市腾讯信息技术有限公司 | Software Development Kit test method, device and equipment and computer storage medium |
| CN110209381A (en) * | 2019-05-31 | 2019-09-06 | 深圳前海微众银行股份有限公司 | SDK fast integration method, apparatus, equipment and storage medium based on block chain |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113064822A (en) * | 2021-03-29 | 2021-07-02 | 上海酷量信息技术有限公司 | Application joint debugging method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111309551B (en) | 2023-08-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113835777B (en) | Mobile application activity detector | |
| US9244818B1 (en) | Automated selection of quality control tests to run on a software application | |
| US8234692B2 (en) | System and method for processing an upload of a program with export compliance information | |
| US20100122351A1 (en) | Software Application Framework for Network-Connected Devices | |
| CN106897096B (en) | JAVA shop | |
| US20160071156A1 (en) | Information processing method and device | |
| US8856685B2 (en) | Method and system for providing web content on a mobile device | |
| US20140025469A1 (en) | Reward granting apparatus, reward granting method, and reward granting program | |
| CN107608663B (en) | Mobile application plug-in and mobile application development method and device | |
| AU2018241159B2 (en) | Contextual solicitation in a starter application | |
| US11846972B2 (en) | Method and apparatus for generating software test reports | |
| US8695020B2 (en) | Techniques for customizing a toolbar using widgets | |
| CN111367531A (en) | Code processing method and device | |
| CN110674023B (en) | Interface testing method and device | |
| JP2013143125A (en) | Platform system of network infrastructure | |
| CN111309551A (en) | Method and device for determining correct integration of event monitoring SDK | |
| US9354849B2 (en) | Modification of compiled applications and application management using retrievable policies | |
| CN106034150B (en) | Application program dynamic pushing method, device and system | |
| US20130054409A1 (en) | In-application purchasing method and method for processing in-application purchase | |
| US11381940B1 (en) | Tethering computer programs and user interfaces to selected targets | |
| US10755321B1 (en) | Techniques for dynamic utilization of advertising capabilities by applications on user devices | |
| KR101837255B1 (en) | System and method for providing on-line game service | |
| KR101717772B1 (en) | An App market place system for multi-device environment | |
| CN113901483A (en) | Application detection method and device, computer storage medium and electronic equipment | |
| CN117111810A (en) | Event interaction processing method and device, electronic equipment and storage medium |
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 |