EP3693914A1 - Methods and apparatus to determine media impressions - Google Patents
Methods and apparatus to determine media impressions Download PDFInfo
- Publication number
- EP3693914A1 EP3693914A1 EP20166716.9A EP20166716A EP3693914A1 EP 3693914 A1 EP3693914 A1 EP 3693914A1 EP 20166716 A EP20166716 A EP 20166716A EP 3693914 A1 EP3693914 A1 EP 3693914A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- impressions
- cookie
- panelist
- partner
- impression
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
- G06F16/48—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market modelling; Market analysis; Collecting market data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0242—Determining effectiveness of advertisements
- G06Q30/0246—Traffic
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0277—Online advertisement
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/04—Processing captured monitoring data, e.g. for logfile generation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/81—Monomedia components thereof
- H04N21/812—Monomedia components thereof involving advertisement data
Definitions
- An example methods includes detecting a cookie identifier established by a database proprietor at a computing device, determining an impression of media, wherein the impression occurs after the cookie identifier is established, determining a first panelist identifier associated with the impression based on the cookie identifier, determining a second panelist identifier associated with the impression based on determination of a user identity by a panelist meter associated with the computing device, storing an adjustment factor determined by comparing the first panelist identifier and the second panelist identifier.
- the second panelist identifier is different than the first panelist.
- comparing the first panelist identifier and the second panelist identifier comprises incrementing a first count of impressions for a first demographic group associated with the first panelist identifier, incrementing a second count of impressions for a second demographic group associated with the second panelist identifier, wherein the first demographic group and the second demographic group are the same, and dividing the first count by the second count to determine the adjustment factor, wherein the second count is incremented based on impressions associated with a plurality of panelist meters including the panelist meter.
- the impression occurs before detecting a second cookie identifier established by the database proprietor.
- the partner sessions pageview analyzer is further to determine the first panelist identifier by: determining a start of an estimated computing session based on a time at which the cookie identifier is established and determining an end of an estimated computing session based on a time at which a second cookie identifier is established.
- Blumenau disclosed a technique wherein Internet media (e.g., content, advertisements, etc.) to be tracked is tagged with beacon instructions (e.g., tag instructions).
- monitoring instructions are associated with the HTML of the media (e.g., advertisements or other Internet content) to be tracked.
- both the content and the beacon or tag instructions are downloaded to the client either simultaneously (e.g., with the tag instructions present in the HTML) or via subsequent requests (e.g., via execution of a request to retrieve the monitoring instructions embedded in the HTML of the content).
- the tag instructions are, thus, executed whenever the media is accessed, be it from a server or from a cache.
- the login reporting message 118 is shown in the example of FIG. 2 as including the partner A cookie 228, for instances in which the partner A database proprietor 104a has not yet set the partner A cookie 228 in the client device 108, the cookie field 230 is empty in the login reporting message 118. In this manner, the empty cookie field 230 prompts the partner A database proprietor 104a to set the partner A cookie 228 in the client device 108. In such instances, the partner A database proprietor 104a sends the client device 108 a response message (not shown) including the partner A cookie 228 and records the partner A cookie 228 in association with the AME cookie 208.
- the partner cookie map 236 stores partner cookies (e.g., the partner A cookie 228) in association with respective AME cookies (e.g., the AME cookie 208) and respective timestamps (e.g., the timestamp 220).
- the partner cookie map 236 stores a unique user ID (UUID) found in a name-value pair (i.e., a parameter name such as 'user_ID' and a value such as the UUID) of the partner A cookie 228 in association with a unique user ID found in a name-value pair of the AME cookie 208.
- UUID unique user ID
- the tag instructions 304 may be implemented using java script or any other type(s) of executable instruction(s) including, for example, Java, HTML, etc. It should be noted that tagged content such as web pages, and/or any other media are processed the same way as the tagged advertisement 110. That is, for any tagged media, corresponding tag instructions are received in connection with the download of the tagged content and cause a tag request to be sent from the client device that downloaded the tagged content to the impression monitor system 102 (or any other server indicated by the instructions).
- the apparatus 400 is provided with the cookie matcher 402 to match AME user IDs from AME cookies (e.g., the AME cookie 208 of FIGS. 2 and 3 ) from the AME impression logs 122 to AME user IDs in the partner A cookie map 236.
- the apparatus 400 performs such cookie matching to identify registered users of the partner A database proprietor 104a to which the logged impressions are attributable (e.g., partner A registered users for which the impression monitor system 102 set AME cookies as described above in connection with FIG. 2 and tracked impressions as described above in connection with FIG. 3 ).
- the partner cookie map 236 is shown in FIG.
- the apparatus 400 is provided with the demographics associator 404 to associate demographics information from the user accounts database 238 with corresponding partner-based impressions from the partner-based impressions structure 700.
- the demographics associator 404 may retrieve demographics information for partner user IDs noted in the partner user ID column 712 ( FIG. 7 ) and associate the retrieved demographics information with corresponding ones of the records in the partner-based impressions structure 700.
- the cookie status detector 1402, the cookie generator 1404, the timestamp generator 1406, the message generator 1408, the impression logger 1410, the communication interface 1412 and/or, more generally, the example apparatus 102 of FIG. 14 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware.
- any of the cookie status detector 1402, the cookie generator 1404, the timestamp generator 1406, the message generator 1408, the impression logger 1410, the communication interface 1412 and/or, more generally, the example apparatus 102 and/or any of the login event detector 1502, the cookie status detector 1504, the cookie interface 1506, the message generator 1508, the communication interface 1510 and/or, more generally, the example apparatus 202 could be implemented by one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), etc.
- an ad campaign-level age/gender and impression composition data structure 900 is shown, which, in the illustrated example, may be generated by the report generator 412 of FIG. 4 .
- the impression data in the ad campaign-level age/gender and impression composition structure 900 of FIG. 9 corresponds to impressions attributable to registered user of a particular partner database (DB) proprietor (e.g., the partner A database proprietor 104a of FIGS. 1 and 2 or the partner B database proprietor 104b of FIG. 1 ).
- DB partner database
- Similar tables can be generated for content and/or other media. Additionally or alternatively, other media in addition to advertisements may be added to the data structure 900.
- the cookie interface 1506 and/or the message generator 1508 store(s) the AME cookie 208 as a data parameter (e.g., in the payload 232) in the login reporting message 118 (block 1036).
- the message generator 1508 also stores the login timestamp 220 in the login reporting message 118 (e.g., in the payload 232) (block 1038).
- the communication interface 1510 sends the login reporting message 118 to a corresponding partner database proprietor (e.g., the partner A database proprietor 104a) (block 1040).
- the cookie reporter 202 enables the partner A database proprietor 104a to map the partner A cookie 228 to the AME cookie 208 and the login timestamp 220 in the partner cookie map 236 of FIGS. 2 and 5 .
- the example process of FIG. 10 then ends.
- FIG. 16 is a block diagram of an example system 1600 to generate an adjustment factor.
- the system 1600 may generate an adjustment factor to determine more accurate information based on the information generated in accordance with the methods and apparatus described in conjunction with FIGS. 1-15 .
- the example system 1600 includes one or more panelist meter(s) 1602, a datastore 1604, a cookie to panelist matcher 1606, a panelist to session matcher 1608, a partner sessions pageview analyzer 1610, a panelist sessions pageview analyzer 1612, and an adjustment factor generator 1614.
- the program may be embodied in software stored on a tangible computer readable medium such as a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), a BluRay disk, a flash memory, a read-only memory (ROM), a random-access memory (RAM), or a memory associated with the processor 2912, but the entire program and/or parts thereof could alternatively be executed by a device other than the processor 2912 and/or embodied in firmware or dedicated hardware.
- a tangible computer readable medium such as a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), a BluRay disk, a flash memory, a read-only memory (ROM), a random-access memory (RAM), or a memory associated with the processor 2912, but the entire program and/or parts thereof could alternatively be executed by a device other than the processor 2912 and/or embodied in firmware or dedicated hardware.
- the example panelist sessions pageview analyzer 1612 determines pageviews by demographic group (block 2612).
- the pageview information of block 2612 represents the baseline pageview count by demographic information that is assumed to be accurate.
- the recorded panelist member associated with a computer session e.g., determined by prompting a user of a computing device
- the pageviews are then aggregated by demographic group.
- the cookie to panelist matcher 1606 determines if there are additional partner cookies to be processed (block 2710). If there are additional partner cookies to be processed, the next partner cookie is selected (block 2712) and control returns to block 2704 to process the partner cookie. If there are not additional partner cookies to be processed, the process of FIG. 27 completes. The completion of the process of FIG. 27 may result in initiation of the process of FIG. 28 .
- the panelist to session matcher 1608 determines if there are additional partner instances to be processed (block 2808). If there are additional partner cookie instances to be processed, the next partner cookie instance is selected (block 2810). The time of the newly selected cookie instance is recorded as the stop of the session for the previously selected panel member session (block 2812). In other words, the occurrence of each new cookie instance indicates the termination of the previous cookie instance (and thereby the end of a generated panel member browsing session). Control then returns to block 2804 to process the newly selected cookie instance.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- Marketing (AREA)
- General Business, Economics & Management (AREA)
- Game Theory and Decision Science (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Library & Information Science (AREA)
- Computer Hardware Design (AREA)
- Information Transfer Between Computers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Storage Device Security (AREA)
Abstract
Description
- This patent claims priority to
U.S. Provisional Patent Application Serial No. 61/454,326, filed on March 18, 2011 - The present disclosure relates generally to monitoring media and, more particularly, to methods and apparatus to determine media impressions.
- Traditionally, audience measurement entities determine audience engagement levels for media programming based on registered panel members. That is, an audience measurement entity enrolls people who consent to being monitored into a panel. The audience measurement entity then monitors those panel members to determine media (e.g., television programs or radio programs, movies, DVDs, advertisements, etc.) exposed to those panel members. In this manner, the audience measurement entity can determine exposure measures for different media based on the collected media measurement data.
- Techniques for monitoring user access to Internet resources such as web pages, advertisements and/or other content has evolved significantly over the years. Some known systems perform such monitoring primarily through server logs. In particular, entities serving media on the Internet can use known techniques to log the number of requests received for their media at their server.
- Example methods and apparatus to determine media impressions are disclosed. An example methods includes detecting a cookie identifier established by a database proprietor at a computing device, determining an impression of media, wherein the impression occurs after the cookie identifier is established, determining a first panelist identifier associated with the impression based on the cookie identifier, determining a second panelist identifier associated with the impression based on determination of a user identity by a panelist meter associated with the computing device, storing an adjustment factor determined by comparing the first panelist identifier and the second panelist identifier. In some examples, the second panelist identifier is different than the first panelist. In some examples, comparing the first panelist identifier and the second panelist identifier comprises incrementing a first count of impressions for a first demographic group associated with the first panelist identifier, incrementing a second count of impressions for a second demographic group associated with the second panelist identifier, wherein the first demographic group and the second demographic group are the same, and dividing the first count by the second count to determine the adjustment factor, wherein the second count is incremented based on impressions associated with a plurality of panelist meters including the panelist meter. In some examples, the impression occurs before detecting a second cookie identifier established by the database proprietor.
- In some examples, determining the first panelist identifier comprises determining a plurality of computing sessions, determining the first estimated panelist identifier associated with a first subset of the computing sessions, determining a third panelist identifier associated with a second subset of the computing sessions, and determining that the cookie identifier is associated with the first panelist identifier because the cookie identifier is established during the first subset of the computing sessions more frequently than the second subset of the computing sessions. In some such examples, determining the first panelist identifier further comprises determining a start of an estimated computing session based on a time at which the cookie identifier is established and determining an end of an estimated computing session based on a time at which a second cookie identifier is established.
- In some examples, determining the impression of the media comprises detecting that the media was received at the computing device. In some examples, the adjustment factor is applied to metering data received from the database proprietor. In some examples, determining adjustment factors for each of a plurality of demographic groups. In some examples, the method further comprises receiving a number of impressions associated with a demographic group from the database proprietor and multiplying the adjustment factor by the number of impressions to determine an adjusted number of impressions.
- In some examples, the method further comprises determining a first content provider and a second content provider associated with a campaign, wherein the adjustment factor is an adjustment factor associated with the first content provider, determining a second adjustment factor, multiplying the adjustment factor by a first number of impressions determined for the first content provider to determine a first adjusted number of impressions, multiplying the second adjustment factor by a second number of impressions determined for the second content provider to determine a second adjusted number of impressions, and adding the first adjusted number of impressions and the second adjusted number of impressions to determine an adjusted number of impressions for the campaign. In some such examples, the method further comprises determining a proportion of campaign impressions associated with the first content provider, wherein the adjusted number of impressions for the campaign is determined based on the proportion campaign impressions associated with the first content provider.
- In some examples, the adjustment factor is indicative of a difference between a number of impressions calculated using a plurality panelist meters and a number of impressions calculated by the database proprietor.
- An example apparatus includes a cookie to panelist matcher to detect a cookie identifier established by a database proprietor at a computing device and to determine a first panelist identifier associated with the cookie identifier, a partner sessions pageview analyzer to determine that a media impression is associated with the first panelist based on the cookie identifier, a panelist sessions pageview analyzer to determine that the media impression is associated with a second panelist identifier based on a determination of a user identity, and an adjustment factor generator to compare the first panelist identifier and the second panelist identifier to determine an adjustment factor and to store the adjustment factor. In some examples, the determination of a user identifier is performed by a panelist meter associated with the computing device. In some examples, the second panelist identifier is different than the first panelist.
- In some examples, the apparatus comprises a partner sessions pageview analyzer to increment a first count of impressions for a first demographic group associated with the first panelist identifier, a panelist sessions pageview analyzer to increment a second count of impressions for a second demographic group associated with the second panelist identifier, wherein the first demographic group and the second demographic group are the same, and the adjustment factor generator compares the first panelist identifier and the second panelist identifier by dividing the first count by the second count to determine the adjustment factor. In some such examples, the panelist sessions pageview analyzer is to increment the second count based on impressions associated with a plurality of panelist meters including the panelist meter.
- In some examples, the impression occurs before the cookie to panelist matcher detects a second cookie identifier established by the database proprietor. In some examples, the partner sessions pageview analyzer is to determine the first panelist identifier by: determining a plurality of computing sessions, determining the first estimated panelist identifier associated with a first subset of the computing sessions, determining a third panelist identifier associated with a second subset of the computing sessions, and determining that the cookie identifier is associated with the first panelist identifier because the cookie identifier is established during the first subset of the computing sessions more frequently than the second subset of the computing sessions. In some such examples, the partner sessions pageview analyzer is further to determine the first panelist identifier by: determining a start of an estimated computing session based on a time at which the cookie identifier is established and determining an end of an estimated computing session based on a time at which a second cookie identifier is established.
- In some examples, the cookie to panelist matcher is to determine the impression of the media by detecting that the media was received at the computing device. In some examples, the adjustment factor is applied to metering data received from the database proprietor. In some examples, the adjustment factor generator is to determine adjustment factors for each of a plurality of demographic groups. In some examples, the adjustment factor generator is to: receive a number of impressions associated with a demographic group from the database proprietor and multiply the adjustment factor by the number of impressions to determine an adjusted number of impressions.
- In some examples, the adjustment factor generator is to: determine a first content provider and a second content provider associated with a campaign, wherein the adjustment factor is an adjustment factor associated with the first content provider, determine a second adjustment factor, multiply the adjustment factor by a first number of impressions determined for the first content provider to determine a first adjusted number of impressions, multiply the second adjustment factor by a second number of impressions determined for the second content provider to determine a second adjusted number of impressions, and add the first adjusted number of impressions and the second adjusted number of impressions to determine an adjusted number of impressions for the campaign. In some such examples, the adjustment factor generator is to determine a proportion of campaign impressions associated with the first content provider, wherein the adjusted number of impressions for the campaign is determined based on the proportion campaign impressions associated with the first content provider.
- In some examples, the adjustment factor is indicative of a difference between a number of impressions calculated using a plurality panelist meters and a number of impressions calculated by the database proprietor.
- An example a tangible computer readable medium stores instructions that, when executed causes a machine to: detect a cookie identifier established by a database proprietor at a computing device, determine an impression of media, wherein the impression occurs after the cookie identifier is established, determine a first panelist identifier associated with the impression based on the cookie identifier, determine a second panelist identifier associated with the impression based on determination of a user identity by a panelist meter associated with the computing device, and store an adjustment factor determined by comparing the first panelist identifier and the second panelist identifier. In some examples, the second panelist identifier is different than the first panelist.
- In some examples, the instructions, when executed, compare the first panelist identifier and the second panelist identifier by: incrementing a first count of impressions for a first demographic group associated with the first panelist identifier, incrementing a second count of impressions for a second demographic group associated with the second panelist identifier, wherein the first demographic group and the second demographic group are the same, and dividing the first count by the second count to determine the adjustment factor. In some such examples, the second count is incremented based on impressions associated with a plurality of panelist meters including the panelist meter.
- In some examples, the impression occurs before detecting a second cookie identifier established by the database proprietor. In some examples, the instructions, when executed, determine the first panelist identifier by: determining a plurality of computing sessions, determining the first estimated panelist identifier associated with a first subset of the computing sessions, determining a third panelist identifier associated with a second subset of the computing sessions, and determining that the cookie identifier is associated with the first panelist identifier because the cookie identifier is established during the first subset of the computing sessions more frequently than the second subset of the computing sessions. In some such examples, the instructions, when executed, determine the first panelist identifier further by: determining a start of an estimated computing session based on a time at which the cookie identifier is established and determining an end of an estimated computing session based on a time at which a second cookie identifier is established.
- In some examples, the instructions, when executed, determine the impression of the media by detecting that the media was received at the computing device. In some examples, the adjustment factor is applied to metering data received from the database proprietor. In some examples, the instructions, when executed, cause the machine to determine adjustment factors for each of a plurality of demographic groups. In some examples, the instructions, when executed, cause the machine to: receiving a number of impressions associated with a demographic group from the database proprietor and multiplying the adjustment factor by the number of impressions to determine an adjusted number of impressions.
- In some examples, the instructions, when executed, cause the machine to: determine a first content provider and a second content provider associated with a campaign, wherein the adjustment factor is an adjustment factor associated with the first content provider, determine a second adjustment factor, multiply the adjustment factor by a first number of impressions determined for the first content provider to determine a first adjusted number of impressions, multiply the second adjustment factor by a second number of impressions determined for the second content provider to determine a second adjusted number of impressions, and add the first adjusted number of impressions and the second adjusted number of impressions to determine an adjusted number of impressions for the campaign. In some such examples, the instructions, when executed, cause the machine to determine a proportion of campaign impressions associated with the first content provider, wherein the adjusted number of impressions for the campaign is determined based on the proportion campaign impressions associated with the first content provider.
- In some examples, the adjustment factor is indicative of a difference between a number of impressions calculated using a plurality panelist meters and a number of impressions calculated by the database proprietor. In some examples, determining the first panelist identifier further comprises: determining a start of an estimated computing session based on a time at which the cookie identifier is established and determining an end of an estimated computing session based on a time at which a second cookie identifier is established.
-
-
FIG. 1 depicts an example system to determine advertisement and/or media impressions using distributed demographic information. -
FIG. 2 depicts an example manner of reporting cookies to an audience measurement entity and database proprietor(s) in response to users logging in to website(s) of the database proprietor(s). -
FIG. 3 depicts an example manner in which a web browser can report impressions to an impression monitor of the example system ofFIG. 1 . -
FIG. 4 is an example apparatus that may be used to associate impressions with demographics of users registered with one or more database proprietors. -
FIG. 5 is an example partner cookie map that may be used by an Internet service database proprietor to map user identifiers associated with an audience measurement entity with user identifiers of users registered with the Internet service database proprietor. -
FIG. 6 is an example impressions table generated by the impression monitor system of the example system ofFIG. 1 to correlate impressions with user identifiers of monitored audience members. -
FIG. 7 depicts an example partner-based impressions table generated by an Internet service database proprietor to correlate impressions with user identifiers of registered users of the Internet service database proprietors. -
FIG. 8 depicts an example impressions table showing quantities of impressions associated with monitored users. -
FIG. 9 depicts an example campaign-level age/gender and impression composition table generated by a database proprietor. -
FIG. 10 is a flow diagram representative of example machine readable instructions that may be executed to report login events and user cookies to database proprietors. -
FIG. 11 is a flow diagram representative of example machine readable instructions that may be executed to map audience measurement entity (AME) cookie identifiers to user identifiers of users registered with a database proprietor. -
FIG. 12 is a flow diagram representative of example machine readable instructions that may be executed to log impressions. -
FIG. 13 is a flow diagram representative of example machine readable instructions that may be executed to generate demographics-based impressions reports. -
FIG. 14 is an example apparatus that may be used to implement the impression monitor ofFIGS. 1-3 . -
FIG. 15 is an example apparatus that may be used to implement a cookie reporter ofFIG. 2 . -
FIG. 16 is a block diagram of an example system to generate an adjustment factor. -
FIGS. 17 to 25 illustrate example tables that may be generated by the system ofFIG. 16 . -
FIGS. 26 to 28 are flow diagrams representative of example machine readable instructions that may be executed generate adjustment factor(s). -
FIG. 29 is an example processor system that can be used to execute the example instructions ofFIGS. 10-13 and/or 26-28 to implement the example apparatus and systems ofFIGS. 1 ,2 ,3 ,4 , and/or 16. - Techniques for monitoring user access to Internet resources such as web pages, advertisements, content and/or other media has evolved significantly over the years. At one point in the past, such monitoring was done primarily through server logs. In particular, entities serving media on the Internet would log the number of requests received for their media at their server. Basing Internet usage research on server logs is problematic for several reasons. For example, server logs can be tampered with either directly or via zombie programs that repeatedly request media from the server to increase the server log counts. Secondly, media is sometimes retrieved once, cached locally and then repeatedly viewed from the local cache without involving the server in the repeat viewings. Server logs cannot track these views of cached media. Thus, server logs are susceptible to both over-counting and under-counting errors.
- The inventions disclosed in Blumenau,
US Patent 6,108,637 , fundamentally changed the way Internet monitoring is performed and overcame the limitations of the server side log monitoring techniques described above. For example, Blumenau disclosed a technique wherein Internet media (e.g., content, advertisements, etc.) to be tracked is tagged with beacon instructions (e.g., tag instructions). In particular, monitoring instructions are associated with the HTML of the media (e.g., advertisements or other Internet content) to be tracked. When a client requests the media, both the content and the beacon or tag instructions are downloaded to the client either simultaneously (e.g., with the tag instructions present in the HTML) or via subsequent requests (e.g., via execution of a request to retrieve the monitoring instructions embedded in the HTML of the content). The tag instructions are, thus, executed whenever the media is accessed, be it from a server or from a cache. - The tag instructions cause monitoring data reflecting information about the access to the media to be sent from the client that downloaded the media to a monitoring entity. The monitoring entity may be an audience measurement entity that did not provide the media to the client and who is a trusted third party for providing accurate usage statistics (e.g., The Nielsen Company, LLC). Advantageously, because the tag instructions are associated with the media (e.g., embedded in or otherwise linked to some portion of the media) and executed by the client browser whenever the media is accessed, the monitoring information is provided to the audience measurement company irrespective of whether the client is a panelist of the audience measurement company.
- In some instances, it is important to link demographics to the monitoring information. To address this issue, the audience measurement company establishes a panel of users who have agreed to provide their demographic information and to have their Internet browsing activities monitored. When an individual joins the panel, they provide detailed information concerning their identity and demographics (e.g., gender, race, income, home location, occupation, etc.) to the audience measurement company. The audience measurement entity sets a cookie (e.g., a panelist cookie) on the panelist computer that enables the audience measurement entity to identify the panelist whenever the panelist accesses tagged media (e.g., media associated with beacon or tag instructions) and, thus, sends monitoring information to the audience measurement entity.
- Since most of the clients providing monitoring information from the tagged pages are not panelists and, thus, are unknown to the audience measurement entity, it has heretofore been necessary to use statistical methods to impute demographic information based on the data collected for panelists to the larger population of users providing data for the tagged media. However, panel sizes of audience measurement entities remain small compared to the general population of users. Thus, a problem is presented as to how to increase panel sizes while ensuring the demographics data of the panel is accurate.
- There are many database proprietors operating on the Internet. These database proprietors provide services to large numbers of subscribers or registered users. In exchange for the provision of the service, the subscribers register with the proprietor. As part of this registration, the subscribers provide detailed demographic information. Examples of such database proprietors include social network providers such as Facebook, Myspace, etc. These database proprietors set cookies on the computing device (e.g., computer, cell phone, etc.) of their subscribers to enable the database proprietors to recognize the users when they visit their websites.
- The protocols of the Internet make cookies inaccessible outside of the domain (e.g., Internet domain, domain name, etc.) on which they were set. Thus, a cookie set in the HFZlaw.com domain is accessible to servers in the HFZlaw.com domain, but not to servers outside that domain. Therefore, although an audience measurement entity might find it advantageous to access the cookies set by the database proprietors, they are unable to do so.
- In view of the foregoing,
FIGS. 1-15 illustrate and the corresponding portions of the specification describe methods and apparatus to leverage the existing databases of database proprietors to collect more extensive Internet usage and demographic data. For example, some of the example methods and apparatus leverage cookies stored on a user computer that identify a user that has logged into a database provider. However, for a shared computer, the identity of the user logged into the database provider may not match the person that is actually using the computer. Consider a circumstance in which a first user logs into the database provider and the cookie is stored on the computer. Assume the first user stops using the computer but does not log out of the database provider. Further, assume a second user then starts using the computer. If the cookie from the database provider is used to identify the computer user while the second user is using the computer, activity at the computer will wrongly be attributed to the first user. Another problem occurs when no database provider cookie exists on a computer. When no cookie exists on a computer, techniques that leverage the cookie will not be able to associate demographic information with the computer activity. - To compensate for incorrect attribution due to incorrect prediction of a user during computing activity, example methods and apparatus described in conjunction with
FIGS. 16-28 determine adjustment factor(s) for data determined using database providers (e.g., information determined as described in conjunction withFIGS. 1-15 ). Some panelists ("traditional panelists") are willing to provide their demographic information to a measurement entity and/or allow collection of more detailed information about their computer activity. For example, some traditional panelists allow panelist meter software to be installed on their computer to track detailed activity of computer activity. In some examples disclosed herein, an adjustment factor (e.g., an error rate, a correction factor, compensation factor, etc.) is determined by comparing demographic information collected from panelist meter software for computing sessions with demographic information determined using a database provider for the same computing sessions. In other words, demographic information for a computing session is determined using two different techniques (e.g., prompting a user to identify themselves using panelist metering software and determining an identify of the user using a database provider) and the demographic information for the two techniques is compared to determine the adjustment factor. The example adjustment factor can then be applied to other computing sessions (e.g., demographic information for all computing sessions (or a subset) determined using the database provider). In some examples, the comparison and determination of the adjustment factor is determined for all traditional panelists to more accurately determine the adjustment factor. An adjustment factor may be determined for each media provider, for each group of media providers, for the entire universe of media providers, and/or any combination of the foregoing. - Turning to the examples of
FIGS. 1-15 , example methods, apparatus, systems, and/or articles of manufacture disclosed herein cooperate with one or more database proprietors (also referred to herein as partners). The database proprietors provide Internet services to their registered users (e.g., users of those database proprietors) and store demographic information (e.g., in user account records) for those registered users. As part of this effort, the database proprietor agrees to provide demographic information of its registered users to the audience measurement entity for purposes of measuring demographic-based exposures to media such as content and/or advertisements. To prevent violating privacy agreements with the registered users of the database proprietor, examples disclosed herein employ cookie mapping techniques. That is, the database proprietor can maintain a mapping of its registered user cookies (i.e., partner cookies assigned by the database proprietor to its registered users) to cookies assigned by the audience measurement entity (i.e., audience measurement entity (AME) cookies) to the same registered users. In this manner, the audience measurement entity can log impressions of registered users based on the AME cookies and send full or partial AME cookie-based impression logs to a database proprietor. The database proprietor can, in turn, match its registered users to the AME cookie-based impressions based on its partner-to-AME cookie map. The database proprietor can then use the matches to associate demographic information for the matching registered users with corresponding impression logs. The database proprietor can then remove any identifying data (i.e., partner cookie data) from the demographic-based impression logs and provide the demographic-based impression logs to the audience measurement entity without revealing the identities of the database proprietor's registered users to the audience measurement entity. Thus, example techniques disclosed herein may be implemented without compromising privacies of registered users of database proprietors that partner with an audience measurement entity to track impressions based on audience demographics. - A database proprietor (e.g., Facebook) can access cookies it has set on a client device (e.g., a computer) to thereby identify the client based on the internal records (e.g., user account records) of the database proprietor. Because the identification of client devices is done with reference to enormous databases of registered users far beyond the quantity of persons present in a typical audience measurement panel, this process may be used to develop data that is extremely accurate, reliable, and detailed.
- Because the audience measurement entity remains the first leg of the data collection process (i.e., receives tag requests generated by tag instructions from client devices to log impressions), the audience measurement entity is able to obscure the source of the media access being logged as well as the identity of the media (e.g., content, webpages, advertisements, and/or other types of media) itself from the database proprietors (thereby protecting the privacy of the media sources), without compromising the ability of the database proprietors to provide demographic information corresponding to ones of their subscribers for which the audience measurement entity logged impressions.
- Example methods, apparatus, and/or articles of manufacture disclosed herein can be used to determine impressions or exposures to webpages, advertisements and/or other types of media using demographic information, which is distributed across different databases (e.g., different website owners, different service providers, etc.) on the Internet. Not only do example methods, apparatus, and articles of manufacture disclosed herein enable more accurate correlation of demographics to media impressions, but they also effectively extend panel sizes and compositions beyond persons participating (and/or willing to participate) in the panel of a ratings entity to persons registered in other Internet databases such as the databases of social media sites such as Facebook, Twitter, Google, etc. This extension effectively leverages the media tagging capabilities of the audience ratings entity and the use of databases of non-ratings entities such as social media and other websites to create an enormous, demographically accurate panel that results in accurate, reliable measurements of exposures to Internet media such as webpages, advertising, content of any type, and/or programming.
- Traditionally, audience measurement entities (also referred to herein as "ratings entities") determine demographic reach for advertising and media programming based on registered panel members. That is, an audience measurement entity enrolls people that consent to being monitored into a panel. During enrollment, the audience measurement entity receives demographic information from the enrolling people so that subsequent correlations may be made between media (e.g., content and/or advertisements) exposure to those panelists and different demographic markets. Unlike traditional techniques in which audience measurement entities rely solely on their own panel member data to collect demographics-based audience measurements, example methods, apparatus, and/or articles of manufacture disclosed herein enable an audience measurement entity to obtain demographic information from other entities that operate based on user registration models. As used herein, a user registration model is a model in which users subscribe to services of those entities by creating user accounts and providing demographic-related information about themselves. Obtaining such demographic information associated with registered users of database proprietors enables an audience measurement entity to extend or supplement its panel data with substantially reliable demographics information from external sources (e.g., database proprietors), thus extending the coverage, accuracy, and/or completeness of their demographics-based audience measurements. Such access also enables the audience measurement entity to monitor persons who would not otherwise have joined an audience measurement panel.
- Any entity having a database identifying demographics of a set of individuals may cooperate with the audience measurement entity. Such entities are referred to herein as "database proprietors" and include entities such as Facebook, Google, Yahoo!, MSN, Twitter, Apple iTunes, Experian, etc. Such database proprietors may be, for example, online web services providers. For example, a database proprietor may be a social network site (e.g., Facebook, Twitter, MySpace, etc.), a multi-service site (e.g., Yahoo!, Google, Experian, etc.), an online retailer site (e.g., Amazon.com, Buy.com, etc.), and/or any other web services site that maintains user registration records and irrespective of whether the site fits into none, or one or more of the categories noted above.
- Example methods, apparatus, and/or articles of manufacture disclosed herein may be implemented by an audience measurement entity, a ratings entity, and/or any other entity interested in measuring or tracking audience exposures to content, advertisements and/or any other type(s) of media.
- To increase the likelihood that measured viewership is accurately attributed to the correct demographics, example methods, apparatus, and/or articles of manufacture disclosed herein use demographic information located in the audience measurement entity's records as well as demographic information located at one or more database proprietors (e.g., web service providers) that maintain records or profiles of users having accounts therewith. In this manner, example methods, apparatus, and/or articles of manufacture may be used to supplement demographic information maintained by a ratings entity (e.g., an audience measurement company such as The Nielsen Company of Schaumburg, Illinois, United States of America, that collects media exposure measurements and/or demographics) with demographic information from one or more different database proprietors (e.g., web service providers).
- The use of demographic information from disparate data sources (e.g., high-quality demographic information from the panels of an audience measurement company and/or registered user data of web service providers) results in, for example, improving the reporting effectiveness of metrics for online and/or offline advertising campaigns. Examples disclosed herein use online registration data to identify demographics of users. Such examples also use server impression counts, tagging (also referred to as beaconing), and/or other techniques to track quantities of advertisement and/or media impressions attributable to those users. Online web service providers such as social networking sites and multi-service providers (collectively and individually referred to herein as online database proprietors) maintain detailed demographic information (e.g., age, gender, geographic location, race, income level, education level, religion, etc.) collected via user registration processes. An impression corresponds to a home or individual having been exposed to the corresponding media (e.g., content and/or advertisement). Thus, an impression represents a home or an individual having been exposed to an advertisement and/or content or group of advertisements or content. In Internet advertising, a quantity of impressions or impression count is the total number of times an advertisement or advertisement campaign has been accessed by a web population (e.g., including number of times accessed as decreased by, for example, pop-up blockers and/or increased by, for example, retrieval from local cache memory).
- Example impression reports generated using example methods, apparatus, and/or articles of manufacture disclosed herein may be used to report TV GRPs and online GRPs in a side-by-side manner. For instance, advertisers may use impression reports to report quantities of unique people or users that are reached individually and/or collectively by TV and/or online advertisements.
- Although examples are disclosed herein in connection with advertisements, advertisement exposures, and/or advertisement impressions, such examples may additionally or alternatively be implemented in connection with other types of media in addition to or instead of advertisements. That is, processes, apparatus, systems, operations, structures, data, and/or information disclosed herein in connection with advertisements may be similarly used and/or implemented for use with other types of media such as content. As used herein, "media" refers to content (e.g., websites, movies, television and/or other programming) and/or advertisements.
- Turning now to
FIG. 1 , anexample system 100 is shown. In the illustrated example, thesystem 100 includes animpression monitor system 102 which may be owned and/or operated by anaudience measurement entity 103. In the illustrated examples, theimpression monitor system 102 works cooperatively with one or more database proprietors, two of which are shown as a partnerA database proprietor 104a and a partnerB database proprietor 104b, to generateimpression reports database proprietors impression monitor system 102 may be owned and/or operated by an audience measurement entity to collect and log impressions fromclient devices 108 using, for example, audience measurement entity (AME) cookies set on thoseclient devices 108. In illustrated examples described herein, AME cookies (e.g., anAME cookie 208 ofFIG. 2 ) are set in theclient devices 108 in response to contacting theaudience measurement entity 103 after executing monitoring or tag instructions regardless of whether all, some, or none of theclient devices 108 are associated with audience member panels of theaudience measurement entity 103. That is, by setting AME cookies in theclient devices 108, theaudience measurement entity 103 is able to log ad and/or media impressions regardless of whether the ad and/or media impressions are attributable to panelists or non-panelists. In the illustrated example ofFIG. 1 , theclient devices 108 may be stationary or portable computers, handheld computing devices (e.g., tablets such as iPads®), smart phones, Internet appliances, and/or any other type of device that may be connected to the Internet and capable of presenting media. - In the illustrated example, media providers and/or advertisers distribute
advertisements 110 via the Internet to users that access websites and/or online television services (e.g., web-based TV, Internet protocol TV (IPTV), etc.). In the illustrated example, theadvertisements 110 may be individual, stand alone ads and/or may be part of one or more ad campaigns. The ads of the illustrated example are encoded with identification codes (i.e., data) that identify the associated ad campaign (e.g., campaign ID, if any), a creative type ID (e.g., identifying a Flash-based ad, a banner ad, a rich type ad, etc.), a source ID (e.g., identifying the ad publisher), and/or a placement ID (e.g., identifying the physical placement of the ad on a screen). Theadvertisements 110 of the illustrated example are also tagged or encoded to include computer executable monitoring instructions (e.g., Java, java script, or any other computer language or script) that are executed by web browsers that access theadvertisements 110 via, for example, the Internet. In the illustrated example ofFIG. 1 , theadvertisements 110 are presented to audience members via theclient devices 108. Computer executable monitoring instructions may additionally or alternatively be associated with media to be monitored. Thus, although this disclosure frequently speaks in terms of tracking advertisements, it is not restricted to tracking any particular type of media. On the contrary, it can be used to track media (e.g., content and/or advertisements) of any type or form in a network. Irrespective of the type of media being tracked, execution of the monitoring instructions causes the web browser to send impression request(s) 112 (e.g., referred to herein as tag requests 112) to a specified server (e.g., the audience measurement entity). The tag request(s) 112 may be implemented using HTTP requests. However, whereas HTTP requests traditionally identify web pages or other resources to be downloaded, the tag request(s) 112 of the illustrated example include audience measurement information (e.g., ad campaign identification, media identifier, content identifier, and/or user identification information) as their payloads. The server (e.g., the impression monitor system 102) to which the tag request(s) 112 are directed is programmed to log the audience measurement data caused by the tag request(s) 112 as impressions (e.g., ad and/or media impressions depending on the nature of the media tagged with the monitoring instructions). To collect and log exposure measurements, theimpression monitor system 102 includes anAME impressions store 114. Example impression logging processes are described in detail below in connection withFIG. 3 . - In some examples, advertisements tagged with such tag instructions are distributed with Internet-based media such as, for example, web pages, streaming video, streaming audio, IPTV content, etc. As noted above, methods, apparatus, systems, and/or articles of manufacture disclosed herein are not limited to advertisement monitoring but can be adapted to any type of content monitoring (e.g., web pages, movies, television programs, etc.) Example techniques that may be used to implement such monitoring, tag and/or beacon instructions are described in Blumenau,
U.S. Patent 6,108,637 , which is hereby incorporated herein by reference in its entirety. - In the illustrated example of
FIG. 1 , theimpression monitor system 102 tracks users associated with impressions using AME cookies (e.g., name-value pairs of Universally Unique Identifiers (UUIDs)) when theclient devices 108 present tagged advertisements (e.g., the advertisements 110) and/or other tagged media. Due to Internet security protocols, theimpression monitor system 102 can only collect cookies set in its domain (e.g., AME cookies). Thus, if, for example, theimpression monitor system 102 operates in the "Nielsen.com" domain, it can only collect cookies set in the Nielsen.com domain. Thus, when theimpression monitor system 102 receives tag request(s) 112 from theclient devices 108, theimpression monitor system 102 only has access to AME cookies set on that client device for, for example, the Nielsen.com domain, but not cookies set outside its domain (e.g., outside the Nielsen.com domain). - To overcome the domain limitations associated with collecting cookie information, the
impression monitoring system 102 monitors impressions of users of theclient devices 108 that are registered users of one or both of the partner A and partnerB database proprietors client devices 108 logs into a service of one of thedatabase proprietors client device 108 is directed to theimpression monitor system 102 to perform an initialization (INIT) AMEcookie message exchange 116 with theimpression monitor system 102 and sends alogin reporting message 118 to the database proprietor providing that service. For example, as described in more detail below in connection withFIG. 2 , if a user logs into a service of the partnerA database proprietor 104a, the INIT AMEcookie message exchange 116 sets an AME cookie in theclient device 108 based on the domain of theimpression monitor system 102 for the user that logged into the service of the partnerA database proprietor 104a. In addition, thelogin reporting message 118 sent to the partnerA database proprietor 104a includes the same AME cookie for theclient device 108 and a partner A cookie set by the partnerA database proprietor 104a for thesame client device 108. In the illustrated example, the partnerA database proprietor 104a sets the partner A cookie in theclient device 108 when theclient device 108 visits a webpage of the partnerA database proprietor 104a and/or when a user logs into a service of the partnerA database proprietor 104a via a login page of the partnerA database proprietor 104a (e.g., thelogin webpage 204 ofFIG. 2 ). In the illustrated example, the AME cookie is outside a domain (e.g., a root domain) of the partner A cookie. Because thelogin reporting message 118 includes the AME cookie, it enables the partnerA database proprietor 104a to map its partner A cookie to the AME cookie for the user of theclient device 108. The INIT AMEcookie message exchange 116 includes a login timestamp indicative of when a user associated with the specified AME cookie logged into the partnerA database proprietor 104a. If an AME cookie was previously set for the client, a new AME cookie is not set unless the previous AME cookie has been removed from the client, is no longer present on the client, and/or has expired. These processes are described in greater detail below in connection withFIG. 2 . - Subsequently, the
impression monitor system 102 receives the tag request(s) 112 based on ads and/or content presented via theclient devices 108 and logs impressions based on the presented ads and/or content in association with respective AME cookies of theclient devices 108 as described in detail below in connection withFIG. 3 . In the illustrated example ofFIG. 1 , theimpression monitor system 102 stores the logged impressions in the AME impressions store 114 and subsequently sends AME impression logs 122 containing some or all of the logged impressions from the AME impressions store 114 to thepartner database proprietors - Each of the
partner database proprietors 104a-b may subsequently use their respective AME cookie-to-partner cookie mappings to match demographics of users of theclient devices 108 identified based on partner cookies with impressions logged based on AME cookies in the AME impression logs 122. Example demographic matching and reporting is described in greater detail below in connection withFIG. 4 . Because theaudience measurement entity 103 sets AME cookies on any client that sends it a tag request (i.e., including non-panelists), the map of the AME cookies to partner cookies is not limited to panelists but instead extends to any client that accesses tagged media. As a result, theaudience measurement entity 103 is able to leverage the data of the partner as if the non-panelists with AME cookies were panelists of theaudience measurement entity 103, thereby effectively increasing the panel size. In some examples, the panel of the audience measurement entity is eliminated. -
FIG. 2 depicts an example manner of setting cookies with theimpression monitor system 102 and reporting the same to the database proprietors (e.g., the partnerA database proprietor 104a and/or the partnerB database proprietor 104b) in response to users logging in to websites of the database proprietors. One of theclient devices 108 ofFIG. 1 is shown inFIG. 2 and is provided with acookie reporter 202 configured to monitor login events on theclient device 108 and to send cookies to theimpression monitor system 102 and thedatabase proprietors FIG. 2 , thecookie reporter 202 is shown performing the INIT AMEcookie message exchange 116 with theimpression monitor system 102 and sending thelogin reporting message 118 to the partnerA database proprietor 104a. - In the illustrated example of
FIG. 2 , thecookie reporter 202 is implemented using computer executable instructions (e.g., Java, java script, or any other computer language or script) that are executed by web browsers. Also in the illustrated example ofFIG. 2 , thecookie reporter 202 is provided to the clients, directly or indirectly, by an audience measurement entity that owns and/or operates theimpression monitor system 102. For example, thecookie reporter 202 may be provided to the database proprietor from theAME 103 and subsequently downloaded to theclient device 108 from a server serving alogin webpage 204 of the partnerA database proprietor 104a (or of the partnerB database proprietor 104b or of any other partner database proprietor) in response to theclient device 108 requesting the login webpage. - A web browser of the
client device 108 may execute thecookie reporter 202 to monitor for login events associated with thelogin page 204. When a user logs in to a service of the partnerA database proprietor 104a via thelogin page 204, thecookie reporter 202 initiates the INITAME message exchange 116 by sending arequest 206 to theimpression monitor system 102. In the illustrated example ofFIG. 2 , therequest 206 is a dummy request because its purpose is not to actually retrieve a webpage, but is instead to cause theimpression monitor system 102 to generate anAME cookie 208 for the client device 108 (assuming an AME cookie has not already been set for and/or is not present on the client). TheAME cookie 208 uniquely identifies theclient device 108. However, because theclient device 108 may not be associated with a panelist of theAME 103, the identity and/or characteristics of the user may not be known. Theimpression monitor system 102 subsequently uses theAME cookie 208 to track or log impressions associated with theclient device 108, irrespective of whether theclient device 108 is a panelist of theAME 103, as described below in connection withFIG. 3 . Because disclosed examples monitor clients as panelists even though they may not have been registered (i.e., have not agreed to be a panelist of the AME 103), such clients may be referred to herein as pseudo-panelists. - The
request 206 of the illustrated example is implemented using an HTTP request that includes aheader field 210, acookie field 212, and apayload field 214. Theheader field 210 stores standard protocol information associated with HTTP requests. When theclient device 108 does not yet have an AME cookie set therein, thecookie field 212 is empty to indicate to theimpression monitor system 102 that it needs to create and set theAME cookie 208 in theclient device 108. In response to receiving arequest 206 that does not contain anAME cookie 208, theimpression monitor system 102 generates anAME cookie 208 and sends theAME cookie 208 to theclient device 108 in acookie field 218 of aresponse message 216 as part of the INIT AMEcookie message exchange 116 ofFIG. 1 to thereby set theAME cookie 208 in theclient device 108. - In the illustrated example of
FIG. 2 , theimpression monitor system 102 also generates alogin timestamp 220 indicative of a time at which a user logged in to thelogin page 204 and sends thelogin timestamp 220 to theclient device 208 in apayload field 222 of theresponse 216. In the illustrated example, thelogin timestamp 220 is generated by the impression monitor system 102 (e.g., rather than the client device 108) so that all login events from allclient devices 108 are time stamped based on the same clock (e.g., a clock of the impression monitor system 102). In this manner, login times are not skewed or offset based on clocks ofrespective client devices 108, which may have differences in time between one another. In some examples, thetimestamp 220 may be omitted from thepayload 222 of theresponse 216, and theimpression monitor system 102 may instead indicate a login time based on a timestamp in aheader field 224 of theresponse 216. In some examples, theresponse 216 is anHTTP 302 redirect response which includes a URL 226 of the partnerA database proprietor 104a to which thecookie reporter 202 should send theAME cookie 208. Theimpression monitor system 102 populates the redirect response with the URL. - In the illustrated example of
FIG. 2 , after receiving theresponse 216, thecookie reporter 202 generates and sends thelogin reporting message 118 to the partnerA database proprietor 104a. For example, thecookie reporter 202 of the illustrated example sends thelogin reporting message 118 to a URL indicated by thelogin page 204. Alternatively, if theresponse 216 is anHTTP 302 redirect and includes the URL 226, thecookie reporter 202 sends thelogin reporting message 118 to the partnerA database proprietor 104a using the URL 226. In the illustrated example ofFIG. 2 , thelogin reporting message 118 includes apartner A cookie 228 in acookie field 230. Thepartner A cookie 228 uniquely identifies theclient device 108 for the partnerA database proprietor 104a. Also in the illustrated example, thecookie reporter 202 sends theAME cookie 208 and thelogin timestamp 220 in apayload field 232 of thelogin reporting message 118. Thus, in the illustrated example ofFIG. 2 , theAME cookie 208 is sent as regular data (e.g., a data parameter) or payload in thelogin reporting message 118 to the partnerA database proprietor 104a to overcome the fact that theAME cookie 208 was not set in the domain of the partnerA database proprietor 104a, and, thus, could not be sent to a third party as an ordinary cookie. In the illustrated example, theAME cookie 208 corresponds to another domain (e.g., a Nielsen.com root domain) outside the domain of the partner A cookie 228 (e.g., a Facebook.com root domain). Using example processes illustrated inFIG. 2 advantageously enables sending cookie data across different domains, which would otherwise not be possible using known cookie communication techniques. Thedatabase proprietor 104a receives theAME cookie 208 in association with thepartner A cookie 228, thereby, creating an entry in an AME cookie-to-partner cookie map (e.g., the partner cookie map 236). - Although the
login reporting message 118 is shown in the example ofFIG. 2 as including thepartner A cookie 228, for instances in which the partnerA database proprietor 104a has not yet set thepartner A cookie 228 in theclient device 108, thecookie field 230 is empty in thelogin reporting message 118. In this manner, theempty cookie field 230 prompts the partnerA database proprietor 104a to set thepartner A cookie 228 in theclient device 108. In such instances, the partnerA database proprietor 104a sends the client device 108 a response message (not shown) including thepartner A cookie 228 and records thepartner A cookie 228 in association with theAME cookie 208. - In some examples, the partner
A database proprietor 104a uses thepartner A cookie 228 to track online activity of its registered users. For example, the partnerA database proprietor 104a may track user visits to web pages hosted by the partnerA database proprietor 104a, display those web pages according to the preferences of the users, etc. Thepartner A cookie 228 may also be used to collect "domain-specific" user activity. As used herein, "domain-specific" user activity is user Internet activity associated within the domain(s) of a single entity. Domain-specific user activity may also be referred to as "intra-domain activity." In some examples, the partnerA database proprietor 104a collects intra-domain activity such as the number of web pages (e.g., web pages of the social network domain such as other social network member pages or other intra-domain pages) visited by each registered user and/or the types of devices such as mobile devices (e.g., smart phones, tablets, etc.) or stationary devices (e.g., desktop computers) used for access. The partnerA database proprietor 104a may also track account characteristics such as the quantity of social connections (e.g., friends) maintained by each registered user, the quantity of pictures posted by each registered user, the quantity of messages sent or received by each registered user, and/or any other characteristic of user accounts. - In some examples, the
cookie reporter 202 is configured to send therequest 206 to theimpression monitor system 102 and send thelogin reporting message 118 to the partnerA database proprietor 104a only after the partnerA database proprietor 104a has indicated that a user login via thelogin page 204 was successful. In this manner, therequest 206 and thelogin reporting message 118 are not performed unnecessarily should a login be unsuccessful. In the illustrated example ofFIG. 2 , a successful login ensures that the partnerA database proprietor 104a will associate the correct demographics of a logged in registered user with thepartner A cookie 228 and theAME cookie 208. - In the illustrated example of
FIG. 2 , the partnerA database proprietor 104a includes aserver 234, apartner cookie map 236, and a user accountsdatabase 238. Although not shown, other database proprietors (e.g., the partnerB database proprietor 104b ofFIG. 1 ) that partner with the audience measurement entity 103 (FIG. 1 ) also include a respective partner cookie map similar to thepartner cookie map 236 and a user accounts database similar to the user accountsdatabase 238 but, of course, relative to their own users. Theserver 234 of the illustrated example communicates with theclient device 108 to, for example, receive login information, receive cookies from theclient device 108, set cookies in theclient device 108, etc. - The
partner cookie map 236 stores partner cookies (e.g., the partner A cookie 228) in association with respective AME cookies (e.g., the AME cookie 208) and respective timestamps (e.g., the timestamp 220). In the illustrated example ofFIG. 2 , thepartner cookie map 236 stores a unique user ID (UUID) found in a name-value pair (i.e., a parameter name such as 'user_ID' and a value such as the UUID) of thepartner A cookie 228 in association with a unique user ID found in a name-value pair of theAME cookie 208. In addition, thepartner cookie map 236 stores thelogin timestamp 220 in association with the UUIDs to indicate a time at which a corresponding user login occurred. Referring briefly toFIG. 5 , an example implementation of thepartner cookie map 236 is shown, in which an AMEuser ID column 502 stores UUIDs from AME cookies (e.g., theAME cookie 208 ofFIG. 2 ), a partneruser ID column 504 stores UUIDs from partner cookies (e.g., thepartner A cookie 228 ofFIG. 2 ), and alogin timestamp column 506 stores login timestamps (e.g., thelogin timestamp 220 ofFIG. 2 ). In illustrated examples disclosed herein, the partnerA database proprietor 104a uses thepartner cookie map 236 to match impressions received from theimpression monitor system 102 based on AME cookies (e.g., the AME cookie 208) to registered users of the partnerA database proprietor 104a identified by respective partner A cookies (e.g., the partner A cookie 228). In this manner, the partnerA database proprietor 104a can determine which of its registered users are associated with specific impressions logged by theimpression monitor system 102. - Returning to
FIG. 2 , the partnerA database proprietor 104a uses the user accountsdatabase 238 to store, among other things, demographic information for registered users of the partnerA database proprietor 104a. In the illustrated example ofFIG. 2 , such demographic information is received from registered users during an enrollment and/or registration process or during a subsequent personal information update process. The demographic information stored in the user accountsdatabase 238 may include, for example, age, gender, interests (e.g., music interests, movie interests, product interests, or interests associated with any other topic), number of friends or social connections maintained by each registered user via the partnerA database proprietor 104a, personal yearly income, household income, geographic location of residence, geographic location of work, graduation year(s), quantity of group associations, or any other demographic information. The partnerA database proprietor 104a uses the user accountsdatabase 238 to associate demographic information to particular impressions logged by theimpression monitor system 102 after determining which registered users of the partnerA database proprietor 104a correspond to which logged impressions based on thepartner cookie map 236. -
FIG. 3 depicts anexample system 300 that may be used to log impressions at theimpression monitor system 102 of theexample system 100 ofFIG. 1 . Theexample system 300 enables the impressions monitorsystem 102 ofFIGS. 1 and2 to log impressions in association with corresponding AME cookies (e.g., theAME cookie 208 ofFIG. 2 ) based on tag requests (e.g., the tag request(s) 112 ofFIG. 1 ) received from aweb browser 302 executed by a client device (e.g., anyclient device 108 ofFIGS. 1 and2 ). In the illustrated example ofFIG. 3 , theimpression monitor system 102 logs impressions from any client device (e.g., theclient devices 108 ofFIG. 1 ) from which it receives atag request 112 as described below. Theimpression monitor system 102 compiles the received impression data in the AMEimpression data store 114. - Turning in detail to
FIG. 3 , the client device may be any one of theclient devices 108 ofFIGS. 1 and2 or another device not shown inFIGS. 1 or2 . However, for simplicity of discussion and without loss of generality, the client device will be referred to asclient device 108. As shown, theclient device 108 sends communications to the impressions monitorsystem 102. In the illustrated example, theclient device 108 executes theweb browser 302, which is directed to a host website (e.g., www.acme.com) that displays one of the advertisement(s) 110 received from anad publisher 303. Theadvertisement 110 of the illustrated example is tagged with identifier information (e.g., a campaign ID, a creative type ID, a placement ID, a publisher source URL, etc.) andtag instructions 304. When thetag instructions 304 are executed by theclient device 108, thetag instructions 304 cause theclient device 108 to send atag request 112 to a URL address of the impressions monitorsystem 102 as specified in thetag instructions 304. Alternatively, the URL address specified in thetag instructions 304 may direct thetag request 112 to any other server owned, operated, and/or accessible by the audience measurement entity 103 (FIG. 1 ) or another entity. Thetag instructions 304 may be implemented using java script or any other type(s) of executable instruction(s) including, for example, Java, HTML, etc. It should be noted that tagged content such as web pages, and/or any other media are processed the same way as the taggedadvertisement 110. That is, for any tagged media, corresponding tag instructions are received in connection with the download of the tagged content and cause a tag request to be sent from the client device that downloaded the tagged content to the impression monitor system 102 (or any other server indicated by the instructions). - In the illustrated example of
FIG. 3 , thetag request 112 is implemented using an HTTP request and is shown in detail as including aheader field 310, acookie field 312, and apayload field 314. In the illustrated example ofFIG. 3 , theweb browser 302 stores theAME cookie 208 ofFIG. 2 in thecookie field 312 and storesad campaign information 316 and apublisher site ID 318 in thepayload field 314. In the illustrated example, thead campaign information 316 may include information identifying one or more of an associated ad campaign (e.g., an ad campaign ID), a creative type ID (e.g., identifying a Flash-based ad, a banner ad, a rich type ad, etc.), and/or a placement ID (e.g., identifying the physical placement of the ad on a screen). In some examples, to log a media impression, thead campaign information 316 is replaced with media information identifying the media (e.g., a media identifier), a creative ID, and/or a placement ID. In the illustrated example, thepublisher site ID 318 identifies a source of theadvertisement 110 and/or content (e.g., a source ID identifying thead publisher 303 and/or media publisher). - In the illustrated example, in response to receiving the
tag request 112, theimpression monitor system 102 logs an impression associated with theclient device 108 in the AME impressions store 114 by storing theAME cookie 208 in association with a media identifier (e.g., thead campaign information 316 and/or the publisher site ID 318). In addition, theimpression monitor system 102 generates a timestamp indicative of the time/date of when the impression occurred and stores the timestamp in association with the logged impression. An example implementation of the exampleAME impression store 114 is shown inFIG. 6 . Turning briefly toFIG. 6 , theAME impression store 114 includes an AMEuser ID column 602 to store AME cookies (e.g., theAME cookie 208 ofFIGS. 2 and3 ), atimestamp column 604 to store impression timestamps indicative of when impressions occurred at client devices (e.g., theclient device 108 ofFIGS. 1-3 ), acampaign ID column 606 to store thecampaign information 316 ofFIG. 3 , and asite ID column 608 to store thepublisher site ID 318 ofFIG. 3 . -
FIG. 4 is anexample apparatus 400 that may be used to associate impressions with demographics of users (e.g., users of theclient devices 108 ofFIGS. 1-3 ) registered with one or more database proprietors (e.g., thepartner database proprietors 104a-b ofFIGS. 1-3 ). In some examples, theapparatus 400 is implemented at one or more database proprietors (e.g., thepartner database proprietors 104a-b ofFIGS. 1-3 ). Alternatively, theapparatus 400 may be implemented at other sites. In some examples, theapparatus 400 may be developed by the audience measurement entity 103 (FIG. 1 ) and provided to a database proprietor to enable the database proprietor to combine database proprietor-owned demographic information with impression logs provided by theaudience measurement entity 103. To ensure privacy of registered users of a database proprietor, theaudience measurement entity 103 may install or locate theexample apparatus 400 at a database proprietor so that the database proprietor need not provide identities of its registered users to theaudience measurement entity 103 in order to associate demographics information with logged impressions. Instead, theaudience measurement entity 103 can provide its logged impressions (e.g., the AME impression logs 122) to the database proprietor and the database proprietor can associate respective demographics with the logged impressions while concealing the identities (e.g., names and contact information) of its registered users. - In the illustrated example, the
apparatus 400 is provided with anexample cookie matcher 402, an example demographics associator 404, anexample demographics analyzer 406, anexample demographics modifier 408, an exampleuser ID modifier 410, anexample report generator 412, anexample data parser 414, anexample mapper 416, and an example instructions interface 418. While an example manner of implementing theapparatus 400 has been illustrated inFIG. 4 , one or more of the elements, processes and/or devices illustrated inFIG. 4 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, thecookie matcher 402, the demographics associator 404, thedemographics analyzer 406, thedemographics modifier 408, theuser ID modifier 410, thereport generator 412, thedata parser 414, themapper 416, theinstructions interface 418 and/or, more generally, theexample apparatus 400 ofFIG. 4 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of thecookie matcher 402, the demographics associator 404, thedemographics analyzer 406, thedemographics modifier 408, theuser ID modifier 410, thereport generator 412, thedata parser 414, themapper 416, theinstructions interface 418 and/or, more generally, theexample apparatus 400 could be implemented by one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), etc. When any of the apparatus or system claims of this patent are read to cover a purely software and/or firmware implementation, at least one of thecookie matcher 402, the demographics associator 404, thedemographics analyzer 406, thedemographics modifier 408, theuser ID modifier 410, thereport generator 412, thedata parser 414, themapper 416, and/or the instructions interface 418 are hereby expressly defined to include a tangible computer readable medium such as a memory, DVD, CD, BluRay disk, etc. storing the software and/or firmware. Further still, theexample apparatus 400 ofFIG. 4 may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated inFIG. 4 , and/or may include more than one of any or all of the illustrated elements, processes and devices. - Turning in detail to
FIG. 4 , in the illustrated example, theapparatus 400 is implemented at the partnerA database proprietor 104a (FIGS. 1 and2 ). Other instances of theapparatus 400 could be similarly implemented at any other database proprietor participating with the AME 103 (e.g., the partnerB database proprietor 104b). In the illustrated example ofFIG. 4 , theapparatus 400 receives the AME impression logs 122 from theimpression monitor system 102 to enable theapparatus 400 to associate user/audience member demographics from the user accountsdatabase 238 with logged impressions. - In the illustrated example, the
apparatus 400 is provided with thecookie matcher 402 to match AME user IDs from AME cookies (e.g., theAME cookie 208 ofFIGS. 2 and3 ) from the AME impression logs 122 to AME user IDs in the partnerA cookie map 236. Theapparatus 400 performs such cookie matching to identify registered users of the partnerA database proprietor 104a to which the logged impressions are attributable (e.g., partner A registered users for which theimpression monitor system 102 set AME cookies as described above in connection withFIG. 2 and tracked impressions as described above in connection withFIG. 3 ). For example, thepartner cookie map 236 is shown inFIG. 5 as associating AME user IDs in the AMEuser ID column 502 to partner user IDs in the partneruser ID column 504. The AME impression logs 122 are structured similar to the data in theAME impression store 114 as shown inFIG. 6 , which logs impressions per AME user ID. Thus, thecookie matcher 402 matches AME user IDs from the AMEuser ID column 602 of the AME impression logs 122 to AME user IDs of the AMEuser ID column 502 of thepartner cookie map 236 to associate a logged impression from the AME impression logs 122 to a corresponding partner user ID mapped in thepartner cookie map 236 ofFIG. 5 . In some examples, theAME 103 encrypts, obfuscates, varies, etc. campaign IDs in the AME impression logs 122 before sending the AME impression logs 122 to partner database proprietors (e.g., thepartner database proprietors FIGS. 1 and2 ) to prevent the partner database proprietors from recognizing the media to which the campaign IDs correspond or to otherwise protect the identity of the media. In such examples, a lookup table of campaign ID information may be stored at theimpression monitor system 102 so that impression reports (e.g., the impression reports 106a and 106b ofFIG. 1 ) received from the partner database proprietors can be correlated with the media. - In some examples, the
cookie matcher 402 uses login timestamps (e.g., thelogin timestamp 220 ofFIG. 2 ) stored in thelogin timestamp column 506 ofFIG. 5 and impression timestamps stored in thetimestamp column 604 ofFIG. 6 to discern between different users to which impressions logged by theimpression monitor system 102 are attributable. That is, if two users having respective username/password login credentials for the partnerA database proprietor 104a use thesame client device 108, all impressions logged by theimpression monitor system 102 will be based on the same AME cookie (e.g., theAME cookie 208 ofFIGS. 2 and3 ) set in theclient device 108 regardless of which user was using theclient device 108 when the impression occurred. However, by comparing logged impression timestamps (e.g., in thetimestamp column 604 ofFIG. 6 ) to login timestamps (e.g., in thelogin timestamp column 506 ofFIG. 5 ), thecookie matcher 402 can determine which user was logged into the partnerA database proprietor 104a when a corresponding impression occurred. For example, if a user 'TOM' logged in to the partnerA database proprietor 104a at 12:57 AM on January 1, 2010 and a user 'MARY' logged in to the partnerA database proprietor 104a at 3:00 PM on January 1, 2010 using thesame client device 108, the login events are associated with the same AME cookie (e.g., theAME cookie 208 ofFIGS. 2 and3 ). In such an example, thecookie matcher 402 associates any impressions logged by theimpression monitor system 102 for the same AME cookie between 12:57 AM and 3:00 pm on January 1, 2010 to the user 'TOM' and associates any impressions logged by theimpression monitor system 102 for the same AME cookie after 3:00 pm on January 1, 2010 to the user 'MARY'. Such time-based associations are shown in the illustrated example data structure ofFIG. 7 described below. - In the illustrated example, the
cookie matcher 402 compiles the matched results into an example partner-basedimpressions data structure 700, which is shown in detail inFIG. 7 . Turning briefly toFIG. 7 , the partner-basedimpressions structure 700 includes an AMEuser ID column 702, animpression timestamp column 704, acampaign ID column 706, asite ID column 708, a user login timestamp 710, and a partneruser ID column 712. In the AMEuser ID column 702, thecookie matcher 402 stores AME cookies (e.g., theAME cookie 208 ofFIGS. 2 and3 ). In theimpression timestamp column 704, thecookie matcher 402 stores timestamps generated by theimpression monitor system 102 indicative of when each impression was logged. In thecampaign ID column 706, thecookie matcher 402 stores ad campaign IDs stored in, for example, thecampaign information 316 ofFIG. 3 . In some examples, instead of or in addition to thecampaign ID column 706, the partner-basedimpressions data structure 700 includes a content ID column to store identifying information of media. In some examples, some media (e.g., advertisements, content, and/or other media) is not associated with a campaign ID or content ID. In the illustrated example ofFIG. 7 , blanks in thecampaign ID column 706 indicate media that is not associated with campaign IDs and/or content IDs. In thesite ID column 708, thecookie matcher 402 stores advertisement publisher site IDs (e.g., thepublisher site ID 318 ofFIG. 3 ). In the user login timestamp column 710, thecookie matcher 402 stores timestamps (e.g., thetimestamp 220 ofFIG. 2 ) indicative of when respective users logged in via partner login pages (e.g., thelogin page 204 ofFIG. 2 ). In the partneruser ID column 712, thecookie matcher 402 stores partner cookies (e.g., thepartner A cookie 228 ofFIG. 2 ). - Returning to
FIG. 4 , in the illustrated example, theapparatus 400 is provided with the demographics associator 404 to associate demographics information from the user accountsdatabase 238 with corresponding partner-based impressions from the partner-basedimpressions structure 700. For example, the demographics associator 404 may retrieve demographics information for partner user IDs noted in the partner user ID column 712 (FIG. 7 ) and associate the retrieved demographics information with corresponding ones of the records in the partner-basedimpressions structure 700. - In the illustrated example of
FIG. 4 , to analyze demographic information for accuracy and/or completeness, theapparatus 400 is provided with thedemographics analyzer 406. In addition, to update, modify, and/or fill-in demographics information in inaccurate and/or incomplete records, theapparatus 400 is provided with thedemographics modifier 408. In some examples, thedemographics analyzer 406 and/or thedemographics modifier 408 analyze and/or adjust inaccurate demographic information using example methods, systems, apparatus, and/or articles of manufacture disclosed inU.S. patent application serial no. 13/209,292, filed on August 12, 2011 - In the illustrated example, to remove user IDs from the partner-based
impressions structure 700 after adding the demographics information and before providing the data to theAME 103, theapparatus 400 of the illustrated example is provided with auser ID modifier 410. In the illustrated example, theuser ID modifier 410 is configured to at least remove partner user IDs (from the partner user ID column 712) to protect the privacy of registered users of the partnerA database proprietor 104a. In some examples, theuser ID modifier 410 may also remove the AME user IDs (e.g., from the AME user ID column 702) so that theimpression reports 106a generated by theapparatus 400 are demographic-level impression reports. "Removal" of user IDs (e.g., by theuser ID modifier 410 and/or by the report generator 412) may be done by not providing a copy of the data in the corresponding user ID fields as opposed to deleting any data from those fields. If the AME user IDs are preserved in theimpressions data structure 700, theapparatus 400 of the illustrated example can generate user-level impression reports. - In the illustrated example of
FIG. 4 , to generate theimpression reports 106a, theapparatus 400 is provided with thereport generator 412. Example information that thereport generator 412 may generate for the impression reports 106a is described in detail below in connection withFIGS. 8 and 9 . - In the illustrated example of
FIG. 4 , to parse information, theapparatus 400 is provided with thedata parser 414. In some examples, thedata parser 414 receives messages from client devices and/or other systems and parses information from those received messages. For example, theapparatus 400 may use thedata parser 414 to receive thelogin reporting message 118 from the cookie reporter 202 (FIG. 2 ) and parse out thepartner A cookie 228, theAME cookie 208, and/or thelogin timestamp 220 from thelogin reporting message 118. In some examples, theapparatus 400 also uses thedata parser 414 to parse information in the AME impression logs 122 and/or to parse information from any other data structure and/or message. - In the illustrated example of
FIG. 4 , to map information, theapparatus 400 is provided with themapper 416. In some examples, themapper 416 maps cookie identifiers associated with the same user but corresponding to different Internet domains. For example, theapparatus 400 may use themapper 416 to map thepartner A cookie 228 to the AME cookie 208 (FIG. 2 ) in the partner cookie map 236 (FIGS. 2 ,4 , and5 ). In some examples, themapper 416 also maps login timestamps with corresponding cookie identifiers. For example, theapparatus 400 may use themapper 416 to map the login timestamp 220 (FIG. 2 ) with the correspondingpartner A cookie 228 andAME cookie 208 in thepartner cookie map 236. - In the illustrated example of
FIG. 4 , to send computer executable instructions to the client device(s) 108 to monitor user logins via login webpages (e.g., thelogin webpage 204 ofFIG. 2 ), theapparatus 400 is provided with theinstructions interface 418. For example, theapparatus 400 may use the instructions interface 418 to send computer executable instructions (e.g., Java, java script, or any other computer language or script) to theclient device 108 that are executed by the web browser 302 (FIG. 3 ) to implement the cookie reporter 202 (FIG. 2 ). In some examples, the instructions interface 418 sends the computer executable instructions to theclient device 108 in response to receiving a request from theweb browser 302 for a login webpage (e.g., the login webpage 204) of an Internet-based service provided by the entity (e.g., one of thedatabase proprietor partners apparatus 400. In this manner, theclient device 108 can execute the computer executable instructions to monitor login events at the login webpage. -
FIG. 15 is an example apparatus that may be used to implement theimpression monitor system 102 ofFIGS. 1-3 . In the illustrated example, to detect whether AME cookies (e.g., theAME cookie 208 ofFIG. 2 ) have been set (e.g., are stored) in client devices (e.g., any of theclient devices 108 ofFIGS. 1-3 ), theimpression monitor system 102 is provided with acookie status detector 1402. For example, thecookie status detector 1402 may inspect or analyze messages (e.g., therequest 206 ofFIG. 2 ) from client devices to determine whether AME cookies are present therein. In the illustrated example, to generate AME cookies (e.g., the AME cookie 208 (FIG. 2 )), theimpression monitor system 102 is provided with acookie generator 1404. - In the illustrated example, to generate login timestamps (e.g., the
login timestamp 220 ofFIG. 2 ), theimpression monitor system 102 is provided with atimestamp generator 1406. For example, thetimestamp generator 1406 may be implemented using a real-time clock (RTC) or any other timing or clock device or interface to track time and generate timestamps. In the illustrated example, to generate messages (e.g., theresponse 216 ofFIG. 2 ), theimpression monitor system 102 is provided with amessage generator 1408. In the illustrated example, to log impressions, theimpression monitor system 102 is provided with animpression logger 1410. For example, theimpression logger 1410 may log impressions in theAME impression store 114 as shown inFIG. 6 . - In the illustrated example, to receive messages and/or information from
client devices 108 and send messages and/or information toclient devices 108 and/or topartner database proprietors impression monitor system 102 is provided with acommunication interface 1412. For example, thecommunication interface 1412 may receive messages such as the tag request(s) 112 (FIG. 1 ) and the request 206 (FIG. 2 ) fromclient devices 108. Additionally, thecommunication interface 1412 may send messages such as the response 216 (FIG. 2 ) to theclient devices 108 and send logged impressions (e.g., impressions logged in the AME impression store 114) topartner database proprietors -
FIG. 15 is an example apparatus that may be used to implement acookie reporter 202 ofFIG. 2 . In the illustrated example, to detect log events, thecookie reporter 202 is provided with alogin event detector 1502. For example, thelogin detector 1502 may be configured to monitor login events generated by web browsers (e.g., theweb browser 302 ofFIG. 3 ) of client devices (e.g., theclient devices 108 ofFIGS. 1-3 ). In the illustrated example, when a user logs in to thelogin webpage 204 ofFIG. 2 , thelogin detector 1502 detects a login event. - In the illustrated example, to detect whether AME cookies (e.g., the
AME cookie 208 ofFIG. 2 ) or partner cookies (e.g., thepartner cookie 228 ofFIG. 2 ) have been set (e.g., are stored) in client devices (e.g., theclient devices 108 ofFIGS. 1-3 ), thecookie reporter 202 is provided with acookie status detector 1504. For example, thecookie status detector 1502 may inspect or analyze cookie files or cookie entries in client devices to determine whether AME cookies (e.g., theAME cookie 208 ofFIG. 2 ) or partner cookies (e.g., thepartner cookie 228 ofFIG. 2 ) have been previously set. In the illustrated example, thecookie status detector 1504 may also determine whether cookies have expired. In the illustrated example, when a cookie expires, it is treated as invalid or as if it no longer exists in a client device and must be set again by a corresponding server domain. - In the illustrated example, to retrieve cookies from storage locations in client devices (e.g., the
client devices 108 ofFIGS. 1-3 ), thecookie reporter 202 is provided with acookie interface 1506. For example, thecookie interface 1506 may retrieve AME cookies (e.g., theAME cookie 208 ofFIG. 2 ) or partner cookies (e.g., thepartner cookie 228 ofFIG. 2 ) from their respective storage locations in client devices. In addition, thecookie interface 1506 may also store cookies set by and received from theimpression monitor system 102 and/or any partner database proprietor in the client devices. - In the illustrated example, to generate messages (e.g., the tag request(s) 112 of
FIGS. 1 and3 , thelog reporting messages 118 ofFIGS. 1 and2 , and therequest 206 ofFIG. 2 ), thecookie reporter 202 is provided with amessage generator 1508. In the illustrated example, to send messages and/or information to theimpression monitor system 102 and/or to partner database proprietors (e.g., thepartner database proprietors FIGS. 1 and2 ) and/or to receive messages and/or information from theimpression monitor system 102, thecookie reporter 202 is provided with acommunication interface 1510. For example, thecommunication interface 1510 may send the tag request(s) 112 (FIGS. 1 and3 ) and therequest 206 ofFIG. 2 to theimpression monitor system 102, receive the response 216 (FIG. 2 ) from theimpression monitor system 102, and send the login reporting messages 118 (FIGS. 1 and2 ) to thepartner database proprietors - While example manners of implementing the
apparatus FIGS. 14 and 15 , one or more of the elements, processes and/or devices illustrated inFIGS. 14 and 15 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, thecookie status detector 1402, thecookie generator 1404, thetimestamp generator 1406, themessage generator 1408, theimpression logger 1410, thecommunication interface 1412 and/or, more generally, theexample apparatus 102 ofFIG. 14 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. In addition, thelogin event detector 1502, thecookie status detector 1504, thecookie interface 1506, themessage generator 1508, thecommunication interface 1510 and/or, more generally, theexample apparatus 202 ofFIG. 15 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of thecookie status detector 1402, thecookie generator 1404, thetimestamp generator 1406, themessage generator 1408, theimpression logger 1410, thecommunication interface 1412 and/or, more generally, theexample apparatus 102 and/or any of thelogin event detector 1502, thecookie status detector 1504, thecookie interface 1506, themessage generator 1508, thecommunication interface 1510 and/or, more generally, theexample apparatus 202 could be implemented by one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), etc. When any of the apparatus or system claims of this patent are read to cover a purely software and/or firmware implementation, at least one of thecookie status detector 1402, thecookie generator 1404, thetimestamp generator 1406, themessage generator 1408, theimpression logger 1410, thecommunication interface 1412, thelogin event detector 1502, thecookie status detector 1504, thecookie interface 1506, themessage generator 1508, and/or thecommunication interface 1510 are hereby expressly defined to include a tangible computer readable medium such as a memory, DVD, CD, BluRay disk, etc. storing the software and/or firmware. Further still, theexample apparatus FIGS. 14 and 15 , and/or may include more than one of any or all of the illustrated elements, processes and devices. - Turning to
FIG. 8 , an example impressions totalizationdata structure 800, which may be generated by thereport generator 412 ofFIG. 4 , stores impression totalizations based on the impressions logged by the impression monitor system 102 (FIGS. 1-3 ). As shown inFIG. 8 , the impressions totalizationstructure 800 shows quantities of impressions logged for the client devices 108 (FIGS 1-3 ). In the illustrated example, the impressions totalizationstructure 800 is generated by thereport generator 412 for an advertisement campaign (e.g., one or more of theadvertisements 110 ofFIG. 1 ) to determine frequencies of impressions per day for each monitored user. - To track frequencies of impressions per unique user per day, the impressions totalization
structure 800 is provided with afrequency column 802. A frequency of 1 indicates one exposure per day of an ad campaign to a unique user, while a frequency of 4 indicates four exposures per day of the same ad campaign to a unique user. To track the quantity of unique users to which impressions are attributable, the impressions totalizationstructure 800 is provided with aUUIDs column 804. A value of 100,000 in theUUIDs column 804 is indicative of 100,000 unique users. Thus, the first entry of the impressions totalizationstructure 800 indicates that 100,000 unique users (i.e., UUIDs = 100,000) were exposed once (i.e., frequency = 1) in a single day to a particular ad campaign. - To track impressions based on exposure frequency and UUIDs, the impressions totalization
structure 800 is provided with animpressions column 806. Each impression count stored in theimpressions column 806 is determined by multiplying a corresponding frequency value stored in thefrequency column 802 with a corresponding UUID value stored in theUUID column 804. For example, in the second entry of the impressions totalizationstructure 800, the frequency value of two is multiplied by 200,000 unique users to determine that 400,000 impressions are attributable to a particular ad campaign. - Turning to
FIG. 9 , an ad campaign-level age/gender and impressioncomposition data structure 900 is shown, which, in the illustrated example, may be generated by thereport generator 412 ofFIG. 4 . The impression data in the ad campaign-level age/gender andimpression composition structure 900 ofFIG. 9 corresponds to impressions attributable to registered user of a particular partner database (DB) proprietor (e.g., the partnerA database proprietor 104a ofFIGS. 1 and2 or the partnerB database proprietor 104b ofFIG. 1 ). Similar tables can be generated for content and/or other media. Additionally or alternatively, other media in addition to advertisements may be added to thedata structure 900. - The ad campaign-level age/gender and
impression composition structure 900 is provided with an age/gender column 902, animpressions column 904, afrequency column 906, and animpression composition column 908. The age/gender column 902 of the illustrated example indicates different age/gender demographic groups. Theimpressions column 904 of the illustrated example stores values indicative of the total impressions for a particular ad campaign for corresponding age/gender demographic groups. Thefrequency column 906 of the illustrated example stores values indicative of the frequency of exposure per user for the ad campaign that contributed to the impressions in theimpressions column 904. Theimpressions composition column 908 of the illustrated example stores the percentage of impressions for each of the age/gender demographic groups. - In some examples, the
demographics analyzer 406 and thedemographics modifier 408 ofFIG. 4 perform demographic accuracy analyses and adjustment processes on demographic information before tabulating final results of impression-based demographic information in the campaign-level age/gender and impression composition table 900. This can be done to address a problem facing online audience measurement processes in that the manner in which registered users represent themselves to online database proprietors (e.g., thepartners demographics analyzer 406 and/or thedemographics modifier 408 may use example methods, systems, apparatus, and/or articles of manufacture disclosed inU.S. patent application serial no. 13/209,292, filed on August 12, 2011 - Although the example ad campaign-level age/gender and
impression composition structure 900 shows impression statistics in connection with only age/gender demographic information, thereport generator 412 ofFIG. 4 may generate the same or other data structures to additionally or alternatively include other types of demographic information. In this manner, thereport generator 412 can generate the impression reports 106a (FIGS. 1 and4 ) to reflect impressions based on different types of demographics and/or different types of media. -
FIGS. 10-13 are flow diagrams representative of machine readable instructions that can be executed to implement the apparatus and systems ofFIGS. 1 ,2 ,3 , and/or 4. The example processes ofFIGS. 10-13 may be implemented using machine readable instructions that, when executed, cause a device (e.g., a programmable controller or other programmable machine or integrated circuit) to perform the operations shown inFIGS. 10-13 . In this example, the machine readable instructions comprise a program for execution by a processor such as theprocessor 2912 shown in theexample computer 2910 discussed below in connection withFIG. 29 . The program may be embodied in software stored on a tangible computer readable medium such as a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), a BluRay disk, a flash memory, a read-only memory (ROM), a random-access memory (RAM), or a memory associated with theprocessor 2912, but the entire program and/or parts thereof could alternatively be executed by a device other than theprocessor 2912 and/or embodied in firmware or dedicated hardware. - As used herein, the term tangible computer readable medium is expressly defined to include any type of computer readable storage and to exclude propagating signals. Additionally or alternatively, the example processes of
FIGS. 10-13 may be implemented using coded instructions (e.g., computer readable instructions) stored on a non-transitory computer readable medium such as a flash memory, a read-only memory (ROM), a random-access memory (RAM), a cache, or any other storage media in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term non-transitory computer readable medium is expressly defined to include any type of computer readable medium and to exclude propagating signals. As used herein, when the phrase "at least" is used as the transition term in a preamble of a claim, it is open-ended in the same manner as the term "comprising" is open ended. Thus, a claim using "at least" as the transition term in its preamble may include elements in addition to those expressly recited in the claim. - Alternatively, the example processes of
FIGS. 10-13 may be implemented using any combination(s) of application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)), field programmable logic device(s) (FPLD(s)), discrete logic, hardware, firmware, etc. Also, the example processes ofFIGS. 10-13 may be implemented as any combination(s) of any of the foregoing techniques, for example, any combination of firmware, software, discrete logic and/or hardware. - Although the example processes of
FIGS. 10-13 are described with reference to the flow diagrams ofFIGS. 10-13 , other methods of implementing the apparatus and systems ofFIGS. 1 ,2 ,3 , and/or 4 may be employed. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, sub-divided, or combined. Additionally, one or both of the example processes ofFIGS. 10-13 may be performed sequentially and/or in parallel by, for example, separate processing threads, processors, devices, discrete logic, circuits, etc. - Turning in detail to
FIG. 10 , the depicted example processes may be used to report login events and user cookies (e.g., theAME cookie 208 and thepartner A cookie 228 ofFIGS. 2 and3 ) to database proprietors (e.g., the partnerA database proprietor 104a ofFIGS. 1 and2 ). In the illustrated example, the flow diagram shows aclient device process 1002 and an impressionmonitor system process 1004. In the illustrated example, theclient device process 1002 may be performed by thecookie reporter 202 ofFIGS. 2 and15 , and the impressionmonitor system process 1004 may be implemented by theimpression monitor system 102 ofFIGS. 1-3 and14 . The example processes ofFIG. 10 are described in connection withFIG. 2 as interactions between theclient device 108, theimpression monitor system 102, and the partnerA database proprietor 104a. However, processes similar or identical to the example processes ofFIG. 10 may be performed at any time or at the same time between other client devices, theimpression monitor system 102 and/or other database proprietors to accomplish the same type of user login reporting events when users login to login pages (e.g., thelogin page 204 ofFIG. 2 ) of respective database proprietors (e.g., thedatabase proprietors FIGS. 1 and2 ). - Initially, as part of the
client device process 1002, the login event detector 1502 (FIG. 15 ) detects a login event (block 1006). The login event may be, for example, a user of theclient device 108 logging into thelogin page 204 ofFIG. 2 . The message generator 1508 (FIG. 15 ) generates the request 206 (FIG. 2 ) to indicate the login event (block 1008). The cookie status detector 1504 (FIG. 15 ) determines whether an AME cookie (e.g. theAME cookie 208 ofFIG. 2 ) is already set in the client device 108 (block 1010). If theAME cookie 208 is already set, the cookie interface 1506 (FIG. 15 ) and/or themessage generator 1508 store(s) the AME cookie 208 (e.g., a name-value pair identifying a user) in the request 206 (block 1012). After storing theAME cookie 208 in the request 206 (block 1012) or if theAME cookie 208 is not already set in the client device (block 1010), the communication interface 1510 (FIG. 15 ) sends therequest 206 to the impression monitor system 102 (block 1014). - As shown in the example impression
monitor system process 1004, the communication interface 1412 (FIG. 14 ) receives the request 206 (block 1016), and the cookie status detector 1402 (FIG. 14 ) determines whether theAME cookie 208 is already set in the client device 108 (block 1018). For example, thecookie status detector 1402 can determine whether theAME cookie 208 is already set based on whether therequest 206 contains theAME cookie 208. If thecookie status detector 1402 determines that theAME cookie 208 is not already set (block 1018), the cookie generator 1404 (FIG. 14 ) creates the AME cookie 208 (block 1020). For example, thecookie generator 1404 can generate theAME cookie 208 by generating a UUID for theclient device 108. The message generator 1408 (FIG. 14 ) stores theAME cookie 208 in the response 216 (FIG. 2 ) (block 1022). - After storing the
AME cookie 208 in the response 216 (block 1022) or if thecookie status detector 1402 determines atblock 1018 that theAME cookie 208 is already set in theclient device 108, thetimestamp generator 1406 generates a login timestamp (e.g., thelogin timestamp 220 ofFIG. 2 ) (block 1024) to indicate a login time for the detected login event. Themessage generator 1408 stores thelogin timestamp 220 in the response 216 (block 1026), and thecommunication interface 1412 sends theresponse 216 to the client device 108 (block 1028). - Returning to the
client device process 1002, the communication interface 1510 (FIG. 15 ) receives the response 216 (block 1030), and the message generator 1508 (FIG. 15 ) generates the login reporting message 118 (FIGS. 1 and2 ) (block 1032). If present, the cookie interface 1506 (FIG. 15 ) and/or themessage generator 1508 store(s) a partner cookie corresponding to the login event detected at block 1006 (e.g., the partner A cookie 228) in the login reporting message 118 (block 1034). If a corresponding partner cookie is not present in theclient device 108, a partner cookie is not stored in thelogin reporting message 118 to indicate to the corresponding partner that it should create a partner cookie for theclient device 108. In addition, thecookie interface 1506 and/or themessage generator 1508 store(s) theAME cookie 208 as a data parameter (e.g., in the payload 232) in the login reporting message 118 (block 1036). Themessage generator 1508 also stores thelogin timestamp 220 in the login reporting message 118 (e.g., in the payload 232) (block 1038). Thecommunication interface 1510 sends thelogin reporting message 118 to a corresponding partner database proprietor (e.g., the partnerA database proprietor 104a) (block 1040). In this manner, thecookie reporter 202 enables the partnerA database proprietor 104a to map thepartner A cookie 228 to theAME cookie 208 and thelogin timestamp 220 in thepartner cookie map 236 ofFIGS. 2 and5 . The example process ofFIG. 10 then ends. - Turning now to
FIG. 11 , the depicted flow diagram is representative of an example process that may be performed by a partner database proprietor (e.g., thepartner database proprietors 104a and/or 104b ofFIGS. 1 and2 ) to map AME cookie identifiers (e.g., a UUID of theAME cookie 208 ofFIG. 2 ) with user identifiers (e.g., a UUID of thepartner A cookie 228 ofFIG. 2 ) of users registered with the partner database proprietor. While for simplicity,FIG. 11 refers to a process receiving a single login message, many such processes may exist and execute in parallel (e.g., parallel threads). The example process ofFIG. 11 is described in connection with the illustrated example ofFIG. 2 , theapparatus 400 ofFIG. 4 , and the partnerA database proprietor 104a. However, processes similar or identical to the example processes ofFIG. 11 may be performed at any time or at the same time by other partner database proprietors and/or other apparatus to accomplish the same type of cookie mapping process. - Initially, the partner
A database proprietor 104a receives the login reporting message 118 (FIGS. 1 and2 ) (block 1102). The data parser 414 (FIG. 4 ) extracts the partner A cookie 228 (block 1104) from thelogin reporting message 118. In the illustrated example, thedata parser 414 extracts thepartner A cookie 228 from thecookie field 230 of thelogin reporting message 118. Thedata parser 414 extracts the AME cookie 208 (block 1106) from thelogin reporting message 118. In the illustrated example, thedata parser 414 extracts theAME cookie 208 as a data parameter from thepayload 232 of thelogin reporting message 118. In addition, thedata parser 414 extracts thelogin timestamp 220 from the login reporting message 118 (block 1108). The mapper 416 (FIG. 4 ) maps thepartner A cookie 228 to the AME cookie 208 (e.g., maps the UUIDs of each cookie to one another) (block 1110) in, for example, thepartner cookie map 236 ofFIGS. 2 and5 . In addition, themapper 416 stores thelogin timestamp 220 in association with the mapped cookies (block 1112) in thepartner cookie map 236. The example process ofFIG. 11 then ends. - Now turning to
FIG. 12 , the depicted example process may be performed to log impressions. In the illustrated example, the example process ofFIG. 12 is described in connection withFIGS. 3 and14 as being performed by theimpression monitor system 102 based on tag requests received from theclient device 108. However, processes similar or identical to the example process ofFIG. 12 may be performed at any time or at the same time (e.g., multiple threads may be spawned and execute in parallel) by theimpression monitor system 102 in connection with other client devices (e.g., any of theclient devices 108 ofFIG. 1 or any other client devices) to log impressions attributable to those client devices. - Initially, the communication interface 1412 (
FIG. 14 ) receives a tag request (e.g., thetag request 112 ofFIGS. 1 and3 ) (block 1202). The impression logger 1410 (FIG. 14 ) logs an impression for an AME UUID indicated by the AME cookie 208 (block 1204). In the illustrated example, theimpression logger 1410 logs the impression in theAME impression store 114 ofFIGS. 1 ,3 , and6 . Theimpression logger 1410 determines whether it should send the AME impression logs 122 (FIGS. 1 and4 ) to one or more partner database proprietors (block 1206). For example, theimpression logger 1410 may be configured to periodically or aperiodically send the AME impression logs 122 to one or more partner database proprietors (e.g., thepartner database proprietors FIGS. 1 and2 ) based on one or more of a schedule and/or a threshold of logged impressions. - If the
impression logger 1410 determines that it should send the AME impression logs 122 to one or more partner database proprietors (block 1206), thecommunication interface 1412 sends the AME impression logs 122 to the one or more partner database proprietors (block 1208). In response, thecommunication interface 1412 receives one or more impression reports (e.g., the impression reports 106a and 106b ofFIGS. 1 and4 ) from the one or more partner database proprietors (block 1210). In some examples, theimpression monitor system 102 applies weighting factors to impression audience data in impression reports from different database proprietors (e.g., thepartner database proprietors AME 103 for registered users of the particular database proprietor). - After receiving the one or more impression reports (block 1210) or if at
block 1206 theimpression logger 1410 determines that it should not send the AME impression logs 122 to one or more partner database proprietors, theimpression monitor system 102 determines whether it should continue to monitor impressions (block 1212). For example, theimpression monitor system 102 may be configured to monitor impressions until it is turned off or disabled. If theimpression monitor system 102 determines that it should continue to monitor impressions (block 1212), control returns to block 1202. Otherwise, the example process ofFIG. 12 ends. - Turning now to
FIG. 13 , the depicted example process may be used to generate demographics-based impressions reports (e.g., the impression reports 106a and 106b ofFIGS. 1 and4 ). The example process ofFIG. 13 is described in connection withFIG. 4 as being implemented by theexample apparatus 400 via the partnerA database proprietor 104a. However, processes similar or identical to the example process ofFIG. 13 may be performed at any time or at the same time by any other partner database proprietor(s) to generate impression reports based on registered users of those partner database proprietor(s). - Initially, the
apparatus 400 receives the AME impression logs 122 (FIG. 4 ) (block 1302). The cookie matcher 402 (FIG. 4 ) matches AME cookies to partner database proprietor cookies (block 1304). For example, thecookie matcher 402 can use a cookie map of the corresponding database proprietor (e.g., the partner A cookie map 236 (FIG. 4 )) to match UUIDs from AME cookies (e.g., theAME cookie 208 ofFIGS. 2 and3 ) indicated in the AME impression logs 122 to UUIDs from partner database proprietor cookies (e.g., the partner Adatabase proprietor cookie 228 ofFIGS. 2 and3 ). Thecookie matcher 402 then associates impressions (e.g., impressions noted in the AME impression logs 122) to corresponding partner database proprietor UUIDs (block 1306) based on matches found atblock 1304. For example, thecookie matcher 402 may generate the partner-basedimpressions data structure 700 described above in connection withFIG. 7 . - The demographics associator 404 (
FIG. 4 ) associates demographics of registered users of the corresponding database proprietor (e.g., the partnerA database proprietor 104a) to the impressions (block 1308). For example, the demographics associator 404 may retrieve demographics information from the user accounts database 238 (FIGS. 2 and4 ) for partner user IDs noted in the partneruser ID column 712 of the partner-basedimpressions data structure 700. - The
user ID modifier 410 removes user IDs from the demographics-based impressions data structure 700 (block 1310). For example, theuser ID modifier 410 can remove UUIDs from the AMEuser ID column 702 corresponding to AME cookies (e.g., theAME cookie 208 ofFIGS. 2 and3 ) and the partneruser ID column 712 corresponding to partner cookies (e.g., thepartner A cookie 228 ofFIGS. 2 and3 ). In other examples, thereport generator 412 can copy selected portions from the demographics-basedimpressions data structure 700 and store the selected portions in a report without copying over the user IDs. In this manner, theapparatus 400 can obfuscate identities of registered users to protect their privacy when the demographics-based impressions are shared with others (e.g., an audience measurement entity). - The demographics analyzer 406 (
FIG. 4 ) analyzes the demographics information (block 1312) that was associated with the impressions atblock 1308. The demographics analyzer 406 determines whether any demographics information needs to be modified (block 1314). If any of the demographics information needs to be modified (e.g., demographics information needs to be changed or added due to being incomplete and/or inaccurate), the demographics modifier 408 (FIG. 4 ) modifies select demographics data needing modification (block 1316). In the illustrated example, thedemographics analyzer 406 and/or thedemographics modifier 408 may perform the operations ofblocks U.S. patent application serial no. 13/209,292, filed on August 12, 2011 - After modifying demographics information at
block 1316 or if atblock 1314 thedemographics analyzer 406 determines that none of the demographics information requires modification, thereport generator 412 generates one or more impression reports (e.g., the impression reports 106a ofFIGS. 1 and4 ) (block 1318). For example, thereport generator 412 may generate one or more of the impression reports 106a using one or more example techniques described above in connection withFIGS. 8 and 9 and/or using any other suitable technique(s). Theapparatus 400 then sends the one ormore impression reports 106a to the impression monitor system 102 (block 1320). In the illustrated example, theimpression reports 106a are indicative of demographic segments, populations, or groups associated with different AME cookies 208 (and corresponding partner A cookies 228) and that were exposed to media (e.g., advertisements, content, and/or other media) identified by campaign IDs and/or other the media content IDs. The example process ofFIG. 13 then ends. -
FIG. 16 is a block diagram of anexample system 1600 to generate an adjustment factor. For example, thesystem 1600 may generate an adjustment factor to determine more accurate information based on the information generated in accordance with the methods and apparatus described in conjunction withFIGS. 1-15 . Theexample system 1600 includes one or more panelist meter(s) 1602, adatastore 1604, a cookie topanelist matcher 1606, a panelist tosession matcher 1608, a partner sessions pageviewanalyzer 1610, a panelist sessions pageviewanalyzer 1612, and anadjustment factor generator 1614. - The panelist meter(s) 1602 collect information about computing activity on traditional panelists' computers. According to the illustrated example, the panelist meter(s) 1602 are implemented by software that is installed on traditional panelists' computers. Alternatively, any other type of panelist meter(s) 1602 may be utilized. For example, the panelist meter(s) 1602 may be partly or entirely implemented by a device associated with a computer.
- The panelist meter(s) 1602 of the illustrated example collect information about computing sessions. For example, a computing session may begin when a user logs into the computer, when a user opens a web browser, when the user requests media from a media provider, when a user identifies themselves to the panelist meter(s) 1602, etc. The panelist meter(s) 1602 of the illustrated example determine a user associated with a computing session by prompting a user to identify themself. The panelist meter(s) 1602 also determine an end of a computing session. For example, the panelist meter(s) 1602 may determine that a computing session has ended when a user logs out of the computer, when a user closes a web browser, after a period of time in which there is no user input to the computer, etc. The computing session information is stored in the
datastore 1604. For the computing session information may be stored in a table as shown inFIG. 17 . - According to the example illustrated in
FIG. 17 , the table includes a meter_id field that identifies the panelist meter that collected the information, a member_id field identifying the user associated with the computing session, a computer_id field identifying the computer, a start_time field identifying the start of the computing session, and an end_time field identifying the end of the computing session. - The panelist meter(s) 1602 of the illustrated example also collects information about requests to and responses from media providers. The panelist meter(s) 1602 also collect information about cookies that identify a user to a media provider and/or a partner database provider. For example, when a tag request is sent to a partner database provider, the tag request and a cookie identifying the user to the partner database provider (if one exists) are logged by the panelist meter(s) 1602. In some examples, the cookie is only logged when it is set on the computer instead of logging the cookie each time it is sent with a tag request. The logged information is stored in the
datastore 1604. For example, the logged information may be stored as shown inFIG. 18 . - According to the example illustrated in
FIG. 18 , the logged information includes a cookie_value field identifying the recorded cookie value, a meter_id field that identifies the panelist meter that logged the information, a computer_id field identifying the computer, and a local_time field indicating the time that the cookie value was established (e.g., the time that the user logged in and the cookie was set on the user's computer). - The
datastore 1604 of the illustrated example ofFIG. 16 stores data received from the panelist meter(s) 1602 and transmits the data to one or more of the cookie topanelist matcher 1606, the partner tosession matcher 1608, and the panelist sessions pageviewanalyzer 1612. In some examples, thedatastore 1604 may also store data generated by one or more of the cookie topanelist matcher 1606, the panelist tosession matcher 1608, the partner sessions pageviewanalyzer 1610, and the panelist sessions pageviewanalyzer 1612. Thedatastore 1604 may additionally or alternatively store data from or transmit data to any other element. - The cookie to
panelist matcher 1606 of the illustrated example analyzes the information about computing sessions and the information about partner cookies from the panelist meter(s) 1602 to determine an association of partner cookies and panelist members. The example cookie topanelist matcher 1606 compares the time at which a partner cookie is set (e.g., the time identified in the table ofFIG. 18 ) to computing session start and end times (e.g., the start and end times in the table ofFIG. 17 ) to determine an association of cookies to computing sessions. The example cookie topanelist matcher 1606 also determines a panelist member identified for matching sessions (e.g., from the member ID in the table ofFIG. 17 ). - The cookie to
panelist matcher 1606 of the illustrated example subtotals the number of times that a cookie is associated with each panelist member to generate the table ofFIG. 19 . As shown in the example table ofFIG. 19 ,cookie 100000964240495 is associated with computing sessions ofmember ID 1 twice and is associated withmember ID 2 once. According to the illustrated example, the cookie topanelist matcher 1606 determines thatcookie 100000964240495 is associated withmember ID 1 because the count formember ID 1 is greater than the count formember ID 2. Accordingly, the example cookie topanelist matcher 1606 generates the table ofFIG. 20 , which associates the cookie with the panelist member. The association illustrated in the example ofFIG. 20 indicates a determination as to which panelist member is associated with a particular partner cookie. This process enables demographic information known for the panelist member to be associated with the partner cookie. - The panelist to
session matcher 1608 of the illustrated example utilizes the panelist to partner cookie association from the cookie topanelist matcher 1606 and the information about partner cookie instances from the panelist meter(s) 1602 to determine the start and end of partner cookie sessions. An example partner cookie to panelist association is illustrated inFIG. 21 (this table is similar to the table illustrated inFIG. 20 , but includes an additional panelist member for further explanation). An example listing of partner cookie instances is illustrated inFIG. 22 (this table is similar to the table illustrated inFIG. 18 , but includes an additional partner cookie for further explanation). The example panelist tosession matcher 1608 uses the partner cookie instance times to generate a listing of partner cookie sessions as illustrated inFIG. 23 . A flowchart of an example method for generating the listing of partner cookie sessions is described in conjunction with the flowchart ofFIG. 28 . - The partner sessions pageview
analyzer 1610 of the illustrated example determines demographic information associated with media provider pageviews using the listing of partner cookie sessions from the panelist tosession matcher 1608. The demographic information for the pageviews simulates the demographic information that would be associated with such media provider pageviews using the methods and apparatus described in conjunction withFIGS. 1-15 . The demographic information is determined by retrieving the demographic information from the panelist information determined to be associated with the partner cookies because the demographic information from the partner is typically not available due to privacy restrictions. The example partner sessions pageviewanalyzer 1610 aggregates information based on gender and age to determine a number of pageviews as shown incolumn 2402 ofFIG. 24 . - The panelist sessions pageview
analyzer 1612 of the illustrated example determines demographic information associated with media provider pageviews using the panelist member information determined by the panelist meter(s) 1602. For example, where the panelist meter(s) 1602 prompt users of the computing device to input their identity, the demographic information utilized by the panelist sessions pageviewanalyzer 1612 is the demographic information associated with the panelist member identified in response to the prompting. The example panelist sessions pageviewanalyzer 1612 aggregates information based on gender and age to determine a number of pageviews as shown incolumn 2404 ofFIG. 24 . The identity of the user of the computing device determined based on the panelist meter(s) 1602 represents the control information against which the partner cookie demographic determination is compared. - The
adjustment factor generator 1614 of the illustrated example compares the pageview information from the partner sessions pageviewanalyzer 1610 with the pageview information from the panelist sessions pageviewanalyzer 1612 to determine an adjustment factor. The adjustment factor is a correction value to be applied to pageview counts determined using the partner cookie and partner databases. In other words, the adjustment factor represents the statistical difference between demographic information determined using the partner cookie (e.g., according to the methods and apparatus ofFIGS. 1-15 ) and demographic information determined from the panelist meter(s) 1602. For example,column 2406 ofFIG. 24 indicates an adjustment factor calculated for each demographic category by dividing the pageviews determined using demographic information from the partner cookie (column 2402) by the pageviews determined using the panelist meter(s) 1602 demographic information (column 2404). The "ALL" row ofFIG. 24 indicates that 10,810 pageviews (40,943 - 30,133) had no partner cookie associated with them, which results in anadjustment factor 74%. In other words, determining pageviews using the partner cookie accounts for 74% of pageviews and an pageview count determined based on the partner cookies should be scaled according (e.g., pageviews determined using partner cookie should be divided by 0.74) to account for pageviews by computing devices having no partner cookie. - In some examples, the
system 1600 may additionally or alternatively determine counts for unique users instead of individual pageviews by determining the number of unique users for a media provider using the panelist meter(s) 1602 and the partner cookie information. An example table illustrating counts and adjustment factors for unique audience is illustrated inFIG. 25 . - While the foregoing described of the
system 1600 ofFIG. 16 refers to media provider pageviews, any other computing activity may be analyzed and demographic information may be associated with the computing activity. -
FIGS. 26-29 are flow diagrams representative of machine readable instructions that can be executed to implement the apparatus and systems ofFIG. 16 . The example processes ofFIGS. 26-29 may be implemented using machine readable instructions that, when executed, cause a device (e.g., a programmable controller or other programmable machine or integrated circuit) to perform the operations shown inFIGS. 26-29 . In this example, the machine readable instructions comprise a program for execution by a processor such as theprocessor 2912 shown in theexample computer 2910 discussed below in connection withFIG. 29 . The program may be embodied in software stored on a tangible computer readable medium such as a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), a BluRay disk, a flash memory, a read-only memory (ROM), a random-access memory (RAM), or a memory associated with theprocessor 2912, but the entire program and/or parts thereof could alternatively be executed by a device other than theprocessor 2912 and/or embodied in firmware or dedicated hardware. - As used herein, the term tangible computer readable medium is expressly defined to include any type of computer readable storage and to exclude propagating signals. Additionally or alternatively, the example processes of
FIGS. 26-29 may be implemented using coded instructions (e.g., computer readable instructions) stored on a non-transitory computer readable medium such as a flash memory, a read-only memory (ROM), a random-access memory (RAM), a cache, or any other storage media in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term non-transitory computer readable medium is expressly defined to include any type of computer readable medium and to exclude propagating signals. As used herein, when the phrase "at least" is used as the transition term in a preamble of a claim, it is open-ended in the same manner as the term "comprising" is open ended. Thus, a claim using "at least" as the transition term in its preamble may include elements in addition to those expressly recited in the claim. - Alternatively, the example processes of
FIGS. 26-29 may be implemented using any combination(s) of application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)), field programmable logic device(s) (FPLD(s)), discrete logic, hardware, firmware, etc. Also, the example processes ofFIGS. 26-29 may be implemented as any combination(s) of any of the foregoing techniques, for example, any combination of firmware, software, discrete logic and/or hardware. - Although the example processes of
FIGS. 26-29 are described with reference to the flow diagrams ofFIGS. 26-29 , other methods of implementing the apparatus and systems ofFIG. 16 may be employed. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, sub-divided, or combined. Additionally, one or both of the example processes ofFIG. 16 may be performed sequentially and/or in parallel by, for example, separate processing threads, processors, devices, discrete logic, circuits, etc. - The example process of
FIG. 26 begins when the panelist meter(s) 1602 ofFIG. 16 determine cookie identifiers for partner logins (block 2602) and determine panel member identifiers for computing sessions (block 2604). For example, the panelist meter(s) 1602 may meter a computing device for a period of time collecting the identified information. The panelist meter(s) 1602 may track the determined cookie identifiers for partner logins (block 2602) as illustrated in the example ofFIG. 18 . The panelist meter(s) may track the determined panel member identifiers for computing sessions (block 2604) as illustrated in the example ofFIG. 17 . The information tracked byblocks datastore 1604. - The example cookie to
panelist 1606 then associates partner cookie identifiers with panelist member identifiers (block 2606). An example process for associating partner cookie identifiers with panelist member identifiers is described in conjunction withFIG. 27 . The association of the partner cookie identifiers may be stored in a table or other data structure (e.g., the table illustrated inFIG. 20 . - The example panelist to
session matcher 1608 then associates panelists to computing sessions using the association determined in block 2606 (block 2608). While the panelist meter(s) 1602 associate panelists with computing sessions (e.g., by prompting users to identify themselves), the association ofblock 2608 determines (e.g., simulates) a matching of panelists (and their demographic information) that would be performed by the methods and apparatus ofFIGS. 1-15 . An example process for associating panelists to computing sessions is described in conjunction withFIG. 28 . - Using the association from
block 2608, the example partner sessions pageviewanalyzer 1610 determines pageviews by demographic group (block 2610). The pageviews information ofblock 2610 is indicative of the pageview counts that would be determined using partner cookie information in accordance with the methods and apparatus ofFIGS. 1-15 . According to the illustrated example, the session information in the table ofFIG. 23 is used to associate pageviews at a particular time with a panelist member associated with a computing session using the partner cookie (rather than the panelist member identified by the panelist meter(s) 1602). The pageviews are then aggregated by demographic group. - Using panelist identity information from the panelist meter(s) 1602, the example panelist sessions pageview
analyzer 1612 determines pageviews by demographic group (block 2612). The pageview information ofblock 2612 represents the baseline pageview count by demographic information that is assumed to be accurate. The recorded panelist member associated with a computer session (e.g., determined by prompting a user of a computing device) is utilized to determine demographic information associated with pageviews during a computing session. The pageviews are then aggregated by demographic group. - The
adjustment factor generator 1614 then compares pageviews based on partner cookie information (from block 2608) to pageviews based on panelist member (from block 2610) to determine adjustment factor(s) by demographic group (block 2614). An example process for determining adjustment factors is described in conjunction withFIG. 29 . - In one example, the count of pageviews by demographic using panelist session information (determined in block 2612) may be represented by Pi.j , where i is the index for media providers and j is the index for demographic groups. The count of pageviews by demographic using partner session information (determined in block 2610) may be represented by
- Similarly, an average monthly count of unique panelists belonging to demographic group may be represented by UAi.j , where i is the index for media providers and j is the index for demographic groups. The average monthly count of unique panelists by demographic using partner session information may be represented by
- In some examples, the adjustment factor is calculated at the category of sub-category level (e.g., an adjustment factor may be calculated for all media providers in the News category). For example, the adjustment factor may be calculated at the sub-category when unique audience for a given media provider and demographic group is less than 100.
-
FIG. 27 is a flowchart of an example process to associate partner cookies and panel member identifiers. According to the illustrated example, the process ofFIG. 27 is performed by the cookie topanelist matcher 1606 ofFIG 16 . The example process begins by selecting a first partner cookie identified on a list of cookie instances (block 2702). For example, the partner cookies may be identified on a list as illustrated inFIGS. 18 and/or 22. Next, the cookie instances are matched with computing sessions (e.g., computing sessions identified in a table as illustrated inFIG. 17 ) and the panelist member identifiers associated with the matching computing sessions are subtotaled (block 2704). For example, the member identifiers may be subtotaled as illustrated inFIG. 19 . The panel member identifier with the greatest count in the subtotal is selected (block 2706). An association of the selected partner cookie and the selected member identifier is recorded (block 2708). For example, the association may be recorded as shown inFIGS. 20 and 21 . - After recording the association for the selected partner cookie, the cookie to
panelist matcher 1606 determines if there are additional partner cookies to be processed (block 2710). If there are additional partner cookies to be processed, the next partner cookie is selected (block 2712) and control returns to block 2704 to process the partner cookie. If there are not additional partner cookies to be processed, the process ofFIG. 27 completes. The completion of the process ofFIG. 27 may result in initiation of the process ofFIG. 28 . -
FIG. 28 is a flowchart of an example process to determine session information for panelist members based on cookie to panelist member association information determined by the process illustrated inFIG. 27 . According to the illustrated example, the process ofFIG. 28 is performed by the panelist tosession matcher 1608 ofFIG. 16 . The example process begins by selecting a first partner cookie instance (block 2802). For example, the first partner cookie instance may be selected from a table of partner cookie instances such as the table illustrated inFIGS. 18 and 22 . Next, a panel member identifier for the cookie instance is determined using the cookie to panelist member association information determined by the process illustrated inFIG. 27 (block 2804). The time of the cookie instance is recorded as a session start time for a computing session and the determined panel member identifier is associated with the session (block 2806). For example, the session information may be recorded as illustrated inFIG. 23 . - After recording the session information, the panelist to
session matcher 1608 determines if there are additional partner instances to be processed (block 2808). If there are additional partner cookie instances to be processed, the next partner cookie instance is selected (block 2810). The time of the newly selected cookie instance is recorded as the stop of the session for the previously selected panel member session (block 2812). In other words, the occurrence of each new cookie instance indicates the termination of the previous cookie instance (and thereby the end of a generated panel member browsing session). Control then returns to block 2804 to process the newly selected cookie instance. - If there are not additional partner cookie instances to be processed (block 2808), the process of
FIG. 28 completes. The completion of the process ofFIG. 28 may result in initiation of one or more ofblocks - In some examples, media (e.g., advertisements) is displayed across on several media providers in an advertising network. A measurement entity may not know in advance which media providers will be displaying advertisements. Furthermore, the demographics of different media providers vary depending on the targeted demographic of the webpage (e.g., a sport news webpage vs. an entertainment news webpage). Accordingly, the panelist meter(s) 1602 capture the domain name where media impressions appear (e.g., when the panelist meter(s) 1602 log an impression of an advertisement they also log the domain name of the media provider on which the advertisement was displayed). Where media is displayed on both advertising networks and non-advertising networks (advertisements are provided directly to some media providers), the domain name may be captured for a random sample (e.g., 20% of impressions).
- To determine impressions for an advertising network a composite adjustment factor that is a combination of media provider adjustment factors weighted by impression volume during presentation of the media (e.g., during an advertising campaign) is determined. In some examples, the composite adjustment factor is computed on a daily basis.
- As previously described, the adjustment factor
- After computing adjustment factors, the adjustment factors can be applied to collected monitoring data (e.g., the entire universe of collected, a subset of collected data, etc.). In the following example a reporting entity is a media provider or an advertising network. The following measurement data may be determined by tagging and partner data provider measurement as described in conjunction with
FIGS. 1-15 . Impressions collected by webpage tagging for the United States for entity i may be represented by Ii and impression collected by webpage tagging for global sites may be represented by -
-
- The unique audience international exclusion factor is determined as
- In examples where a total unique audience measurement is not available, it may be assumed that the frequency observed for a partner database provider is the same as the frequency for audience not observed by the partner database provider. Accordingly, a raw observed frequency is determined as
- Once the data has been adjusted, the data can be grouped by campaign to determine impressions and unique audience for a campaign. The set of entities (e.g., media providers and/or advertising networks) belonging to a campaign is represented by Sn , where n is an index of the campaign. The estimated impressions for the campaign can be determined as
- While the foregoing examples describe particular equations for determining impressions and unique audience using calculated adjustment factors, any suitable equations may be used.
-
FIG. 29 is a block diagram of anexample processor system 2910 that may be used to implement the example apparatus, methods, and systems disclosed herein. As shown inFIG. 29 , theprocessor system 2910 includes aprocessor 2912 that is coupled to aninterconnection bus 2914. Theprocessor 2912 may be any suitable processor, processing unit, or microprocessor. Although not shown inFIG. 29 , thesystem 2910 may be a multi-processor system and, thus, may include one or more additional processors that are identical or similar to theprocessor 2912 and that are communicatively coupled to theinterconnection bus 2914. - The
processor 2912 ofFIG. 29 is coupled to achipset 2918, which includes amemory controller 2920 and an input/output (I/O)controller 2922. A chipset provides I/O and memory management functions as well as a plurality of general purpose and/or special purpose registers, timers, etc. that are accessible or used by one or more processors coupled to thechipset 2918. Thememory controller 2920 performs functions that enable the processor 2912 (or processors if there are multiple processors) to access asystem memory 2924, amass storage memory 2925, and/or anoptical media 2927. - In general, the
system memory 2924 may include any desired type of volatile and/or non-volatile memory such as, for example, static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, read-only memory (ROM), etc. Themass storage memory 2925 may include any desired type of mass storage device including hard disk drives, optical drives, tape storage devices, etc. Theoptical media 2927 may include any desired type of optical media such as a digital versatile disc (DVD), a compact disc (CD), or a blu-ray optical disc. The instructions of any ofFIGS. 10-13 may be stored on any of the tangible media represented by thesystem memory 2924, themass storage device 2925, theoptical media 2927, and/or any other media. - The I/
O controller 2922 performs functions that enable theprocessor 2912 to communicate with peripheral input/output (I/O)devices network interface 2930 via an I/O bus 2932. The I/O devices network interface 2930 may be, for example, an Ethernet device, an asynchronous transfer mode (ATM) device, an 802.11 device, a digital subscriber line (DSL) modem, a cable modem, a cellular modem, etc. that enables theprocessor system 2910 to communicate with another processor system. - While the
memory controller 2920 and the I/O controller 2922 are depicted inFIG. 29 as separate functional blocks within thechipset 2918, the functions performed by these blocks may be integrated within a single semiconductor circuit or may be implemented using two or more separate integrated circuits. - Although the above discloses example methods, apparatus, systems, and articles of manufacture including, among other components, firmware and/or software executed on hardware, it should be noted that such methods, apparatus, systems, and articles of manufacture are merely illustrative and should not be considered as limiting. Accordingly, while the above describes example methods, apparatus, systems, and articles of manufacture, the examples provided are not the only ways to implement such methods, apparatus, systems, and articles of manufacture.
- Although certain example methods, apparatus and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus and articles of manufacture fairly falling within the scope of the claims of this patent.
Claims (15)
- An apparatus comprising:a partner sessions pageview analyzer to:increment a first impressions count for a first demographic group associated with a first panelist identifier when a cookie is received at a first client device based on a media impression corresponding to a first panelist, andincrement a second impressions count for the first demographic group associated with the first panelist identifier when a user is identified by a panelist meter associated with the first client device corresponding to the media impression with the first panelist identifier;an adjustment factor generator to determine an adjustment factor based on a comparison of the first impressions count with the second impressions count;memory to store computer-generated data provided by a database proprietor, the computer-generated data representative of impressions logged by a server of the database proprietor based on network communications received by the server from second client devices, the network communications reporting accesses to media via the second client devices, some of the impressions incorrectly attributed by the server to the first demographic group in the computer-generated data when the some of the impressions correspond to a second demographic; andthe adjustment factor generator to determine an adjusted number of impressions based on applying the adjustment factor to the computer-generated data, the adjusted number of impressions to improve a demographic accuracy of the computer-generated data generated by the server.
- The apparatus of claim 1, further including a datastore to:obtain, from the panelist meter installed on the first client device, first impression data logged by the panelist meter in association with the cookie based on access to the media at the first client device, the cookie identifying a user to the database proprietor; andobtain, from the server of the database proprietor, second impression data including a number of impressions attributed by the server to the first demographic group, some of the number of impressions inaccurately attributed by the server to the first demographic group, the network communications based on beacon instructions executed at the first client device, the beacon instructions located in the media accessed at the first client device.
- The apparatus of claim 1, wherein the partner sessions pageview analyzer is to determine that the media impression is associated with the first panelist based on the cookie by:determining a plurality of computing sessions of the first client device;determining a first estimated panelist identifier associated with a first subset of the computing sessions;determining a third panelist identifier associated with a second subset of the computing sessions; anddetermining that the cookie is associated with the first panelist identifier based on the cookie being logged at the first client device during the first subset of the computing sessions more frequently than the cookie is logged at the first client device during the second subset of the computing sessions.
- The apparatus as defined in claim 3, wherein the partner sessions pageview analyzer is to determine the first panelist identifier by:determining a start of an estimated computing session at the first client device based on a first time at which the cookie is logged; anddetermining an end of the estimated computing session at the first client device based on a second time at which a second cookie is logged.
- The apparatus as defined in claim 1, wherein the second impressions count is incremented based on impressions associated with a plurality of panelist meters including the panelist meter.
- The apparatus as defined in claim 1, wherein the adjusted number of impressions is a first adjusted number of impressions, the adjustment factor generator to:determine a first content provider and a second content provider associated with a campaign, the adjustment factor associated with the first content provider;determine a second adjustment factor;combine the second adjustment factor with a second number of impressions determined for the second content provider to determine a second adjusted number of impressions; andadd the first adjusted number of impressions and the second adjusted number of impressions to determine a third adjusted number of impressions for the campaign.
- The apparatus as defined in claim 6, wherein the adjustment factor is to determine a proportion of campaign impressions associated with the first content provider, the third adjusted number of impressions for the campaign determined based on the proportion of campaign impressions associated with the first content provider.
- A computer program comprising instructions which, when executed, cause a machine to at least:increment a first impressions count for a first demographic group associated with a first panelist identifier when a cookie is received at a first client device based on a media impression corresponding to a first panelist;increment a second impressions count for the first demographic group associated with the first panelist identifier when a user is identified by a panelist meter associated with the first client device corresponding to the media impression with the first panelist identifier;determine an adjustment factor based on a comparison of the first impressions count with the second impressions count;store computer-generated data provided by a database proprietor, the computer-generated data representative of impressions logged by a server of the database proprietor based on network communications received by the server from second client devices, the network communications reporting accesses to media via the second client devices, some of the impressions incorrectly attributed by the server to the first demographic group in the computer-generated data when the some of the impressions correspond to a second demographic; anddetermine an adjusted number of impressions based on applying the adjustment factor to the computer-generated data, the adjusted number of impressions to improve a demographic accuracy of the computer-generated data generated by the server.
- The computer readable storage medium of claim 8, wherein the instructions cause the machine to at least:obtain, from the panelist meter installed on the first client device, first impression data logged by the panelist meter in association with the cookie based on access to the media at the first client device, the cookie identifying a user to the database proprietor; andobtain, from the server of the database proprietor, second impression data including a number of impressions attributed by the server to the first demographic group, some of the number of impressions inaccurately attributed by the server to the first demographic group, the network communications based on beacon instructions executed at the first client device, the beacon instructions located in the media accessed at the first client device.
- The computer readable storage medium of claim 8, wherein the instructions cause the machine to at least determine that the media impression is associated with the first panelist based on the cookie by:determining a plurality of computing sessions of the first client device;determining a first estimated panelist identifier associated with a first subset of the computing sessions;determining a third panelist identifier associated with a second subset of the computing sessions; anddetermining that the cookie is associated with the first panelist identifier based on the cookie being logged at the first client device during the first subset of the computing sessions more frequently than the cookie is logged at the first client device during the second subset of the computing sessions.
- The computer readable storage medium as defined in claim 10, wherein the instructions cause the machine to at least determine the first panelist identifier by:determining a start of an estimated computing session at the first client device based on a first time at which the cookie is logged; anddetermining an end of the estimated computing session at the first client device based on a second time at which a second cookie is logged.
- The computer readable storage medium as defined in claim 8, wherein the second impressions count is incremented based on impressions associated with a plurality of panelist meters including the panelist meter.
- The computer readable storage medium as defined in claim 8, wherein the adjusted number of impressions is a first adjusted number of impressions, the instructions cause to the machine to at least:determine a first content provider and a second content provider associated with a campaign, the adjustment factor associated with the first content provider;determine a second adjustment factor;combine the second adjustment factor with a second number of impressions determined for the second content provider to determine a second adjusted number of impressions; andadd the first adjusted number of impressions and the second adjusted number of impressions to determine a third adjusted number of impressions for the campaign.
- The computer readable storage medium as defined in claim 13, wherein the instructions cause the machine to at least determine a proportion of campaign impressions associated with the first content provider, the third adjusted number of impressions for the campaign determined based on the proportion of campaign impressions associated with the first content provider.
- A method comprising:incrementing a first impressions count for a first demographic group associated with a first panelist identifier when a cookie is received at a first client device based on a media impression corresponding to a first panelist,incrementing a second impressions count for the first demographic group associated with the first panelist identifier when a user is identified by a panelist meter associated with the first client device corresponding the media impression with the first panelist identifier;determining an adjustment factor based on a comparison of the first impressions count with the second impressions count;storing computer-generated data provided by a database proprietor, the computer-generated data representative of impressions logged by a server of the database proprietor based on network communications received by the server from second client devices, the network communications reporting accesses to media via the second client devices, some of the impressions incorrectly attributed by the server to the first demographic group in the computer-generated data when the some of the impressions correspond to a second demographic; anddetermining an adjusted number of impressions based on applying the adjustment factor to the computer-generated data, the adjusted number of impressions to improve a demographic accuracy of the computer-generated data generated by the server.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161454326P | 2011-03-18 | 2011-03-18 | |
EP12760524.4A EP2686779A4 (en) | 2011-03-18 | 2012-02-27 | Methods and apparatus to determine media impressions |
PCT/US2012/026760 WO2012128895A2 (en) | 2011-03-18 | 2012-02-27 | Methods and apparatus to determine media impressions |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP12760524.4A Division EP2686779A4 (en) | 2011-03-18 | 2012-02-27 | Methods and apparatus to determine media impressions |
Publications (1)
Publication Number | Publication Date |
---|---|
EP3693914A1 true EP3693914A1 (en) | 2020-08-12 |
Family
ID=46879955
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP12760524.4A Ceased EP2686779A4 (en) | 2011-03-18 | 2012-02-27 | Methods and apparatus to determine media impressions |
EP20166716.9A Pending EP3693914A1 (en) | 2011-03-18 | 2012-02-27 | Methods and apparatus to determine media impressions |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP12760524.4A Ceased EP2686779A4 (en) | 2011-03-18 | 2012-02-27 | Methods and apparatus to determine media impressions |
Country Status (7)
Country | Link |
---|---|
US (2) | US9118542B2 (en) |
EP (2) | EP2686779A4 (en) |
JP (3) | JP5769816B2 (en) |
CN (2) | CN106156363B (en) |
AU (1) | AU2012231667B9 (en) |
CA (1) | CA2810264C (en) |
WO (1) | WO2012128895A2 (en) |
Families Citing this family (101)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8307006B2 (en) | 2010-06-30 | 2012-11-06 | The Nielsen Company (Us), Llc | Methods and apparatus to obtain anonymous audience measurement data from network server data for particular demographic and usage profiles |
US11869024B2 (en) | 2010-09-22 | 2024-01-09 | The Nielsen Company (Us), Llc | Methods and apparatus to analyze and adjust demographic information |
US9092797B2 (en) | 2010-09-22 | 2015-07-28 | The Nielsen Company (Us), Llc | Methods and apparatus to analyze and adjust demographic information |
CA3027898C (en) | 2010-09-22 | 2023-01-17 | The Nielsen Company (Us), Llc | Methods and apparatus to determine impressions using distributed demographic information |
CA2977942C (en) | 2010-12-20 | 2021-08-03 | The Nielsen Company (Us), Llc | Methods and apparatus to determine media impressions using distributed demographic information |
CA2810264C (en) | 2011-03-18 | 2020-06-09 | The Nielsen Company (Us), Llc | Methods and apparatus to determine media impressions |
US8538333B2 (en) | 2011-12-16 | 2013-09-17 | Arbitron Inc. | Media exposure linking utilizing bluetooth signal characteristics |
US8966021B1 (en) * | 2011-12-20 | 2015-02-24 | Amazon Technologies, Inc. | Composable machine image |
US9015255B2 (en) | 2012-02-14 | 2015-04-21 | The Nielsen Company (Us), Llc | Methods and apparatus to identify session users with cookie information |
US8973023B1 (en) | 2012-02-29 | 2015-03-03 | The Nielsen Company (Us), Llc | Methods and apparatus to determine audience duplication in cross-media campaigns |
US9965767B2 (en) | 2012-04-20 | 2018-05-08 | Comscore, Inc. | Attribution of demographics to census data |
US9292856B1 (en) * | 2012-04-25 | 2016-03-22 | Comscore, Inc. | Audience duplication for parent-child resource pairs |
AU2013204865B2 (en) | 2012-06-11 | 2015-07-09 | The Nielsen Company (Us), Llc | Methods and apparatus to share online media impressions data |
AU2013204953B2 (en) | 2012-08-30 | 2016-09-08 | The Nielsen Company (Us), Llc | Methods and apparatus to collect distributed user information for media impressions |
US20140108130A1 (en) * | 2012-10-12 | 2014-04-17 | Google Inc. | Calculating audience metrics for online campaigns |
US9154565B2 (en) * | 2012-11-29 | 2015-10-06 | The Nielsen Company (Us), Llc | Methods and apparatus to monitor online activity |
US9503536B2 (en) | 2013-03-14 | 2016-11-22 | The Nielsen Company (Us), Llc | Methods and apparatus to monitor media presentations |
US20140280888A1 (en) * | 2013-03-15 | 2014-09-18 | Francis Gavin McMillan | Methods, Apparatus and Articles of Manufacture to Monitor Media Devices |
US9697533B2 (en) | 2013-04-17 | 2017-07-04 | The Nielsen Company (Us), Llc | Methods and apparatus to monitor media presentations |
US9635404B2 (en) * | 2013-04-24 | 2017-04-25 | The Nielsen Company (Us), Llc | Methods and apparatus to correlate census measurement data with panel data |
US9560149B2 (en) | 2013-04-24 | 2017-01-31 | The Nielsen Company (Us), Llc | Methods and apparatus to create a panel of media device users |
US9519914B2 (en) | 2013-04-30 | 2016-12-13 | The Nielsen Company (Us), Llc | Methods and apparatus to determine ratings information for online media presentations |
US20140337104A1 (en) * | 2013-05-09 | 2014-11-13 | Steven J. Splaine | Methods and apparatus to determine impressions using distributed demographic information |
US10068246B2 (en) | 2013-07-12 | 2018-09-04 | The Nielsen Company (Us), Llc | Methods and apparatus to collect distributed user information for media impressions |
US10776834B2 (en) | 2013-07-15 | 2020-09-15 | Criteo Sa | Domain selection for advertisement data |
US9313294B2 (en) | 2013-08-12 | 2016-04-12 | The Nielsen Company (Us), Llc | Methods and apparatus to de-duplicate impression information |
US9723051B2 (en) * | 2013-08-13 | 2017-08-01 | Criteo Sa | Setting first-party cookies by redirection |
US10333882B2 (en) | 2013-08-28 | 2019-06-25 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate demographics of users employing social media |
US9332035B2 (en) * | 2013-10-10 | 2016-05-03 | The Nielsen Company (Us), Llc | Methods and apparatus to measure exposure to streaming media |
US10051066B1 (en) | 2013-11-06 | 2018-08-14 | Google Llc | Sharing panelist information without providing cookies |
CA2931106C (en) * | 2013-11-19 | 2020-06-23 | The Nielsen Company (Us), Llc | Methods and apparatus to measure a cross device audience |
US9565090B1 (en) * | 2013-11-21 | 2017-02-07 | Facebook, Inc. | Measuring deletion of cookies included in browsers used by online system users |
US20150181267A1 (en) * | 2013-12-19 | 2015-06-25 | Simulmedia, Inc. | Systems and methods for inferring and forecasting viewership and demographic data for unmonitored media networks |
US10956947B2 (en) | 2013-12-23 | 2021-03-23 | The Nielsen Company (Us), Llc | Methods and apparatus to measure media using media object characteristics |
US9852163B2 (en) | 2013-12-30 | 2017-12-26 | The Nielsen Company (Us), Llc | Methods and apparatus to de-duplicate impression information |
US9237138B2 (en) * | 2013-12-31 | 2016-01-12 | The Nielsen Company (Us), Llc | Methods and apparatus to collect distributed user information for media impressions and search terms |
US20150193816A1 (en) | 2014-01-06 | 2015-07-09 | The Nielsen Company (Us), Llc | Methods and apparatus to correct misattributions of media impressions |
US10147114B2 (en) | 2014-01-06 | 2018-12-04 | The Nielsen Company (Us), Llc | Methods and apparatus to correct audience measurement data |
FR3018408B1 (en) * | 2014-03-06 | 2017-05-26 | Mediametrie | METHOD FOR MEASURING THE CENTER-USER AUDIENCE OF A CONTENT, COMBINING A MARKING TECHNIQUE WITH A PANELING TECHNIQUE |
US9953330B2 (en) | 2014-03-13 | 2018-04-24 | The Nielsen Company (Us), Llc | Methods, apparatus and computer readable media to generate electronic mobile measurement census data |
CA3119830C (en) | 2014-03-13 | 2023-11-14 | The Nielsen Company (Us), Llc | Methods and apparatus to compensate impression data for misattribution and/or non-coverage by a database proprietor |
US9602368B1 (en) * | 2014-03-14 | 2017-03-21 | Google Inc. | Identifier quality |
US10332145B2 (en) * | 2014-05-06 | 2019-06-25 | Insightexpress, Inc. | Techniques for co-usage adjustment of audience verification |
US10311464B2 (en) | 2014-07-17 | 2019-06-04 | The Nielsen Company (Us), Llc | Methods and apparatus to determine impressions corresponding to market segments |
US20160063539A1 (en) | 2014-08-29 | 2016-03-03 | The Nielsen Company (Us), Llc | Methods and apparatus to associate transactions with media impressions |
US9923942B2 (en) * | 2014-08-29 | 2018-03-20 | The Nielsen Company (Us), Llc | Using messaging associated with adaptive bitrate streaming to perform media monitoring for mobile platforms |
US9402111B2 (en) * | 2014-09-17 | 2016-07-26 | Ispot.Tv, Inc. | Television audience measurement method and apparatus |
US10810607B2 (en) | 2014-09-17 | 2020-10-20 | The Nielsen Company (Us), Llc | Methods and apparatus to monitor media presentations |
US20160125439A1 (en) * | 2014-10-31 | 2016-05-05 | The Nielsen Company (Us), Llc | Methods and apparatus to correct segmentation errors |
US20160189182A1 (en) | 2014-12-31 | 2016-06-30 | The Nielsen Company (Us), Llc | Methods and apparatus to correct age misattribution in media impressions |
US10091252B2 (en) * | 2015-04-10 | 2018-10-02 | Microsoft Technology Licensing, Llc | Endpoint control for a communication session |
US9870486B2 (en) | 2015-05-28 | 2018-01-16 | The Nielsen Company (Us), Llc | Methods and apparatus to assign demographic information to panelists |
US10045082B2 (en) | 2015-07-02 | 2018-08-07 | The Nielsen Company (Us), Llc | Methods and apparatus to correct errors in audience measurements for media accessed using over-the-top devices |
US10380633B2 (en) | 2015-07-02 | 2019-08-13 | The Nielsen Company (Us), Llc | Methods and apparatus to generate corrected online audience measurement data |
US9838754B2 (en) | 2015-09-01 | 2017-12-05 | The Nielsen Company (Us), Llc | On-site measurement of over the top media |
WO2017054051A1 (en) * | 2015-10-01 | 2017-04-06 | Roy Morgan Research Ltd | Mapping web impressions to a unique audience |
US20170127133A1 (en) * | 2015-10-30 | 2017-05-04 | The Nielsen Company (Us), Llc | Methods and apparatus to categorize media impressions by age |
US10193988B2 (en) | 2015-11-06 | 2019-01-29 | Criteo Sa | Setting a first-party user ID cookie on a web servers domain |
US10313752B2 (en) * | 2015-11-30 | 2019-06-04 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate deduplicated total audiences in cross-platform media campaigns |
US10205994B2 (en) | 2015-12-17 | 2019-02-12 | The Nielsen Company (Us), Llc | Methods and apparatus to collect distributed user information for media impressions |
AU2016369558A1 (en) * | 2015-12-18 | 2018-07-12 | Pebblepost, Inc. | Collateral generation system for direct mail |
US10244278B2 (en) * | 2015-12-28 | 2019-03-26 | The Nielsen Company (Us), Llc | Methods and apparatus to perform identity matching across audience measurement systems |
US10270673B1 (en) | 2016-01-27 | 2019-04-23 | The Nielsen Company (Us), Llc | Methods and apparatus for estimating total unique audiences |
US20170228795A1 (en) * | 2016-02-05 | 2017-08-10 | The Nielsen Company (Us), Llc | Methods and apparatus to associate panelist data with census data |
US9872072B2 (en) * | 2016-03-21 | 2018-01-16 | Google Llc | Systems and methods for identifying non-canonical sessions |
US10193882B2 (en) | 2016-06-12 | 2019-01-29 | Criteo Sa | Provision of cross-device identification |
US10210459B2 (en) | 2016-06-29 | 2019-02-19 | The Nielsen Company (Us), Llc | Methods and apparatus to determine a conditional probability based on audience member probability distributions for media audience measurement |
US10769670B2 (en) | 2016-08-17 | 2020-09-08 | Criteo Sa | Runtime matching of computing entities |
JP6534977B2 (en) * | 2016-08-19 | 2019-06-26 | 株式会社インテージ | Advertising contact situation analysis system and advertising contact situation analysis method |
WO2018107459A1 (en) * | 2016-12-16 | 2018-06-21 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate media impression frequency distributions |
JP6517182B2 (en) * | 2016-12-16 | 2019-05-22 | ソフトバンク株式会社 | Identifier synchronization system, advertisement delivery system, and program |
US10834449B2 (en) | 2016-12-31 | 2020-11-10 | The Nielsen Company (Us), Llc | Methods and apparatus to associate audience members with over-the-top device media impressions |
US10469903B2 (en) | 2017-02-09 | 2019-11-05 | The Nielsen Company (Us), Llc | Methods and apparatus to correct misattributions of media impressions |
US10728614B2 (en) | 2017-02-28 | 2020-07-28 | The Nielsen Company (Us), Llc | Methods and apparatus to replicate panelists using a local minimum solution of an integer least squares problem |
US10602224B2 (en) | 2017-02-28 | 2020-03-24 | The Nielsen Company (Us), Llc | Methods and apparatus to determine synthetic respondent level data |
US10681414B2 (en) | 2017-02-28 | 2020-06-09 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate population reach from different marginal rating unions |
US20180249211A1 (en) | 2017-02-28 | 2018-08-30 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate population reach from marginal ratings |
US10382818B2 (en) | 2017-06-27 | 2019-08-13 | The Nielson Company (Us), Llc | Methods and apparatus to determine synthetic respondent level data using constrained Markov chains |
US11120486B2 (en) * | 2017-07-24 | 2021-09-14 | Walmart Apollo Llc | Systems and methods for distributing online advertisements |
US10631018B2 (en) | 2017-08-15 | 2020-04-21 | The Nielsen Company (Us), Llc | Methods and apparatus of identification of streaming activity and source for cached media on streaming devices |
US10554616B1 (en) | 2017-12-08 | 2020-02-04 | Criteo S.A. | Generating mobile device-specific identifiers across native mobile applications and mobile browsers |
WO2019191875A1 (en) | 2018-04-02 | 2019-10-10 | The Nielsen Company (Us), Llc | Processor systems to estimate audience sizes and impression counts for different frequency intervals |
CN108876434B (en) * | 2018-05-24 | 2022-08-16 | 北京五八信息技术有限公司 | User portrait construction method and device, computing device and readable storage medium |
US11039190B1 (en) | 2018-07-24 | 2021-06-15 | The Nielsen Company (Us), Llc | Methods and apparatus to determine a unique audience for internet-based media |
WO2020103079A1 (en) | 2018-11-22 | 2020-05-28 | The Nielsen Company (US) , LLC | Methods and apparatus to reduce computer-generated errors in computer-generated audience measurement data |
US11115479B2 (en) | 2019-01-10 | 2021-09-07 | Google Llc | Enhanced online privacy |
US11216834B2 (en) | 2019-03-15 | 2022-01-04 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate population reach from different marginal ratings and/or unions of marginal ratings based on impression data |
US10856027B2 (en) | 2019-03-15 | 2020-12-01 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate population reach from different marginal rating unions |
US11030078B1 (en) * | 2019-06-27 | 2021-06-08 | Facebook, Inc. | Systems and methods for digital content testing |
US11741485B2 (en) | 2019-11-06 | 2023-08-29 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate de-duplicated unknown total audience sizes based on partial information of known audiences |
US11153392B2 (en) | 2019-12-03 | 2021-10-19 | The Nielsen Company (Us), Llc | Methods and apparatus for session building from ping-level data |
US20210319474A1 (en) * | 2020-04-08 | 2021-10-14 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate population reach from marginals |
WO2021231299A1 (en) | 2020-05-13 | 2021-11-18 | The Nielsen Company (Us), Llc | Methods and apparatus to generate computer-trained machine learning models to correct computer-generated errors in audience data |
US11783354B2 (en) | 2020-08-21 | 2023-10-10 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate census level audience sizes, impression counts, and duration data |
US20220058666A1 (en) * | 2020-08-21 | 2022-02-24 | The Nielsen Company (Us), Llc | Estimation and use of duplication factors for audience measurement |
US11481802B2 (en) | 2020-08-31 | 2022-10-25 | The Nielsen Company (Us), Llc | Methods and apparatus for audience and impression deduplication |
US11941646B2 (en) | 2020-09-11 | 2024-03-26 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate population reach from marginals |
US11514131B2 (en) * | 2020-09-23 | 2022-11-29 | Td Ameritrade Ip Company, Inc. | Facilitating inter-system data transfer with serialized data objects |
US11553226B2 (en) | 2020-11-16 | 2023-01-10 | The Nielsen Company (Us), Llc | Methods and apparatus to estimate population reach from marginal ratings with missing information |
EP4035411A1 (en) * | 2020-11-30 | 2022-08-03 | Google LLC | Integrating secure watermarks into content |
US11790397B2 (en) | 2021-02-08 | 2023-10-17 | The Nielsen Company (Us), Llc | Methods and apparatus to perform computer-based monitoring of audiences of network-based media by using information theory to estimate intermediate level unions |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1997041673A2 (en) * | 1996-04-26 | 1997-11-06 | Freedom Of Information, Inc. | Computer network and method for determining user behaviour |
US5948061A (en) * | 1996-10-29 | 1999-09-07 | Double Click, Inc. | Method of delivery, targeting, and measuring advertising over networks |
WO2000041115A1 (en) * | 1998-12-30 | 2000-07-13 | Catalina Marketing International, Inc. | Communicating with a computer based on the offline purchase history of a particular consumer |
US6108637A (en) | 1996-09-03 | 2000-08-22 | Nielsen Media Research, Inc. | Content display monitor |
US20020099609A1 (en) * | 2000-12-01 | 2002-07-25 | Nascenzi Robert A. | Method and system for using customer preferences in real time to customize a commercial transaction |
US20030177488A1 (en) * | 2002-03-12 | 2003-09-18 | Smith Geoff S. | Systems and methods for media audience measurement |
US20040088212A1 (en) * | 2002-10-31 | 2004-05-06 | Hill Clarke R. | Dynamic audience analysis for computer content |
US20100153544A1 (en) * | 2008-12-16 | 2010-06-17 | Brad Krassner | Content rendering control system and method |
WO2010088372A1 (en) * | 2009-01-29 | 2010-08-05 | The Nielsen Company (Us), Llc | Methods and apparatus to measure market statistics |
Family Cites Families (305)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3540003A (en) | 1968-06-10 | 1970-11-10 | Ibm | Computer monitoring system |
US3906450A (en) | 1970-10-09 | 1975-09-16 | Jr Eduardo Da Silva Prado | Electronic system for the recording of periodically sampled variables |
US3818458A (en) | 1972-11-08 | 1974-06-18 | Comress | Method and apparatus for monitoring a general purpose digital computer |
US3906454A (en) | 1973-05-18 | 1975-09-16 | Bell Telephone Labor Inc | Computer monitoring system |
UST955010I4 (en) | 1975-03-12 | 1977-02-01 | International Business Machines Corporation | Hardware/software monitoring system |
US4361832A (en) | 1977-01-28 | 1982-11-30 | Cole Martin T | Automatic centralized monitoring system |
GB1553027A (en) | 1977-05-12 | 1979-09-19 | Marconi Co Ltd | Message signal scrambling apparatus |
US4168396A (en) | 1977-10-31 | 1979-09-18 | Best Robert M | Microprocessor for executing enciphered programs |
US4230990C1 (en) | 1979-03-16 | 2002-04-09 | John G Lert Jr | Broadcast program identification method and system |
US4319079A (en) | 1979-09-13 | 1982-03-09 | Best Robert M | Crypto microprocessor using block cipher |
US4306289A (en) | 1980-02-04 | 1981-12-15 | Western Electric Company, Inc. | Digital computer having code conversion apparatus for an encrypted program |
US4367525A (en) | 1980-06-06 | 1983-01-04 | Tesdata Systems Corporation | CPU Channel monitoring system |
EP0067998B1 (en) | 1980-09-26 | 1986-04-16 | Bo LÖFBERG | Method for processing an information signal and means for carrying out the method |
GB2128453A (en) | 1982-10-08 | 1984-04-26 | Philips Electronic Associated | System identification in communications systems |
US4588991A (en) | 1983-03-07 | 1986-05-13 | Atalla Corporation | File access security method and means |
JPH0648293B2 (en) | 1983-03-18 | 1994-06-22 | 和芙 橋本 | Automatic measurement and alarm device for radioactivity |
US4590550A (en) | 1983-06-29 | 1986-05-20 | International Business Machines Corporation | Internally distributed monitoring system |
US4658093A (en) | 1983-07-11 | 1987-04-14 | Hellman Martin E | Software distribution system |
US4558413A (en) | 1983-11-21 | 1985-12-10 | Xerox Corporation | Software version management system |
US4740890A (en) | 1983-12-22 | 1988-04-26 | Software Concepts, Inc. | Software protection system with trial period usage code and unlimited use unlocking code both recorded on program storage media |
US4754262A (en) | 1984-03-01 | 1988-06-28 | Interactive Technologies, Inc. | Multiplexed alarm system |
US4718005A (en) | 1984-05-03 | 1988-01-05 | International Business Machines Corporation | Distributed control of alias name usage in networks |
US4672572A (en) | 1984-05-21 | 1987-06-09 | Gould Inc. | Protector system for computer access and use |
US4621325A (en) | 1984-06-06 | 1986-11-04 | Information Retrieval Methods, Inc. | Method for monitoring receipt and stocking of goods in a direct store delivery |
US4791565A (en) | 1984-06-20 | 1988-12-13 | Effective Security Systems, Inc. | Apparatus for controlling the use of computer software |
US4747139A (en) | 1984-08-27 | 1988-05-24 | Taaffe James L | Software security method and systems |
US4696034A (en) | 1984-10-12 | 1987-09-22 | Signal Security Technologies | High security pay television system |
GB2176639B (en) | 1985-05-31 | 1988-11-23 | Mars Inc | Data acquisition system |
US4685056A (en) | 1985-06-11 | 1987-08-04 | Pueblo Technologies, Inc. | Computer security device |
US4757533A (en) | 1985-09-11 | 1988-07-12 | Computer Security Corporation | Security system for microcomputers |
US4825354A (en) | 1985-11-12 | 1989-04-25 | American Telephone And Telegraph Company, At&T Bell Laboratories | Method of file access in a distributed processing computer network |
US4720782A (en) | 1986-01-13 | 1988-01-19 | Digital Equipment Corporation | Console unit for clustered digital data processing system |
US4734865A (en) | 1986-01-28 | 1988-03-29 | Bell & Howell Company | Insertion machine with audit trail and command protocol |
US4926255A (en) | 1986-03-10 | 1990-05-15 | Kohorn H Von | System for evaluation of response to broadcast transmissions |
US4821178A (en) | 1986-08-15 | 1989-04-11 | International Business Machines Corporation | Internal performance monitoring by event sampling |
US4977594A (en) | 1986-10-14 | 1990-12-11 | Electronic Publishing Resources, Inc. | Database usage metering and protection system and method |
US4827508A (en) | 1986-10-14 | 1989-05-02 | Personal Library Software, Inc. | Database usage metering and protection system and method |
US5050213A (en) | 1986-10-14 | 1991-09-17 | Electronic Publishing Resources, Inc. | Database usage metering and protection system and method |
US4970644A (en) | 1987-01-02 | 1990-11-13 | Schlumberger Technology Corporation | Reconfigurable well logging system |
US4866769A (en) | 1987-08-05 | 1989-09-12 | Ibm Corporation | Hardware assist for protecting PC software |
US4914689A (en) | 1987-12-22 | 1990-04-03 | Bell Mountain States Telephone & Telegraph Co. | Reverse automatic number identification system |
US4943963A (en) | 1988-01-19 | 1990-07-24 | A. C. Nielsen Company | Data collection and transmission system with real time clock |
US4940976A (en) | 1988-02-05 | 1990-07-10 | Utilicom Inc. | Automated remote water meter readout system |
US4956769A (en) | 1988-05-16 | 1990-09-11 | Sysmith, Inc. | Occurence and value based security system for computer databases |
US5113518A (en) | 1988-06-03 | 1992-05-12 | Durst Jr Robert T | Method and system for preventing unauthorized use of software |
US5023907A (en) | 1988-09-30 | 1991-06-11 | Apollo Computer, Inc. | Network license server |
US4926162A (en) | 1988-10-28 | 1990-05-15 | Honeywell Inc. | High security communication line monitor |
DE3991548C1 (en) | 1989-01-09 | 1995-05-04 | Shogaku Ikueisha Kyoiku Kenkyusho | Electrical device for determining the television programme viewing figures |
ATE143511T1 (en) | 1989-04-28 | 1996-10-15 | Softel Inc | METHOD AND DEVICE FOR REMOTE CONTROL AND MONITORING THE USE OF COMPUTER PROGRAMS |
CA2053261A1 (en) | 1989-04-28 | 1990-10-29 | Gary D. Hornbuckle | Method and apparatus for remotely controlling and monitoring the use of computer software |
US5086386A (en) | 1990-03-23 | 1992-02-04 | Sun Microsystems, Inc. | Method and apparatus for benchmarking the working set of window-based computer systems |
US5214780A (en) | 1990-03-23 | 1993-05-25 | Sun Microsystems, Inc. | Synchronized journaling system |
CA2036205C (en) | 1990-06-01 | 1996-11-19 | Russell J. Welsh | Program monitoring unit |
US5032979A (en) | 1990-06-22 | 1991-07-16 | International Business Machines Corporation | Distributed security auditing subsystem for an operating system |
US5182770A (en) | 1991-04-19 | 1993-01-26 | Geza Medveczky | System and apparatus for protecting computer software |
US5444642A (en) | 1991-05-07 | 1995-08-22 | General Signal Corporation | Computer system for monitoring events and which is capable of automatically configuring itself responsive to changes in system hardware |
US5440738A (en) | 1991-05-16 | 1995-08-08 | Tally Systems Corporation | Method and apparatus for digital data processor file configuration detection |
US5233642A (en) | 1991-05-24 | 1993-08-03 | Omnitronix, Inc. | Cellular telephone usage monitoring system |
US5204897A (en) | 1991-06-28 | 1993-04-20 | Digital Equipment Corporation | Management interface for license management system |
US5406269A (en) | 1991-07-05 | 1995-04-11 | David Baran | Method and apparatus for the remote verification of the operation of electronic devices by standard transmission mediums |
US5355484A (en) | 1991-08-12 | 1994-10-11 | International Business Machines Corporation | Dynamically established event monitors in event management services of a computer system |
US5343239A (en) | 1991-11-20 | 1994-08-30 | Zing Systems, L.P. | Transaction based interactive television system |
US5287408A (en) | 1992-08-31 | 1994-02-15 | Autodesk, Inc. | Apparatus and method for serializing and validating copies of computer software |
US5377269A (en) | 1992-10-29 | 1994-12-27 | Intelligent Security Systems, Inc. | Security access and monitoring system for personal computer |
US5450134A (en) | 1993-01-12 | 1995-09-12 | Visual Automation Systems, Inc. | Video facility management system for encoding and decoding video signals to facilitate identification of the video signals |
US5483658A (en) | 1993-02-26 | 1996-01-09 | Grube; Gary W. | Detection of unauthorized use of software applications in processing devices |
US5499340A (en) | 1994-01-12 | 1996-03-12 | Isogon Corporation | Method and apparatus for computer program usage monitoring |
JP3400068B2 (en) * | 1994-03-18 | 2003-04-28 | 富士通株式会社 | Response amount prediction system |
CA2119970A1 (en) | 1994-03-25 | 1995-09-26 | Michael A. Lyons | Program monitoring system |
IL114359A0 (en) | 1994-06-30 | 1995-10-31 | Walker Asset Management Ltd | System and method for remote gaming |
US5594934A (en) | 1994-09-21 | 1997-01-14 | A.C. Nielsen Company | Real time correlation meter |
US5758257A (en) | 1994-11-29 | 1998-05-26 | Herz; Frederick | System and method for scheduling broadcast of and access to video programs and other data using customer profiles |
WO1996028904A1 (en) | 1995-03-16 | 1996-09-19 | Bell Atlantic Network Services, Inc. | Simulcasting digital video programs for broadcast and interactive services |
US5812928A (en) | 1995-04-12 | 1998-09-22 | Watson Technologies | Cable television control apparatus and method with channel access controller at node of network including channel filtering system |
JPH0944432A (en) | 1995-05-24 | 1997-02-14 | Fuji Xerox Co Ltd | Information processing method and information processor |
US5940738A (en) | 1995-05-26 | 1999-08-17 | Hyundai Electronics America, Inc. | Video pedestal network |
US5675510A (en) | 1995-06-07 | 1997-10-07 | Pc Meter L.P. | Computer use meter and analyzer |
US8574074B2 (en) | 2005-09-30 | 2013-11-05 | Sony Computer Entertainment America Llc | Advertising impression determination |
US6073241A (en) | 1996-08-29 | 2000-06-06 | C/Net, Inc. | Apparatus and method for tracking world wide web browser requests across distinct domains using persistent client-side state |
US6052730A (en) | 1997-01-10 | 2000-04-18 | The Board Of Trustees Of The Leland Stanford Junior University | Method for monitoring and/or modifying web browsing sessions |
US6035339A (en) | 1997-03-13 | 2000-03-07 | At&T Corporation | Network information delivery system for delivering information based on end user terminal requirements |
US5796952A (en) | 1997-03-21 | 1998-08-18 | Dot Com Development, Inc. | Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database |
US6643696B2 (en) | 1997-03-21 | 2003-11-04 | Owen Davis | Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database |
US6247050B1 (en) | 1997-09-12 | 2001-06-12 | Intel Corporation | System for collecting and displaying performance improvement information for a computer |
US6286140B1 (en) | 1997-11-20 | 2001-09-04 | Thomas P. Ivanyi | System and method for measuring and storing information pertaining to television viewer or user behavior |
US6098093A (en) | 1998-03-19 | 2000-08-01 | International Business Machines Corp. | Maintaining sessions in a clustered server environment |
US20020095676A1 (en) | 1998-05-15 | 2002-07-18 | Robert A. Knee | Interactive television program guide system for determining user values for demographic categories |
US6279036B1 (en) | 1998-05-15 | 2001-08-21 | International Business Machines Corporation | Method and apparatus for detecting actual viewing or electronic advertisements |
US7240022B1 (en) | 1998-05-19 | 2007-07-03 | Mypoints.Com Inc. | Demographic information gathering and incentive award system and method |
US6434614B1 (en) | 1998-05-29 | 2002-08-13 | Nielsen Media Research, Inc. | Tracking of internet advertisements using banner tags |
US6223215B1 (en) | 1998-09-22 | 2001-04-24 | Sony Corporation | Tracking a user's purchases on the internet by associating the user with an inbound source and a session identifier |
US6684194B1 (en) | 1998-12-03 | 2004-01-27 | Expanse Network, Inc. | Subscriber identification system |
US7150030B1 (en) | 1998-12-03 | 2006-12-12 | Prime Research Alliance, Inc. | Subscriber characterization system |
US6457010B1 (en) | 1998-12-03 | 2002-09-24 | Expanse Networks, Inc. | Client-server based subscriber characterization system |
US7949565B1 (en) | 1998-12-03 | 2011-05-24 | Prime Research Alliance E., Inc. | Privacy-protected advertising system |
US6164975A (en) | 1998-12-11 | 2000-12-26 | Marshall Weingarden | Interactive instructional system using adaptive cognitive profiling |
US6460079B1 (en) | 1999-03-04 | 2002-10-01 | Nielsen Media Research, Inc. | Method and system for the discovery of cookies and other client information |
US6529952B1 (en) * | 1999-04-02 | 2003-03-04 | Nielsen Media Research, Inc. | Method and system for the collection of cookies and other information from a panel |
US6721713B1 (en) | 1999-05-27 | 2004-04-13 | Andersen Consulting Llp | Business alliance identification in a web architecture framework |
US7523191B1 (en) | 2000-06-02 | 2009-04-21 | Yahoo! Inc. | System and method for monitoring user interaction with web pages |
US6102406A (en) | 1999-06-07 | 2000-08-15 | Steven A. Miles | Internet-based advertising scheme employing scavenger hunt metaphor |
US6606657B1 (en) | 1999-06-22 | 2003-08-12 | Comverse, Ltd. | System and method for processing and presenting internet usage information |
US7010497B1 (en) | 1999-07-08 | 2006-03-07 | Dynamiclogic, Inc. | System and method for evaluating and/or monitoring effectiveness of on-line advertising |
AUPQ206399A0 (en) | 1999-08-06 | 1999-08-26 | Imr Worldwide Pty Ltd. | Network user measurement system and method |
US6415323B1 (en) | 1999-09-03 | 2002-07-02 | Fastforward Networks | Proximity-based redirection system for robust and scalable service-node location in an internetwork |
US6839680B1 (en) | 1999-09-30 | 2005-01-04 | Fujitsu Limited | Internet profiling |
US7007080B2 (en) | 1999-12-23 | 2006-02-28 | Solution Inc Limited | System for reconfiguring and registering a new IP address for a computer to access a different network without user intervention |
US6691163B1 (en) | 1999-12-23 | 2004-02-10 | Alexa Internet | Use of web usage trail data to identify related links |
US6993590B1 (en) | 2000-01-13 | 2006-01-31 | Inktomi Corporation | Method of creating data streams for user-specific usage data gathering systems |
WO2001052173A1 (en) | 2000-01-13 | 2001-07-19 | Erinmedia, Inc. | Privacy compliant multiple dataset correlation system |
US7146329B2 (en) | 2000-01-13 | 2006-12-05 | Erinmedia, Llc | Privacy compliant multiple dataset correlation and content delivery system and methods |
WO2001052168A1 (en) | 2000-01-14 | 2001-07-19 | Matsushita Electric Industrial Company, Limited | Cookie data stored on transportable recording medium |
WO2001054034A1 (en) | 2000-01-21 | 2001-07-26 | Angara E-Commerce Services, Inc. | Electronic commerce services |
US7260837B2 (en) | 2000-03-22 | 2007-08-21 | Comscore Networks, Inc. | Systems and methods for user identification, user demographic reporting and collecting usage data usage biometrics |
US7181412B1 (en) | 2000-03-22 | 2007-02-20 | Comscore Networks Inc. | Systems and methods for collecting consumer data |
JP2001338176A (en) | 2000-03-23 | 2001-12-07 | Casio Comput Co Ltd | Method and system for information transmission and intermediation |
JP2001282982A (en) | 2000-03-28 | 2001-10-12 | Hisahiro Negi | Web marketing system |
US7039699B1 (en) | 2000-05-02 | 2006-05-02 | Microsoft Corporation | Tracking usage behavior in computer systems |
US7962603B1 (en) | 2000-06-06 | 2011-06-14 | Nobuyoshi Morimoto | System and method for identifying individual users accessing a web site |
JP2001357192A (en) * | 2000-06-12 | 2001-12-26 | Toshiba Corp | Method and system for customer awareness research and storage medium storing program |
JP2004504674A (en) * | 2000-07-18 | 2004-02-12 | ヤフー! インコーポレイテッド | System and method for selecting another advertising inventory instead of a sold-out advertising inventory |
WO2002019717A2 (en) | 2000-08-31 | 2002-03-07 | Myrio Corporation | Real-time audience monitoring, content rating, and content enhancing |
JP2002091852A (en) | 2000-09-18 | 2002-03-29 | Seino Information Service Co Ltd | Access history acquiring method and information providing method |
KR20020037980A (en) | 2000-11-16 | 2002-05-23 | 김형순 | System for retrieving and providing information |
US7600014B2 (en) | 2000-11-16 | 2009-10-06 | Symantec Corporation | Method and system for monitoring the performance of a distributed application |
JP4248183B2 (en) | 2001-02-26 | 2009-04-02 | パナソニック株式会社 | Cookie processing program and image data display device |
AU2002305137A1 (en) | 2001-04-06 | 2002-10-21 | Predictive Media Corporation | Method and apparatus for identifying unique client users from user behavioral data |
WO2002084507A1 (en) | 2001-04-13 | 2002-10-24 | Netiq Corporation | User-side tracking of multimedia application usage within a web page |
US7647418B2 (en) | 2001-06-19 | 2010-01-12 | Savvis Communications Corporation | Real-time streaming media measurement system and method |
US20030037131A1 (en) | 2001-08-17 | 2003-02-20 | International Business Machines Corporation | User information coordination across multiple domains |
JP2003067289A (en) | 2001-08-30 | 2003-03-07 | Bear Communications Co Ltd | Delivery system for advertisement on the web |
WO2003027860A1 (en) * | 2001-09-19 | 2003-04-03 | Ntt Advertising, Inc. | Content delivery system for delivering content changing on time axis, content delivery server, log collection server, content relay server, user terminal, content viewing/listening state grasping method, recommendation method, and content providing method |
US20030074252A1 (en) | 2001-10-12 | 2003-04-17 | Avenue A, Inc. | System and method for determining internet advertising strategy |
US6877007B1 (en) | 2001-10-16 | 2005-04-05 | Anna M. Hentzel | Method and apparatus for tracking a user's interaction with a resource supplied by a server computer |
US7343417B2 (en) * | 2001-11-30 | 2008-03-11 | Knowledge Networks, Inc. | System and method for rating media information |
US7272617B1 (en) | 2001-11-30 | 2007-09-18 | Ncr Corp. | Analytic data set creation for modeling in a customer relationship management system |
WO2003065180A2 (en) | 2002-02-01 | 2003-08-07 | John Fairweather | System and method for creating a distributed network architecture |
US20030229884A1 (en) | 2002-05-21 | 2003-12-11 | Hewlett-Packard Development Company | Interaction manager template |
US20040167763A1 (en) | 2002-05-31 | 2004-08-26 | Liebman Michael N | Information processing method for evaluating biochemical pathway models using clinical data |
EP1379044A1 (en) | 2002-06-22 | 2004-01-07 | TELEFONAKTIEBOLAGET LM ERICSSON (publ) | Method for providing information to a web server |
US20040098229A1 (en) | 2002-06-28 | 2004-05-20 | Brett Error | Efficient click-stream data collection |
US20040044566A1 (en) * | 2002-08-30 | 2004-03-04 | Bostelmann Janet K. | Landing page and channel identifier in multichannel marketing system |
US7890451B2 (en) | 2002-10-09 | 2011-02-15 | Compete, Inc. | Computer program product and method for refining an estimate of internet traffic |
US7574423B2 (en) | 2003-03-20 | 2009-08-11 | International Business Machines Corporation | Partial data model exposure through client side caching |
US7505958B2 (en) | 2004-09-30 | 2009-03-17 | International Business Machines Corporation | Metadata management for a data abstraction model |
US20050033657A1 (en) | 2003-07-25 | 2005-02-10 | Keepmedia, Inc., A Delaware Corporation | Personalized content management and presentation systems |
ZA200600900B (en) * | 2003-08-01 | 2007-05-30 | Tacoda Systems Inc | System and method for segmenting and targeting audience members |
US9117217B2 (en) | 2003-08-01 | 2015-08-25 | Advertising.Com Llc | Audience targeting with universal profile synchronization |
US20070198327A1 (en) | 2003-08-15 | 2007-08-23 | Amir Yazdani | Systems and methods for measuring, targeting, verifying, and reporting advertising impressions |
JPWO2005024689A1 (en) * | 2003-09-04 | 2007-11-08 | 株式会社インタースコープ | Method and apparatus for analyzing consumer purchasing behavior |
US11042886B2 (en) * | 2003-09-04 | 2021-06-22 | Google Llc | Systems and methods for determining user actions |
US7152074B2 (en) | 2003-09-19 | 2006-12-19 | International Business Machines Corporation | Extensible framework supporting deposit of heterogenous data sources into a target data repository |
AU2003272178A1 (en) | 2003-10-24 | 2005-05-11 | Telefonaktiebolaget Lm Ericsson (Publ) | A method and device for audience monitoring on multicast capable networks |
US20050144069A1 (en) | 2003-12-23 | 2005-06-30 | Wiseman Leora R. | Method and system for providing targeted graphical advertisements |
US7949639B2 (en) | 2004-02-20 | 2011-05-24 | Symphonyiri Group, Inc. | Attribute segments and data table bias reduction |
US7792954B2 (en) | 2004-04-02 | 2010-09-07 | Webtrends, Inc. | Systems and methods for tracking web activity |
DE202004007054U1 (en) | 2004-05-03 | 2005-09-15 | Brose Fahrzeugteile | Motor vehicle door with side window |
US20050267799A1 (en) | 2004-05-10 | 2005-12-01 | Wesley Chan | System and method for enabling publishers to select preferred types of electronic documents |
US7302447B2 (en) | 2005-01-14 | 2007-11-27 | International Business Machines Corporation | Virtual columns |
CN102523063A (en) | 2004-08-09 | 2012-06-27 | 尼尔森(美国)有限公司 | Methods and apparatus to monitor audio/visual content from various sources |
US7546370B1 (en) | 2004-08-18 | 2009-06-09 | Google Inc. | Search engine with multiple crawlers sharing cookies |
US20060089754A1 (en) | 2004-10-27 | 2006-04-27 | Andrew Mortenson | An installed Vehicle Personal Computing (VPC) system with touch interaction, voice interaction or sensor interaction(s) that provides access to multiple information sources and software applications such as internet connected data applications, dynamic traffic-aware navigational routing, vehicle tracking, emergency accident dispatching, business applications, office applications, music and video player(s), personal info portal, vehicle monitoring, alarm and camera security and recording. |
JP2006127321A (en) * | 2004-10-29 | 2006-05-18 | Solid Technology Kk | Terminal attribute addition device and terminal attribute addition method |
JP2006127320A (en) * | 2004-10-29 | 2006-05-18 | Solid Technology Kk | Terminal attribute estimation apparatus and terminal attribute estimation method |
US8131861B2 (en) | 2005-05-20 | 2012-03-06 | Webtrends, Inc. | Method for cross-domain tracking of web site traffic |
US8583827B2 (en) | 2005-05-26 | 2013-11-12 | Citrix Systems, Inc. | Dynamic data optimization in data network |
US7849154B2 (en) | 2005-06-27 | 2010-12-07 | M:Metrics, Inc. | Acquiring, storing, and correlating profile data of cellular mobile communications system's users to events |
JP4764103B2 (en) | 2005-08-18 | 2011-08-31 | 株式会社東芝 | Content data distribution system and information processing apparatus |
US20090030780A1 (en) | 2006-01-03 | 2009-01-29 | Ds-Iq, Inc. | Measuring effectiveness of marketing campaigns presented on media devices in public places using audience exposure data |
CA2841017C (en) | 2006-03-27 | 2016-12-20 | The Nielsen Company (Us), Llc | Methods and systems to meter media content presented on a wireless communication device |
JP4535016B2 (en) | 2006-03-28 | 2010-09-01 | 住友ベークライト株式会社 | Vinyl chloride resin composition, vinyl chloride resin sheet and molded body produced using the same |
MX2007015979A (en) | 2006-03-31 | 2009-04-07 | Nielsen Media Res Inc | Methods, systems, and apparatus for multi-purpose metering. |
US7941525B1 (en) | 2006-04-01 | 2011-05-10 | ClickTale, Ltd. | Method and system for monitoring an activity of a user |
WO2007146876A2 (en) * | 2006-06-15 | 2007-12-21 | The Nielsen Company | Methods and apparatus to meter content exposure using closed caption information |
US20080004958A1 (en) | 2006-06-29 | 2008-01-03 | Tony Ralph | Client side counting verification testing |
CN100456298C (en) | 2006-07-12 | 2009-01-28 | 百度在线网络技术(北京)有限公司 | Advertisement information retrieval system and method therefor |
CN101523379A (en) * | 2006-08-18 | 2009-09-02 | 阿卡麦科技公司 | Method of data collection in a distributed network |
US20080086523A1 (en) | 2006-08-18 | 2008-04-10 | Akamai Technologies, Inc. | Method of data collection in a distributed network |
US20100004977A1 (en) | 2006-09-05 | 2010-01-07 | Innerscope Research Llc | Method and System For Measuring User Experience For Interactive Activities |
CN101222348B (en) * | 2007-01-10 | 2011-05-11 | 阿里巴巴集团控股有限公司 | Method and system for calculating number of website real user |
US8874563B1 (en) * | 2007-03-07 | 2014-10-28 | Comscore, Inc. | Detecting content and user response to content |
US8166076B2 (en) | 2007-03-08 | 2012-04-24 | Microsoft Corporation | Digital media metadata management |
KR100910517B1 (en) | 2007-03-21 | 2009-07-31 | 엔에이치엔비즈니스플랫폼 주식회사 | System and method for expanding target inventory according to borwser-login mapping |
US8229458B2 (en) | 2007-04-08 | 2012-07-24 | Enhanced Geographic Llc | Systems and methods to determine the name of a location visited by a user of a wireless device |
US20080276179A1 (en) | 2007-05-05 | 2008-11-06 | Intapp Inc. | Monitoring and Aggregating User Activities in Heterogeneous Systems |
US20090217315A1 (en) | 2008-02-26 | 2009-08-27 | Cognovision Solutions Inc. | Method and system for audience measurement and targeting media |
US20080300965A1 (en) | 2007-05-31 | 2008-12-04 | Peter Campbell Doe | Methods and apparatus to model set-top box data |
US7890592B2 (en) | 2007-06-29 | 2011-02-15 | Microsoft Corporation | Processing data obtained from a presence-based system |
US8229780B2 (en) | 2007-07-30 | 2012-07-24 | Silvercarrot, Inc. | System and method for online lead generation |
US20090055241A1 (en) | 2007-08-23 | 2009-02-26 | Att Knowledge Ventures L.P. | System and Method for Estimating a Qualiifed Impression Count for Advertising Data in a Communication System |
US7698422B2 (en) | 2007-09-10 | 2010-04-13 | Specific Media, Inc. | System and method of determining user demographic profiles of anonymous users |
US20090076899A1 (en) | 2007-09-14 | 2009-03-19 | Gbodimowo Gbeminiyi A | Method for analyzing, searching for, and trading targeted advertisement spaces |
US7925694B2 (en) | 2007-10-19 | 2011-04-12 | Citrix Systems, Inc. | Systems and methods for managing cookies via HTTP content layer |
US8180112B2 (en) | 2008-01-21 | 2012-05-15 | Eastman Kodak Company | Enabling persistent recognition of individuals in images |
US8302120B2 (en) * | 2008-02-19 | 2012-10-30 | The Nielsen Company (Us), Llc | Methods and apparatus to monitor advertisement exposure |
WO2009114634A1 (en) * | 2008-03-11 | 2009-09-17 | Hongguag Bi | Ad matching system and method thereof |
US8151194B1 (en) | 2008-03-26 | 2012-04-03 | Google Inc. | Visual presentation of video usage statistics |
US8112301B2 (en) | 2008-04-14 | 2012-02-07 | Tra, Inc. | Using consumer purchase behavior for television targeting |
AU2009251492A1 (en) | 2008-04-17 | 2009-12-03 | Arbitron Inc. | Cross-media interactivity metrics |
US20090307084A1 (en) | 2008-06-10 | 2009-12-10 | Integrated Media Measurement, Inc. | Measuring Exposure To Media Across Multiple Media Delivery Mechanisms |
US20100010866A1 (en) | 2008-07-11 | 2010-01-14 | Microsoft Corporation | Advertising across social network communication pathways |
US8280683B2 (en) | 2008-07-17 | 2012-10-02 | International Business Machines Corporation | Probabilistic framework for the highly efficient correlation of call chains with hardware events |
JP4834042B2 (en) | 2008-08-06 | 2011-12-07 | ヤフー株式会社 | User-created content management device, user-created content management system, and browser preference survey method |
US20100076814A1 (en) | 2008-09-24 | 2010-03-25 | Manning Kathleen E | Method for financial forecasting for associations using actuarial open group simulation |
US20100088152A1 (en) | 2008-10-02 | 2010-04-08 | Dominic Bennett | Predicting user response to advertisements |
US20100088373A1 (en) | 2008-10-06 | 2010-04-08 | Jeremy Pinkham | Method of Tracking & Targeting Internet Payloads based on Time Spent Actively Viewing |
US20100121676A1 (en) | 2008-11-11 | 2010-05-13 | Yahoo! Inc. | Method and system for logging impressions of online advertisments |
US20100153175A1 (en) | 2008-12-12 | 2010-06-17 | At&T Intellectual Property I, L.P. | Correlation of Psycho-Demographic Data and Social Network Data to Initiate an Action |
US20100161385A1 (en) | 2008-12-19 | 2010-06-24 | Nxn Tech, Llc | Method and System for Content Based Demographics Prediction for Websites |
AU2010204563B2 (en) | 2009-01-15 | 2016-05-26 | Google Llc | Requesting offline profile data for online use in a privacy-sensitive manner |
US20100205057A1 (en) | 2009-02-06 | 2010-08-12 | Rodney Hook | Privacy-sensitive methods, systems, and media for targeting online advertisements using brand affinity modeling |
GB2524907A (en) | 2009-03-06 | 2015-10-07 | Appnexus Inc | A computer system |
CN101505247A (en) | 2009-03-09 | 2009-08-12 | 成都市华为赛门铁克科技有限公司 | Detection method and apparatus for number of shared access hosts |
KR101073112B1 (en) | 2009-03-11 | 2011-10-12 | 박상호 | A management method for contents combined work and advertising using an open license and apparatus thereof |
US8150974B2 (en) | 2009-03-17 | 2012-04-03 | Kindsight, Inc. | Character differentiation system generating session fingerprint using events associated with subscriber ID and session ID |
US8266687B2 (en) | 2009-03-27 | 2012-09-11 | Sophos Plc | Discovery of the use of anonymizing proxies by analysis of HTTP cookies |
JP5492630B2 (en) * | 2009-03-31 | 2014-05-14 | 株式会社ビデオリサーチ | Content contact investigation system and content contact investigation method |
US8429287B2 (en) | 2009-04-29 | 2013-04-23 | Rangecast Technologies, Llc | Network audio distribution system and method |
US8990337B2 (en) | 2009-06-08 | 2015-03-24 | Collective, Inc. | Tracking advertising abandonment rates |
CN102473174A (en) | 2009-07-08 | 2012-05-23 | 瑞典爱立信有限公司 | A method and arrangements for analysing multimedia content |
US9178634B2 (en) | 2009-07-15 | 2015-11-03 | Time Warner Cable Enterprises Llc | Methods and apparatus for evaluating an audience in a content-based network |
JP5324352B2 (en) | 2009-07-31 | 2013-10-23 | 寺岡ファシリティーズ株式会社 | Windbreak room door opening / closing control method and apparatus |
US8612860B2 (en) | 2009-08-12 | 2013-12-17 | Warner Music Inc. | Systems, methods, and media for coordinating the presentation of media with an event |
US20120192214A1 (en) | 2009-12-22 | 2012-07-26 | Resonate Networks | Method and apparatus for delivering targeted content to television viewers |
KR101118741B1 (en) | 2009-08-31 | 2012-03-12 | 주식회사 나스미디어 | A method for providing internet advertisement popularity rating |
US8234408B2 (en) | 2009-09-10 | 2012-07-31 | Cloudshield Technologies, Inc. | Differentiating unique systems sharing a common address |
US20110087519A1 (en) | 2009-10-09 | 2011-04-14 | Visa U.S.A. Inc. | Systems and Methods for Panel Enhancement with Transaction Data |
US8082464B2 (en) | 2009-10-13 | 2011-12-20 | International Business Machines Corporation | Managing availability of a component having a closed address space |
US8595058B2 (en) | 2009-10-15 | 2013-11-26 | Visa U.S.A. | Systems and methods to match identifiers |
US8549552B2 (en) * | 2009-11-03 | 2013-10-01 | The Nielsen Company (Us), Llc | Methods and apparatus to monitor media exposure in vehicles |
US8566856B2 (en) | 2009-12-01 | 2013-10-22 | International Business Machines Corporation | Video stream measurement method and system |
CA2783355C (en) | 2009-12-08 | 2016-07-12 | Comscore, Inc. | Systems and methods for identification and reporting of ad delivery hierarchy |
US8925024B2 (en) | 2009-12-31 | 2014-12-30 | The Nielsen Company (Us), Llc | Methods and apparatus to detect commercial advertisements associated with media presentations |
US20110191664A1 (en) | 2010-02-04 | 2011-08-04 | At&T Intellectual Property I, L.P. | Systems for and methods for detecting url web tracking and consumer opt-out cookies |
US20110196735A1 (en) | 2010-02-05 | 2011-08-11 | Von Sydow Gustav | System and method for measuring effectiveness of electronically presented advertizing |
BR112012019739A2 (en) | 2010-02-08 | 2020-09-08 | Facebook, Inc. | method to track information about the activities of users of a social networking system in another domain, system and computer-readable media. |
US8280844B2 (en) | 2010-02-15 | 2012-10-02 | Bank Of America Corporation | Anomalous activity detection |
US20120310729A1 (en) * | 2010-03-16 | 2012-12-06 | Dalto John H | Targeted learning in online advertising auction exchanges |
WO2011116514A1 (en) | 2010-03-23 | 2011-09-29 | Nokia Corporation | Method and apparatus for determining a user age range |
CA2795128A1 (en) | 2010-03-31 | 2011-10-06 | Mediamath, Inc. | Systems and methods for integration of a demand side platform |
US8626901B2 (en) | 2010-04-05 | 2014-01-07 | Comscore, Inc. | Measurements based on panel and census data |
US20110282730A1 (en) | 2010-05-13 | 2011-11-17 | AdChoice, Inc. | System and method for selecting and implementing an internet advertising campaign |
US8307006B2 (en) | 2010-06-30 | 2012-11-06 | The Nielsen Company (Us), Llc | Methods and apparatus to obtain anonymous audience measurement data from network server data for particular demographic and usage profiles |
US8484511B2 (en) | 2010-07-01 | 2013-07-09 | Time Warner Cable Enterprises Llc | Apparatus and methods for data collection, analysis and validation including error correction in a content delivery network |
US9747605B2 (en) | 2010-08-02 | 2017-08-29 | Facebook, Inc. | Measuring quality of user interaction with third party content |
US8886773B2 (en) * | 2010-08-14 | 2014-11-11 | The Nielsen Company (Us), Llc | Systems, methods, and apparatus to monitor mobile internet activity |
CA3027898C (en) * | 2010-09-22 | 2023-01-17 | The Nielsen Company (Us), Llc | Methods and apparatus to determine impressions using distributed demographic information |
US9092797B2 (en) | 2010-09-22 | 2015-07-28 | The Nielsen Company (Us), Llc | Methods and apparatus to analyze and adjust demographic information |
AU2013203898B2 (en) | 2010-09-22 | 2015-07-02 | The Nielsen Company (Us), Llc | Methods and apparatus to determine impressions using distributed demographic information |
JP5674414B2 (en) | 2010-10-27 | 2015-02-25 | 株式会社ビデオリサーチ | Access log matching system and access log matching method |
US8484241B2 (en) | 2010-10-29 | 2013-07-09 | Russell Kent Bouse | Systems and methods to consolidate and communicate user profiles and modality preferences information for content delivery or interaction experiences |
US20130014144A1 (en) | 2011-07-06 | 2013-01-10 | Manish Bhatia | User impression media analytics platform methods |
US8631122B2 (en) * | 2010-11-29 | 2014-01-14 | Viralheat, Inc. | Determining demographics based on user interaction |
US20120143713A1 (en) | 2010-12-06 | 2012-06-07 | Campaigngrid, Llc | Electronic and network-based franking |
US8453173B1 (en) | 2010-12-13 | 2013-05-28 | Google Inc. | Estimating demographic compositions of television audiences from audience similarities |
US20120151079A1 (en) | 2010-12-13 | 2012-06-14 | Jan Besehanic | Methods and apparatus to measure media exposure |
US9497154B2 (en) | 2010-12-13 | 2016-11-15 | Facebook, Inc. | Measuring social network-based interaction with web content external to a social networking system |
US20120158490A1 (en) | 2010-12-16 | 2012-06-21 | Yahoo! Inc. | Sponsored search auction mechanism for rich media advertising |
CA2977942C (en) * | 2010-12-20 | 2021-08-03 | The Nielsen Company (Us), Llc | Methods and apparatus to determine media impressions using distributed demographic information |
US8874639B2 (en) | 2010-12-22 | 2014-10-28 | Facebook, Inc. | Determining advertising effectiveness outside of a social networking system |
US20120185274A1 (en) | 2011-01-14 | 2012-07-19 | Guzihou Hu | System and Method for Predicting Inner Age |
US20120209920A1 (en) | 2011-02-10 | 2012-08-16 | Microsoft Corporation | Social influencers discovery |
US20120206331A1 (en) | 2011-02-14 | 2012-08-16 | Gandhi Sidhant D | Methods and Systems for Supporting Gesture Recognition Applications across Devices |
CA2810264C (en) * | 2011-03-18 | 2020-06-09 | The Nielsen Company (Us), Llc | Methods and apparatus to determine media impressions |
US8984547B2 (en) | 2011-04-11 | 2015-03-17 | Google Inc. | Estimating demographic compositions of television audiences |
US8315620B1 (en) | 2011-05-27 | 2012-11-20 | The Nielsen Company (Us), Llc | Methods and apparatus to associate a mobile device with a panelist profile |
US9282158B2 (en) | 2011-06-06 | 2016-03-08 | Google Inc. | Reducing redirects |
US8560683B2 (en) | 2011-06-10 | 2013-10-15 | Google Inc. | Video and site analytics |
US9210208B2 (en) | 2011-06-21 | 2015-12-08 | The Nielsen Company (Us), Llc | Monitoring streaming media content |
US8688524B1 (en) | 2011-06-28 | 2014-04-01 | Amazon Technologies, Inc. | Tracking online impressions to offline purchases |
US8498491B1 (en) | 2011-08-10 | 2013-07-30 | Google Inc. | Estimating age using multiple classifiers |
US10783547B2 (en) | 2011-08-17 | 2020-09-22 | Facebook, Inc. | Approximating unique advertisement impressions on a social networking system |
US20130060629A1 (en) | 2011-09-07 | 2013-03-07 | Joshua Rangsikitpho | Optimization of Content Placement |
JP2013057918A (en) | 2011-09-09 | 2013-03-28 | Shigeto Umeda | System for displaying and bidding for variable-length advertisement |
US8909771B2 (en) * | 2011-09-15 | 2014-12-09 | Stephan HEATH | System and method for using global location information, 2D and 3D mapping, social media, and user behavior and information for a consumer feedback social media analytics platform for providing analytic measurements data of online consumer feedback for global brand products or services of past, present or future customers, users, and/or target markets |
US20130080263A1 (en) | 2011-09-23 | 2013-03-28 | Jonathan Goldman | Per-view charging for video advertisements |
US20130117103A1 (en) | 2011-11-08 | 2013-05-09 | Insightexpress, Llc | Universal control |
WO2013078640A1 (en) | 2011-11-30 | 2013-06-06 | Google Inc. | Estimating user demographics |
US9331975B2 (en) * | 2011-12-16 | 2016-05-03 | The Nielsen Company (Us), Llc | Systems, methods, and apparatus to identify media presentation devices |
CA3013711C (en) | 2012-01-26 | 2022-08-09 | James R. Oliver | Systems, methods, and articles of manufacture to measure online audiences |
US8600796B1 (en) | 2012-01-30 | 2013-12-03 | Bazaarvoice, Inc. | System, method and computer program product for identifying products associated with polarized sentiments |
US20130204694A1 (en) | 2012-02-07 | 2013-08-08 | Sayso, Llc | Context-Based Study Generation and Administration |
US9015255B2 (en) | 2012-02-14 | 2015-04-21 | The Nielsen Company (Us), Llc | Methods and apparatus to identify session users with cookie information |
US8973023B1 (en) | 2012-02-29 | 2015-03-03 | The Nielsen Company (Us), Llc | Methods and apparatus to determine audience duplication in cross-media campaigns |
US9659105B2 (en) | 2012-03-15 | 2017-05-23 | The Nielsen Company (Us), Llc | Methods and apparatus to track web browsing sessions |
US20130262181A1 (en) | 2012-03-30 | 2013-10-03 | Alexander Topchy | Methods and apparatus to predict audience composition and/or solicit audience members |
US20130325588A1 (en) | 2012-06-04 | 2013-12-05 | The Board of Trustees for the Leland Stanford, Junior, University | Method and System for Measuring the Effectiveness of Search Advertising |
US20130331971A1 (en) | 2012-06-10 | 2013-12-12 | Eran Bida | Watermarking and using same for audience measurement |
AU2013204865B2 (en) | 2012-06-11 | 2015-07-09 | The Nielsen Company (Us), Llc | Methods and apparatus to share online media impressions data |
US9461876B2 (en) | 2012-08-29 | 2016-10-04 | Loci | System and method for fuzzy concept mapping, voting ontology crowd sourcing, and technology prediction |
AU2013204953B2 (en) | 2012-08-30 | 2016-09-08 | The Nielsen Company (Us), Llc | Methods and apparatus to collect distributed user information for media impressions |
US20140108130A1 (en) * | 2012-10-12 | 2014-04-17 | Google Inc. | Calculating audience metrics for online campaigns |
US9621446B2 (en) | 2012-10-26 | 2017-04-11 | Comscore, Inc. | Combining measurements based on beacon data |
US9055021B2 (en) | 2012-11-30 | 2015-06-09 | The Nielsen Company (Us), Llc | Methods and apparatus to monitor impressions of social media messages |
US20140279074A1 (en) | 2013-03-15 | 2014-09-18 | Turn Inc. | Data management platform for digital advertising |
US9635404B2 (en) * | 2013-04-24 | 2017-04-25 | The Nielsen Company (Us), Llc | Methods and apparatus to correlate census measurement data with panel data |
US20140324544A1 (en) | 2013-04-26 | 2014-10-30 | Paul Donato | Methods and apparatus to determine demographic distributions of online users |
US9519914B2 (en) | 2013-04-30 | 2016-12-13 | The Nielsen Company (Us), Llc | Methods and apparatus to determine ratings information for online media presentations |
US20140337104A1 (en) | 2013-05-09 | 2014-11-13 | Steven J. Splaine | Methods and apparatus to determine impressions using distributed demographic information |
US8775332B1 (en) | 2013-06-13 | 2014-07-08 | InsideSales.com, Inc. | Adaptive user interfaces |
US10068246B2 (en) | 2013-07-12 | 2018-09-04 | The Nielsen Company (Us), Llc | Methods and apparatus to collect distributed user information for media impressions |
US9313294B2 (en) | 2013-08-12 | 2016-04-12 | The Nielsen Company (Us), Llc | Methods and apparatus to de-duplicate impression information |
US20150193816A1 (en) | 2014-01-06 | 2015-07-09 | The Nielsen Company (Us), Llc | Methods and apparatus to correct misattributions of media impressions |
US8910195B1 (en) | 2014-02-20 | 2014-12-09 | Google Inc. | Systems and methods for enhancing audience measurement data |
CA3119830C (en) | 2014-03-13 | 2023-11-14 | The Nielsen Company (Us), Llc | Methods and apparatus to compensate impression data for misattribution and/or non-coverage by a database proprietor |
-
2012
- 2012-02-27 CA CA2810264A patent/CA2810264C/en active Active
- 2012-02-27 AU AU2012231667A patent/AU2012231667B9/en active Active
- 2012-02-27 EP EP12760524.4A patent/EP2686779A4/en not_active Ceased
- 2012-02-27 WO PCT/US2012/026760 patent/WO2012128895A2/en active Application Filing
- 2012-02-27 CN CN201610624244.6A patent/CN106156363B/en not_active Expired - Fee Related
- 2012-02-27 JP JP2013544887A patent/JP5769816B2/en active Active
- 2012-02-27 EP EP20166716.9A patent/EP3693914A1/en active Pending
- 2012-02-27 CN CN201280003504.8A patent/CN103189856B/en not_active Expired - Fee Related
-
2013
- 2013-01-31 US US13/756,493 patent/US9118542B2/en active Active
-
2014
- 2014-08-19 US US14/463,309 patent/US9497090B2/en active Active
-
2015
- 2015-06-23 JP JP2015125892A patent/JP6120909B2/en active Active
-
2017
- 2017-03-28 JP JP2017063529A patent/JP6436445B2/en active Active
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1997041673A2 (en) * | 1996-04-26 | 1997-11-06 | Freedom Of Information, Inc. | Computer network and method for determining user behaviour |
US6108637A (en) | 1996-09-03 | 2000-08-22 | Nielsen Media Research, Inc. | Content display monitor |
US5948061A (en) * | 1996-10-29 | 1999-09-07 | Double Click, Inc. | Method of delivery, targeting, and measuring advertising over networks |
WO2000041115A1 (en) * | 1998-12-30 | 2000-07-13 | Catalina Marketing International, Inc. | Communicating with a computer based on the offline purchase history of a particular consumer |
US20020099609A1 (en) * | 2000-12-01 | 2002-07-25 | Nascenzi Robert A. | Method and system for using customer preferences in real time to customize a commercial transaction |
US20030177488A1 (en) * | 2002-03-12 | 2003-09-18 | Smith Geoff S. | Systems and methods for media audience measurement |
US20040088212A1 (en) * | 2002-10-31 | 2004-05-06 | Hill Clarke R. | Dynamic audience analysis for computer content |
US20100153544A1 (en) * | 2008-12-16 | 2010-06-17 | Brad Krassner | Content rendering control system and method |
WO2010088372A1 (en) * | 2009-01-29 | 2010-08-05 | The Nielsen Company (Us), Llc | Methods and apparatus to measure market statistics |
Non-Patent Citations (1)
Title |
---|
STEVE COFFEY: "Internet Audience Measurement", JOURNAL OF INTERACTIVE ADVERTISING, vol. 1, no. 2, 1 March 2001 (2001-03-01), pages 10 - 17, XP055126434, DOI: 10.1080/15252019.2001.10722047 * |
Also Published As
Publication number | Publication date |
---|---|
CA2810264A1 (en) | 2012-09-27 |
AU2012231667A1 (en) | 2013-03-21 |
CA2810264C (en) | 2020-06-09 |
EP2686779A2 (en) | 2014-01-22 |
JP5769816B2 (en) | 2015-08-26 |
JP2017152006A (en) | 2017-08-31 |
EP2686779A4 (en) | 2014-09-17 |
CN103189856A (en) | 2013-07-03 |
AU2012231667B2 (en) | 2015-05-28 |
US20130145022A1 (en) | 2013-06-06 |
WO2012128895A9 (en) | 2013-09-19 |
WO2012128895A2 (en) | 2012-09-27 |
JP2014508336A (en) | 2014-04-03 |
CN106156363B (en) | 2019-08-09 |
US20140358676A1 (en) | 2014-12-04 |
JP6120909B2 (en) | 2017-04-26 |
US9497090B2 (en) | 2016-11-15 |
AU2012231667B9 (en) | 2015-09-24 |
CN103189856B (en) | 2016-09-07 |
JP6436445B2 (en) | 2018-12-12 |
WO2012128895A3 (en) | 2013-04-04 |
US9118542B2 (en) | 2015-08-25 |
JP2015212959A (en) | 2015-11-26 |
CN106156363A (en) | 2016-11-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US12015681B2 (en) | Methods and apparatus to determine media impressions using distributed demographic information | |
US9497090B2 (en) | Methods and apparatus to determine an adjustment factor for media impressions | |
AU2015200121A1 (en) | Methods and apparatus to determine media impressions |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED |
|
AC | Divisional application: reference to earlier application |
Ref document number: 2686779 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: GAUNT, JOSH Inventor name: PEREZ, ALBERT, R. Inventor name: DONATO, PAUL Inventor name: OLIVER, JAMES, R. Inventor name: SRIVASTAVA, SEEMA, V. Inventor name: MAZUMDAR, MAINAK Inventor name: RAO, KUMAR Inventor name: AURISSET, JULIETTE Inventor name: PENG, YUTAO |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: PENG, YUTAO Inventor name: MAZUMDAR, MAINAK Inventor name: RAO, KUMAR Inventor name: PEREZ, ALBERT, R. Inventor name: OLIVER, JAMES, R. Inventor name: AURISSET, JULIETTE Inventor name: GAUNT, JOSH Inventor name: DONATO, PAUL Inventor name: SRIVASTAVA, SEEMA, V. |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20210212 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
17Q | First examination report despatched |
Effective date: 20220324 |