# US 2018/0027085 A1 · Systems, devices, articles and methods for tracking user referral actions

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

- Number: US 2018/0027085 A1
- Document ID: US20180027085A1
- Status: Published application
- Kind: A1
- Application number: 15/653,829
- Filed: 2017-07-19
- Published: 2018-01-25
- Earliest claimed: 2016-07-21
- Assignees: Simply Measured, Inc.
- Applicants: Simply Measured, Inc.
- Inventors: Brewster Stanislaw; Bryan Short; Joseph Kotkins; Saurabh Kothari; Andy Thivyanathan; Alan Balasundaram; Tim Killian
- Web page: https://patentgrep.com/patent/US20180027085A1

## CPC

- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- G06F 16/9566: {URL specific, e.g. using aliases, detecting broken or misspelled links}
- G06Q 10/40: Business processes related to social networking or social networking services
- G06Q 10/46: Determination of level of influence of users within social networking services
- G06Q 30/0273: Determination of fees for advertising
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- 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)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Systems, methods and articles that detect or otherwise analyze dark social traffic, which traffic was previously designated as “direct traffic” by Web analytics tools. The dark social traffic may be attributed to social channels which allows social marketers to analyze and prove the value of social marketing to their business. Such detection of dark social traffic may include analyzing a Web address included in a Web page request to determine whether the Web address (e.g., URL) includes at least one tracking parameter, which provides an indication that the Web page request emanated from a social share rather than direct traffic. Metadata present in a Web page request may be analyzed to determine the referrer source even when the source does not pass a referrer URL.

## Claims

### Claim 1

A method of operating a processor-based system, the method comprising:
receiving, by an at least one processor of the processor-based system, a Web page request for a first Web page from a client processor-based system, the Web page request includes data indicative of a Web address of the first Web page and does not include data which identifies a Web address of a second Web page that linked to the first Web page;
determining, by the at least one processor of the processor-based system, whether the data indicative of the Web address of the first Web page includes at least one tracking parameter; and
responsive to determining that the data indicative of the Web address of the first Web page includes at least one tracking parameter, designating the Web page request as a social share Web request by the at least one processor of the processor-based system in at least one nontransitory processor-readable storage medium communicatively coupled to the at least one processor, the social share Web request signifying the data indicative of the Web address of the first Web page was previously shared with the client processor-based system by another client processor-based system.

### Claim 2 (depends on 1)

The method of claim 1 wherein receiving a first Web page request for a Web page comprises receiving a Web page request which comprises a URL.

### Claim 3 (depends on 2)

The method of claim 2 wherein determining whether the data indicative of the Web address of the first Web page includes at least one tracking parameter comprises determining whether the URL includes at least one tracking parameter.

### Claim 4 (depends on 1)

The method of claim 1 wherein determining whether the data indicative of the Web address of the first Web page includes at least one tracking parameter comprises determining whether the data indicative of the Web address of the first Web page includes at least one Urchin Traffic Monitor (UTM) parameter.

### Claim 5 (depends on 1)

The method of claim 1 wherein receiving a Web page request comprises receiving a Web page request which includes metadata which identifies information regarding the client processor-based system, the method further comprising:
analyzing, by the at least one processor of the processor-based system, the received metadata to identify a social channel as a referral source for the Web page request; and
logically associating, by the at least one processor of the processor-based system, the Web page request with the social channel as a referral source in the at least one nontransitory processor-readable storage medium.

### Claim 6 (depends on 5)

The method of claim 5 wherein receiving a Web page request comprises receiving a Web page request which includes a user agent string.

### Claim 7 (depends on 6)

The method of claim 6 wherein analyzing the received metadata comprises analyzing the received user agent string to identify a social channel-specific identifier indicative of the social channel.

### Claim 8 (depends on 1)

The method of claim 1 wherein determining whether the data indicative of the Web address of the first Web page includes at least one tracking parameter comprises determining whether the data indicative of the Web address of the first Web page includes a URL hash fragment.

### Claim 9 (depends on 1)

The method of claim 1 wherein determining whether the data indicative of the Web address of the first Web page includes at least one tracking parameter comprises determining whether the data indicative of the Web address of the first Web page includes a query string.

### Claim 10 (depends on 1)

The method of claim 1 wherein determining whether the data indicative of the Web address of the first Web page includes at least one tracking parameter comprises determining whether the data indicative of the Web address of the first Web page includes an identifier of a client processor-based system that previously generated the Web page request.

### Claim 11

A processor-based system, comprising:
at least one nontransitory processor-readable storage medium that stores at least one of processor-readable instructions or data;
at least one processor communicatively coupled to the at least one nontransitory processor-readable storage medium, in operation the at least one processor:
receives a Web page request for a first Web page from a client processor-based system, the Web page request includes data indicative of a Web address of the first Web page and does not include data which identifies a Web address of a second Web page that linked to the Web page;
determines whether the data indicative of the Web address of the first Web page includes at least one tracking parameter; and
responsive to a determination that the data indicative of the Web address of the first Web page includes at least one tracking parameter, designates the Web page request as a social share Web request in the at least one nontransitory processor-readable storage medium, the social share Web request signifying the data indicative of the Web address of the first Web page was previously shared with the client processor-based system by another client processor-based system.

### Claim 12 (depends on 11)

The system of claim 11 wherein the Web page request comprises a URL.

### Claim 13 (depends on 12)

The system of claim 12 wherein the at least one processor:
determines whether the URL includes at least one tracking parameter.

### Claim 14 (depends on 11)

The system of claim 11 wherein the at least one processor:
determines whether the data indicative of the Web address of the first Web page includes at least one Urchin Traffic Monitor (UTM) parameter.

### Claim 15 (depends on 11)

The system of claim 11 wherein the Web page request includes metadata which identifies information regarding the client processor-based system, and the at least one processor:
analyzes the received metadata to identify a social channel as a referral source for the Web page request; and
logically associates the Web page request with the social channel as a referral source in the at least one nontransitory processor-readable storage medium.

### Claim 16 (depends on 15)

The system of claim 15 wherein the Web page request includes a user agent string.

### Claim 17 (depends on 16)

The system of claim 16 wherein the at least one processor:
analyzes the received user agent string to identify a social channel-specific identifier indicative of the social channel.

### Claim 18 (depends on 11)

The system of claim 11 wherein the at least one processor:
determines whether the data indicative of the Web address of the first Web page includes a URL hash fragment.

### Claim 19 (depends on 11)

The system of claim 11 wherein the at least one processor:
determines whether the data indicative of the Web address of the first Web page includes a query string.

### Claim 20 (depends on 11)

The system of claim 11 wherein the at least one processor:
determines whether the data indicative of the Web address of the first Web page includes an identifier of a client processor-based system that previously generated the Web page request.

### Claim 21

A method of operating a processor-based system, comprising:
receiving, by at least one processor of the processor-based system, a Web page request for a Web page from a first client processor-based system;
generating, by the at least one processor of the processor-based system, a Web page request identifier based on the received Web page request to uniquely identify the Web page request from other requests received by the processor-based system for the Web page and from requests for other Web pages;
including, by the at least one processor of the processor-based system, the Web page request identifier in a metadata tag of the requested Web page;
including, by the at least one processor of the processor-based system, a client side executable script with the Web page, the client side executable script which, when executed by a client side processor of the first client processor-based system, causes the first client processor-based system to transmit a digital package including at least the Web page request identifier and a user identifier logically associable with the first client processor-based system;
transmitting, by the at least one processor of the processor-based system, the Web page including the Web page request identifier and including the client side executable script to the first client processor-based system in response to the request from the first client processor-based system;
receiving, by an at least one processor of the processor-based system, a Web page request for the Web page from a second client processor-based system, the Web page request includes data indicative of a Web address of the Web page and does not include data which identifies a Web address of a second Web page that linked to the Web page;
determining, by the at least one processor of the processor-based system, whether the data indicative of the Web address of the first Web page includes the Web page request identifier; and
responsive to determining that the data indicative of the Web address of the first Web page includes at the Web page request identifier, designating the Web page request as a social share Web request by the at least one processor of the processor-based system in a nontransitory processor-readable storage medium, the social share Web request signifying the data indicative of the Web address of the first Web page was previously shared with the second client processor-based system by the first client processor-based system or by another client processor-based system.

### Claim 22 (depends on 21)

The method of claim 21 wherein receiving a Web page request for a Web page comprises receiving a Web page request which comprises a URL.

### Claim 23 (depends on 22)

The method of claim 22 wherein determining whether the data indicative of the Web address of the first Web page includes a Web page request identifier comprises determining whether the data indicative of the Web address of the Web page includes at least one Urchin Traffic Monitor (UTM) parameter.

### Claim 24 (depends on 21)

The method of claim 21 wherein receiving a Web page request comprises receiving a Web page request which includes metadata which identifies information regarding the client processor-based system, the method further comprising:
analyzing, by the at least one processor of the processor-based system, the received metadata to identify a social channel as a referral source for the Web page request; and
logically associating, by the at least one processor of the processor-based system, the Web page request with the social channel as a referral source in the at least one nontransitory processor-readable storage medium.

### Claim 25 (depends on 24)

The method of claim 24 wherein receiving a Web page request comprises receiving a Web page request which includes a user agent string.

### Claim 26 (depends on 25)

The method of claim 25 wherein analyzing the received metadata comprises analyzing the received user agent string to identify a social channel-specific identifier indicative of the social channel.

### Claim 27 (depends on 21)

The method of claim 21 wherein determining whether the data indicative of the Web address of the Web page includes the Web page request identifier comprises determining whether the data indicative of the Web address of the Web page includes a URL hash fragment.

### Claim 28 (depends on 21)

The method of claim 21 wherein determining whether the data indicative of the Web address of the Web page includes the Web page request identifier comprises determining whether the data indicative of the Web address of the first Web page includes a query string.

### Claim 29 (depends on 21)

The method of claim 21 wherein determining whether the data indicative of the Web address of the Web page includes the Web page request identifier comprises determining whether the data indicative of the Web address of the first Web page includes an identifier of the first client processor-based system.

### Claim 30

A processor-based system, comprising:
at least one nontransitory processor-readable storage medium that stores at least one of processor-readable instructions or data;
at least one processor communicatively coupled to the at least one nontransitory processor-readable storage medium, in operation the at least one processor:
receiving, by at least one processor of the processor-based system, a Web page request for a Web page from a first client processor-based system;
generating, by the at least one processor of the processor-based system, a Web page request identifier based on the received Web page request to uniquely identify the Web page request from other requests received by the processor-based system for the Web page and from requests for other Web pages;
including, by the at least one processor of the processor-based system, the Web page request identifier in a metadata tag of the requested Web page;
including, by the at least one processor of the processor-based system, a client side executable script with the Web page, the client side executable script which, when executed by a client side processor of the first client processor-based system, causes the first client processor-based system to transmit a digital package including at least the Web page request identifier and a user identifier logically associable with the first client processor-based system;
transmitting, by the at least one processor of the processor-based system, the Web page including the Web page request identifier and including the client side executable script to the first client processor-based system in response to the request from the first client processor-based system;
receiving, by an at least one processor of the processor-based system, a Web page request for the Web page from a second client processor-based system, the Web page request includes data indicative of a Web address of the Web page and does not include data which identifies a Web address of a second Web page that linked to the Web page;
determining, by the at least one processor of the processor-based system, whether the data indicative of the Web address of the first Web page includes the Web page request identifier; and
responsive to determining that the data indicative of the Web address of the first Web page includes at the Web page request identifier, designating the Web page request as a social share Web request by the at least one processor of the processor-based system in a nontransitory processor-readable storage medium, the social share Web request signifying the data indicative of the Web address of the first Web page was previously shared with the second client processor-based system by the first client processor-based system or by another client processor-based system.

### Claim 31 (depends on 30)

The system of claim 30 wherein the Web page request comprises a URL.

### Claim 32 (depends on 31)

The system of claim 31 wherein the at least one processor:
determines whether the data indicative of the Web address of the Web page includes at least one Urchin Traffic Monitor (UTM) parameter.

### Claim 33 (depends on 30)

The system of claim 30 wherein the Web page request includes metadata which identifies information regarding the client processor-based system, and the at least one processor:
analyzes the received metadata to identify a social channel as a referral source for the Web page request; and
logically associates the Web page request with the social channel as a referral source in the at least one nontransitory processor-readable storage medium.

### Claim 34 (depends on 33)

The system of claim 33 wherein the Web page request includes a user agent string.

### Claim 35 (depends on 34)

The system of claim 34 wherein the at least one processor:
analyzes the received user agent string to identify a social channel-specific identifier indicative of the social channel.

### Claim 36 (depends on 30)

The system of claim 30 wherein the at least one processor:
determines whether the data indicative of the Web address of the Web page includes a URL hash fragment.

### Claim 37 (depends on 30)

The system of claim 30 wherein the at least one processor:
determines whether the data indicative of the Web address of the first Web page includes a query string.

### Claim 38 (depends on 30)

The system of claim 30 wherein the at least one processor:
determines whether the data indicative of the Web address of the first Web page includes an identifier of the first client processor-based system.
