# US 2012/0084133 A1 · Methods and apparatus to distinguish between parent and child webpage accesses and/or browser tabs in focus

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

- Number: US 2012/0084133 A1
- Document ID: US20120084133A1
- Status: Published application
- Kind: A1
- Application number: 12/895,288
- Filed: 2010-09-30
- Published: 2012-04-05
- Earliest claimed: 2010-09-30
- Assignees: The Nielsen Company (US), LLC
- Inventors: Scott Ross; Vianney Dervaux; Binlay Low
- Web page: https://patentgrep.com/patent/US20120084133A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- G06F 11/3438: {monitoring of user actions (tracking the activity of the user H04L67/535)}
- G06F 11/3476: {Data logging (G06F11/14, G06F11/2205 take precedence)}
- G06F 11/3495: {for systems}
- G06F 16/95: Retrieval from the web
- G06Q 30/0226: Incentive systems for frequent usage, e.g. frequent flyer miles programs or point systems
- H04L 43/062: related to network traffic
- G06F 16/954: Navigation, e.g. using categorised browsing
- G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F 2201/875: Monitoring of systems including the internet
- 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

Methods and apparatus to distinguish between parent and child webpage accesses and/or browser tabs in focus are disclosed. An example implementation includes identifying an HTTP request; retrieving Page Info data from a browser; electronically detecting if the Page Info data and the HTTP request identify a same Internet resource; electronically classifying the HTTP request as a parent call when the Page Info data and the HTTP request identify the same Internet resource; and electronically classifying the HTTP request as a child call when the Page Info data and the HTTP request identify different Internet resources.

## Claims

### Claim 1

A method to monitor Internet usage, the method comprising:
identifying an HTTP request;
retrieving Page Info data from a browser;
electronically detecting if the Page Info data and the HTTP request identify a same Internet resource;
electronically classifying the HTTP request as a parent call when the Page Info data and the HTTP request identify the same Internet resource; and
electronically classifying the HTTP request as a child call when the Page Info data and the HTTP request identify different Internet resources.

### Claim 2 (depends on 1)

The method as described in claim 1, wherein electronically classifying the HTTP request as a parent call further comprises collecting tab data from the browser and classifying the HTTP request as a parent call when the tab data identifies an active tab of the browser.

### Claim 3 (depends on 1)

The method as described in claim 1, wherein electronically classifying the HTTP request as a parent call further comprises collecting computer interaction data and classifying the HTTP request as a parent call when the computer interaction data indicates that there was user input within a past time window associated with the HTTP request.

### Claim 4 (depends on 3)

The method as described in claim 3, wherein the computer interaction data includes at least one of keyboard data, mouse data, or a focus status of the web browser.

### Claim 5 (depends on 3)

The method as described in claim 3, wherein the past time window is less than 4 seconds.

### Claim 6 (depends on 1)

The method as described in claim 1, wherein electronically classifying the HTTP request as a parent call further comprises determining if the browser was the application source of the HTTP request and classifying the HTTP request as a parent call when the browser was the application source of the HTTP request

### Claim 7 (depends on 1)

The method as described in claim 1, wherein electronically classifying the HTTP request as a parent call further comprises determining if the browser was in focus at the time of the HTTP request and classifying the HTTP request as a parent call when the browser was in focus at the time of the HTTP request.

### Claim 8 (depends on 1)

The method as described in claim 1, further comprising electronically awarding presentation credit to a website when the associated HTTP traffic is classified as a parent call.

### Claim 9 (depends on 8)

The method as described in claim 8, wherein presentation credit awarded to the site is based on a time difference between the parent call and a next non-child call; wherein the next non-child call is either a parent call or a non-browser event.

### Claim 10 (depends on 8)

The method as described in claim 8, wherein the website is determined based on the Page Info data.

### Claim 11 (depends on 8)

The method as described in claim 8, further comprising electronically transmitting the awarded presentation credit to a monitoring data collection site.

### Claim 12 (depends on 1)

The method as described in claim 1, wherein the collected page info data includes at least one of an address of the HTTP request, a type of HTTP request, a referring Internet resource, or metadata relating to the HTTP request.

### Claim 13

An apparatus to monitor Internet traffic caused by a user, the apparatus comprising:
a browser information data gatherer to collect page info data from a web browser;
an Hypertext Transfer Protocol (HTTP) data gatherer to collect HTTP traffic data from a network interface of the computer; and
a processor to compare the gathered page info data and the HTTP traffic data to determine whether an HTTP request identified in the HTTP traffic data should be credited as a call to a parent webpage or a call to a child webpage.

### Claim 14 (depends on 13)

The apparatus as described in claim 13, wherein the browser information data gatherer further collects active tab data from the web browser, and the processor further compares an application source of the HTTP request identified in the HTTP traffic data and the active tab data to determine whether the HTTP request identified in the HTTP traffic data should be credited as the call to the parent webpage or the call to the child webpage.

### Claim 15 (depends on 13)

The apparatus as described in claim 13, further comprising an interaction data gatherer to collect interaction data indicative of user input to a computer, wherein the processor further compares a timestamp of the HTTP request identified in the HTTP traffic data and the interaction data to determine whether the HTTP request identified in the HTTP traffic data should be credited as a call to a parent webpage.

### Claim 16

A tangible computer readable medium storing instructions which when executed cause a machine to:
identify an HTTP request;
retrieve Page Info data from a browser;
collect tab data from the browser;
electronically detect if the Page Info data and the HTTP request identify a same Internet resource; and
electronically classify the HTTP request as a parent call when the Page Info data and the HTTP request identify the same Internet resource and when the tab data identifies an active tab of the browser as associated with HTTP request; and
electronically classify the HTTP request as a child call when either the Page Info data and the HTTP request identify different Internet resources or the tab data does not identify the active tab of the browser as associated with the HTTP request.

### Claim 17 (depends on 16)

The tangible computer readable medium as described in claim 16, wherein the instructions cause the machine to electronically classify the HTTP request as a parent call when computer interaction data indicates that there was user input within a past time window associated with the HTTP request.

### Claim 18 (depends on 17)

The tangible computer readable medium as described in claim 17, wherein the computer interaction data includes at least one of keyboard data, mouse data, or focus status of the web browser.

### Claim 19 (depends on 17)

The tangible computer readable medium as described in claim 17, wherein the past time window is less than 4 seconds.

### Claim 20 (depends on 16)

The tangible computer readable medium as described in claim 16, wherein the instructions cause the machine to electronically classify the HTTP request as a parent call when the browser was the application source of the HTTP request.

### Claim 21 (depends on 16)

The tangible computer readable medium as described in claim 16, wherein the instructions cause the machine to electronically classify the HTTP request as a parent call when the browser was in focus.

### Claim 22 (depends on 16)

The tangible computer readable medium as described in claim 16, wherein the instructions cause the machine to electronically award presentation credit to a website when the associated the associated HTTP traffic is classified as a parent call.

### Claim 23 (depends on 22)

The tangible computer readable medium as described in claim 22, wherein the presentation credit awarded to the site is based on a time difference between the parent call and a next non-child call; wherein the next non-child call is either a parent call or a non-browser event.

### Claim 24 (depends on 22)

The tangible computer readable medium as described in claim 22, wherein the website is determined based on the Page Info data.

### Claim 25 (depends on 22)

The tangible computer readable medium as described in claim 22, wherein the instructions cause the machine to electronically transmit the awarded presentation credit to a monitoring data collection site.

### Claim 26 (depends on 16)

The tangible computer readable medium as described in claim 16, wherein the retrieved page info data includes at least one of an address of the HTTP request, a type of HTTP request, a referring Internet resource, or metadata relating to the HTTP request.
