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 system comprising:
one or more computer processors;
one or more computer memories; and
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:
accessing a data set from a buffer on a client device, the data set representing one or more signals of the client device, the client device including a collection module, an orchestrator module, the buffer, and a tracking plan monitor, the collection module capturing one or more user actions and passing the one or more user actions to the buffer as the one or more signals of the client device;
qualifying, using the tracking plan monitor, the one or more signals as one or more events, the qualifying including passing the one or more signals through a filter logic, the filter logic being configured to qualify the one or more signals as the one or more events based on a value or relevancy of one or more data points included in the one or more signals, the filter logic having been developed outside of a client application of the client device and loaded into the client application without rebuilding the client application, the orchestrator module keeping the client device in synchronization with a developer console for a latest version of the filter logic; and
passing the one or more events through a chain of middleware built into an analytics library to enrich the one or more events, each middleware in the chain of middleware including a function runtime, the function runtime providing an operating environment in which an edge function is implemented within each middleware.
2. The system of claim 1 , wherein the filter logic is deployed to the client application over-the-air.
3. The system of claim 1 , wherein the filter logic is deployed to the client application in real time.
4. The system of claim 1 , wherein the one or more signals are passed through a plurality of filter logic, the plurality of filter logic having been developed outside of the client application of the client device and loaded into the client application without rebuilding the client application, and wherein the plurality of filter logic are written in a single language and the client application includes infrastructure that ensures the plurality of filter logic are executable independently of a platform of the client device.
5. The system of claim 1 , the operations further comprising:
fetching the filter logic upon loading of the client application.
6. The system of claim 5 , wherein the fetching of the filter logic is based on release data associated with the filter logic.
7. The system of claim 6 , wherein the release data is used to verify whether the filter logic is a latest versions.
8. A method comprising:
accessing a data set from a buffer on a client device, the data set representing one or more signals of the client device, the client device including a collection module, an orchestrator module, the buffer, and a tracking plan monitor, the collection module capturing one or more user actions and passing the one or more user actions to the buffer as the one or more signals of the client device;
qualifying, using the tracking plan monitor, the one or more signals as one or more events, the qualifying including passing the one or more signals through a filter logic, the filter logic being configured to qualify the one or more signals as the one or more events based on a value or relevancy of one or more data points included in the one or more signals, the filter logic having been developed outside of a client application of the client device and loaded into the client application without rebuilding the client application, the orchestrator module keeping the client device in synchronization with a developer console for a latest version of the filter logic; and
passing the one or more events through a chain of middleware built into an analytics library to enrich the one or more events, each middleware in the chain of middleware including a function runtime, the function runtime providing an operating environment in which an edge function is implemented within each middleware.
9. The method of claim 8 , wherein the filter logic is deployed to the client application over-the-air.
10. The method of claim 8 , wherein the filter logic is deployed to the client application in real time.
11. The method of claim 8 , wherein the one or more signals are passed through a plurality of filter logic, the plurality of filter logic having been developed outside of the client application of the client device and loaded into the client application without rebuilding the client application, and wherein the plurality of filter logic are written in a single language and the client application includes infrastructure that ensures the plurality of filter logic are executable independently of a platform of the client device.
12. The method of claim 8 , further comprising:
fetching the filter logic upon loading of the client application.
13. The method of claim 12 , wherein the fetching of the filter logic is based on release data associated with the filter logic.
14. The method of claim 13 , wherein the release data is used to verify whether the filter logic is a latest versions.
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 processor to perform operations, the operations comprising:
accessing a data set from a buffer on a client device, the data set representing one or more signals of the client device, the client device including a collection module, an orchestrator module, the buffer, and a tracking plan monitor, the collection module capturing one or more user actions and passing the one or more user actions to the buffer as the one or more signals of the client device;
qualifying, using the tracking plan monitor, the one or more signals as one or more events, the qualifying including passing the one or more signals through a filter logic, the filter logic being configured to qualify the one or more signals as the one or more events based on a value or relevancy of one or more data points included in the one or more signals, the filter logic having been developed outside of a client application of the client device and loaded into the client application without rebuilding the client application, the orchestrator module keeping the client device in synchronization with a developer console for a latest version of the filter logic; and
passing the one or more events through a chain of middleware built into an analytics library to enrich the one or more events, each middleware in the chain of middleware including a function runtime, the function runtime providing an operating environment in which an edge function is implemented within each middleware.
16. The non-transitory computer-readable storage medium of claim 15 , wherein the filter logic is deployed to the client application over-the-air.
17. The non-transitory computer-readable storage medium of claim 15 , wherein the filter logic is deployed to the client application in real time.
18. The non-transitory computer-readable storage medium of claim 15 , wherein the one or more signals are passed through a plurality of filter logic, the plurality of filter logic having been developed outside of the client application of the client device and loaded into the client application without rebuilding the client application, and wherein the plurality of filter logic are written in a single language and the client application includes infrastructure that ensures the plurality of filter logic are executable independently of a platform of the client device.
19. The non-transitory computer-readable storage medium of claim 15 , the operations further comprising:
fetching the filter logic upon loading of the client application.
20. The non-transitory computer-readable storage medium of claim 19 , wherein the fetching of the filter logic is based on release data associated with the filter logic.