Web browser tracking

• US 9,794,357 B2
• Filed: 10/23/2013
• Issued: 10/17/2017
• Est. Priority Date: 10/23/2013
• Status: Active Grant

• Current Assignee: Cision US Inc. (Cision Ltd.)
• Original Assignee: Cision US Inc. (Cision Ltd.)
• Inventors: Fluehr, Timothy Michael, Heys, Mark James
• Primary Examiner(s): Sison, June
• Assistant Examiner(s): Cooney, Adam
• Application Number:
  US14/061,489
• Publication Number:
  US 20150113126A1
• Time in Patent Office: 1,455 Days
• Field of Search: 709224
• CPC Class Codes: G06F 11/006 Identification G06F11/2289 takes precedence
• CPC Class Codes: G06F 11/3438 monitoring of user actions tracking the activity of the user H04L67/535
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/83 the solution involving signatures
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

A technique for tracking web browsing activity of a client device that includes storing, in a memory, a client profile having a client identifier associated therewith, providing a client device with a cache file having the client identifier embedded therein, receiving from the client device an identification of a client action and the client identifier, and updating the client profile to include the identification of the client action.

Claims

1. In a tracking server, a method for tracking web browsing activity of a client device accessing a vendor server, comprising:

receiving a request for tracking software from the client device, the request for the tracking software being prompted by software sent to the client device by the vendor server;

transmitting the tracking software to the client device, wherein the tracking software is configured to execute upon receipt by the client device and prompt the client device to determine whether the client device has stored therein a particular web cache file, and to request the creation of a new web cache file from the tracking server when the client device does not have the web cache file stored therein;

receiving a request for the new web cache file from the client device;

establishing a client identifier associated with the client device;

storing, in a memory of the tracking server, a client profile associated with the client identifier;

embedding the client identifier in a body of the new web cache file;

transmitting the new web cache file to the client device;

receiving the client identifier and an identification of a client action from the client device; and

updating the client profile to include the identification of the client action.

2. The method as recited in claim 1, wherein the vendor server is associated with a vendor, the method further comprising:

receiving, with the client identifier and the identification of the client action, a vendor identifier associated with the vendor;

updating the client profile to include the vendor identifier; and

transmitting the identification of the client action to the vendor.

3. The method as recited in claim 2, wherein the vendor identifier comprises a globally unique identifier (GUID).

4. The method as recited in claim 1, wherein the client identifier is a new client identifier, and wherein the method further comprises:

receiving a backup client identifier with the new client identifier and the identification of the client action from the client device;

comparing the backup client identifier with the new client identifier; and

linking a client profile associated with the backup client identifier with the client profile associated with the new client identifier, when the backup client identifier and the new client identifier are determined to be different.

5. The method as recited in claim 1, wherein the client identifier comprises a globally unique identifier (GUID).

6. The method as recited in claim 1, wherein the client profile further includes one or more of the client identifier, a vendor identifier, a referring URL, a date of the client action, or a time of the client action.

7. The method as recited in claim 1, wherein the client action comprises the accessing of a web page.

8. The method as recited in claim 1, wherein the client action comprises the hovering of a cursor over an object on a web page.

9. The method as recited in claim 1, wherein the client action comprises the downloading of a file.

10. The method as recited in claim 1, wherein updating the client profile to include the identification of the client action comprises storing, in the memory, the identification of the client action, into the client profile associated with the extracted client identifier.

11. The method as recited in claim 1, wherein the tracking software is configured to create a backup of the client identifier after receiving the web cache file from the tracking server.

12. A system for tracking web browsing activity, comprising:

a client device having a web browser running thereon and a client storage device for storing for the web browser a web cache file having embedded therein a fingerprint unique to the client device, the client device configured to;

determine whether the web cache is currently stored in the client storage device; and

request a new web cache file from the tracking server when the web cache file is not stored in the client storage device; and

the tracking server, communicatively coupled with the client device and comprising;

a tracking server storage device for storing a plurality of client profiles, each of the client profiles having associated therewith a unique fingerprint and descriptions of zero or more client actions,

the tracking server configured to;

create a new client profile and the fingerprint for the client device and embed the fingerprint in a body of the new web cache file in response to the request for the new web cache file; and

transmit the new web cache file to the client device,

wherein the client device is configured to transmit the fingerprint and an identification of a client action to the tracking server, and

wherein the tracking server is configured to update the client profile to include the identification of the client action.

13. The system as recited in claim 12, wherein after the client device receives the new web cache file containing the embedded fingerprint from the tracking server, the client device is configured to create a new backup of the fingerprint.

14. The system as recited in claim 13, wherein the new backup of the fingerprint is embedded in a cookie stored in the client storage device.

15. The system as recited in claim 12,

wherein the client device is configured to:

determine if the client storage device has stored therein an old backup of a fingerprint; and

transmit the old backup of the fingerprint to the tracking server together with the fingerprint from the new web cache file and the identification of the client action, and

wherein the tracking server is configured to;

compare the old backup of the fingerprint and the fingerprint from the new web cache file; and

link the client profile associated with the old backup of the fingerprint to the client profile associated with the fingerprint from the new web cache file when the old backup of the fingerprint and the fingerprint from the new web cache file are the same.