System and method for separating content site visitor profiles
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.
1. A system comprising:
a first device comprising a first hardware processor configured to:
receive first visitor data from a first tag associated with a first content page, the first visitor data comprising a cookie-derived visitor identifier associated with a first visitor visiting the first content page,
identify a first identifier of the first visitor from the first visitor data, and
add at least some of the first visitor data to a first visitor profile; and
a second device comprising a second hardware processor configured to:
detect, via a second tag associated with a second content page, a login credential associated with the second content page, the login credential comprising a second identifier, and
transmit, to the first device, second visitor data comprising the cookie-derived visitor identifier and the second identifier,
wherein the first hardware processor is further configured to:
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 detecting the login credential comprises:
reading the login credential from a document object model (DOM) associated with the second content page.
3. 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.
4. The system of claim 1 , wherein the second hardware processor is further configured to:
transmit, to the first device, the first visitor data.
5. The system of claim 1 , wherein the first tag and the second tag are separate instances of a same data collection tag.
6. A method comprising:
under control of a hardware processor:
receiving first visitor data from a first tag associated with 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 associated with a second content page, the second visitor data comprising (i) the cookie-derived visitor identifier and (ii) a second identifier, wherein the second tag received the second identifier from user input provided to the second content page;
determining, based at least in part on 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.
7. The method of claim 6 , 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.
8. The method of claim 7 , wherein determining that the second visitor data is potentially associated with the second visitor is further based at least in part on:
determining that a time difference between (i) a first time associated with the first visitor data and (ii) a second time associated with the second visitor data exceeds a threshold time value.
9. The method of claim 6 , wherein determining that the second visitor data is potentially associated with the second visitor is further based at least in part on:
determining that a time difference between (i) a first time associated with the first visitor data and (ii) a second time associated with the second visitor data exceeds a threshold time value.
10. The method of claim 6 , wherein determining that the second visitor data is potentially associated with the second visitor comprises:
performing a textual comparison between the first identifier and the second identifier.
11. The method of claim 10 , 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.
12. The method of claim 6 , wherein the first tag is configured to read at least some of the first visitor data from a document object model (DOM) associated with the first content page.
13. A system comprising:
a first device comprising a first hardware processor configured to:
receive first visitor data from a first tag associated with a first content page, the first visitor data comprising (i) a cookie-derived visitor identifier associated with a first visitor visiting the first content page and (ii) a first identifier of the first visitor, and
add at least some of the first visitor data to a first visitor profile; and
a second device comprising a second hardware processor configured to:
receive, via a second tag associated with a second content page, user input comprising a second identifier, and
transmit, to the first device, second visitor data comprising the cookie-derived visitor identifier and the second identifier,
wherein the first hardware processor is further configured to:
determine, based at least in part on 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.
14. The system of claim 13 , wherein receiving the user input comprising the second identifier comprises:
detecting, via the second tag, login data from a login process associated with the second content page.
15. The system of claim 14 , wherein detecting the login data comprises:
reading the login data from a document object model (DOM) associated with the second content page.
16. The system of claim 13 , 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.
17. The system of claim 16 , 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.
18. The system of claim 17 , wherein determining that the second visitor data is potentially associated with the second visitor is further based at least in part on:
determining that a time difference between (i) a first time associated with the first visitor data and (ii) a second time associated with the second visitor data exceeds a threshold time value.
19. The system of claim 18 , 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.