System and method for separating content site visitor profiles

Patent metadata

Field	Value
Publication number	US-12348592-B2
Application number	US-202418759572-A
Country	US
Kind code	B2
Filing date	Jun 28, 2024
Priority date	Aug 30, 2013
Publication date	Jul 1, 2025
Grant date	Jul 1, 2025

Abstract

Embodiments of the systems described herein can implement one or more visitor tearing processes. Visitor tearing can include, among other things, one or more processes by which multiple visitors that may appear to be the same visitor may be separated into different visitor profiles due to the leveraging of one or more unique persistent identifiers.

First claim

What is claimed:

1. A method comprising:
under control of a hardware processor:
receiving first visitor data from a container comprising script code that gathered first interaction data indicative of user interactions with a first page,
wherein the first visitor data comprises (i) the first interaction data, (ii) a first identifier, and (iii) a second identifier different from the first identifier;
identifying the first identifier and the second identifier from the first visitor data;
generating a first combined identifier from the first identifier and the second identifier;
adding at least some of the first interaction data to a first visitor profile;
receiving second visitor data from the container comprising the script code that gathered second interaction data indicative of user interactions with a second page,
wherein the second visitor data comprises (i) the second interaction data, (ii) the first identifier, and (iii) a third identifier different from the second identifier;
identifying the first identifier and the third identifier from the second visitor data;
generating a second combined identifier from the first identifier and the third identifier;
determining that the first combined identifier and the second combined identifier are different; and
in response to determining that the first combined identifier and the second combined identifier are different, adding at least some of the second interaction data to a second visitor profile different from the first visitor profile.

2. The method of claim 1 , wherein the first identifier corresponds to a first identifier type different from a second identifier type, and the second identifier corresponds to the second identifier type.

3. The method of claim 2 , wherein the first identifier type and the second identifier type each correspond to a different one of an email address type, a social network identifier type, a login credential type, a phone number type, or a mailing address type.

4. The method of claim 1 , wherein the first identifier comprises an email address, a social network identifier, a login credential, a phone number, or a mailing address.

5. The method of claim 1 , further comprising:
receiving third visitor data from the container comprising the script code that gathered third interaction data indicative of user interactions with a third page;
identifying the third identifier from the third visitor data; and
adding at least some of the third interaction data to the second visitor profile and not adding the third interaction data to the first visitor profile.

6. The method of claim 1 , wherein the first and second visitor profiles are configured so that a first visitor associated with the first visitor profile is considered to be different from a second visitor associated with the second visitor profile.

7. The method of claim 1 , wherein the first and second pages are the same page.

8. The method of claim 1 , wherein the first and second visitor data are received in response to the first and second pages being accessed by a first computing device.

9. The method of claim 1 , further comprising, in response to determining that the first combined identifier and the second combined identifier are different, not adding the second interaction data to the first visitor profile.

10. A system comprising:
a hardware processor programmed to:
receive first visitor data from a container comprising script code that gathered first interaction data indicative of user interactions with a first page,
wherein the first visitor data comprises (i) the first interaction data, (ii) a first identifier, and (iii) a second identifier different from the first identifier;
identify the first identifier and the second identifier from the first visitor data;
generate a first combined identifier from the first identifier and the second identifier;
add at least some of the first interaction data to a first visitor profile;
receive second visitor data from the container comprising the script code that gathered second interaction data indicative of user interactions with a second page,
wherein the second visitor data comprises (i) the second interaction data, (ii) the first identifier, and (iii) a third identifier different from the second identifier;
identify the first identifier and the third identifier from the second visitor data;
generate a second combined identifier from the first identifier and the third identifier;
determine that the first combined identifier and the second combined identifier are different; and
in response to determining that the first combined identifier and the second combined identifier are different, adding at least some of the second interaction data to a second visitor profile different from the first visitor profile.

11. The system of claim 10 , wherein the first and second visitor profiles are associated with a first computing device.

12. The system of claim 10 , wherein the hardware processor is programmed to:
in response to determining that the first combined identifier and the second combined identifier are different, remove the second interaction data from the first visitor profile.

13. The system of claim 10 , wherein the first identifier corresponds to a first identifier type different from a second identifier type, and the second identifier corresponds to the second identifier type.

14. The system of claim 10 , wherein the first identifier comprises an email address, a social network identifier, a phone number, a mailing address, or a login credential.

15. Non-transitory physical computer storage comprising instructions stored thereon that, when executed by a hardware processor, are configured to implement a process comprising:
receiving first visitor data from a container comprising script code that gathered first interaction data indicative of user interactions with a first page,
wherein the first visitor data comprises (i) the first interaction data, (ii) a first identifier, and (iii) a second identifier different from the first identifier;
identifying the first identifier and the second identifier from the first visitor data;
generating a first combined identifier from the first identifier and the second identifier;
adding at least some of the first interaction data to a first visitor profile;
receiving second visitor data from the container comprising the script code that gathered second interaction data indicative of user interactions with a second page,
wherein the second visitor data comprises (i) the second interaction data, (ii) the first identifier, and (iii) a third identifier different from the second identifier;
identifying the first identifier and the third identifier from the second visitor data;
generating a second combined identifier from the first identifier and the third identifier;
determining that the first combined identifier and the second combined identifier are different; and
in response to determining that the first combined identifier and the second combined identifier are different, adding at least some of the second interaction data to a second visitor profile different from the first visitor profile.

16. The non-transitory physical computer storage of claim 15 , wherein the first identifier corresponds to a first identifier type different from a second identifier type, and the second identifier corresponds to the second identifier type.

17. The non-transitory physical computer storage of claim 15 , wherein the first identifier comprises an email address, a social network identifier, a phone number, a mailing address,

Assignees

• Tealium Inc

Inventors

• Glommen Charles
• Williams Ii Benjamin Richard

Classifications

• H04L67/146

  Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding · CPC title

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L67/306 Primary

  User profiles · CPC title

• H04L67/535 Primary

  Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34) · CPC title