TRACKING WEB SERVER

• US 20140164613A1
• Filed: 02/14/2014
• Published: 06/12/2014
• Est. Priority Date: 02/09/2007
• Status: Active Grant

• Current Assignee: Intimis Limited
• Original Assignee: Proctor & Stevenson Limited
• Inventors: Mason, Kevin, Griffiths, Ian, Pollard, Ian Nicholas
• Granted Patent: US 9,787,784 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• 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 web server is disclosed that is configured to track requests for web pages on a third party web server. The tracking web server traps a web page request, such as a PURL (Personalised URL) for a personalised web page, before it attempts to serve the web page requested. The URL of the web page request is analysed to determine the location of the requested page on a third party server, and details of the contact with which the personalised web page is associated. Receipt of the web page request is then recorded in a memory associated with the server, and the web page request is forwarded to the third party server for processing. The redirection to the third party web server may be seamless, such that the contact requesting the page does not know of the redirection. In this way, a tracking web server is provided which can supply a personalised tracking and forwarding function.

Claims

1. A tracking web server providing a tracking and forwarding function for requests to personalized Uniform Resource Locators (URL), the tracking web server comprising:

a memory configured to store;

i) data defining a plurality of personalized URLs; and

ii) data indicating for which personalized URLs a corresponding resource request has been received;

a receiver for receiving a URL request, and for trapping the URL request before the tracking web server attempts to access a resource identified by the URL request;

an analyzer arranged to;

identify the URL request as a personalized URL request, wherein the personalized URL request includes a first resource location having a first domain name, and a contact associated with the personalized URL,

update the memory to show that a request for the personalized URL has been received,

wherein the analyzer formulates a new URL request based on the personalized URL, the new URL request indicating a second domain name and a second resource location,

wherein the second resource location is on a web server that is physically separate from the tracking web server, and the second domain of the second resource location is different from the first domain of the first resource location; and

a re-router arranged to transmit the new URL request to the web server.

2. The tracking web server of claim 1, wherein the personalized URL is associated with an identifier that is stored in the memory, wherein the identifier identifies the second resource location.

3. The tracking web server of claim 2, wherein the second resource location indicates a web page or a private web page.

4. The tracking web server of claim 2, wherein the tracking web server includes a server section for serving web pages requested by the URL request when the URL request does not include one of the plurality of personalized URLs, and the memory is arranged to store the web pages,

wherein upon determining that the received URL is not one of the personalized URLs, the analyzer is arranged to provide the URL request to the server section so that the requested web page can be served.

5. The tracking web server of claim 1, wherein the tracking web server includes a server section, wherein the memory stores a security identifier associated with the personalized URL, and the analyzer is arranged to detect whether the security identifier is associated with the personalized URL, and upon determining that the security identifier is associated with the personalized URL, request that the server section serve a web page requesting that a user input the security identifier.

6. The tracking web server of claim 5, wherein the analyzer is further arranged to:

i) detect user input that includes a security code entered into the web page served by the server section;

ii) match the security code received in the user input code against that the security identifier stored in the memory; and

iii) block the re-router from transmitting the new URL request if the security code input by the user does not match the stored security identifier.

7. The tracking web server of claim 2, wherein the identifier for the second resource location is a URL, a URI, or an IP address.

8. The tracking web server of claim 1, further comprising a personalized URL generator that is arranged to:

i) receive personalized URL elements from a tracking entity, including the first domain name, and information unique to a contact to be associated with that personalized URL, as well as receiving an identifier for a target web site to be associated with the personalized URL, and

ii) generate a text string comprising the elements received and representing a personalized URL, and

iii) outputting the text string to the tracking entity.

9. The tracking web server of claim 8, wherein the personalized URL elements include a name of a web page on the first domain.

10. The tracking web server of claim 8, wherein the personalized URL generator is arranged to register the first domain name of the personalized URL with a Domain Name Server (DNS) so that the first domain name points to the IP address of the tracking web server.

11. The tracking web server of claim 8, wherein the analyzer is arranged to store in the memory, one or more of:

i) whether a URL request for a personalized URL request has been received;

ii) data indicating the dates/and or times the request for the personalized URL was received; and

iii) an IP address from which the URL request was received.

12. A method of tracking and forwarding requests to personalized Uniform Resource Locators (URL) with a tracking web server, the method comprising:

storing;

i) data defining a plurality of personalized URLs; and

ii) data indicating for which personalized URLs a corresponding resource request has been received;

receiving a URL request at the tracking web-server, and trapping the URL request before the tracking web server attempts to access a resource identified by the URL request;

identifying the received URL request as a personalized URL request that includes a personalized URL indicating a first resource location having a first domain name;

updating the memory to show that a request for the personalized URL has been received;

formulating a new URL request based on the personalized URL, the new URL request indicating a second resource location and a second domain name, wherein the second resource location is on a web that is physically separate from the tracking web server, and wherein the second domain name of the second resource location is different from the first domain name; and

transmitting the new URL request to the second resource location on the web server.

13. The method of claim 12, wherein the personalized URL is associated with an identifier that is stored in the memory, wherein the identifier identifies the second resource location.

14. The method of claim 13, wherein the second resource location is a web page or a private web page.

15. The method of claim 13, comprising, upon determining that the received URL is not one of the stored plurality of personalized URLs, providing the URL request to a server section so that the requested web page can be served.

16. The method of claim 12, comprising:

storing a security identifier associated with the personalized URL;

detecting whether a security identifier is associated with the personalized URL, and

upon determining that the security identifier is associated with the personalized URL, requesting that a server section serve a web page requesting that a user input the security identifier.

17. The method of claim 16, comprising:

i) detecting user input entered into the web page served by the server section, the user input including a security code;

ii) matching the security code against the stored security identifier; and

iii) blocking the transmission of the new URL request if the security code input by the user does not match the stored security identifier.

18. The method of claim 12, wherein the identifier for the second resource location is a URL, a URI, or an IP address.

19. The method of claim 12, comprising:

receiving personalized URL elements from a tracking entity, the personalized URL elements including the first domain name, and information unique to a contact to be associated with that personalized URL,

receiving an identifier for a target web site to be associated with the personalized URL, and

generating a text string comprising the elements received and representing a personalized URL, and

outputting the text string to the tracking entity.

20. The method of claim 19, wherein the personalized URL elements include the name of a web page on the first domain.

21. The method of claim 19, comprising registering the first domain name of the personalized URL with a Domain Name Server (DNS) so that the first domain name points to an IP address of the tracking web server.

22. The method of claim 21, comprising storing in the memory, one or more of:

i) whether a URL request for a personalized URL request has been received;

ii) data indicating the dates/and or times the request for the personalized URL was received; and

iii) an IP address from which the URL request was received.

23. A computer program product comprising a non-transitory computer readable medium on which computer code is stored, the computer code when executed by a computer causing the computer to track and forward requests to personalized Uniform Resource Locators (URL) with a tracking web server,

wherein the tracking and forwarding comprising:

a) storing;

i) data defining a plurality of personalized URLs; and

ii) data indicating for which personalized URLs a corresponding resource request has been received;

b) receiving a URL request at the tracking web server, and trapping the URL request before the tracking web server attempts to access a resource identified the URL request;

c) identifying the received URL request as a personalized URL request that includes a personalized URL indicating a first resource location having a first domain name, and a contact associated with the personalized URL;

d) updating the memory to show that a request for the personalized URL has been received;

e) formulating a new URL request based on the personalized URL, the new URL request indicating a second resource location having a second domain name, wherein the second resource location is on a web server that is physically separate to the tracking web server, and wherein the second domain name of the second resource location is different from the first domain name; and

f) transmitting the new URL request to the second resource location on the web server.

24. The computer program product of claim 23, wherein the personalized URL is associated with an identifier that is stored in the memory, wherein the identifier identifies the second resource location.

25. The computer program product of claim 24, wherein the second resource location is a web page or a private web page.

26. The computer program product of claim 24, wherein said computer code when executed by a computer causes the computer, upon determining that the received URL is not one of the plurality of personalized URLs, further comprising providing the URL request to a server section for so that the requested web page can be served.

27. The computer program product of claim 23, wherein said computer code when executed by a computer causes the computer to:

store a security identifier associated with the personalized URL before the personalized URL is received;

detect whether a security identifier is associated with the personalized URL when received in the URL request, and

upon determining that the security identifier is associated with the personalized URL, request that a server section serve a web page requesting that a user input the security identifier.

28. The computer program product of claim 27, wherein the computer code when executed by a computer causes the computer to:

i) detect user input entered into the web page served by the server section, the user input including a security code;

ii) match the security code against the stored security identifier; and

iii) block the transmission of the new URL request if the security code input by the user does not match the stored security identifier.

29. The computer program product of claim 24, wherein the identifier for the second resource location is a URL, a URI, or an IP address.

30. The computer program product of claim 23, wherein said computer code when executed by a computer causes the computer to:

receive personalized URL elements from a tracking entity, the personalized URL elements including the second domain name, and information unique to a contact to be associated with that personalized URL,

receive an identifier for a target web site to be associated with the personalized URL, and

generate a text string comprising the elements received and representing a personalized URL, and

outputting the text string to the tracking entity.

31. The computer program product of claim 30, wherein the personalized URL elements include a name of a web page on the first domain.

32. The computer program product of claim 30, wherein said computer code when executed by a computer causes the computer to register the first domain name of the personalized URL with a Domain Name Server (DNS) so that the first domain name points to an IP address of the tracking web server.

33. The computer program product of claim 32, wherein said computer code when executed by a computer causes the computer to store in memory, one or more of:

i) whether a URL request for a personalized URL request has been received;

ii) data indicating the dates/and or times the request for the personalized URL was received; and

iii) an IP address from which the URL request was received.