Client-side enrichment and transformation via dynamic logic for analytics
Described are systems and methods for client side enrichment and transform via dynamic logic for analytics across various platforms for improved performance, features, and uses. Analytics data collected in client applications is transformed and enriched before being sent to the downstream pipeline using native code and logic bundled into the core application code. The additional logic specific to manipulation of analytics may be unbundled from client-side application code and still be executed on on-device to achieve the same result. The logic may be written in a single language, such as JavaScript, and run across all clients including web browser and mobile operating systems.
1. A computer system comprising:
one or more computer processors;
one or more computer memories;
a set of instructions incorporated into the one or more computer memories, the set of instructions configuring the one or more computer processors to perform operations, the operations comprising:
receiving a sample signal from an instance of a client application deployed on a client device, the client device including an orchestrator module, a sampler, a client-side buffer, and a function runtime;
passing the sample signal to a sample buffer in a server-side developer console via the sampler in the client device, the sampler being configured to generate one or more filter functions based on content of the sample signal;
feeding the sample signal from the sample buffer to a debugger in a client-side developer console, the debugger including an interface to test custom code associated with the one or more filter functions generated by the sampler against the sample signal;
in response to testing the custom code against the sample signal, storing the tested custom code associated with the one or more filter functions in a code cache in the server-side developer console; and
fetching, using the orchestrator module in the client device, the one or more filter functions; and
executing, using the function runtime in the client device, the one or more filter functions based on a condition associated with the client-side buffer.
2. The system of claim 1 , wherein personally-identifiable information is stripped from the sample signal using a differentially private algorithm.
3. The system of claim 1 , wherein testing the custom code against the sample signal is configured to ensure that the one or more filter functions meet one or more predefined performance and/or security benchmarks, wherein the client application is kept in synchronization with the server-side developer console to ensure that a latest version of the one or more filter functions stored in the code cache is available for deployment by the orchestrator module.
4. The system of claim 1 , wherein the receiving is triggered at a fixed interval or by a request to fetch the sample signal.
5. The system of claim 4 , wherein the request to fetch the sample signal is based on a determination to identify one or more additional events from the sample signal.
6. The system of claim 1 , wherein each of the one or more filter functions is configured to run as either a source or a destination edge function.
7. The system of claim 1 , wherein the one or more filter functions are created in a separate coding environment and pushed to the server-side developer console via an application programming interface (API).
8. A method comprising:
receiving a sample signal from an instance of a client application deployed on a client device, the client device including an orchestrator module, a sampler, a client-side buffer, and a function runtime;
passing the sample signal to a sample buffer in a server-side developer console via the sampler in the client device, the sampler being configured to generate one or more filter functions based on content of the sample signal;
feeding the sample signal from the sample buffer to a debugger in a client-side developer console, the debugger including an interface to test custom code associated with the one or more filter functions generated by the sampler against the sample signal;
in response to testing the custom code against the sample signal, storing the tested custom code associated with the one or more filter functions in a code cache in the server-side developer console; and
fetching, using the orchestrator module in the client device, the one or more filter functions; and
executing, using the function runtime in the client device, the one or more filter functions based on a condition associated with the client-side buffer.
9. The method of claim 8 , wherein personally-identifiable information is stripped from the sample signal using a differentially private algorithm.
10. The method of claim 8 , wherein testing the custom code against the sample signal is configured to ensure that the one or more filter functions meet one or more predefined performance and/or security benchmarks, wherein the client application is kept in synchronization with the server-side developer console to ensure that a latest version of the one or more filter functions stored in the code cache is available for deployment by the orchestrator module.
11. The method of claim 8 , wherein the receiving is triggered at a fixed interval or by a request to fetch the sample signal.
12. The method of claim 11 , wherein the request to fetch the sample signal is based on a determination to identify one or more additional events from the sample signal.
13. The method of claim 8 , wherein each of the one or more filter functions is configured to run as either a source or a destination edge function.
14. The method of claim 8 , wherein the one or more filter functions are created in a separate coding environment and pushed to the server-side developer console via an application programming interface (API).
15. A non-transitory computer-readable storage medium storing a set of instructions that, when executed by one or more computer processors, causes the one or more computer processors to perform operations, the operations comprising:
receiving a sample signal from an instance of a client application deployed on a client device, the client device including an orchestrator module, a sampler, a client-side buffer, and a function runtime;
passing the sample signal to a sample buffer in a server-side developer console via the sampler in the client device, the sampler being configured to generate one or more filter functions based on content of the sample signal;
feeding the sample signal from the sample buffer to a debugger in a client-side developer console, the debugger including an interface to test custom code associated with the one or more filter functions generated by the sampler against the sample signal;
in response to testing the custom code against the sample signal, storing the tested custom code associated with the one or more filter functions in a code cache in the server-side developer console; and
fetching, using the orchestrator module in the client device, the one or more filter functions; and
executing, using the function runtime in the client device, the one or more filter functions based on a condition associated with the client-side buffer.
16. The non-transitory computer-readable storage medium of claim 15 , wherein personally-identifiable information is stripped from the sample signal using a differentially private algorithm.
17. The non-transitory computer-readable storage medium of claim 15 , wherein testing the custom code against the sample signal is configured to ensure that the one or more filter functions meet one or more predefined performance and/or security benchmarks, wherein the client application is kept in synchronization with the server-side developer console to ensure that a latest version of the one or more filter functions stored in the code cache is available for deployment by the orchestrator module.
18. The non-transitory computer-readable storage medium of claim 15 , wherein the receiving is triggered at a fixed interval or by a request to fetch the sample signal.
19. The non-transitory computer-readable storage medium of claim 18 , wherein the request to fetch the sample signal is based on a determination to identify one or more additional events from the sample signal.
20. The non-transitory computer-readable storage medium of claim 15 , wherein each of the one or more filter functions is configured to run as either a source or a destination edge function.