# US 2018/0324265 A1 · Matching and attribution of user device events

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

- Number: US 2018/0324265 A1
- Document ID: US20180324265A1
- Status: Published application
- Kind: A1
- Application number: 15/972,707
- Filed: 2018-05-07
- Published: 2018-11-08
- Earliest claimed: 2017-05-08
- Assignees: Branch Metrics, Inc.
- Applicants: Branch Metrics, Inc.
- Inventors: Sofus Attila Macskassy; Dmitri Ariel Gaskin; Eric J. Glover; Kan Yu; Wenchang Yan
- Web page: https://patentgrep.com/patent/US20180324265A1

## CPC

- G06F 16/9558: {Details of hyperlinks; Management of linked annotations}
- G06Q 30/0201: Market modelling; Market analysis; Collecting market data
- H04L 65/40: Support for services or applications
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/306: User profiles
- H04L 67/53: using third party service providers
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- 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
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method includes receiving first event data from a device, the first event data including a first identifier (ID) that identifies the device, web browser metadata, and data associated with an application state. The method includes generating a first persona including the first ID and a first event identifier that identifies a first user action. The method includes receiving second event data, the second event data including device metadata and a second ID that identifies the device. The method includes generating a second persona based on the second event data, the second persona including the second ID and a second event identifier that identifies a second user action. Additionally, the method includes determining that the first and second personas are associated with the device based on matches between the browser metadata and device metadata and transmitting a response to the device configured to route the device to the application state.

## Claims

### Claim 1

A method comprising:
generating, at a computing device, a first data object that includes a first device identifier (ID) and web browser metadata that are associated with a web browser application on a user device;
generating, at the computing device, a second data object that includes a second device ID and device metadata that are associated with an installed application on the user device;
determining, at the computing device, a matching score based on the web browser metadata and the device metadata, wherein the matching score indicates that the first device ID and the second device ID are likely associated with the user device;
receiving, at the computing device, web event data from the user device, the web event data generated in response to a user action on the web browser application, wherein the web event data includes the first device ID, and wherein the web event data includes data associated with an application state;
receiving, at the computing device, application event data from the user device that is generated by the installed application, wherein the application event data includes the second device ID; and
in response to receiving the application event data and determining the matching score indicates that the first and second device IDs are likely associated with the user device, transmitting a response to the user device including routing data configured to route the installed application to the application state associated with the web event data.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
comparing the matching score to a threshold matching score; and
determining that the matching score indicates the first device ID and the second device ID are likely associated with the user device when the matching score is greater than the threshold matching score.

### Claim 3 (depends on 1)

The method of claim 1, wherein the first device ID is a web cookie ID, and wherein the second device ID is an ID that is accessed by the installed application.

### Claim 4 (depends on 1)

The method of claim 1, wherein the web browser metadata and the device metadata include internet protocol (IP) addresses, and wherein the method comprises determining the matching score based on the IP addresses included in the web browser metadata and the device metadata.

### Claim 5 (depends on 1)

The method of claim 1, wherein the web browser metadata and the device metadata include the same internet protocol (IP) address, the method further comprising:
prior to receiving the web event data and the application event data, receiving prior instances of additional web event data and prior instances of additional application event data associated with the same IP address as the web browser metadata and the device metadata; and
determining the matching score based on the number of instances of the additional web event data and the additional application event data that include the same IP address as the web metadata and the device metadata.

### Claim 6 (depends on 1)

The method of claim 1, wherein the web browser metadata and the device metadata include device type data that is descriptive of the user device, and wherein the method comprises determining the matching score based on the device type data included in the web browser metadata and the device metadata.

### Claim 7 (depends on 1)

The method of claim 1, wherein the web browser metadata and the device metadata include device type data that is descriptive of the user device, the method further comprising:
receiving instances of additional web event data and instances of additional application event data including device type data that is descriptive of the user device; and
determining the matching score based on the number of instances of additional web event data and the number of instances of additional application event data.

### Claim 8 (depends on 1)

The method of claim 1, wherein the web browser metadata and the device metadata include screen resolution data, and wherein the method comprises determining the matching score based on the resolution data included in the web browser metadata and the device metadata.

### Claim 9 (depends on 1)

The method of claim 1, wherein the web browser metadata includes a username and a website identifier that identifies a website, wherein the device metadata includes the username and an application identifier that identifies the installed application, and wherein the method comprises determining that the first device ID and the second device ID are likely associated with the user device based on determining that the usernames match and the application identifier matches the website identifier.

### Claim 10 (depends on 1)

The method of claim 1, wherein the first data object includes a first event identifier that identifies a user action on the web browser application, and wherein the second data object includes a second event identifier that identifies an action associated with the installed application.

### Claim 11 (depends on 10)

The method of claim 10, wherein the user action on the web browser application was a selection of a web link, and wherein the action associated with the installed application is the initial opening of the installed application after installation.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
generating, at the computing device, a third data object based on the received web event data, wherein the third data object includes the first device ID and a first event identifier, and wherein the first event identifier indicates that the web event data was generated by the user device in response to user selection of a web link; and
generating, at the computing device, a fourth data object based on the received application event data, wherein the fourth data object includes the second device ID and a second event identifier, and wherein the second event identifier indicates that the application event data was generated by the user device in response to the opening of the installed application.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
generating, at the computing device, a third data object based on the received web event data, wherein the third data object includes the first device ID;
generating, at the computing device, a fourth data object based on the received application event data, wherein the fourth data object includes the second device ID;
receiving, at the computing device, subsequent application event data from the user device, wherein the subsequent application event data includes the first device ID and the second device ID; and
in response to receiving the subsequent application event data, generating a fifth data object based on data included in the first data object, the second data object, the third data object, the fourth data object, and the subsequent application event data.

### Claim 14

A system comprising:
one or more storage devices configured to store:
a first data object that includes a first device identifier (ID) and web browser metadata that are associated with a web browser application on a user device; and
a second data object that includes a second device ID and device metadata that are associated with an installed application on the user device; and
one or more processing units that execute computer-readable instructions that cause the one or more processing units to:
determine a matching score based on the web browser metadata and the device metadata, wherein the matching score indicates that the first device ID and the second device ID are likely associated with the user device;
receive web event data from the user device, the web event data generated in response to a user action on the web browser application, wherein the web event data includes the first device ID, and wherein the web event data includes data associated with an application state;
receive application event data from the user device that is generated by the installed application, wherein the application event data includes the second device ID; and in response to receiving the application event data and determining the
matching score indicates that the first and second device IDs are likely associated with the user device, transmit a response to the user device including routing data configured to route the installed application to the application state associated with the web event data.

### Claim 15 (depends on 14)

The system of claim 14, wherein the one or more processing units are configured to:
compare the matching score to a threshold matching score; and
determine that the matching score indicates the first device ID and the second device ID are likely associated with the user device when the matching score is greater than the threshold matching score.

### Claim 16 (depends on 14)

The system of claim 14, wherein the first device ID is a web cookie ID, and wherein the second device ID is an ID that is accessed by the installed application.

### Claim 17 (depends on 14)

The system of claim 14, wherein the web browser metadata and the device metadata include internet protocol (IP) addresses, and wherein the one or more processing units are configured to determine the matching score based on the IP addresses included in the web browser metadata and the device metadata.

### Claim 18 (depends on 14)

The system of claim 14, wherein the web browser metadata and the device metadata include the same internet protocol (IP) address, and wherein the one or more processing units are configured to:
prior to receiving the web event data and the application event data, receive prior instances of additional web event data and prior instances of additional application event data associated with the same IP address as the web browser metadata and the device metadata; and
determine the matching score based on the number of instances of the additional web event data and the additional application event data that include the same IP address as the web metadata and the device metadata.

### Claim 19 (depends on 14)

The system of claim 14, wherein the web browser metadata and the device metadata include device type data that is descriptive of the user device, and wherein the one or more processing units are configured to determine the matching score based on the device type data included in the web browser metadata and the device metadata.

### Claim 20 (depends on 14)

The system of claim 14, wherein the web browser metadata and the device metadata include device type data that is descriptive of the user device, and wherein the one or more processing units are configured to:
receive instances of additional web event data and instances of additional application event data including device type data that is descriptive of the user device; and
determine the matching score based on the number of instances of additional web event data and the number of instances of additional application event data.

### Claim 21 (depends on 14)

The system of claim 14, wherein the web browser metadata and the device metadata include screen resolution data, and wherein the one or more processing units are configured to determine the matching score based on the resolution data included in the web browser metadata and the device metadata.

### Claim 22 (depends on 14)

The system of claim 14, wherein the web browser metadata includes a username and a website identifier that identifies a website, wherein the device metadata includes the username and an application identifier that identifies the installed application, and wherein the one or more processing units are configured to determine that the first device ID and the second device ID are likely associated with the user device based on determining that the usernames match and the application identifier matches the website identifier.

### Claim 23 (depends on 14)

The system of claim 14, wherein the first data object includes a first event identifier that identifies a user action on the web browser application, and wherein the second data object includes a second event identifier that identifies an action associated with the installed application.

### Claim 24 (depends on 23)

The system of claim 23, wherein the user action on the web browser application was a selection of a web link, and wherein the action associated with the installed application is the initial opening of the installed application after installation.

### Claim 25 (depends on 14)

The system of claim 14, wherein the one or more processing units are configured to:
generate a third data object based on the received web event data, wherein the third data object includes the first device ID and a first event identifier, and wherein the first event identifier indicates that the web event data was generated by the user device in response to user selection of a web link; and
generate a fourth data object based on the received application event data, wherein the fourth data object includes the second device ID and a second event identifier, and wherein the second event identifier indicates that the application event data was generated by the user device in response to the opening of the installed application.

### Claim 26 (depends on 14)

The system of claim 14, wherein the one or more processing units are configured to:
generate a third data object based on the received web event data, wherein the third data object includes the first device ID;
generate a fourth data object based on the received application event data, wherein the fourth data object includes the second device ID;
receive subsequent application event data from the user device, wherein the subsequent application event data includes the first device ID and the second device ID; and
in response to receiving the subsequent application event data, generate a fifth data object based on data included in the first data object, the second data object, the third data object, the fourth data object, and the subsequent application event data.
