CN104750717B - A kind of click volume recording method, server and client - Google Patents

Abstract

The invention discloses a method for recording hits, which is used for better statistics of hits in applications. The method includes: the server obtains M pieces of click information for an application sent by the client, the click information includes address information of the client; wherein, the click information is obtained through the client installed in the client component, the client component is installed in the browser of the client, the application is an application running in the browser, M is a positive integer; the server saves the M click information . The invention also discloses another method for recording hits, a server and a client.

Description

A method for recording hits, server and client

technical field

The invention relates to the field of computer technology, in particular to a method for recording hits, a server and a client.

Background technique

In the prior art, there is already a method for counting hits for applications in the Web (World Wide Web), mainly for web pages, formulating statistical rules, and initiating statistical requests through dynamic pages or static pages.

Generally speaking, the request is initiated through the built-in JS (javascript, a scripting language) in the page, and the server-side code or Web service is called for statistics.

There are following deficiencies in the scheme in the prior art:

This method is mainly aimed at a single page or a single application. Statistics are made by embedding JS codes in the pages. It is necessary to "modify" the application and insert new codes, and the process is relatively complicated. However, the encoding methods and statistical rules of different pages are not the same, and the same JS code cannot be used to complete the statistics. It can be seen that the portability of the JS code in this statistical method is weak, and if there are too many pages, it will increase too much. Workload, not universal.

This method is mainly based on the mechanical addition operation of the page request. It cannot be avoided for some illegal requests, automatic refreshing of tools, etc., resulting in low accuracy of the obtained statistical data.

This method is only a common counting operation, and the source of the data cannot be traced, which also makes it impossible to locate illegal data.

It can be seen that there is no better method for calculating clicks in the prior art.

Contents of the invention

An embodiment of the present invention provides a server and a client of a method for recording hits, which are used to provide a better method for counting hits.

A method for recording hits, comprising:

The server obtains M pieces of click information for an application sent by the client, and the click information includes the address information of the client; wherein, the click information is obtained through a client component installed in the client, and The client component is installed in the browser of the client, the application is an application running in the browser, and M is a positive integer;

The server saves the M pieces of click information.

Preferably, the click information also includes user information corresponding to the user who clicked.

Preferably, the server storing the M pieces of click information includes: the server filters the M pieces of click information according to preset rules and then saves them.

Preferably, the server filters the M click information according to preset rules, including:

The server matches each of the M pieces of click information with preset N click information templates, and the click information templates are information templates corresponding to click information other than user behavior; wherein, each click information The template corresponds to click information of a non-user behavior, and N is a positive integer;

The server discards click information that matches successfully.

A method for recording hits, comprising:

When the client runs an application through the browser, the client component is obtained, and the client component is used to obtain click information for the application, the click information includes the address information of the client, and the click information is for the Obtained when the application clicks;

The client obtains M click information through the application component;

The client sends the M pieces of click information to the server for storage.

Preferably, the client obtains client components, including: the client obtains header and footer components or highly adaptive IFrame components, and the client components are embedded in the header and footer components or the IFrame in the component.

Preferably, the click information also includes user information corresponding to the user who clicked.

A server comprising:

The first obtaining module is used to obtain M pieces of click information for an application sent by the client, and the click information includes the address information of the client; obtained by the client component, the client component is installed in the browser of the client, the application is an application running in the browser, and M is a positive integer;

An operation module, configured to save the M pieces of click information.

Preferably, the click information also includes user information corresponding to the user who clicked.

Preferably, the operation module is specifically configured to: filter and save the M pieces of click information according to preset rules.

Preferably, the operation module is specifically configured to: match each of the M pieces of click information with preset N click information templates, and the click information templates are click information corresponding to non-user behaviors. Information templates; wherein, each click information template corresponds to a click information of a non-user behavior, and N is a positive integer; click information that matches successfully is discarded.

A client, including:

The second acquisition module is configured to obtain a client component when running an application through a browser, the client component is used to obtain click information for the application, the click information includes address information of the client, and The above click information is obtained when clicking on the application;

The third obtaining module is used to obtain M pieces of click information through the application component;

A sending module, configured to send the M pieces of click information to a server for storage.

Preferably, the second acquiring module is specifically configured to: acquire header and footer components or a highly adaptive IFrame component, and the client component is embedded in the header and footer components or the IFrame component.

Preferably, the click information also includes user information corresponding to the user who clicked.

In the embodiment of the present invention, the server may save the M click information after obtaining the M click information, and the click information includes the address information of the client, so that each click corresponds to The information is recorded, the source of the data can be traced, the abnormal data can be easily located, and even the data can be fine-tuned. Moreover, the click information is obtained through the client component installed in the browser, that is, in the embodiment of the present invention, the click information is obtained through the client component, and there is no need to modify the application, so The client component described above can be installed in the browser, has strong portability and versatility, and has a relatively wide range of applications.

Description of drawings

Fig. 1 is the main flow chart of a kind of hit record method in the embodiment of the present invention;

Fig. 2 is the main flow chart of another kind of hit record method in the embodiment of the present invention;

FIG. 3 is a structural block diagram of a server in an embodiment of the present invention;

FIG. 4 is a structural block diagram of a client in an embodiment of the present invention.

Detailed ways

The method for recording clicks in the embodiment of the present invention may include: the server obtains M pieces of click information for an application sent by the client, and the click information includes the address information of the client; wherein, the click information is obtained through the The client component installed in the client is obtained, the client component is installed in the browser of the client, the application is an application running in the browser, M is a positive integer; the server will The M pieces of click information are saved.

In the embodiment of the present invention, the server may save the M click information after obtaining the M click information, and the click information includes the address information of the client, so that each click corresponds to The information is recorded, the source of the data can be traced, the abnormal data can be easily located, and even the data can be fine-tuned. Moreover, the click information is obtained through the client component installed in the browser, that is, in the embodiment of the present invention, the click information is obtained through the client component, and there is no need to modify the application, so The client component described above can be installed in the browser, has strong portability and versatility, and has a relatively wide range of applications.

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

Additionally, the terms "system" and "network" are often used herein interchangeably.

The term "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

The embodiments of the present invention will be further described in detail below in conjunction with the accompanying drawings.

Please refer to Fig. 1, the embodiment of the present invention provides a method for recording hits, the main flow of the method is as follows:

Step 101: The server obtains M pieces of click information for an application sent by the client, and the click information includes the address information of the client; wherein, the click information is obtained through a client component installed in the client Yes, the client component is installed in the browser of the client, the application is an application running in the browser, and M is a positive integer.

In the embodiment of the present invention, the application may be an application running in the browser, such as some small games or the like. When a user performs a click operation on the application, the client component may obtain click information corresponding to the click operation performed by the user.

In the embodiment of the present invention, M may be 1, that is, the client will report the click information to the server every time it obtains one click information.

Alternatively, in the embodiment of the present invention, M may be greater than 1, that is, the client reports the obtained click information to the server after obtaining multiple click information. For example, the client may report periodically, that is, report the click information obtained within a period to the server, or the client may report when triggered, or the client may report the click information when the application exits Report all the click information obtained at the time, which is not specifically limited in the present invention.

Preferably, the address information of the client may refer to the IP (Internet Protocol) address of the client, or may refer to the MAC (medium access control, medium access control) address of the client, or may refer to Other address information of the client.

Preferably, in the embodiment of the present invention, in addition to the address information of the client, the click information may also include user information corresponding to the user who made the click. For example, if M=2, the client has reported two click information in total, the first click information is generated by user 1 performing click operation 1, and the second click information is generated by user 2 performing click operation 2 , then the first click information may include the address information of the client and the user information of the user 1, and the second click information may include the address information of the client and the user 2 user information.

Step 102: The server saves the M pieces of click information.

After receiving the M pieces of click information, the server may store the M pieces of click information.

Preferably, the server saves the M pieces of click information. Specifically, the server stores the M pieces of click information after filtering according to preset rules.

That is, after receiving the M pieces of click information, the server may first filter the M pieces of click information, and save the remaining click information after filtering.

Preferably, in the embodiment of the present invention, the server filters the M pieces of click information according to preset rules. Specifically, the server filters each of the M pieces of click information with the preset N click information templates are matched, and the click information templates are information templates corresponding to non-user behavior click information; wherein, each click information template corresponds to a kind of non-user behavior click information, and N is a positive integer; The server discards click information that matches successfully.

In the embodiment of the present invention, the click information of non-user behavior can be, for example, page information redirected by SSO, or blacklisted URL data, or page access information without UA (user agent, user agent) information, or Some search website crawler information and so on. For example, each type of click information of non-user behaviors may correspond to one click information template, and click information of N types of non-user behaviors may correspond to N click information templates. Preferably, as many click information templates as possible can be set to consider possible non-user behavior click information more comprehensively, which can improve the reliability of the filtering process, so that useless click information can be filtered out as much as possible, thereby enabling The resulting clicks are more accurate.

Preferably, in the embodiment of the present invention, one click information is matched with the N click information templates, as long as the click information matches one of the click information templates, it can be indicated that the click information is a non-user click information, you can filter it out. In the embodiment of the present invention, filtering out a piece of click information may refer to discarding the click information.

After filtering, the server may save the remaining click information after filtering, and it may be considered that the remaining click information after filtering is the click information of the user's behavior, which is valid click information. For example, the server may save the remaining click information after filtering in the form of a list. Because the click information may include the address information of the client and the user information of the corresponding user who performed the click operation, then according to the list generated by the server, the specific information corresponding to each click information can be determined, which can be traced back. The source of the data makes it easy to locate abnormal data and even fine-tune the data.

Moreover, in the embodiment of the present invention, the server should filter the click information, and try to filter out the click information that is not the behavior of the user, so as to make the final count of clicks more accurate.

Please refer to Fig. 2. Based on the same inventive concept, the embodiment of the present invention provides another method for recording hits. The main flow of the method is as follows:

Step 201: When the client runs an application through a browser, obtain a client component, the client component is used to obtain click information for the application, the click information includes the address information of the client, and the click The information is obtained when clicking on the application.

When the client runs the application through a browser, it may request to obtain the client component.

Preferably, in the embodiment of the present invention, the client obtains the client component, which may specifically be: the client obtains the header and footer components or the IFrame (highly adaptive) component, and the client component is embedded in the in the header and footer components or the IFrame component.

Preferably, if it is a wap page, the client can obtain the header and footer components, and if it is a web page, the client can obtain the IFrame component.

In the embodiment of the present invention, corresponding improvements can be made to the header and footer components or the IFrame components, for example, corresponding codes can be implanted, that is, it can be regarded as the header and footer components or the IFrame The client component is embedded in the component.

Step 202: The client obtains M pieces of click information through the application component.

After obtaining the client component, the client may present the display interface corresponding to the application to the user, so that the user may perform some click operations on the display interface. The client may obtain the M pieces of click information through the client component.

In the embodiment of the present invention, M may be 1, that is, the client will report the click information to the server every time it obtains one click information.

Alternatively, in the embodiment of the present invention, M may be greater than 1, that is, the client reports the obtained click information to the server after obtaining multiple click information. For example, the client may report periodically, that is, report the click information obtained within a period to the server, or the client may report when triggered, or the client may report the click information when the application exits Report all the click information obtained at the time, which is not specifically limited in the present invention.

Preferably, the address information of the client may refer to the IP (Internet Protocol) address of the client, or may refer to the MAC (medium access control, medium access control) address of the client, or may refer to Other address information of the client.

Preferably, in the embodiment of the present invention, in addition to the address information of the client, the click information may also include user information corresponding to the user who made the click. For example, if M=2, the client has reported two click information in total, the first click information is generated by user 1 performing click operation 1, and the second click information is generated by user 2 performing click operation 2 , then the first click information may include the address information of the client and the user information of the user 1, and the second click information may include the address information of the client and the user 2 user information.

Step 203: the client sends the M pieces of click information to the server for storage.

After obtaining the M pieces of click information, the client may send the M pieces of click information to the server, and the server may save the M pieces of click information.

Preferably, the server may filter the M pieces of click information before saving them. The specific filtering and saving methods have been introduced in the embodiment in FIG. 1 , and will not be repeated here.

In the embodiment of the present invention, the client component is embedded in the header and footer components or the IFrame component, and the click information is obtained directly through the client component, which does not need to be displayed on the entire page as in the prior art. Embedding a plurality of JS codes to perform statistics separately is obviously simpler and easier than the solutions in the prior art, and is also more portable than the solutions in the prior art.

The method for recording hits in the embodiment of the present invention is generally introduced below through two specific embodiments.

Embodiment one:

Take the wap page as an example.

The user clicks a link on the application details page corresponding to an application displayed in the browser in the client.

After receiving the request from the user, the browser directs to the address of the application details page corresponding to the application.

The client requests to obtain header and footer components, wherein the client component has been embedded in the header and footer components.

The client obtains the header and footer components, and embeds the header and footer components into the application.

The client outputs the display interface corresponding to the application to the user.

When the display interface is loaded, the client component can start to obtain click information, that is, as long as there is a click operation on the display interface, the client component can obtain click information accordingly. For example, the client component may specifically execute an analytics() (an analysis function) method to obtain click information.

The client component sends the obtained click information to the server.

The server filters the received click information, and saves the click information remaining after filtering.

For example, the server can generate a click volume report according to the saved click information, and the click volume information can be obtained according to the click volume report, not only how many valid click volumes there are, but also the source data of each click information.

Embodiment two:

Take web pages as an example.

The user clicks a link on the application details page corresponding to an application displayed in the browser in the client.

After receiving the request from the user, the browser directs to the address of the application details page corresponding to the application.

The client requests to obtain an IFrame component, wherein the client component has been embedded in the IFrame component.

The client obtains the IFrame component, and embeds the IFrame component into the application.

The client outputs the display interface corresponding to the application to the user.

When the loading of the display interface is completed, the client component may execute heightAdapt() (a height adjustment function) to make the display interface adaptively displayed in the browser. This step is to enable the user to better view the display interface.

When the display interface is loaded, the client component can start to obtain click information, that is, as long as there is a click operation on the display interface, the client component can obtain click information accordingly. For example, the client component may specifically execute an analytics() (an analysis function) method to obtain click information.

The client component sends the obtained click information to the server.

The server filters the received click information, and saves the click information remaining after filtering.

For example, the server can generate a click volume report according to the saved click information, and the click volume information can be obtained according to the click volume report, not only how many valid click volumes there are, but also the source data of each click information.

Referring to FIG. 3 , based on the same inventive concept, an embodiment of the present invention provides a server, and the server may include a first acquiring module 301 and an operating module 302 .

The first obtaining module 301 can be used to obtain M pieces of click information for an application sent by the client, and the click information includes the address information of the client; The client component is installed in the browser of the client, the application is an application running in the browser, and M is a positive integer.

The operation module 302 may be configured to save the M pieces of click information.

Preferably, in the embodiment of the present invention, the click information further includes user information corresponding to the user who clicked.

Preferably, in the embodiment of the present invention, the operation module 302 can be specifically configured to filter and save the M pieces of click information according to preset rules.

Preferably, in the embodiment of the present invention, the operation module 302 can be specifically configured to: match each of the M pieces of click information with preset N click information templates, and the click information templates are non-user The information template corresponding to the click information of the behavior; wherein, each click information template corresponds to a click information of a non-user behavior, and N is a positive integer; the click information that matches successfully is discarded.

Referring to FIG. 4 , based on the same inventive concept, an embodiment of the present invention provides a client, and the client may include a second obtaining module 401 , a third obtaining module 402 and a sending module 403 .

The second obtaining module 401 may be used to obtain a client component when running an application through a browser, the client component is used to obtain click information for the application, the click information includes address information of the client, The click information is obtained when a click operation is performed on the application.

The third obtaining module 402 may be configured to obtain M pieces of click information through the application component.

The sending module 403 may be configured to send the M pieces of click information to the server for storage.

Preferably, in the embodiment of the present invention, the second obtaining module 401 can be specifically used to: obtain a page header and footer component or a highly adaptive IFrame component, and the client component is embedded in the page header and footer component or the in the IFrame component.

Preferably, in the embodiment of the present invention, the click information further includes user information corresponding to the user who clicked.

The method for recording clicks in the embodiment of the present invention may include: the server obtains M pieces of click information for an application sent by the client, and the click information includes the address information of the client; wherein, the click information is obtained through the The client component installed in the client is obtained, the client component is installed in the browser of the client, the application is an application running in the browser, M is a positive integer; the server will The M pieces of click information are saved.

In the embodiment of the present invention, the server may save the M click information after obtaining the M click information, and the click information includes the address information of the client, so that each click corresponds to The information is recorded, the source of the data can be traced, the abnormal data can be easily located, and even the data can be fine-tuned. Moreover, the click information is obtained through the client component installed in the browser, that is, in the embodiment of the present invention, the click information is obtained through the client component, and there is no need to modify the application, so The client component described above can be installed in the browser, has strong portability and versatility, and has a relatively wide range of applications.

Those skilled in the art can clearly understand that for the convenience and brevity of description, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional modules according to needs. The internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the above-described system, device, and unit, reference may be made to the corresponding process in the foregoing method embodiments, and details are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be Incorporation may either be integrated into another system, or some features may be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk, and other media that can store program codes. .

As mentioned above, the above embodiments are only used to introduce the technical solutions of the present application in detail, but the descriptions of the above embodiments are only used to help understand the method and core idea of the present invention, and should not be construed as limiting the present invention. Any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention shall fall within the protection scope of the present invention.

Claims (8)

1. A method for recording hits, characterized in that, comprising: The server obtains M pieces of click information for an application sent by the client, and the click information includes the address information of the client; wherein, the click information is obtained through a client component installed in the client, and The client component is installed in the browser of the client, the application is an application running in the browser, and M is a positive integer; the server filters the M click information according to preset rules save; Wherein, the server filtering the M pieces of click information according to preset rules includes: the server matching each of the M pieces of click information with preset N click information templates, the The click information template is the information template corresponding to the click information of non-user behavior; wherein, each click information template corresponds to a kind of click information of non-user behavior, and N is a positive integer; the server discards the click information that matches successfully. 2. The method according to claim 1, wherein the click information further includes user information corresponding to the user who clicked. 3. A method for recording hits, comprising: When the client runs an application through the browser, the client component is obtained, and the client component is used to obtain click information for the application, the click information includes the address information of the client, and the click information is for the Obtained when the application performs a click operation; wherein, the client obtains client components, including the client obtaining header and footer components or a highly adaptive IFrame component, and the client component is embedded in the header in the footer component or the IFrame component; The client obtains M click information through the application component; The client sends the M pieces of click information to the server for storage. 4. The method according to claim 3, wherein the click information further includes user information corresponding to the user who clicked. 5. A server, characterized in that, comprising: The first obtaining module is used to obtain M pieces of click information for an application sent by the client, and the click information includes the address information of the client; terminal component, the client component is installed in the browser of the client, the application is an application running in the browser, M is a positive integer; the operation module is used to convert the The above M click information is filtered and saved; Wherein, the operation module is specifically configured to: match each of the M pieces of click information with preset N click information templates, and the click information templates are information templates corresponding to click information of non-user behaviors ; Wherein, each click information template corresponds to a click information of a non-user behavior, and N is a positive integer; the click information that matches successfully is discarded. 6. The server according to claim 5, wherein the click information further includes user information corresponding to the user who clicked. 7. A client, characterized in that, comprising: The second acquisition module is configured to obtain a client component when running an application through a browser, the client component is used to obtain click information for the application, the click information includes address information of the client, and The click information is obtained when a click operation is performed on the application; wherein, the second acquisition module is specifically used to obtain a page header and footer component or a highly adaptive IFrame component, and the client component is embedded in the page header in the footer component or the IFrame component; The third obtaining module is used to obtain M pieces of click information through the application component; A sending module, configured to send the M pieces of click information to a server for storage. 8. The client according to claim 7, wherein the click information further includes user information corresponding to the user who clicked.