# US 2023/0273971 A1 · System and method for third party application activity data collection

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

- Number: US 2023/0273971 A1
- Document ID: US20230273971A1
- Status: Published application
- Kind: A1
- Application number: 18/311,908
- Filed: 2023-05-04
- Published: 2023-08-31
- Earliest claimed: 2013-02-10
- Assignees: Wix.com Ltd.
- Applicants: Wix.com Ltd.
- Inventors: Yoav ABRAHAMI; Kfir BLOCH; Nitzan ACHSAF
- Web page: https://patentgrep.com/patent/US20230273971A1

## CPC

- G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system for a website, includes a processor and a unit running on the processor to capture interactions between a user of the website and at least one third party application embedded as an instance in a page of the website and to use the interactions to update a contact record associated with a user. The unit includes a data extractor to extract contact related information from the interactions; and a data merger to merge at least two contact records where the at least two contact records have an association with the same identified user and to merge the extracted contact related information to that of an existing contact record for the identified user according to predefined merging rules.

## Claims

### Claim 1

A system for a website, the system comprising:
a processor; and
a unit running on said processor to capture interactions between a user of said website and at least one third party application embedded as an instance in a page of said website and to use said interactions to update a contact record associated with a user, said unit comprising:
a data extractor to extract contact related information from said interactions; and
a data merger to merge at least two contact records wherein said at least two contact records have an association with the same identified user and to merge said extracted contact related information to that of an existing contact record for said identified user according to predefined merging rules.

### Claim 2 (depends on 1)

The system according to claim 1 and also comprising a contact handler to handle site user identity and to create at least one of: an identifiable new user and an anonymous user during a session of said website.

### Claim 3 (depends on 1)

The system according to claim 1 wherein said data merger comprises at least one of:
a contact identifier to identify at least one of: identical primary ID field values in said at least two contact records, primary key field values within said at least two contact records which are identical when normalized, site users using a cookie, a site user using site login for registered users and a site user through a social login for site users with an account associated with a social network;
a uniter to unite contact related information using at least one of linguistic, syntax, text analysis and consultation with external data sources and services;
a contradiction resolver to resolve contradictions between said at least two contact records according to predefined rules;
a list value creator to create list value fields between said at least two contact records to prevent said contradictions;
a horizontal contact merger to merge two unrelated contact records due to a detected common primary ID; and
a vertical contact merger to merge contact related information for an anonymous user with a registered user according to a login or registration which connects the two.

### Claim 4 (depends on 3)

The system according to claim 3 and wherein said horizontal contact merger comprises a virtual horizontal merger to maintain at least two contact records as separate and to link them together so they are marked as representing the same user.

### Claim 5 (depends on 3)

The system according to claim 3 and wherein said vertical contact merger comprises a virtual vertical merger to maintain an anonymous user and a user associated with a registered user as separate and to link them together so they are marked as representing the same user.

### Claim 6 (depends on 1)

The system according to claim 1 and further comprising a data and permissions handler to handle privacy protection and permissions of said contact related information.

### Claim 7 (depends on 1)

The system according to claim 1 and further comprising at least one database to store contact records.

### Claim 8

A method for a website, the method comprising:
capturing interactions between a user of said website and at least one third party application embedded as an instance in a page of said website; and
using said interactions to update a contact record associated with said user, said capturing and using comprising:
extracting contact related information from said interactions;
merging at least two contact records wherein said at least two contact records have an association with the same identified user; and
merging said extracted contact related information to an existing contact record for said identified user according to predefined merging rules.

### Claim 9 (depends on 8)

The method according to claim 8 and also comprising handling site user identity and creating at least one of an identifiable new user and an anonymous user during a session of said website.

### Claim 10 (depends on 8)

The method according to claim 8 wherein said merging at least two contact records comprises at least one of:
identifying at least one of: identical primary ID field values in said at least two contact records, primary key field values within said at least two contact records which are identical when normalized, site users using a cookie, a site user using site login for registered users and a site user through a social login for site users with an account associated with a social network;
uniting contact related information using at least one of linguistic, syntax, text analysis and consultation with external data sources and services;
resolving contradictions between said at least two contact records according to predefined rules;
creating list value fields between said at least two contact records to prevent said contradictions;
merging two unrelated contact records due to a detected common primary ID; and
merging contact related information for an anonymous user with a registered user according to a login or registration which connects the two.

### Claim 11 (depends on 10)

The method according to claim 10 and wherein said merging two unrelated contact records due to a detected common primary ID comprises maintaining at least two contact records as separate and linking them together so they are marked as representing the same user.

### Claim 12 (depends on 10)

The method according to claim 10 and wherein said merging contact related information for an anonymous user comprises maintaining an anonymous user and a user associated with a registered user as separate and linking them together so they are marked as representing the same user.

### Claim 13 (depends on 8)

The method according to claim 8 and further comprising handling privacy protection and permissions of said contact related information.

### Claim 14 (depends on 8)

The method according to claim 8 and further comprising storing contact records in a least one database.
