User tracking in a Web session spanning multiple Web resources without need to modify user-side hardware or software or to store cookies at user-side hardware

• US 20020078191A1
• Filed: 12/20/2000
• Published: 06/20/2002
• Est. Priority Date: 12/20/2000
• Status: Abandoned Application

• Current Assignee: Markado, Inc.
• Original Assignee: Markado, Inc.
• Inventors: Lorenz, Todd
• Application Number:
  US09/742,849
• Publication Number:
  US 20020078191A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A tracking system tracks user interaction with Web resources over the Internet and maintains continuity as the user changes hosts during the Web session, without relying on cookies. An entry point activated by the user, such as a loaded link in an email, routs a request for a Web resource to a gateway facility different from the host of the Web resource. The gateway facility processes the request, modifies is as needed, keeps tracking information, and sends the modified request to the server that actually hosts the Web resource the user sought. The response to the modified request goes to the gateway facility, which modifies it as needed, keeps tracking information, and then sends it to the user, with loaded links that point back to the gateway facility to thereby

Claims

1. A method of tracking a user'"'"'s transactions with multiple Web resources and hosts in a Web session without a need to modify user-side hardware or software or to store cookies at user-side hardware, comprising:

utilizing an entry point related to an action of the user during the Web session to route a user'"'"'s request for a Web resource to a gateway facility;

extracting session parameters from information available to the gateway facility as a consequence of said routing; and

tracking transactions that the user routed to the gateway server carries out with multiple Web resources and hosts in the Web session.

2. A method as in claim 1 in which said tracking comprises routing transactions between the user and said multiple Web resources and hosts through said gateway facility.

3. A method as in claim 2 in which said tracking further comprises modifying information transmitted at least in one direction between the user and said multiple Web resources at a location functionally intermediate the user and the Web resources.

4. A method as in claim 3 in which said modifying comprises modifying information transmitted in each direction between the user and the multiple Web resources.

5. A method as in claim 4 in which said modifying comprises modifying hyperlinks in information transmitted from said multiple Web resources to the user to cause the modified hyperlinks to point to the gateway server.

6. A method as in claim 5 in which said modifying comprises modifying information in addition to hyperlinks in information transmitted from said multiple Web resources to the user.

7. A method as in claim 6 in which said modifying comprises modifying URL information transmitted from the user and sending the modified URL information to at least one of said multiple Web resources.

8. A method as in claim 7 in which said modifying comprises consulting an agenda of rules relating information directed to the gateway facility and information sent from the gateway server to at least one of the user and the multiple Web resources.

9. A method as in claim 8 in which said modifying comprises modifications in accordance with instructions contained in said agenda.

10. A method as in claim 1 in which said entry point comprises a loaded link selected by the user in a Web session.

11. A method as in claim 10 in which said loaded link is in an email message to the user.

12. A method as in claim 10 in which said loaded link is in a Web page transmitted to the user.

13. A method as in claim 1 in which said extracting comprises filling in gaps in the extracted parameters.

14. A method as in claim 1 in which said tracking comprises selectively modifying information transmitted between the user and the multiple Web resources in accordance with instructions stored for use by the gateway facility.

16. A method as in claim 15, further including repeating steps (b) and (c) for the request for said another Web resource.

17. A method as in claim 15 in which said modifying comprises modifying URL information contained in said response.

18. A method as in claim 17 in which said modifying further includes modifying information in said responses different from URL information.

19. A method as in claim 15 in which said steps (b) and (c) are repeated for a number of requests made by the user for Web resources from a number of different Web servers.

20. A method as in claim 15 in which said modifying of requests includes filling gaps in said requests before sending modified requests from said gateway facility. before sending.

15. A method of tracking a user through multiple Web resources and hosts in a Web session comprising:

(a) receiving at a gateway facility information resulting from a user activating, in said Web session, an entry point related to a request by the user for a Web resource from a server different from the gateway facility;

(b) extracting session parameters from said request, modifying the request in accordance with an agenda, and sending the modified request to the Web resource, said modified request pointing to the gateway facility;

(c) receiving a response to the modified request at the gateway facility, modifying the received response in accordance with said agenda, and sending the modified response to the user, said modified response containing an entry point to the gateway facility in a request for another Web resource;

(d) receiving at the gateway facility a request for said another Web resource resulting from the user activating, in said Web session, the entry point in the modified response; and

(e) creating a record of user actions related to the entry points recited in steps (a) and (d).

21. A system for tracking a user'"'"'s transactions with multiple Web resources in a Web session without a need to modify user-side hardware or software or to store cookies at user-side hardware, comprising:

a gateway facility functionally intermediate a user-side hardware and software and Web resources stored at resource facilities different from the gateway facility;

said gateway facility being configured to respond to a user'"'"'s request routed thereto as a result of the user activating an entry point in a Web session to extract session parameters from the request, modify the request to cause a response thereto to be routed to the gateway facility, and to send the request to a resource facility;

said gateway receiver further being configured to receive a response from said resource facility to the modified request, to modify the response to include an entry point in a request for another Web resource, and the send the modified response to the user;

said gateway facility being responsive to the user activating said entry points to create and maintain a record of user actions related to activation of said entry points.

22. An Internet method comprising:

sending information to a user side computer facility, said information containing a loaded link containing address information pointing to a Web resource and to a gateway facility;

responding to a user activation of the loaded link to send at least a portion of said address information to the gateway facility;

processing the transmitted information to produce and send a request for the Web resource to a first server facility different from the user side facility and from the gateway facility;

responding to the request sent from the gateway facility by sending the Web resource from said server to the gateway facility, modifying the Web resource by modifying links therein to point the gateway facility, and sending the modified response to the user side facility;

In response to user activation of a modified links, receiving information related to the modified link at said gateway facility, processing the received information, and transmitting the resulting processed information to a second server facility different from the user side facility and from the gateway facility; and

using the gateway facility to create and maintain a record at least of user interaction with said links.