# US 2022/0036477 A1 · System and method for determining revenue generated by any zone in a webpage

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

- Number: US 2022/0036477 A1
- Document ID: US20220036477A1
- Status: Published application
- Kind: A1
- Application number: 16/940,800
- Filed: 2020-07-28
- Published: 2022-02-03
- Earliest claimed: 2020-07-28
- Assignees: Content Square SAS
- Applicants: Content Square SAS
- Inventors: Luis DIAZ; Lionel SEGUIN
- Web page: https://patentgrep.com/patent/US20220036477A1

## CPC

- G06Q 40/12: Accounting
- G06F 3/0482: Interaction with lists of selectable items, e.g. menus
- G06F 16/955: using information identifiers, e.g. uniform resource locators [URL]
- G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06Q 30/0201: Market modelling; Market analysis; Collecting market data
- G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03)
- H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066)
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- H04L 67/75: Indicating network or usage conditions on the user display
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method for determining revenue generated by zones in a webpage are provided. The method includes receiving session interaction data gathered from a plurality of user devices of a plurality of visitors visiting the webpage during a plurality of sessions; determining, for each session, and for session interaction data received from each user device of the plurality of user devices, if the respective session interaction data includes a purchase event, wherein the purchase event is indicative of a completion of a transaction; generating zone revenue data per session by analyzing session interaction data with purchase events; aggregating the generated zone revenue data across multiple sessions recorded for the plurality of visitors visiting the webpage, wherein the aggregated revenue data lists all zones in the webpage which contributed to a completion of the transaction; and reporting the aggregated revenue data.

## Claims

### Claim 1

A method for determining revenue generated by zones in a webpage, comprising:
receiving session interaction data gathered from a plurality of user devices of a plurality of visitors visiting the webpage during a plurality of sessions;
determining, for each session, and for session interaction data received from each user device of the plurality of user devices, if the respective session interaction data includes a purchase event, wherein the purchase event is indicative of a completion of a transaction;
generating zone revenue data per session by analyzing session interaction data with purchase events;
aggregating the generated zone revenue data across multiple sessions recorded for the plurality of visitors visiting the webpage, wherein the aggregated revenue data lists all zones in the webpage which contributed to a completion of the transaction; and
reporting the aggregated revenue data.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
identifying zones in the collected webpage versions; and
analyzing session interaction data with purchase events to determine which of the identified zones was accessed by a visitor during a session.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
receiving a request to determine revenue data generated by zones in the webpage during a selected date range;
collecting past webpage versions of the website, wherein the past webpage versions are collected for the selected date range;
generating zone revenues for each past webpage version; and
aggregating the generated zone revenue data across multiple past webpage versions.

### Claim 4 (depends on 1)

The method of claim 1, wherein zones in the webpage which contributed to a completion of the transaction includes any zone with which a visitor interacted prior to completing a transaction.

### Claim 5 (depends on 1)

The method of claim 1, wherein an interaction with a zone includes any one of: clicking on a zone, scrolling through a zone, hovering over a zone, zooming into a zone, zooming out of a zone.

### Claim 6 (depends on 1)

The method of claim 1, wherein a transaction includes at least a monetary transaction, wherein the monetary transaction includes a sale, a subscription, a donation, a refund, and an exchange.

### Claim 7 (depends on 1)

The method of claim 1, wherein the aggregated revenue data further includes: revenue generated by each zone of the listed zones.

### Claim 8 (depends on 7)

The method of claim 7, wherein reporting the aggregated revenue data further comprises:
overlaying the revenue generated by each zone over the webpage with reference to the respective zone.

### Claim 9 (depends on 1)

The method of claim 1, wherein the session interaction data is data describing a visitor's interactions with the webpage during a session, wherein a session is a period occurring between a visitor's initial connection with a website and disconnection with the website.

### Claim 10 (depends on 1)

The method of claim 1, wherein a zone is a visible element included in the webpage.

### Claim 11

A non-transitory computer readable medium having stored thereon instructions for causing a processing circuitry to execute a process, the process comprising:
receiving session interaction data gathered from a plurality of user devices of a plurality of visitors visiting the webpage during a plurality of sessions;
determining, for each session, and for session interaction data received from each user device of the plurality of user devices, if the respective session interaction data includes a purchase event, wherein the purchase event is indicative of a completion of a transaction;
generating zone revenue data per session by analyzing session interaction data with purchase events;
aggregating the generated zone revenue data across multiple sessions recorded for the plurality of visitors visiting the webpage, wherein the aggregated revenue data lists all zones in the webpage which contributed to a completion of the transaction; and
reporting the aggregated revenue data.

### Claim 12

A system for determining revenue generated by zones in a webpage, comprising:
a processing circuitry; and
a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to:
receive session interaction data gathered from a plurality of user devices of a plurality of visitors visiting the webpage during a plurality of sessions;
determine, for each session, and for session interaction data received from each user device of the plurality of user devices, if the respective session interaction data includes a purchase event, wherein the purchase event is indicative of a completion of a transaction;
generate zone revenue data per session by analyzing session interaction data with purchase events;
aggregate the generated zone revenue data across multiple sessions recorded for the plurality of visitors visiting the webpage, wherein the aggregated revenue data lists all zones in the webpage which contributed to a completion of the transaction; and
report the aggregated revenue data.

### Claim 13 (depends on 12)

The system of claim 12, wherein the system is further configured to:
identify zones in the collected webpage versions; and
analyze session interaction data with purchase events to determine which of the identified zones was accessed by a visitor during a session.

### Claim 14 (depends on 12)

The system of claim 12, wherein the system is further configured to:
receive a request to determine revenue data generated by zones in the webpage during a selected date range;
collect past webpage versions of the website, wherein the past webpage versions are collected for the selected date range;
generate zone revenues for each past webpage version; and
aggregate the generated zone revenue data across multiple past webpage versions.

### Claim 15 (depends on 12)

The system of claim 12, wherein zones in the webpage which contributed to a completion of the transaction includes any zone with which a visitor interacted prior to completing a transaction.

### Claim 16 (depends on 12)

The system of claim 12, wherein an interaction with a zone includes any one of: clicking on a zone, scrolling through a zone, hovering over a zone, zooming into a zone, zooming out of a zone.

### Claim 17 (depends on 12)

The system of claim 12, wherein a transaction includes at least a monetary transaction, wherein the monetary transaction includes a sale, a subscription, a donation, a refund, and an exchange.

### Claim 18 (depends on 12)

The system of claim 12, wherein the aggregated revenue data further includes: revenue generated by each zone of the listed zones.

### Claim 19 (depends on 18)

The system of claim 18, wherein the system is further configured to:
overlay the revenue generated by each zone over the webpage with reference to the respective zone.

### Claim 20 (depends on 12)

The system of claim 12, wherein the session interaction data is data describing a visitor's interactions with the webpage during a session, wherein a session is a period occurring between a visitor's initial connection with a website and disconnection with the website.

### Claim 21 (depends on 12)

The system of claim 12, wherein a zone is a visible element included in the webpage.
