System and method for separating content site visitor profiles

Patent metadata

Field	Value
Publication number	US-2016269497-A1
Application number	US-201615067089-A
Country	US
Kind code	A1
Filing date	Mar 10, 2016
Priority date	Mar 11, 2015
Publication date	Sep 15, 2016
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

What is claimed:

1 . A method of managing content site visitor profiles, the method comprising:
under control of a hardware processor:
receiving first visitor data from a first tag embedded within a first content page, the first visitor data comprising a cookie-derived visitor identifier associated with a first visitor visiting the first content page;
identifying a first identifier of the first visitor from the first visitor data;
adding at least some of the first visitor data to a first visitor profile;
receiving second visitor data from a second tag embedded within a second content page, the second visitor data comprising the cookie-derived visitor identifier;
identifying a second identifier from the second visitor data;
determining whether the first and second identifiers are different; and
in response to determining that the first and second identifiers are different, adding at least some of the second visitor data to a second visitor profile different from the first visitor profile.

2 . The method of claim 1 , wherein the first identifier or the second identifier comprises a persistent identifier.

3 . The method of claim 1 , wherein the first identifier or the second identifier comprises an email address, a social network identifier, or a login credential.

4 . The method of claim 1 , wherein the first identifier or the second identifier comprises a phone number or a mailing address.

5 . The method of claim 1 , further comprising:
receiving third visitor data from a third tag embedded within a third content page, the third visitor data comprising the cookie-derived visitor identifier; identifying the second identifier from the third visitor data; and adding at least some of the third visitor data to the second visitor profile and not adding the third visitor data to the first visitor profile.

6 . The method of claim 1 , wherein the first and second visitor profiles are configured so that the 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 content pages are the same content page, and the first and second tags are separate instances of the same tag.

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

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

10 . A system for managing content site visitor profiles, the system comprising:
a memory device configured to store a first visitor profile associated with a first visitor to a content page, the first visitor profile being associated with a first persistent identifier; and a hardware processor configured to:
access the first visitor profile from the memory device,
update the first visitor profile based at least on visitor data comprising interaction data regarding interactions with the content page, the visitor data being obtained from a tag embedded in the content page,
identify a second persistent identifier from the visitor data, and
in response to determining that the first and second persistent identifiers are different, add the 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 the same computing device.

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

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

14 . The system of claim 10 , wherein the first persistent identifier or the second persistent 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:
creating a first visitor profile based at least on first visitor data comprising first interaction data regarding first interactions of a first visitor with a first content page, the first visitor data being obtained from a first tag embedded in the first content page, the first visitor profile being associated with a first persistent identifier; receiving second visitor data comprising second interaction data regarding second interactions with a second content page, the second visitor data being obtained from a second tag embedded in the second content page, the second visitor data being initially associated with the first visitor profile; identifying a second persistent identifier from the second visitor data; determining that the second persistent identifier is associated with a second visitor different from the first visitor based at least on a comparison of the first and second persistent identifiers; and adding the second interaction data to a second visitor profile associated with the second visitor.

16 . The non-transitory physical computer storage of claim 15 , wherein the first persistent identifier or the second persistent identifier comprises an email address, a social network identifier, a phone number, a mailing address, or a login credential.

17 . The non-transitory physical computer storage of claim 15 , wherein the process further comprises:
receiving third visitor data comprising third interaction data regarding third interactions with a third content page, the third visitor data being obtained from a third tag embedded in the third content page; identifying the second persistent identifier from the third visitor data; and adding the third interaction data to the second visitor profile.

18 . The non-transitory physical computer storage of claim 15 , wherein the process further comprises:
in response to determining that the second persistent identifier is associated with the second visitor, removing the second interaction data from the first visitor profile.

19 . The non-transitory physical computer storage of claim 15 , wherein the first and second content pages are the same content page, and the first and second tags are separate instances of the same tag.

20 . The non-transitory physical computer storage of claim 15 , wherein the second visitor data is received in response to the second content page being accessed by a computing device previously used to access the first content page.

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/306 Primary

  User profiles · CPC title

• H04L67/02

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

• H04L67/22 Primary

  Electricity · mapped topic

• H04L67/535 Primary

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