System and method for audience segment profiling and targeting
A system and method for audience segment profiling and targeting. The method includes providing a Web server and receiving each of the inbound request messages from one of the Web browsers in the Web server. Selected data contained in each of the inbound request messages is extracted including a UserAgent string and an IP address associated with the inbound request message. A hash ID is generated from the extracted data to uniquely identify each user associated with inbound request messages which is used to augment traditional means for identifying a user such as using a LSO or Cookie when such a LSO or Cookie are not present.
1. A computer implemented method for identifying a user from content extracted from a plurality of inbound HTTP request messages sent to a Web server from a plurality of remotely located Web browsers via the Internet, the method consisting of:
providing a Web server, the Web server including a memory, a processor in communication therewith, wherein the processor is configured by the instructions executing therein;
receiving a first plurality of the inbound request messages from a first of said Web browsers by the configured processor of said Web server;
extracting, by the configured processor, data contained in each of said plurality of inbound request messages including a UserAgent and IP address associated with each of said plurality of inbound request messages, wherein the UserAgent identifies the first particular Web browser transmitting the plurality of inbound HTTP request messages;
generating, by the configured processor, a hash from said extracted data to uniquely identify each user associated with said plurality of inbound request messages; and
determining whether the IP address associated with the first plurality of inbound messages having one of the hashes was associated with other previously extracted inbound HTTP request messages having a different hash,
whereby the user is identified from one of the hashes generated from the extracted data whether the IP address associated with the first plurality of inbound messages was associated with other inbound HTTP request messages having a different hash.
2. A method as recited in claim 1 , further including the steps of:
providing a database coupled to said web server; and
storing, by the configured processor, said generated hash in said database with other data extracted from said inbound request messages and augmenting said generated hash to provide profile information associated with each said generated hash, wherein said generated hash is stored in association with a previously generated hash if said generated hash and the previously generated hash match.
3. A method as recited in claim 2 wherein the step of extracting data includes extracting a Cookie from said inbound request messages to augment said generated hash to uniquely identify each user associated with said inbound request messages.
4. A method as recited in claim 2 wherein the step of extracting data includes extracting a Flash Local Stored Object (LSO) from said inbound request messages to augment said generated hash to uniquely identify a user associated with said inbound request messages.
5. A method as recited in claim 2 further including the step of analyzing said generated hash to determine if said user is using a firewall having a static Internet Protocol (IP) address.
6. A method as recited in claim 2 further including the step of analyzing said generated hash to determine if said user is using multiple Internet Protocol (IP) addresses to connect to the Internet.
7. A system for extracting selected content in a plurality of HTTP request messages from a plurality of remotely located Web browsers presented to a Web server having a processor and a memory, consisting of:
an Internet connection for receiving the plurality of HTTP request messages in the Web server;
instructions are stored in the memory and executing in the processor of the Web server operative to:
extract data contained in each of the plurality of HTP request messages including a UserAgent and an IP address for the first plurality of HTTP request messages, wherein the UserAgent identifies a first particular Web browser transmitting a first plurality of the HTTP request messages;
generate a hash from the extracted data to uniquely identify each user associated with said inbound request messages; and
determine whether the IP address associated with the first plurality of inbound messages have one of the hashes was associated with other previously extracted inbound HTTP request messages having a different hash,
whereby the user is identified from one of the hashes generated from the extracted data whether the IP address associated with the first plurality of inbound messages was associated with other inbound HTTP request messages having a different hash.
8. A method as recited in claim 1 , further including the steps:
determining if said generated hash matches a previously generated hash stored in a database in association with a user profile record, and if not, generating the user profile record;
storing, by the configured processor, said generated hash in said database with other data extracted from said inbound request messages augmenting said generated hash to provide profile information associated with said generated hash, wherein said generated hash is stored in association with the user profile record.