Using hashed media identifiers to determine audience measurement data including demographic data from third party providers
US-2016148232-A1 · May 26, 2016 · US
US12437311B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12437311-B2 |
| Application number | US-202318364888-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 3, 2023 |
| Priority date | Jan 29, 2015 |
| Publication date | Oct 7, 2025 |
| Grant date | Oct 7, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods, apparatus, and systems are disclosed to collect impressions associated with over-the-top media devices. An example apparatus includes memory; and at least one processor to execute instructions to access a first request, the first request from a user-controlled client device, the first request including an over-the-top device identifier that identifies an over-the-top device that presents media, in response to determining a user of the user-controlled client device is a panelist of a first server, store the over-the-top device identifier with demographics corresponding to the panelist, access a second request, the second request from the over-the-top device, the second request including the over-the-top device identifier and a media identifier, and log an impression associated with the media identifier and the demographics, the impression corresponding to the panelist of the first server.
Opening claim text (preview).
What is claimed is: 1. A computing system operated by an audience measurement entity (AME) and comprising a processor and a memory, the computing system configured to perform a set of acts comprising: receiving, from a client device of an audience member, a first beacon request including a device identifier of an over-the-top (OTT) device of the audience member and an AME cookie, wherein the client device executing beacon instructions embedded in a registration website causes the client device to generate the first beacon request, wherein the client device accesses the registration website to register the OTT device; sending, to the client device, a beacon response including a redirect request, wherein the redirect request specifies a mapping identifier for the OTT device, different from the device identifier of the OTT device, and instructs the client device to send to a database proprietor computing system a second beacon request including the mapping identifier and a database proprietor cookie, wherein the mapping identifier comprises a hashed version of the device identifier, wherein the mapping identifier is different from the AME cookie, wherein the database proprietor computing system is operated by a data enrichment provider that sets cookies, including the database proprietor cookie, on client devices of subscribers to enable the database proprietor computing system to identify demographic information of the subscribers, wherein the cookies that the data enrichment provider sets are inaccessible to the audience measurement entity outside of a Internet domain of the data enrichment provider, wherein the database proprietor computing system uses the database proprietor cookie to identify the demographic information, and wherein sending the second beacon request including the mapping identifier obfuscates the device identifier of the OTT device from the database proprietor computing system; receiving, from the database proprietor computing system, a demographics share communication associating the mapping identifier with demographic information corresponding to the audience member; and using the mapping identifier to associate the demographic information with the device identifier of the OTT device. 2. The method of claim 1 , wherein the client device is separate from the OTT device. 3. The computing system of claim 1 , wherein the set of acts further comprises: storing the mapping identifier in a mapping table in association with the device identifier of the OTT device, and using the mapping identifier to associate the demographic information with the device identifier of the OTT device comprises storing the demographic information in the mapping table in association with the device identifier of the OTT device. 4. The computing system of claim 1 , wherein the set of acts further comprises: collecting a media impression indicative of media accessed by the OTT device, the media impression including the device identifier of the OTT device; and based on the demographic information associated with the device identifier of the OTT device, logging the media impression in association with the demographic information. 5. The computing system of claim 1 , wherein the database proprietor computing system sets the database proprietor cookie on the client device. 6. The computing system of claim 1 , wherein the device identifier comprises one or more of identification information for the OTT device stored in an HTML5 datastore, an international mobile equipment identity (IMEI), or a mobile equipment identifier (MEID), or a media access control (MAC). 7. The computing system of claim 1 , wherein the client device sends the first beacon request to the computing system using a hypertext transfer protocol request or a hypertext transfer protocol secure request. 8. The computing system of claim 1 , wherein the redirect request further instructs the client device to send to a second database proprietor computing system a third beacon request including the mapping identifier and a second database proprietor cookie, and wherein the client device sending the second beacon request and the third beacon request comprises the client device sending the second beacon request and the third beacon request in parallel or sequentially. 9. A method comprising: receiving, by a computing system operated by an audience measurement entity (AME), from a client device of an audience member, a first beacon request including a device identifier of an over-the-top (OTT) device of the audience member and an AME cookie, wherein the client device executing beacon instructions embedded in a registration website causes the client device to generate the first beacon request, wherein the client device accesses the registration website to register the OTT device; sending, by the computing system to the client device, a beacon response including a redirect request, wherein the redirect request specifies a mapping identifier for the OTT device, different from the device identifier of the OTT device, and instructs the client device to send to a database proprietor computing system a second beacon request including the mapping identifier and a database proprietor cookie, wherein the mapping identifier comprises a hashed version of the device identifier, wherein the mapping identifier is different from the AME cookie, wherein the database proprietor computing system is operated by a data enrichment provider that sets cookies, including the database proprietor cookie, on client devices of subscribers to enable the database proprietor computing system to identify demographic information of the subscribers, wherein the cookies that the data enrichment provider sets are inaccessible to the audience measurement entity outside of an Internet domain of the data enrichment provider, wherein the database proprietor computing system uses the database proprietor cookie to identify the demographic information, and wherein sending the second beacon request including the mapping identifier obfuscates the device identifier of the OTT device from the database proprietor computing system; receiving, by the computing system from the database proprietor computing system, a demographics share communication associating the mapping identifier with demographic information corresponding to the audience member; and using, by the computing system, the mapping identifier to associate the demographic information with the device identifier of the OTT device. 10. The method of claim 9 , wherein the client device is separate from the OTT device. 11. The method of claim 9 , further comprising: storing the mapping identifier in a mapping table in association with the device identifier of the OTT device, and using the mapping identifier to associate the demographic information with the device identifier of the OTT device comprises storing the demographic information in the mapping table in association with the device identifier of the OTT device. 12. The method of claim 9 , further comprising: collecting a media impression indicative of media accessed by the OTT device, the media impression including the device identifier of the OTT device; and based on the demographic information associated with the device identifier of the OTT device, logging the media impression in association with the demographic information. 13. The method of claim 9 , wherein the device identifier comprises one or more of identification information for the OTT device stored in an HTML5 datastore, an international mobile equipment identity (IMEI), or a mobile equipment identifier (MEID), or a media access control (MAC). 14. The method o
Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34) · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Market modelling; Market analysis; Collecting market data · CPC title
Market segmentation · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.