Delivery of instructions in host applications

Patent metadata

Field	Value
Publication number	US-10951687-B2
Application number	US-201916585735-A
Country	US
Kind code	B2
Filing date	Sep 27, 2019
Priority date	Dec 5, 2014
Publication date	Mar 16, 2021
Grant date	Mar 16, 2021

Abstract

Embodiments of the systems described herein can implement one or more processes remotely delivering customized code to a host application and/or computing device. The host application may be configured as an Application Programming Interface with a customized code processing library that may configure the host application to receive further instructions remotely. The host application may be further configured to execute host code and/or third-party code. The host application may be configured to receive remote application logic, after the host application has been installed on a computing device, and to execute the received application logic to alter the behavior of the host application, such as selectively tracking end user interactions.

First claim

What is claimed:

1. A method comprising:
executing a host application comprising a first tag library, the first tag library configured to track interaction data indicative of end user interactions with a physical user computing device;
sending a request to a first remote network server;
receiving, from the first remote network server, a response to the request, the response comprising a token;
sending the token to a second remote network server;
receiving, from the second remote network server, a second tag library comprising application logic, wherein the application logic comprises the token;
executing the host application to generate an event indicating a user interaction with the physical user computing device;
loading, in the host application, the application logic comprising a set of instructions;
determining, using the application logic, to track the event; and
executing the set of instructions specified by the application logic to cause the physical user computing device to transmit first data associated with the event, wherein the first data comprises the token.

2. The method of claim 1 , further comprising:
executing the host application to generate a second event indicating a second user interaction type associated with the physical user computing device; and
determining, using the application logic, to ignore the second event.

3. The method of claim 2 , further comprising:
receiving, from the second remote network server, a third tag library comprising updated application logic;
executing the host application to generate a third event indicating the second user interaction type; and
determining, using the updated application logic, to track the third event.

4. The method of claim 2 , wherein the second user interaction type associated with the physical user computing comprises at least one of a selection type, a text input type, a login type, or a navigation type.

5. The method of claim 3 , further comprising:
requesting the third tag library from the second remote network server.

6. The method of claim 1 , wherein the first tag library is loadable by a browser application which is different from the host application.

7. The method of claim 1 , wherein the token comprises a device identifier.

8. Non-transitory physical computer storage comprising instructions stored thereon for implementing, in one or more computer hardware processors, a method comprising:
executing a host application comprising a first tag library, the first tag library configured to track interaction data indicative of end user interactions with a physical user computing device;
sending a request to a first remote network server;
receiving, from the first remote network server, a response to the request, the response comprising a token;
sending the token to a second remote network server;
receiving, from the second remote network server, a second tag library comprising application logic, wherein the application logic comprises the token;
executing the host application to generate an event indicating a user interaction with the physical user computing device;
loading, in the host application, the application logic comprising a set of instructions;
determining, using the application logic, to track the event; and
executing the set of instructions specified by the application logic to cause the physical user computing device to transmit first data associated with the event, wherein the first data comprises the token.

9. The non-transitory physical computer storage of claim 8 , wherein the method further comprises:
executing the host application to generate a second event indicating a second user interaction type associated with the physical user computing device; and
determining, using the application logic, to ignore the second event.

10. The non-transitory physical computer storage of claim 9 , wherein the method further comprises:
receiving, from the second remote network server, a third tag library comprising updated application logic;
executing the host application to generate a third event indicating the second user interaction type; and
determining, using the updated application logic, to track the third event.

11. The non-transitory physical computer storage of claim 9 , wherein the second user interaction type associated with the physical user computing comprises at least one of a selection type, a text input type, a login type, or a navigation type.

12. The non-transitory physical computer storage of claim 10 , wherein the method further comprises:
requesting the third tag library from the second remote network server.

13. The non-transitory physical computer storage of claim 8 , wherein the token comprises a device identifier.

14. A system comprising:
non-transitory physical computer storage configured to store a host application comprising a first tag library, the first tag library configured to track interaction data indicative of end user interactions with a physical user computing device; and
a computer hardware processor in the physical user computing device, the computer hardware processor being in communication with the non-transitory physical computer storage and configured to:
execute the host application;
send a request to a first remote network server;
receive, from the first remote network server, a response to the request, the response comprising a token;
send the token to a second remote network server;
receive, from the second remote network server, a second tag library comprising application logic, wherein the application logic comprises the token;
execute the host application to generate an event indicating a user interaction with the physical user computing device;
load, in the host application, the application logic comprising a set of instructions;
determine, using the application logic, to track the event; and
execute the set of instructions specified by the application logic to cause the physical user computing device to transmit first data associated with the event, wherein the first data comprises the token.

15. The system of claim 14 , wherein the computer hardware processor is further configured to:
execute the host application to generate a second event indicating a second user interaction type associated with the physical user computing device; and
determine, using the application logic, to ignore the second event.

16. The system of claim 15 , wherein the computer hardware processor is further configured to:
receive, from the second remote network server, a third tag library comprising updated application logic;
execute the host application to generate a third event indicating the second user interaction type; and
determine, using the updated application logic, to track the third event.

17. The system of claim 15 , wherein the second user interaction type associated with the physical user computing device comprises at least one of a selection type, a text input type, a login type, or a navigation type.

18. The system of claim 16 , wherein the computer hardware processor is further configured to:
request the third tag library from the second remote network server.

19. The system of claim 14 , wherein the first tag library is loadable by a browser application which is different from the host application.

20. The system of claim 14 , wherein the token comprises a device identifier.

Assignees

• Tealium Inc

Inventors

• Mcwilliams Patrick
• Koo Jason Lap-Wing
• Hartman Chad Major
• Webster Iv George Thomas
• Hoang Son Phi

Classifications

• G06F9/542 Primary

  Event management; Broadcasting; Multicasting; Notifications · CPC title

• H04L67/10 Primary

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L67/535

  Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34) · CPC title

• H04L67/01

  Protocols · CPC title

• H04L67/34

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title