# US 12,592,986 B2 · Computer system and method with referral tracking for shared content

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,592,986 B2
- Document ID: US12592986B2
- Status: Granted
- Kind: B2
- Application number: 18/419,268
- Filed: 2024-01-22
- Published: 2024-05-16
- Granted: 2026-03-31
- Earliest claimed: 2022-06-27
- Assignees: Achim Edelmann; Christian Müller
- Applicants: Achim Edelmann; Christian Müller
- Inventors: Achim Edelmann; Christian Müller; Marco Bastos
- Web page: https://patentgrep.com/patent/US12592986B2

## CPC

- H04L 51/234: for tracking messages
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- G06F 16/955: using information identifiers, e.g. uniform resource locators [URL]
- G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A tracking server may receive, from a requester, a content request for accessing a content element on a content server. The content request includes a request Uniform Resource Locator (“URL”) with at least a content identifier specifying the requested content element on the content server, and a request referral identifier. If the content identifier does not refer to a content element provided on the content server, an error response is sent. If the content identifier refers to a content element provided on the content server, a new and unique referral identifier associated with the content request is generated. Further, a new and unique referral URL for the content request is generated as a response URL comprising the received content identifier and the newly generated unique referral identifier. The requested content element is then served to the requester under the response URL.

## Claims

### Claim 1

A computer-implemented method for tracking sharing of web-content provided by a content server, the method comprising:
receiving, from a requester, a first content request for accessing a content element on the content server, wherein the first content request comprises a first request Uniform Resource Locator (URL) (URLreq) with at least a content identifier (CI) specifying the content element on the content server, and a first referral identifier (RI) being a code indicating that the first request URL was previously used as a first response URL;
generating a new and unique second referral identifier associated with the first content request;
generating a new and unique first referral URL for the first content request as a second response URL (URLres) comprising the content identifier and the second referral identifier;
adding the first request URL (URLreq) and the second response URL (URLres) as a first data record to a tracking data structure;
serving the content element to the requester under the second response URL (URLres);
receiving, from the requester, a second content request for accessing the content element on the content server, wherein the second content request comprises the first request URL (URLreq);
generating a new and unique third referral identifier associated with the second content request;
generating a new and unique second referral URL for the second content request as a third response URL (URLres) comprising the content identifier and the third referral identifier;
adding the first request URL (URLreq) and the third response URL (URLres) as a second data record to the tracking data structure; and
serving the content element to the requester under the third response URL (URLres).

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
before adding the first data record to the tracking data structure, generating a new and unique requester identifier to be stored at the requester if the first content request does not include a requester identifier; and
wherein the first record further comprises either the new and unique requester identifier or the requester identifier included in the first content request, respectively.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
generating the new and unique second referral identifier if the first content request does not include the requester identifier, or if the first content request includes the requester identifier for which no pair of said requester identifier and the received content identifier is present in a record of the tracking data structure;
if the first content request includes the requester identifier for which a pair of said requester identifier and the received content identifier is present in a corresponding record of the tracking data structure, using a corresponding referral identifier from the corresponding record;
generating the second response URL with the received content identifier and the generated new and unique second referral identifier, or with the received content identifier and the corresponding referral identifier of the corresponding record, respectively;
adding the first request URL (URLreq), the second response URL (URLres), and the requester identifier (R-ID) as the first data record to the tracking data structure; and
serving the requested content element (CE) to the requester under the second response URL (URLres).

### Claim 4 (depends on 1)

The method of claim 1, wherein the tracking server receives additional data with the first content request, the additional data associated with further properties associated with the first content request, wherein each new data record added to the tracking data structure further includes additional information (INFadd) which includes the additional data and/or properties derived from the additional data.

### Claim 5 (depends on 4)

The method of claim 4, wherein the additional information (INFadd) is associated with at least one or more of the following: Internet Protocol (IP) address of the requester, time when the first content request was submitted, information about a client of the requester, geolocation associated with an origin of the first content request, geolocation associated with an origin of the requester, and requester's site interaction history.

### Claim 6 (depends on 4)

The method of claim 4, further comprising:
changing response behavior of the tracking server by applying behavioral decision rules to the additional information for determining a conditional behavior setting for the tracking server, wherein, dependent on the additional information, the content element is served to the requester under the conditional behavior setting.

### Claim 7

A tracking server for tracking sharing of web-content provided by a content server, the tracking server including at least one processor and at least one memory storing instructions, which, when executed, cause the at least one processor to:
receive, from a requester, a first content request for accessing a content element on the content server, wherein the first content request comprises a first request Uniform Resource Locator (URL) (URLreq) with at least a content identifier (CI) specifying the content element on the content server, and a first referral identifier (RI) being a code indicating that the first request URL was previously used as a first response URL;
generate a new and unique second referral identifier associated with the first content request;
generate a new and unique first referral URL as a second response URL (URLres) for the first content request, the second response URL comprising the content identifier and the second referral identifier; and
add the first request URL (URLreq) and the second response URL (URLres) as a first data record to a tracking data structure:
serve the content element to the requester under the second response URL (URLres);
receive, from the requester, a second content request for accessing the content element on the content server, wherein the second content request comprises the first request URL (URLreq);
generate a new and unique third referral identifier associated with the second content request;
generate a new and unique second referral URL for the second content request as a third response URL (URLres) comprising the content identifier and the third referral identifier;
add the first request URL (URLreq) and the third response URL (URLres) as a second data record to the tracking data structure; and
serve the content element to the requester under the third response URL (URLres).

### Claim 8 (depends on 7)

The tracking server of claim 7, wherein the instructions, when executed, cause the at least one processor to:
before adding the first data record to the tracking data structure, generate a new and unique requester identifier to be stored at the requester if the first content request does not include a requester identifier; and
wherein the first data record further comprises either the new and unique requester identifier or the requester identifier included in the first content request, respectively.

### Claim 9 (depends on 8)

The tracking server of claim 8, wherein the instructions, when executed, cause the at least one processor:
to generate the new and unique second referral identifier if the first content request does not include the requester identifier, or if the first content request includes the requester identifier for which no pair of said requester identifier and the received content identifier is present in a record of the tracking data structure;
if the first content request includes the requester identifier for which a pair of said requester identifier and the received content identifier is present in a record of the tracking data structure, to use a corresponding referral identifier from a corresponding record;
to generate the second response URL with the received content identifier and the generated new and unique second referral identifier, or with the received content identifier and the corresponding referral identifier used from the corresponding record, respectively;
to add the first request URL, the second response URL, and the requester identifier as the first data record to the tracking data structure; and
to serve the requested content element to the requester under the second response URL.

### Claim 10 (depends on 7)

The tracking server of claim 7, wherein the instructions, when executed, cause the at least one processor to: receive additional data with the first content request, the additional data associated with further properties associated with the first content request, wherein each new data record added to the tracking data structure further includes additional information (INFadd) which includes the additional data and/or properties derived from the additional data.

### Claim 11 (depends on 10)

The tracking server of claim 10, wherein the additional information (INFadd) is associated with at least one or more of the following: Internet Protocol (IP) address of the requester, time when the first content request was submitted, information about a client of the requester, geolocation associated with an origin of the first content request, geolocation associated with an origin of the requester, and requester's site interaction history.

### Claim 12 (depends on 10)

The tracking server of claim 10, wherein the instructions, when executed, cause the at least one processor to:
change response behavior of the tracking server by applying behavioral decision rules to the additional information for determining a conditional behavior setting for the tracking server; and;
dependent on the additional information, serve the content element to the requester under the conditional behavior setting.

### Claim 13

A computer program product for tracking sharing of web-content provided by a content server, the computer program product being tangibly embodied on a non-transitory computer-readable storage medium and comprising instructions that, when executed by at least one computing device, are configured to cause the at least one computing device to:
receive, from a requester, a first content request for accessing a content element on the content server, wherein the first content request comprises a first request Uniform Resource Locator (URL) (URLreq) with at least a content identifier (CI) specifying the content element on the content server, and a first referral identifier (RI) being a code indicating that the first request URL was previously used as a first response URL;
generate a new and unique second referral identifier associated with the first content request;
generate a new and unique first referral URL for the first content request as a second response URL (URLres) comprising the content identifier and the second referral identifier;
add the first request URL (URLreq) and the second response URL (URLres) as a first data record to a tracking data structure;
serve the content element to the requester under the second response URL (URLres);
receive, from the requester, a second content request for accessing the content element on the content server, wherein the second content request comprises the first request URL (URLreq);
generate a new and unique third referral identifier associated with the second content request;
generate a new and unique second referral URL for the second content request as a third response URL (URLres) comprising the content identifier and the third referral identifier;
add the first request URL (URLreq) and the third response URL (URLres) as a second data record to the tracking data structure; and
serve the content element to the requester under the third response URL (URLres).

### Claim 14 (depends on 13)

The computer program product of claim 13, wherein the instructions are further configured to cause the at least one computing device to:
before adding the first data record to the tracking data structure, generate a new and unique requester identifier to be stored at the requester if the first content request does not include a requester identifier; and
wherein the new data record further comprises either the new and unique requester identifier or the requester identifier included in the first content request, respectively.

### Claim 15 (depends on 14)

The computer program product of claim 14, wherein the instructions are further configured to cause the at least one computing device to:
generate the new and unique second referral identifier if the first content request does not include the requester identifier, or if the first content request includes the requester identifier for which no pair of said requester identifier and the received content identifier is present in a record of the tracking data structure;
if the first content request includes the requester identifier for which a pair of said requester identifier and the received content identifier is present in a corresponding record of the tracking data structure, using a corresponding referral identifier from the corresponding record;
generate the second response URL with the received content identifier and the generated new and unique referral identifier, or with the received content identifier and the corresponding referral identifier of the corresponding record, respectively;
adding the first request URL (URLreq), the second response URL (URLres), and the requester identifier (R-ID) as the first data record to the tracking data structure; and
serve the requested content element (CE) to the requester under the second response URL (URLres).

### Claim 16 (depends on 13)

The computer program product of claim 13, wherein the instructions are further configured to cause the at least one computing device to:
receive additional data with the first content request, the additional data associated with further properties associated with the first content request, wherein each new data record added to the tracking data structure further includes additional information (INFadd) which includes the additional data and/or properties derived from the additional data.

### Claim 17 (depends on 16)

The computer program product of claim 16, wherein the additional information (INFadd) is associated with at least one or more of the following: Internet Protocol (IP) address of the requester, time when the first content request was submitted, information about a client of the requester, geolocation associated with an origin of the first content request, geolocation associated with an origin of the requester, and requester's site interaction history.