Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein, but rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
FIG. 1 illustrates a schematic diagram of an exemplary system architecture to which the methods for data monitoring of embodiments of the present disclosure may be applied.
As shown in fig. 1, the system architecture may include a server 101, a network 102, and a terminal device 103. The network 102 is a medium used to provide a communication link between the terminal device 103 and the server 101. Network 102 may include various connection types such as wired, wireless communication links, or fiber optic cables, among others.
The server 101 may be a server providing various services, such as a background management server providing support for devices operated by the user with the terminal device 103. The background management server may perform analysis and other processing on the received data such as the request, and feed back the processing result to the terminal device 103.
In the embodiment of the present disclosure, the Server may be a click monitoring Server (Server), but the present disclosure is not limited thereto.
The terminal device 103 may be a mobile terminal such as a mobile phone, a game console, a tablet computer, an electronic book reader, smart glasses, a smart home device, an AR (Augmented Reality) device, a VR (Virtual Reality) device, or the like, or the terminal device 103 may be a personal computer such as a laptop portable computer and a desktop computer, or the like.
The server 101 may respond to the action of clicking the directional link by the user, execute a call-up protocol to enable the terminal device to open a target application in the terminal device 103, send a data monitoring request to the server 101 by the terminal device 103, receive the data monitoring request sent by the terminal device 103 by the server 101, where the data monitoring request may include a terminal device identifier of the terminal device 103 and a directional link identifier of the directional link, generate a data tracking parameter corresponding to the directional link identifier in real time by the server 101, redirect the terminal device 103 to a preset page by the server 101, splice the terminal device identifier and the data tracking parameter to the call-up protocol by the server 101, enable the terminal device 103 to open a target page corresponding to the directional link by the server 101, and monitor the operation action of the user on the target page.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative, and the server 101 may be a server of one entity, may be a server cluster formed by a plurality of servers, may be a cloud server, and may have any number of terminal devices, networks and servers according to actual needs.
The steps of the method for data monitoring in the exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings and examples.
FIG. 2 is a flow chart illustrating a method for data monitoring according to an exemplary embodiment. The method provided by the embodiment of the present disclosure may be performed by a server or a terminal device as shown in fig. 1, for example, may be performed by a click monitoring server, but the present disclosure is not limited thereto.
As shown in fig. 2, a method for data monitoring provided by an embodiment of the present disclosure may include the following steps.
In step S202, in response to the behavior that the target object clicks on the directional link, a call-up protocol is executed to open the target application.
In the embodiment of the disclosure, the target object may be a user who operates the terminal device.
In the embodiment of the disclosure, the directional link may be set in association with the directional information, and the user may jump to the target application by clicking on the directional link or the directional information.
The orientation information may refer to information that a certain designated information (which may be any one or a combination of a plurality of pictures, videos, audios, texts, etc.) is put on a target media platform according to a preset orientation information putting policy for display. In the following examples, the advertisement is described by taking the targeting information as an example, but the present disclosure is not limited thereto.
In the embodiment of the disclosure, the target media platform may be a platform, a webpage or an Application program for displaying the directional link or the directional information, and the target Application may be an Application program (APP) or a webpage to which the directional link points.
For example, the target media platform may be a social APP, a video play APP, a travel APP, etc., and the target application may be a shopping APP, an application store APP, etc.
In the embodiment of the disclosure, the call-up protocol may be an open app protocol, that is, a protocol that jumps from one application to another application.
In an exemplary embodiment, the directional link may include a call-up protocol.
In an exemplary embodiment, the directional links may include preset page links, which may include call-up protocols and target page links.
The preset page may be, for example, a blank page, and the preset page link may be, for example, a blank page URL (Uniform Resource Locator ), where the blank page URL may include a call-up protocol (or include logic spliced into the call-up protocol) and a macro to be replaced. The macro to be replaced may include a return button parameter, a target page URL, and the like. The target page may be a floor page.
In the embodiment of the disclosure, a layer of click codes can be packaged on blank page URLs, the packaged URLs are used as parameter values of TO URLs and are put into an calling-up protocol (open app protocol), and other fixed parameters are added TO the calling-up protocol TO form a complete directional link.
In an exemplary embodiment, the directional link may be a deep link (Deeplink).
Wherein Deeplink links can implement application direct, i.e., clicking on an advertisement or button (button) at one APP directly hangs another APP. DeepLink can realize direct skip between webpages, direct skip between APPs or direct skip between webpages and APPs.
In an exemplary embodiment, the act of clicking on the directional link in the target media platform in response to the target object.
For example, the user may click on advertisement information in the social software (the user clicking on advertisement information corresponds to clicking on an advertisement link), and the server may execute a call-up protocol included in the advertisement link in response to the clicking action of the user, so that the terminal device opens shopping software corresponding to the advertisement information.
In step S204, a data monitoring request sent by a target application is received.
Wherein the data monitoring request includes a terminal device identification of the terminal device and a directional link identification of the directional link.
The terminal device identifier may be Imei (International Mobile Equipment Identity ), and the directional link identifier may be Idfa (IDENTIFIER FOR ADVERTISING, advertisement identifier), for example, but the disclosure is not limited thereto.
In an embodiment of the disclosure, the target application may send a data monitoring request to the click monitoring server, which may receive the data monitoring request.
In the embodiment of the disclosure, the click monitoring server can acquire the terminal equipment identifier from the data monitoring request, and the media platform is not required to return the terminal equipment identifier, so that the dependence on the media platform can be reduced.
In the embodiment of the disclosure, the terminal device may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc., but the disclosure is not limited thereto.
In the embodiment of the disclosure, the data monitoring request may include data (Cookie) stored on the local terminal device of the user, where the data may include preset advertisement attribution logic.
In step S206, data tracking parameters corresponding to the directional link identification are generated.
In the embodiment of the disclosure, the click monitoring server can generate the data tracking parameters corresponding to the directional link identifiers one by one in real time, and the data tracking parameters are used for tracking the behavior of the user after clicking the directional link.
For example, after clicking an advertisement, the user jumps to an item detail page corresponding to the advertisement, and after generating data tracking parameters corresponding to the advertisement, the server may bring the data tracking parameters to the item detail page, so that the user may associate with the advertisement in the actions of browsing, purchasing, ordering, etc. of the item detail page.
In an exemplary embodiment, the data tracking parameters are UTM (Urchin Tracking Module, tracking module) parameters.
In embodiments of the present disclosure, traffic sources may be counted using UTM parameters.
The UTM parameters may include UTM _source, utm_medium, utm_campaign, utm_content, utm_term, and the like, among others.
In the disclosed embodiment utm _source may be defined as an advertisement source for representing a search engine, channel name, or other source, utm _medium may be defined as an advertisement medium for representing a specific form of advertisement, utm _campaign may be defined as an advertisement name, utm _content may be defined as advertisement content, and utm _term may be defined as an advertisement keyword.
According to the embodiment of the disclosure, the click monitoring server can generate UTM parameters corresponding to each advertisement in real time, splice the UTM parameters, splice the spliced parameters in a call-up protocol and bring the call-up protocol to a landing page, so that the landing page and the subsequent browsing behavior of the same session can be associated with a click monitoring log through UTM _term (keywords), and the monitoring of the drainage effect of the advertisement landing page in the APP and the analysis of the deep browsing behavior after the advertisement landing page arrives at the station are realized.
In step S208, redirection is performed to skip the terminal device to a preset page, so as to splice the terminal device identifier and the data tracking parameter to the call-up protocol.
In an exemplary embodiment, the preset page is a blank page.
It should be noted that, the preset page may be other pages, or may be implemented by other components in the APP, which is not limited in this disclosure.
In the disclosed embodiment, the redirection may be 302 redirection.
Redirection (Redirect) may Redirect various network requests to other locations (e.g., web page redirection, redirection of domain names, change in routing is also a redirection of data messages via paths). 302 redirection is also known as temporary transfer.
In the embodiment of the disclosure, the click monitoring server may perform 302 redirection to make the terminal device jump to a blank page, and may splice the terminal device identifier, the data tracking parameter, the Cookie data and the like to the call-up protocol.
In the embodiment of the disclosure, the terminal equipment can jump to the blank page through 302 redirection, and after the terminal equipment identification and the data tracking parameters are spliced to the blank page, the target page is opened, so that the terminal equipment identification and the data tracking parameters can be brought to the landing page, and the follow-up monitoring and analysis of the operation of a user on the landing page are facilitated.
In step S210, the spliced call-up protocol is executed to open the target page corresponding to the directional link.
In an exemplary embodiment, a post-concatenation call-up protocol is executed, so that the terminal device opens a target page corresponding to the directional link.
In the embodiment of the disclosure, the server may execute the post-concatenation call-up protocol, so that the terminal device opens the target page corresponding to the directional link.
For example, the server may execute a post-splice call-up protocol, so that the terminal device opens an item detail page corresponding to the advertisement clicked by the user.
The method for data monitoring can respond to the action of clicking the directional link by the target object, execute the call-up protocol to open the target application, acquire the terminal equipment identifier and the directional link identifier from the data monitoring request sent by the target application, reduce the dependence on a media platform, generate the data tracking parameter corresponding to the directional link identifier, monitor the action of clicking the directional link of each target object, jump the terminal equipment to a preset page through redirection, splice the terminal equipment identifier and the data tracking parameter to the call-up protocol, execute the call-up protocol after splicing, open the target page, bring the terminal equipment identifier and the data tracking parameter to the target page, correlate the action of clicking the directional link by the target object and the operation of the subsequent target object on the target page, realize the monitoring and analysis of the subsequent operation action of the target object, and accurately obtain the conversion effect of the directional information corresponding to the directional link.
FIG. 3 is a flow chart illustrating another method for data monitoring according to an exemplary embodiment.
In an embodiment of the present disclosure, the method for data monitoring shown in fig. 3 may further include the following steps on the basis of the method for data monitoring shown in fig. 2.
In step S302, user behavior data generated by the target object operation target page is acquired.
In the embodiment of the disclosure, after the terminal device opens the target page, the target object may operate the target page, and the server may obtain user behavior data generated by the target object operating the target page.
The operation target page may include, but is not limited to, browsing the target page, sliding the target page, clicking a button in the target page, and the like.
For example, after the terminal device opens the item detail page, the user may browse the item detail page, slide the item detail page up and down or left and right, click a "enter shopping cart" or "go to purchase" button in the item detail page, the terminal device may generate user behavior data according to the operation of the user and send the user behavior data to the server, and the server may acquire the user behavior data generated by the operation of the user.
In step S304, the user behavior data is analyzed to obtain a data monitoring result.
In the embodiment of the disclosure, the user behavior data and the terminal equipment identifier and the directional link identifier can be associated for analysis, so that a data monitoring result is obtained.
For example, the purchasing behavior of the user may be associated with an advertisement identification to obtain a conversion effect of the advertisement.
In an exemplary embodiment, analyzing the user behavior data to obtain a data monitoring result may include storing a terminal device identifier and a data tracking parameter in a click monitoring log, reporting the terminal device identifier, the data tracking parameter and the user behavior data to a buried point log of a target page, and obtaining the data monitoring result according to the click monitoring log and the buried point log.
In the embodiment of the disclosure, the server may store the terminal device identifier in the data monitoring request and the data tracking parameter generated in real time in the click monitoring log.
In the embodiment of the disclosure, the server may report the terminal device identifier and the data tracking parameter to the embedded point log of the target page.
In the embodiment of the disclosure, after generating the user behavior data, the server may report the user behavior data to the embedded point log of the target page.
In the embodiment of the disclosure, the click monitoring log and the buried point log can be associated through the terminal equipment identifier (such as Device ID) and the data tracking parameter (such as UTM parameter), the behavior data of the user is analyzed, the relationship between the subsequent operation behavior of the user and the click directional link is obtained, and the conversion rate of the directional information corresponding to the directional link is determined.
Fig. 4 is a schematic diagram illustrating a system architecture for data monitoring, according to an example.
Referring to fig. 4, the media may display advertisement information, a user may click an advertisement (equivalent to clicking Deeplink links) on the media, the server may execute a call-up protocol, so that the terminal device jumps from the media to the APP, the APP may send a data monitoring request to the click monitoring server, the click monitoring server may acquire a terminal device identifier and an advertisement identifier from the data monitoring request, and generate UTM parameters corresponding to the advertisement identifier in real time, the click monitoring server performs 302 redirection to cause the terminal device to jump to a blank page, and splice the UTM parameters to the call-up protocol, and execute the spliced call-up protocol inside the APP, and jump to an APP internal page. The subsequent operation behavior of the user on the APP internal page can be monitored through an APP embedded point server, the APP embedded point server can generate an APP embedded point log, the click monitoring server can generate a click monitoring log, the click monitoring log and the APP embedded point log can be associated through parameters such as terminal equipment identification, UTM and the like, and the association attribution of the APP internal behavior event and the advertisement event can be carried out by taking the terminal equipment identification and the UTM as Key values.
It should be noted that the server, the click monitoring server, and the blank page server may be the same entity server, or may be different servers, which is not limited in this disclosure.
It is noted that the above-described figures are merely schematic illustrations of processes involved in a method according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
The following are device embodiments of the present disclosure that may be used to perform method embodiments of the present disclosure. For details not disclosed in the embodiments of the apparatus of the present disclosure, please refer to the embodiments of the method of the present disclosure.
Fig. 5 is a block diagram illustrating an apparatus for data monitoring according to an exemplary embodiment.
As shown in fig. 5, an apparatus 500 for data monitoring may include a first protocol execution module 502, a request receiving module 504, a parameter generating module 506, a page skip module 508, a second protocol execution module 510.
The first protocol execution module 502 may be configured to respond to a target object clicking action of a directional link to execute a call-up protocol to open a target application, the request receiving module 504 may be configured to receive a data monitoring request sent by the target application, where the data monitoring request includes a terminal device identifier of a terminal device and a directional link identifier of the directional link, the parameter generating module 506 may be configured to generate a data tracking parameter corresponding to the directional link identifier, the page skip module 508 may be configured to redirect the terminal device to a preset page to splice the terminal device identifier and the data tracking parameter to the call-up protocol, and the second protocol execution module 510 may be configured to execute the spliced call-up protocol to open the target page corresponding to the directional link.
In an exemplary embodiment, the directional link includes a preset page link including the call-up protocol and a target page link.
In an exemplary embodiment, the apparatus 500 for data monitoring may further include a data obtaining module, configured to obtain user behavior data generated by the target object operating the target page, and a result obtaining module, configured to analyze the user behavior data to obtain a data monitoring result.
In an exemplary embodiment, the result obtaining module may include a parameter saving unit configured to save the terminal device identifier and the data tracking parameter to a click monitoring log, a parameter reporting unit configured to report the terminal device identifier, the data tracking parameter, and the user behavior data to a buried point log of the target page, and a result obtaining unit configured to obtain the data monitoring result according to the click monitoring log and the buried point log.
In an exemplary embodiment, the second protocol execution module 510 may include a protocol execution unit, which may be configured to execute the spliced call-up protocol, so that the terminal device opens the target page corresponding to the directional link.
In an exemplary embodiment, the first protocol execution module 502 may include a behavior response unit that may be used to respond to the behavior of the target object clicking on the directional link in the target media platform.
In an exemplary embodiment, the directional link is a deep link Deeplink, the data tracking parameter is a UTM parameter, and the preset page is a blank page.
It should be noted that the block diagrams shown in the above figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
Fig. 6 is a schematic diagram of an electronic device according to an exemplary embodiment. It should be noted that the electronic device shown in fig. 6 is only an example, and should not impose any limitation on the functions and application scope of the embodiments of the present invention.
As shown in fig. 6, the electronic device 600 includes a Central Processing Unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the system 600 are also stored. The CPU601, ROM 602, and RAM 603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Connected to the I/O interface 605 are an input section 606 including a keyboard, a mouse, and the like, an output section 607 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like, a storage section 608 including a hard disk, and the like, and a communication section 609 including a network interface card such as a LAN card, a modem, and the like. The communication section 609 performs communication processing via a network such as the internet. The drive 610 is also connected to the I/O interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on drive 610 so that a computer program read therefrom is installed as needed into storage section 608.
In particular, according to embodiments of the present invention, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 601.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of a computer-readable storage medium may include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present invention may be implemented in software or in hardware. The described units may also be provided in a processor, for example as a processor comprising a sending unit, an obtaining unit, a determining unit and a first processing unit. The names of these units do not constitute a limitation on the unit itself in some cases, and for example, the transmitting unit may also be described as "a unit that transmits a picture acquisition request to a connected server".
As a further aspect, the invention also provides a computer readable medium which may be comprised in the device described in the above embodiments or may be present alone without being fitted into the device. The computer readable medium carries one or more programs, when the one or more programs are executed by the equipment, the equipment comprises a behavior of responding to a target object to click on a directional link, executing a call-up protocol to open a target application, receiving a data monitoring request sent by the target application, wherein the data monitoring request comprises a terminal equipment identifier of the terminal equipment and a directional link identifier of the directional link, generating a data tracking parameter corresponding to the directional link identifier, carrying out redirection to enable the terminal equipment to jump to a preset page so as to splice the terminal equipment identifier and the data tracking parameter to the call-up protocol, and executing the spliced call-up protocol to open the target page corresponding to the directional link.
The exemplary embodiments of the present invention have been particularly shown and described above. It is to be understood that the invention is not to be limited to the specific constructions, arrangements, or instrumentalities described herein, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.