System and method for separating content site visitor profiles

Patent metadata

Field	Value
Publication number	US-2026025440-A1
Application number	US-202519255727-A
Country	US
Kind code	A1
Filing date	Jun 30, 2025
Priority date	Aug 30, 2013
Publication date	Jan 22, 2026
Grant date	—

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

1 - 20 . (canceled)

21 . 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 page, the first visitor data comprising the first interaction data and metadata;
identify a first identifier of a first visitor from the first visitor data;
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, the second visitor data comprising a second identifier and the metadata;
determine, from at least the first identifier and the second identifier, that the second visitor data is potentially associated with a second visitor different from the first visitor; and
in response to determining that the second visitor data is potentially associated with the second visitor different from the first visitor, add at least some of the second interaction data to a second visitor profile.

22 . The system of claim 21 , wherein the second interaction data comprises a plurality of events, wherein each event of the plurality of events is associated with a timestamp, and wherein the hardware processor is further programmed to:
determine, from the plurality of events, a subset of events where each event from the subset of events has an associated timestamp that satisfies a time threshold, wherein the at least some of the second interaction data comprises the subset of events.

23 . The system of claim 21 , wherein the at least some of the second interaction data comprises a plurality of events, and wherein adding the at least some of the second interaction data to the second visitor profile further comprises:
reprocessing each event from the plurality of events for the second visitor profile; and adding a visitor attribute to the second visitor profile from at least some of the plurality of events.

24 . The system of claim 21 , wherein determining that the second visitor data is potentially associated with the second visitor different from the first visitor further comprises applying a textual analysis technique to the first identifier and the second identifier.

25 . The system of claim 21 , wherein the hardware processor is further programmed to:
determine a time period configuration; determine a visitor attribute from the at least some of the second interaction data and other interaction data within the time period configuration; and add the visitor attribute to the second visitor profile.

26 . The system of claim 21 , wherein the hardware processor is further programmed to:
determine that at least some of the second interaction data satisfies and other interaction data satisfies a series of steps from a visitor attribute configuration; and add a visitor attribute associated with the visitor attribute configuration to the second visitor profile.

27 . 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 page, the first visitor data comprising the first interaction data and metadata;
identifying a first identifier of a first visitor from the first visitor data;
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, the second visitor data comprising a second identifier and the metadata;
determining, from at least the first identifier and the second identifier, that the second visitor data is potentially associated with a second visitor different from the first visitor; and
in response to determining that the second visitor data is potentially associated with the second visitor different from the first visitor, adding at least some of the second interaction data to a second visitor profile.

28 . The method of claim 27 , wherein the second interaction data comprises a plurality of events, wherein each event of the plurality of events is associated with a timestamp, further comprising:
determining, from the plurality of events, a subset of events where each event from the subset of events has an associated timestamp that satisfies a time threshold, wherein the at least some of the second interaction data comprises the subset of events.

29 . The method of claim 27 , wherein the at least some of the second interaction data comprises a plurality of events, and wherein adding the at least some of the second interaction data to the second visitor profile further comprises:
reprocessing each event from the plurality of events for the second visitor profile; and adding a visitor attribute to the second visitor profile from at least some of the plurality of events.

30 . The method of claim 27 , wherein determining that the second visitor data is potentially associated with the second visitor different from the first visitor further comprises applying a textual analysis technique to the first identifier and the second identifier.

31 . The method of claim 27 , further comprising:
determining a time period configuration; determining a visitor attribute from the at least some of the second interaction data and other interaction data within the time period configuration; and adding the visitor attribute to the second visitor profile.

32 . The method of claim 27 , further comprising:
determining that at least some of the second interaction data satisfies and other interaction data satisfies a series of steps from a visitor attribute configuration; and adding a visitor attribute associated with the visitor attribute configuration to the second visitor profile.

33 . The method of claim 32 , wherein the series of steps are time ordered.

34 . Non-transitory physical computer storage comprising instructions stored thereon that, when executed by a hardware processor, can be 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 page, the first visitor data comprising the first interaction data and metadata; identifying a first identifier of a first visitor from the first visitor data; 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, the second visitor data comprising a second identifier and the metadata; determining, from at least the first identifier and the second identifier, that the second visitor data is potentially associated with a second visitor different from the first visitor; and in response to determining that the second visitor data is potentially associated with the second visitor different from the first visitor, adding at least some of the second interaction data to a second visitor profile.

35 . The non-transitory physical computer storage of claim 34 , wherein the second interaction data comprises a plurality of events, wherein each event of the plurality of events is associated with a timestamp, and wherein the process further comprises:
determining, from the plurality of events, a subset of events where each event from the subset of events has an associated timestamp that satisfies

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