methods and gadgets for sharing media impression data online

专利摘要:
methods and apparatus for sharing media print data online. methods and apparatus for sharing media online print data is disclosed. an example method includes sending a response to a request, the response including the identification of a first cookie used by an audience measurement entity and an indication of the holder of a database, and receiving the mapping of a first cookie with a second cookie used by the holder database and demographic information associated with the second cookie holder database.
公开号:BR112014030132A2
申请号:R112014030132-8
申请日:2013-06-11
公开日:2021-08-24
发明作者:Amit Seth；Brahmanand Reddy Shivampet
申请人:The Nielsen Company (Us), Llc；
IPC主号:

专利说明:

[001] [001] This patent claims priority from Provisional Patent Application Serial US 61/658,233, filed on June 11, 2012, from Provisional Patent Application Serial US 61/810,235, filed on April 9, 2013 and Patent Application Serial AU 2103204865, filed on April 12, 2013, the entirety of which is incorporated by reference. FIELD OF REVELATION
[002] [002] The present disclosure relates generally to monitoring media and, more particularly, to methods and apparatus for determining impressions using distributed demographic information. FUNDAMENTALS
[003] [003] Traditionally, audience measurement entities determine audience engagement levels for media programming based on registered panelists. That is, an audience measurement entity enrolls people who consent to be monitored on a dashboard. The audience measurement entity then monitors those panelists to determine media programs (eg, television or radio programs, films, DVDs, etc.) exposed to those panelists. In this way, the audience measurement entity can determine exposure measurements for different media content based on the collected media measurement data.
[004] [004] Techniques to monitor user access to Internet resources such as web pages, advertisements and/or other content have developed significantly over the years. Some well-known systems perform such monitoring primarily through server log inserts. In particular, entities serving content on the Internet may use known techniques to record the number of requests received for their content on their server. BRIEF DESCRIPTION OF THE DRAWINGS
[005] [005] Figure 1 shows an example system for generating an audience measurement entity (AME) to partner cookie mapping based on a redirect from the AME to a partner database owner (DP).
[006] [006] Figure 2 shows an example message flow diagram corresponding to the example system of Figure 1 for generating an AME to partner cookie mapping based on a redirect from the AME to a DP partner.
[007] [007] Figure 3 shows another example system for generating an AME cookie mapping for partner DP1 based on a redirect from the AME to a partner DP1, and to additionally send a request to a second partner DP (partner DP2) to identify a registered user of the partner DP2.
[008] [008] Figure 4 shows an example message flow diagram corresponding to the example system of Figure 3 to generate an AME cookie mapping to partner DP1 based on a redirect from the AME to a partner DP1, and to additionally send a request to a second partner DP (partner DP2) to identify a registered user of the partner DP2.
[009] [009] Figure 5A is a representative flow diagram of exemplary machine-readable instructions that can be executed to collect distributed demographic information from the first and second partner database owners in connection with collecting online campaign ratings data. (OCR) of the first partner DP.
[010] [010] Figure 5B illustrates an exemplary process of the system of Figure 1 that implements the instructions of Figure 5 A.
[011] [011] Figure 6A is a representative flow diagram of exemplary machine-readable instructions that can be executed to collect distributed demographic information from the first and second partner database owners without an OCR collection process to collect data from OCR of the first partner DP.
[012] [012] Figure 6B illustrates an exemplary process of the system of Figure 1 that implements the instructions of Figure 6A.
[013] [013] Figure 7A is a representative flow diagram of exemplary machine-readable instructions that can be executed to perform a user-level cookie synchronization process.
[014] [014] Figure 7B illustrates an exemplary process of the system of Figure 1 that implements the instructions of Figure 7A.
[015] [015] Figure 8A is a representative flow diagram of exemplary machine-readable instructions that can be executed to perform a print-level cookie synchronization process.
[016] [016] Figure 8B illustrates an exemplary process of the system of Figure 1 that implements the instructions of Figure 8A.
[017] [017] Figure 9 is a representative flowchart of example machine-readable instructions that can be executed to deploy the example browser of Figures 1 to 4, 5B, 6B, 7B and/or 8B to deploy the mapping of an AME cookie to DP partner cookies for the browser.
[018] [018] Figure 10 is a representative flowchart of example machine-readable instructions that can be executed to deploy the example AME server of Figures 1 to 4, 5B, 6B, 7B and/or 8B to start mapping a cookie from AME for DP partner cookies.
[019] [019] Figure 11 is a representative flowchart of example machine-readable instructions that can be executed to deploy the example AME server of Figures 1 to 4, 5B, 6B, 7B and/or 8B to associate demographic data obtained from a DP partner for online activity tracking information.
[020] [020] Figure 12 is a representative flowchart of example machine-readable instructions that can be executed to deploy the example partner DP servers of Figures 1 to 4, 5B, 6B, 7B and/or 8B to map an AME cookie to a partner DP cookie.
[021] [021] Figure 13 is a representative flowchart of exemplary machine-readable instructions that can be executed to deploy the exemplary flag instruction generator of Figure 1 to generate flag instructions (e.g., tags) to be served by a server of the web (for example, the web server in Figure 1).
[022] [022] Figure 14 is an exemplary processor system that can be used to execute the exemplary instructions of Figures 5A to 13 for implementing exemplary apparatus and systems disclosed herein.
[023] [023] Whenever possible, the same numerical reference will be used throughout the drawing(s) and attached written description to refer to equal or similar parts. DETAILED DESCRIPTION
[024] [024] Techniques for monitoring user access to Internet resources such as web pages, content, advertisements and/or other media have developed significantly over the years. At one point in the past, such monitoring was done primarily through server log inserts. In particular, entities serving media (eg content and/or advertisements) on the Internet would record the number of requests received for their media on their server. Basing the Internet usage survey on server log entries is problematic for several reasons. For example, server log inserts can be tampered with either directly or through zombie programs that repeatedly request media from the server to increase the server log insert count. Second, media is sometimes retrieved once, cached locally, and then repeatedly viewed from the local cache without involving the server in repeated views. Server log inserts cannot track these cached media views. As such, server log inserts are susceptible to both over and under count errors.
[025] [025] The inventions disclosed in Blumenau, U.S. Patent 6,108,637, fundamentally change the way Internet monitoring is performed and overcome the limitations of the server-side record insertion monitoring techniques described above. For example, Blumenau has disclosed a technique where Internet media (eg content and/or advertisements) to be crawled is marked with beacon instructions. In particular, tracking instructions are associated with the HTML of the media to be tracked. When a client requests the media, both the media and the flag instructions are downloaded to the client. The flag instructions are thus executed whenever the media is accessed, whether from a server or from a cache. The U.S. Patent
[026] [026] The beacon instructions cause monitoring data that reflects information regarding media access to be sent from the client that downloaded the media to a monitoring entity.
[027] [027] It is important, however, to link demographic data to monitoring information. To address this issue, the audience measurement company establishes a panel of users who have agreed to provide their demographic information and have their Internet browser activities monitored. When an individual joins the panel, they provide detailed information regarding their identity and demographics (eg, gender, race, income, place of residence, profession, etc.) to the audience measurement company. The audience measurement entity places a cookie on the panelist's computer that enables the audience measurement entity to identify the panelist whenever the panelist accesses tagged media and thereby sends monitoring information to the audience measurement entity.
[028] [028] Since most of the customers who provide monitoring information for bookmarked pages are not panelists and, therefore, are unknown to the audience measurement entity, it is necessary to use statistical methods to impute demographic information based on the data collected. for panelists to the larger population of users who provide data for branded media. However, the panel sizes of audience measurement entities remain small compared to the general user population. Thus, an issue is presented regarding how to increase the panel size while ensuring that the panel demographics are accurate.
[029] [029] There are many database owners operating on the Internet. These database owners provide services to a wide range of subscribers. In exchange for providing the service, subscribers register with the owner. As part of this registration, subscribers provide detailed demographic information. Examples of such database owners include social media providers such as Facebook, Myspace etc. These database owners place cookies on their subscribers' computers to enable the database owner to recognize the user when they visit their website.
[030] [030] Internet protocols make cookies inaccessible outside the domain (eg Internet domain, domain name, etc.) in which they were placed. Thus, a cookie placed in the amazon.com domain is accessible to servers in the amazon.com domain, but not to servers outside that domain. Therefore, while an audience measurement entity may find it advantageous to access cookies placed by database owners, they are unable to do so.
[031] [031] In view of the above, an audience measurement company would like to leverage existing databases of database owners to collect more extensive Internet usage and demographic data.
[032] [032] Exemplary methods, apparatus and/or articles of manufacture disclosed herein collect audience exposure data using cookie mapping techniques, wherein an audience measurement entity (AME) cookie for an private audience is mapped to a partnered database owner cookie (a partner cookie) once during the lifetime of the cookies (for example, while cookies are valid and/or not deleted or replaced on client machines). In this way, AME only needs to redirect a client browser once (during the lifetime of the cookies) to a particular database owner to determine which partner cookie to map to an AME cookie in the client browser. Once cookie mapping is complete, AME may monitor media exposures for one or more non-panelist(s) and/or panelist(s) audience member(s) using the client's browser based on a AME cookie, and receive demographic information for the partner's audience member(s) based on the AME-to-partner cookie mapping. This reduces the number of redirects to the database owner needed, for example, to just one during the lifetime or validity of AME and partner cookies. By reducing the number of redirects, there are fewer interruptions, less interference, and/or less background processing to negatively affect performance of client browsers, thereby improving an overall user experience for audience members. Network traffic is also reduced, thereby improving the overall effectiveness of the network environment by reducing network delay and congestion. Furthermore, the amount of processing required by the database owner is reduced. Also, the amount of data (for example, the number of impressions) shared with the database owner is reduced.
[033] [033] Using AME cookie mapping for partners, the audience measurement entity may request demographic information from partner database owners for partner cookies which are mapped to their AME cookies in the partner cookie mapping. LOVE for partners. In response, partnered database owners provide their record entries and demographic information to the audience measurement entity, which then compiles the collected data into statistical reports that precisely identify the demographics of people accessing tagged media. . Due to the fact that customer identification is done with reference to huge user databases far beyond the number of people present in a conventional audience measurement panel, the data developed from this process is extremely accurate, reliable and detailed. . In some instances, by agreeing to participate in combined audience measurement efforts, the partnered database owners are provided with exposure information and audience demographics collected by the other partnering database owners. In this way, partner database owners can supplement their own audience exposure metrics with information provided by other partner database owners.
[034] [034] Exemplary methods, apparatus, and articles of manufacture disclosed herein may be used to determine media impressions (e.g., content impressions and/or ad impressions), media exposure (e.g., content exposure and /or ad exposure) using demographic information, which is distributed across different databases (eg different website owners, service providers, streaming media providers, etc.) on the Internet. The methods, apparatus and articles of manufacture disclosed in this document not only enable more accurate correlation of Internet media exposure to demographics, but also effectively extend panel sizes and compositions beyond the people who sit on an entity's panel. audience measurement and/or a ratings entity for people registered in other Internet databases such as the databases of social media sites such as Facebook, Twitter, Google etc. and/or any other Internet sites such as Yahoo! , Amazon.com etc. This extension effectively leverages the ratings entity's media tagging capabilities and the use of databases from non-rating entities such as social media and/or other web sites to create a huge demographically accurate dashboard that results in reliable measurements. accurate exposures to Internet media such as content, advertising and/or programming.
[035] [035] Traditionally, audience measurement entities (also referred to herein as “rating entities”) determine demographic reach for media (eg, content and advertising programming) based on registered panelists. That is, an audience measurement entity enrolls people who consent to be monitored on a dashboard. During enrollment, the audience measurement entity receives demographic information from the persons enrolled so that subsequent correlations can be made between media exposure (e.g.,
[036] [036] Exemplary methods, apparatus, and/or articles of manufacture disclosed herein may be deployed by an audience measurement entity (e.g., any entity interested in measuring or tracking audience exposures to advertisements, content, and/or any other media) in cooperation with any number of database owners such as online web service providers to develop online media exposure metrics. Such database owners/online web service providers may be social networking sites (e.g. Facebook, Twitter, MySpace etc.), multi-service sites (e.g. Yahoo!, Google, Experian etc.), online retailers (eg Amazon.com, Buy.com etc.) and/or any other website(s) that maintain user log recordings.
[037] [037] To increase the likelihood that the measured media exposure is accurately attributed to the exemplary correct demographics, methods, apparatus and/or articles of manufacture disclosed herein use demographic information located in the audience measurement entity records and information demographics located in one or more database owners (eg, web service providers) that maintain records or profiles of users who have accounts with them. Accordingly, exemplary methods, apparatus, and/or articles of manufacture disclosed herein 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 measurements of media exposure and/or demographic data) with demographic information from one or more different database owners (eg, web service providers).
[038] [038] Use of demographic information from disparate data sources (e.g. high quality demographic information from the panel(s) of an audience measurement entity and/or registered user data from web service providers ) results in improved metric reporting effectiveness for both online and offline ad campaigns. Exemplary techniques disclosed herein use online log data to identify user demographics and use server print accounts, tagging (also called flagging) and/or other techniques to track attributable impression quantities to those users. Online web service providers such as social networking sites (e.g. Facebook) and multi-service providers (e.g. Yahoo!, Google, Experian etc.) (collectively and individually hereinafter referred to as database owners ) maintain detailed demographic information (eg age, gender, geographic location, race, income level, education level, religion, etc.) collected through user registration processes. An impression corresponds to a household or individual who was exposed to the corresponding media (eg, content and/or advertisement). Thus, an impression represents a household or an individual who has been exposed to an ad or content or ad group or content. In Internet advertising, impression count or impression count is the total number of times an ad or ad campaign was accessed by a web population (e.g. the number of access times can be decreased, e.g. pop-up blockers and/or increased, e.g. local cache memory retrieval).
[039] [039] Exemplary methods, apparatus and/or articles of manufacture disclosed herein also make it possible to report TV ratings online and (eg with the use of gross ratings points (GRPs)) in a side-by-side manner. For example, techniques disclosed in this document enable advertisers to report numbers of unique people or users that are reached individually and/or collectively by online and/or TV advertisements.
[040] [040] Exemplary methods, apparatus and/or articles of manufacture disclosed herein also collect impressions mapped to demographic data at various locations on the Internet. For example, an audience measurement entity collects such impression data for its dashboard and lists one or more online demographic data owners to collect impression data for its subscribers. Combining this collected impression data, the audience measurement entity can then generate GRP metrics for different ad campaigns. These GRP metrics may be correlated or otherwise associated with particular demographic segments and/or markets that were reached.
[041] [041] Exemplary methods disclosed herein include sending a first request to an audience measurement entity and sending a second request to have a database owner send the audience measurement entity a cookie mapping of a audience measurement entity cookie to a corresponding database owner cookie for a customer. Some exemplary methods additionally include storing the database owner cookie. In some examples, sending the first request to the audience measurement entity is, in response, executing flag instructions on a web page. In some examples, the second request must additionally cause the database owner to send the audience measurement entity a demographic characteristic associated with the customer.
[042] [042] Some exemplary methods additionally include sending a third request to the audience measurement entity and sending a fourth request to have a second database owner send the audience measurement entity a second cookie mapping of the entity from audience measurement cookie to a second database owner cookie. In some of these examples, the second request is to make the database owner send the cookie mapping to the audience measurement entity asynchronously. Some exemplary methods additionally include sending a third request to the audience measurement entity, with the third request including cookie mapping.
[043] [043] Exemplary apparatus disclosed herein include a communications interface and a web browser. The web browser must send a first request to an audience measurement entity through the communications interface and send a second request through the communications interface to make a database owner send to the audience measurement entity. audience A cookie mapping from an audience measurement entity cookie to a corresponding database owner cookie for a customer. In some examples, the web browser must send the audience measurement entity cookie on the first request. On some example devices, the web browser must send the first request to the audience measurement entity in response to executing flag instructions on a web page.
[044] [044] On some exemplary devices, the second request must additionally cause the database owner to send the audience measurement entity a demographic characteristic associated with the customer. In some examples, the web browser must send a third request to the audience measurement entity and send a fourth request to a second database owner to have the second database owner send to the measurement entity a second cookie mapping from the audience measurement cookie entity to a second database owner cookie. In some examples, the second request is to make the database owner send the cookie mapping to the audience measurement entity asynchronously. In some examples, the web browser must send a third request to the audience measurement entity, with the third request including cookie mapping.
[045] [045] Exemplary methods disclosed herein include sending a response to a request, the response including an identification of a first cookie used by an audience measurement entity and an indication of a partner database owner and receiving a mapping of the first cookie to a second cookie used by the partner database owner and demographic information associated with the second cookie by the partner database owner. In some example methods, mapping and demographic information is received in an asynchronous communication from the partner database owner. In some examples, the response comprises a redirect message, the redirect message to cause a device client to send a request to the partner database owner.
[046] [046] In some exemplary methods, the mapping is received at a first moment and the demographic information is received at a second moment after the first moment. Some example methods additionally include selecting the database owner from a list of database owners based on a website from which the flag request originated. In some examples, selecting the database owner includes determining a quality of demographic information provided by the database owner for an expected demographic group associated with the website. Some example methods additionally include determining whether the flag request includes the first cookie and, when the flag request does not include the first cookie, generating the first cookie.
[047] [047] The exemplary devices disclosed herein include a redirector for sending a response to a request, the response including an identification of a first cookie used by an audience measurement entity and an indication of a database owner. partner; and a communication interface for receiving a mapping of the first cookie to a second cookie used by the partner database owner and demographic information associated with the second cookie by the partner database owner. In some example devices, the communication interface must receive mapping and demographic information in an asynchronous communication from the partner database owner.
[048] [048] In some examples, the response includes a redirect message, the redirect message to cause a device client to send a request to the partner database owner. In some examples, the communication interface must receive the mapping at a first moment and receive the demographic information at a second moment after the first moment. Some exemplary devices additionally include a partner selector to select the database owner from a list of database owners based on a website from which the request originated. In some examples, the partner selector must select the database owner which comprises determining a quality of demographic information provided by the database owner for an expected demographic group associated with the website. Some exemplary devices additionally include a cookie generator, the redirector to determine if the request includes the first cookie and, when the request does not include the first cookie, the cookie generator must generate the first cookie.
[049] [049] Exemplary methods disclosed herein include receiving a first request from a client device, the first request comprising an audience measurement entity cookie identifier, and determining an audience measurement cookie entity cookie mapping. to a database owner cookie associated with the client. Some exemplary methods additionally include sending a redirect message to cause the client to send the cookie mapping to the audience measurement entity. In some of these examples, the redirect message includes a database owner cookie identifier, the audience measurement entity cookie identifier, and an indication of the association between the database owner cookie identifier and the identifier. measurement entity cookie icon.
[050] [050] Some exemplary methods additionally include sending a message to the audience measurement entity, the message comprising the cookie mapping. In some of these examples, the message additionally includes a second cookie mapping between a second audience measurement entity cookie identifier for a second client device and a second database owner cookie associated with the second client device.
[051] [051] Exemplary methods disclosed herein include receiving a first request from a client device, the first request comprising an audience measurement entity cookie identifier, and providing a cookie mapping to an associated audience measurement entity. to the cookie, where the cookie mapping comprises an association between a database owner cookie and the audience measurement cookie associated with the customer. In some examples, providing the cookie mapping includes sending a redirect message to have the client send the cookie mapping to the audience measurement entity. In some of these examples, the redirect message includes a database owner cookie identifier, the audience measurement entity cookie identifier, and an indication of the association between the database owner cookie identifier and the identifier. measurement entity cookie icon.
[052] [052] In some exemplary methods, providing the cookie mapping includes sending a message to the audience measurement entity, the message comprising the cookie mapping. In some of these examples, the message additionally includes a second cookie mapping between a second audience measurement entity cookie identifier for a second client device and a second database owner cookie associated with the second client device.
[053] [053] The exemplary apparatus disclosed herein includes a communications interface for receiving a first request from a client device, the first request comprising an audience measurement entity cookie identifier; and a cookie mapper to determine a cookie mapping from the audience measurement cookie entity to a database owner cookie associated with the customer. On some example devices, the communications interface must provide cookie mapping to an audience measurement entity associated with the cookie, with the cookie mapping comprising an association between a database owner cookie and the audience measurement cookie. audience associated with the customer.
[054] [054] In some examples, the communications interface must provide the cookie mapping by sending a redirect message to make the client send the cookie mapping to the audience measurement entity. In some of these examples, the redirect message includes a database owner cookie identifier, the audience measurement entity cookie identifier, and an indication of the association between the database owner cookie identifier and the identifier. measurement entity cookie icon. In some exemplary devices, the communications interface must provide cookie mapping by sending a message to the audience measurement entity, the message comprising cookie mapping. In some of these examples, the message additionally comprises a second cookie mapping between a second audience measurement entity cookie identifier for a second client device and a second database owner cookie associated with the second client device.
[055] [055] The exemplary devices disclosed herein include a communications interface for receiving a first request from a client device, the first request comprising an audience measurement entity cookie identifier and providing a message to an audience measurement entity. audience measurement associated with the cookie, the message including a cookie mapping wherein the cookie mapping comprises an association between a database owner cookie and the audience measurement cookie associated with the customer; and a processor to execute instructions, the instructions must cause the processor to generate the message.
[056] [056] Exemplary methods disclosed herein include providing instructions to be included on a website, the instructions shall cause a customer, upon execution of the instructions, to initiate a process including: submitting a first request to a measurement entity of audience; and sending a second request to cause a database owner to send the audience measurement entity a cookie mapping of an audience measurement entity cookie to a corresponding customer database owner cookie. Some exemplary methods additionally include receiving information associated with the website and generating instructions based on the information. In some examples, the process additionally includes receiving a redirect message from the audience measurement entity, the redirect message comprising an audience measurement cookie identifier.
[057] [057] The exemplary apparatus disclosed in this document includes a communications interface and a processor for generating instructions to be included in a website and for causing the communications interface to provide the instructions to a web server associated with the website. , instructions for causing a customer, upon execution of the instructions, to initiate a process comprising: submitting a first request to an audience measurement entity; and send a second request to cause a database owner to send, to the audience measurement entity, a cookie mapping of an audience measurement entity cookie to a cookie database owner that corresponds to the customer . In some examples, the communications interface must receive information associated with the website, the processor must generate instructions based on the information. In some exemplary devices, the method further comprises receiving a redirect message from the audience measurement entity, the redirection message comprising an identifier of the audience measurement cookie.
[058] [058] Figure 1 depicts an example system 100 for generating an audience measurement entity (AME) to partner cookie mapping based on a redirect from AME 102 to a partner database owner (DP) 104. A Figure 2 represents an example message flowchart 200 corresponding to the example system 100 of Figure 1 for generating an AME-to-partner cookie mapping based on redirection from the AME 102 to a partner DP 104.
[059] [059] In the example of Figure 1, a web server 106 provides access to one or more web sites. Exemplary system 100 determines an AME-to-partner cookie mapping for web browsers requesting access to websites served by web server 106 (e.g., an example web browser 110). While an exemplary web browser 110 is shown for the illustration, the exemplary system 100 of Figure 1 may duplicate and/or repeat the process illustrated of Figure 1 for the web browser 110 and/or other web browsers. The exemplary web browser 110 of Figure 1 is a specific instance of a web browser computer application that runs on a specific computer device (e.g., a personal computer, a mobile device, such as the processing platform 1400 of the Figure 14). However, an exemplary deployment of the exemplary system 100 of Figure 1 will typically involve multiple browsers.
[060] [060] An example web page available from the example web server 106 of Figure 1 is marked with flag instructions. In some instances, the AME 102 provides the markup or flag instructions to the web server 106 to be included in the websites or elements or websites (e.g. media, advertisements and/or other elements of the websites) served by the web server 106. The flag instructions provided may allow and/or request modifications by the web server based on the specific page being bookmarked and/or based on any arguments and/or other variables present on the web page.
[061] [061] When the example browser 110 requests the web page from the web server 106 (e.g. arrow (1) of Figure 1), the example web server 106 returns the page content with the flag instructions (e.g. , arrow (2) of Figure 1). The exemplary flag instructions of Figure 1 are provided by AME 102 and/or modified from instructions provided by AME 102 to web server 106 and include a URL 112 that points to an AME server 114 and specifies, among other things , a presentation and/or media display resulting from the provision of the requested page from the web server 106 and an indication (e.g. bold text in URL 112) from a web server or publisher (e.g. the web server web 106) that provided the flag instructions (eg arrow (3) in Figure 1). In some examples, the web server 106 is controlled by the partner DP 104 or another database owner. In some such examples, the web server 106 includes an identifier or other indication of the partner DP 104 in the URL 112. If the browser 110 has previously stored a cookie that corresponds to the AME 102 (for example, an AME cookie) ( and the cookie has not expired), the sample browser 110 provides a flag request to the AME cookie).
[062] [062] The exemplary AME server 114 includes a flag request redirector 120, a cookie generator 122, a partner picker 124, a flag instruction generator 126, and a communication interface 128. When the AME server 114 receives the flag request from browser 110, the sample flag request redirector 120 determines whether the flag request includes an AME cookie. If the flag request does not include an AME cookie, the sampler cookie generator 122 creates an AME cookie for the browser 110. If the flag request includes an AME cookie, the sampler request redirector 120 determines whether the flag request AME cookie is associated with (eg mapped to) a DP cookie value for a DP (eg partner DP 104). If there is a DP cookie, the exemplary AME server 114 stores the flag in association with the browser 110. The AME server 114 may or may not respond to the flag request. In the illustrated example, the AME server 114 responds to the flag request with something not intended to affect the display of the tagged web page or ad (for example, with a transparent 1x1 pixel image or other requested media such as a placeholder) . In some examples, the flag request does not get a response.
[063] [063] If the AME server 114 in the illustrated example has created an AME cookie for the browser 110 or if there is no DP cookie value for the browser 110 associated with (for example, mapped to) an existing AME =cookie (e.g. For example, the bookmarked web page or bookmarked ad is not from a DP server), the sample flag request redirect 120 adds an AME cookie to the URL parameter 116 of a response to the flag request. The sample flag request redirector 120 sends a redirect response (e.g., an HTTP “302 Found” redirect message) to browser 110 in response to the beacon request (e.g., arrow (4) in Figure 1) . The example URL parameter 116 of Figure 1 includes an address of a partner DP server 108 (e.g., the bold and underlined text in URL 116 of Figure 1) and an AME cookie identifier or value to be mapped to a DP partner cookie 104 (e.g. text in bold and not underlined). The example URL parameter 116 further includes an address of the partner DP server 108. The example partner selector 124 selects the partner DP server to which the redirect message is to be directed. For example, the partner selector 124 may select one or more of multiple partner DPs (e.g. from a list of cooperating partner DPs) based, for example, on the expected demographics of the media served by the web server 106 (e.g. , the marked media). In some other examples, the partner selector 124 selects a default partner DP and one or more supporting partner DPs.
[064] [064] The exemplary beacon instruction generator 126 of Figure 1 receives the information associated with the exemplary web server 106 and/or websites to be served by the web server 106. The information may include an address range and/or Web server URL 106 and/or media. Based on the information, the exemplary flag instruction generator 126 generates the flag instructions to be used by the exemplary web server 106 to tag the media served by the web server 106. In some other examples, the flag instruction generator 126 provides generic instructions to the web server 106 that can be modified by the web server 106 based on the media being served.
[065] [065] The sample communication interface 128 communicatively couples the sample AME server 114 to the sample browser 110 (e.g., over a network such as the Internet). Exemplary communication interface 128 includes a combination of hardware and software and/or firmware for transmitting and receiving communications, such as beacon requests and redirect responses. In some examples, the communication interface 128 includes load balancing capabilities to split large amounts of communications between multiple AME servers 114.
[066] [066] The sample browser 110 receives the redirection response to the flag request and makes a request to the partner DP server 108 based on (e.g. using) URL 116 (e.g. arrow (5) in Figure 1 ). If the browser 110 has a cookie for the domain of the partner DP 104, the sample browser 110 provides the request for the cookie. The exemplary partner DP server 108 of Figure 1 includes a cookie mapper 130 and a communications interface 132. The partner DP server 108 determines whether a cookie is provided by the browser 110. If the browser 110 provides a request for the cookie, the example partner DP server 108 (e.g. via cookie mapper 130) recognizes the cookie and maps the partner DP cookie to the AME cookie identified in URL 116 (e.g. stores an association between partner DP cookie and the AME cookie). The exemplary partner DP server 108 sends a message to the exemplary AME server 114 that indicates a mapping between the AME cookie and the partner DP cookie to the browser 110 (e.g., arrow (6) of Figure 1). The example message includes a URL 118 that provides the mapping
[067] [067] The example cookie mapper 130 may additionally or alternatively be deployed on the AME servers 114. As described below, in some examples the AME server performs the mapping between AME cookies and partner DP cookies based on the AME cookies, DP partner user identifiers and/or DP partner cookies associated with the browser 110.
[068] [068] Example communication interface 312 communicatively couples example partner DP server 108 to example browser 110 (e.g., over a network such as the Internet). Exemplary communication interface 132 includes a combination of hardware and software and/or firmware for transmitting and receiving communications, such as beacon redirects, cookie mapping, and demographic information. In some examples, the communication interface 132 includes load balancing capabilities to split large amounts of communications between multiple partner DP servers 108.
[069] [069] In the example of Figure 1, the mapping URL 118 additionally includes the browser-associated demographic information (eg, demographic information for a browser user) that is known to the partner DP 104. For example, a browser user 110 may have provided the demographic information to the partner DP 104 in exchange for using a service provided by the partner DP 104. In some examples, the mapping URL 118 additionally includes a mapping timestamp and/or a timestamp of another event leading to mapping to facilitate mapping of the AME cookie and/or partner DP cookie to the impression data. In some other examples, the AME server 114 stores the timestamps derived from HTTP messages transmitted and received during the mapping process. In some examples, the AME cookie is unique, so timestamps are not required to match the AME cookie and/or partner DP cookie with impression data.
[070] [070] The example AME server 114 of Figure 1 stores the mapping between the AME cookie and the partner DP cookie. The exemplary AME server 114 of Figure 1 additionally stores the demographic information for the browser 110 received from the partner DP (if any). For subsequent beacon requests received from the browser 110 for the same AME cookie, the example AME server 114 stores the beacon request (and associated page view/exposure information) and does not redirect the browser 110, thereby reducing , traffic to the DP and also reducing the data (e.g. impression counts) provided to the DP).
[071] [071] Figure 3 represents another exemplary system 300 for generating an AME cookie mapping to first partner DP based on a redirect from the AME to a partner DP1 and to additionally send a request to a second partner DP (partner DP2) to identify a registered user of the partner DP2. Figure 4 represents an example message flowchart corresponding to the example system of Figure 3 for generating a cookie mapping from AME to partner DP1 based on a redirect from the AME to a partner DP1 and to additionally send a request to a second partner DP (DP2 partner) to identify a registered user of the DP2 partner. The example system 300 of Figure 3 includes the AME 102, the first partner DP 104, the web server 106, the first partner DP server(s) 108, the example browser 110 and the AME server. (s) 114 of Figure 1 . The exemplary system 300 of Figure 3 additionally includes a second partner DP 302 that includes one or more second partner DP servers 304.
[072] [072] In a manner similar to arrows (1) and (2) of Figure 1, the example browser 110 requests a web page from the first web server 106 and receives the media (e.g. a web page, an advertisement ) with flag instructions. The request to the web server 106 may be for any media (eg, a web page, a part of a web page such as an advertisement) that is bookmarked. The web page itself may be bookmarked and/or an advertisement or other portion within the page may be bookmarked. Exemplary beacon instructions include a 306 URL that specifies the web server, publisher, and/or website owner from which the beacon instructions come (e.g., the font in bold). Similar to the arrow (3) of Figure 1, the sampler browser 110, upon receipt of the beacon instructions, makes a beacon request to the sampler AME server 114. If the browser 110 has previously stored a cookie that matches the AME 102 (and the cookie has not expired), the sample browser 110 provides the flag request to the AME cookie). In the examples in Figures 1 and 3, the AME server 114 does not need to determine whether the AME cookie is expired due to the fact that the browser 110 does not send (for example, delete) an expired AME cookie (or any expired cookies) .
[073] [073] When the AME server 114 receives the flag request from the browser 110, the exemplary AME server 114 determines whether the flag request includes an AME cookie. If the flag request does not include an AME cookie, the AME server sampler 114 creates an AME cookie for the browser
[074] [074] If the AME server 114 has created an AME cookie for the browser 110 or if there is no DP cookie value for the browser 110 associated (e.g. mapped to) an existing AME cookie, the AME server sampler 114 adds an AME cookie to a URL parameter 308 of a redirect response to the flag request. The exemplifying AME server 114 then sends a redirect response (e.g., an HTTP “302 Found” redirect message) to browser 110 in response to the flag request (e.g., in a manner similar to the arrow ( 4) of Figure 1). The example URL parameter 308 of Figure 3 includes an address of the first partner DP server 108 (e.g., the text in bold, non-underlined) and an AME cookie identifier or value to be mapped to a first partner DP cookie 104 (e.g. bold underlined text). If the browser 110 has previously stored a cookie that corresponds to the domain of the first DP partner 104, the browser sampler 110 includes the first DP partner cookie with the request to the first DP partner server 108.
[075] [075] The first sampler partner DP server 108 determines whether the request includes a first DP cookie. If the request includes a first partner DP cookie, the sampler first DP partner server 108 sends a message to the AME server 114 that includes a URL 310. The URL 310 includes a mapping of the first partner DP cookie to the partner cookie. AME (for example, the text in bold). In some examples, the first DP partner server 108 stores the first DP partner cookie for later mapping and transmission to the AME server 114 (eg, as a batch). At periodic or aperiodic intervals, the first partner DP server 108 sends multiple messages that include the URLs (e.g. the URL 310) that indicate the respective mappings of the first partner DP cookies to the AME cookies.
[076] [076] In addition to or as an alternative to mapping, the AME cookie to a partner DP cookie for the first partner DP 104 (e.g. a partner DP from which the browser requested the web page), the example system 300 maps the AME cookie to the browser 110 to a partner DP cookie to the second partner DP 302. The exemplary second partner DP 302 may have additional or alternative information about the browser user 110 in relation to the first partner DP
[077] [077] In some instances, the system 300 maps the AME cookie to the second partner DP cookie to enable the second partner DP 302 to enter impression records for a media campaign (eg, ad). The example second DP partner 302 provides impression information that is tracked through the second partner DP cookie to the example AME 102, along with a mapping of the second partner DP cookie to the example AME cookie to the browser 110. In some examples , the second partner DP 302 additionally provides demographic information associated with impressions.
[078] [078] To map the AME cookie for browser 110 to the second partner DP cookie 114, the example AME server 114 sends a redirect response to the flag request that includes a URL 312 to the second partner DP 302 (e.g. , to the second partner DP server 304). For example, tagged media may include multiple flags to enable the AME 102 to redirect the browser 110 to multiple DP partners. Additionally or alternatively, tagged media issues only one flag request and the AME server 114 may respond with multiple redirect messages. Additionally or alternatively, each DP (eg first partner DP 104, second partner DP 304, etc.) can respond to a request generated by a redirect by returning a redirect to another DP. In examples where AME server 114 sends multiple redirects, example URL 312 of Figure 3 is similar to URL 308, with the exception that URL 310 specifies the address of the second email server(s). DP partner 304 instead of the address of the first DP partner server(s) 108.
[079] [079] Example URL 310 of the illustrated example includes the AME cookie value. Sample browser 110 receives the redirect response and sends a request to second sample partner DP server 304. If browser 110 has a cookie for second partner DP server 304, browser 110 includes the cookie in the request. The second exemplary partner DP server 304 determines whether the browser request 110 includes a cookie. If the request includes a cookie, the second exemplary partner DP server 304 reads a cookie value that identifies the browser 110 or a user associated with the browser (eg, uniquely identifies the user).
[080] [080] Unlike the first example partner DP 104, the second example partner DP 302 of the example illustrated in Figure 3 provides the AME cookie to the second partner DP cookie mapping at intervals rather than immediately upon generation of the mapping . For example, Second partner DP 302 stores the mapping between second partner DP cookies and mapped AME cookies for later transmission to AME server 1 14 (eg as a batch). At periodic or aperiodic intervals, the second partner DP server 304 sends one or more multiple messages that include the respective mappings of the second partner DP cookies to the AME cookies. Exemplary second partner DP servers 304 may send a set of multiple mappings via a message in one or more data files (e.g., an array or other data structure). Additionally or alternatively, second partner DP servers 304 may send multiple messages (e.g. spoofed HTTP requests) where each message includes a mapping (e.g. a URL containing the mapping information). If the second exemplary partner DP server 304 recognizes the user (e.g., through the user identifier in the cookie), the second exemplary partner DP server 304 sends a mapping message or other acknowledgment message to the exemplary AME server 114 (for example, an HTTP 200 OK response message).
[081] [081] The examples in Figures 1 to 4, 5B, 6B, 7B, and/or 8B are shown in connection with operations that can be performed using machine-readable instructions executed by one or more servers or computers on the systems exemplary 100, 300 of Figures 1 and 3.
[082] [082] In the examples of Figures 5A, 6A, 7A and 8A, the operations described as being performed by AME can be implemented, for example, by the AME servers 114 of Figures 1 to 4, 5B, 6B, 7B and/or 8B and the operations described as being performed by a partner DP may be performed, for example, by the partner DP server 108, 304 of Figures 1 to 4, 5B, 6B, 7B and/or 8B. In the example in Figure 5A, a first database owner (DP1) agreed to provide cookie-level data and a second database owner (DP2) refused to provide cookie-level data but agreed to provide summary data representing the aggregations of your cookie-level data across partitions or categories (e.g. men, ages 30 to 40).
[083] [083] Figure 5A is a representative flowchart of exemplary machine-readable instructions 500 that can be executed to collect the distributed demographic information from the first and second partner database owners. Figure 5B illustrates an exemplary process of the system 100 of Figure
[084] [084] At block 510, when a browser accesses the media (eg arrow (1) of Figure 5B), the flag instructions included and/or associated with the media (eg arrow (2) of Figure 5B) do cause the browser to record an impression by sending a flag request to the AME (eg arrow (3) in Figure 5B). In operations at process block 512, AME collects online activity data for the browser. For example, AME receives a beacon request from a browser (block 512a) and collects and/or stores print data contained in, or otherwise associated with, the beacon request (block 512b). Data associated with the beacon request may include an AME cookie associated with the browser and/or may identify the media that triggered the beacon request. AME processes the collected impression data based on the corresponding AME cookie received from the browser to, for example, correlate web page views and media exposures (block 512c).
[085] [085] In block 514, the AME determines to which DP partner(s) the browser should be redirected. The exemplary AME may select partner DP1, partner DP2 and/or one or more additional partner DPs. For example, the AME may select the partner DP1 based on an expected or estimated demographic composition of a bookmarked website when a quality of demographic information for the expected or estimated demographic composition is higher for the partner DP1 than for other partner DPs . In some other examples, the AME may select multiple (eg all available) DP partners (eg DP1 and DP2). Based on the result of block 514, the example AME sends a redirect response to the client browser (e.g. arrow (4) of Figure 5B) to cause the client browser to send a redirect request to the partner DP1 (e.g. arrow (5) of Figure 5B, starting blocks 502a to 502c) and/or to the partner DP2 (e.g. starting blocks 516a to 516d).
[086] [086] In the illustrated example, operations in process block 502 are performed by the partner DP1, rather than the AME, to collect print data based on flag requests received from a web browser on a client computer. For example, after accessing tagged media, the client browser sends a flag request to the AME and is redirected by the AME to one or both of the partner DP1 and/or partner DP2 (block 514). Assuming, for discussion purposes, that the partner DP1 receives a message from a client browser based on the redirect (e.g. block 502a), the partner DP1 accesses the tag information (e.g. media information, publisher information , a timestamp, etc.) of the message received from the client to thereby collect and/or store print data from the browser (eg block 502b). The partner DP1 processes the tagging information to associate the tagging information with DP1 partner cookie identifiers and/or AME cookie identifiers for the user exposed to the tagged media (block 502c). Therefore, the example operations of block 502 enable the partner DP1 to collect impression information from panelist and/or non-paneler users accessing marked media. The collection of impression information by the partner DP1 can be done in addition to the collection of impression information by the AME or as an alternative to it.
[087] [087] At block 504, partner DP1 compresses raw print data (e.g. media information, cookie identifiers, timestamp, etc.) collected by partner DP1 to send to AME (e.g. arrow (6) of Figure 5B). The impression data provided by DP1 partner to AME includes mappings between AME cookie identifiers (e.g. identifiers received through tagging information) and DP1 partner cookie identifiers (e.g. identifiers of users that are known to by the partner DP1 and, for example, stored by the client device). Figure 5B illustrates an example table 524 that includes a timestamp, printing information (e.g., a media identifier), and an association between a partner DP1 user identifier and an AME cookie identifier. The exemplary partner DP1 sends table 524 to the exemplary AME server in a message corresponding to arrow (6) of Figure 5B. The partner DP1 cookie identifier may be anonymized in the print data provided to AME for privacy. Exemplary mapping information enables AME to correlate print data across multiple partner DPs (eg DP1, DP2, etc.). Exemplary blocks 502 and/or 504 of the
[088] [088] In operations in process block 506, partner DP1 generates user demographic files at cookie level (block 506a). For example, DP1 partner may generate a file that includes DP partner cookie identifiers to be mapped to AME cookies, and which additionally includes demographic information for the users identified respectively by DP partner cookies. For example, DP1 partner includes DP cookie identifiers of users, and the demographic information associated with users, from which DP cookies were received in association with a tag redirect message (e.g., during the period of previous report). The cookie-level demographic files are compressed and transferred to the AME (e.g. periodically, aperiodically, in response to a request, at designated times, etc.) (e.g. block 506b, arrow (7) of Figure 5B) . An exemplary table 526 is illustrated in Figure 5B and includes demographic information associated with partner DP1 cookie identifiers. Demographics may be limited to users for whom cookie mapping has taken place, or may cover a larger set of the database owner's cookies.
[089] [089] In operations referenced by reference numeral 508, the AME merges and/or aggregates the impression data and demographic data of the partner DP1 (block 508a). For example, AME may associate the demographic information that corresponds to individual DP partner cookies with impression data (e.g. impression data received in block 504 from partner DP1, impression data received from other DP partners, and/or other impression collection data by AME) that correspond to individual DP partner cookies. The exemplary AME summarizes the partner DP1's findings (eg, grouping data into partitions and/or demographic groups) (block 508b). The DP partner demographic and impression information, and/or a summary thereof can then be fed to a calibration engine for adjustment (e.g. calibration) based on known data (e.g. AME 520 panelist data) and/or media impression reporting (eg online campaign ratings).
[090] [090] In operations in process block 516, upon receipt of a request that results from a redirect response by AME (block 516a), a second partner DP2 (e.g., server 304 in Figure 3) collects and/or stores activity information that corresponds to a cookie known by the second partner DP2 (for example, the second partner DP 302) to the browser (block 516b). The example partner DP2 collects marking information (e.g. print data) in a similar manner to the partner DP1 as described above with reference to block 502 operations. The example partner DP2 processes the print data based on the DP2 partner cookies (block 516c). The partner DP2 may perform processing at block 516c in a similar manner to processing performed by AME at block 512c. However, instead of compressing the data, the second exemplary partner DP Server 304 periodically summarizes the tag information and sends the tag information to the OCR calibration engine 518 (block 516d). For example, data summarization may include grouping impression and/or demographic information into larger demographic groups rather than providing impression and/or demographic information for individual users and/or individual cookies. The exemplary OCR calibration engine 518 additionally receives AME panel factors 520 (e.g., weights to be applied to print information based on characteristics of a representative AME panel). The exemplary 518 OCR calibration engine generates 522 OCR reports based on the AME cookie for partner DP cookie mapping, partner DP demographics, partner DP activity measurements (e.g., impression data collection), and /or AME activity measurements (eg, panelist and/or non-AME panelist impression collection). Exemplary instructions 500 may include any number of partner DPs that perform blocks 502 and/or 504 and/or may include any number of partner DPs that perform block 516.
[091] [091] Figure 6A is a representative flowchart of example machine-readable instructions 600 that can be executed to collect distributed demographic information from the first and second partner database owners without collecting print data on the first partner DP. Figure 6B illustrates an exemplary process of the system 100 of Figure 1 that implements the instructions 600 of Figure 6A. Exemplary instructions 600 include blocks 506 to 522 of Figure 5A (e.g. arrows (1) to (4) of Figure 6B). Unlike the instructions 500 of Figure 5A, the example instructions 600 cause the AME to collect print information and release the partner DP1 from the task of collecting print information.
[092] [092] The example instructions 600 of Figure 6A include instructions referenced by the reference numeral 602, which causes the AME to redirect the browser to a subdomain of the partner DP1 domain (e.g., an AME server of Figure 1 that operates under a subdomain of the partner DP1's domain such as an AME server 604, rather than to a server operated by DP1). An exemplary way to use a subdomain of the partner DP1 domain is described in Patent Application Serial US 13/239,005, filed September 21, 2011, which is incorporated by reference in its entirety. The exemplary AME server 604 receives the bookmark redirection from the browser at the partner DP1 subdomain address (block 602a) (arrow (5) of Figure 6B). Since it operates under the partner DP1 subdomain, the example AME can receive the partner DP1 cookie for the AME cookie directly by the AME (e.g. by retrieving the AME cookie from the payload in the redirect request) ( block 602b). Therefore, in Figure 6A, the partner DP1 is released from the responsibility of collecting and reporting exposure or impression data. The data collected by the AME through the AME server in the subdomain of DP1 can be used by the same or different AME server in block 508 to merge the print data with transmitted demographic data in block 506. The example AME server 604 stores and/or sends the mapping information to another AME server 114 (eg arrow (6) in Figure 6B).
[093] [093] Figure 7A is a representative flowchart of exemplary machine-readable instructions 700 that can be executed to perform a user-level cookie synchronization process. Figure 7B illustrates an exemplary process of the system 100 of Figure 1 that implements the instructions 700 of Figure 7A. A user-level cookie sync refers to synchronizing an AME cookie associated with a user/device with a partner DP cookie associated with the same user/device. Exemplary instructions 700 include blocks 510, 512, and 516 through 522 of Figure 5A.
[094] [094] During a 702 collection process, DP1 partner site media is marked to allow user cookie IDs to be mapped to AME cookies (block 702a). For example, when a registered user of the partner DP1 site accesses the partner DP1 site (e.g., when accessing a marked system entry (login) page) (arrow (1) in Figure 7B), the marking associated with the DP1 partner website (arrow (2) in Figure 7B) causes the browser to send a beacon request to the AME that includes an AME cookie (if available) and a user identifier (e.g. an alphanumeric code or value ) of the user that is also known by the partner DP1 (block 702b). For example, the user identifier can be carried in the flag request payload. To maintain user privacy, the example user identifier may be set arbitrarily by the example partner DP1 and/or may be changed to the same user with each mapping from an AME cookie to a partner DP1 cookie. Also, the user identifier is mapped to the DP1 cookie, but is not itself the DP1 cookie. The example AME stores an association between the user identifier and the received AME cookie. If there is no AME cookie received, the sample AME stores a new AME cookie in the browser and writes an association between the new AME cookie and the user identifier. In some instances where the DP1 partner provides a consistent user identifier for a user, AME associates multiple AME cookies and the impression data that corresponds to multiple AME cookies based on AME cookies that are mapped to the same cookie of partner DP1.
[095] [095] Separately from the mapping process 702, the example browser 110 accesses the media (e.g. from the media server) at block 510 (arrow (4) of Figure 7B). As described above, the exemplary AME collects and stores impression information received from the browser via the flag request (eg, block 512, arrows (5) and (6) of Figure 7B).
[096] [096] During a 704 demographics process, the partner DP1 generates a partner DP1 daily/weekly demographic table (e.g. table 708 in Figure 7B) that contains user IDs (e.g. user IDs sent via flag requests for AME) and key demographic segments (block 704a). The exemplary partner DP1 compresses and/or transfers the demographic file to the AME (e.g., block 704b, arrow (7) of Figure 7B). Because the partner DP1 is aware of the association between its users and the user IDs provided to the AME, the example partner DP1 may match the user IDs to the demographic information of the corresponding users. In the illustrated example, the partner DP1 anonymizes the data to meet privacy requirements. The mappings between user IDs (e.g. DP1 partner) and AME cookies (e.g. as determined by AME from data provided by block 702) and partner DP1 demographic tables (e.g. the demographic file provided by DP1 partner) can be used to create a mapping file between AME cookies and partner DP1 cookies. Cookie mapping and/or the mapping between user IDs and AME cookies are subsequently used to associate audience demographics that correspond to online media impressions and/or to perform, for example, online campaigning and/or calculations exposure and reporting. In the illustrated example, AME applies profile corrections to correct or adjust any demographics that are found to be inaccurate.
[097] [097] During a 706 reporting process, partner DP1 demographic tables (i.e., received from 704 process block) are compatible with AME collection tables (i.e., printing information tables collected by the AME in the AME block of process 512) (block 706a) for summarizing and reporting (block 706b). For example, AME supports demographic data that matches DP1 partner cookies (i.e., received from process block 704 of Figure 7A and/or arrow (7) of Figure 7B) for data activity monitoring that uses the partner DP1 cookie to AME cookie mappings (i.e. received and/or determined from process block 702 of Figure 7A and/or arrow (3) of Figure 7B). In this way, demographic data is joined with impression data based on AME cookie IDs and/or user identifiers provided by DP1 to associate demographic data with activity data. Demographic and activity data can then be fed into a calibration engine to generate reports that reflect exposure to various demographic groups.
[098] [098] The example instructions 700 of Figure 7A do not cause the navigation to redirect to the DP1 servers. Instead, the cookie mapping between the DP1 partner cookie (and/or the DP1 partner user identifier) and the AME cookie allows impression data collected by AME to be mapped to the demographic information provided by the DP1 partner. As a result, the number of redirects is reduced relative to the systems of Figures 5A to 5B, 6A to 6B, and 8A to 8B, and thus network traffic is reduced. Additionally, reduced browsing redirection results in an improved user experience due to the fact that the user experiences fewer delays associated with redirected messages.
[099] [099] Figure 8A is a representative flowchart of exemplary computer-readable instructions 800 that can be executed to perform a print-level cookie synchronization process. Figure 8B illustrates an exemplary process of the system 100 of Figure 1 that implements the instructions 800 of Figure 8A. An impression-level cookie synchronization refers to the synchronization of an AME cookie associated with an impression with a partner DP cookie also associated with that same impression. Exemplary instructions 600 include blocks 510-522 of Figure 5A, which deploy at least arrows (1) through (4) of Figure 8B.
[100] [100] During an 802 collection process, the partner DP1 receives a redirect from a client navigation (i.e., block 802a of Figure 8A, arrow (5) of Figure 8B). The redirect includes an AME cookie as a parameter (ie in the request payload) to be passed to the partner DP1. The partner DP1 receives the redirected request from the client navigation and automatically returns a response that contains a mapping between the AME cookie ID (provided by the AME via the redirect) and the partner DP1 cookie ID (received from the client navigation when present) (block 802b, arrow (6) of Figure 8B). In some examples, the response is sent to the client navigation, which forwards the data to the AME. In other examples, a response is sent directly (i.e., omitting navigation) to the AME (i.e., via asynchronous communication) of the partner DP1 to avoid additional messages involving client navigation that can reduce the customer experience. user. Exemplary cookie mapping during the 802 collection process results in rapid collection of demographic information (i.e., collection that approximates real-time), allowing advertisers to more quickly identify discrepancies between ad goals and advertise results and/or to adjust faster insertion and/or service of advertisements in order to reach the desired demographic composition.
[101] [101] For example, if an ad publisher intends to place ads on websites A and B to achieve 10,000 impressions per day with men, ages 30 to 40, but instead collects data by the process in Figure 8A shows that website A produces 6000 impressions for men, ages 30 to 40, and website A produces mostly female impressions, the ad publisher can increase ad insertion on website B and decrease the ad placement on website A within the time period associated with the target demographic (i.e., a seven-day period to meet a daily target, a one-hour period to meet an hourly target, etc.) to achieve your demographic printing targets. This switch on ad insertion can potentially be done in real time to achieve desired ad goals in an actual ad campaign. In the past, demographic results were not available until after the ad campaign was completed, thus resulting in missed goals.
[102] [102] The partner DP1 periodically (i.e. hourly, daily, weekly, biweekly, monthly, etc.) or aperiodically (i.e. with the mapping information) provides a user table
[103] [103] During an 806 reporting process, the exemplary AME uses the mapping received from block 802 to match partner DP1's demographic tables (i.e., demographics from block 804) to AME collection tables (i.e., data from block 512) online activity (block 806a) for summarizing and reporting (block 806b). For example, data summarization may include grouping impression information and/or demographic information into larger demographic groups rather than providing impression and/or demographic information to individual users and/or individual individual cookies. In this way, demographic data is joined with impression data based on DP1 partner cookie IDs.
[104] [104] In operations within the process block 808, the example AME provides the OCR reports 522 of Figure 8A to the media publisher and/or web server (i.e. arrow (8) to the web server 106 of Figure 8B ). In the example in Figure 8A, the publisher compares the
[105] [105] While exemplary instructions 500-800 are disclosed above with reference to Figures 5A to 8B, any of the 500-800 instructions and/or blocks of Figures 5A-8B may be combined, split, rearranged, omitted, eliminated, and/or or implanted in any other form to achieve various advantages such as those described in relation to Figures 5A to 8B.
[106] [106] While an exemplary way of deploying systems 100, 300 is illustrated in Figures 1 through 4, 5B, 6B, 7B, and/or 8B, one or more of the elements, processes, and/or devices illustrated in Figures 1 through 4 , 5B, 6B, 7B, and/or 8B may be combined, divided, rearranged, omitted, deleted and/or implanted in any other way. In addition, the example web server 106, the example AME server(s) 114, 604 the example partner DP servers 108, 304, the example navigation 110, the example beacon request redirector 120, the exemplary cookie 122, exemplary partner selector 124, exemplary beacon instruction generator 126, exemplary communications interfaces 128, 132, exemplary cookie mapper 130, and/or, more generally, exemplary systems 100, 300 of the Figures 1 through 4, 5B, 6B, 7B, and/or 8B may be deployed by hardware, software, firmware, and/or any combination of hardware, software, and/or firmware.
[107] [107] Representative flowcharts of exemplary computer-readable instructions for deploying systems 100, 300 of Figures 1 through 4, 5B, 6B, 7B, and/or 8B are shown in Figures 9 through 13. In this example, the machine-readable instructions comprise programs for execution by a processor such as the processor 1412 shown in the exemplary processor platform 1400 discussed below in connection with Figure 14. The programs may be embedded in software stored on a tangible computer-readable storage medium such as a CD-ROM , a floppy disk, a hard disk, a digital versatile disk (DVD), a Blu-ray disc, or memory associated with the processor 1412, but the entire programs and/or parts thereof could alternatively be executed by a device other than the processor 1412 and/or embedded in firmware or dedicated hardware. Furthermore, while the example programs are described with reference to the flow charts illustrated in Figures 9 to 13, many other methods of deploying the example systems 100, 300 may alternatively be used. For example, the execution order of the blocks can be changed, and/or some of the described blocks can be changed, deleted, or combined.
[108] [108] As mentioned above, the exemplary processes of Figures 9 to 13 can be implemented using coded instructions (i.e., computer and/or machine readable instructions) stored on a tangible computer readable storage medium such as a hard disk drive, flash memory, read-only memory (ROM), compact disc (CD), digital versatile disk (DVD), cache, random access memory (RAM), and/or any other device storage disk or storage disk in the information is stored for any duration (that is, for extended periods of time, permanently, for brief cases, for temporary storage, and/or for caching of the information). As used herein, the term tangible computer readable storage medium is expressly defined to include any type of computer readable storage device and/or storage disk and to exclude advertising signs. As used herein, “tangible computer-readable storage medium” and “tangible machine-readable storage medium” are used interchangeably. Additionally or alternatively, the exemplary processes of Figures 9 to 13 may be implemented using coded instructions (i.e., computer and/or machine readable instructions) stored on a non-transient computer and/or machine readable medium such as a hard disk drive, flash memory, read-only memory, compact disc, digital versatile disk, cache, random access memory, and/or any other storage device or storage disk on which information is stored for any duration (that is, for extended periods of time, permanently, for brief cases, for temporary storage, and/or for caching of information). As used herein, the term non-transient computer-readable medium is expressly defined to include any type of computer-readable device or disk and to exclude advertising signals. As used herein, when the phrase "at least" is used as the transitional term in a preamble of a claim, it is open ended in the same way that the term "comprise" is open ended.
[109] [109] Figure 9 is a representative flowchart of example computer-readable instructions 900 that can be executed to implement the example navigation 110 of Figures 1 through 4, 5B, 6B, 7B, and/or 8B to implement mapping of a cookie from AME for partner DP cookies for browsing.
[110] [110] The example browser 110 of Figure 1 sends a request to a web page (e.g. to a partner DP and/or another web page publisher)
[111] [111] Sample browser 110 determines whether a cookie for the AME domain is stored (block 910). For example, AME may have caused the browser 110 to previously store a cookie for the AME domain. If a cookie for the AME domain is stored (block 910), the sample browser 110 adds the AME cookie to the flag request (block 912). After adding the AME cookie to the flag request (block 912), or if there is no cookie stored for the AME domain (block 910), the sample browser 110 sends the flag request to the AME server 114 (block 914) . Exemplary methods and apparatus for making any blocks 902 to 914 are described in U.S. Patent No. 8,370,489, the entirety of which is incorporated by reference as though set forth in its entirety herein.
[112] [112] Example browser 110 determines whether a response has been received (block 916). If a response has not been received (block 916), the example browser 110 determines whether a response timeout (e.g., a watchdog timer) has elapsed (block 917). For example, when the browser 110 provides an AME cookie in the flag request and the AME server 114 determines that the AME cookie is mapped to a partner DP cookie, the exemplary AME server 114 may insert impression record and omit transmitting a response to browser 110. Upon non-response, the exemplary AME server 114 and browser 110 can reduce the amount of network traffic and/or reduce the amount of data that is sent to partner DPs. If a response timeout has not occurred (block 917), control reverts to block 916 to continue waiting for a response to the flag request. In some examples, a timer is used at block 916 to prevent stopping in an infinite loop. In such examples, if no response is received within the timeout period, control jumps out of block 916 to terminate the instructions of Figure 9.
[113] [113] When a response is received (block 916), the exemplary browser 110 determines whether the response is a redirect message (e.g., a 302 FOUND message) (block 918). If the response is a redirect message (block 918), the example browser 110 generates a partner DP request from the redirection instructions (block 920). For example, the DP partner request might include a URL of a DP partner server specified in the redirect message.
[114] [114] Sample browser 110 determines whether a cookie for the partner DP domain specified in the redirect is stored (block 922). For example, the partner DP may have caused a browser 110 to previously store a cookie for the partner DP's domain. If there is a cookie for the DP partner domain stored (block 922), the example browser adds the DP partner cookie to the DP partner request (block 924). After the DP partner cookie is added (block 924), or if no DP partner cookie is stored (block 922), the example browser 110 sends the DP partner request to the DP partner server 108 (block 926). After sending the partner DP request to the partner DP server (block 926), if the response from the AME server 114 is not a redirect (for example, it is a placeholder image such as a 1x1 transparent pixel) (block 918), or if a response timeout occurs (block 917), example instructions 900 terminate.
[115] [115] Figure 10 is a representative flowchart of example machine-readable instructions 1000 that can be executed to deploy the example AME server 114 of Figures 1 through 4, 5B, 6B, 7B, and/or 8B to start mapping an AME cookie for partner DP cookies.
[116] [116] The exemplary AME server 114 of Figure 1 receives a flag request from a browser (e.g., browser 110 of Figure 1) (block 1002). The exemplary AME server 114 determines whether the flag request includes an AME cookie (block 1004). If the flag request does not include an AME cookie (block 1004), the example AME server 114 generates an AME cookie for the browser (block 1006). For example, the AME cookie enables the AME server to track online browser activity on AME-tagged web pages. If the flag request includes an AME cookie (block 1004), the example AME server 114 determines whether the AME cookie is already mapped to a partner DP cookie (block 1008). For example, the AME server 114 can determine whether the AME cookie maps to a cookie from one or more partner DPs. If the AME cookie is mapped to a partner DP cookie (block 1008), the exemplary AME server 114 determines whether an additional mapping is desired (block 1009). For example, although the AME server 114 may have a mapping between the AME cookie and a first partner DP cookie, it may be desirable to map the AME cookie to a second (or more) partner DP cookies from other DPs partners to improve the quality of demographic information applied to print data.
[117] [117] If a mapping from the AME cookie to a partner DP cookie (e.g. the first partner DP cookie and/or an additional partner DP cookie) is desired (blocks 1008, 1009), or after generation of the AME cookie (block 1006), the exemplary AME server 114 generates a redirect response (block 1010). The exemplary AME server 114 includes an AME cookie identifier (e.g., the cookie generated or previously stored) and an address (e.g., a URL) of a partner DP to be contacted in the redirect response (block 1012). The exemplary AME server 114 sends the redirect response (e.g., including the AME cookie identifier and partner DP address) to browser 110 (block 1014). In some examples, blocks 1002 to 1014 represent a process and blocks 1016 to 1030 represent a separate process running in parallel. In such examples, the first process terminates after block 1014.
[118] [118] Returning to the example of Figure 10, the exemplary AME server 114 determines whether an AME cookie to partner DP cookie mapping has been received (block 1016). Exemplary AME server 114 may wait for a period of time between blocks 1014 and 1016 (e.g. to allow browser 110 to send request s to partner DP server 108). If an AME cookie to partner DP cookie mapping is received (block 1016), the exemplary AME server 114 inserts AME cookie record to partner DP cookie mapping (block 1018). For example, the mapping might include the AME cookie identifier and a corresponding partner DP cookie identifier.
[119] [119] In some examples, blocks 1016 and 1018 constitute a thread that can run as a separate process to receive and/or store mappings between AME cookies and partner DP cookies. For example, AME server 114 may redirect browsers to DP partner servers 108, 304. DP partner servers 108, 304 determine the associations between AME cookies and DP partner cookies and, instead of immediately transmitting the mappings to the AME server 114 (e.g. directly via the browser 110), the example partner DP servers 108, 304 process and/or transmit the mappings as a batch (e.g. multiple messages, multiple mappings in a file, etc.).
[120] [120] Returning to the example in Figure 10, after inserting the mapping cookie record (block 1018) or, if no mapping cookie is received (block 1016), the example AME server 114 determines whether to request a mapping from from an additional partner DP (block 1020). For example, the browser 110 may select multiple flag requests based on the tag instructions to enable the AME server 114 to redirect requests to multiple partner DPs. If the AME server 114 must request mapping from an additional partner DP (block 1020), the exemplary AME server 114 generates a redirect response (block 1022). The exemplary AME server 114 includes an AME cookie (e.g., the generated or received AME cookie) in the redirect response (block 1024). The exemplary AME server 114 sends the redirect request to the browser 110 (block 1026).
[121] [121] In some instances where the AME server 114 must request mappings from additional (e.g. multiple) partner DPs (block 1020), the exemplary AME server 114 may issue multiple redirect responses to the browser 110 simultaneously in response to the flag request.
[122] [122] Returning to the example in Figure 10, the exemplary AME server 114 stores the AME cookie for subsequent matching to DP partner data (e.g., through a periodic transmission of DP partner OCR and/or demographic information) ( block 1028).
[123] [123] After storing the AME cookie (block 1028), if the AME server 114 should not request the mapping from an additional partner DP (block 1020) or, if the cookie mappings to additional partner DPs are not (block 1009), the example instructions 1000 of Figure 10 ends.
[124] [124] Figure 11 is a representative flowchart of example machine-readable instructions 1100 that can be executed to deploy the example AME server 114 of Figures 1 through 4, 5B, 6B, 7B, and/or 8B to associate obtained demographics with from a partner DP with online monitoring activity information (eg print data and/or exposure data).
[125] [125] Example AME server 114 obtains an AME cookie for partner DP cookie mapping (block 1102). For example, the AME server 114 may receive an aperiodic report including mappings of AME cookies to partner DP cookies from the partner DP server 108 of Figure 1. Additionally or alternatively, the exemplary AME server 114 may receive messages ( eg HTTP messages) from DP partner servers 108, 304 (eg directly or via browser 110) which includes AME cookie to DP partner cookie mappings. The exemplary AME server 114 obtains demographic information corresponding to the partner DP cookie(s) (block 1104).
[126] [126] Example AME server 114 selects an AME cookie for partner DP cookie mapping (block 1106). The exemplary AME server 114 determines whether the partner DP cookie in the selected mapping is mapped to additional AME cookies (e.g., other AME cookies in addition to the AME cookie in the selected mapping) (block 1108). For example, multiple AME cookies may be provided to the browser 110 which is associated with a user which in turn is associated with a partner DP cookie. As AME cookies expire or are deleted by browser 110, additional AME cookies are provided to browser 110 and may be mapped to the same partner DP cookie. The exemplary AME server 114 can then correlate impressions for the user by merging impression data for multiple AME cookies that are mapped to the same partner DP cookie. If the partner DP cookie is mapped to additional AME cookies (block 1108), the example AME server merges the AME cookie(s) mappings corresponding to the partner DP cookie (block 1110). By merging the mappings, the exemplary AME server 114 can merge user activities (eg, impressions) associated with the browser.
[127] [127] After the mappings are merged (block 1110) or if the partner DP cookie is mapped to additional AME cookies (block 1108), the example AME server 114 determines whether the AME cookie(s) ( for example, the AME cookie of the selected mapping and/or the merged AME cookie(s) is(are) mapped to the additional partner DP cookie(s) (block 1112). For example, AME server 114 may request and receive mappings from multiple partner DP servers 108, 304 for a single AME cookie as described above. If AME cookie(s) are mapped (s) for cookie(s) of additional partner DP(s) (block 1112), the example AME server 114 merges the cookie mappings of additional partner DP(s) with the cookie(s) of AME (block 1114).
[128] [128] After the mappings are merged (block 1114), or, if there are no additional partner DPs cookies mapped to the AME cookies (block 1112), the example AME server 114 determines if there are additional mappings to consider for blend (block 1116). If there are additional mappings (block 1116), control returns to block 1106 to select another AME cookie for partner DP cookie mapping.
[129] [129] When there are no additional mappings (block 1116), the example AME server 114 associates measured online activity (e.g. print data) with AME cookies to incoming demographic information corresponding to DP partner cookies (e.g. based on merged or unmerged mappings from AME cookies to DP partner cookies) (block 1118). For example, the AME server 114 can match the impression data measured in association with an AME cookie with the demographic data received in association with a DP partner cookie by determining the mapping from the AME cookie to the DP partner cookie. The exemplary AME server 114 associates with the AME cookie any additional online activity that has been measured by the DP partner using the DP partner cookie (block 1120). As a result, the example AME server 114 aggregates the online activity (if any) measured by the AME with online activity measured by the DP partner that was not measured by the AME, which is additionally associated with the demographic information provided by the DP partner that was not available prior to AME. Exemplary instructions 1100 then terminate.
[130] [130] Figure 12 is a representative flowchart of example machine-readable instructions 1200 that can be executed to deploy the example DP partner server 108, 304 of Figures 1 through 4, 5B, 6B, 7B, and/or 8B for mapping an AME cookie to a DP partner cookie. For clarity, the exemplary instructions 1200 of Figure 12 are described below with reference to the exemplary DP partner server 108.
[131] [131] The exemplary DP partner server 108 of Figure 1 receives a request from a browser (e.g., browser 110 of Figure 1) (lock 1202). The exemplary DP partner server 108 determines whether the request includes a DP partner cookie (block 1204). For example, if a user of browser 110 has previously established an account or otherwise provided information to the DP partner, the exemplary DP partner may have stored a cookie on a computer running browser 110.
[132] [132] If the request includes a DP partner cookie (block 1204), the exemplary DP partner server 108 reads the DP partner cookie data (block 1206). For example, the DP partner server 108 may determine a user identifier or other identifying information from the DP partner cookie data. The exemplary DP partner server 108 then identifies the user registered with the DP partner based on the cookie (lock 1208).
[133] [133] The exemplary DP partner server 108 generates a mapping response (block 1210). The DP partner server 108 includes an AME cookie for mapping DP partner cookie in the mapping response (block 1212). For example, the DP partner server 108 may include a URL that includes the domain of the AME server 114, an AME cookie identifier, and a DP partner cookie identifier mapped to the AME cookie in the mapping response. The exemplary DP partner server 108 determines whether to include the demographic information corresponding to the DP partner cookie in the mapping (block 1214). For example, the DP partner server 108 may provide demographic information with the mapping and/or may provide demographic information to the AME 102 on a periodic basis.
[134] [134] If DP partner server 108 is not to include demographic information in the mapping (block 1214), example DP partner server 108 sends a mapping response to AME server 114 or browser 110 (block 1216). For example, the DP partner server 108 may send an asynchronous HTTP request to the AME server 114 and/or send a redirected response to the browser 110 to cause the browser to send a request to the AME server 114. The exemplary DP partner server 108 periodically sends data including the AME cookie, DP partner cookie and demographic information to the AME server 114 (block 1218). However, the DP partner server 108 may additionally or alternately send the data to the AME server 114 at aperiodic or other intervals. If the DP partner server 108 is to include demographic information (block 1214), the example DP partner server 108 sends a mapping response that includes demographic information to the AME server 114 or browser 110 (block 1220).
[135] [135] After sending the mapping response that includes the demographic information (block 1220) or after sending the mapping response and sending the demographic data separately (blocks 1216 and 1218), the example instructions in Figure 12 end.
[136] [136] Figure 13 is a representative flowchart of exemplary machine-readable instructions 1300 that can be executed to implement the exemplary flag instruction generator 126 of Figure 1 to generate flag instructions (e.g., flags) to be served by a web server (e.g., the web server 106 of Figure 1) to mark up media (e.g., an advertisement, a web page, etc.).
[137] [137] The example beacon instruction generator 126 of Figure 1 receives web location and/or web server information (e.g. address information, information describing the web locations served by the web server 106 of Figure 1 ) (lock 1302). Exemplary beacon instruction generator 126 generates beacon instruction(s) for the web site and/or the web server (block 1304). In some examples, the flag instruction generator 126 generates a template instruction for a web site and/or web site element (e.g., for a total web site, for an advertisement or other media that is part of a web site). a web site, etc.). The exemplary flag instruction generated by the flag instruction generator 126 causes a browser or other client device that receives the flag instruction to initiate flag requests to facilitate print measurement and/or a process that results in mapping a AME cookie to one or more DP partner cookies as disclosed herein.
[138] [138] Example flag instruction generator 126 determines whether the flag instruction includes modified (e.g. customizable) data (lock 1306). Exemplary modified data can be included in the beacon instruction to customize the beacon instruction for a web site, a web server, an ad campaign, or other purpose. Exemplary information that can be configured as unmodified includes an address of the AME server 114 to which the flag instruction is to initiate communication. If there is modified information in the beacon instruction (block 1306), the example beacon instruction generator 126 modifies the modified beacon instruction data based on web location and/or web server information (block 1308).
[139] [139] In some examples, the flag instruction includes data that is modified by the web server 106 based on the web page that is served to the browser 110. For example, the flag instruction may provide different data to the example browser 110 depending on browser user identity 110 and/or a timestamp of sending the flag instruction.
[140] [140] After modifying the flag instruction data (block 1308), or if the flag instruction is not modified (block 1306), the example flag instruction generator 126 provides the flag instruction to the web server 106 for inclusion on the media (lock 1310). For example, the beacon instruction generator 126 may transmit the beacon instruction to the web server 106 through a communications interface and/or provide the instruction to a developer or web site administrator for inclusion in script and/or code. from the web server 106. The example instructions 1300 then terminate and/or iterate to generate additional beacon instructions for the web server 106 or additional web servers.
[141] [141] Figure 14 is a block diagram of an example processor platform 1400 capable of executing the instructions of Figures 9 to 13 for deploying the exemplary AME server(s) 114, the exemplary DP partner server 108 , 304, example browser 110 and/or, more generally, example systems 100, 300 of Figures 1 to 4, 5B, 6B, 7B, and/or 8B. Processor platform 1400 can be, for example, a server, a personal computer, or any other type of computing device.
[142] [142] The 1400 processor platform of the illustrated examples includes a 1412 processor. The 1412 processor of the illustrated example is hardware. For example, the 1412 processor can be deployed by one or more integrated circuits, logic circuits, microprocessors or controllers from any desired family or manufacturer.
[143] [143] The 1412 processor in the illustrated example includes a 1413 local memory (eg, a cache). The processor 1412 of the illustrated example is in communication with a main memory that includes a volatile memory 1414 and a non-temporary memory 1416 over a bus 1418. The volatile memory 1414 can be deployed by Synchronous Dynamic Random Access Memory (SDRAM), Memory Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and/or any other type of random access memory device. The non-temporary memory 1416 can be deployed by fast memory and/or any other desired type of memory device. Access to main memory 1414, 1416 is controlled by a memory controller.
[144] [144] The 1400 processor platform of the illustrated example also includes a 1420 interface circuit. The 1420 interface circuit can be implemented by any type of interface standard, such as the Ethernet interface, a universal serial bus (USB), a PCI expression interface and/or any other communications interface.
[145] [145] In the illustrated example, one or more input devices 1422 are connected to the interface circuit 1420. The input device(s) 1422 allow a user to enter data and command within the 1412 processor. The input device(s) may be implanted by, for example, an audio sensor, a microphone, a camera (static or video), a keyboard, a button, a mouse, a touch screen, a track-pad device, a trackball device, isopoint and/or a voice recognition system.
[146] [146] One or more output devices 1424 are also connected to the 1420 interface circuit of the illustrated example. The 1424 output devices may be deployed, for example, by display devices (e.g., a light-emitting diode (LED), an organic light-emitting diode (OLED), a liquid crystal display, a cathode ray tube (CRT), a touch screen, a touch output device, a light emitting diode (LED), a printer and/or speakers). The illustrated example interface circuit 1420, then, typically includes a graphics driver card, graphics driver chip, or graphics driver processor.
[147] [147] The 1420 interface circuit of the illustrated example also includes a communication device such as a transmitter, a receiver, a transceiver, a modem and/or network interface card to facilitate data exchange with external machines (e.g., computing devices of any kind) over a 1426 network (for example, an Ethernet connection, a digital subscriber line (DSL), a telephone cable, a coaxial cable, a cellular telephone system, etc.).
[148] [148] The processor platform 1400 of the illustrated example also includes one or more mass storage devices 1428 for storing software and/or data. Examples of such 1428 mass storage devices include floppy disk drives, hard drives, compact disk drives, Blu-ray Disc drives, RAID systems, and Digital Versatile Disk (DVD) drives.
[149] [149] Coded instructions 1432 of Figures 9 to 13 may be stored on mass storage device 1428, volatile memory 1414, non-volatile memory 1416, and/or on a removable, tangible computer-readable storage medium such as a CD or DVD.
[150] [150] The exemplary methods and apparatus disclosed in this document provide demographic information to audience measurement entities for larger numbers of online users than was previously available to audience measurement entities. The exemplary methods and apparatus disclosed herein reduce the uncertainty associated with the use of statistical methods by increasing the amounts of data collected, while maintaining privacy for individual users. The exemplary methods and devices disclosed in this document reduce a number of redirects necessary for database owners during the lifetime or validity of the associated cookies. By reducing the number of redirects, example methods and devices disclosed in this document reduce interruptions, interference and/or background processing that can adversely affect the performance of client browsers, thereby enhancing an overall user experience for members. of audience. Exemplary methods and devices improve the overall efficiencies of networking environments by reducing network and display congestion associated with collecting exposure information corresponding to demographic information.
[151] [151] Note that this patent claims priority from Patent Application Serial No. AU 2013204865, which was filed on April 12, 2013 and incorporated herein in its entirety by reference.
[152] [152] While certain exemplary methods, apparatus and articles of manufacture have been disclosed herein, the scope of coverage of that patent is not limited thereto. On the contrary, this patent covers all methods, apparatus and articles of manufacture that are correctly within the scope of the claims of this patent.

权利要求:
Claims (1)
[1]
client device.
16. Apparatus, characterized in that it comprises a processor configured to perform the method as defined in claims 11 to 15.
17. Computer-readable storage medium, characterized in that it comprises computer-readable instructions that, when executed, cause the processor to perform the method as defined in claims 11 to 15.
18. Method, characterized in that it comprises: receiving a first request from a client device, the first request comprising an audience measurement entity cookie; and providing a cookie mapping to an audience measurement entity associated with the cookie, wherein the cookie mapping comprises an association between a database owner cookie and the audience measurement cookie associated with the customer.
19. Method according to claim 18, characterized in that providing the cookie mapping comprises sending a redirect message to make the client send the cookie mapping to the audience measurement entity.
20. Method according to claim 19, characterized in that the redirect message comprises the database owner cookie, the audience measurement entity cookie and an indication of association between the database owner cookie data and the audience measurement entity cookie.
21. Method according to claim 18, characterized in that providing the cookie mapping comprises sending a message to the audience measurement entity, the message comprising the cookie mapping.
22. Method according to claim 21, characterized in that the message additionally comprises a second cookie mapping between a second audience measurement entity cookie for a second client device and a second database owner cookie. data associated with the second client device.
23. Apparatus, characterized in that it comprises a processor configured to perform the method as defined in claims 18 to 22.
24. Computer-readable storage medium, characterized in that it comprises computer-readable instructions that, when executed, cause the processor to perform the method as defined in claims 18 to 22.
25. Apparatus, characterized in that it comprises: a communications interface for receiving a first request from a client device, the first request comprising an audience measurement entity cookie identifier; and a cookie mapper to determine a cookie mapping from the audience measurement entity cookie to a database owner cookie associated with the customer.
26. Method, characterized by the fact that it comprises: providing instructions to be included in a website, instructions to make a customer, after executing the instructions, start a process that comprises: sending a first request to an entity audience measurement; and sending a second request to cause a database owner to send the audience measurement entity a cookie mapping of an audience measurement entity cookie to a corresponding customer database owner cookie.
27. Method according to claim 26, characterized in that it additionally comprises receiving information associated with the website and generating instructions based on the information.
28. Method according to claim 27, characterized in that the process additionally comprises receiving a redirect message from the audience measurement entity, the redirection message comprising an audience measurement cookie identifier.
29. Apparatus, characterized in that it comprises a processor configured to perform the method as defined in claims 26 to 28.
30. Computer-readable storage medium, characterized in that it comprises computer-readable instructions that, when executed, cause the processor to perform the method as defined in claims 26 to 28.
31. Device, characterized in that it comprises: a communications interface; and a processor for generating instructions to be included in a website and for causing the communications interface to provide instructions to a web server associated with the website, instructions for causing a client, after execution from the instructions, initiate a process comprising: submitting a first request to an audience measurement entity; and sending a second request to cause a database owner to send the audience measurement entity a cookie mapping of an audience measurement entity cookie to a corresponding customer database owner cookie.
32. Method, characterized in that it comprises: sending a first request to an audience measurement entity; and sending a second request to cause a database owner to send the audience measurement entity a cookie mapping of an audience measurement entity cookie to a database owner cookie corresponding to a customer.
33. Method according to claim 32, characterized in that it additionally comprises storing the database owner cookie.
34. Method according to claim 32, characterized in that the sending of the first request to the audience measurement entity occurs in response to the execution of beacon instructions on a web page.
35. Method according to claim 32, characterized in that the second request additionally serves to cause the database owner to send to the audience measurement entity a demographic characteristic associated with the customer.
36. Method, according to claim 32, characterized in that it additionally comprises: sending a third request to the audience measurement entity; and sending a fourth request to have a second database owner send the audience measurement entity a second cookie mapping from the audience measurement entity cookie to a second database owner cookie.
37. Method according to claim 32, characterized in that the second request serves to make the database owner send the cookie mapping to the audience measurement entity asynchronously.
38. Method according to claim 32, characterized in that it additionally comprises sending a third request to the audience measurement entity, the third request including the cookie mapping.
39. Apparatus, characterized in that it comprises a processor configured to perform the method as defined in claims 32 to 38.
40. Computer-readable storage medium, characterized in that it comprises computer-readable instructions that, when executed, cause the processor to perform the method as defined in claims 32 to 38.
41. Device, characterized in that it comprises: a communications interface; and a web browser to: send a first request to an audience measurement entity through the communications interface; and sending a second request through the communications interface to cause a database owner to send the audience measurement entity a cookie mapping of an audience measurement entity cookie to a database owner cookie corresponding to a customer.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112014030132A2|2021-08-24|methods and gadgets for sharing media impression data online

---

JP2020004415A|2020-01-09|Method and device for specifying impression using distributed demographic information

---

US20180295199A1|2018-10-11|Methods and apparatus to use client-server communications across internet domains to determine distributed demographic information for media impressions

---

US20200236569A1|2020-07-23|Cross-channel user tracking systems, methods, and devices

---

US20160189182A1|2016-06-30|Methods and apparatus to correct age misattribution in media impressions

---

US20160379246A1|2016-12-29|Methods and apparatus to estimate an unknown audience size from recorded demographic impressions

---

JP6593936B2|2019-10-23|Perform media monitoring for mobile platforms using adaptive bitrate streaming and associated messaging

---

US20160344838A1|2016-11-24|Caching of tracking elements in network content

---

US20150245110A1|2015-08-27|Management of invitational content during broadcasting of media streams

---

US20180315060A1|2018-11-01|Methods and apparatus to estimate media impression frequency distributions

---

JP2020030849A|2020-02-27|Apparatus, methods and storage media to share online media impression data

---

JP2022043222A|2022-03-15|Devices, storage media and methods for sharing online media impression data

---

JP6198214B2|2017-09-20|Method and apparatus for measuring media using media object properties

同族专利:

---

公开号 | 公开日

---

CA3146671A1|2013-12-19|

---

WO2013188429A2|2013-12-19|

---

WO2013188429A3|2014-04-24|

---

JP2019023924A|2019-02-14|

---

KR20150029631A|2015-03-18|

---

AU2018282471A1|2019-01-24|

---

US20180255151A1|2018-09-06|

---

AU2013204865B2|2015-07-09|

---

EP2859466A2|2015-04-15|

---

CN109905458A|2019-06-18|

---

AU2015230772B2|2016-10-06|

---

US10027773B2|2018-07-17|

---

JP2017174461A|2017-09-28|

---

US9215288B2|2015-12-15|

---

KR20160106210A|2016-09-09|

---

JP6157021B2|2017-07-05|

---

AU2017200060B2|2018-11-08|

---

AU2013204865A1|2014-01-09|

---

US20160021204A1|2016-01-21|

---

AU2015230772A1|2015-10-15|

---

IN2014DN10164A|2015-08-21|

---

CN109905458B|2021-12-24|

---

EP2859466A4|2016-01-06|

---

JP2015524118A|2015-08-20|

---

AU2017200060A1|2017-02-02|

---

KR101727602B1|2017-04-17|

---

US10536543B2|2020-01-14|

---

AU2018282471B2|2020-07-02|

---

JP6612949B2|2019-11-27|

---

CN104520839A|2015-04-15|

---

CN104520839B|2019-01-15|

---

CA2875210A1|2013-12-19|

---

US20130332604A1|2013-12-12|

---

KR101655998B1|2016-09-22|

---

US20200153916A1|2020-05-14|

---

HK1208279A1|2016-02-26|

---

JP6423486B2|2018-11-14|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

GB2176639B|1985-05-31|1988-11-23|Mars Inc|Data acquisition system|

---

JP3400068B2|1994-03-18|2003-04-28|富士通株式会社|Response amount prediction system|

---

CA2119970A1|1994-03-25|1995-09-26|Michael A. Lyons|Program monitoring system|

---

US5594934A|1994-09-21|1997-01-14|A.C. Nielsen Company|Real time correlation meter|

---

US5758257A|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|1995-03-16|1996-09-19|Bell Atlantic Network Services, Inc.|Simulcasting digital video programs for broadcast and interactive services|

---

US5675510A|1995-06-07|1997-10-07|Pc Meter L.P.|Computer use meter and analyzer|

---

US5848396A|1996-04-26|1998-12-08|Freedom Of Information, Inc.|Method and apparatus for determining behavioral profile of a computer user|

---

US5832520A|1996-07-03|1998-11-03|Miller, Call, Plauck And Miller|Automatic file differencing and updating system|

---

US6073241A|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|

---

US6108637A|1996-09-03|2000-08-22|Nielsen Media Research, Inc.|Content display monitor|

---

US5870740A|1996-09-30|1999-02-09|Apple Computer, Inc.|System and method for improving the ranking of information retrieval results for short queries|

---

US5948061A|1996-10-29|1999-09-07|Double Click, Inc.|Method of delivery, targeting, and measuring advertising over networks|

---

US6052730A|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|1997-03-13|2000-03-07|At&T Corporation|Network information delivery system for delivering information based on end user terminal requirements|

---

US6643696B2|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|

---

US5796952A|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|

---

US6141694A|1997-09-16|2000-10-31|Webtv Networks, Inc.|Determining and verifying user data|

---

US6286140B1|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|1998-03-19|2000-08-01|International Business Machines Corp.|Maintaining sessions in a clustered server environment|

---

US6279036B1|1998-05-15|2001-08-21|International Business Machines Corporation|Method and apparatus for detecting actual viewing or electronic advertisements|

---

US20020095676A1|1998-05-15|2002-07-18|Robert A. Knee|Interactive television program guide system for determining user values for demographic categories|

---

US7240022B1|1998-05-19|2007-07-03|Mypoints.Com Inc.|Demographic information gathering and incentive award system and method|

---

US6434614B1|1998-05-29|2002-08-13|Nielsen Media Research, Inc.|Tracking of internet advertisements using banner tags|

---

US6223215B1|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|

---

US6275934B1|1998-10-16|2001-08-14|Soft Book Press, Inc.|Authentication for information exchange over a communication network|

---

US7949565B1|1998-12-03|2011-05-24|Prime Research Alliance E., Inc.|Privacy-protected advertising system|

---

US6457010B1|1998-12-03|2002-09-24|Expanse Networks, Inc.|Client-server based subscriber characterization system|

---

US7150030B1|1998-12-03|2006-12-12|Prime Research Alliance, Inc.|Subscriber characterization system|

---

US6684194B1|1998-12-03|2004-01-27|Expanse Network, Inc.|Subscriber identification system|

---

US6055573A|1998-12-30|2000-04-25|Supermarkets Online, Inc.|Communicating with a computer based on an updated purchase behavior classification of a particular consumer|

---

US6460079B1|1999-03-04|2002-10-01|Nielsen Media Research, Inc.|Method and system for the discovery of cookies and other client information|

---

US6529952B1|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|1999-05-27|2004-04-13|Andersen Consulting Llp|Business alliance identification in a web architecture framework|

---

US6102406A|1999-06-07|2000-08-15|Steven A. Miles|Internet-based advertising scheme employing scavenger hunt metaphor|

---

US6606657B1|1999-06-22|2003-08-12|Comverse, Ltd.|System and method for processing and presenting internet usage information|

---

US7010497B1|1999-07-08|2006-03-07|Dynamiclogic, Inc.|System and method for evaluating and/or monitoring effectiveness of on-line advertising|

---

AUPQ206399A0|1999-08-06|1999-08-26|Imr Worldwide Pty Ltd.|Network user measurement system and method|

---

US6415323B1|1999-09-03|2002-07-02|Fastforward Networks|Proximity-based redirection system for robust and scalable service-node location in an internetwork|

---

US6839680B1|1999-09-30|2005-01-04|Fujitsu Limited|Internet profiling|

---

US6704787B1|1999-12-03|2004-03-09|Intercard Payments, Inc.|Date of birth authentication system and method using demographic and/or geographic data supplied by a subscriber that is verified by a third party|

---

US6691163B1|1999-12-23|2004-02-10|Alexa Internet|Use of web usage trail data to identify related links|

---

US7146329B2|2000-01-13|2006-12-05|Erinmedia, Llc|Privacy compliant multiple dataset correlation and content delivery system and methods|

---

US6993590B1|2000-01-13|2006-01-31|Inktomi Corporation|Method of creating data streams for user-specific usage data gathering systems|

---

US7139723B2|2000-01-13|2006-11-21|Erinmedia, Llc|Privacy compliant multiple dataset correlation system|

---

US7065503B2|2000-01-14|2006-06-20|Matsushita Electric Industrial Co., Ltd.|Cookie data stored on transportable recording medium|

---

WO2001052168A1|2000-01-14|2001-07-19|Matsushita Electric Industrial Company, Limited|Cookie data stored on transportable recording medium|

---

AU2965401A|2000-01-21|2001-07-31|Angara E Commerce Services Inc|Electronic commerce services|

---

US6732331B1|2000-02-15|2004-05-04|Vlad Alexander|System and process for managing content organized in a tag-delimited template using metadata|

---

US7930285B2|2000-03-22|2011-04-19|Comscore, Inc.|Systems for and methods of user demographic reporting usable for identifying users and collecting usage data|

---

US7260837B2|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|2000-03-22|2007-02-20|Comscore Networks Inc.|Systems and methods for collecting consumer data|

---

JP2001338176A|2000-03-23|2001-12-07|Casio Comput Co Ltd|Method and system for information transmission and intermediation|

---

JP2001282982A|2000-03-28|2001-10-12|Hisahiro Negi|Web marketing system|

---

US7039699B1|2000-05-02|2006-05-02|Microsoft Corporation|Tracking usage behavior in computer systems|

---

US7523191B1|2000-06-02|2009-04-21|Yahoo! Inc.|System and method for monitoring user interaction with web pages|

---

US7962603B1|2000-06-06|2011-06-14|Nobuyoshi Morimoto|System and method for identifying individual users accessing a web site|

---

JP2001357192A|2000-06-12|2001-12-26|Toshiba Corp|Method and system for customer awareness research and storage medium storing program|

---

JP2004504674A|2000-07-18|2004-02-12|ヤフー！　インコーポレイテッド|System and method for selecting another advertising inventory instead of a sold-out advertising inventory|

---

US7363643B2|2000-08-31|2008-04-22|Eddie Drake|Real-time audience monitoring, content rating, and content enhancing|

---

KR20020037980A|2000-11-16|2002-05-23|김형순|System for retrieving and providing information|

---

JP2002163562A|2000-11-27|2002-06-07|Dainippon Printing Co Ltd|Information distribution server device|

---

US6879960B2|2000-12-01|2005-04-12|Claritas, Inc.|Method and system for using customer preferences in real time to customize a commercial transaction|

---

US20030006911A1|2000-12-22|2003-01-09|The Cadre Group Inc.|Interactive advertising system and method|

---

JP4248183B2|2001-02-26|2009-04-02|パナソニック株式会社|Cookie processing program and image data display device|

---

WO2002082214A2|2001-04-06|2002-10-17|Predictive Media Corporation|Method and apparatus for identifying unique client users from user behavioral data|

---

WO2002084507A1|2001-04-13|2002-10-24|Netiq Corporation|User-side tracking of multimedia application usage within a web page|

---

US20040167763A1|2002-05-31|2004-08-26|Liebman Michael N|Information processing method for evaluating biochemical pathway models using clinical data|

---

US7647418B2|2001-06-19|2010-01-12|Savvis Communications Corporation|Real-time streaming media measurement system and method|

---

US20030037131A1|2001-08-17|2003-02-20|International Business Machines Corporation|User information coordination across multiple domains|

---

JP2003067289A|2001-08-30|2003-03-07|Bear Communications Co Ltd|Delivery system for advertisement on the web|

---

JPWO2003027860A1|2001-09-19|2005-01-13|株式会社エヌ・ティ・ティ・アド|Content distribution system for distributing content changing on time axis, content distribution server, log collection server, content relay server, user terminal, content viewing state grasping method, recommendation method, and content providing method|

---

US6877007B1|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|

---

US7272617B1|2001-11-30|2007-09-18|Ncr Corp.|Analytic data set creation for modeling in a customer relationship management system|

---

US7343417B2|2001-11-30|2008-03-11|Knowledge Networks, Inc.|System and method for rating media information|

---

US7555755B2|2002-02-01|2009-06-30|John Fairweather|System and method for navigating data|

---

US7890451B2|2002-10-09|2011-02-15|Compete, Inc.|Computer program product and method for refining an estimate of internet traffic|

---

US20030177488A1|2002-03-12|2003-09-18|Smith Geoff S.|Systems and methods for media audience measurement|

---

US20030229884A1|2002-05-21|2003-12-11|Hewlett-Packard Development Company|Interaction manager template|

---

EP1379044A1|2002-06-22|2004-01-07|TELEFONAKTIEBOLAGET LM ERICSSON |Method for providing information to a web server|

---

US8086559B2|2002-09-24|2011-12-27|Google, Inc.|Serving content-relevant advertisements with client-side device support|

---

US20040088212A1|2002-10-31|2004-05-06|Hill Clarke R.|Dynamic audience analysis for computer content|

---

US7574423B2|2003-03-20|2009-08-11|International Business Machines Corporation|Partial data model exposure through client side caching|

---

CA2686265A1|2003-06-17|2004-12-17|Ibm Canada Limited - Ibm Canada Limitee|Multiple identity management in an electronic commerce site|

---

US9117217B2|2003-08-01|2015-08-25|Advertising.Com Llc|Audience targeting with universal profile synchronization|

---

ZA200600900B|2003-08-01|2007-05-30|Tacoda Systems Inc|System and method for segmenting and targeting audience members|

---

US7805332B2|2003-08-01|2010-09-28|AOL, Inc.|System and method for segmenting and targeting audience members|

---

US8464290B2|2003-08-01|2013-06-11|Tacoda, Inc.|Network for matching an audience with deliverable content|

---

US20070198327A1|2003-08-15|2007-08-23|Amir Yazdani|Systems and methods for measuring, targeting, verifying, and reporting advertising impressions|

---

JPWO2005024689A1|2003-09-04|2007-11-08|株式会社インタースコープ|Method and apparatus for analyzing consumer purchasing behavior|

---

US7152074B2|2003-09-19|2006-12-19|International Business Machines Corporation|Extensible framework supporting deposit of heterogenous data sources into a target data repository|

---

WO2005041456A1|2003-10-24|2005-05-06|Telefonaktiebolaget Lm Ericsson |A method and device for audience monitoring on multicast capable networks|

---

US20050144069A1|2003-12-23|2005-06-30|Wiseman Leora R.|Method and system for providing targeted graphical advertisements|

---

US7949639B2|2004-02-20|2011-05-24|Symphonyiri Group, Inc.|Attribute segments and data table bias reduction|

---

US7792954B2|2004-04-02|2010-09-07|Webtrends, Inc.|Systems and methods for tracking web activity|

---

US20050267799A1|2004-05-10|2005-12-01|Wesley Chan|System and method for enabling publishers to select preferred types of electronic documents|

---

NZ553385A|2004-08-09|2010-06-25|Nielsen Co Us Llc|Methods and apparatus to monitor audio/visual content from various sources|

---

US7546370B1|2004-08-18|2009-06-09|Google Inc.|Search engine with multiple crawlers sharing cookies|

---

US7505958B2|2004-09-30|2009-03-17|International Business Machines Corporation|Metadata management for a data abstraction model|

---

US20060089754A1|2004-10-27|2006-04-27|Andrew Mortenson|An installed Vehicle Personal Computing system with touch interaction, voice interaction or sensor interaction 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, personal info portal, vehicle monitoring, alarm and camera security and recording.|

---

JP2006127320A|2004-10-29|2006-05-18|Solid Technology Kk|Terminal attribute estimation apparatus and terminal attribute estimation method|

---

JP2006127321A|2004-10-29|2006-05-18|Solid Technology Kk|Terminal attribute addition device and terminal attribute addition method|

---

US7302447B2|2005-01-14|2007-11-27|International Business Machines Corporation|Virtual columns|

---

US9003441B1|2005-04-13|2015-04-07|Google Inc.|Probabilistic inference of demographic information from user selection of content|

---

US8131861B2|2005-05-20|2012-03-06|Webtrends, Inc.|Method for cross-domain tracking of web site traffic|

---

US8856279B2|2005-05-26|2014-10-07|Citrix Systems Inc.|Method and system for object prediction|

---

US7849154B2|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|2005-08-18|2011-08-31|株式会社東芝|Content data distribution system and information processing apparatus|

---

CN101297315A|2005-08-26|2008-10-29|光点信迅公司|Systems and methods for media planning, ad production, ad placement and content customization|

---

US8574074B2|2005-09-30|2013-11-05|Sony Computer Entertainment America Llc|Advertising impression determination|

---

CN100452781C|2005-10-26|2009-01-14|华为技术有限公司|Method for transmitting partial unavailable information to destination user|

---

US20080086356A1|2005-12-09|2008-04-10|Steve Glassman|Determining advertisements using user interest information and map-based location information|

---

US20090030780A1|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|

---

CA2666199C|2006-03-27|2015-08-25|Nielsen Media Research, Inc.|Methods and systems to meter media content presented on a wireless communication device|

---

MX2007015979A|2006-03-31|2009-04-07|Nielsen Media Res Inc|Methods, systems, and apparatus for multi-purpose metering.|

---

US7941525B1|2006-04-01|2011-05-10|ClickTale, Ltd.|Method and system for monitoring an activity of a user|

---

US8131763B2|2006-05-03|2012-03-06|Cellco Partnership|Age verification and content filtering systems and methods|

---

US20070271518A1|2006-05-16|2007-11-22|Bellsouth Intellectual Property Corporation|Methods, Apparatus and Computer Program Products for Audience-Adaptive Control of Content Presentation Based on Sensed Audience Attentiveness|

---

US20070271580A1|2006-05-16|2007-11-22|Bellsouth Intellectual Property Corporation|Methods, Apparatus and Computer Program Products for Audience-Adaptive Control of Content Presentation Based on Sensed Audience Demographics|

---

US7818290B2|2006-06-14|2010-10-19|Identity Metrics, Inc.|System to associate a demographic to a user of an electronic system|

---

WO2007146876A2|2006-06-15|2007-12-21|The Nielsen Company|Methods and apparatus to meter content exposure using closed caption information|

---

US20080004958A1|2006-06-29|2008-01-03|Tony Ralph|Client side counting verification testing|

---

CN100456298C|2006-07-12|2009-01-28|百度在线网络技术（北京）有限公司|Advertisement information retrieval system and method therefor|

---

US20080086523A1|2006-08-18|2008-04-10|Akamai Technologies, Inc.|Method of data collection in a distributed network|

---

US9514436B2|2006-09-05|2016-12-06|The Nielsen Company , Llc|Method and system for predicting audience viewing behavior|

---

US20080086741A1|2006-10-10|2008-04-10|Quantcast Corporation|Audience commonality and measurement|

---

US8700457B2|2007-01-03|2014-04-15|William H. Bollman|Mobile phone based rebate device for redemption at a point of sale terminal|

---

CN101222348B|2007-01-10|2011-05-11|阿里巴巴集团控股有限公司|Method and system for calculating number of website real user|

---

US8874563B1|2007-03-07|2014-10-28|Comscore, Inc.|Detecting content and user response to content|

---

US8166076B2|2007-03-08|2012-04-24|Microsoft Corporation|Digital media metadata management|

---

KR100910517B1|2007-03-21|2009-07-31|엔에이치엔비즈니스플랫폼 주식회사|System and method for expanding target inventory according to borwser-login mapping|

---

US8229458B2|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|2007-05-05|2008-11-06|Intapp Inc.|Monitoring and Aggregating User Activities in Heterogeneous Systems|

---

WO2008150575A2|2007-05-31|2008-12-11|The Nielsen Company|Methods and apparatus to model set-top box data|

---

US8099315B2|2007-06-05|2012-01-17|At&T Intellectual Property I, L.P.|Interest profiles for audio and/or video streams|

---

US7890592B2|2007-06-29|2011-02-15|Microsoft Corporation|Processing data obtained from a presence-based system|

---

US8229780B2|2007-07-30|2012-07-24|Silvercarrot, Inc.|System and method for online lead generation|

---

US20110041168A1|2007-08-14|2011-02-17|Alan Murray|Systems and methods for targeting online advertisements using data derived from social networks|

---

US20090055241A1|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|2007-09-10|2010-04-13|Specific Media, Inc.|System and method of determining user demographic profiles of anonymous users|

---

US20090076899A1|2007-09-14|2009-03-19|Gbodimowo Gbeminiyi A|Method for analyzing, searching for, and trading targeted advertisement spaces|

---

US7925694B2|2007-10-19|2011-04-12|Citrix Systems, Inc.|Systems and methods for managing cookies via HTTP content layer|

---

US8073807B1|2007-11-02|2011-12-06|Google Inc|Inferring demographics for website members|

---

US8235814B2|2007-12-13|2012-08-07|Google Inc.|Impression normalization|

---

US20090171762A1|2008-01-02|2009-07-02|Microsoft Corporation|Advertising in an Entertainment Access Service|

---

US8180112B2|2008-01-21|2012-05-15|Eastman Kodak Company|Enabling persistent recognition of individuals in images|

---

US8302120B2|2008-02-19|2012-10-30|The Nielsen Company , Llc|Methods and apparatus to monitor advertisement exposure|

---

US20090217315A1|2008-02-26|2009-08-27|Cognovision Solutions Inc.|Method and system for audience measurement and targeting media|

---

US8151194B1|2008-03-26|2012-04-03|Google Inc.|Visual presentation of video usage statistics|

---

US8112301B2|2008-04-14|2012-02-07|Tra, Inc.|Using consumer purchase behavior for television targeting|

---

US20090292587A1|2008-04-17|2009-11-26|Arbitron, Inc.|Cross-media interactivity metrics|

---

US9083853B2|2008-06-02|2015-07-14|Intent IQ, LLC|Targeted television advertisements associated with online users' preferred television programs or channels|

---

US20090307084A1|2008-06-10|2009-12-10|Integrated Media Measurement, Inc.|Measuring Exposure To Media Across Multiple Media Delivery Mechanisms|

---

US20100010866A1|2008-07-11|2010-01-14|Microsoft Corporation|Advertising across social network communication pathways|

---

US8280683B2|2008-07-17|2012-10-02|International Business Machines Corporation|Probabilistic framework for the highly efficient correlation of call chains with hardware events|

---

JP4834042B2|2008-08-06|2011-12-07|ヤフー株式会社|User-created content management device, user-created content management system, and browser preference survey method|

---

US8549163B2|2008-09-18|2013-10-01|Jonathan M. Urdan|Passive parameter based demographics generation|

---

US20100088152A1|2008-10-02|2010-04-08|Dominic Bennett|Predicting user response to advertisements|

---

US20100088373A1|2008-10-06|2010-04-08|Jeremy Pinkham|Method of Tracking & Targeting Internet Payloads based on Time Spent Actively Viewing|

---

CA2741421A1|2008-10-28|2010-05-06|Norwell Sa|Audience measurement system|

---

US20100121676A1|2008-11-11|2010-05-13|Yahoo! Inc.|Method and system for logging impressions of online advertisments|

---

US8087041B2|2008-12-10|2011-12-27|Google Inc.|Estimating reach and frequency of advertisements|

---

US20100153175A1|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|

---

US8356247B2|2008-12-16|2013-01-15|Rich Media Worldwide, Llc|Content rendering control system and method|

---

US20100161385A1|2008-12-19|2010-06-24|Nxn Tech, Llc|Method and System for Content Based Demographics Prediction for Websites|

---

JP5626537B2|2009-01-15|2014-11-19|アーモンドネット インコーポレーテッドＡｌｍｏｎｄｎｅｔ，Ｉｎｃ．|Request offline profile data for online use in confidentiality|

---

WO2010082364A1|2009-01-16|2010-07-22|Telefonaktiebolaget L M Ericsson |Apparatus and method for advertising during login process|

---

JP2012516514A|2009-01-29|2012-07-19|ザニールセンカンパニー（ユーエス）エルエルシー|Method and apparatus for measuring market statistics|

---

US20100205057A1|2009-02-06|2010-08-12|Rodney Hook|Privacy-sensitive methods, systems, and media for targeting online advertisements using brand affinity modeling|

---

KR101168705B1|2009-02-18|2012-08-02|김기미|Customized and intellectual symbol, icon internet information searching system utilizing a mobile communication terminal and IP-based information terminal|

---

US10262337B2|2009-03-06|2019-04-16|AppNexus Inc.|Advertising platform transaction management|

---

CN101505247A|2009-03-09|2009-08-12|成都市华为赛门铁克科技有限公司|Detection method and apparatus for number of shared access hosts|

---

KR101073112B1|2009-03-11|2011-10-12|박상호|A management method for contents combined work and advertising using an open license and apparatus thereof|

---

US8150974B2|2009-03-17|2012-04-03|Kindsight, Inc.|Character differentiation system generating session fingerprint using events associated with subscriber ID and session ID|

---

US7882054B2|2009-03-19|2011-02-01|Gutman Levitan|System for estimating audience size in a digital broadcast environment using control packets and predictions|

---

US8266687B2|2009-03-27|2012-09-11|Sophos Plc|Discovery of the use of anonymizing proxies by analysis of HTTP cookies|

---

JP5492630B2|2009-03-31|2014-05-14|株式会社ビデオリサーチ|Content contact investigation system and content contact investigation method|

---

US20100268573A1|2009-04-17|2010-10-21|Anand Jain|System and method for utilizing supplemental audio beaconing in audience measurement|

---

US10008212B2|2009-04-17|2018-06-26|The Nielsen Company , Llc|System and method for utilizing audio encoding for measuring media exposure with environmental masking|

---

US20100268540A1|2009-04-17|2010-10-21|Taymoor Arshi|System and method for utilizing audio beaconing in audience measurement|

---

US8429287B2|2009-04-29|2013-04-23|Rangecast Technologies, Llc|Network audio distribution system and method|

---

US8990337B2|2009-06-08|2015-03-24|Collective, Inc.|Tracking advertising abandonment rates|

---

US20100313009A1|2009-06-09|2010-12-09|Jacques Combet|System and method to enabletracking of consumer behavior and activity|

---

US20100325051A1|2009-06-22|2010-12-23|Craig Stephen Etchegoyen|System and Method for Piracy Reduction in Software Activation|

---

WO2011005155A1|2009-07-08|2011-01-13|Telefonaktiebolaget Lm Ericsson |A method and arrangements for analysing multimedia content|

---

US9178634B2|2009-07-15|2015-11-03|Time Warner Cable Enterprises Llc|Methods and apparatus for evaluating an audience in a content-based network|

---

US8612860B2|2009-08-12|2013-12-17|Warner Music Inc.|Systems, methods, and media for coordinating the presentation of media with an event|

---

US20120192214A1|2009-12-22|2012-07-26|Resonate Networks|Method and apparatus for delivering targeted content to television viewers|

---

KR101118741B1|2009-08-31|2012-03-12|주식회사 나스미디어|A method for providing internet advertisement popularity rating|

---

US8285218B2|2009-08-31|2012-10-09|The Nielsen Company , Llc|Methods and apparatus to identify wireless carrier performance effects|

---

US8504411B1|2009-09-14|2013-08-06|Aol Advertising Inc.|Systems and methods for online user profiling and segmentation|

---

US20110087519A1|2009-10-09|2011-04-14|Visa U.S.A. Inc.|Systems and Methods for Panel Enhancement with Transaction Data|

---

US8595058B2|2009-10-15|2013-11-26|Visa U.S.A.|Systems and methods to match identifiers|

---

US8549552B2|2009-11-03|2013-10-01|The Nielsen Company , Llc|Methods and apparatus to monitor media exposure in vehicles|

---

US8566856B2|2009-12-01|2013-10-22|International Business Machines Corporation|Video stream measurement method and system|

---

US9390438B2|2009-12-08|2016-07-12|Comscore, Inc.|Systems and methods for capturing and reporting metrics regarding user engagement including a canvas model|

---

US20110153391A1|2009-12-21|2011-06-23|Michael Tenbrock|Peer-to-peer privacy panel for audience measurement|

---

US8925024B2|2009-12-31|2014-12-30|The Nielsen Company , Llc|Methods and apparatus to detect commercial advertisements associated with media presentations|

---

US20110246306A1|2010-01-29|2011-10-06|Bank Of America Corporation|Mobile location tracking integrated merchant offer program and customer shopping|

---

US20110191184A1|2010-01-29|2011-08-04|Bank Of America Corporation|Mobile location integrated merchant offer program and customer shopping|

---

US20110191664A1|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|2010-02-05|2011-08-11|Von Sydow Gustav|System and method for measuring effectiveness of electronically presented advertizing|

---

CA2789224C|2010-02-08|2017-09-05|Facebook, Inc.|Communicating information in a social network system about activities from another domain|

---

US8280844B2|2010-02-15|2012-10-02|Bank Of America Corporation|Anomalous activity detection|

---

US8799640B2|2010-02-27|2014-08-05|Novell, Inc.|Techniques for managing a secure communication session|

---

US20120310729A1|2010-03-16|2012-12-06|Dalto John H|Targeted learning in online advertising auction exchanges|

---

US9105053B2|2010-03-23|2015-08-11|Nokia Technologies Oy|Method and apparatus for determining a user age range|

---

WO2011123564A2|2010-03-31|2011-10-06|Mediamath, Inc.|Systems and methods for integration of a demand side platform|

---

US8626901B2|2010-04-05|2014-01-07|Comscore, Inc.|Measurements based on panel and census data|

---

US8307006B2|2010-06-30|2012-11-06|The Nielsen Company , Llc|Methods and apparatus to obtain anonymous audience measurement data from network server data for particular demographic and usage profiles|

---

US8484511B2|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|

---

US8321681B2|2010-07-19|2012-11-27|Google Inc.|Managing user accounts|

---

US8543518B2|2010-07-26|2013-09-24|Yahoo! Inc.|Deducing shadow user profiles for ad campaigns|

---

US9747605B2|2010-08-02|2017-08-29|Facebook, Inc.|Measuring quality of user interaction with third party content|

---

US20130210455A1|2010-08-10|2013-08-15|Telefonaktiebolaget L M Ericsson |Aggregating demographic distribution information|

---

US8886773B2|2010-08-14|2014-11-11|The Nielsen Company , Llc|Systems, methods, and apparatus to monitor mobile internet activity|

---

AU2013203898B2|2010-09-22|2015-07-02|The Nielsen Company , Llc|Methods and apparatus to determine impressions using distributed demographic information|

---

US8713168B2|2010-09-22|2014-04-29|The Nielsen Company , Llc|Methods and apparatus to determine impressions using distributed demographic information|

---

US9092797B2|2010-09-22|2015-07-28|The Nielsen Company , Llc|Methods and apparatus to analyze and adjust demographic information|

---

US8549103B2|2010-10-07|2013-10-01|Yahoo! Inc.|Multisided audience-related hybrid measurements|

---

US9122760B2|2010-10-12|2015-09-01|Robert Osann, Jr.|User preference correlation for web-based selection|

---

JP5674414B2|2010-10-27|2015-02-25|株式会社ビデオリサーチ|Access log matching system and access log matching method|

---

US8484241B2|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|

---

US8495143B2|2010-10-29|2013-07-23|Facebook, Inc.|Inferring user profile attributes from social information|

---

US9558502B2|2010-11-04|2017-01-31|Visa International Service Association|Systems and methods to reward user interactions|

---

US20120116873A1|2010-11-05|2012-05-10|Revnetics, Inc.|Network Traffic Redirection And Conversion Tracking|

---

US8909792B2|2010-11-12|2014-12-09|Socialware, Inc.|Method, system, and computer program product for identifying and tracking social identities|

---

US8631122B2|2010-11-29|2014-01-14|Viralheat, Inc.|Determining demographics based on user interaction|

---

US20120143713A1|2010-12-06|2012-06-07|Campaigngrid, Llc|Electronic and network-based franking|

---

US8453173B1|2010-12-13|2013-05-28|Google Inc.|Estimating demographic compositions of television audiences from audience similarities|

---

US9497154B2|2010-12-13|2016-11-15|Facebook, Inc.|Measuring social network-based interaction with web content external to a social networking system|

---

US20120151079A1|2010-12-13|2012-06-14|Jan Besehanic|Methods and apparatus to measure media exposure|

---

WO2012087954A2|2010-12-20|2012-06-28|The Nielsen Company , Llc|Methods and apparatus to determine media impressions using distributed demographic information|

---

US8874639B2|2010-12-22|2014-10-28|Facebook, Inc.|Determining advertising effectiveness outside of a social networking system|

---

US20120173701A1|2010-12-30|2012-07-05|Arbitron Inc.|Matching techniques for cross-platform monitoring and information|

---

US20120185274A1|2011-01-14|2012-07-19|Guzihou Hu|System and Method for Predicting Inner Age|

---

US20120209920A1|2011-02-10|2012-08-16|Microsoft Corporation|Social influencers discovery|

---

US20120206331A1|2011-02-14|2012-08-16|Gandhi Sidhant D|Methods and Systems for Supporting Gesture Recognition Applications across Devices|

---

US8543454B2|2011-02-18|2013-09-24|Bluefin Labs, Inc.|Generating audience response metrics and ratings from social interest in time-based media|

---

EP2686779A4|2011-03-18|2014-09-17|Nielsen Co Us Llc|Methods and apparatus to determine media impressions|

---

US8984547B2|2011-04-11|2015-03-17|Google Inc.|Estimating demographic compositions of television audiences|

---

US20120265606A1|2011-04-14|2012-10-18|Patnode Michael L|System and method for obtaining consumer information|

---

US8315620B1|2011-05-27|2012-11-20|The Nielsen Company , Llc|Methods and apparatus to associate a mobile device with a panelist profile|

---

US9282158B2|2011-06-06|2016-03-08|Google Inc.|Reducing redirects|

---

US8560683B2|2011-06-10|2013-10-15|Google Inc.|Video and site analytics|

---

US9210208B2|2011-06-21|2015-12-08|The Nielsen Company , Llc|Monitoring streaming media content|

---

US8688524B1|2011-06-28|2014-04-01|Amazon Technologies, Inc.|Tracking online impressions to offline purchases|

---

US8635674B2|2011-07-06|2014-01-21|Symphony Advanced Media|Social content monitoring platform methods|

---

US8498491B1|2011-08-10|2013-07-30|Google Inc.|Estimating age using multiple classifiers|

---

US10783547B2|2011-08-17|2020-09-22|Facebook, Inc.|Approximating unique advertisement impressions on a social networking system|

---

US20130060629A1|2011-09-07|2013-03-07|Joshua Rangsikitpho|Optimization of Content Placement|

---

JP2013057918A|2011-09-09|2013-03-28|Shigeto Umeda|System for displaying and bidding for variable-length advertisement|

---

US8909771B2|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|2011-09-23|2013-03-28|Jonathan Goldman|Per-view charging for video advertisements|

---

US9131355B2|2011-09-30|2015-09-08|Cbs Interactive Inc.|System and method of configuring operations of communication services|

---

US20130124628A1|2011-11-15|2013-05-16|Srilal Weerasinghe|Method and apparatus for providing social network based advertising with user control and privacy|

---

WO2013078640A1|2011-11-30|2013-06-06|Google Inc.|Estimating user demographics|

---

US9331975B2|2011-12-16|2016-05-03|The Nielsen Company , Llc|Systems, methods, and apparatus to identify media presentation devices|

---

US9224094B2|2012-01-26|2015-12-29|The Nielsen Company , Llc|Systems, methods, and articles of manufacture to measure online audiences|

---

US8600796B1|2012-01-30|2013-12-03|Bazaarvoice, Inc.|System, method and computer program product for identifying products associated with polarized sentiments|

---

US20130204694A1|2012-02-07|2013-08-08|Sayso, Llc|Context-Based Study Generation and Administration|

---

US9015255B2|2012-02-14|2015-04-21|The Nielsen Company , Llc|Methods and apparatus to identify session users with cookie information|

---

US8973023B1|2012-02-29|2015-03-03|The Nielsen Company , Llc|Methods and apparatus to determine audience duplication in cross-media campaigns|

---

US9009258B2|2012-03-06|2015-04-14|Google Inc.|Providing content to a user across multiple devices|

---

US9659105B2|2012-03-15|2017-05-23|The Nielsen Company , Llc|Methods and apparatus to track web browsing sessions|

---

US9965767B2|2012-04-20|2018-05-08|Comscore, Inc.|Attribution of demographics to census data|

---

US20130331971A1|2012-06-10|2013-12-12|Eran Bida|Watermarking and using same for audience measurement|

---

AU2013204865B2|2012-06-11|2015-07-09|The Nielsen Company , Llc|Methods and apparatus to share online media impressions data|

---

US20130346172A1|2012-06-26|2013-12-26|Echoed, Inc.|Method and system for valuing and rewarding third party marketing of products via a social network|

---

US9430778B2|2012-07-30|2016-08-30|Kount Inc.|Authenticating users for accurate online audience measurement|

---

AU2013204953B2|2012-08-30|2016-09-08|The Nielsen Company , Llc|Methods and apparatus to collect distributed user information for media impressions|

---

US20140108130A1|2012-10-12|2014-04-17|Google Inc.|Calculating audience metrics for online campaigns|

---

US9621446B2|2012-10-26|2017-04-11|Comscore, Inc.|Combining measurements based on beacon data|

---

US9055021B2|2012-11-30|2015-06-09|The Nielsen Company , Llc|Methods and apparatus to monitor impressions of social media messages|

---

US20140164447A1|2012-12-12|2014-06-12|Akamai Technologies Inc.|Cookie synchronization and acceleration of third-party content in a web page|

---

US20150089354A1|2013-02-10|2015-03-26|Wixpress Ltd.|Third party application activity data collection|

---

US9858600B2|2013-03-15|2018-01-02|Turn Inc.|Universal tag for page analytics and campaign creation|

---

US20140324544A1|2013-04-26|2014-10-30|Paul Donato|Methods and apparatus to determine demographic distributions of online users|

---

US9519914B2|2013-04-30|2016-12-13|The Nielsen Company , Llc|Methods and apparatus to determine ratings information for online media presentations|

---

US20140337104A1|2013-05-09|2014-11-13|Steven J. Splaine|Methods and apparatus to determine impressions using distributed demographic information|

---

US8775332B1|2013-06-13|2014-07-08|InsideSales.com, Inc.|Adaptive user interfaces|

---

US10068246B2|2013-07-12|2018-09-04|The Nielsen Company , Llc|Methods and apparatus to collect distributed user information for media impressions|

---

US9313294B2|2013-08-12|2016-04-12|The Nielsen Company , Llc|Methods and apparatus to de-duplicate impression information|

---

US9852163B2|2013-12-30|2017-12-26|The Nielsen Company , Llc|Methods and apparatus to de-duplicate impression information|

---

US9237138B2|2013-12-31|2016-01-12|The Nielsen Company , Llc|Methods and apparatus to collect distributed user information for media impressions and search terms|

---

US20150193816A1|2014-01-06|2015-07-09|The Nielsen Company , Llc|Methods and apparatus to correct misattributions of media impressions|

---

US8910195B1|2014-02-20|2014-12-09|Google Inc.|Systems and methods for enhancing audience measurement data|

---

KR101934841B1|2014-03-13|2019-01-03|더 닐슨 컴퍼니 엘엘씨|Methods and apparatus to compensate impression data for misattribution and/or non-coverage by a database proprietor|

---

US20160275548A1|2015-03-16|2016-09-22|Facebook, Inc.|Integrating advertisement impressions with user identity for search advertisements|

---

US20160359989A1|2015-06-02|2016-12-08|UserIQ, Inc.|Recording And Triggering Web And Native Mobile Application Events With Mapped Data Fields|US9092797B2|2010-09-22|2015-07-28|The Nielsen Company , Llc|Methods and apparatus to analyze and adjust demographic information|

---

US8713168B2|2010-09-22|2014-04-29|The Nielsen Company , Llc|Methods and apparatus to determine impressions using distributed demographic information|

---

WO2012087954A2|2010-12-20|2012-06-28|The Nielsen Company , Llc|Methods and apparatus to determine media impressions using distributed demographic information|

---

EP2686779A4|2011-03-18|2014-09-17|Nielsen Co Us Llc|Methods and apparatus to determine media impressions|

---

AU2013204865B2|2012-06-11|2015-07-09|The Nielsen Company , Llc|Methods and apparatus to share online media impressions data|

---

US9282366B2|2012-08-13|2016-03-08|The Nielsen Company , Llc|Methods and apparatus to communicate audience measurement information|

---

AU2013204953B2|2012-08-30|2016-09-08|The Nielsen Company , Llc|Methods and apparatus to collect distributed user information for media impressions|

---

US9055021B2|2012-11-30|2015-06-09|The Nielsen Company , Llc|Methods and apparatus to monitor impressions of social media messages|

---

WO2014116542A1|2013-01-22|2014-07-31|Tealium Inc.|Activation of dormant features in native applications|

---

US9832155B2|2013-01-31|2017-11-28|The Nielsen Company , Llc|Methods and apparatus to monitor impressions of social media messages|

---

US9697533B2|2013-04-17|2017-07-04|The Nielsen Company , Llc|Methods and apparatus to monitor media presentations|

---

US9519914B2|2013-04-30|2016-12-13|The Nielsen Company , Llc|Methods and apparatus to determine ratings information for online media presentations|

---

US10068246B2|2013-07-12|2018-09-04|The Nielsen Company , Llc|Methods and apparatus to collect distributed user information for media impressions|

---

US9313294B2|2013-08-12|2016-04-12|The Nielsen Company , Llc|Methods and apparatus to de-duplicate impression information|

---

US10333882B2|2013-08-28|2019-06-25|The Nielsen Company , Llc|Methods and apparatus to estimate demographics of users employing social media|

---

US20150066587A1|2013-08-30|2015-03-05|Tealium Inc.|Content site visitor processing system|

---

US8805946B1|2013-08-30|2014-08-12|Tealium Inc.|System and method for combining content site visitor profiles|

---

US9332035B2|2013-10-10|2016-05-03|The Nielsen Company , Llc|Methods and apparatus to measure exposure to streaming media|

---

US9081789B2|2013-10-28|2015-07-14|Tealium Inc.|System for prefetching digital tags|

---

WO2015069659A1|2013-11-05|2015-05-14|Tealium Inc.|Universal visitor identification system|

---

WO2015099824A2|2013-12-23|2015-07-02|The Nielsen Company , Llc|Methods and apparatus to measure media using media object characteristics|

---

US10956947B2|2013-12-23|2021-03-23|The Nielsen Company , Llc|Methods and apparatus to measure media using media object characteristics|

---

US9852163B2|2013-12-30|2017-12-26|The Nielsen Company , Llc|Methods and apparatus to de-duplicate impression information|

---

US9237138B2|2013-12-31|2016-01-12|The Nielsen Company , Llc|Methods and apparatus to collect distributed user information for media impressions and search terms|

---

US20150193816A1|2014-01-06|2015-07-09|The Nielsen Company , Llc|Methods and apparatus to correct misattributions of media impressions|

---

US10147114B2|2014-01-06|2018-12-04|The Nielsen Company , Llc|Methods and apparatus to correct audience measurement data|

---

US10679242B2|2014-01-29|2020-06-09|IPSOS America, Inc.|Methods and systems for conducting ad research|

---

US8910195B1|2014-02-20|2014-12-09|Google Inc.|Systems and methods for enhancing audience measurement data|

---

US9953330B2|2014-03-13|2018-04-24|The Nielsen Company , Llc|Methods, apparatus and computer readable media to generate electronic mobile measurement census data|

---

KR101934841B1|2014-03-13|2019-01-03|더 닐슨 컴퍼니엘엘씨|Methods and apparatus to compensate impression data for misattribution and/or non-coverage by a database proprietor|

---

US9288256B2|2014-04-11|2016-03-15|Ensighten, Inc.|URL prefetching|

---

US9699499B2|2014-04-30|2017-07-04|The Nielsen Company , Llc|Methods and apparatus to measure exposure to streaming media|

---

US10311464B2|2014-07-17|2019-06-04|The Nielsen Company , Llc|Methods and apparatus to determine impressions corresponding to market segments|

---

US9402111B2|2014-09-17|2016-07-26|Ispot.Tv, Inc.|Television audience measurement method and apparatus|

---

US10652127B2|2014-10-03|2020-05-12|The Nielsen Company , Llc|Fusing online media monitoring data with secondary online data feeds to generate ratings data for online media exposure|

---

US9537964B2|2015-03-11|2017-01-03|Tealium Inc.|System and method for separating content site visitor profiles|

---

US10169778B1|2015-03-26|2019-01-01|Amazon Technologies, Inc.|Cross-channel online advertising attribution|

---

US10977685B1|2015-04-30|2021-04-13|Amazon Technologies, Inc.|Identity resolution service|

---

US9870486B2|2015-05-28|2018-01-16|The Nielsen Company , Llc|Methods and apparatus to assign demographic information to panelists|

---

US10380633B2|2015-07-02|2019-08-13|The Nielsen Company , Llc|Methods and apparatus to generate corrected online audience measurement data|

---

US10045082B2|2015-07-02|2018-08-07|The Nielsen Company , Llc|Methods and apparatus to correct errors in audience measurements for media accessed using over-the-top devices|

---

US9838754B2|2015-09-01|2017-12-05|The Nielsen Company , Llc|On-site measurement of over the top media|

---

US10332158B2|2015-09-24|2019-06-25|The Nielsen Company , Llc|Methods and apparatus to adjust media impressions based on media impression notification loss rates in network communications|

---

US20170091794A1|2015-09-25|2017-03-30|The Nielsen Company , Llc|Methods and apparatus to determine ratings data from population sample data having unreliable demographic classifications|

---

CN105306542B|2015-09-25|2018-12-14|北京奇艺世纪科技有限公司|A kind of system for integrating web service|

---

JP6636143B2|2015-10-07|2020-01-29|エックスアド インコーポレーテッドＸａｄ，Ｉｎｃ．|Method and apparatus for measuring the effect of information delivered to a mobile device|

---

US10205994B2|2015-12-17|2019-02-12|The Nielsen Company , Llc|Methods and apparatus to collect distributed user information for media impressions|

---

US10045057B2|2015-12-23|2018-08-07|The Nielsen Company , Llc|Methods and apparatus to generate audience measurement data from population sample data having incomplete demographic classifications|

---

CN106919595B|2015-12-25|2020-10-13|阿里巴巴集团控股有限公司|Cookie mapping method and device and electronic equipment|

---

US10270673B1|2016-01-27|2019-04-23|The Nielsen Company , Llc|Methods and apparatus for estimating total unique audiences|

---

US9872072B2|2016-03-21|2018-01-16|Google Llc|Systems and methods for identifying non-canonical sessions|

---

US10834449B2|2016-12-31|2020-11-10|The Nielsen Company , Llc|Methods and apparatus to associate audience members with over-the-top device media impressions|

---

US20190245935A1|2018-02-07|2019-08-08|The Nielsen Company , Llc|Methods and apparatus to create opportunistic network of iot collaboration agents to collect data from mobile devices|

---

US20190289085A1|2018-03-13|2019-09-19|Indigenous Software, Inc.|System and method for tracking online user behavior across browsers or devices|

---

US11146911B2|2018-08-17|2021-10-12|xAd, Inc.|Systems and methods for pacing information campaigns based on predicted and observed location events|

---

US11115479B2|2019-01-10|2021-09-07|Google Llc|Enhanced online privacy|

---

US11146656B2|2019-12-20|2021-10-12|Tealium Inc.|Feature activation control and data prefetching with network-connected mobile devices|

---

US11184444B1|2020-07-27|2021-11-23|International Business Machines Corporation|Network traffic reduction by server-controlled cookie selection|

法律状态:
2018-12-04| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|

---

2020-01-21| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201261658233P| true| 2012-06-11|2012-06-11|

---

US61/658,233|2012-06-11|

---

US201361810235P| true| 2013-04-09|2013-04-09|

---

US61/810,235|2013-04-09|

---

AU2013204865|2013-04-12|

---

AU2013204865A|AU2013204865B2|2012-06-11|2013-04-12|Methods and apparatus to share online media impressions data|

---

PCT/US2013/045211|WO2013188429A2|2012-06-11|2013-06-11|Methods and apparatus to share online media impressions data|

---