Systems and methods for tracking events of a client device

1. A method for tracking events of a client device, the method comprising:

receiving, at the client device from a server, a configuration file that includes a tracking script, wherein the tracking script provides instructions for the client device and includes a tracking rule that designates one or more events to be tracked, and the tracking rule is configured at the server by a server-side user;

tracking events of the client device as instructed by the tracking script;

analyzing tracked events tracked as instructed by the tracking script; and

upon occurrence of one or more analytical results corresponding to requirements indicated by the tracking script, sending tracking information to an analytics collection engine, wherein the tracking information at least includes some of the one or more analytical results;

checking whether there is an update for the configuration file;

upon occurrence of the update, loading and updating the configuration file to generate an updated configuration file, the updated configuration file including an updated tracking rule configured by the server-side user at the server.

2. The method of claim 1 , wherein the events include user interactions with an object displayed on the client device.

3. The method of claim 1 , wherein the tracking events of the client device as instructed by the tracking script includes:

tracking the events of the client device based on the tracking rule specified by the tracking script, the tracking rule associates with a data name and a data type related to each of the events.

4. The method of claim 3 , wherein the data name corresponds to an input field embedded in a page of an application at the client device.

5. The method of claim 3 , wherein the data type corresponds to an input field embedded in a page of an application at the client device.

6. The method of claim 1 , wherein the analyzing tracked events tracked as instructed by the tracking script includes:

determining a first data name of a first input field associated with a first user interaction;

determining whether the first data name satisfies the tracking rule; and

tracking an event associated with the first user interaction if the first data name satisfies the tracking rule.

7. The method of claim 1 , wherein the analyzing tracked events tracked as instructed by the tracking script includes:

obtaining input data of a second input field associated with a second user interaction;

determining a second data type of the second input field based on the input data;

determining whether the second data type satisfies the tracking rule; and

tracking an event associated with the second user interaction if the second data type satisfies the tracking rule.

8. The method of claim 1 , wherein the analyzing tracked events tracked as instructed by the tracking script includes:

recording data associated with the tracked events; and

determining statistical data using at least some of the recorded data.

9. The method of claim 1 , further comprising:

identifying, by the analytics collection engine, user identification based on the sent tracking information.

10. The method of claim 1 , wherein the tracking script indicates a preset order of the tracked events,

and upon occurrence of one or more analytical results corresponding to requirements indicated by the tracking script, sending tracking information to an analytics collection engine comprises:

determining whether an order of the tracked events satisfies the preset order; and

in response to determining that the order of the tracked events satisfies the preset order, generating the tracking information that includes a positive result indicating that the order of the tracked events satisfies the requirements indicated by the tracking script.

11. The method of claim 1 , further comprising:

determining, by the analytics collection engine, user login information of a client-side user of the client device based on the sent tracking information;

determining whether the user login information is abnormal; and

in response to determining that the user login information is abnormal, transmitting an alert to the client device.

12. The method of claim 1 , wherein the configuration file is a Software Development Kit (SDK).

13. A system for tracking events of a client device, the system comprising:

at least one storage device including one or more sets of instructions;

at least one processor in communication with the at least one storage device, wherein when executing the one or more sets of instructions, the at least one processor is directed to:

receive, at the client device from a server, a configuration file that includes a tracking script, wherein the tracking script provides instructions for the client device and includes a tracking rule that designates one or more events to be tracked, and the tracking rule is configured at the server by a server-side user;

track events of the client device as instructed by the tracking script;

analyze tracked events tracked as instructed by the tracking script;

upon occurrence of one or more analytical results corresponding to requirements indicated by the tracking script, send tracking information to an analytics collection engine, wherein the tracking information at least includes some of the one or more analytical results;

check whether there is an update for the configuration file;

upon occurrence of the update, load and update the configuration file to generate an updated configuration file, the updated configuration file including an updated tracking rule configured by the server-side user at the server.

14. The system of claim 13 , wherein the events include user interactions with an object displayed on the client device.

15. The system of claim 13 , wherein to track events of the client device as instructed by the tracking script, the at least one processor is directed to:

track the events of the client device based on the tracking rule specified by the tracking script, the tracking rule associates with a data name and a data type related to each of the events.

16. The system of claim 13 , wherein to analyze tracked events tracked as instructed by the tracking script, the at least one processor is directed to:

determine a first data name of a first input field associated with a first user interaction;

determine whether the first data name satisfies the tracking rule; and

track an event associated with the first user interaction if the first data name satisfies the tracking rule.

17. The system of claim 13 , wherein to analyze tracked events tracked as instructed by the tracking script, the at least one processor is directed to:

obtain input data of a second input field associated with a second user interaction;

determine a second data type of the second input field based on the input data;

determine whether the second data type satisfies the tracking rule; and

track an event associated with the second user interaction if the second data type satisfies the tracking rule.

18. The system of claim 13 , wherein to analyze tracked events tracked as instructed by the tracking script, the at least one processor is directed to:

record data associated with the tracked events; and

determine statistical data using at least some of the recorded data.

19. A non-transitory computer readable medium, comprising at least one set of instructions for tracking events of a client device, wherein when executed by at least one processor of a computing device, the at least one set of instructions causes the computing device to perform a method, the method comprising:

receiving, at the client device from a server, a configuration file that includes a tracking script, wherein the tracking script provides instructions for the client device and includes a tracking rule that designates one or more events to be tracked, and the tracking rule is configured at the server by a server-side user;

tracking events of the client device as instructed by the tracking script;

analyzing tracked events tracked as instructed by the tracking script; and

upon occurrence of one or more analytical results corresponding to requirements indicated by the tracking script, sending tracking information to an analytics collection engine, wherein the tracking information at least includes some of the one or more analytical results;

checking whether there is an update for the configuration file;

upon occurrence of the update, loading and updating the configuration file to generate an updated configuration file, the updated configuration file including an updated tracking rule configured by the server-side user at the server.