IP Library Granted Patent US 12,028,429
Granted Patent B2
US 12,028,429 · App. 18/345,730 · Granted Jul 2, 2024

System and method for separating content site visitor profiles

Inventors: Charles Glommen (Oceanside, CA); Benjamin Richard Williams, II (San Diego, CA)
Assignee: Tealium Inc.
H04L67/535H04L67/02H04L67/146H04L67/306
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,028,429
App. No.
18/345,730
Granted
Jul 2, 2024
Kind
B2
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.

Claims (69)

1. A system comprising:

non-transitory physical computer storage; and

a computer hardware processor in a physical computing device, the computer hardware processor being in communication with the non-transitory physical computer storage and configured to:

receive first visitor data associated with a first content page, the first visitor data comprising a first cookie-derived identifier, a first Internet Protocol (IP) address, or a first hardware address;

identify a first identifier for a first visitor from the first visitor data;

add at least some of the first visitor data to a first visitor profile associated with the first identifier and the first visitor;

receive, via a tag associated with a second content page, a login credential associated with the second content page, the login credential comprising a second identifier;

receive second visitor data associated with the second content page, the second visitor data comprising (i) the first cookie-derived identifier, the first IP address, or the first hardware address and (ii) the second identifier;

determine, based at least in part on that the first identifier and the second identifier, that the second visitor data is potentially associated with a second visitor different from the first visitor associated with the first visitor data; and

in response to determining that the second visitor data is potentially associated with the second visitor different from the first visitor associated with the first visitor data, add at least some of the second visitor data to a second visitor profile different from the first visitor profile.

2. The system of claim 1 , wherein determining that the second visitor data is potentially associated with the second visitor comprises:

determining that the first identifier and the second identifier are different, wherein determining that the first identifier and the second identifier are different comprises:

performing a textual comparison between the first identifier and the second identifier.

3. The system of claim 2 , wherein the first identifier is associated with a first identifier type different from a second identifier type, and the second identifier is associated with the second identifier type.

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

5. The system of claim 1 , wherein the computer hardware processor is further configured to:

determine a first timestamp associated with the second visitor data;

determine a second timestamp associated with third visitor data that comprises the first cookie-derived identifier, the first IP address, or the first hardware address;

determine that a first difference between the first timestamp and the second timestamp satisfies a threshold; and

add at least some of the third visitor data to the second visitor profile.

6. The system of claim 5 , wherein the second timestamp is earlier than the first timestamp.

7. The system of claim 5 , wherein the computer hardware processor is further configured to:

determine a third timestamp associated with the first visitor data;

determine a fourth timestamp associated with fourth visitor data that comprises the first cookie-derived identifier, the first IP address, or the first hardware address;

determine that a second difference between the third timestamp and the fourth timestamp satisfies the threshold; and

add at least some of the fourth visitor data to the first visitor profile.

8. The system of claim 7 , wherein the fourth timestamp is earlier than the third timestamp.

9. The system of claim 1 , wherein the computer hardware processor is further configured to:

receive third visitor data that comprises the first cookie-derived identifier, the first IP address, or the first hardware address;

identify that the third visitor data indicates a log out associated with the login credential; and

add at least some of the third visitor data to the first visitor profile.

10. The system of claim 1 , wherein the computer hardware processor is further configured to:

receive third visitor data associated with a third content page, the third visitor data comprising a second cookie-derived identifier, a second IP address, or a second hardware address;

identify the second identifier for the second visitor from the third visitor data; and

add at least some of the third visitor data to the second visitor profile associated with the second identifier and the second visitor.

11. A method comprising:

under control of a hardware processor:

receiving first visitor data associated with a first content page, the first visitor data comprising a first cookie-derived identifier, a first Internet Protocol (IP) address, or a first hardware address;

identifying a first identifier for a first visitor from the first visitor data;

adding at least some of the first visitor data to a first visitor profile associated with the first identifier and the first visitor;

receiving, via a tag associated with a second content page, a login credential associated with the second content page, the login credential comprising a second identifier;

receiving second visitor data associated with the second content page, the second visitor data comprising (i) the first cookie-derived identifier, the first IP address, or the first hardware address and (ii) the second identifier;

determining, based at least in part on that the first identifier and the second identifier, that the second visitor data is potentially associated with a second visitor different from the first visitor associated with the first visitor data; and

in response to determining that the second visitor data is potentially associated with the second visitor different from the first visitor associated with the first visitor data, adding at least some of the second visitor data to a second visitor profile different from the first visitor profile.

12. The method of claim 11 , wherein determining that the second visitor data is potentially associated with the second visitor comprises:

determining that the first identifier and the second identifier are different, wherein determining that the first identifier and the second identifier are different comprises:

performing a textual comparison between the first identifier and the second identifier.

13. The method of claim 12 , wherein the first identifier is associated with a first identifier type different from a second identifier type, and the second identifier is associated with the second identifier type.

14. The method of claim 11 , wherein the login credential comprises an email address, a social network identifier, username, or a phone number.

15. The method of claim 11 , further comprising:

determining a first timestamp associated with the second visitor data;

determining a second timestamp associated with third visitor data that comprises the first cookie-derived identifier, the first IP address, or the first hardware address;

determining that a first difference between the first timestamp and the second timestamp satisfies a threshold; and

adding at least some of the third visitor data to the second visitor profile.

16. The method of claim 15 , wherein the second timestamp is earlier than the first timestamp.

17. The method of claim 15 , further comprising:

determining a third timestamp associated with the first visitor data;

determining a fourth timestamp associated with fourth visitor data that comprises the first cookie-derived identifier, the first IP address, or the first hardware address;

determining that a second difference between the third timestamp and the fourth timestamp satisfies the threshold; and

adding at least some of the fourth visitor data to the first visitor profile.

18. The method of claim 17 , wherein the fourth timestamp is earlier than the third timestamp.

19. The method of claim 11 , further comprising:

receiving third visitor data that comprises the first cookie-derived identifier, the first IP address, or the first hardware address;

identifying that the third visitor data indicates a log out associated with the login credential; and

adding at least some of the third visitor data to the first visitor profile.

20. The method of claim 11 , further comprising:

receiving third visitor data associated with a third content page, the third visitor data comprising a second cookie-derived identifier, a second IP address, or a second hardware address;

identifying the second identifier for the second visitor from the third visitor data; and

adding at least some of the third visitor data to the second visitor profile associated with the second identifier and the second visitor.

Continuity (16)
Continuation 17493621 · Oct 4, 2021
Continuation 16510482 · Jul 12, 2019
Continuation In Part 16250948 · Jan 17, 2019
Continuation 15698023 · Sep 7, 2017
Continuation 15394469 · Dec 29, 2016
Continuation 15166111 · May 26, 2016
Continuation 15067089 · Mar 10, 2016
Continuation 14456289 · Aug 11, 2014
Continuation 14216801 · Mar 17, 2014
Provisional Application 62131659 · Mar 11, 2015
Provisional Application 61939972 · Feb 14, 2014
Provisional Application 61900274 · Nov 5, 2013
Provisional Application 61896351 · Oct 28, 2013
Provisional Application 61889876 · Oct 11, 2013
Provisional Application 61872530 · Aug 30, 2013
Related Publication 20240022642A1 · Jan 18, 2024