Methods and apparatus to determine demographic classifications for census level impression counts and unique audience sizes
US-2023096891-A1 · Mar 30, 2023 · US
US12294764B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12294764-B2 |
| Application number | US-202218051291-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 31, 2022 |
| Priority date | Oct 31, 2022 |
| Publication date | May 6, 2025 |
| Grant date | May 6, 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, systems, and articles of manufacture to identify inconsistencies in audience measurement data are disclosed. Example apparatus disclosed herein are to compare ones of a first set of cumulative audience metrics with one or more limits based on a second set of event-level audience metrics to detect an inconsistency in at least one of the first set of cumulative audience metrics or the second set of event-level audience metrics. Disclosed example apparatus are further to generate a report of the inconsistency in the at least one of the first set of event-level audience metrics or the second set of cumulative audience metrics.
Opening claim text (preview).
What is claimed is: 1. A computing system comprising: a processor; and a non-transitory computer-readable storage medium, having stored thereon program instructions that, upon execution by the processor, cause performance of a set of operations comprising: obtaining, at a server associated with an audience measurement entity, audience measurement data corresponding to a plurality of media devices; determining, using the audience measurement data, a set of cumulative audience metrics and a set of event-level audience metrics, wherein the set of event-level audience metrics corresponds to metrics associated with media impressions corresponding respectively to a series of events, and wherein the set of cumulative audience metrics corresponds to metrics associated with a cumulative number of unique users having accessed media at the same series of events; comparing ones of the set of cumulative audience metrics with one or more limits based on the set of event-level audience metrics at a corresponding event of the series of events to detect one or more inconsistencies in at least one of the set of cumulative audience metrics or the set of event-level audience metrics; detecting an inconsistency of the one or more inconsistencies based on a difference between a first cumulative audience metric of the set of cumulative audience metrics and a second cumulative audience metric of the set of cumulative audience metrics being greater than an event-level audience metric of the set of event-level audience metrics associated with a target event of the series of events, wherein the first cumulative audience metric is associated with the target event, and wherein the second cumulative audience metric is associated with a preceding event relative to the target event; and causing, in response to detecting the inconsistency of the one or more inconsistencies, the server of the audience measurement entity to stop processing the audience measurement data thereby reducing computational resources associated with the server processing the audience measurement data. 2. The computing system of claim 1 , wherein the set of operations further comprise detecting another inconsistency of the one or more inconsistencies in response to a third cumulative audience metric of the set of cumulative audience metrics associated with the target event being greater than a largest event-level audience metric of the set of event-level audience metrics. 3. The computing system of claim 1 , wherein the set of operations further comprise detecting another inconsistency of the one or more inconsistencies in response to a third cumulative audience metric of the set of cumulative audience metrics associated with the target event being greater than a limit. 4. The computing system of claim 3 , wherein the limit corresponds to a smaller of (i) a sum of event-level audience metrics associated with events ranging from an initial event to the target event in the set of event-level audience metrics or (ii) a universe estimate of a population. 5. The computing system of claim 4 , wherein the universe estimate of the population is an estimate of a total audience that could be exposed to a particular media. 6. The computing system of claim 1 , wherein the set of operations further comprise detecting another inconsistency of the one or more inconsistencies in response to a third cumulative audience metric of the set of cumulative audience metrics associated with the target event being less than a fourth cumulative audience metric of the set of cumulative audience metrics associated with a preceding event relative to the target event. 7. The computing system of claim 1 , wherein the causing, in response to detecting the inconsistency of the one or more inconsistencies, the server of the audience measurement entity to stop processing the audience measurement data further comprises sending an instruction to an audience data provider to stop collecting the audience measurement data, wherein the audience measurement data is obtained from the audience data provider. 8. The computing system of claim 1 , wherein the set of operations further comprise triggering an alert based on the detecting the inconsistency. 9. The computing system of claim 8 , wherein the triggering the alert comprises transmitting the alert to a mobile device. 10. A non-transitory computer-readable storage medium, having stored thereon program instructions which, when executed, cause a processor to perform a set of operations: obtaining, at a server associated with an audience measurement entity, audience measurement data corresponding to a plurality of media devices; determining, using the audience measurement data, a set of cumulative audience metrics and a set of event-level audience metrics, wherein the set of event-level audience metrics corresponds to metrics associated with media impressions corresponding respectively to a series of events, and wherein the set of cumulative audience metrics corresponds to metrics associated with a cumulative number of unique users having accessed media at the same series of events; comparing ones of the set of cumulative audience metrics with one or more limits based on the set of event-level audience metrics at a corresponding event of the series of events to detect one or more inconsistencies in at least one of the set of cumulative audience metrics or the set of event-level audience metrics; detecting an inconsistency of the one or more inconsistencies based on a difference between a first cumulative audience metric of the set of cumulative audience metrics and a second cumulative audience metric of the set of cumulative audience metrics being greater than an event-level audience metric of the set of event-level audience metrics associated with a target event of the series of events, wherein the first cumulative audience metric is associated with the target event, and wherein the second cumulative audience metric is associated with a preceding event relative to the target event; generating, after the detecting, a report of the inconsistency of the one or more inconsistencies; and causing, in response to detecting the inconsistency of the one or more inconsistencies, the server of the audience measurement entity to stop processing the audience measurement data thereby reducing computational resources associated with the server processing the audience measurement data. 11. The non-transitory computer-readable storage medium of claim 10 , wherein the set of operations further comprise detecting another inconsistency of the one or more inconsistencies in response to a third cumulative audience metric of the set of cumulative audience metrics associated with the target event being less than a largest event-level audience metric of the set of event-level audience metrics. 12. The non-transitory computer-readable storage medium of claim 10 , wherein the set of operations further comprise detecting another inconsistency of the one or more inconsistencies in response to a third cumulative audience metric of the set of cumulative audience metrics associated with the target event being greater than a limit. 13. The non-transitory computer-readable storage medium of claim 12 , wherein the limit corresponds to a smaller of (i) a sum of event-level audience metrics associated with events ranging from an initial event to the target event in the set of event-level audience metrics or (ii) a universe estimate of a population. 14. The non-transitory computer-readable storage medium of claim 10 , wherein the set of operations further comprise detecting another inconsistency of the one or
Management of end-user data (customer care in data networks H04L41/5077) · CPC title
Data stored in the client, e.g. viewing habits, hardware capabilities, credit card number (arrangements where receivers interact with the broadcast H04H20/38) · CPC title
Processing of monitored end-user data, e.g. trend analysis based on the log file of viewer selections · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.