[
 {
  "id": "IDN-A-F01",
  "headline": false,
  "claim": "IAB Tech Lab added EID provenance attributes for who inserted or bridged an ID and the match method in OpenRTB 2.6.",
  "chapter": "2, 4",
  "source_ids": [
   "IDN-A-S02",
   "IDN-A-S01"
  ],
  "passage": "[IDN-A-S02, September 23, 2024 update, fourth bullet] New attributes (inserter, matcher, mm) [IDN-A-S01, §3.2.27 EID, mm row] Match method used by the",
  "support": [
   {
    "source_id": "IDN-A-S02",
    "passage": "New attributes (inserter, matcher, mm)",
    "locator": "September 23, 2024 update, fourth bullet"
   },
   {
    "source_id": "IDN-A-S01",
    "passage": "Match method used by the",
    "locator": "§3.2.27 EID, mm row"
   }
  ],
  "scope_time": "2024-09-23 announcement; specification read 2026-11-11",
  "scope_geo": "Cross-market specification",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The September 23, 2024 IAB Tech Lab change notice names inserter, matcher and mm. OpenRTB 2.6 §3.2.27 gives their definitions, separates source from inserter, and permits a missing matcher in specified cases. They describe ID provenance when provided. Neither source shows a completed transaction. The September 2024 additions are optional provenance fields. Do not code observed transmission from the schema.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "The record describes the interface; actual use and enforcement depend on implementation.",
  "final_wording": "IAB Tech Lab added EID provenance attributes for who inserted or bridged an ID and the match method in OpenRTB 2.6.",
  "counterevidence": "The record describes the interface; actual use and enforcement depend on implementation.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F02",
  "headline": false,
  "claim": "GPP is designed to carry privacy and choice signals from sites and apps to ad-tech providers across supported jurisdictions.",
  "chapter": "2, 4",
  "source_ids": [
   "IDN-A-S03"
  ],
  "passage": "transmission of privacy, consent, and consumer choice signals from sites and apps to ad tech providers",
  "support": [
   {
    "source_id": "IDN-A-S03",
    "passage": "transmission of privacy, consent, and consumer choice signals from sites and apps to ad tech providers",
    "locator": "About the Global Privacy Protocol, paragraph 2"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "US and supported international jurisdictions",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The GPP overview describes transmission of privacy, consent and consumer-choice signals to ad-tech providers across supported frameworks. Its list includes the US national and state sections and European and Canadian TCF. Conveying a string does not establish the receiver’s conduct.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "The record describes the interface; actual use and enforcement depend on implementation.",
  "final_wording": "GPP is designed to carry privacy and choice signals from sites and apps to ad-tech providers across supported jurisdictions.",
  "counterevidence": "The record describes the interface; actual use and enforcement depend on implementation.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F03",
  "headline": false,
  "claim": "IAB Europe says newly created TC strings lacking the disclosed-vendor segment are invalid from March 1, 2026, while earlier strings can remain valid until users renew or change their choices.",
  "chapter": "2, 4",
  "source_ids": [
   "IDN-A-S04"
  ],
  "passage": "[IDN-A-S04, v2.3 key changes, validity of new TC strings] TC Strings created after 28 February 2026 without this segment will be considered invalid. [IDN-A-S04, Transition Timeline, paragraph on pre-March 2026 TC strings] will remain valid until they progressively get replaced",
  "support": [
   {
    "source_id": "IDN-A-S04",
    "passage": "TC Strings created after 28 February 2026 without this segment will be considered invalid.",
    "locator": "v2.3 key changes, validity of new TC strings"
   },
   {
    "source_id": "IDN-A-S04",
    "passage": "will remain valid until they progressively get replaced",
    "locator": "Transition Timeline, paragraph on pre-March 2026 TC strings"
   }
  ],
  "scope_time": "Transition effective 2026-03-01",
  "scope_geo": "Europe, participating TCF implementations",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "IAB Europe’s transition timeline says new strings created beginning March 1 require the disclosedVendors segment. Earlier strings without it remain valid until renewed or replaced. The vendor bit records whether the vendor was disclosed. It does not grant consent. A disclosure bit is distinct from a vendor-purpose consent bit.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "Disclosing a vendor does not on its own authorize every purpose. The transition did not retroactively invalidate all older strings.",
  "final_wording": "IAB Europe says newly created TC strings lacking the disclosed-vendor segment are invalid from March 1, 2026, while earlier strings can remain valid until users renew or change their choices.",
  "counterevidence": "Disclosing a vendor does not on its own authorize every purpose. The transition did not retroactively invalidate all older strings.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F04",
  "headline": false,
  "claim": "The September 2026 W3C Global Privacy Control Working Draft defines a signal sent through HTTP and the DOM to request that sites and services refrain from selling or sharing personal information.",
  "chapter": "2, 4",
  "source_ids": [
   "IDN-A-S05"
  ],
  "passage": "signal, transmitted over HTTP and through the DOM, that conveys a person's request",
  "support": [
   {
    "source_id": "IDN-A-S05",
    "passage": "signal, transmitted over HTTP and through the DOM, that conveys a person's request",
    "locator": "Abstract; Status of This Document"
   }
  ],
  "scope_time": "Working Draft 2026-09-24",
  "scope_geo": "Cross-market specification",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The abstract and specification define an HTTP signal and a DOM property conveying a preference on selling or sharing personal information. The September 24 document is explicitly a Working Draft. The applicable jurisdiction determines the effect of a signal.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "The record describes the interface; actual use and enforcement depend on implementation.",
  "final_wording": "The September 2026 W3C Global Privacy Control Working Draft defines a signal sent through HTTP and the DOM to request that sites and services refrain from selling or sharing personal information.",
  "counterevidence": "The record describes the interface; actual use and enforcement depend on implementation.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F05",
  "headline": false,
  "claim": "From Prebid.js 11.14, a configured TCF or GPP CMP lookup failure prevents user-ID retrieval and inclusion in bids; a timeout follows a different path using the consent data then available.",
  "chapter": "2, 4",
  "source_ids": [
   "IDN-A-S06",
   "IDN-AV-S01"
  ],
  "passage": "no IDs are retrieved and none are added to bid requests. A CMP timeout is not treated as a failure",
  "support": [
   {
    "source_id": "IDN-A-S06",
    "passage": "no IDs are retrieved and none are added to bid requests. A CMP timeout is not treated as a failure",
    "locator": "User ID, GDPR, Permissions, and Opt-Out, since Prebid.js 11.14"
   }
  ],
  "scope_time": "From Prebid.js 11.14, as documented at cutoff",
  "scope_geo": "Cross-market specification",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "The 11.14.0 release record confirms that userId does not run when an expected CMP cannot be found. The User ID module guide also covers CMP error responses and distinguishes a timeout: the submodules then run using the consent data available. The guarantee concerns IDs retrieved by these submodules, not every source of IDs in a bid request. A bid may carry an ID supplied by another route. Both the release record and current guide were checked.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "Publisher-side Prebid.js behavior. This case does not show what a DSP does with identifiers it previously received.",
  "final_wording": "From Prebid.js 11.14, user-ID submodules skip retrieval and add no IDs to bid requests when a configured TCF or GPP consent-platform lookup fails. On a timeout, the submodules run with the consent data available.",
  "counterevidence": "Publisher-side Prebid.js behavior. This case does not show what a DSP does with identifiers it previously received.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F06",
  "headline": false,
  "claim": "Prebid documents a publisher option that can require TCF Purpose 4 consent before passing user IDs and EIDs.",
  "chapter": "4",
  "source_ids": [
   "IDN-A-S07"
  ],
  "passage": "If true, user IDs and EIDs will not be shared without evidence of consent for TCF Purpose 4.",
  "support": [
   {
    "source_id": "IDN-A-S07",
    "passage": "If true, user IDs and EIDs will not be shared without evidence of consent for TCF Purpose 4.",
    "locator": "Page Integration, gdpr.rules[].eidsRequireP4Consent"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "TCF integration",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The personalizedAds rule exposes eidsRequireP4Consent. It defaults to false. When enabled, the rule ties transmission to Purpose 4, subject to configured enforcement and exceptions. The normal rule can check a purpose from 2 through 10. This is a published configuration option. Prebid.org is the source for the configuration it publishes. The direct record concerns the wrapper option, not independent evidence of deployment or legal compliance.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "The documented flag defaults to false. This option depends on configuration.",
  "final_wording": "Prebid documents a publisher option that can require TCF Purpose 4 consent before passing user IDs and EIDs.",
  "counterevidence": "The documented flag defaults to false. This option depends on configuration.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F07",
  "headline": false,
  "claim": "The UID2 operator describes a global opt-out route in which the portal sends the choice to the operator, publishers receive an opt-out response and DSPs receive a separate webhook.",
  "chapter": "2, 4",
  "source_ids": [
   "IDN-A-S08",
   "IDN-A-S09"
  ],
  "passage": "The UID2 Operator Service distributes information on all opted-out users to DSPs via a webhook provided for the purpose.",
  "support": [
   {
    "source_id": "IDN-A-S08",
    "passage": "The UID2 Operator Service distributes information on all opted-out users to DSPs via a webhook provided for the purpose.",
    "locator": "Opt-out workflow, steps 1–3 and participant table"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "UID2 ecosystem",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The UID2 guide distinguishes a single participant’s opt-out, which is not relayed to the operator, from portal opt-out for an email address or phone number. For the latter, token generation or refresh calls return the opt-out status and DSPs get webhook notifications. The guide acknowledges a propagation delay. A site-specific opt-out is not relayed to the operator; each email address or phone number needs its own portal opt-out.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "Technical instructions. The opt-out is propagated outside the individual bid request; refresh can introduce delay.",
  "final_wording": "UID2’s portal accepts an ecosystem opt-out for a supplied email address or phone number. Publishers learn the result when they generate or refresh a token, and the operator notifies DSPs through a separate webhook. Propagation can take time.",
  "counterevidence": "Technical instructions. The opt-out is propagated outside the individual bid request; refresh can introduce delay.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F08",
  "headline": false,
  "claim": "The UID2 DSP guide forbids using an opted-out UID2 in real-time bidding and allows the DSP to use another identifier or decline to bid.",
  "chapter": "2, 4",
  "source_ids": [
   "IDN-A-S09",
   "IDN-A-S08"
  ],
  "passage": "If the user has opted out, the UID2 must not be used for RTB.",
  "support": [
   {
    "source_id": "IDN-A-S09",
    "passage": "If the user has opted out, the UID2 must not be used for RTB.",
    "locator": "Honor user opt-outs, Bidding opt-out logic"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "DSPs integrating UID2",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The bidding section instructs a DSP that it may bid with an alternate identifier, or abstain, once a UID2 is opted out. The prohibition attaches to that UID2. The webhook and status endpoint describe how to learn the choice, with no published compliance rate. The reopened DSP guide’s last-modified timestamp is November 11, 2026. This is the document revision date; the origin date of its bidding rule is unestablished.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "This is the specified handling for UID2, not an observed buyer compliance rate or a platform-wide ban on bidding.",
  "final_wording": "The UID2 DSP guide forbids using an opted-out UID2 in real-time bidding and allows the DSP to use another identifier or decline to bid.",
  "counterevidence": "This is the specified handling for UID2, not an observed buyer compliance rate or a platform-wide ban on bidding.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F09",
  "headline": false,
  "claim": "ID5 says its Prebid Server Java module forwards available privacy signals to the ID5 API during identifier generation.",
  "chapter": "2, 4",
  "source_ids": [
   "IDN-A-S10"
  ],
  "passage": "The module forwards available privacy signals to the ID5 API, which honors them when generating an identifier:",
  "support": [
   {
    "source_id": "IDN-A-S10",
    "passage": "The module forwards available privacy signals to the ID5 API, which honors them when generating an identifier:",
    "locator": "Privacy & Data Sharing; list of TCF, US Privacy, COPPA and GPP fields"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "TCF and US privacy signal contexts",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "For the Java Prebid Server module, the ID5 guide specifies the available GDPR-applies flag and TCF string, US Privacy string, COPPA flag, and GPP string with section IDs sent to the ID5 API. Generating and adding the EID to selected bidder requests are distinct actions. Displayed ID5 guide timestamp October 15, 2026, 6:44 a.m. EDT. The route is Prebid Server Java, and existing ID5 EIDs skip a new fetch.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "Source-side integration instructions do not independently verify ID5’s enforcement.",
  "final_wording": "ID5 says its Prebid Server Java module forwards available privacy signals to the ID5 API during identifier generation.",
  "counterevidence": "Source-side integration instructions do not independently verify ID5’s enforcement.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F10",
  "headline": false,
  "claim": "ID5 describes its DSP decryption model as restricting access to platforms authorized under the consumer’s and publisher’s preferences.",
  "chapter": "4",
  "source_ids": [
   "IDN-A-S11"
  ],
  "passage": "only platforms that have authorization to process data (based on the consumer’s and publisher’s privacy preferences)",
  "support": [
   {
    "source_id": "IDN-A-S11",
    "passage": "only platforms that have authorization to process data (based on the consumer’s and publisher’s privacy preferences)",
    "locator": "Privacy & Regulations / Privacy-by-Design, paragraph beginning “When ID5 returns an ID to the page”"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "Cross-market specification",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "ID5 says it encrypts the ID and that only platforms authorized under consumer and publisher preferences can recover a stable ID. The operative passage is in Privacy & Regulations / Privacy-by-Design. The DSP guide links further decryption material behind a login; the public page describes the design, not actual decisions by a given DSP. Displayed guide timestamp November 25, 2025, 8:24 a.m. EST. The research locator should point to Privacy & Regulations / Privacy-by-Design; the decryption link itself requires login.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "Seller-described decryption design. An encryption statement alone cannot establish legal anonymity or an observed recipient action.",
  "final_wording": "ID5 describes its DSP decryption model as restricting access to platforms authorized under the consumer’s and publisher’s preferences.",
  "counterevidence": "Seller-described decryption design. An encryption statement alone cannot establish legal anonymity or an observed recipient action.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F11",
  "headline": false,
  "claim": "LiveRamp says its ATS JavaScript checks a US GPP National or fallback CCPA string and removes the stored RampID envelope when consent is rejected.",
  "chapter": "2, 4",
  "source_ids": [
   "IDN-A-S12"
  ],
  "passage": "[IDN-A-S12, Check for consent signal, US setting] a GPP National String or a CCPA Privacy String as a fallback. [IDN-A-S12, same bullet, rejected consent] remove the RampID envelope from the configured storage in the browser.",
  "support": [
   {
    "source_id": "IDN-A-S12",
    "passage": "a GPP National String or a CCPA Privacy String as a fallback.",
    "locator": "Check for consent signal, US setting"
   },
   {
    "source_id": "IDN-A-S12",
    "passage": "remove the RampID envelope from the configured storage in the browser.",
    "locator": "same bullet, rejected consent"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "US ATS.js",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The US Basic Requirements bullet describes the GPP National String with a CCPA Privacy String fallback. ATS.js removes the envelope from configured browser storage on rejection. The TCF v2.3-before-load rule in the same bullet applies to UK/EU users. The page records February 6, 2026 as last modified, not an original publication date.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "The cited behavior concerns browser storage. LiveRamp separately requires a TCF-compatible string for UK/EU users.",
  "final_wording": "LiveRamp says its ATS JavaScript checks a US GPP National or fallback CCPA string and removes the stored RampID envelope when consent is rejected.",
  "counterevidence": "The cited behavior concerns browser storage. LiveRamp separately requires a TCF-compatible string for UK/EU users.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F12",
  "headline": false,
  "claim": "Yahoo’s ConnectID toggle stores a domain-specific opt-out in local storage and stops its JavaScript module from generating identifiers when the opt-out flag is set.",
  "chapter": "2",
  "source_ids": [
   "IDN-A-S13"
  ],
  "passage": "the ConnectID JavaScript module will be disabled, preventing ConnectIDs from being generated.",
  "support": [
   {
    "source_id": "IDN-A-S13",
    "passage": "the ConnectID JavaScript module will be disabled, preventing ConnectIDs from being generated.",
    "locator": "Local storage toggle, connectIdOptOut value 1"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "Participating website",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The ConnectID guide says a domain-specific local storage entry with connectIdOptOut equal to 1 disables the publisher’s ConnectID JavaScript module. The claim covers generation on that domain. The page does not say the flag withdraws earlier IDs across the ecosystem.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "Yahoo documents local suppression. This source does not establish deletion at a downstream buyer.",
  "final_wording": "Yahoo’s ConnectID toggle stores a domain-specific opt-out in local storage and stops its JavaScript module from generating identifiers when the opt-out flag is set.",
  "counterevidence": "Yahoo documents local suppression. This source does not establish deletion at a downstream buyer.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F13",
  "headline": false,
  "claim": "Utiq documents a consenthub deactivation that prevents generation of its martechpass or adtechpass tokens.",
  "chapter": "",
  "source_ids": [
   "IDN-A-S14"
  ],
  "passage": "preventing the generation of martechpass or adtechpass tokens regardless of consent status.",
  "support": [
   {
    "source_id": "IDN-A-S14",
    "passage": "preventing the generation of martechpass or adtechpass tokens regardless of consent status.",
    "locator": "Utiq consent management overview, Deactivate Service / Prevent activation"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "Utiq participating sites; territory not assigned from this record",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The Utiq consent management table states that users can deactivate or prevent activation through consenthub, preventing martechpass/adtechpass generation whatever the consent status. Its separate revocation workflow documents site and consenthub handling of existing browser state.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "This describes future generation. US product eligibility is a separate question.",
  "final_wording": "Utiq documents a consenthub deactivation that prevents generation of its martechpass or adtechpass tokens.",
  "counterevidence": "This describes future generation. US product eligibility is a separate question.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F14",
  "headline": false,
  "claim": "Prebid describes the Lotame Panorama ID module sending the request’s IP address, user agent and timestamp to Lotame to generate an ID.",
  "chapter": "",
  "source_ids": [
   "IDN-A-S15"
  ],
  "passage": "sends the IP address, user agent, and timestamp from the request to Lotame",
  "support": [
   {
    "source_id": "IDN-A-S15",
    "passage": "sends the IP address, user agent, and timestamp from the request to Lotame",
    "locator": "Lotame Panorama ID overview"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "Cross-market specification",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The Lotame submodule page expressly identifies IP address, user agent and timestamp as request inputs sent to generate Panorama ID. It separately describes use of hashed emails and device/browser data in the broader graph. The page supplies no recipient refusal rule.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "Module documentation, not proof of a correct person match. The author previously worked at Lotame.",
  "final_wording": "Prebid describes the Lotame Panorama ID module sending the request’s IP address, user agent and timestamp to Lotame to generate an ID.",
  "counterevidence": "Module documentation, not proof of a correct person match. The author previously worked at Lotame.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F15",
  "headline": false,
  "claim": "Prebid’s Parrable integration guide says the module’s cookie holds the identifier and the user’s opt-out state.",
  "chapter": "2",
  "source_ids": [
   "IDN-A-S16"
  ],
  "passage": "containing the ID and optout states of the user.",
  "support": [
   {
    "source_id": "IDN-A-S16",
    "passage": "containing the ID and optout states of the user.",
    "locator": "Parrable ID Configuration, note on _parrable_id"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "Cross-market specification",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The Parrable integration guide says _parrable_id contains the identifier and the user’s opt-out state. It also describes changing encrypted values and partner configuration. A stored opt-out flag alone does not show receipt or enforcement by a downstream bidder.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "Storage of a choice cannot establish that a later recipient enforces it.",
  "final_wording": "Prebid’s Parrable integration guide says the module’s cookie holds the identifier and the user’s opt-out state.",
  "counterevidence": "Storage of a choice cannot establish that a later recipient enforces it.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F16",
  "headline": false,
  "claim": "Prebid names criteo.com as the EID source for the Criteo ID for Exchanges module.",
  "chapter": "2",
  "source_ids": [
   "IDN-A-S17"
  ],
  "passage": "criteo.com",
  "support": [
   {
    "source_id": "IDN-A-S17",
    "passage": "criteo.com",
    "locator": "Criteo ID for Exchanges, Module/EID Source table"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "Cross-market specification",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The module metadata table places criteo.com in the EID Source cell and criteoId in the bidRequest.userId cell. It refers specifically to Criteo ID for Exchanges. Its reference to the separate Direct Bidder does not establish equivalence with the OneTag seed. The source is a rendered two-cell table. The vertical bar in the research quote is table serialization, not literal prose; quote only the cell value when reproducing it.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "Verify the buyer-facing product boundary before linking to a OneTag seed; sharing an owner or a brand is insufficient.",
  "final_wording": "Prebid names criteo.com as the EID source for the Criteo ID for Exchanges module.",
  "counterevidence": "Verify the buyer-facing product boundary before linking to a OneTag seed; sharing an owner or a brand is insufficient.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F17",
  "headline": false,
  "claim": "Prebid describes SharedID as an ID stored in the publisher’s first-party domain and made available to adapters.",
  "chapter": "2, 4",
  "source_ids": [
   "IDN-A-S18",
   "IDN-A-S06"
  ],
  "passage": "stores an unique user id in the first party domain and makes it accessible to all adapters.",
  "support": [
   {
    "source_id": "IDN-A-S18",
    "passage": "stores an unique user id in the first party domain and makes it accessible to all adapters.",
    "locator": "SharedID overview"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "Cross-market specification",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Prebid describes SharedID as a locally stored UUID in the first-party domain and says supporting adapters can use it. Cookie and HTML5 options are documented. The general user-ID module allows publishers to select recipients, so adapter access here is capacity, not universal delivery.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "Adapter access does not establish receipt by every bidder, cross-device correctness or the recipient’s response to withdrawal.",
  "final_wording": "Prebid describes SharedID as an ID stored in the publisher’s first-party domain and made available to adapters.",
  "counterevidence": "Adapter access does not establish receipt by every bidder, cross-device correctness or the recipient’s response to withdrawal.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-A-F18",
  "headline": false,
  "claim": "IAB Tech Lab reports that Seller Defined Audiences was renamed Curated Audiences in December 2024.",
  "chapter": "2",
  "source_ids": [
   "IDN-A-S19"
  ],
  "passage": "In December 2024, Seller Defined Audiences was renamed",
  "support": [
   {
    "source_id": "IDN-A-S19",
    "passage": "In December 2024, Seller Defined Audiences was renamed",
    "locator": "Curated Audiences introduction"
   }
  ],
  "scope_time": "2024-12",
  "scope_geo": "Cross-market specification",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "IAB Tech Lab’s Curated Audiences page dates the change from Seller Defined Audiences to December 2024. It describes a seller audience classification approach without requiring cookie or mobile identifiers. The renaming, by itself, cannot show changes in deployments.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "A standards rename supplies no evidence that a particular commercial vendor retained a predecessor’s graph.",
  "final_wording": "IAB Tech Lab reports that Seller Defined Audiences was renamed Curated Audiences in December 2024.",
  "counterevidence": "A standards rename supplies no evidence that a particular commercial vendor retained a predecessor’s graph.",
  "stream": "A",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-B-F01",
  "headline": false,
  "claim": "Truthset reported a 13% mean across six data providers for IP-to-postal accuracy in its US operator-reference benchmark.",
  "chapter": "3, 7",
  "source_ids": [
   "IDN-B-S01",
   "IDN-B-S02"
  ],
  "passage": "[IDN-B-S01, Significant Variation Across Providers: IP-to-Postal] On average, across all providers, IP-to-postal linkages are accurate only 13% of the time [IDN-B-S02, Report introduction, second paragraph] commissioned jointly by CIMM and Go Addressable",
  "support": [
   {
    "source_id": "IDN-B-S01",
    "passage": "On average, across all providers, IP-to-postal linkages are accurate only 13% of the time",
    "locator": "Significant Variation Across Providers: IP-to-Postal"
   },
   {
    "source_id": "IDN-B-S02",
    "passage": "commissioned jointly by CIMM and Go Addressable",
    "locator": "Report introduction, second paragraph"
   }
  ],
  "scope_time": "2024-12-01 to 2025-02-28 for the operator reference and vendor inference sets.",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "commissioned_measurement",
  "review_outcome": "supported_with_qualification",
  "review_note": "Truthset scores provider-supplied IPv4/postal pairs with models calibrated against operator subscriber assignments. The study reports a 13% mean across six masked providers, with displayed provider results from 4% to 18%. The reference inputs came from two ISPs and one virtual pay-TV provider. The 938 million distinct pairs are scored candidate links. The report does not give a numerator and denominator of operator-confirmed hits over those pairs or the weights used in the reported mean.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The provider mean cannot be assigned to an IQ product. The report distinguishes the 938 million distinct provider IP-to-postal pairs from the much smaller operator reference; do not call 13% a share of all those pairs.",
  "final_wording": "In a US benchmark commissioned by CIMM and Go Addressable, Truthset reported average modeled IP-to-postal linkage accuracy of 13% across six unnamed providers for December 2024 through February 2025.",
  "counterevidence": "The provider mean cannot be assigned to an IQ product. The report distinguishes the 938 million distinct provider IP-to-postal pairs from the much smaller operator reference; do not call 13% a share of all those pairs.",
  "stream": "B",
  "study_id": "",
  "study_design": "Six masked providers. Two ISPs and one TV operator supplied reference records with lease times. Proprietary confidence-score method; no named product results or provider-level uncertainty supplied.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-B-F02",
  "headline": false,
  "claim": "Truthset reported a 16% mean IP-to-email accuracy across providers for the other linkage type in the same study.",
  "chapter": "3, 7",
  "source_ids": [
   "IDN-B-S01",
   "IDN-B-S02"
  ],
  "passage": "IP-to-email linkages are accurate, on average, 16% of the time",
  "support": [
   {
    "source_id": "IDN-B-S01",
    "passage": "IP-to-email linkages are accurate, on average, 16% of the time",
    "locator": "Results: IP Accuracy"
   }
  ],
  "scope_time": "2024-12-01 to 2025-02-28 for the operator reference and vendor inference sets.",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "commissioned_measurement",
  "review_outcome": "supported_with_qualification",
  "review_note": "Truthset also scores 5.6 billion distinct IP-to-email pairs from participating providers. Its mean is 16%, with provider results from 7% to 30%. Data Sources and Methodology Overview distinguish the scored inference set from sampled subscriber links. The unit is a pair consisting of an IP and email identifier. No admitted product is identified.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The email-link comparison has a separate denominator from the postal-link comparison. Neither measure tests the whole household graph.",
  "final_wording": "In the same December 2024 through February 2025 US benchmark, Truthset reported average modeled IP-to-email linkage accuracy of 16% across six unnamed providers.",
  "counterevidence": "The email-link comparison has a separate denominator from the postal-link comparison. Neither measure tests the whole household graph.",
  "stream": "B",
  "study_id": "",
  "study_design": "Same commissioned source, six masked providers. IP-to-email linkage pairs and operator reference records.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-B-F03",
  "headline": false,
  "claim": "CIMM’s comparative TV study reported that the post-match viewing profile skewed toward older, higher-income and heavier viewers.",
  "chapter": "3, 7",
  "source_ids": [
   "IDN-B-S03"
  ],
  "passage": "skews older, higher income, towards heavier TV viewers",
  "support": [
   {
    "source_id": "IDN-B-S03",
    "passage": "skews older, higher income, towards heavier TV viewers",
    "locator": "p. 3, Findings in Brief, Bias"
   }
  ],
  "scope_time": "TV input 2021-10-17 to 2021-10-29; study work 2021–2022",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "commissioned_measurement",
  "review_outcome": "supported_as_stated",
  "review_note": "The May 2023 report compares household profiles before and after matching two national TV datasets with five masked providers. It reports older and higher-income profiles and heavier viewing, especially in prime time and sports. TV data came from one ACR and one set-top-box source. The design measures the composition of retained households. The finding does not claim a measured person-link error rate.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "Five masked providers matched two TV sources. Sample composition can change even if every accepted link is correct.",
  "final_wording": "CIMM’s comparative TV study reported that the post-match viewing profile skewed toward older, higher-income and heavier viewers.",
  "counterevidence": "Five masked providers matched two TV sources. Sample composition can change even if every accepted link is correct.",
  "stream": "B",
  "study_id": "",
  "study_design": "Comparison of the input populations with post-match profiles; providers selected their own eligible households and matching identifiers.",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-B-F04",
  "headline": false,
  "claim": "The CIMM TV match study expressly lacked the independent validation data needed to test whether individual links were correct.",
  "chapter": "3, 7",
  "source_ids": [
   "IDN-B-S03"
  ],
  "passage": "requires an independent validation data set which was not available",
  "support": [
   {
    "source_id": "IDN-B-S03",
    "passage": "requires an independent validation data set which was not available",
    "locator": "p. 13, Match Rate Versus Match Accuracy"
   }
  ],
  "scope_time": "TV input 2021-10-17 to 2021-10-29; study work 2021–2022",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "commissioned_measurement",
  "review_outcome": "supported_as_stated",
  "review_note": "CIMM's page 13 explicitly says it assessed matching bias and lacked the independent validation data needed for match accuracy. Three matching steps incorporated TV records, Claritas household clusters and restaurant visits. Agreement among providers and post-match bias cannot identify whether each accepted link is true.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "Confine this limitation to the named 2023 study and the TV matching task.",
  "final_wording": "The CIMM TV match study expressly lacked the independent validation data needed to test whether individual links were correct.",
  "counterevidence": "Confine this limitation to the named 2023 study and the TV matching task.",
  "stream": "B",
  "study_id": "",
  "study_design": "Its three matching steps examined TV records, household demographics and visits; sampled pre/post populations, no independent truth labels.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-B-F05",
  "headline": false,
  "claim": "LiveRamp attributes a 95%–98.9% graph precision range to comScore in a note on deterministic matching.",
  "chapter": "3",
  "source_ids": [
   "IDN-B-S04"
  ],
  "passage": "LiveRamp’s graph was tested by comScore to have an industry leading 95%-98.9% precision",
  "support": [
   {
    "source_id": "IDN-B-S04",
    "passage": "LiveRamp’s graph was tested by comScore to have an industry leading 95%-98.9% precision",
    "locator": "Deterministic Matching, Note"
   }
  ],
  "scope_time": "Test period undisclosed; documentation read 2026-11-11",
  "scope_geo": "Test geography not disclosed in this note",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The LiveRamp note, last modified August 19, 2020, attributes 95%–98.9% precision to a comScore comparison with a panel of roughly 12 million verified devices and individuals. The range varies with sample quality. A named seller and tester are present. Panel size is not the number of accepted links used for either estimate; the tester's report, recruitment, funding, geography, tested service version and test dates are absent from these seller documents.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The note describes roughly 12 million verified devices and individuals. That panel size is not the published denominator of each precision estimate. Unknown independence, product version, window and geography.",
  "final_wording": "LiveRamp attributes a 95%–98.9% graph precision range to comScore in a note on deterministic matching.",
  "counterevidence": "The note describes roughly 12 million verified devices and individuals. That panel size is not the published denominator of each precision estimate. Unknown independence, product version, window and geography.",
  "stream": "B",
  "study_id": "",
  "study_design": "Seller summary of external test; acceptance denominator, labels, study funding and original report not established.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-B-F06",
  "headline": false,
  "claim": "Tapad reported that its Device Graph achieved twice the precision of the runner-up in a 2016 Hotels.com evaluation.",
  "chapter": "3",
  "source_ids": [
   "IDN-B-S05"
  ],
  "passage": "Tapad achieved twice the precision of the next highest-scoring cross-screen offering",
  "support": [
   {
    "source_id": "IDN-B-S05",
    "passage": "Tapad achieved twice the precision of the next highest-scoring cross-screen offering",
    "locator": "Opening paragraph, New York, September 14, 2016"
   }
  ],
  "scope_time": "Three-and-a-half-month evaluation preceding release; exact dates undisclosed",
  "scope_geo": "New York release; evaluated sample geography undisclosed",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Experian's Tapad-branded announcement describes three offerings in Hotels.com's three-and-a-half-month 2016 comparison. It reports twice the precision of the next offering, without identifying the two competitors. This is a relative comparison reported by the winning seller. No absolute precision, count of evaluated links, holdout design or current-product equivalence appears in the announcement.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "Relative precision is not an absolute link precision. Vendor release does not specify the numerator, absolute denominator, independent truth-label construction, or sampled US stratum.",
  "final_wording": "Tapad reported that its Device Graph achieved twice the precision of the runner-up in a 2016 Hotels.com evaluation.",
  "counterevidence": "Relative precision is not an absolute link precision. Vendor release does not specify the numerator, absolute denominator, independent truth-label construction, or sampled US stratum.",
  "stream": "B",
  "study_id": "",
  "study_design": "Customer partner selection; three competitors including Tapad, three-and-a-half months, two unnamed competitors, as reported by the seller.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-B-F07",
  "headline": false,
  "claim": "Nielsen’s announced verification method treated match rate, precision and recall as separate measures.",
  "chapter": "",
  "source_ids": [
   "IDN-B-S06"
  ],
  "passage": "five metrics including match rate, precision, recall, cross-device scale and a composite score",
  "support": [
   {
    "source_id": "IDN-B-S06",
    "passage": "five metrics including match rate, precision, recall, cross-device scale and a composite score",
    "locator": "January 2017 announcement, methodology paragraph"
   }
  ],
  "scope_time": "Program announced January 2017",
  "scope_geo": "Announcement does not identify study geography",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Nielsen’s January 30, 2017 launch notice describes census-based external data validated by Nielsen panels and lists match rate, precision, recall, scale and a composite score. The wording describes an announced methodology. It supplies no tested graph's precision and no evidence of financial independence for a particular engagement.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "This program description does not supply a named product test report or its result.",
  "final_wording": "Nielsen’s announced verification method treated match rate, precision and recall as separate measures.",
  "counterevidence": "This program description does not supply a named product test report or its result.",
  "stream": "B",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-B-F08",
  "headline": false,
  "claim": "The 0.91 F1 reported by Zimmeck and colleagues applies to their participant-device matcher; it cannot be attributed to a commercial identity graph.",
  "chapter": "",
  "source_ids": [
   "IDN-B-S07"
  ],
  "passage": "F-1 = 0.91 for connecting a mobile to a desktop device in our dataset",
  "support": [
   {
    "source_id": "IDN-B-S07",
    "passage": "F-1 = 0.91 for connecting a mobile to a desktop device in our dataset",
    "locator": "Abstract"
   }
  ],
  "scope_time": "2017 publication; historical participant traces",
  "scope_geo": "Study cohort; US institutional setting, no nationally representative estimate",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "inference",
  "review_outcome": "supported_as_stated",
  "review_note": "In their own three-stage model, Zimmeck and colleagues reported F1 of 0.91, precision of 0.88 and recall of 0.95. Table 4 evaluates 44 linked mobile/desktop pairs from the held-out split and the methods include unmatched devices. The recruitment total was 126 people, distinct from the 107 complete pairs split into 63 training and 44 testing pairs. Comcast supported the user study. F1 is the harmonic mean of precision and recall; accuracy is a separate 0.84 in the same table.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The authors tested their own matcher and disclosed a Comcast grant for the participant study. Provide the study comparator and original funding rather than assigning an independent verdict to a named graph.",
  "final_wording": "The 0.91 F1 reported by Zimmeck and colleagues applies to their participant-device matcher; it cannot be attributed to a commercial identity graph.",
  "counterevidence": "Direct record of what the authors tested and reported. The study tested their own matcher; Comcast funded the user study. This is not an independent accuracy test of Tapad or another vendor listed in the paper.",
  "stream": "B",
  "study_id": "",
  "study_design": "126 recruited internet users; 107 paired devices split into 63 training and 44 test pairs, with unmatched devices also evaluated. Authors tested their own three-stage model.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-B-F09",
  "headline": false,
  "claim": "A 2015 multinational RIPE Atlas probe study found that address changes coincided with outages of networks or power at customer equipment.",
  "chapter": "",
  "source_ids": [
   "IDN-B-S08"
  ],
  "passage": "changes are correlated with network and power outages",
  "support": [
   {
    "source_id": "IDN-B-S08",
    "passage": "changes are correlated with network and power outages",
    "locator": "Abstract, p. 1"
   }
  ],
  "scope_time": "2015-01 to 2015-12",
  "scope_geo": "156 countries, pooled",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "independent_measurement",
  "review_outcome": "supported_as_stated",
  "review_note": "The 2016 paper analyzed 2015 logs from 3,038 RIPE Atlas probes across 929 autonomous systems in 156 countries. It reports that network or power outages correlate with address changes at customer equipment. These are observational IPv4/network events. ISP and outage duration matter. Nothing here establishes a US advertising graph’s rate of household misassignment or its expiry policy. NSF grants are named.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The RIPE Atlas probe host is the unit. Do not infer the duration of a US household identity link or a universal expiry interval.",
  "final_wording": "A 2015 multinational RIPE Atlas probe study found that address changes coincided with outages of networks or power at customer equipment.",
  "counterevidence": "The RIPE Atlas probe host is the unit. Do not infer the duration of a US household identity link or a universal expiry interval.",
  "stream": "B",
  "study_id": "",
  "study_design": "3,038 probes, 929 autonomous systems in 156 countries; all months of 2015; observational probe and reachability data.",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-B-F10",
  "headline": false,
  "claim": "Miller and Skiera estimated a mean third-party cookie lifetime of 279 days in their historical European exchange sample.",
  "chapter": "",
  "source_ids": [
   "IDN-B-S09"
  ],
  "passage": "an average cookie lifetime of 279 days",
  "support": [
   {
    "source_id": "IDN-B-S09",
    "passage": "an average cookie lifetime of 279 days",
    "locator": "Abstract; §5.2 Description of Data, sampling and “mean cookie lifetime adjusted for censoring” in the results."
   }
  ],
  "scope_time": "2014-03-03 to 2016-07-16",
  "scope_geo": "European ad exchange; specific country withheld",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "independent_measurement",
  "review_outcome": "supported_with_qualification",
  "review_note": "One European exchange supplied auctions observed March 3, 2014 to July 16, 2016. Section 5.2 and the lifetime analysis distinguish the observed mean, 216 days, from the censoring-adjusted mean, 279 days; both medians are 68. The sample is 1% of active unique cookies on April 29, 2015, not a panel of 54,127 verified people or the full population of newly issued cookies. This is historical exchange evidence, not a US platform-policy limit.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "A historical exchange-cookie estimate is neither a browser policy limit nor the duration of an identifiable person or household. Geography is European, not US.",
  "final_wording": "Miller and Skiera estimated a censoring-adjusted mean lifetime of 279 days for 54,127 third-party cookies sampled on one day at a European ad exchange. The observed mean was 216 days.",
  "counterevidence": "A historical exchange-cookie estimate is neither a browser policy limit nor the duration of an identifiable person or household. Geography is European, not US.",
  "stream": "B",
  "study_id": "",
  "study_design": "Random sample of eligible exchange cookies with roughly 128 million observed ad impressions; observation window 867 days; authors address censoring.",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-B-F11",
  "headline": false,
  "claim": "In its December 2006 US home-PC analysis, comScore reported that 31% of users cleared first-party cookies for the site studied.",
  "chapter": "",
  "source_ids": [
   "IDN-B-S10"
  ],
  "passage": "31 percent of U.S. Internet users cleared their first-party cookies during the month",
  "support": [
   {
    "source_id": "IDN-B-S10",
    "passage": "31 percent of U.S. Internet users cleared their first-party cookies during the month",
    "locator": "Average Computer Receives 2.5 First-Party Cookies per Site Each Month"
   }
  ],
  "scope_time": "2006-12",
  "scope_geo": "United States, home PCs in comScore sample",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Comscore's narrative calls them users. In its first-party table, 31% is in the column for percent of computers with at least one reset. The study covers 400,000 US home PCs, one site and separately one third-party server. The table supplies a computer denominator, not unique people. The third-party column is a separate 27% for one ad server.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "Vendor-reported panel result. Use the home-PC frame and selected first-party site; avoid a present-day national deletion rate.",
  "final_wording": "In Comscore’s December 2006 US home-PC sample, 31% of computers had at least one first-party cookie reset at the site studied. The first-party analysis excluded login cookies.",
  "counterevidence": "Vendor-reported panel result. Use the home-PC frame and selected first-party site; avoid a present-day national deletion rate.",
  "stream": "B",
  "study_id": "",
  "study_design": "400,000 home PCs in comScore US sample; one first-party site and separate third-party advertising server; historical panel analysis.",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-B-F12",
  "headline": false,
  "claim": "A LiveRamp manual bearing 2017 copyright already published the same comScore precision range that appears in its later online help.",
  "chapter": "3",
  "source_ids": [
   "IDN-B-S11",
   "IDN-B-S04"
  ],
  "passage": "[IDN-B-S11, Copyright notice; 1. Deterministic, Methodology] 95%-98.9% precision (depending on quality of sample data). [IDN-B-S04, Deterministic Matching, Note] (depending on quality of sample data).",
  "support": [
   {
    "source_id": "IDN-B-S11",
    "passage": "95%-98.9% precision (depending on quality of sample data).",
    "locator": "Copyright notice; 1. Deterministic, Methodology"
   },
   {
    "source_id": "IDN-B-S04",
    "passage": "(depending on quality of sample data).",
    "locator": "Deterministic Matching, Note"
   }
  ],
  "scope_time": "PDF copyright 2017, file created 2018-10-05; web help last modified 2020-08-19. Neither gives the test period.",
  "scope_geo": "The tested panel geography is unstated",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "The PDF has a 2017 copyright and repeats the same precision range as the Connect note. This PDF's creation and modification metadata both give October 5, 2018. The online note explicitly gives August 19, 2020 as its last modification. Neither the copyright nor the file's creation date establishes first public release or the period of comScore’s test. These are two seller documents repeating one claim.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The two seller records repeat one result. Their dates bound the documents; they do not date the comScore fieldwork or establish its relevance to the 2026 product.",
  "final_wording": "A LiveRamp PDF bearing a 2017 copyright and an online help page last modified in August 2020 repeat the same comScore precision range.",
  "counterevidence": "The two seller records repeat one result. Their dates bound the documents; they do not date the comScore fieldwork or establish its relevance to the 2026 product.",
  "stream": "B",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-B-F13",
  "headline": false,
  "claim": "Firsthand Technology Value Fund reported that its portfolio company Tapad commissioned Nielsen’s device-graph validation.",
  "chapter": "3",
  "source_ids": [
   "IDN-B-S12",
   "IDN-BV-S01"
  ],
  "passage": "The company recently commissioned Nielsen, a leading information and measurement company, to validate the accuracy of Tapad’s Device Graph matching capability",
  "support": [
   {
    "source_id": "IDN-B-S12",
    "passage": "The company recently commissioned Nielsen, a leading information and measurement company, to validate the accuracy of Tapad’s Device Graph matching capability",
    "locator": "Winter 2015, Portfolio Company News: Tapad Cross-Device Connections 91% Accurate"
   }
  ],
  "scope_time": "Winter 2015 portfolio newsletter; test window undisclosed",
  "scope_geo": "Study geography unconfirmed",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The Winter 2015 portfolio newsletter says Tapad commissioned Nielsen, and describes 91.2% matching of related devices. The fund held an interest in Tapad. Later trade coverage says Nielsen used its panel as a reference, but provides no original test design or confusion matrix. The evidence is an interested investor’s newsletter about a portfolio company, not a regulatory or other official record. The historical study was explicitly commissioned; the claim here concerns who reported its sponsor. The newsletter supports attribution to an interested investor. It is neither a regulatory filing nor a tester-issued measurement report. Do not apply the reported percentage to today's product or substitute the later Hotels.com comparison.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The interested fund describes the sponsor. It does not publish the underlying test design, panel size or an independent result. This is distinct from the Hotels.com evaluation.",
  "final_wording": "In its Winter 2015 portfolio newsletter, Firsthand Technology Value Fund said Tapad had commissioned Nielsen to test Tapad’s Device Graph.",
  "counterevidence": "The interested fund describes the sponsor. It does not publish the underlying test design, panel size or an independent result. This is distinct from the Hotels.com evaluation.",
  "stream": "B",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-C-F01",
  "headline": false,
  "claim": "LiveRamp’s activation calculation uses unique identifiable records as its base and counts records linked to a device at the selected destination.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S01"
  ],
  "passage": "percentage of total unique, identifiable records that we can match to one or more online devices",
  "support": [
   {
    "source_id": "IDN-C-S01",
    "passage": "percentage of total unique, identifiable records that we can match to one or more online devices",
    "locator": "How LiveRamp Calculates Match Rates, first paragraph and exclusion note"
   }
  ],
  "scope_time": "2026-08-06 revision",
  "scope_geo": "Vendor documentation; destination-dependent",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The 6 August 2026 Connect guide calculates destination activation yield on unique identifiable records, credits any match to at least one destination device and excludes records not assigned for delivery. Different destinations and precision levels can produce different results. No observed file result is needed for this definition.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "This is a metric definition. Actual file results are reported separately.",
  "final_wording": "LiveRamp’s activation calculation uses unique identifiable records as its base and counts records linked to a device at the selected destination.",
  "counterevidence": "This is a metric definition. Actual file results are reported separately.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F02",
  "headline": false,
  "claim": "LiveRamp illustrates how one recognized device among four can yield 25% device recognition while the same person’s email yields a 100% activation rate at a destination.",
  "chapter": "3",
  "source_ids": [
   "IDN-C-S02"
  ],
  "passage": "we only recognize 1/4 Joe's devices, so our recognition rate for Joe is 25%.",
  "support": [
   {
    "source_id": "IDN-C-S02",
    "passage": "we only recognize 1/4 Joe's devices, so our recognition rate for Joe is 25%.",
    "locator": "Recognition Rates, “Joe” example"
   }
  ],
  "scope_time": "2025-07-10 revision",
  "scope_geo": "Illustration with no geographic sample",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "illustrative_scenario",
  "review_outcome": "supported_as_stated",
  "review_note": "The guide, last modified 10 July 2025, uses Joe as a hypothetical individual. One of four devices recognized is 25% of device inputs. Supplying Joe’s email and finding just one device at the destination counts as success for the single activation input. These two fractions have different denominators.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "The named person is illustrative. No observed US sample, seller benchmark or graph accuracy.",
  "final_wording": "LiveRamp illustrates how one recognized device among four can yield 25% device recognition while the same person’s email yields a 100% activation rate at a destination.",
  "counterevidence": "The named person is illustrative. No observed US sample, seller benchmark or graph accuracy.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F03",
  "headline": false,
  "claim": "LiveRamp documents a derived RampID generated for a submitted PII string even when that string has no match in its identity graph.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S03"
  ],
  "passage": "there isn't a match in the Identity Graph, a derived RampID version is returned",
  "support": [
   {
    "source_id": "IDN-C-S03",
    "passage": "there isn't a match in the Identity Graph, a derived RampID version is returned",
    "locator": "About RampIDs, derived RampIDs"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "API documentation; geography unspecified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The developer page distinguishes an AbiliTec graph hit (maintained) from a persistent ID computed on an input string with no graph hit (derived). Identical input can return the same derived value. An API return by itself does not establish a graph match to a real person.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Receiving an ID does not by itself establish a maintained match. The API documentation names a service behavior, not a rate.",
  "final_wording": "LiveRamp documents a derived RampID generated for a submitted PII string even when that string has no match in its identity graph.",
  "counterevidence": "Receiving an ID does not by itself establish a maintained match. The API documentation names a service behavior, not a rate.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F04",
  "headline": false,
  "claim": "In its public summary of a US insurer’s Data Health Assessment, TransUnion reports a 99.5% match to identities for that insurer’s customers.",
  "chapter": "3",
  "source_ids": [
   "IDN-C-S04",
   "IDN-CV-S01",
   "IDN-CV-S02"
  ],
  "passage": "[IDN-C-S04, Case summary, first bullet] Match 99.5% of its customers to real, verified identities [IDN-CV-S01, p. 2, Solution, first column (99.5% and 97.4%)] TransUnion matched 99.5% of records to a person in the TransUnion offline identity graph [IDN-CV-S02, Snowflake Marketplace Offerings: TruAudience Identity – Data Health Assessment; following heading: TruAudience Identity Resolution & Enrichment] The DHA app shows the rate at which TransUnion can resolve your data to a unique individual or household",
  "support": [
   {
    "source_id": "IDN-C-S04",
    "passage": "Match 99.5% of its customers to real, verified identities",
    "locator": "Case summary, first bullet"
   },
   {
    "source_id": "IDN-CV-S01",
    "passage": "TransUnion matched 99.5% of records to a person in the TransUnion offline identity graph",
    "locator": "p. 2, Solution, first column (99.5% and 97.4%)"
   },
   {
    "source_id": "IDN-CV-S02",
    "passage": "The DHA app shows the rate at which TransUnion can resolve your data to a unique individual or household",
    "locator": "Snowflake Marketplace Offerings: TruAudience Identity – Data Health Assessment; following heading: TruAudience Identity Resolution & Enrichment"
   }
  ],
  "scope_time": "2025 copyright on case PDF; date of insurer assessment undisclosed; opened 2026-11-11.",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The teaser uses customers and potential language. In the two-page case report, TransUnion says it actually matched 99.5% of this insurer’s records to a person in its offline identity graph. It reports 97.4% matching on first name, last name and another PII field. The absolute input count, field combination or threshold for the remaining links, deduplication rule and labeled truth are absent. TransUnion separately lists its assessment and its commercial resolution/enrichment service. The teaser and full PDF are one corporate origin. Field agreement for 97.4% does not specify the acceptance rule for all 99.5%. The separately listed provision of a diagnostic does not prove the commercial resolution SKU handled the case.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "The full case provides a record denominator category, person-level output and a field-agreement slice. It gives no absolute file count, measurement period, acceptance threshold covering 99.5%, independently verified identity labels or link to a specific commercial resolution SKU.",
  "final_wording": "In a Data Health Assessment for one unnamed US insurer, TransUnion says it matched 99.5% of the insurer’s records to a person in its offline identity graph. The report also gives a 97.4% match on first name, last name and at least one other PII field. It does not disclose the full acceptance rule for the 99.5% rate.",
  "counterevidence": "The full case provides a record denominator category, person-level output and a field-agreement slice. It gives no absolute file count, measurement period, acceptance threshold covering 99.5%, independently verified identity labels or link to a specific commercial resolution SKU.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F05",
  "headline": false,
  "claim": "Experian reports a 70% match between IP addresses supplied by MiQ and cookieless IDs in the Experian/MiQ engagement.",
  "chapter": "3",
  "source_ids": [
   "IDN-C-S05",
   "IDN-C-S06"
  ],
  "passage": "[IDN-C-S05, MiQ Digital Graph case, Results; companion overview, MiQ case entry] 70% match rate between MiQ-provided IP addresses and cookieless IDs [IDN-C-S06, p. 4, Solution] MiQ incorporated Experian’s Digital Graph, licensing HEMs, UID2s, and third-party partner cookies",
  "support": [
   {
    "source_id": "IDN-C-S05",
    "passage": "70% match rate between MiQ-provided IP addresses and cookieless IDs",
    "locator": "MiQ Digital Graph case, Results; companion overview, MiQ case entry"
   },
   {
    "source_id": "IDN-C-S06",
    "passage": "MiQ incorporated Experian’s Digital Graph, licensing HEMs, UID2s, and third-party partner cookies",
    "locator": "p. 4, Solution"
   }
  ],
  "scope_time": "Case materials available by cutoff",
  "scope_geo": "Global MiQ engagement; case cohort geography unspecified",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The seller’s results directory and its PDF, printed pages 5–6, report the same MiQ input-IP to cookieless-ID rate of 70%. The 6.5 devices statistic has matched IPs as its denominator. Page 4 describes licensed hashed emails, UID2s and partner cookies but does not document the acceptance rule for the 70% figure. The issuer and case are the same for both links.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "The files describe global operations and several ID types, without a US-only rate, row counts, exclusions or link-acceptance criterion.",
  "final_wording": "Experian reports a 70% match between IP addresses supplied by MiQ and cookieless IDs in the Experian/MiQ engagement.",
  "counterevidence": "The files describe global operations and several ID types, without a US-only rate, row counts, exclusions or link-acceptance criterion.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F06",
  "headline": false,
  "claim": "In a 2022 post about a clean-room offering, Epsilon reported a 95% match rate between IRI transaction data and CORE ID.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S07"
  ],
  "passage": "95% match rate between IRI’s transaction data and Epsilon’s CORE ID",
  "support": [
   {
    "source_id": "IDN-C-S07",
    "passage": "95% match rate between IRI’s transaction data and Epsilon’s CORE ID",
    "locator": "Final section, IRI data paragraph"
   }
  ],
  "scope_time": "2022-09-09 publication",
  "scope_geo": "US publisher page; population territory unspecified",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Epsilon’s 9 September 2022 article pairs IRI transactional data with CORE ID and gives 95%. Its discussion of deterministic IDs does not say which IRI items were eligible, what was counted once, or how a particular link passed. No sample geography or measurement period is supplied.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "IRI transaction data could denote transactions, customer records or accounts. The metric paragraph does not give the eligible row definition, tested period or sample geography.",
  "final_wording": "In a 2022 post about a clean-room offering, Epsilon reported a 95% match rate between IRI transaction data and CORE ID.",
  "counterevidence": "IRI transaction data could denote transactions, customer records or accounts. The metric paragraph does not give the eligible row definition, tested period or sample geography.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F07",
  "headline": false,
  "claim": "Epsilon reports a 77% match rate for known email subscribers in a specialty retailer’s Intent Messaging case.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S08"
  ],
  "passage": "match rate (known email subscribers)",
  "support": [
   {
    "source_id": "IDN-C-S08",
    "passage": "match rate (known email subscribers)",
    "locator": "Increasing revenue and match rate, second tile"
   }
  ],
  "scope_time": "Undated case read 2026-11-11",
  "scope_geo": "US publisher page; retailer cohort territory unspecified",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The unnamed specialty-retailer marketing case labels the 77% tile as the rate for known email subscribers. Its later CORE ID passage concerns a different, unauthenticated-reach outcome. The page gives no tested input count, output identity definition, observation dates or false-match check for 77%.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "77% is in the adjacent metric tile; CORE ID appears under the separate unauthenticated-reach result. Do not attribute the 77% metric to CORE ID.",
  "final_wording": "Epsilon reports a 77% match rate for known email subscribers in a specialty retailer’s Intent Messaging case.",
  "counterevidence": "77% is in the adjacent metric tile; CORE ID appears under the separate unauthenticated-reach result. Do not attribute the 77% metric to CORE ID.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F08",
  "headline": false,
  "claim": "In March 2022 Cadent advertised an average match rate above 90% for audience segments using Aperture Viewer Graph.",
  "chapter": "3",
  "source_ids": [
   "IDN-C-S09"
  ],
  "passage": "over a 90% average match rate for audience segments",
  "support": [
   {
    "source_id": "IDN-C-S09",
    "passage": "over a 90% average match rate for audience segments",
    "locator": "Product metrics, paragraph following launch discussion"
   }
  ],
  "scope_time": "March 2022 release",
  "scope_geo": "US release; segment universe unspecified",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Cadent’s own 30 March 2022 release, syndicated on PR Newswire, reports an average exceeding 90% for segments and separately counts match keys and onboarding minutes. It gives no submitted-record total per segment, weights, or test dates; Q1 provides the release’s coverage context.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "The release describes multiple keys but does not identify the eligible records in each segment, the weighting of segments, or the sample underpinning the average.",
  "final_wording": "In March 2022 Cadent advertised an average match rate above 90% for audience segments using Aperture Viewer Graph.",
  "counterevidence": "The release describes multiple keys but does not identify the eligible records in each segment, the weighting of segments, or the sample underpinning the average.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F09",
  "headline": false,
  "claim": "In 2019 Viant and Acxiom reported matching more than 275 million unique identifiers across their US data partnership.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S10"
  ],
  "passage": "executed a match of over 275 million unique identifiers",
  "support": [
   {
    "source_id": "IDN-C-S10",
    "passage": "executed a match of over 275 million unique identifiers",
    "locator": "Irvine dateline, opening paragraph"
   }
  ],
  "scope_time": "2019-09-11 release",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Viant’s 11 September 2019 corporate release describes a joint direct match of over 275 million unique IDs with Acxiom. The US dataset context does not turn matched identifier count into a count of people. The release supplies no eligible-ID total or observed rate.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Identifier count only. No percentage or eligible input denominator. US historical partnership is not a product-specific present-day household rate.",
  "final_wording": "In 2019 Viant and Acxiom reported matching more than 275 million unique identifiers across their US data partnership.",
  "counterevidence": "Identifier count only. No percentage or eligible input denominator. US historical partnership is not a product-specific present-day household rate.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F10",
  "headline": false,
  "claim": "Forrester’s July 2026 TransUnion-commissioned model puts a 20-percentage-point gain in identity match rates on a composite enterprise derived from four customer interviews.",
  "chapter": "3",
  "source_ids": [
   "IDN-C-S11"
  ],
  "passage": "20 percentage points Increase in identity match rates",
  "support": [
   {
    "source_id": "IDN-C-S11",
    "passage": "20 percentage points Increase in identity match rates",
    "locator": "Executive Summary, metrics strip and interview/composite paragraphs"
   }
  ],
  "scope_time": "July 2026 study",
  "scope_geo": "Composite enterprise; no US-only file",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "commissioned_measurement",
  "review_outcome": "supported_with_qualification",
  "review_note": "TransUnion selected the customer names; Forrester interviewed four decision-makers at US-headquartered companies. Its July 2026 table assumes 15 million targeted households and 60% vs 80% matching in each of three model years. Twenty percentage points and 3 million incremental households follow from those inputs. These are model assumptions informed by interviews; none is a measured file-level outcome. Keep commissioned_measurement for the study provenance; change claim_status from actual to forecast for modeled outcomes in the three-year TEI composite, consistent with the tables.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Composite estimate across audience and identity solutions; not an audited rate for one service. Units are percentage points, not percent.",
  "final_wording": "In July 2026, Forrester used four customer interviews in a TransUnion-funded study to model a rise in household match rate from 60% to 80% for a composite enterprise. The 20-percentage-point gain is a model assumption.",
  "counterevidence": "Composite estimate across audience and identity solutions; not an audited rate for one service. Units are percentage points, not percent.",
  "stream": "C",
  "study_id": "",
  "study_design": "Forrester interviewed four decision-makers from US-headquartered customers whose names TransUnion supplied. The three-year composite uses modeled rates of 60% and 80%. No tested file is disclosed.",
  "claim_status": "forecast",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F11",
  "headline": false,
  "claim": "TransUnion described its January 2024 identity graph enhancement as combining TransUnion and Neustar data, clustering identifiers into people and households and scoring those identities.",
  "chapter": "8",
  "source_ids": [
   "IDN-C-S12"
  ],
  "passage": "cluster identifiers into individuals and households and then score the strength of those identities",
  "support": [
   {
    "source_id": "IDN-C-S12",
    "passage": "cluster identifiers into individuals and households and then score the strength of those identities",
    "locator": "Opening paragraphs, Graph building"
   }
  ],
  "scope_time": "2024-01-04 announcement",
  "scope_geo": "US-oriented marketing solutions; portfolio",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The 4 January 2024 Chicago release describes the integrated data assets of TransUnion and Neustar, AI-assisted clustering into individual and household identities and a strength score for those identities. Those implementation claims do not disclose which older graph edges survived the process.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Combining asset pools does not establish that the predecessor’s primary edges persisted or how input coverage changed.",
  "final_wording": "TransUnion described its January 2024 identity graph enhancement as combining TransUnion and Neustar data, clustering identifiers into people and households and scoring those identities.",
  "counterevidence": "Combining asset pools does not establish that the predecessor’s primary edges persisted or how input coverage changed.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-C-F12",
  "headline": false,
  "claim": "LiveRamp’s May 2021 notice describes a rename from IdentityLink to RampID, and its ATS developer guide still illustrates an identityLink configuration and idl_env envelope key.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S13",
   "IDN-C-S14"
  ],
  "passage": "[IDN-C-S13, Opening paragraph and FAQ on effect on product] The name for LiveRamp's pseudonymous identifier (formerly known as \"IdentityLink\" or \"IDL\") is now called \"RampID\". [IDN-C-S14, Configuring Prebid, example storage object] name: 'idl_env'",
  "support": [
   {
    "source_id": "IDN-C-S13",
    "passage": "The name for LiveRamp's pseudonymous identifier (formerly known as \"IdentityLink\" or \"IDL\") is now called \"RampID\".",
    "locator": "Opening paragraph and FAQ on effect on product"
   },
   {
    "source_id": "IDN-C-S14",
    "passage": "name: 'idl_env'",
    "locator": "Configuring Prebid, example storage object"
   }
  ],
  "scope_time": "May 2021 transition and published implementation observed by cutoff",
  "scope_geo": "Seller’s global identifier",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "The 24 May 2021 name-change announcement says the pseudonymous identifier is being renamed, without changing the product. The separate ATS Prebid configuration still uses the identityLink module name and idl_env as its cookie-storage key. This corroborates naming continuity, without establishing historical edge-by-edge continuity.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Identifier namespace continuity is well documented. A name or key alone does not establish unchanged underlying edges or a distinct relaunch pitched for US cookie substitution.",
  "final_wording": "LiveRamp’s May 2021 notice describes a rename from IdentityLink to RampID, and its ATS developer guide still illustrates an identityLink configuration and idl_env envelope key.",
  "counterevidence": "Identifier namespace continuity is well documented. A name or key alone does not establish unchanged underlying edges or a distinct relaunch pitched for US cookie substitution.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-C-F13",
  "headline": false,
  "claim": "Lotame described its October 2020 Panorama ID as a cookieless ID powered by its graphing technology. Its company timeline dates the Panorama Identity Graph to 2019.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S15",
   "IDN-C-S16"
  ],
  "passage": "[IDN-C-S15, Opening release paragraph and technology paragraph] Powered by Lotame’s patented graphing technology [IDN-C-S16, Company history, 2019 milestone] 2019: Launched Panorama Identity Graph",
  "support": [
   {
    "source_id": "IDN-C-S15",
    "passage": "Powered by Lotame’s patented graphing technology",
    "locator": "Opening release paragraph and technology paragraph"
   },
   {
    "source_id": "IDN-C-S16",
    "passage": "2019: Launched Panorama Identity Graph",
    "locator": "Company history, 2019 milestone"
   }
  ],
  "scope_time": "2019–2020 events, release republished 2023",
  "scope_geo": "New York launch, global pitch",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "Lotame’s launch text datelined New York, 28 October 2020 describes a graph-powered cookieless identifier, while the page header is 12 September 2023. Its own timeline distinguishes the 2019 graph from the 2020 identifier. No public edge crosswalk is in either source. These two accounts share an interested issuer.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "The sources do not supply an edge crosswalk or a migration map proving that the primary US linkage stayed the same. Lotame is a declared former employer.",
  "final_wording": "Lotame described its October 2020 Panorama ID as a cookieless ID powered by its graphing technology. Its company timeline dates the Panorama Identity Graph to 2019.",
  "counterevidence": "The sources do not supply an edge crosswalk or a migration map proving that the primary US linkage stayed the same. Lotame is a declared former employer.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-C-F14",
  "headline": false,
  "claim": "OpenAP describes its 2025 Open Identity launch as an evolution of OpenID that lets parties match without a central identity spine.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S17"
  ],
  "passage": "without requiring a central identity spine",
  "support": [
   {
    "source_id": "IDN-C-S17",
    "passage": "without requiring a central identity spine",
    "locator": "Open Identity launch, explanatory paragraph"
   }
  ],
  "scope_time": "2025-04-15",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "OpenAP’s 15 April 2025 announcement describes a federated successor to OpenID allowing direct matches between parties without a central spine. It distinguishes three data partners available at launch from two integrations still underway. That architecture does not establish the accuracy of the matches.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Federated matching architecture can change without a documented replacement of underlying partner graphs. Verify whether a cookie-replacement pitch makes this launch eligible.",
  "final_wording": "OpenAP describes its 2025 Open Identity launch as an evolution of OpenID that lets parties match without a central identity spine.",
  "counterevidence": "Federated matching architecture can change without a documented replacement of underlying partner graphs. Verify whether a cookie-replacement pitch makes this launch eligible.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-C-F15",
  "headline": false,
  "claim": "Deep Sync reports resolving 83.5% of a US outdoor retailer’s full CRM file with its Profile Hygiene & Enrichment service using 19 enabled matching rules against its graph.",
  "chapter": "3",
  "source_ids": [
   "IDN-C-S19",
   "IDN-C-S18"
  ],
  "passage": "[IDN-C-S19, The solution, All 19 matching rules, and opening KPI tiles] With all rules active, Deep Sync resolved 83.5% of the 884K-record CRM [IDN-C-S18, Case study 02, opening paragraph] the largest U.S. seller of recreational vehicles",
  "support": [
   {
    "source_id": "IDN-C-S19",
    "passage": "With all rules active, Deep Sync resolved 83.5% of the 884K-record CRM",
    "locator": "The solution, All 19 matching rules, and opening KPI tiles"
   },
   {
    "source_id": "IDN-C-S18",
    "passage": "the largest U.S. seller of recreational vehicles",
    "locator": "Case study 02, opening paragraph"
   }
  ],
  "scope_time": "Case linked on 2026-09-01; measurement dates unspecified",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The case labels the service Profile Hygiene & Enrichment and says every one of the 19 rules was enabled on the retailer’s full CRM; 83.5% of that file resolved. The body says 884K, the KPI tile 885K, and a separate reach diagram calls 700K the incoming audience. The September overview identifies a US outdoor/RV seller. No list of the 19 rules or truth labels is supplied.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Case also displays 885K submitted, nearly 885,000 and a 700K audience figure. Preserve rounding and distinct labels. Rules are enumerated by count, not defined individually. A product admission and method-sufficiency check remain.",
  "final_wording": "Deep Sync reports resolving 83.5% of a US outdoor retailer’s full CRM file with its Profile Hygiene & Enrichment service using 19 enabled matching rules against its graph.",
  "counterevidence": "Case also displays 885K submitted, nearly 885,000 and a 700K audience figure. Preserve rounding and distinct labels. Rules are enumerated by count, not defined individually. A product admission and method-sufficiency check remain.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F16",
  "headline": false,
  "claim": "Deep Sync reports a 73.0% cumulative match rate after three passes over a US grocery chain’s monthly POS file, using loyalty, payment-card and modeled geographic/household links.",
  "chapter": "abstract, 3, 11",
  "source_ids": [
   "IDN-C-S20"
  ],
  "passage": "store-level geographic catchment modeling combined with household identity data",
  "support": [
   {
    "source_id": "IDN-C-S20",
    "passage": "store-level geographic catchment modeling combined with household identity data",
    "locator": "The solution, pass 3, and cumulative result directly below"
   }
  ],
  "scope_time": "One month; case linked from 2026-09-01 publication",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The grocery case identifies a US retailer and presents three cumulative percentages, 22.8%, 30.6% and 73.0%, over the monthly POS file after loyalty, card and household/geographic inference. The roughly 9.6m, 3.3m and 18.1m pass counts sum to 31.0m, versus the approximately 32m headline and 43.8m+ monthly volume. Elsewhere it gives 64–73% of monthly volume and discusses anonymous transactions. No exact common count or labeled person accuracy is recoverable. Use vendor-published waterfall endpoint and attach its rounding and file caveats in H1. No ground truth is shown for the third pass.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Monthly POS file and anonymous transactions are described separately. The waterfall ends at 73.0%; the summary gives 64–73% and an approximate 32m total, but the three approximate pass counts sum to 31.0m. No calendar month, exact common numerator or person-level accuracy is established.",
  "final_wording": "Deep Sync reports a 73.0% cumulative match rate for one US grocery chain’s monthly POS file after loyalty, card and probabilistic household/geographic matching. Its summary gives a range of roughly 64–73% of monthly volume. Its rounded pass counts and headline total do not reconcile exactly.",
  "counterevidence": "Seller also describes roughly 70% of anonymous transactions, 64–73% of monthly volume and 73.0% cumulative. Verify full-file vs anonymous base, period and person versus household output before using H1.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F17",
  "headline": false,
  "claim": "Deep Sync’s general identity resolution product sheet describes its online-to-offline linkage as deterministic on shared information.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S21"
  ],
  "passage": "we link online identifiers to real-world people and households based on shared information",
  "support": [
   {
    "source_id": "IDN-C-S21",
    "passage": "we link online identifiers to real-world people and households based on shared information",
    "locator": "Fully-Deterministic Matching"
   }
  ],
  "scope_time": "Product sheet read 2026-11-11",
  "scope_geo": "US identity graph",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The original issuer PDF recovered from the web index describes the general online-to-person/household linkage as deterministic, using shared information. The product sheet does not name the transaction case or prove all sold workflows are deterministic. The live PDF URL returned HTTP 404. Technical-sounding marketing copy is grade D. Indexed PDF opened when the live link returned 404.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Technical marketing does not validate ground truth. The separate grocery transaction service expressly includes a probabilistic step.",
  "final_wording": "Deep Sync’s general identity resolution product sheet describes its online-to-offline linkage as deterministic on shared information.",
  "counterevidence": "Technical marketing does not validate ground truth. The separate grocery transaction service expressly includes a probabilistic step.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-C-F18",
  "headline": false,
  "claim": "In 2019 Neustar commissioned Forrester to survey 175 respondents across the US, UK and Germany about brand identity-resolution practices.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S22"
  ],
  "passage": "Forrester conducted an online survey with 175 respondents in a variety of industries in the US, the UK, and Germany",
  "support": [
   {
    "source_id": "IDN-C-S22",
    "passage": "Forrester conducted an online survey with 175 respondents in a variety of industries in the US, the UK, and Germany",
    "locator": "Executive summary, survey description"
   }
  ],
  "scope_time": "2019 survey",
  "scope_geo": "US, UK, Germany pooled",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "commissioned_measurement",
  "review_outcome": "supported_as_stated",
  "review_note": "Forrester’s Neustar-funded study reports an incentivized online survey of 175 customer-data and analytics decision-makers from multiple industries, April–May 2019. The geography is pooled across the US, UK and Germany. The questionnaire elicited practices and views; it did not label or independently test a graph.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Survey of decision-makers; does not test a named graph’s accuracy or supply a US-only estimate.",
  "final_wording": "In 2019 Neustar commissioned Forrester to survey 175 respondents across the US, UK and Germany about brand identity-resolution practices.",
  "counterevidence": "Survey of decision-makers; does not test a named graph’s accuracy or supply a US-only estimate.",
  "stream": "C",
  "study_id": "",
  "study_design": "Online survey, 175 customer-data/analytics decision-makers in three countries pooled. No labeled graph links or accuracy test.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-C-F19",
  "headline": false,
  "claim": "Verizon Media’s December 2020 ConnectID launch cited a graph built from deterministic data obtained through its direct relationships with consumers.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S24"
  ],
  "passage": "Verizon Media’s Identity Graph is built on deterministic data from direct consumer relationships",
  "support": [
   {
    "source_id": "IDN-C-S24",
    "passage": "Verizon Media’s Identity Graph is built on deterministic data from direct consumer relationships",
    "locator": "Diverse ID graph bullet"
   }
  ],
  "scope_time": "2020-12-01 launch",
  "scope_geo": "United States launch, global product pitch",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Verizon Media’s own December 2020 announcement says its graph draws deterministic data from direct relationships across email, search and its owned services. A market launch and asserted data lineage do not prove consent events, graph accuracy or the unchanged reuse of every link.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Launch positioning identifies an upstream graph, while edge-level continuity into the later Yahoo implementation remains unknown.",
  "final_wording": "Verizon Media’s December 2020 ConnectID launch cited a graph built from deterministic data obtained through its direct relationships with consumers.",
  "counterevidence": "Launch positioning identifies an upstream graph, while edge-level continuity into the later Yahoo implementation remains unknown.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-C-F20",
  "headline": false,
  "claim": "Yahoo’s ConnectID server-to-server guide instructs publishers to request an ID using a hashed email and include the returned ID in an ad request.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S23"
  ],
  "passage": "Obtain a ConnectID by sending a hashed email along with several other parameters described below.",
  "support": [
   {
    "source_id": "IDN-C-S23",
    "passage": "Obtain a ConnectID by sending a hashed email along with several other parameters described below.",
    "locator": "High-level integration steps 1 and 2"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "Global publisher implementation guide",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Yahoo’s integration overview specifies two steps, exchanging a hashed email and other parameters for a ConnectID, then passing that ID in the ad request. The later API section requires a publisher identifier and authorization. This is a vendor integration recipe, not an observed auction or consent test.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "A publisher-side implementation path does not establish how a recipient processes a refusal or honors withdrawal.",
  "final_wording": "Yahoo’s ConnectID server-to-server guide instructs publishers to request an ID using a hashed email and include the returned ID in an ad request.",
  "counterevidence": "A publisher-side implementation path does not establish how a recipient processes a refusal or honors withdrawal.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-C-F21",
  "headline": false,
  "claim": "Kantar reports that its match rates with TV partners increased more than tenfold after it integrated Blockgraph’s Identity Operating System.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S25"
  ],
  "passage": "Kantar match rates with TV partners have increased over 10x",
  "support": [
   {
    "source_id": "IDN-C-S25",
    "passage": "Kantar match rates with TV partners have increased over 10x",
    "locator": "Second paragraph, after explanation of direct panel matching"
   }
  ],
  "scope_time": "2022-11-01 announcement",
  "scope_geo": "Kantar North America; participating TV-partner sample unspecified",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Kantar says its match rate with TV partners rose more than tenfold following Blockgraph integration. It describes direct matching of panel and client datasets. The signed partner quotation rounds the factor to ten; the release contains no absolute before/after rate, row count or eligible denominator.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Partner-reported multiplier. Starting and ending rates, eligible records and study period are not supplied in that paragraph.",
  "final_wording": "Kantar reports that its match rates with TV partners increased more than tenfold after it integrated Blockgraph’s Identity Operating System.",
  "counterevidence": "Partner-reported multiplier. Starting and ending rates, eligible records and study period are not supplied in that paragraph.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F22",
  "headline": false,
  "claim": "ID5 describes a Telefónica and Havas campaign test in Spain that ran from February 13 to April 21, 2023.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S26"
  ],
  "passage": "A test was run in Spain between February 13th and April 21st, 2023.",
  "support": [
   {
    "source_id": "IDN-C-S26",
    "passage": "A test was run in Spain between February 13th and April 21st, 2023.",
    "locator": "Test section, opening sentence"
   }
  ],
  "scope_time": "2023-02-13 through 2023-04-21",
  "scope_geo": "Spain",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "ID5 places its named Telefónica/Havas test in Spain between 13 February and 21 April 2023. Havas also worked on publisher adoption in the market, a potential change in supply. The reported costs per lead and acquisition are campaign outcomes with no independent causal attribution or US stratum.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Commercial participants and seller-hosted campaign account. It does not supply an observed US ID match rate; never use Spain as the US basis.",
  "final_wording": "ID5 describes a Telefónica and Havas campaign test in Spain that ran from February 13 to April 21, 2023.",
  "counterevidence": "Commercial participants and seller-hosted campaign account. It does not supply an observed US ID match rate; never use Spain as the US basis.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F23",
  "headline": false,
  "claim": "Yahoo DataX documents a partner API that supplies both per-file and aggregated match statistics.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S27"
  ],
  "passage": "Match rates per file and an aggregated overall match rate are provided by Yahoo Ad Tech.",
  "support": [
   {
    "source_id": "IDN-C-S27",
    "passage": "Match rates per file and an aggregated overall match rate are provided by Yahoo Ad Tech.",
    "locator": "Match Rates, overview and API Responses"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "Yahoo onboarding partners; example unlocated",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The Yahoo DataX documentation describes per-request results and aggregation using multiple request IDs; its displays use 80/100 and 700/1,000 as sample payloads. The HTML example is illustrative. Neither number is an observed ConnectID match rate.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "The 80/100 API example illustrates a response shape. No observed US ConnectID sample or product-transfer claim follows.",
  "final_wording": "Yahoo DataX documents a partner API that supplies both per-file and aggregated match statistics.",
  "counterevidence": "The 80/100 API example illustrates a response shape. No observed US ConnectID sample or product-transfer claim follows.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F24",
  "headline": false,
  "claim": "ID5 says Pubfinity tested ID5 ID on 5% of its global Windows desktop campaign traffic over 14 days in Q1 2024.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S28"
  ],
  "passage": "over 14 days in Q1 2024 on 5% of global traffic",
  "support": [
   {
    "source_id": "IDN-C-S28",
    "passage": "over 14 days in Q1 2024 on 5% of global traffic",
    "locator": "Solution, test design"
   }
  ],
  "scope_time": "Q1 2024 test",
  "scope_geo": "Global sample",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "ID5 says the Pubfinity A/B test used 5% of global traffic for 14 days in Q1 2024, with display and video inventory from over twenty publishers and over one hundred Windows desktop games and apps. The unit of traffic sampled, total eligible impressions/users and allocation procedure are unspecified.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "The source describes Windows games/apps and several separate outcomes. Its addressability uplift, revenue per active user and an observed US match rate have different units.",
  "final_wording": "ID5 says Pubfinity ran a 14-day A/B test in Q1 2024 on 5% of global traffic in a test of Windows desktop games and apps. It does not specify the traffic unit or total eligible volume.",
  "counterevidence": "The source describes Windows games/apps and several separate outcomes. Its addressability uplift, revenue per active user and an observed US match rate have different units.",
  "stream": "C",
  "study_id": "",
  "study_design": "SSP-run A/B test in Windows games/apps. Identity seller’s report; randomization method, group sizes, error labels and detailed US stratum unreported.",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F25",
  "headline": false,
  "claim": "Zeta’s DSP pixel guide says the tag calls exchange partners to match IDs when it loads.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S29"
  ],
  "passage": "Each time a Zeta tag loads, we match with exchange partners",
  "support": [
   {
    "source_id": "IDN-C-S29",
    "passage": "Each time a Zeta tag loads, we match with exchange partners",
    "locator": "JavaScript FAQ: What is Cookie Matching?"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "DSP implementation; geography unspecified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The JavaScript FAQ says exchange-partner requests on tag loads help synchronize cookie IDs. The later piggybacking FAQ permits turning those requests off and states that which pixels fire depends on prior matching and the user’s cookies. The page does not date a change in behavior or describe every Zeta service.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "One mutable guide on a DSP route does not establish a before/after change, or that the separately registered identity product has the same path.",
  "final_wording": "Zeta’s DSP guide says its JavaScript tag normally requests cookie-ID matches from exchange partners when it loads. The guide says the partner pixels can be disabled.",
  "counterevidence": "One mutable guide on a DSP route does not establish a before/after change, or that the separately registered identity product has the same path.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-C-F26",
  "headline": false,
  "claim": "For one US mass retailer, Deep Sync reports that UID2 matched 73.2 million records (51%) before CRM enrichment and 94.4 million (66%) after enrichment.",
  "chapter": "3",
  "source_ids": [
   "IDN-C-S30"
  ],
  "passage": "UID2 (The Trade Desk)  | 73.2M · 51%  | 94.4M · 66%  | +15 pts",
  "support": [
   {
    "source_id": "IDN-C-S30",
    "passage": "UID2 (The Trade Desk)  | 73.2M · 51%  | 94.4M · 66%  | +15 pts",
    "locator": "The results: Social & identity platforms, UID2 row; US geography and full 141.7M CRM file in The challenge section."
   }
  ],
  "scope_time": "Case published by 2026-09-01; duration not given",
  "scope_geo": "United States, one retailer",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The social/identity comparison table labels the UID2 rows as matched records: 73.2m/51% before and 94.4m/66% after. With the stated 141.7m CRM total, those counts yield around 51.7% and 66.6%; no rounding, exclusion or destination eligibility rule is given. The case is Deep Sync’s account, not a Trade Desk measurement.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The seller identifies the destination, country of the retail case and before/after row counts and percentages.",
  "limitations": "The advertiser is unnamed. Deep Sync published the labeled UID2 row; recipient eligibility, precise denominator and percent rounding are unstated. Dividing the submitted nominal file into the listed counts gives about 51.7% and 66.6%. No independent test of match correctness.",
  "final_wording": "For one US mass retailer, Deep Sync’s UID2 row reports 73.2 million matched records (51%) before CRM enrichment and 94.4 million (66%) after. The case gives a nominal file of 141.7 million records but does not explain the whole-percent rounding or exact destination denominator.",
  "counterevidence": "The same file’s Meta range reaches 104%. Read each destination’s metric separately; do not assume a unique-person fraction for all platforms.",
  "stream": "C",
  "study_id": "",
  "study_design": "One retailer, before/after files across five activation destinations; no holdout or truth set reported.",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F27",
  "headline": false,
  "claim": "ID5’s onboarding preview reports how many distinct input hashed emails had at least one match for each output identifier type.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S31"
  ],
  "passage": "the count and percentage of HEMs with at least one match",
  "support": [
   {
    "source_id": "IDN-C-S31",
    "passage": "the count and percentage of HEMs with at least one match",
    "locator": "§3 Match Test Output, first sentence and Fields table"
   }
  ],
  "scope_time": "Technical guide as read 2026-11-11; no measured cohort or period supplied",
  "scope_geo": "Integration documentation; no study geography specified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The October 2026 ID5 guide takes normalized SHA-256 email values. It divides distinct inputs with at least one match of the output type by all distinct inputs; it separately counts output IDs. The worked 8,000/10,000 row is labeled an example, not an observed US population.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer documents the representation. External verification and sample selection remain open.",
  "limitations": "A report definition applies to this onboarding output. The individual fields and the aggregate row use distinct input identifiers; no measured US client rate is taken from this example.",
  "final_wording": "ID5’s onboarding preview reports how many distinct input hashed emails had at least one match for each output identifier type.",
  "counterevidence": "A report definition applies to this onboarding output. The individual fields and the aggregate row use distinct input identifiers; no measured US client rate is taken from this example.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-C-F28",
  "headline": false,
  "claim": "In its 2024 presentation, Merkle advertised a match rate of at least 95% for DataSource consumer data to Data Cloud profiles, based on prior client performance.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S32"
  ],
  "passage": "[IDN-C-S32, Merkury Data Enhancement slide, headline] 95%+ MATCH-RATE OF DATASOURCE™ CONSUMER DATA TO DATA CLOUD PROFILES [IDN-C-S32, same slide, asterisk footnote] Results are based on prior performance of Merkle clients",
  "support": [
   {
    "source_id": "IDN-C-S32",
    "passage": "95%+ MATCH-RATE OF DATASOURCE™ CONSUMER DATA TO DATA CLOUD PROFILES",
    "locator": "Merkury Data Enhancement slide, headline"
   },
   {
    "source_id": "IDN-C-S32",
    "passage": "Results are based on prior performance of Merkle clients",
    "locator": "same slide, asterisk footnote"
   }
  ],
  "scope_time": "2024 presentation; cited prior-client observation period unspecified",
  "scope_geo": "Presentation names no case-specific country on this slide",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The original 2024 Adobe Summit deck, slide 10 in the identity match-rate talk, advertises 95%+ for DataSource consumer data matched to Data Cloud profiles. A footnote attributes the result to earlier Merkle clients. Neither case count, calendar period, country nor eligibility and acceptance rules appear on this slide. The two cited passages come from a single slide in a single issuer deck. Exact date of the earlier client measurements is unknown.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer documents the representation. External verification and sample selection remain open.",
  "limitations": "The slide footnote refers to prior Merkle clients. The case-level geography, exact input population, observation period and matching-rule configuration are not supplied on this slide. Do not infer which clients reached the figure.",
  "final_wording": "In its 2024 presentation, Merkle advertised a match rate of at least 95% for DataSource consumer data to Data Cloud profiles, based on prior client performance.",
  "counterevidence": "The slide footnote refers to prior Merkle clients. The case-level geography, exact input population, observation period and matching-rule configuration are not supplied on this slide. Do not infer which clients reached the figure.",
  "stream": "C",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-D-F01",
  "headline": false,
  "claim": "LiveRamp entered its merger agreement with MMS USA Holdings on May 16, 2026.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S01"
  ],
  "passage": "entered into an Agreement and Plan of Merger",
  "support": [
   {
    "source_id": "IDN-D-S01",
    "passage": "entered into an Agreement and Plan of Merger",
    "locator": "Item 1.01, first paragraph"
   }
  ],
  "scope_time": "2026-05-16",
  "scope_geo": "US/France",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The opening of Item 1.01 gives May 16, the acquired company and MMS USA. It also names Covey and Publicis in a limited contractual capacity. The 8-K was filed May 18; it describes an agreement subject to conditions. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "Signature establishes agreement only.",
  "final_wording": "LiveRamp entered its merger agreement with MMS USA Holdings on May 16, 2026.",
  "counterevidence": "Signature establishes agreement only.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F02",
  "headline": false,
  "claim": "Publicis Groupe’s wholly owned subsidiary MMS USA Holdings completed its acquisition of LiveRamp Holdings on November 2, 2026.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S02",
   "IDN-D-S03"
  ],
  "passage": "[IDN-D-S02, Introductory note, first paragraph] completed the previously announced acquisition of LiveRamp Holdings, Inc. [IDN-D-S03, Part III, Narrative] a wholly owned subsidiary of Publicis Groupe S.A.",
  "support": [
   {
    "source_id": "IDN-D-S02",
    "passage": "completed the previously announced acquisition of LiveRamp Holdings, Inc.",
    "locator": "Introductory note, first paragraph"
   },
   {
    "source_id": "IDN-D-S03",
    "passage": "a wholly owned subsidiary of Publicis Groupe S.A.",
    "locator": "Part III, Narrative"
   }
  ],
  "scope_time": "2026-11-02",
  "scope_geo": "US/France",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The November 2 closing 8-K identifies MMS USA as the acquiring parent and LiveRamp as its surviving direct wholly owned subsidiary. Part III of the separate November 10 late-filing form independently describes MMS USA as wholly owned by Publicis. The latter is not a quarterly financial report. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "Common ownership alone cannot establish a merger of identity namespaces or underlying edges.",
  "final_wording": "Publicis Groupe’s wholly owned subsidiary MMS USA Holdings completed its acquisition of LiveRamp Holdings on November 2, 2026.",
  "counterevidence": "Common ownership alone cannot establish a merger of identity namespaces or underlying edges.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F03",
  "headline": false,
  "claim": "At the closing, each qualifying outstanding LiveRamp common share converted to a right to $38.50 in cash.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S02"
  ],
  "passage": "$38.50 in cash, without interest",
  "support": [
   {
    "source_id": "IDN-D-S02",
    "passage": "$38.50 in cash, without interest",
    "locator": "Item 2.01, merger consideration"
   }
  ],
  "scope_time": "2026-11-02",
  "scope_geo": "US",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Item 2.01 sets US$38.50 cash without interest per eligible share immediately before the merger. Perfected appraisal shares and specified company/group-owned shares are expressly excepted. This is a share price, not deal enterprise value. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "The filing specifies exclusions, including shares with perfected appraisal rights. This is a per-share figure.",
  "final_wording": "At the closing, each qualifying outstanding LiveRamp common share converted to a right to $38.50 in cash.",
  "counterevidence": "The filing specifies exclusions, including shares with perfected appraisal rights. This is a per-share figure.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F04",
  "headline": false,
  "claim": "LiveRamp reported consolidated revenue of $812.9 million for the year ended March 31, 2026.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S04"
  ],
  "passage": "Total revenues were $812.9 million for the twelve months ended March 31, 2026",
  "support": [
   {
    "source_id": "IDN-D-S04",
    "passage": "Total revenues were $812.9 million for the twelve months ended March 31, 2026",
    "locator": "Item 7, Revenues, paragraph following revenue table"
   }
  ],
  "scope_time": "FY ended 2026-03-31",
  "scope_geo": "global consolidated",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Item 7 reports USD 812,940 thousand, rounded to USD 812.9 million. Subscription was 614,388 thousand and Marketplace and Other was 198,552 thousand. They sum to the consolidated worldwide total for the fiscal year ending March 31, 2026. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "The figure includes the subscription and marketplace businesses. It cannot be assigned to RampID or treated as US identity spend.",
  "final_wording": "LiveRamp reported consolidated revenue of $812.9 million for the year ended March 31, 2026.",
  "counterevidence": "The figure includes the subscription and marketplace businesses. It cannot be assigned to RampID or treated as US identity spend.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F05",
  "headline": false,
  "claim": "LiveRamp reported one operating segment in its fiscal 2026 annual financial statements.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S04"
  ],
  "passage": "the Company operates as one operating segment",
  "support": [
   {
    "source_id": "IDN-D-S04",
    "passage": "the Company operates as one operating segment",
    "locator": "Note on segment information, first sentence"
   }
  ],
  "scope_time": "FY ended 2026-03-31",
  "scope_geo": "global consolidated",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Note 16 and Item 7 describe the CEO evaluating the business as a single consolidated operating and reportable segment. The separate revenue categories do not create reportable product segments. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "Two revenue categories are tabulated separately. Neither is a RampID product segment.",
  "final_wording": "LiveRamp reported one operating segment in its fiscal 2026 annual financial statements.",
  "counterevidence": "Two revenue categories are tabulated separately. Neither is a RampID product segment.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F06",
  "headline": false,
  "claim": "Publicis announced the Lotame agreement in March 2025 and reported acquiring 100% of Lotame Solutions in April 2025.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S05",
   "IDN-D-S06"
  ],
  "passage": "[IDN-D-S05, opening paragraph] entered into an agreement to acquire Lotame [IDN-D-S06, Note 3.1, Acquisitions in financial year 2025, first bullet] in April 2025, 100% of Lotame Solutions, Inc.",
  "support": [
   {
    "source_id": "IDN-D-S05",
    "passage": "entered into an agreement to acquire Lotame",
    "locator": "opening paragraph"
   },
   {
    "source_id": "IDN-D-S06",
    "passage": "in April 2025, 100% of Lotame Solutions, Inc.",
    "locator": "Note 3.1, Acquisitions in financial year 2025, first bullet"
   }
  ],
  "scope_time": "2025-03 to 2025-04",
  "scope_geo": "US/France",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The March 6 release announces an agreement. Note 3.1 of the 2025 consolidated accounts says Publicis acquired 100% of Lotame Solutions, Inc., in April; the same table lists EUR 122 million in cash consideration. No daily close date follows. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "The annual accounts supply the month of acquisition. A precise closing day is not established here.",
  "final_wording": "Publicis announced the Lotame agreement in March 2025 and reported acquiring 100% of Lotame Solutions in April 2025.",
  "counterevidence": "The annual accounts supply the month of acquisition. A precise closing day is not established here.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F07",
  "headline": false,
  "claim": "Publicis reported closing its Epsilon acquisition on July 2, 2019.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S07",
   "IDN-DV-S01"
  ],
  "passage": "completion of the acquisition of data-driven marketing company, Epsilon, from Alliance Data Systems Corporation",
  "support": [
   {
    "source_id": "IDN-D-S07",
    "passage": "completion of the acquisition of data-driven marketing company, Epsilon, from Alliance Data Systems Corporation",
    "locator": "page 1, opening paragraph"
   }
  ],
  "scope_time": "2019-07-01 close; 2019-07-02 announcement",
  "scope_geo": "US/France",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "contradicted",
  "review_note": "Publicis announced completion on July 2. Alliance Data’s item 8.01 says the sellers completed the Epsilon sale to Publicis and its subsidiaries on July 1. The buyer’s release alone does not date the underlying close. The corrected close date is supplied directly by the seller’s 8-K. The July 2 buyer announcement remains a party release. The original is recorded as a July 2 event. The buyer’s announcement only says the acquisition was completed; it does not report July 2 as the close. The seller’s 8-K affirmatively dates the close to July 1.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "Historical acquisition scope; it does not establish the lineage of any later graph.",
  "final_wording": "Alliance Data’s filing dates the sale of Epsilon to Publicis to July 1, 2019. Publicis announced completion on July 2.",
  "counterevidence": "Historical acquisition scope; it does not establish the lineage of any later graph.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F08",
  "headline": false,
  "claim": "In its November 2, 2026 closing announcement, Publicis described RampID and Epsilon identity as inputs to a combined client data offering.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S08"
  ],
  "passage": "enrich their first-party data with RampID and Epsilon’s Identity",
  "support": [
   {
    "source_id": "IDN-D-S08",
    "passage": "enrich their first-party data with RampID and Epsilon’s Identity",
    "locator": "section 1, Immediate Scale & Activation"
   }
  ],
  "scope_time": "2026-11-02",
  "scope_geo": "global group statement",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Publicis’s November 2 announcement expressly describes using RampID and Epsilon Identity to enrich client first-party data. The record verifies what Publicis marketed, not customer activation, common code or graph accuracy. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "One marketed integration does not prove that the identifiers resolve through the same historic graph.",
  "final_wording": "In its November 2, 2026 closing announcement, Publicis described RampID and Epsilon identity as inputs to a combined client data offering.",
  "counterevidence": "One marketed integration does not prove that the identifiers resolve through the same historic graph.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-D-F09",
  "headline": false,
  "claim": "ID5 announced its acquisition of TrueData in an October 30, 2025 datelined statement and subsequently described the deal as completed.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S09",
   "IDN-D-S10"
  ],
  "passage": "[IDN-D-S09, opening paragraph, October 30 dateline] announced the acquisition of TrueData [IDN-D-S10, second paragraph] ID5 acquired the company formerly known as TrueData",
  "support": [
   {
    "source_id": "IDN-D-S09",
    "passage": "announced the acquisition of TrueData",
    "locator": "opening paragraph, October 30 dateline"
   },
   {
    "source_id": "IDN-D-S10",
    "passage": "ID5 acquired the company formerly known as TrueData",
    "locator": "second paragraph"
   }
  ],
  "scope_time": "2025-10-30 to 2026-10-01",
  "scope_geo": "US/UK",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The first ID5 release carries an October 30 London/New York dateline but November 4 page header. Its October 1, 2026 statement explicitly says ID5 acquired the formerly named TrueData company. ID5 is the buyer in the first transaction. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "The English-language page was posted November 4. This acquisition does not by itself trace a specific historical edge set.",
  "final_wording": "ID5 announced its acquisition of TrueData in an October 30, 2025 datelined statement and subsequently described the deal as completed.",
  "counterevidence": "The English-language page was posted November 4. This acquisition does not by itself trace a specific historical edge set.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F10",
  "headline": false,
  "claim": "On October 1, 2026, ID5 said Cloud Technologies had bought TrueData’s third-party audience business and the TrueData brand.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S10"
  ],
  "passage": "acquired TrueData’s third-party audience business, along with the TrueData brand",
  "support": [
   {
    "source_id": "IDN-D-S10",
    "passage": "acquired TrueData’s third-party audience business, along with the TrueData brand",
    "locator": "opening paragraph"
   }
  ],
  "scope_time": "2026-10-01",
  "scope_geo": "North America",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "ID5 attributes the audience business and brand acquisition to Cloud Technologies and says that business will keep operating in North America under the TrueData brand. The description does not establish a transfer of ID5’s whole identity business. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "The specified perimeter is an audience business and trademark. The transaction description does not assign ID5’s identity operation to the buyer.",
  "final_wording": "On October 1, 2026, ID5 said Cloud Technologies had bought TrueData’s third-party audience business and the TrueData brand.",
  "counterevidence": "The specified perimeter is an audience business and trademark. The transaction description does not assign ID5’s identity operation to the buyer.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F11",
  "headline": false,
  "claim": "Experian reported acquiring Audigent on December 4, 2024, and its annual report identifies the purchase as 100% of the equity.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S11",
   "IDN-D-S12"
  ],
  "passage": "[IDN-D-S11, opening paragraph, Costa Mesa dateline] announced today it has acquired Audigent [IDN-D-S12, Board activities; also see page 111] acquisition of 100% of the equity share capital of Audigent",
  "support": [
   {
    "source_id": "IDN-D-S11",
    "passage": "announced today it has acquired Audigent",
    "locator": "opening paragraph, Costa Mesa dateline"
   },
   {
    "source_id": "IDN-D-S12",
    "passage": "acquisition of 100% of the equity share capital of Audigent",
    "locator": "Board activities; also see page 111"
   }
  ],
  "scope_time": "2024-12-04",
  "scope_geo": "US/Experian group",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Experian’s December 4 dateline says the purchase had occurred. The annual report identifies board approval in November, and note 41 says the group bought all of Predictive Pop, Inc. (Audigent) on December 4, 2024. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "The transaction joined businesses. It does not establish a single purchasable graph or prove the origin of any targetable cohort.",
  "final_wording": "Experian reported acquiring Audigent on December 4, 2024, and its annual report identifies the purchase as 100% of the equity.",
  "counterevidence": "The transaction joined businesses. It does not establish a single purchasable graph or prove the origin of any targetable cohort.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F12",
  "headline": false,
  "claim": "TransUnion and Neustar reported a $3.1 billion closing on December 1, 2021, and expressly excluded Neustar Security Services.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S13",
   "IDN-DV-S03"
  ],
  "passage": "[IDN-D-S13, first paragraph] completed its $3.1 billion acquisition of Neustar [IDN-D-S13, fourth paragraph] Neustar Security Services, is excluded from the transaction",
  "support": [
   {
    "source_id": "IDN-D-S13",
    "passage": "completed its $3.1 billion acquisition of Neustar",
    "locator": "first paragraph"
   },
   {
    "source_id": "IDN-D-S13",
    "passage": "Neustar Security Services, is excluded from the transaction",
    "locator": "fourth paragraph"
   }
  ],
  "scope_time": "2021-12-01",
  "scope_geo": "US",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The parties’ December 1 release states USD 3.1 billion and excludes Neustar Security Services. TransUnion’s separate filed exhibit confirms the December 1 closing and defines the acquired business as marketing, risk and communications. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "Transaction perimeter is distinct from the later TruAudience SKU or CTV-specific commercial terms.",
  "final_wording": "TransUnion and Neustar reported a $3.1 billion closing on December 1, 2021, and expressly excluded Neustar Security Services.",
  "counterevidence": "Transaction perimeter is distinct from the later TruAudience SKU or CTV-specific commercial terms.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F13",
  "headline": false,
  "claim": "IPG’s October 1, 2018 Acxiom transaction excluded LiveRamp.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S14",
   "IDN-DV-S02"
  ],
  "passage": "[IDN-D-S14, paragraph 1] has completed its acquisition of Acxiom LLC [IDN-D-S14, Opening paragraph, final sentence (October 1, 2018)] the transaction does not include the LiveRamp business",
  "support": [
   {
    "source_id": "IDN-D-S14",
    "passage": "has completed its acquisition of Acxiom LLC",
    "locator": "paragraph 1"
   },
   {
    "source_id": "IDN-D-S14",
    "passage": "the transaction does not include the LiveRamp business",
    "locator": "Opening paragraph, final sentence (October 1, 2018)"
   }
  ],
  "scope_time": "2018-10-01",
  "scope_geo": "US",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The October 1 release excludes LiveRamp. Item 2.01 of IPG’s October 2 amended 8-K explains that Acxiom distributed its LiveRamp interests to Holdco and IPG acquired all the equity of the entity holding Marketing Solutions. The filed transaction disclosure substantiates the direct-record label. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "This historical asset purchase explains why the old corporate name cannot be used to combine the later identity products.",
  "final_wording": "IPG’s October 1, 2018 Acxiom transaction excluded LiveRamp.",
  "counterevidence": "This historical asset purchase explains why the old corporate name cannot be used to combine the later identity products.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F14",
  "headline": false,
  "claim": "Omnicom reported closing the Interpublic acquisition on November 26, 2025 and subsequently named Acxiom RealID in its media strategy.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S15",
   "IDN-D-S16"
  ],
  "passage": "[IDN-D-S15, opening paragraph] successful completion of its acquisition of The Interpublic Group of Companies, Inc. [IDN-D-S16, strategy, Strongest Media Ecosystem] powered by Acxiom RealID™ and advanced ID-less solutions",
  "support": [
   {
    "source_id": "IDN-D-S15",
    "passage": "successful completion of its acquisition of The Interpublic Group of Companies, Inc.",
    "locator": "opening paragraph"
   },
   {
    "source_id": "IDN-D-S16",
    "passage": "powered by Acxiom RealID™ and advanced ID-less solutions",
    "locator": "strategy, Strongest Media Ecosystem"
   }
  ],
  "scope_time": "2025-11-26 to 2025-12-01",
  "scope_geo": "US/global",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The November 26 party release reports the closing after conditions and approvals. The December 1 strategy release specifically names Acxiom RealID as powering the media strategy. The second is management’s product statement. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "This is the buyer’s own description. No product accuracy, cross-client reach or continuity evidence is inferred.",
  "final_wording": "Omnicom reported closing the Interpublic acquisition on November 26, 2025 and subsequently named Acxiom RealID in its media strategy.",
  "counterevidence": "This is the buyer’s own description. No product accuracy, cross-client reach or continuity evidence is inferred.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F15",
  "headline": false,
  "claim": "At the September 1, 2021 closing, Apollo said Yahoo would operate under Apollo Funds and Verizon retained 10%.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S17",
   "IDN-DV-S04"
  ],
  "passage": "Yahoo will now operate as a standalone company under Apollo Funds. Verizon has retained a 10% stake in Yahoo.",
  "support": [
   {
    "source_id": "IDN-D-S17",
    "passage": "Yahoo will now operate as a standalone company under Apollo Funds. Verizon has retained a 10% stake in Yahoo.",
    "locator": "page 1, first paragraph"
   }
  ],
  "scope_time": "2021-09-01",
  "scope_geo": "US/global",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Apollo’s September 1 release describes the closing by affiliate-managed funds and the retained 10% stake. Verizon’s financial statements confirm September 1 and identify 10% of fully diluted common limited partnership units in the Apollo affiliate. This is the interest at closing. Checked transaction parties, timing and units against the reopened record.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "A historical stake at closing does not establish the current percentage or the economics of ConnectID.",
  "final_wording": "At the September 1, 2021 closing, Apollo said Yahoo would operate under Apollo Funds and Verizon retained 10%.",
  "counterevidence": "A historical stake at closing does not establish the current percentage or the economics of ConnectID.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-D-F16",
  "headline": false,
  "claim": "The Trade Desk’s FY2025 filing defines gross spend using client inventory, value-added services, data and the platform fee.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S18"
  ],
  "passage": "Gross spend measures the amount of a client’s spend on our platform for advertising inventory, value-added services and data",
  "support": [
   {
    "source_id": "IDN-D-S18",
    "passage": "Gross spend measures the amount of a client’s spend on our platform for advertising inventory, value-added services and data",
    "locator": "Item 7, Executive Summary, Highlights, gross spend footnote (1)"
   }
  ],
  "scope_time": "FY ended 2025-12-31",
  "scope_geo": "global consolidated",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "Item 7 defines gross spend as amounts clients spend on inventory, value-added services and data on the platform plus the platform fee. This is the client’s spend on inventory. The company’s separate consolidated FY2025 revenue is USD 2,896,284 thousand. Neither measure is UID2 revenue. The unit is client spending on inventory, not inventory belonging to clients.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named issuer explicitly reports the event, figures or representation for this scope.",
  "limitations": "This metric includes several types of spend. The cited filing table cannot be used as a measure of UID2 revenue or market share.",
  "final_wording": "The Trade Desk defines gross spend in its FY2025 filing as clients’ spending on advertising inventory, value-added services and data on its platform, plus its platform fee.",
  "counterevidence": "This metric includes several types of spend. The cited filing table cannot be used as a measure of UID2 revenue or market share.",
  "stream": "D",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-E-F01",
  "headline": false,
  "claim": "On April 22, 2025 Google retained Chrome’s existing third-party-cookie choice and declined to introduce a separate prompt.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S01"
  ],
  "passage": "[IDN-E-S01, April 22 post, paragraph beginning “Taking all of these factors”] maintain our current approach to offering users third-party cookie choice in Chrome [IDN-E-S01, April 22 post, paragraph beginning “Taking all of these factors”] not be rolling out a new standalone prompt",
  "support": [
   {
    "source_id": "IDN-E-S01",
    "passage": "maintain our current approach to offering users third-party cookie choice in Chrome",
    "locator": "April 22 post, paragraph beginning “Taking all of these factors”"
   },
   {
    "source_id": "IDN-E-S01",
    "passage": "not be rolling out a new standalone prompt",
    "locator": "April 22 post, paragraph beginning “Taking all of these factors”"
   }
  ],
  "scope_time": "2025-04-22",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Google’s April 22, 2025 post retains users’ Chrome privacy-settings choice for third-party cookies and rules out the proposed additional standalone prompt. It separately says Incognito already blocked third-party cookies by default.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Settings and Incognito are distinct. This announcement gives no cookie-use rate.",
  "final_wording": "On April 22, 2025 Google retained Chrome’s existing third-party-cookie choice and declined to introduce a separate prompt.",
  "counterevidence": "Settings and Incognito are distinct. This announcement gives no cookie-use rate.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F02",
  "headline": false,
  "claim": "Google’s October decision selected named Privacy Sandbox features for retirement through Chrome and Android processes while continuing support for CHIPS and FedCM.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S02"
  ],
  "passage": "[IDN-E-S02, October 17 post, paragraphs beginning “CHIPS”, “After evaluating” and “We will follow”] We will follow Chrome and Android processes for phasing out these technologies [IDN-E-S02, October 17 post, paragraph beginning “CHIPS”] We'll continue to support those APIs",
  "support": [
   {
    "source_id": "IDN-E-S02",
    "passage": "We will follow Chrome and Android processes for phasing out these technologies",
    "locator": "October 17 post, paragraphs beginning “CHIPS”, “After evaluating” and “We will follow”"
   },
   {
    "source_id": "IDN-E-S02",
    "passage": "We'll continue to support those APIs",
    "locator": "October 17 post, paragraph beginning “CHIPS”"
   }
  ],
  "scope_time": "2025-10-17",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "On October 17, 2025 Google named the APIs to phase out under separate web and Android processes. It expressly retained CHIPS and FedCM and said it would maintain Private State Tokens. This establishes an announcement about named technologies.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The announcement is a decision. Actual release effects must be traced by feature, browser and operating system.",
  "final_wording": "Google’s October decision selected named Privacy Sandbox features for retirement through Chrome and Android processes while continuing support for CHIPS and FedCM.",
  "counterevidence": "The announcement is a decision. Actual release effects must be traced by feature, browser and operating system.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F03",
  "headline": false,
  "claim": "Chrome 144 described removal of Private Aggregation as planned; Chrome 152 later recorded its removal.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S03",
   "IDN-E-S04"
  ],
  "passage": "[IDN-E-S03, Chrome 144 / Deprecations and removals / Private Aggregation] Chrome plans to deprecate and remove the Private Aggregation API [IDN-E-S04, Chrome 152, Deprecations and removals / Remove Private Aggregation API] the Private Aggregation API is deprecated and removed",
  "support": [
   {
    "source_id": "IDN-E-S03",
    "passage": "Chrome plans to deprecate and remove the Private Aggregation API",
    "locator": "Chrome 144 / Deprecations and removals / Private Aggregation"
   },
   {
    "source_id": "IDN-E-S04",
    "passage": "the Private Aggregation API is deprecated and removed",
    "locator": "Chrome 152, Deprecations and removals / Remove Private Aggregation API"
   }
  ],
  "scope_time": "Chrome 144: 2026-01-13; Chrome 152: 2026-08-25",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Chrome 144’s January 13 release notes use prospective language for Private Aggregation. Chrome 152’s August 25, 2026 release notes state that the API was removed. The notes apply to the named stable Chrome platforms and do not settle all other Sandbox APIs. The scope includes both the January and August 2026 release dates.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The two records cover Private Aggregation; product-specific schedules differ.",
  "final_wording": "Chrome 144 described removal of Private Aggregation as planned; Chrome 152 later recorded its removal.",
  "counterevidence": "The two records cover Private Aggregation; product-specific schedules differ.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F04",
  "headline": false,
  "claim": "A July Chromium commit reported that Topics’ web-exposed interfaces had already become stubs.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S05"
  ],
  "passage": "with web-exposed APIs turned into stubs.",
  "support": [
   {
    "source_id": "IDN-E-S05",
    "passage": "with web-exposed APIs turned into stubs.",
    "locator": "Commit d37e2f6, message lines 35–40"
   }
  ],
  "scope_time": "2026-07-31",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Chromium’s July 31, 2026 Topics cleanup records prior disabling and web API stubs. The change retains one feature flag to control staged stub removal. Its timestamp is a source-tree event, not an estimate of the proportion of Stable clients.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Source tree evidence does not fix an all-users removal date.",
  "final_wording": "A July Chromium commit reported that Topics’ web-exposed interfaces had already become stubs.",
  "counterevidence": "Source tree evidence does not fix an all-users removal date.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F05",
  "headline": false,
  "claim": "Chromium’s July 14 Protected Audience change replaced renderer behavior, including runAdAuction, with rejected promises or default values.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S06",
   "IDN-EV-S01"
  ],
  "passage": "Audience renderer APIs, returning rejected promises or default values.",
  "support": [
   {
    "source_id": "IDN-E-S06",
    "passage": "Audience renderer APIs, returning rejected promises or default values.",
    "locator": "Commit 4bcc11c, message lines 33–37"
   }
  ],
  "scope_time": "2026-07-14",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The July 14, 2026 Chromium change replaced Protected Audience renderer functions including runAdAuction with rejections or default responses. A later October 30 main-branch commit removed remaining stubbed bindings and runtime features. Neither commit dates completion on all deployed browsers. The July finding is historically correct. The October commit advances the repository status without proving a universal Stable rollout.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "A merged renderer change does not establish every stable user’s deployment date.",
  "final_wording": "Chromium’s July 14 Protected Audience change replaced renderer behavior, including runAdAuction, with rejected promises or default values.",
  "counterevidence": "A merged renderer change does not establish every stable user’s deployment date.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F06",
  "headline": false,
  "claim": "Chromium’s July 14 Attribution Reporting change retained the XMLHttpRequest setter as a no-op.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S07"
  ],
  "passage": "XMLHttpRequest.setAttributionReporting()` is preserved as a no-op stub.",
  "support": [
   {
    "source_id": "IDN-E-S07",
    "passage": "XMLHttpRequest.setAttributionReporting()` is preserved as a no-op stub.",
    "locator": "Commit d7a74fd, message bullet about XMLHttpRequest"
   }
  ],
  "scope_time": "2026-07-14",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The July 14, 2026 Blink renderer cleanup keeps XMLHttpRequest.setAttributionReporting as a no-op. Other entry points including attributionsrc, window.open and fetch parameters were handled separately. The statement describes that revision.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "One renderer method; a retained name does not establish that conversion reports were generated.",
  "final_wording": "Chromium’s July 14 Attribution Reporting change retained the XMLHttpRequest setter as a no-op.",
  "counterevidence": "One renderer method; a retained name does not establish that conversion reports were generated.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F07",
  "headline": false,
  "claim": "In a September project update, the Topics engineers reported that the stable stub-removal trial had reached 1% on milestone 153 and later.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S19",
   "IDN-E-S05"
  ],
  "passage": "We have reached 1% on Stable (M153+)",
  "support": [
   {
    "source_id": "IDN-E-S19",
    "passage": "We have reached 1% on Stable (M153+)",
    "locator": "September 24, 2026 post, paragraph beginning “We have reached”"
   }
  ],
  "scope_time": "2026-09-24",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The September 24 Topics owner post reports a 1% Stable stub-removal trial on Chrome M153+ and requests further stages, with a target after October 15 for 100% Stable. It separately cites a usage metric. The 1% is trial rollout on the named Stable versions, not API adoption or all web traffic. One percent is a Stable field-trial share on M153+. The thread has no device count or geographical breakdown.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The percentage is the team’s trial rollout on the specified Stable versions. Its geography and device count are not reported. It is not adoption or use share.",
  "final_wording": "In a September project update, the Topics engineers reported that the stable stub-removal trial had reached 1% on milestone 153 and later.",
  "counterevidence": "The percentage is the team’s trial rollout on the specified Stable versions. Its geography and device count are not reported. It is not adoption or use share.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F08",
  "headline": false,
  "claim": "In October, the Attribution Reporting team distinguished a window-opening compatibility fix already deployed in Chrome 155 Stable from a proposed later rollout to all Stable users.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S20",
   "IDN-E-S07"
  ],
  "passage": "This fix has been fully verified and rolled out to Stable in M155.",
  "support": [
   {
    "source_id": "IDN-E-S20",
    "passage": "This fix has been fully verified and rolled out to Stable in M155.",
    "locator": "October 8 exchange, rollout schedule and correction for window.open()"
   }
  ],
  "scope_time": "2026-10-08",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "The October 8 author separates a fix for window.open with attributionsrc, deployed in M155 Stable, from the remaining staged Attribution Reporting rollout. Ten percent Stable was to be held through October 24, with 100% targeted later. The thread records approval, without a completion report. Three later approvals in the thread cover the proposal. No completion percentage is inferred.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The target for 100% was a plan; this record does not certify completion by the cutoff.",
  "final_wording": "On October 8, 2026, the Attribution Reporting team reported that its window.open compatibility fix had reached Chrome 155 Stable. It proposed a staged rollout of the remaining API removal to 100% of Stable after October 24.",
  "counterevidence": "The target for 100% was a plan; this record does not certify completion by the cutoff.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F09",
  "headline": false,
  "claim": "Google’s mobile-ads SDK guidance dates the Android Privacy Sandbox deprecation to October 17, 2025.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S08",
   "IDN-E-S02"
  ],
  "passage": "As of October 17, 2025, Privacy Sandbox on Android is deprecated.",
  "support": [
   {
    "source_id": "IDN-E-S08",
    "passage": "As of October 17, 2025, Privacy Sandbox on Android is deprecated.",
    "locator": "Caution before Privacy-Preserving APIs"
   }
  ],
  "scope_time": "2025-10-17",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The Android Ad Manager SDK page dates deprecation to October 17, 2025; its current footer says November 9, 2026. It still lists APIs and SDK permissions. Deprecation does not date rejection on every Android installation. The recorded deprecation event remains October 17, 2025. The current documentation footer reads November 9, 2026, superseding the stored November 4 date.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Does not establish a device-level removal date or say Android Advertising ID was retired.",
  "final_wording": "Google’s mobile-ads SDK guidance dates the Android Privacy Sandbox deprecation to October 17, 2025.",
  "counterevidence": "Does not establish a device-level removal date or say Android Advertising ID was retired.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F10",
  "headline": false,
  "claim": "The Android API reference marks Topics classes deprecated at API level 37 and describes future rejection of calls.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S09"
  ],
  "passage": "Developers should stop using them, as calls will be rejected in future Android releases.",
  "support": [
   {
    "source_id": "IDN-E-S09",
    "passage": "Developers should stop using them, as calls will be rejected in future Android releases.",
    "locator": "android.adservices.topics, Classes / GetTopicsRequest and TopicsManager"
   }
  ],
  "scope_time": "API level 37; reference updated 2026-08-03",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The android.adservices.topics class list marks the named classes deprecated at API level 37 and warns calls will be rejected in future Android releases. It gives no direct replacement or single delivery date for rejection.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "A future rejection does not mean every device at this level rejected the call.",
  "final_wording": "The Android API reference marks Topics classes deprecated at API level 37 and describes future rejection of calls.",
  "counterevidence": "A future rejection does not mean every device at this level rejected the call.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F11",
  "headline": false,
  "claim": "Google scoped the IP Protection design to third-party requests to listed domains in Incognito.",
  "chapter": "",
  "source_ids": [
   "IDN-E-S10",
   "IDN-E-S02"
  ],
  "passage": "for domains listed in Masked Domain List (MDL).",
  "support": [
   {
    "source_id": "IDN-E-S10",
    "passage": "for domains listed in Masked Domain List (MDL).",
    "locator": "IP Protection overview, explanation and first-party exclusion"
   }
  ],
  "scope_time": "Design page updated 2025-10-27",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The design page limits IP masking to eligible third-party requests in Chrome Incognito for domains on the Masked Domain List. The scheme excludes first-party requests even for listed domains and uses two proxies. The October retirement decision covers this technology.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "October retirement decision applies to IP Protection. Neither record proves universal IP masking or subsequent formal removal from every build.",
  "final_wording": "Google scoped the IP Protection design to third-party requests to listed domains in Incognito.",
  "counterevidence": "October retirement decision applies to IP Protection. Neither record proves universal IP masking or subsequent formal removal from every build.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F12",
  "headline": false,
  "claim": "After a user deletes the Android advertising ID, Google Play services describes returning zeros to attempts to access it.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S11"
  ],
  "passage": "Any attempts to access the identifier will receive a string of zeros instead of the identifier.",
  "support": [
   {
    "source_id": "IDN-E-S11",
    "passage": "Any attempts to access the identifier will receive a string of zeros instead of the identifier.",
    "locator": "Google Play services update in 2021"
   }
  ],
  "scope_time": "Android 12 rollout from late 2021; scope expansion scheduled from 2022-04-01",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The Google Play services help page states that deleting the advertising ID in Android Settings causes subsequent access attempts to receive a string of zeroes. It distinguishes reset from deletion, the late-2021/2022 phased rollout and the Android 13+ manifest permission.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Device advertising ID is distinct from Sandbox Topics and from an IP address.",
  "final_wording": "After a user deletes the Android advertising ID, Google Play services describes returning zeros to attempts to access it.",
  "counterevidence": "Device advertising ID is distinct from Sandbox Topics and from an IP address.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-E-F13",
  "headline": false,
  "claim": "For the 14.5 releases of iOS, iPadOS and tvOS, Apple required apps to request permission for tracking or access to the advertising identifier, effective April 26, 2021.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S12"
  ],
  "passage": "use the AppTrackingTransparency framework to request the user’s permission to track them or to access their device's advertising identifier.",
  "support": [
   {
    "source_id": "IDN-E-S12",
    "passage": "use the AppTrackingTransparency framework to request the user’s permission to track them or to access their device's advertising identifier.",
    "locator": "April 20 developer notice, first and second paragraphs"
   }
  ],
  "scope_time": "Effective 2021-04-26",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Apple’s April 20 notice ties the ATT requirement to iOS, iPadOS and tvOS 14.5 and makes it effective April 26, 2021. All apps need permission to track or access IDFA; without permission the IDFA is zeroes.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The unit is an app permission. This is distinct from Safari cookie handling.",
  "final_wording": "For the 14.5 releases of iOS, iPadOS and tvOS, Apple required apps to request permission for tracking or access to the advertising identifier, effective April 26, 2021.",
  "counterevidence": "The unit is an app permission. This is distinct from Safari cookie handling.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-E-F14",
  "headline": false,
  "claim": "In March 2020 WebKit announced default blocking of cross-site cookies in Safari 13.1 on macOS and the iOS/iPadOS 13.4 updates.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S13"
  ],
  "passage": "Cookies for cross-site resources are now blocked by default across the board.",
  "support": [
   {
    "source_id": "IDN-E-S13",
    "passage": "Cookies for cross-site resources are now blocked by default across the board.",
    "locator": "Full Third-Party Cookie Blocking, introduction and first paragraph"
   }
  ],
  "scope_time": "2020-03-24",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "WebKit’s March 24, 2020 announcement covers Safari 13.1 on macOS and iOS/iPadOS 13.4, with a default block on cookies for cross-site resources. It also describes a user-mediated Storage Access API path for authenticated embeds.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "WebKit also described the Storage Access API for authenticated embeds subject to user control.",
  "final_wording": "In March 2020 WebKit announced default blocking of cross-site cookies in Safari 13.1 on macOS and the iOS/iPadOS 13.4 updates.",
  "counterevidence": "WebKit also described the Storage Access API for authenticated embeds subject to user control.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F15",
  "headline": false,
  "claim": "In its OS 27 releases, WebKit says Safari and WebKit block network access to identity-resolution infrastructure at domain level.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S14",
   "IDN-E-S16"
  ],
  "passage": "Safari and WebKit block network access to identity resolution infrastructure to prevent cross-site tracking.",
  "support": [
   {
    "source_id": "IDN-E-S14",
    "passage": "Safari and WebKit block network access to identity resolution infrastructure to prevent cross-site tracking.",
    "locator": "What We Are Doing To Protect Users Against Identity Resolution, first paragraph"
   }
  ],
  "scope_time": "OS 27 releases; WebKit article 2026-10-19",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "WebKit’s October 19, 2026 post explicitly names iOS, iPadOS, macOS and visionOS 27. It describes domain-level network blocking of third-party identity-resolution infrastructure serving cross-site tracking. It does not supply a full list of affected companies or describe all first-party personalization as blocked.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "This record has no complete product/domain inventory and gives no reach-loss estimate.",
  "final_wording": "On October 19, 2026, WebKit reported that Safari and WebKit on iOS, iPadOS, macOS and visionOS 27 block network requests at the domain level to third-party identity-resolution infrastructure used for cross-site tracking.",
  "counterevidence": "This record has no complete product/domain inventory and gives no reach-loss estimate.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F16",
  "headline": false,
  "claim": "UID2’s publisher guide identifies client-side requests to uidapi.com as blocked on the specified iOS 27 and macOS 27 browser paths.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S16",
   "IDN-E-S14"
  ],
  "passage": "WebKit blocks client-side requests to `uidapi.com`.",
  "support": [
   {
    "source_id": "IDN-E-S16",
    "passage": "WebKit blocks client-side requests to `uidapi.com`.",
    "locator": "Client-side integration guide for Prebid.js, Web integration limitations on iOS 27 and macOS 27"
   }
  ],
  "scope_time": "Guide last updated 2026-11-11; accessed 2026-11-11",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The UID2 Prebid.js client-side guide identifies every browser on iOS 27 or later and Safari on macOS 27 or later. It says requests to uidapi.com, client-side token generation and refresh are affected and gives server-side alternatives. The reopened page’s footer is November 11. WebKit’s own post confirms domain-level blocking but does not name uidapi.com. The live footer says November 11, 2026, not November 5. These are vendor integration instructions, not tests in every affected browser.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The guide distinguishes all affected iOS browsers from Safari on macOS and gives a server-only alternative; no claim about all UID2 deployments.",
  "final_wording": "UID2’s Prebid.js guide says that client-side requests to uidapi.com are blocked in all browsers on iOS 27 or later and in Safari on macOS 27 or later. It directs affected publishers to a server-side integration.",
  "counterevidence": "The guide distinguishes all affected iOS browsers from Safari on macOS and gives a server-only alternative; no claim about all UID2 deployments.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F17",
  "headline": false,
  "claim": "Mozilla describes Firefox Total Cookie Protection as maintaining a separate cookie store for each website the user visits.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S15"
  ],
  "passage": "creating a separate “cookie jar” for each website you visit.",
  "support": [
   {
    "source_id": "IDN-E-S15",
    "passage": "creating a separate “cookie jar” for each website you visit.",
    "locator": "What is Total Cookie Protection?, opening explanation"
   }
  ],
  "scope_time": "June 2022 default rollout report, updated August 2024",
  "scope_geo": "Browser or OS product scope; no geographic percentage",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Mozilla’s June 14, 2022 post, updated August 28, 2024, describes a separate jar assigned to each visited website, also for cookies set by embedded third parties. This is a top-level-site partitioning mechanism.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Partitioning may retain within-site functionality. The record does not measure a particular identity provider.",
  "final_wording": "Mozilla describes Firefox Total Cookie Protection as maintaining a separate cookie store for each website the user visits.",
  "counterevidence": "Partitioning may retain within-site functionality. The record does not measure a particular identity provider.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F18",
  "headline": false,
  "claim": "ID5 documents an integration that synchronizes with ad-tech vendors while third-party cookies are available.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S17",
   "IDN-E-S21",
   "IDN-E-S23"
  ],
  "passage": "While third-party cookies are still in use, ID5 can synchronize with ad tech vendors",
  "support": [
   {
    "source_id": "IDN-E-S17",
    "passage": "While third-party cookies are still in use, ID5 can synchronize with ad tech vendors",
    "locator": "Initiate Cookie Sync to ID5 / Process Overview"
   }
  ],
  "scope_time": "2026-04-24",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "ID5’s April 24, 2026 instructions describe syncing with partners through a redirect pixel when third-party cookies are available. The page also describes automatic sync with its JavaScript API and a configurable cascade limit. No path-level traffic, policy-induced increase or market share is measured.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The guide describes this sync route; it does not require it for every ID5 publisher integration.",
  "final_wording": "ID5 documents an integration that synchronizes with ad-tech vendors while third-party cookies are available.",
  "counterevidence": "The guide describes this sync route; it does not require it for every ID5 publisher integration.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F19",
  "headline": false,
  "claim": "LiveRamp’s cookie-to-RampID file guide instructs recipients to enable a cookie sync through a pixel.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S18"
  ],
  "passage": "You enable this by implementing a cookie sync with us through the use of a pixel.",
  "support": [
   {
    "source_id": "IDN-E-S18",
    "passage": "You enable this by implementing a cookie sync with us through the use of a pixel.",
    "locator": "RampID Mapping Files / cookie file and site traffic"
   }
  ],
  "scope_time": "Version read 2026-11-11",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "LiveRamp says that the cookie-to-RampID file relies on collecting site traffic via pixel-based cookie sync, with a 90-day lookback. The main page and its Mapping File Types section display October 15, 2025 as their modification date. Other kinds of mapping file use different inputs. The document carries dated metadata for October 15, 2025. A single modified date earlier than the October announcement cannot establish a before/after change.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Applies to the cookie mapping file, not the alternative mobile-ID or CTV file or all ATS integrations.",
  "final_wording": "LiveRamp’s cookie-to-RampID file guide instructs recipients to enable a cookie sync through a pixel.",
  "counterevidence": "Applies to the cookie mapping file, not the alternative mobile-ID or CTV file or all ATS integrations.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F20",
  "headline": false,
  "claim": "Three versioned ID5 publisher SDK guides spanning both 2025 Google announcements give the same maxCascades default of eight cookie syncs and the same disable value of minus one.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S21",
   "IDN-E-S22",
   "IDN-E-S23"
  ],
  "passage": "[IDN-E-S21, README / Configuration table / maxCascades] A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified [IDN-E-S22, README / Configuration table / maxCascades] A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified [IDN-E-S23, README / Configuration table / maxCascades] A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified",
  "support": [
   {
    "source_id": "IDN-E-S21",
    "passage": "A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified",
    "locator": "README / Configuration table / maxCascades"
   },
   {
    "source_id": "IDN-E-S22",
    "passage": "A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified",
    "locator": "README / Configuration table / maxCascades"
   },
   {
    "source_id": "IDN-E-S23",
    "passage": "A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified",
    "locator": "README / Configuration table / maxCascades"
   }
  ],
  "scope_time": "2025-04-18, 2025-10-15, 2026-11-06",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "Each pinned ID5 README defines maxCascades as a ceiling when user sync is required, default 8 and disabled at −1. Repository commit timestamps are April 18, 2025, October 15, 2025 and November 6, 2026. These are the same path at the three boundaries. The parameter does not report how many syncs occur or establish primacy for US Chrome. The ceiling is conditional. Repository dates do not measure browser traffic or identify the integration as the main US buying route. The research confidence rationale refers to two editions, although there are three.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Three dated revisions of the same SDK guide document the same conditional sync ceiling. Deployment, frequency and the main US integration remain unmeasured.",
  "limitations": "A maximum is not an observed count. The default applies when syncing is required. The records do not establish that this was the designated main US Chrome route.",
  "final_wording": "In ID5 publisher SDK guides dated April 18, 2025, October 15, 2025 and November 6, 2026, maxCascades caps cookie syncs at eight by default when user syncing is needed. A value of −1 disables syncing.",
  "counterevidence": "A maximum is not an observed count. The default applies when syncing is required. The records do not establish that this was the designated main US Chrome route.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F21",
  "headline": false,
  "claim": "Three versions of UID2’s client-side JavaScript guide tell publishers to inspect browser local storage for the generated token.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S24",
   "IDN-E-S25",
   "IDN-E-S26"
  ],
  "passage": "[IDN-E-S24, Client-side JavaScript guide / step checking token generation] To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage. [IDN-E-S25, Client-side JavaScript guide / step checking token generation] To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage. [IDN-E-S26, Client-side JavaScript guide / step checking token generation] To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage.",
  "support": [
   {
    "source_id": "IDN-E-S24",
    "passage": "To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage.",
    "locator": "Client-side JavaScript guide / step checking token generation"
   },
   {
    "source_id": "IDN-E-S25",
    "passage": "To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage.",
    "locator": "Client-side JavaScript guide / step checking token generation"
   },
   {
    "source_id": "IDN-E-S26",
    "passage": "To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage.",
    "locator": "Client-side JavaScript guide / step checking token generation"
   }
  ],
  "scope_time": "2025-03-10, 2025-07-08, 2026-10-13",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "The three JavaScript guide revisions dated March 10 and July 8, 2025 and October 13, 2026 describe inspecting local storage as a token-generation verification step for the client-side workflow. The October version separately directs affected OS 27 browsers to server-side generation. A stored token provides no evidence of third-party-cookie syncing. The research rationale refers to two versions, although three were checked. Local storage is not third-party-cookie sync; the newest guide is explicitly unavailable in affected browsers.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Three dated revisions retain the same local-storage inspection step. The latest restricts the client-side workflow in affected browsers.",
  "limitations": "Storage for this token is not evidence of third-party-cookie sync. The registered sync classification stays unknown.",
  "final_wording": "All three UID2 JavaScript guide revisions tell publishers using a supported client-side integration to look for the generated token in local storage. The October 2026 revision directs publishers to generate and refresh tokens server-side in affected OS 27 browsers.",
  "counterevidence": "Storage for this token is not evidence of third-party-cookie sync. The registered sync classification stays unknown.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F22",
  "headline": false,
  "claim": "Prebid describes SharedID storage in a first-party domain on this header-bidding route.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S27"
  ],
  "passage": "This module stores an unique user id in the first party domain",
  "support": [
   {
    "source_id": "IDN-E-S27",
    "passage": "This module stores an unique user id in the first party domain",
    "locator": "User ID submodule guide / sharedid module"
   }
  ],
  "scope_time": "2024-11-28 path revision to 2024-11-28 latest path revision through cutoff",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Prebid’s pinned SharedID module guide describes first-party-domain storage and alternatives including cookies or HTML5 storage. The November 28, 2024 revision was still the latest change to this path at the selected boundaries. There is no separate later edition here.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The pre-event and cutoff path queries return the same revision. No separate post-event edition or third-party sync role was established.",
  "final_wording": "Prebid describes SharedID storage in a first-party domain on this header-bidding route.",
  "counterevidence": "The pre-event and cutoff path queries return the same revision. No separate post-event edition or third-party sync role was established.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F23",
  "headline": false,
  "claim": "Prebid’s Yahoo module guide says ConnectID can operate without third-party cookies.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S28"
  ],
  "passage": "does not depend on 3rd party cookies.",
  "support": [
   {
    "source_id": "IDN-E-S28",
    "passage": "does not depend on 3rd party cookies.",
    "locator": "User ID submodule guide / yahoo module"
   }
  ],
  "scope_time": "2025-04-04 path revision to 2025-04-04 latest path revision through cutoff",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The April 4, 2025 Yahoo module guide states that ConnectID can operate without third-party cookies. It allows a domain-specific first-party identifier and local or cookie storage. The same revision was returned at the comparison boundaries; independence does not show that optional syncing is disabled.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Both date-limited queries return the same April 4 revision. Independence from third-party cookies does not distinguish disabled sync from optional sync.",
  "final_wording": "Prebid’s Yahoo module guide says ConnectID can operate without third-party cookies.",
  "counterevidence": "Both date-limited queries return the same April 4 revision. Independence from third-party cookies does not distinguish disabled sync from optional sync.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F24",
  "headline": false,
  "claim": "The Prebid Parrable guides in the two distinct revisions both describe support for browsers with third-party cookie restrictions.",
  "chapter": "",
  "source_ids": [
   "IDN-E-S29",
   "IDN-E-S30"
  ],
  "passage": "[IDN-E-S29, User ID submodule guide / parrable module] including browsers that have third party cookie restrictions. [IDN-E-S30, User ID submodule guide / parrable module] including browsers that have third party cookie restrictions.",
  "support": [
   {
    "source_id": "IDN-E-S29",
    "passage": "including browsers that have third party cookie restrictions.",
    "locator": "User ID submodule guide / parrable module"
   },
   {
    "source_id": "IDN-E-S30",
    "passage": "including browsers that have third party cookie restrictions.",
    "locator": "User ID submodule guide / parrable module"
   }
  ],
  "scope_time": "2024-11-28 path revision to 2026-10-26 latest path revision through cutoff",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "The November 28, 2024 and October 26, 2026 Parrable module guides both describe use across browsers and webviews on the same device even where third-party cookies face restrictions. They describe a cookie containing the ID and opt-out flags but do not identify it as a required third-party-sync vehicle.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The two dated versions document the same named setting or workflow; deployment and population remain unobserved.",
  "limitations": "Support for restricted browsers cannot distinguish between optional sync, no sync, or a different route. US main-route identification remains open.",
  "final_wording": "The Prebid Parrable guides in the two distinct revisions both describe support for browsers with third-party cookie restrictions.",
  "counterevidence": "Support for restricted browsers cannot distinguish between optional sync, no sync, or a different route. US main-route identification remains open.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F25",
  "headline": false,
  "claim": "Prebid’s Panorama guide describes a device-representing ID for enrichment and activation.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S31"
  ],
  "passage": "is a pseudonymous ID that represents devices",
  "support": [
   {
    "source_id": "IDN-E-S31",
    "passage": "is a pseudonymous ID that represents devices",
    "locator": "User ID submodule guide / lotame module"
   }
  ],
  "scope_time": "2025-01-06 path revision to 2025-01-06 latest path revision through cutoff",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The January 6, 2025 Prebid module guide describes a pseudonymous device ID for audience enrichment and campaign activation. It describes probabilistic groupings in the graph. The same guide revision remained at all three boundaries, leaving a comparison with a separately dated later edition unavailable.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Same January 2025 revision at both search boundaries. Do not import the requirements of Lotame’s separate Spherical sync-pixel route.",
  "final_wording": "Prebid’s Panorama guide describes a device-representing ID for enrichment and activation.",
  "counterevidence": "Same January 2025 revision at both search boundaries. Do not import the requirements of Lotame’s separate Spherical sync-pixel route.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F26",
  "headline": false,
  "claim": "Prebid identifies its Criteo module as ID for Exchanges.",
  "chapter": "",
  "source_ids": [
   "IDN-E-S32"
  ],
  "passage": "Criteo ID for Exchanges User ID sub-module",
  "support": [
   {
    "source_id": "IDN-E-S32",
    "passage": "Criteo ID for Exchanges User ID sub-module",
    "locator": "User ID submodule guide / criteo module"
   }
  ],
  "scope_time": "2024-11-28 path revision to 2024-11-28 latest path revision through cutoff",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The November 28, 2024 Criteo module header identifies the service as Criteo ID for Exchanges. It documents its own caching and adapter requirement, and points to a separate Direct Bidder. The record does not identify OneTag as the same service.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The seed is OneTag, a different nominal interface. Confirm identity of the purchased service and the main US route before using this as evidence.",
  "final_wording": "Prebid identifies its Criteo module as ID for Exchanges.",
  "counterevidence": "The seed is OneTag, a different nominal interface. Confirm identity of the purchased service and the main US route before using this as evidence.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-E-F27",
  "headline": false,
  "claim": "Prebid’s March 2025 and June 2026 Utiq module editions both discuss local-storage consent controls.",
  "chapter": "",
  "source_ids": [
   "IDN-E-S33",
   "IDN-E-S34",
   "IDN-EV-S02"
  ],
  "passage": "[IDN-E-S33, User ID submodule guide / utiq module] you may need to add a vendor exception for the Utiq user id module to work [IDN-E-S34, User ID submodule guide / utiq module] you may need to add a vendor exception for the Utiq user id module to work",
  "support": [
   {
    "source_id": "IDN-E-S33",
    "passage": "you may need to add a vendor exception for the Utiq user id module to work",
    "locator": "User ID submodule guide / utiq module"
   },
   {
    "source_id": "IDN-E-S34",
    "passage": "you may need to add a vendor exception for the Utiq user id module to work",
    "locator": "User ID submodule guide / utiq module"
   }
  ],
  "scope_time": "2025-03-17 path revision to 2026-06-23 latest path revision through cutoff",
  "scope_geo": "Public publisher documentation. No US-specific deployment asserted.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "The March 17, 2025 and June 23, 2026 Utiq documents describe configuring TCF Control around Utiq’s own consent check for local device storage. An additional July 7, 2025 revision, the latest file before the October retirement announcement, has the same language. None of these versions assigns third-party-cookie sync a required role. The extra July 2025 edition dates the guide before the secondary October event. Utiq US eligibility and comparable primary route remain open.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The two dated versions document the same named setting or workflow; deployment and population remain unobserved.",
  "limitations": "The consent setting does not characterize third-party-cookie sync. US eligibility and comparable Chrome pathways remain unproved.",
  "final_wording": "Prebid’s March 2025 and June 2026 Utiq module editions both discuss local-storage consent controls.",
  "counterevidence": "The consent setting does not characterize third-party-cookie sync. US eligibility and comparable Chrome pathways remain unproved.",
  "stream": "E",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-F-F01",
  "headline": false,
  "claim": "For matched email or phone inputs, Google Ads says it adds the corresponding Google Account to the Customer Match segment.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S01"
  ],
  "passage": "Google adds the corresponding Google account to your Customer Match segments",
  "support": [
   {
    "source_id": "IDN-F-S01",
    "passage": "Google adds the corresponding Google account to your Customer Match segments",
    "locator": "Email address and phone matching, second paragraph"
   }
  ],
  "scope_time": "Read 2026-11-11",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Google’s email and phone subsection describes comparison of customer and account hashes. On a match Google adds the corresponding account to the customer list. The address subsection uses a separate composite key. This is Google’s account-level procedure. Google’s product instructions describe its own matching feature. Treat as first-party vendor disclosure. Reserve direct_record for a formal platform policy or agreement, a standard or another qualifying record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Scope is the matched platform account; the passage does not validate person identity or delivery.",
  "final_wording": "For matched email or phone inputs, Google Ads says it adds the corresponding Google Account to the Customer Match segment.",
  "counterevidence": "Scope is the matched platform account; the passage does not validate person identity or delivery.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-F-F02",
  "headline": false,
  "claim": "Google says API uploads need at least 100 matched unique users for the match rate to display.",
  "chapter": "6, 12",
  "source_ids": [
   "IDN-F-S02"
  ],
  "passage": "Match rates display for API uploads containing at least 100 matched unique users.",
  "support": [
   {
    "source_id": "IDN-F-S02",
    "passage": "Match rates display for API uploads containing at least 100 matched unique users.",
    "locator": "Understand match rates / Visibility criteria"
   }
  ],
  "scope_time": "Read 2026-11-11",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The visibility rule applies to API uploads and counts unique users who matched. A list with 100 uploaded records need not have 100 distinct matches. The number is a display threshold, with no accuracy or delivery denominator. The threshold comes from Google’s product documentation. Treat as first-party vendor disclosure. Reserve direct_record for a formal platform policy or agreement, a standard or another qualifying record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "A visibility rule counts matched unique users. The threshold does not measure the odds a pair is correct.",
  "final_wording": "Google says API uploads need at least 100 matched unique users for the match rate to display.",
  "counterevidence": "A visibility rule counts matched unique users. The threshold does not measure the odds a pair is correct.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-F-F03",
  "headline": false,
  "claim": "Google defines its match rate against the uploaded data connected to logged-in Google users and reports a 29%–62% range for most advertisers.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S03"
  ],
  "passage": "[IDN-F-S03, Use your existing first-party data to maximize list size, match-rate bullet and following benchmark] Most advertisers' match rates are between 29% and 62%. [IDN-F-S03, Use your existing first-party data / Use match rate as a benchmark] percentage of your upload that was able to be connected to Google’s logged-in users",
  "support": [
   {
    "source_id": "IDN-F-S03",
    "passage": "Most advertisers' match rates are between 29% and 62%.",
    "locator": "Use your existing first-party data to maximize list size, match-rate bullet and following benchmark"
   },
   {
    "source_id": "IDN-F-S03",
    "passage": "percentage of your upload that was able to be connected to Google’s logged-in users",
    "locator": "Use your existing first-party data / Use match rate as a benchmark"
   }
  ],
  "scope_time": "Read 2026-11-11; measurement period unreported",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Google’s upload denominator is the advertiser’s submitted data. The numerator is the part linked to logged-in Google users. The following tip gives a range for most advertisers. The source gives no number of advertisers, period, geography or distribution method for this benchmark. The footnote on global conversion lift elsewhere on the page belongs to a different statistic.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Producer is Google. No advertiser sample, period, geography, inclusion rule establishing “most,” or test of correct links supplied. This platform comparator has no automatic place in the scored-product H1 frame.",
  "final_wording": "Google defines Customer Match rate as the share of an upload it can link to logged-in Google users. Google says most advertisers fall between 29% and 62%. It gives no period, geography or advertiser sample for that range.",
  "counterevidence": "Producer is Google. No advertiser sample, period, geography, inclusion rule establishing “most,” or test of correct links supplied. This platform comparator has no automatic place in the scored-product H1 frame.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-F-F04",
  "headline": false,
  "claim": "From April 1, 2026 Google directed most new Customer Match integrations to the Data Manager API while retaining a Google Ads API route for eligible existing integrations.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S04"
  ],
  "passage": "Existing eligible integrations can continue to use the Google Ads API for managing customer lists.",
  "support": [
   {
    "source_id": "IDN-F-S04",
    "passage": "Existing eligible integrations can continue to use the Google Ads API for managing customer lists.",
    "locator": "Manage customer lists, Note before examples"
   }
  ],
  "scope_time": "Rule effective 2026-04-01. Guide revised 2026-10-30 UTC and read 2026-11-11.",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The guide, last updated October 30, 2026, states both the April 1 restriction on the two named Google Ads API services and the continuation route for eligible integrations. Eligibility depends on prior Customer Match activity associated with the developer token. Most new integrations use the Data Manager API. The scope is a vendor developer guide about access to its own APIs. Treat as first-party vendor disclosure. Reserve direct_record for a formal platform policy or agreement, a standard or another qualifying record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Connector choice does not establish a change in match logic.",
  "final_wording": "From April 1, 2026 Google directed most new Customer Match integrations to the Data Manager API while retaining a Google Ads API route for eligible existing integrations.",
  "counterevidence": "Connector choice does not establish a change in match logic.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-F-F05",
  "headline": false,
  "claim": "Google’s Authorized Buyers policy lets publishers send obfuscated signals in bid requests to approved third-party bidders.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S05"
  ],
  "passage": "Secure signals will only be shared at the publisher’s instruction and only with bidders the publisher has allowed to receive its signals.",
  "support": [
   {
    "source_id": "IDN-F-S05",
    "passage": "Secure signals will only be shared at the publisher’s instruction and only with bidders the publisher has allowed to receive its signals.",
    "locator": "Share secure signals with bidders, first three paragraphs"
   }
  ],
  "scope_time": "Read 2026-11-11",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The bidder instructions distinguish the signal originator, the publisher that authorizes sharing and the third-party bidder that can receive it. Signals must be obfuscated before reaching Google and should be unreadable by Google. Registration and both parties’ settings matter. Some markets have separate preferences for cookies and secure signals. The source is operational guidance for bidders and publishers about Google’s product. Treat as first-party vendor disclosure. Reserve direct_record for a formal platform policy or agreement, a standard or another qualifying record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "A transport path is distinct from Google matching the signal to one of its own accounts. Approved bidder does not prove user-level consent.",
  "final_wording": "Google’s Authorized Buyers guide says publishers can instruct Ad Manager to send obfuscated signals in bid requests to third-party bidders they have approved. The signal must be registered, and bidders select which signals to receive.",
  "counterevidence": "A transport path is distinct from Google matching the signal to one of its own accounts. Approved bidder does not prove user-level consent.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-F-F06",
  "headline": false,
  "claim": "Amazon’s advertiser-audience agreement specifies hashed data for matching to Amazon IDs and segment identifiers supplied by the advertiser.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S06"
  ],
  "passage": "You will provide Amazon with Hashed Data for the limited purpose of matching to Amazon IDs.",
  "support": [
   {
    "source_id": "IDN-F-S06",
    "passage": "You will provide Amazon with Hashed Data for the limited purpose of matching to Amazon IDs.",
    "locator": "Section 1(a), Hashed Data; next sentence for segment identifiers"
   }
  ],
  "scope_time": "Agreement last updated 2024-11-20",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "Section 1(a) of the November 20, 2024 agreement limits the hashed-data route to matching against Amazon IDs and requires one or more associated segment identifiers. The agreement separately defines other routes, including a data provider. The document establishes contractual purpose and advertiser duties.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The limited-purpose clause describes the contract workflow, with no numeric match or accuracy guarantee.",
  "final_wording": "Under the hashed-data route in Amazon’s November 20, 2024 advertiser-audience agreement, advertisers supply hashed data for matching to Amazon IDs and provide one or more associated segment identifiers.",
  "counterevidence": "The limited-purpose clause describes the contract workflow, with no numeric match or accuracy guarantee.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-F-F07",
  "headline": false,
  "claim": "Amazon Ads instructs advertisers or their agencies to prepare and hash the source audience, then select the hashed audience for activation.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S07"
  ],
  "passage": "The advertiser or agency then selects the hashed audience to be activated.",
  "support": [
   {
    "source_id": "IDN-F-S07",
    "passage": "The advertiser or agency then selects the hashed audience to be activated.",
    "locator": "How it works, first paragraph"
   }
  ],
  "scope_time": "Guide published 2017-06-12, revised 2026-10-08 and read 2026-11-11.",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Amazon instructs an advertiser or agency to use its offline tool or manual preparation instructions before selecting a hashed audience for activation. It presents a workflow and provides no advertiser-specific match counts or delivery result.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The article describes activation of a segment; it does not specify a buyer export of individual matches.",
  "final_wording": "Amazon Ads instructs advertisers or their agencies to prepare and hash the source audience, then select the hashed audience for activation.",
  "counterevidence": "The article describes activation of a segment; it does not specify a buyer export of individual matches.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-F-F08",
  "headline": false,
  "claim": "Amazon Marketing Cloud limits the analyst-facing outputs it describes to aggregated anonymous results while directing custom audiences to ad activation.",
  "chapter": "6, 12",
  "source_ids": [
   "IDN-F-S08"
  ],
  "passage": "You can only access aggregated, anonymous outputs from AMC.",
  "support": [
   {
    "source_id": "IDN-F-S08",
    "passage": "You can only access aggregated, anonymous outputs from AMC.",
    "locator": "Privacy-safe environment and Custom audiences"
   }
  ],
  "scope_time": "Read 2026-11-11",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Amazon says only aggregated, anonymous AMC output is accessible to the analyst, describes thresholded queries on advertiser and Amazon signals, and separately describes direct activation of AMC audiences for sponsored, video and display advertising. These are Amazon’s statements about its service. The feature and output restrictions come from Amazon’s own commercial product page. Treat as first-party vendor disclosure. Reserve direct_record for a formal platform policy or agreement, a standard or another qualifying record. Commercial product page. Preserve its marketing provenance and corresponding grade cap if considered in later stages.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "An audience activation is a different output channel from an analytical result returned to the advertiser.",
  "final_wording": "Amazon Marketing Cloud limits the analyst-facing outputs it describes to aggregated anonymous results while directing custom audiences to ad activation.",
  "counterevidence": "An audience activation is a different output channel from an analytical result returned to the advertiser.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-F-F09",
  "headline": false,
  "claim": "Meta’s Customer List Custom Audiences terms say advertisers do not receive the individual identities that constitute their matched audience.",
  "chapter": "6, 12",
  "source_ids": [
   "IDN-F-S09"
  ],
  "passage": "Meta does not disclose to you which individual users comprise your Audience",
  "support": [
   {
    "source_id": "IDN-F-S09",
    "passage": "Meta does not disclose to you which individual users comprise your Audience",
    "locator": "Clause beginning “You acknowledge that Meta offers tools”, effective-date footer"
   }
  ],
  "scope_time": "Effective 2025-12-03",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Meta’s terms effective December 3, 2025 expressly say Meta does not disclose which individuals comprise a customer-list audience to the submitting advertiser. They also require rights, a lawful basis and honoring applicable opt-outs. These are contractual provisions for the customer-list feature.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The contract describes the advertiser view. It does not identify the matching algorithm’s error rate.",
  "final_wording": "Meta’s Customer List Custom Audiences terms say advertisers do not receive the individual identities that constitute their matched audience.",
  "counterevidence": "The contract describes the advertiser view. It does not identify the matching algorithm’s error rate.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-F-F10",
  "headline": false,
  "claim": "Meta’s Marketing API lists email addresses and phone numbers among the inputs used to build target Custom Audiences from customer information.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S10"
  ],
  "passage": "The Marketing API allows you to build target Custom Audiences from customer information. This includes email addresses, phone numbers",
  "support": [
   {
    "source_id": "IDN-F-S10",
    "passage": "The Marketing API allows you to build target Custom Audiences from customer information. This includes email addresses, phone numbers",
    "locator": "Custom Audiences from a Customer List, overview"
   }
  ],
  "scope_time": "Developer guide revised 2026-07-14 and read 2026-11-11.",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Meta’s developer guide, updated July 14, 2026, explicitly lists email and phone among accepted customer fields for building a target audience. It describes normalizing and hashing contact fields. Source coverage ends at documented inputs and matching rules. This is Meta’s technical documentation of its own audience API. Treat as first-party vendor disclosure. Reserve direct_record for a formal platform policy or agreement, a standard or another qualifying record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Supplying an identifier is separate from a successful match or an impression.",
  "final_wording": "Meta’s Marketing API lists email addresses and phone numbers among the inputs used to build target Custom Audiences from customer information.",
  "counterevidence": "Supplying an identifier is separate from a successful match or an impression.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-F-F11",
  "headline": false,
  "claim": "Walmart Connect’s May announcement named Yahoo DSP, VIZIO inventory and Magnite for activation of Walmart audiences in an offsite buying workflow.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S11"
  ],
  "passage": "Launch partners include Yahoo DSP, beginning with VIZIO inventory made available via Magnite’s platform",
  "support": [
   {
    "source_id": "IDN-F-S11",
    "passage": "Launch partners include Yahoo DSP, beginning with VIZIO inventory made available via Magnite’s platform",
    "locator": "Paragraph beginning “Through partnerships”"
   }
  ],
  "scope_time": "2026-05-28",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Walmart Connect’s May 28, 2026 release identifies Yahoo DSP as a launch partner and VIZIO inventory made available via Magnite. The audience and associated measurement originate at Walmart. The release calls other partnerships planned.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Walmart described additional integrations as planned. The traffic direction here is retailer audience to buying platform.",
  "final_wording": "Walmart Connect’s May announcement named Yahoo DSP, VIZIO inventory and Magnite for activation of Walmart audiences in an offsite buying workflow.",
  "counterevidence": "Walmart described additional integrations as planned. The traffic direction here is retailer audience to buying platform.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-F-F12",
  "headline": false,
  "claim": "For its managed Google search-ad offering, Roundel describes use of Target’s own audiences, including past Target.com purchasers.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S12"
  ],
  "passage": "our first-party audiences, such as past Target.com purchasers",
  "support": [
   {
    "source_id": "IDN-F-S12",
    "passage": "our first-party audiences, such as past Target.com purchasers",
    "locator": "Reach our guests / Target first-party audience bullet and managed-service text"
   }
  ],
  "scope_time": "Product page published 2023-05-03, revised 2023-06-07 and read 2026-11-11.",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Roundel describes use of Target’s first-party audiences, gives past Target.com purchasers as an example, and says Roundel works directly with Google on the managed search offering. The page covers Target sales reporting, not a CRM join for the advertiser.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "This page does not establish that a brand can import its CRM list through this route.",
  "final_wording": "For its managed Google search-ad offering, Roundel describes use of Target’s own audiences, including past Target.com purchasers.",
  "counterevidence": "This page does not establish that a brand can import its CRM list through this route.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-F-F13",
  "headline": false,
  "claim": "In November 2023 Kroger Precision Marketing said its customers could activate Kroger purchase-based audiences through their existing seats on The Trade Desk.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S13"
  ],
  "passage": "advertisers can now activate Kroger audiences directly in their existing DSP seats.",
  "support": [
   {
    "source_id": "IDN-F-S13",
    "passage": "advertisers can now activate Kroger audiences directly in their existing DSP seats.",
    "locator": "November 15 release, opening paragraph; later paragraph names The Trade Desk"
   }
  ],
  "scope_time": "2023-11-15 announcement",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Kroger’s November 15, 2023 launch describes its purchase audiences available to buyers in existing DSP seats, exclusive to The Trade Desk in the first iteration. Buyers could select their own inventory and rates and use Kroger store and online sales measurement.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Describes a launch-era purchase-audience activation route rather than a general transfer of shopper records.",
  "final_wording": "In November 2023 Kroger Precision Marketing said its customers could activate Kroger purchase-based audiences through their existing seats on The Trade Desk.",
  "counterevidence": "Describes a launch-era purchase-audience activation route rather than a general transfer of shopper records.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-F-F14",
  "headline": false,
  "claim": "When it announced Data Hub in January 2026, Instacart said selected agencies and CPGs had piloted the clean-room service for joining marketer and grocery data.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S14"
  ],
  "passage": "Data Hub has been in pilot with a select group of agencies and CPGs",
  "support": [
   {
    "source_id": "IDN-F-S14",
    "passage": "Data Hub has been in pilot with a select group of agencies and CPGs",
    "locator": "January 6 release, introductory and pilot paragraphs"
   }
  ],
  "scope_time": "2026-01-06",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Instacart’s January 6, 2026 release says the Data Hub clean room had been piloted with selected agencies and CPGs, could combine marketer data with grocery signals and was expected to expand during 2026. The release alone does not verify the planned expansion.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "The planned expansion is not proof every advertiser could use it at announcement.",
  "final_wording": "When it announced Data Hub in January 2026, Instacart said selected agencies and CPGs had piloted the clean-room service for joining marketer and grocery data.",
  "counterevidence": "The planned expansion is not proof every advertiser could use it at announcement.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-F-F15",
  "headline": false,
  "claim": "Instacart’s clean-room setup guide uses a hashed-email intersection between two parties as an example of an analysis where complete datasets stay hidden.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S15"
  ],
  "passage": "an analysis on the intersection of hashed user emails between two companies",
  "support": [
   {
    "source_id": "IDN-F-S15",
    "passage": "an analysis on the intersection of hashed user emails between two companies",
    "locator": "Configure and view clean rooms, first paragraph"
   }
  ],
  "scope_time": "Guide updated 2026-05-14",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Instacart’s guide, dated May 14, 2026 in the page markup, gives a two-company hashed-email intersection as an example for restricted analysis. It distinguishes Overlap Analysis, which needs consumer data linking, from listed templates based only on Instacart data. No realized overlap is reported. This example comes from Instacart’s technical guide. Treat as first-party vendor disclosure. Reserve direct_record for a formal platform policy or agreement, a standard or another qualifying record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Illustrative supported query model. No realized overlap, matching quality or universal key requirement follows.",
  "final_wording": "Instacart’s clean-room setup guide uses a hashed-email intersection between two parties as an example of an analysis where complete datasets stay hidden.",
  "counterevidence": "Illustrative supported query model. No realized overlap, matching quality or universal key requirement follows.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-F-F16",
  "headline": false,
  "claim": "For Data Hub activation queries, Instacart directs results to its own account and says partners cannot see the specific matched identifiers.",
  "chapter": "6",
  "source_ids": [
   "IDN-F-S16"
  ],
  "passage": "Partners don't have visibility into the specific matched identifiers or activation results.",
  "support": [
   {
    "source_id": "IDN-F-S16",
    "passage": "Partners don't have visibility into the specific matched identifiers or activation results.",
    "locator": "Activation templates / How it works, paragraph following the numbered workflow"
   }
  ],
  "scope_time": "Guide updated 2026-05-14",
  "scope_geo": "US-facing platform documentation; no US-only outcome sample.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Instacart’s activation instructions, dated May 14, 2026 in the page markup, route encrypted audience identifiers from the overlap query to Instacart’s Snowflake account. Instacart manages approved platform activation. The partner cannot inspect the matched IDs or results of the activation query. The source is Instacart’s technical workflow documentation. Treat as first-party vendor disclosure. Reserve direct_record for a formal platform policy or agreement, a standard or another qualifying record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The identified first-party text directly describes this limited claim.",
  "limitations": "Specific to audience activation. Standard analytical queries can return other outputs. This clean room stays outside the IQ.",
  "final_wording": "For Data Hub activation queries, Instacart directs results to its own account and says partners cannot see the specific matched identifiers.",
  "counterevidence": "Specific to audience activation. Standard analytical queries can return other outputs. This clean room stays outside the IQ.",
  "stream": "F",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-G-F01",
  "headline": false,
  "claim": "TransUnion’s 2021 TruAudience offering described its identity product as omnichannel and separately named the streaming-data marketplace formerly known as Tru Optik.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S01"
  ],
  "passage": "TruAudience Data Marketplace, formerly Tru Optik",
  "support": [
   {
    "source_id": "IDN-G-S01",
    "passage": "TruAudience Data Marketplace, formerly Tru Optik",
    "locator": "Product list, consecutive TruAudience Identity and TruAudience Data Marketplace bullets"
   }
  ],
  "scope_time": "2021-08-24 product launch",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "TransUnion’s August 24, 2021 release lists TruAudience Identity, Data Marketplace (formerly Tru Optik), and Platform separately. It describes individual, household and device identity alongside its US streaming audience marketplace. The separate labels in a portfolio launch do not demonstrate a separate licence for the underlying CTV household graph. Its household-scale counts are seller figures.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The service list does not establish a separately purchasable US CTV household edge graph.",
  "final_wording": "TransUnion’s 2021 TruAudience offering described its identity product as omnichannel and separately named the streaming-data marketplace formerly known as Tru Optik.",
  "counterevidence": "The service list does not establish a separately purchasable US CTV household edge graph.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F02",
  "headline": false,
  "claim": "Comcast and TransUnion announced a household-level TV audience route that matched Comcast audience data with TransUnion’s existing identity assets.",
  "chapter": "",
  "source_ids": [
   "IDN-G-S02"
  ],
  "passage": "Comcast’s audience data is directly matched with TransUnion’s already existing robust identity assets",
  "support": [
   {
    "source_id": "IDN-G-S02",
    "passage": "Comcast’s audience data is directly matched with TransUnion’s already existing robust identity assets",
    "locator": "June 6, 2024 announcement, paragraph beginning Through this integration"
   }
  ],
  "scope_time": "2024-06-06 announcement",
  "scope_geo": "United States, Comcast footprint",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The June 6, 2024 announcement describes matching Comcast audience data to TransUnion’s existing assets to create addressable segments for Comcast linear and streaming campaigns. Comcast’s footprint was described as close to 32 million households. Footprint is the territory/audience available to Comcast, not observed match yield. The partners describe the route. No edge timer or separate graph sale follows.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "A route to create TV audiences is evidence of a commercial use, not a separate graph licence or a documented refresh interval.",
  "final_wording": "Comcast and TransUnion announced a household-level TV audience route that matched Comcast audience data with TransUnion’s existing identity assets.",
  "counterevidence": "A route to create TV audiences is evidence of a commercial use, not a separate graph licence or a documented refresh interval.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F03",
  "headline": false,
  "claim": "TransUnion lists a monthly full US identity extract containing individual and household IDs.",
  "chapter": "",
  "source_ids": [
   "IDN-G-S03"
  ],
  "passage": "Update frequency  | Monthly",
  "support": [
   {
    "source_id": "IDN-G-S03",
    "passage": "Update frequency  | Monthly",
    "locator": "Metadata, Geographic coverage, Unique identifiers, Update frequency and Update Type rows"
   }
  ],
  "scope_time": "Offering read 2026-11-11",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "TransUnion’s AWS seller listing identifies the covered market as the US, both individual and household identifiers, monthly updates and full refresh of the delivered extract. The listing covers the general Identity Extracts file. Its monthly delivery is not the lifetime of a CTV household edge. The support passage represents two adjacent cells in a rendered table; use both field and value as the locator.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "This is a file delivery schedule. Edge refresh or expiry and the price of a separate TV service remain unconfirmed.",
  "final_wording": "TransUnion lists a monthly full US identity extract containing individual and household IDs.",
  "counterevidence": "This is a file delivery schedule. Edge refresh or expiry and the price of a separate TV service remain unconfirmed.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F04",
  "headline": false,
  "claim": "Viant says its household assignment screens IP addresses by residential ISP, device count and time of association before linking observations to a registered address.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S04"
  ],
  "passage": "residential internet service provider, number of devices, plus the times of day these devices are associated with the IP",
  "support": [
   {
    "source_id": "IDN-G-S04",
    "passage": "residential internet service provider, number of devices, plus the times of day these devices are associated with the IP",
    "locator": "How the Household ID Works, second paragraph"
   }
  ],
  "scope_time": "Viant product description dated 2026-07-10; read 2026-11-11.",
  "scope_geo": "US household context",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Viant’s July 10, 2026 page says it filters IPs by residential ISP, device count and the times of day associated devices appear. It then uses location coordinates from geolocation-enabled devices to match to a registered physical address. Time of day is an input feature, not time elapsed since the link was seen. Viant calls the result deterministic, but this marketing description does not independently validate assignment precision.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "Time-of-day features do not specify an elapsed expiry or refresh rule. This is the operator’s method description.",
  "final_wording": "Viant says it screens IP addresses by residential ISP, device count and time of day, then uses coordinates from location-enabled devices to match them to a registered home address.",
  "counterevidence": "Time-of-day features do not specify an elapsed expiry or refresh rule. This is the operator’s method description.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F05",
  "headline": false,
  "claim": "Blockgraph says its household identity framework anchors a household to its postal address.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S05"
  ],
  "passage": "It’s anchored to postal addresses",
  "support": [
   {
    "source_id": "IDN-G-S05",
    "passage": "It’s anchored to postal addresses",
    "locator": "Working Within the Platform, paragraph on household foundation"
   }
  ],
  "scope_time": "Product page read 2026-11-11",
  "scope_geo": "US TV household marketing context",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Blockgraph’s capability page describes postal addresses as the anchor for its household audience used in activation and measurement. This is an operator statement about the anchor, not evidence excluding IP from every input, partner workflow or device map.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "An address anchor does not rule out IP ingestion elsewhere in an implementation; no timed assignment rule was established on this page.",
  "final_wording": "Blockgraph says its household identity framework anchors a household to its postal address.",
  "counterevidence": "An address anchor does not rule out IP ingestion elsewhere in an implementation; no timed assignment rule was established on this page.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F06",
  "headline": false,
  "claim": "Blockgraph and Cadent described an integration through which Aperture customers could activate TV audiences within participating distributors’ addressable household footprint.",
  "chapter": "",
  "source_ids": [
   "IDN-G-S06"
  ],
  "passage": "across addressable households within the footprint of participating distributors",
  "support": [
   {
    "source_id": "IDN-G-S06",
    "passage": "across addressable households within the footprint of participating distributors",
    "locator": "Partnership announcement, April 27, 2022, paragraph beginning Through the new integration"
   }
  ],
  "scope_time": "April 2022 partnership announcement",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "On April 27, 2022, Blockgraph announced that its agreement with Cadent would allow Aperture customers to match and activate audiences using aggregated, de-identified data within participating distributors’ household footprints. The issuer uses prospective language for this integration. The announcement is not a separate production observation and does not establish the scope of a distributor operating today.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The agreement scopes the delivery path. It does not validate either company’s graph accuracy.",
  "final_wording": "In April 2022, Blockgraph and Cadent announced that Aperture customers would be able to match and activate TV audiences within participating distributors’ addressable household footprints.",
  "counterevidence": "The agreement scopes the delivery path. It does not validate either company’s graph accuracy.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F07",
  "headline": false,
  "claim": "Blockgraph announced GraphPort as an interface for mapping third-party graphs into its Identity Operating System.",
  "chapter": "",
  "source_ids": [
   "IDN-G-S07"
  ],
  "passage": "permissioned mapping of third-party identity graphs to Blockgraph’s comprehensive Identity Operating System",
  "support": [
   {
    "source_id": "IDN-G-S07",
    "passage": "permissioned mapping of third-party identity graphs to Blockgraph’s comprehensive Identity Operating System",
    "locator": "Launch announcement, June 8, 2023, opening paragraph"
   }
  ],
  "scope_time": "June 2023 launch",
  "scope_geo": "US TV advertising context",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Blockgraph’s June 8, 2023 release describes GraphPort as enabling permissioned mapping of third-party graphs to IDoS. The mapped partner graph, the connection product and the IDoS household foundation are distinct objects. The announcement does not test accuracy or document a household expiry rule.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "GraphPort and the underlying IDoS should not automatically be counted as two independent household graphs.",
  "final_wording": "Blockgraph announced GraphPort as an interface for mapping third-party graphs into its Identity Operating System.",
  "counterevidence": "GraphPort and the underlying IDoS should not automatically be counted as two independent household graphs.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F08",
  "headline": false,
  "claim": "FreeWheel describes its embedded Identity Network as using Comcast signals, publisher partner IDs and the buyer’s first-party data.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S08"
  ],
  "passage": "Comcast’s deterministic identity signals, proprietary partner IDs from publishers, and the ability to integrate your own first-party data",
  "support": [
   {
    "source_id": "IDN-G-S08",
    "passage": "Comcast’s deterministic identity signals, proprietary partner IDs from publishers, and the ability to integrate your own first-party data",
    "locator": "Description, first paragraph"
   }
  ],
  "scope_time": "Product description read 2026-11-11",
  "scope_geo": "Comcast/FreeWheel and publisher partners; territory varies",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "FreeWheel describes embedded access to Comcast’s deterministic signals and publishers’ proprietary partner IDs. It also offers buyers the option of connecting their own first-party data. The buyer input is optional. The page does not show that every customer provides it or that every partner uses the same assignment method.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "This identifies upstream inputs and access routes. Standalone household graph product, edge construction and time-based decay remain unresolved.",
  "final_wording": "FreeWheel says its embedded Identity Network provides access to Comcast’s deterministic signals and publisher partner IDs. Buyers can also connect their own first-party data.",
  "counterevidence": "This identifies upstream inputs and access routes. Standalone household graph product, edge construction and time-based decay remain unresolved.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F09",
  "headline": false,
  "claim": "OpenAP describes Open Identity as an evolution of OpenID that enables direct matching across parties without a central identity spine.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S17"
  ],
  "passage": "without requiring a central identity spine",
  "support": [
   {
    "source_id": "IDN-C-S17",
    "passage": "without requiring a central identity spine",
    "locator": "Transforming Identity for Convergent TV, first paragraph"
   }
  ],
  "scope_time": "2025-04-15 announcement; service availability projected beginning May 2025.",
  "scope_geo": "US streaming and cross-platform TV market",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The April 15, 2025 release describes Open Identity as a federated evolution of OpenID that enables direct matches without a central spine. It identifies providers at launch and others undergoing integration, and says the technology would be live beginning in May. The source’s April event is the announcement, not proof of April deployment. The publisher and advertiser choose participating identity providers and householding business logic.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "This is the issuer’s architecture claim; it does not mean that each contributing identity provider has the same matching method.",
  "final_wording": "In April 2025, OpenAP described Open Identity as a successor to OpenID for direct matching among participating parties without a central identity spine. It announced availability beginning in May 2025.",
  "counterevidence": "This is the issuer’s architecture claim; it does not mean that each contributing identity provider has the same matching method.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F10",
  "headline": false,
  "claim": "Cadent says its Aperture contextual targeting offer uses a proprietary IP-to-household Viewer Graph.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S10"
  ],
  "passage": "IP-to-household Viewer Graph.",
  "support": [
   {
    "source_id": "IDN-G-S10",
    "passage": "IP-to-household Viewer Graph.",
    "locator": "Aperture Platform sell sheet, How It Works / Audience Targeting"
   }
  ],
  "scope_time": "PDF in May 2024 upload directory; issue date not printed; read 2026-11-11",
  "scope_geo": "Territory unspecified in sell sheet",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Cadent's 2024 Aperture sales sheet identifies its proprietary IP-to-household Viewer Graph as an input when matching first- and third-party data for contextual audience targeting. Opened the indexed original issuer PDF after its live URL redirected to cadent.com. The sheet identifies a graph-backed targeting option, not a separate graph offering, test or link expiry.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "A graph used inside a contextual product supports the existence of that input. Separate commercial availability and per-edge refresh are unconfirmed.",
  "final_wording": "Cadent says its Aperture contextual targeting offer uses a proprietary IP-to-household Viewer Graph.",
  "counterevidence": "A graph used inside a contextual product supports the existence of that input. Separate commercial availability and per-edge refresh are unconfirmed.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F11",
  "headline": false,
  "claim": "LiveRamp’s programmer guide accepts IP-based CTV events for matching and recommends daily or weekly delivery of new data after initial onboarding.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S11"
  ],
  "passage": "we recommend a daily or weekly file delivery with new data that you have recorded",
  "support": [
   {
    "source_id": "IDN-G-S11",
    "passage": "we recommend a daily or weekly file delivery with new data that you have recorded",
    "locator": "Guidelines for Sending IP Address-Based Data, cadence bullet; opening CTV data only note"
   }
  ],
  "scope_time": "Programmer guide read 2026-11-11",
  "scope_geo": "Service territory unconfirmed in guide",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "LiveRamp’s guide, last modified May 25, 2021, describes CTV-specific IP matching, an initial recommendation of at least two months of recent data, a lookback of up to six months and daily or weekly new file deliveries. The daily/weekly clock belongs to the programmer's submissions. The matching system can resolve an overlapping record to all applicable RampIDs; nothing establishes a household edge’s six-month lifetime.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "This is a programmer delivery schedule. The guide’s separate six-month lookback is an observational window; neither establishes the time at which a household edge is invalidated.",
  "final_wording": "LiveRamp’s programmer guide accepts IP-based CTV events for matching and recommends daily or weekly delivery of new data after initial onboarding.",
  "counterevidence": "This is a programmer delivery schedule. The guide’s separate six-month lookback is an observational window; neither establishes the time at which a household edge is invalidated.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F12",
  "headline": false,
  "claim": "Factori describes its cross-device offering as linking encrypted mobile ad IDs and IP addresses with daily server-to-server feed delivery.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S12",
   "IDN-GV-S04"
  ],
  "passage": "This aggregated data feed is delivered as a daily feed via S2S transfer.",
  "support": [
   {
    "source_id": "IDN-G-S12",
    "passage": "This aggregated data feed is delivered as a daily feed via S2S transfer.",
    "locator": "Cross Device / CTV Graph, opening paragraph"
   }
  ],
  "scope_time": "Developer specification read 2026-11-11",
  "scope_geo": "Global seller listing; the cited Factori documents do not identify a US-specific licence or participating US households.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Factori’s graph documentation ties encrypted mobile ad IDs and IP addresses to its cross-device data and calls the S2S delivery daily. A separate seller AWS listing offers a distinct subscription to the dataset and describes this same cadence. Both descriptions are vendor-origin. The AWS listing identifies a purchasable cross-device dataset with global coverage claimed, without a US-specific contract or validated household-link expiry. Daily delivery, event capture and historic file availability are different clocks.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "Factori lists a distinct CTV/Cross Device Data subscription on AWS Data Exchange. US-specific coverage and a timed rule governing the household link remain unconfirmed in these two records.",
  "final_wording": "Factori describes its cross-device offering as linking encrypted mobile ad IDs and IP addresses with daily server-to-server feed delivery.",
  "counterevidence": "Factori lists a distinct CTV/Cross Device Data subscription on AWS Data Exchange. US-specific coverage and a timed rule governing the household link remain unconfirmed in these two records.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F13",
  "headline": false,
  "claim": "LtvAdx documents an IP-based path for joining devices to a household and a 30-day lifetime after last observation for a device–household link.",
  "chapter": "7, 13",
  "source_ids": [
   "IDN-G-S13",
   "IDN-G-S14",
   "IDN-GV-S01",
   "IDN-GV-S02",
   "IDN-GV-S03"
  ],
  "passage": "[IDN-G-S13, Identity API: matching order, text following the priority table] two devices are joined to one household only through a shared device id or IP [IDN-G-S14, What is kept, and for how long: A device linked to a household] 30 days after the device was last seen. [IDN-GV-S01, For Advertisers, US market offer] Reach US households on the big screen [IDN-GV-S02, Advertiser plan, included capabilities] HouseholdID & ACR segment targeting [IDN-GV-S03, How it works on your stack, Stage 01] Buyer-facing segment IDs, not raw graphs",
  "support": [
   {
    "source_id": "IDN-G-S13",
    "passage": "two devices are joined to one household only through a shared device id or IP",
    "locator": "Identity API: matching order, text following the priority table"
   },
   {
    "source_id": "IDN-G-S14",
    "passage": "30 days after the device was last seen.",
    "locator": "What is kept, and for how long: A device linked to a household"
   },
   {
    "source_id": "IDN-GV-S01",
    "passage": "Reach US households on the big screen",
    "locator": "For Advertisers, US market offer"
   },
   {
    "source_id": "IDN-GV-S02",
    "passage": "HouseholdID & ACR segment targeting",
    "locator": "Advertiser plan, included capabilities"
   },
   {
    "source_id": "IDN-GV-S03",
    "passage": "Buyer-facing segment IDs, not raw graphs",
    "locator": "How it works on your stack, Stage 01"
   }
  ],
  "scope_time": "Matched operator documentation read 2026-11-11.",
  "scope_geo": "US advertiser platform offering documented; separate household-resolution licence unconfirmed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The API first recognizes a previously linked device ID, then tries a previously seen IP as a probabilistic match. Its retention guide gives 30 days since the device's last sighting for a device link and 90 for a household profile. The US site and pricing plan bundle HouseholdID targeting with campaign buying. The operator itself directly describes both rules, and its own commercial pages describe the US route. Combining these pages does not supply an independent measurement or require a cross-source synthesis class. Both technical documents come from the same operator. The US exchange buying route is documented. A separately licensable resolution product, actual enforcement, and independent calibration of the API’s 0.75 confidence code remain unestablished.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The API and retention rule come from the operator and have no independent enforcement test here. Its US exchange advertiser plan includes HouseholdID targeting; the sources do not establish a separate household-resolution purchase.",
  "final_wording": "LtvAdx documents a shared-IP fallback for assigning a device to a household and removes a device link 30 days after the device was last seen. It offers HouseholdID targeting in its US advertising workflow.",
  "counterevidence": "The API and retention rule come from the operator and have no independent enforcement test here. Its US exchange advertiser plan includes HouseholdID targeting; the sources do not establish a separate household-resolution purchase.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F14",
  "headline": false,
  "claim": "Criteo’s CTV guide describes a shared household connection as a fallback when an exact match is unavailable.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S15"
  ],
  "passage": "we use the home's shared internet connection as an approximate signal",
  "support": [
   {
    "source_id": "IDN-G-S15",
    "passage": "we use the home's shared internet connection as an approximate signal",
    "locator": "Step 1, Household match when needed"
   }
  ],
  "scope_time": "Commerce Growth help page read 2026-11-11",
  "scope_geo": "Territory unspecified in guide",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Criteo says it first uses privacy-safe exact signals such as hashed email or a device ID. If that fails, it uses the shared home connection to associate an approximate household. The fallback identifies a household rather than an individual viewer. The one-day visit and up-to-30-day sales windows concern post-view attribution; they do not specify IP link validity.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The same guide’s up-to-30-day sales attribution window measures action after an ad view; it cannot be treated as household-link expiry.",
  "final_wording": "Criteo’s CTV guide describes a shared household connection as a fallback when an exact match is unavailable.",
  "counterevidence": "The same guide’s up-to-30-day sales attribution window measures action after an ad view; it cannot be treated as household-link expiry.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F15",
  "headline": false,
  "claim": "In January 2020, Skydeo described a US mobile-data integration with the then-named Tru Optik Household Graph.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S16"
  ],
  "passage": "to enhance mobile device identity resolution and audience-based targeting capabilities across Tru Optik’s Household Graph™",
  "support": [
   {
    "source_id": "IDN-G-S16",
    "passage": "to enhance mobile device identity resolution and audience-based targeting capabilities across Tru Optik’s Household Graph™",
    "locator": "Partnership announcement, opening paragraph"
   }
  ],
  "scope_time": "January 2020 partnership announcement",
  "scope_geo": "United States, Tru Optik Household Graph",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The January 23, 2020 release announces an agreement whereby Skydeo’s mobile data would be mapped to the existing Tru Optik Household Graph. Its US device and US home totals are separate seller assertions. A planned mapping at announcement is not proof it was deployed, that the historic graph is licensed separately today, or that its claimed footprint was validated.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The historic product is named. Current independent licensing and commercial continuity cannot be inferred from its former name.",
  "final_wording": "In January 2020, Skydeo announced an agreement to map its mobile data to the then-named Tru Optik Household Graph in the United States.",
  "counterevidence": "The historic product is named. Current independent licensing and commercial continuity cannot be inferred from its former name.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F16",
  "headline": false,
  "claim": "TransUnion and Epsilon named TruAudience Data Marketplace as the route for accessing Epsilon audience data for connected TV.",
  "chapter": "7, 8",
  "source_ids": [
   "IDN-G-S17"
  ],
  "passage": "available via the TruAudience® Data Marketplace",
  "support": [
   {
    "source_id": "IDN-G-S17",
    "passage": "available via the TruAudience® Data Marketplace",
    "locator": "Partnership announcement, opening paragraph"
   }
  ],
  "scope_time": "2022 partnership announcement",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "TransUnion’s June 7, 2022 announcement says Epsilon audience insights mapped to TransUnion’s graph could be accessed through TruAudience Data Marketplace for CTV and streaming audio. The Epsilon figure refers to consumers, and TransUnion's refers to connected homes. The release establishes the named buying route for audiences; it does not price or distinguish a separately licensed Streaming Household Graph.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "The household graph underpins this audience product. This announcement does not identify a separate contract or public price for a streaming household graph.",
  "final_wording": "TransUnion and Epsilon named TruAudience Data Marketplace as the route for accessing Epsilon audience data for connected TV.",
  "counterevidence": "The household graph underpins this audience product. This announcement does not identify a separate contract or public price for a streaming household graph.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-G-F17",
  "headline": false,
  "claim": "Viant’s household-identification patent gives 45 days as an example minimum IP assignment age for further processing.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S18"
  ],
  "passage": "a threshold age (e.g., 45 days) to determine if the address is static enough to use for further processing",
  "support": [
   {
    "source_id": "IDN-G-S18",
    "passage": "a threshold age (e.g., 45 days) to determine if the address is static enough to use for further processing",
    "locator": "Specification, Fig. 5 / step 508, IP assignment age"
   }
  ],
  "scope_time": "2022-04-19 grant; implementation date not established",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "Specification step 508 and Figure 5 describe checking whether assignment age exceeds a configurable threshold. Forty-five days is an example for deciding whether an IP address is stable enough for further processing. The comparison uses greater than, not greater than or equal to. This is a patent embodiment, not an expiry after the last sighting or evidence that a live product uses 45 days.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited passage identifies the stated method, result or service. The limitations bound its use.",
  "limitations": "Minimum stability to qualify is distinct from expiration after last observation. Patent embodiment does not show that the live product uses this value.",
  "final_wording": "Viant’s US patent gives 45 days as an example threshold that an IP assignment’s age must exceed to qualify for further processing.",
  "counterevidence": "Minimum stability to qualify is distinct from expiration after last observation. Patent embodiment does not show that the live product uses this value.",
  "stream": "G",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-H-F01",
  "headline": false,
  "claim": "In its June 2023 retargeting decision, the French regulator found that stopping personalised ads was insufficient to meet the erasure requests at issue.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S01"
  ],
  "passage": "ne pouvait donc se limiter à interrompre l’affichage de publicités personnalisées",
  "support": [
   {
    "source_id": "IDN-H-S01",
    "passage": "ne pouvait donc se limiter à interrompre l’affichage de publicités personnalisées",
    "locator": "Paragraphs 134–136, right of withdrawal and erasure"
   }
  ],
  "scope_time": "2023-06-15; read 2026-11-11",
  "scope_geo": "EU / France",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Decision SAN-2023-009, paras 132 and 134–136, distinguishes suppressing targeted ads from erasing the data of people for whom valid consent could not be established. Dispositive passage dates the decision June 15, 2023. Publication on Légifrance was June 22. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "Concerns the examined processing on the partner sites. The original decision is now anonymised; judgment 482872 identifies Criteo.",
  "final_wording": "In its June 2023 retargeting decision, the French regulator found that stopping personalised ads was insufficient to meet the erasure requests at issue.",
  "counterevidence": "Concerns the examined processing on the partner sites. The original decision is now anonymised; judgment 482872 identifies Criteo.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F02",
  "headline": false,
  "claim": "On March 4, 2026, France’s Conseil d’État rejected Criteo’s challenge to the €40 million CNIL sanction.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S02"
  ],
  "passage": "[IDN-H-S02, Article 1er, read with procedural history and paragraph 22] La requête de la société Criteo est rejetée. [IDN-H-S02, Procedural history, first request] une amende administrative d'un montant de 40 millions d'euros",
  "support": [
   {
    "source_id": "IDN-H-S02",
    "passage": "La requête de la société Criteo est rejetée.",
    "locator": "Article 1er, read with procedural history and paragraph 22"
   },
   {
    "source_id": "IDN-H-S02",
    "passage": "une amende administrative d'un montant de 40 millions d'euros",
    "locator": "Procedural history, first request"
   }
  ],
  "scope_time": "2026-03-04; read 2026-11-11",
  "scope_geo": "EU / France",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "In no. 482872, para 22 upholds CNIL’s EUR 40m assessment and article 1 rejects Criteo’s application on March 4, 2026. This French review addresses the June 2023 sanction, not every service with the Criteo name. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "The court expressly puts some remediation before imposition of the sanction. The sanction is not an order requiring every OneTag configuration to change.",
  "final_wording": "On March 4, 2026, France’s Conseil d’État rejected Criteo’s challenge to the €40 million CNIL sanction.",
  "counterevidence": "The court expressly puts some remediation before imposition of the sanction. The sanction is not an order requiring every OneTag configuration to change.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F03",
  "headline": false,
  "claim": "The EDPB-hosted decision summary records that the retargeter introduced partner audits during the investigation.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S03"
  ],
  "passage": "implementing an audit program to scan the compliance of its partners since 2020",
  "support": [
   {
    "source_id": "IDN-H-S03",
    "passage": "implementing an audit program to scan the compliance of its partners since 2020",
    "locator": "Findings, Article 7(1) paragraph"
   }
  ],
  "scope_time": "2023-06-15; read 2026-11-11",
  "scope_geo": "EU / France",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The EDPB-hosted lead authority summary reports an audit program since 2020, contract action against a noncompliant partner and updated contractual proof requirements during the investigation. These pre-sanction steps do not establish compliance caused by the final fine. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "The activity documented here predates the operative June 2023 decision. It cannot establish implementation under that later disposition.",
  "final_wording": "The EDPB-hosted decision summary records that the retargeter introduced partner audits during the investigation.",
  "counterevidence": "The activity documented here predates the operative June 2023 decision. It cannot establish implementation under that later disposition.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F04",
  "headline": false,
  "claim": "The substituted UK notice required Experian to inform certain people whose records came from open sources that it processed their data for direct marketing.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S04"
  ],
  "passage": "their personal data has been obtained by Experian and is being processed by it for direct marketing purposes",
  "support": [
   {
    "source_id": "IDN-H-S04",
    "passage": "their personal data has been obtained by Experian and is being processed by it for direct marketing purposes",
    "locator": "Judgment paragraph 47, substituted notice paragraphs 1–3, pp. 20–21 (printed)"
   }
  ],
  "scope_time": "2024-04-22; read 2026-11-11",
  "scope_geo": "UK",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Para 47 reproduces a substituted notice covering defined people identified from open sources at the relevant date and later identified people, with detailed exceptions and possible notice through sources. The tribunal distinguished those cohorts from the historic group of around 5.3m. The notice did not require notification to every historical database record. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "The notice names three open sources and supplies exceptions. No result for a US identity-resolution SKU follows.",
  "final_wording": "The substituted UK notice required Experian to inform certain people whose records came from open sources that it processed their data for direct marketing.",
  "counterevidence": "The notice names three open sources and supplies exceptions. No result for a US identity-resolution SKU follows.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F05",
  "headline": false,
  "claim": "The UK Upper Tribunal dismissed the Information Commissioner’s appeal in the Experian matter on April 22, 2024.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S05"
  ],
  "passage": "Information Commissioner’s appeal dismissed.",
  "support": [
   {
    "source_id": "IDN-H-S05",
    "passage": "Information Commissioner’s appeal dismissed.",
    "locator": "Decision date and Judicial Summary"
   }
  ],
  "scope_time": "2024-04-22; read 2026-11-11",
  "scope_geo": "UK",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Official judicial summary separates the April 22 decision from April 29 publication. The UK Upper Tribunal dismissed the Commissioner’s appeal from the First-tier Tribunal, which had largely allowed Experian’s appeal and substituted a narrower notice. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "The original 2020 ICO notice was substantially altered by the 2023 First-tier Tribunal. The original was outside the H6 period.",
  "final_wording": "The UK Upper Tribunal dismissed the Information Commissioner’s appeal in the Experian matter on April 22, 2024.",
  "counterevidence": "The original 2020 ICO notice was substantially altered by the 2023 First-tier Tribunal. The original was outside the H6 period.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F06",
  "headline": false,
  "claim": "In June 2025 Experian told investors that it expected to comply with its substituted UK notice by July 24, 2025.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S06"
  ],
  "passage": "have complied with its obligations under the substituted enforcement notice by 24 July 2025.",
  "support": [
   {
    "source_id": "IDN-H-S06",
    "passage": "have complied with its obligations under the substituted enforcement notice by 24 July 2025.",
    "locator": "Use of personal data for direct marketing, fifth sentence; read immediately after “Experian Limited will”"
   }
  ],
  "scope_time": "2025-06-12; read 2026-11-11",
  "scope_geo": "UK",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The June 12 listing particulars state, prospectively, that Experian Limited would have complied by July 24, 2025. The text is the issuer’s representation, not proof of a completed notification program or US product change. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The source directly documents the attributed statement. Independent confirmation of underlying performance or compliance is outside it.",
  "limitations": "Future-tense statement. No regulator confirmation of completion or specific change to a US graph was located in the logged sources.",
  "final_wording": "In June 2025 Experian told investors that it expected to comply with its substituted UK notice by July 24, 2025.",
  "counterevidence": "Future-tense statement. No regulator confirmation of completion or specific change to a US graph was located in the logged sources.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F07",
  "headline": false,
  "claim": "The FTC’s July 2024 amended complaint cited household mapping as a use that Kochava advertised for its location feed.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S07"
  ],
  "passage": "Group devices by dwelling time and frequency at shared locations to map individual devices to households.",
  "support": [
   {
    "source_id": "IDN-H-S07",
    "passage": "Group devices by dwelling time and frequency at shared locations to map individual devices to households.",
    "locator": "Paragraph 88 and Household Mapping graphic, pp. 26–27"
   }
  ],
  "scope_time": "2024-07-15; read 2026-11-11",
  "scope_geo": "US",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The July 15, 2024 second amended FTC complaint (doc 86, para 88 and graphic) reproduces a marketed use case involving dwelling time/frequency at common locations. It contains allegations about a location feed, not an adjudicated household-graph result. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "This is an allegation and a quoted seller use case; it does not establish that the court adjudicated the performance of a household graph.",
  "final_wording": "The FTC’s July 2024 amended complaint cited household mapping as a use that Kochava advertised for its location feed.",
  "counterevidence": "This is an allegation and a quoted seller use case; it does not establish that the court adjudicated the performance of a household graph.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F08",
  "headline": false,
  "claim": "The June 2026 US Kochava order required Collective Data Solutions to provide a means for consumers to withdraw consent to use or disclosure of precise device-location data.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S08"
  ],
  "passage": "provide a simple, easily located means for consumers to withdraw consent",
  "support": [
   {
    "source_id": "IDN-H-S08",
    "passage": "provide a simple, easily located means for consumers to withdraw consent",
    "locator": "Provision VIII, withdrawing consent, pp. 18–19; signature p. 30"
   }
  ],
  "scope_time": "2026-06-25; read 2026-11-11",
  "scope_geo": "US",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Provision VIII of the signed June 25, 2026 order requires CDS to make withdrawal possible for its use/disclosure of precise device location. It permits a conspicuous link to device or OS settings. Separate conditional language extends the duty to Kochava if it engages in the specified handling of precise location data. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "The order permits specified operating-system or device controls and conditionally extends obligations to Kochava. An order term does not establish observed implementation, deletion, or a change to IdentityLink.",
  "final_wording": "The June 2026 US Kochava order required Collective Data Solutions to provide a means for consumers to withdraw consent to use or disclosure of precise device-location data.",
  "counterevidence": "The order permits specified operating-system or device controls and conditionally extends obligations to Kochava. An order term does not establish observed implementation, deletion, or a change to IdentityLink.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F09",
  "headline": false,
  "claim": "The FTC’s January 2025 Mobilewalla order restricted collection or retention of covered information accessed in online advertising auctions to participation in those auctions.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S09"
  ],
  "passage": "online advertising auctions for any other purpose than participating in such auctions.",
  "support": [
   {
    "source_id": "IDN-H-S09",
    "passage": "online advertising auctions for any other purpose than participating in such auctions.",
    "locator": "Provision II, printed p. 5; date on printed p. 16"
   }
  ],
  "scope_time": "2025-01-13; read 2026-11-11",
  "scope_geo": "US",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "FTC C-4811, Provision II, expressly restricts the purpose for which Mobilewalla can acquire or retain covered information accessed while participating in online ad auctions. The January 13, 2025 order is neither a ban on all participation nor a certification of subsequent execution. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "Covered Information has a defined scope; distinguish the final rule from the separate complaint allegations.",
  "final_wording": "The FTC’s January 2025 Mobilewalla order restricted collection or retention of covered information accessed in online advertising auctions to participation in those auctions.",
  "counterevidence": "Covered Information has a defined scope; distinguish the final rule from the separate complaint allegations.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F10",
  "headline": false,
  "claim": "Mobilewalla reported to investors in August 2026 that its US operations applied a third-party sensitive-location filter to incoming signals and outgoing deliveries after its FTC order.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S10",
   "IDN-HV-S02"
  ],
  "passage": "all inbound signals and outbound deliveries are screened against a third-party sensitive-location filter",
  "support": [
   {
    "source_id": "IDN-H-S10",
    "passage": "all inbound signals and outbound deliveries are screened against a third-party sensitive-location filter",
    "locator": "Mobilewalla business, Global Data Governance, paragraph beginning “Since the entry of the FTC consent order”"
   }
  ],
  "scope_time": "2026-08-12; read 2026-11-11",
  "scope_geo": "US",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The August 12 S-4 describes, as Mobilewalla’s own US implementation after the order, a third-party sensitive-location filter for all inbound signals and outbound deliveries. The October 16 amended filing repeats this description and six-month effectiveness checks. Both are the same business’s statements. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The source directly documents the attributed statement. Independent confirmation of underlying performance or compliance is outside it.",
  "limitations": "Issuer’s specific, retrospective account. The accessed record is not a filed sworn compliance report, independent assessor attestation, or FTC determination of implementation. Identity-product attribution also needs a named service.",
  "final_wording": "Mobilewalla reported to investors in August 2026 that its US operations applied a third-party sensitive-location filter to incoming signals and outgoing deliveries after its FTC order.",
  "counterevidence": "Issuer’s specific, retrospective account. The accessed record is not a filed sworn compliance report, independent assessor attestation, or FTC determination of implementation. Identity-product attribution also needs a named service.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F11",
  "headline": false,
  "claim": "California’s February 24, 2026 Disney judgment requires a logged-in consumer’s opt-out to apply across streaming services associated with the same Disney account.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S11",
   "IDN-H-S12"
  ],
  "passage": "effectuate the CONSUMER’S opt-out choice across all DISNEY STREAMING SERVICES",
  "support": [
   {
    "source_id": "IDN-H-S11",
    "passage": "effectuate the CONSUMER’S opt-out choice across all DISNEY STREAMING SERVICES",
    "locator": "Paragraph 26(a), printed p. 6; signed judicial date on p. 10"
   }
  ],
  "scope_time": "2026-02-11; read 2026-11-11",
  "scope_geo": "US / California",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "contradicted",
  "review_note": "The signed page 10 is dated February 11, 2026, and bears Judge Daniel M. Crowley’s signature. Paragraph 26(a) applies a logged-in opt-out across associated Disney streaming services. Paragraph 26(b) separately treats consumers who stay logged out or provide no additional information. The AG announced this settlement on February 11 as well. The original February 24 date is contradicted by the judge’s signed date.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "Paragraph 26(b) sets different terms when the consumer is not logged in. These are Disney obligations, not an order against the operator of an external household graph.",
  "final_wording": "California’s February 11, 2026 judgment requires Disney DTC and ABC Enterprises to honor a logged-in consumer’s opt-out across the Disney streaming services associated with that account.",
  "counterevidence": "Paragraph 26(b) sets different terms when the consumer is not logged in. These are Disney obligations, not an order against the operator of an external household graph.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F12",
  "headline": false,
  "claim": "The California attorney general announced the Disney opt-out settlement on February 11, 2026.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S12",
   "IDN-H-S11"
  ],
  "passage": "announced a settlement",
  "support": [
   {
    "source_id": "IDN-H-S12",
    "passage": "announced a settlement",
    "locator": "Dateline and opening paragraph"
   }
  ],
  "scope_time": "2026-02-11; read 2026-11-11",
  "scope_geo": "US / California",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The California Attorney General’s February 11, 2026 release describes a settlement with Disney and USD 2.75 million in civil penalties. It describes gaps uncovered in the investigation. The Los Angeles court judgment independently supplies the binding terms. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "The California AG announced the settlement on February 11, 2026, the same day the judge signed the order. The AG account describes allegations rather than adjudicated violations.",
  "final_wording": "The California attorney general announced the Disney opt-out settlement on February 11, 2026.",
  "counterevidence": "The California AG announced the settlement on February 11, 2026, the same day the judge signed the order. The AG account describes allegations rather than adjudicated violations.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F13",
  "headline": false,
  "claim": "Texas’s December 2025 petition against Sony cited Samba Interactive TV when describing the opt-out path on BRAVIA televisions.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S13",
   "IDN-HV-S01"
  ],
  "passage": "Fig. 5. Opt-Out Screen for Samba Interactive TV for BRAVIA Models.",
  "support": [
   {
    "source_id": "IDN-H-S13",
    "passage": "Fig. 5. Opt-Out Screen for Samba Interactive TV for BRAVIA Models.",
    "locator": "Paragraphs 57–63 and Figure 5; see caption and signature"
   }
  ],
  "scope_time": "2025-12-15; read 2026-11-11",
  "scope_geo": "US / Texas",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The original Texas pleading dated December 15, 2025 names Sony Corporation of America and Sony Electronics, Inc. Figure 5 and paras 57–63 refer to Samba Interactive TV on BRAVIA models. The caption does not name Samba as a defendant and the petition does not decide liability. The AG still described the distinct Sony case as ongoing on May 11, 2026. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "A pleading against Sony, not a finding of wrongdoing against Samba TV or proof of a change to its graph. Samba is the author’s declared current employer and excluded from scoring.",
  "final_wording": "Texas’s December 2025 petition against Sony cited Samba Interactive TV when describing the opt-out path on BRAVIA televisions.",
  "counterevidence": "A pleading against Sony, not a finding of wrongdoing against Samba TV or proof of a change to its graph. Samba is the author’s declared current employer and excluded from scoring.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F14",
  "headline": false,
  "claim": "Texas’s April 2026 agreed judgment against LG requires affirmative express consent for covered viewing-data use after its 180-day transition.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S14",
   "IDN-HV-S01"
  ],
  "passage": "[IDN-H-S14, Paragraph 16, printed p. 5; effective-date definition, p. 2; blank judicial signature/date lines, p. 9] as of 180 days from the Effective Date [IDN-H-S14, Paragraph 16(a), printed p. 5] without obtaining Consumers’ Affirmative Express Consent.",
  "support": [
   {
    "source_id": "IDN-H-S14",
    "passage": "as of 180 days from the Effective Date",
    "locator": "Paragraph 16, printed p. 5; effective-date definition, p. 2; blank judicial signature/date lines, p. 9"
   },
   {
    "source_id": "IDN-H-S14",
    "passage": "without obtaining Consumers’ Affirmative Express Consent.",
    "locator": "Paragraph 16(a), printed p. 5"
   }
  ],
  "scope_time": "2026-05-11 AG announcement; judicial effective date unverified; read 2026-11-11",
  "scope_geo": "US / Texas",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "In Bell County cause 25DCV358507, the state’s and LG’s posted agreed text makes covered viewing-data practices subject to affirmative express consent beginning 180 days after judicial signature and entry. The date and judge’s signature are both blank on page 9. The Texas AG confirms the settlement on May 11, 2026. The posted evidence does not establish whether or when a judge signed a different copy. A settlement is confirmed. The April judgment date and onset of the 180-day period are unverified.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "Public copies confirm a settlement and its agreed terms. The judge’s signature/date lines in the posted text are blank. A start date, implemented graph change and applicability to an external household identity service remain unverified.",
  "final_wording": "On May 11, 2026, Texas announced a settlement with LG Electronics U.S.A. The agreed terms call for affirmative express consent for covered viewing-data practices 180 days after judicial signature and entry. The posted copy leaves the judge’s signature and date blank.",
  "counterevidence": "Public copies confirm a settlement and its agreed terms. The judge’s signature/date lines in the posted text are blank. A start date, implemented graph change and applicability to an external household identity service remain unverified.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F15",
  "headline": false,
  "claim": "France’s September 2025 order required Google to explain the advertising cookies involved in creating a Google account to users in France.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S15"
  ],
  "passage": "cookies intended for advertising purposes will necessarily be deposited when creating a Google account.",
  "support": [
   {
    "source_id": "IDN-H-S15",
    "passage": "cookies intended for advertising purposes will necessarily be deposited when creating a Google account.",
    "locator": "Decision paragraph 269 and operative injunction, advertising-cookie limb"
   }
  ],
  "scope_time": "2025-09-01; read 2026-11-11",
  "scope_geo": "EU / France",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The French CNIL’s September 1, 2025 order requires the named Google entities to tell users in France that ad cookies necessarily accompany Google account creation. A distinct limb covers Gmail ads inserted between private messages. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "This concerned account creation. It did not order a change to Chrome’s third-party-cookie default, Topics or Protected Audience.",
  "final_wording": "France’s September 2025 order required Google to explain the advertising cookies involved in creating a Google account to users in France.",
  "counterevidence": "This concerned account creation. It did not order a change to Chrome’s third-party-cookie default, Topics or Protected Audience.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F16",
  "headline": false,
  "claim": "In September 2026 the CNIL closed the Google injunction after confirming a disclosure change to the account-creation flow.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S16",
   "IDN-H-S15"
  ],
  "passage": "The companies completed the Google account creation path by adding information",
  "support": [
   {
    "source_id": "IDN-H-S16",
    "passage": "The companies completed the Google account creation path by adding information",
    "locator": "The decision, first and second paragraphs; 23 September decision, 14 October announcement"
   }
  ],
  "scope_time": "2026-09-23; read 2026-11-11",
  "scope_geo": "EU / France",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "The CNIL’s October 14 announcement reports its September 23, 2026 decision closing the injunction after verification of changed account-creation information and a change in the Gmail ad format. The closure concerns that order only; the panel expressly reserved broader Article 82 assessment. The closure of the whole injunction rested on both limbs.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "An original injunction and distinct regulator confirmation exist for this platform use. It is a boundary comparison outside the A–D service population.",
  "final_wording": "On September 23, 2026, the CNIL closed its injunction after Google changed its French account-creation disclosure and the format of Gmail ads. The closure applied to those two requirements.",
  "counterevidence": "An original injunction and distinct regulator confirmation exist for this platform use. It is a boundary comparison outside the A–D service population.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F17",
  "headline": false,
  "claim": "In May 2025 the Belgian authority reported that the Market Court annulled its IAB Europe decision on procedural grounds while confirming the fine.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S17"
  ],
  "passage": "Although decision 21/2022 is annulled for procedural reasons, the Market Court endorses the reasoning of the Belgian DPA and confirms the fine",
  "support": [
   {
    "source_id": "IDN-H-S17",
    "passage": "Although decision 21/2022 is annulled for procedural reasons, the Market Court endorses the reasoning of the Belgian DPA and confirms the fine",
    "locator": "Opening paragraph, 14 May 2025"
   }
  ],
  "scope_time": "2025-05-14; read 2026-11-11",
  "scope_geo": "EU / Belgium",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The Belgian regulator’s May 14, 2025 report says the Market Court procedurally annulled decision 21/2022 and, exercising full jurisdiction, confirmed the EUR 250,000 fine. The court rejected joint control over operations taking place entirely within OpenRTB. A later dispute over action-plan validation is separate. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "The authority also reports that the court rejected joint controllership for processing taking place entirely within OpenRTB. Framework case, not an enforcement outcome against an ID vendor.",
  "final_wording": "In May 2025 the Belgian authority reported that the Market Court annulled its IAB Europe decision on procedural grounds while confirming the fine.",
  "counterevidence": "The authority also reports that the court rejected joint controllership for processing taking place entirely within OpenRTB. Framework case, not an enforcement outcome against an ID vendor.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F18",
  "headline": false,
  "claim": "France’s Conseil d’État rejected Yahoo EMEA Limited’s challenge to the CNIL decision on cookie placement and withdrawal in October 2025.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S18"
  ],
  "passage": "La requête de la société Yahoo EMEA Limited est rejetée",
  "support": [
   {
    "source_id": "IDN-H-S18",
    "passage": "La requête de la société Yahoo EMEA Limited est rejetée",
    "locator": "Article 1er, read with paragraphs 21–23"
   }
  ],
  "scope_time": "2025-10-07; read 2026-11-11",
  "scope_geo": "EU / France",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "In decision 494300 dated October 7, 2025, article 1 dismisses Yahoo EMEA Limited’s application; the December 2023 EUR 10m sanction concerned initial cookie placement and consent withdrawal. The court refers to partial remediation, without identifying a change to ConnectID. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "The respondent’s name alone does not map this website and mail matter to Yahoo ConnectID.",
  "final_wording": "France’s Conseil d’État rejected Yahoo EMEA Limited’s challenge to the CNIL decision on cookie placement and withdrawal in October 2025.",
  "counterevidence": "The respondent’s name alone does not map this website and mail matter to Yahoo ConnectID.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F19",
  "headline": false,
  "claim": "The FTC’s April 2024 X-Mode/Outlogic order required a sensitive-location program within 180 days of issuance.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S19"
  ],
  "passage": "within 180 days of the issuance of this Order, must establish and implement",
  "support": [
   {
    "source_id": "IDN-H-S19",
    "passage": "within 180 days of the issuance of this Order, must establish and implement",
    "locator": "Provision III, opening paragraph, pp. 5–6; issue date printed p. 17"
   }
  ],
  "scope_time": "2024-04-11; read 2026-11-11",
  "scope_geo": "US",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "FTC C-4802, final decision issued April 11, 2024. Provision III expressly runs from issuance and requires creation and maintenance of the sensitive-location program within 180 days. It is an obligation of named respondents, not an independently verified rollout. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "Obligation addressed to X-Mode/Outlogic. Additional proof would be needed to assign a changed identity service or observed compliance.",
  "final_wording": "The FTC’s April 2024 X-Mode/Outlogic order required a sensitive-location program within 180 days of issuance.",
  "counterevidence": "Obligation addressed to X-Mode/Outlogic. Additional proof would be needed to assign a changed identity service or observed compliance.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F20",
  "headline": false,
  "claim": "The FTC’s April 2024 InMarket order prohibits selling or licensing defined location data for valuable consideration.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S20"
  ],
  "passage": "must not sell or license Location Data in exchange for any valuable consideration.",
  "support": [
   {
    "source_id": "IDN-H-S20",
    "passage": "must not sell or license Location Data in exchange for any valuable consideration.",
    "locator": "Provision II, sale or licensing of Location Data, and final signature block"
   }
  ],
  "scope_time": "2024-04-29; read 2026-11-11",
  "scope_geo": "US",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "InMarket final order C-4803 was issued April 29, 2024. Provision II bans selling or licensing defined Location Data for valuable consideration. Targeting/categorising is covered separately in Provision III. The order sets duties without establishing how every product implemented them. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "Distinct from the next provision on products categorizing or targeting people based on sensitive location data. Product-specific compliance not established here.",
  "final_wording": "The FTC’s April 2024 InMarket order prohibits selling or licensing defined location data for valuable consideration.",
  "counterevidence": "Distinct from the next provision on products categorizing or targeting people based on sensitive location data. Product-specific compliance not established here.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F21",
  "headline": false,
  "claim": "The January 2025 Gravy Analytics/Venntel order required a sensitive-location program within 90 days of its effective date.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S21"
  ],
  "passage": "within 90 days of the effective date of this Order, must establish and implement",
  "support": [
   {
    "source_id": "IDN-H-S21",
    "passage": "within 90 days of the effective date of this Order, must establish and implement",
    "locator": "Final decision and order, Provision III, printed p. 6 of the order, PDF p. 20"
   }
  ],
  "scope_time": "2025-01-13; read 2026-11-11",
  "scope_geo": "US",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "In C-4810 the final order within the FTC package (issued January 13, 2025), Provision III runs from the effective date; within 90 days respondents must establish and implement, and then maintain, the sensitive-location program. Distinct from the allegations in the complaint contained in the same package. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "This is an order deadline, not when the program went live. The earlier pages in the bundled PDF are the complaint.",
  "final_wording": "The January 2025 Gravy Analytics/Venntel order required a sensitive-location program within 90 days of its effective date.",
  "counterevidence": "This is an order deadline, not when the program went live. The earlier pages in the bundled PDF are the complaint.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-H-F22",
  "headline": false,
  "claim": "The Court of Justice held in March 2024 that a TC String constitutes personal data when reasonable linkage to an identifier allows the person to be identified.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S22"
  ],
  "passage": "reasonable means, be associated with an identifier",
  "support": [
   {
    "source_id": "IDN-H-S22",
    "passage": "reasonable means, be associated with an identifier",
    "locator": "Paragraph 51, answer to first question, read with paragraphs 44–50 and operative part"
   }
  ],
  "scope_time": "2024-03-07; read 2026-11-11",
  "scope_geo": "EU",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The CJEU’s March 7, 2024 preliminary ruling, para 51 and point 1 of its operative part, conditions the personal-data finding on reasonable association with an identifier that makes the person identifiable. Point 2 separately limits attribution of subsequent processing. The English judgment was read via the EU Publications Office. Passages, locators, date, named party and scope checked against the controlling record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The operative text or the issuing party’s own record supports this wording.",
  "limitations": "This is the answer to a preliminary question about the TCF. It does not establish that any specific commercial ID honours consent or exposes a person’s name.",
  "final_wording": "The Court of Justice held in March 2024 that a TC String constitutes personal data when reasonable linkage to an identifier allows the person to be identified.",
  "counterevidence": "This is the answer to a preliminary question about the TCF. It does not establish that any specific commercial ID honours consent or exposes a person’s name.",
  "stream": "H",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-I-F01",
  "headline": false,
  "claim": "CIMM’s buyer guide asks how many matched records can actually be addressed on the buyer’s primary activation platforms.",
  "chapter": "12",
  "source_ids": [
   "IDN-I-S01"
  ],
  "passage": "of the matched records, how many are addressable across primary activation platforms.",
  "support": [
   {
    "source_id": "IDN-I-S01",
    "passage": "of the matched records, how many are addressable across primary activation platforms.",
    "locator": "p. 17, Kicking the Tires, Match Test"
   }
  ],
  "scope_time": "April 2026",
  "scope_geo": "US industry coalition; guidance not population estimates",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "Printed page 17 of CIMM’s April 2026 guide separates supplied and matched records from the matched records that remain addressable on primary activation platforms. It frames this as a buyer’s evaluation question. No deployment or observed survival rate is reported. CIMM describes mixed-method guidance drawn from interviews and references. Its guide is a source of original buyer advice, not a formal standard, regulator record or independent product test.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Procurement question. No evidence that a specific end user implements it or that any platform returns the entire universe.",
  "final_wording": "CIMM’s April 2026 buyer guide recommends checking how many matched records can be addressed on the buyer’s primary activation platforms.",
  "counterevidence": "Procurement question. No evidence that a specific end user implements it or that any platform returns the entire universe.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-I-F02",
  "headline": false,
  "claim": "CIMM’s buyer guide calls for a truth set when evaluating matching accuracy.",
  "chapter": "3, 12",
  "source_ids": [
   "IDN-I-S01"
  ],
  "passage": "you will need to establish a truth set",
  "support": [
   {
    "source_id": "IDN-I-S01",
    "passage": "you will need to establish a truth set",
    "locator": "p. 20, Data Quality, paragraph below Figure 6.1"
   }
  ],
  "scope_time": "April 2026",
  "scope_geo": "US industry coalition; guidance not population estimates",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "On printed page 20, CIMM advises building a reference truth set and gives precision, recall and accuracy concepts. The paper cites industry material and interviews with more than 40 contributors to date, some more than once. It supplies no validation result for a named product. CIMM describes mixed-method guidance drawn from interviews and references. Its guide is a source of original buyer advice, not a formal standard, regulator record or independent product test.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Guidance alone supplies no labeled independent test on an admitted product.",
  "final_wording": "CIMM’s April 2026 buyer guide recommends establishing a truth set to evaluate match accuracy and distinguishes precision from recall.",
  "counterevidence": "Guidance alone supplies no labeled independent test on an admitted product.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-I-F03",
  "headline": false,
  "claim": "Disney’s 2023 LiveRamp destination terms define a custom segment through overlap between advertiser and Disney data.",
  "chapter": "6, 12",
  "source_ids": [
   "IDN-I-S02"
  ],
  "passage": "an overlap between Advertiser Data and Disney Data conducted by LiveRamp",
  "support": [
   {
    "source_id": "IDN-I-S02",
    "passage": "an overlap between Advertiser Data and Disney Data conducted by LiveRamp",
    "locator": "Clause 1, definition of Custom Segment"
   }
  ],
  "scope_time": "2023-07-26 version",
  "scope_geo": "United States; Disney Advertising Sales / Hulu",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The 26 July 2023 Disney/Hulu click-through terms define a Custom Segment as advertiser/Disney data overlap performed by LiveRamp for use on Disney properties. Accepting a destination term defines a possible transaction path; it does not document a completed campaign. Direct record of the publisher’s own terms or the company’s policy under this paper’s platform-policy rule. It does not establish compliance or actual execution.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Defines the commercial handoff; the terms do not give a match yield, named campaign or performance warranty.",
  "final_wording": "Disney’s 2023 LiveRamp destination terms define a custom segment through overlap between advertiser and Disney data.",
  "counterevidence": "Defines the commercial handoff; the terms do not give a match yield, named campaign or performance warranty.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-I-F04",
  "headline": false,
  "claim": "Disney’s destination terms require the submitting party to warrant rights and consents for the advertiser data.",
  "chapter": "6, 12",
  "source_ids": [
   "IDN-I-S02"
  ],
  "passage": "You have obtained and will maintain all rights and consents necessary",
  "support": [
   {
    "source_id": "IDN-I-S02",
    "passage": "You have obtained and will maintain all rights and consents necessary",
    "locator": "Clause 2, advertiser representations"
   }
  ],
  "scope_time": "2023-07-26 version",
  "scope_geo": "United States; Disney Advertising Sales / Hulu",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Clause 2 puts the obligation to obtain and maintain the necessary rights and consents on the submitting party. Clause 5 also restricts specified data, including certain opt-outs, and generally limits non-US-resident data absent written agreement. These are contractual representations, not proof they were fulfilled. Direct record of the publisher’s own terms or the company’s policy under this paper’s platform-policy rule. It does not establish compliance or actual execution.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "A contractual representation does not establish a recipient’s technical reaction or compliant behavior.",
  "final_wording": "Disney’s destination terms require the submitting party to warrant rights and consents for the advertiser data.",
  "counterevidence": "A contractual representation does not establish a recipient’s technical reaction or compliant behavior.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-I-F05",
  "headline": false,
  "claim": "HP’s US advertising notice says it works with partners to turn hashed emails into advertising identifiers such as UID2 for advertising and measurement on other platforms.",
  "chapter": "",
  "source_ids": [
   "IDN-I-S03"
  ],
  "passage": "converting hashed email addresses into advertising identifiers, such as UID2",
  "support": [
   {
    "source_id": "IDN-I-S03",
    "passage": "converting hashed email addresses into advertising identifiers, such as UID2",
    "locator": "How we use and share data, paragraph naming The Trade Desk"
   }
  ],
  "scope_time": "June 2026 version",
  "scope_geo": "United States version of HP privacy notice",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "HP’s US notice, updated June 2026, names The Trade Desk as an example of a partner and UID2 as one resulting identifier for third-party targeted advertising and measurement. HP separately says it requires consent for personalized ads using personal data and identifies an opt-out. No volume or compliance test is shown. Direct record of the publisher’s own terms or the company’s policy under this paper’s platform-policy rule. It does not establish compliance or actual execution.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "HP names an opt-out route. The notice does not include logs of auctions, revocation or a buyer’s matching outcomes.",
  "final_wording": "HP’s US advertising notice says it works with partners to turn hashed emails into advertising identifiers such as UID2 for advertising and measurement on other platforms.",
  "counterevidence": "HP names an opt-out route. The notice does not include logs of auctions, revocation or a buyer’s matching outcomes.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-I-F06",
  "headline": false,
  "claim": "Dentsu reported in January 2025 that its New Stream Media team was testing its Merkury/Trade Desk integration with Hy-Vee’s RedMedia.",
  "chapter": "12",
  "source_ids": [
   "IDN-I-S04"
  ],
  "passage": "has been testing the integration with clients like Hy-Vee, and its RedMedia",
  "support": [
   {
    "source_id": "IDN-I-S04",
    "passage": "has been testing the integration with clients like Hy-Vee, and its RedMedia",
    "locator": "Introductory narrative, named retail-media test"
   }
  ],
  "scope_time": "2025-01-08 announcement",
  "scope_geo": "US announcement; Hy-Vee RedMedia",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Dentsu’s 8 January 2025 US release says its New Stream Media group had been testing the Merkury/Trade Desk integration with clients including Hy-Vee and its RedMedia. UID2 connections are described at the integration level; no client-specific measured match rate and no denominator are provided.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Statement by the agency/technology owner. No client file counts, match precision or campaign lift identified by the cited test.",
  "final_wording": "Dentsu reported in January 2025 that its New Stream Media team was testing its Merkury/Trade Desk integration with Hy-Vee’s RedMedia.",
  "counterevidence": "Statement by the agency/technology owner. No client file counts, match precision or campaign lift identified by the cited test.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-I-F07",
  "headline": false,
  "claim": "iProspect’s October 2025 agency appointment announcement calls for Merkury to connect Hy-Vee enterprise media, RedMedia and loyalty programs.",
  "chapter": "12",
  "source_ids": [
   "IDN-I-S05"
  ],
  "passage": "will leverage iProspect’s Merkury identity solution as the connective backbone",
  "support": [
   {
    "source_id": "IDN-I-S05",
    "passage": "will leverage iProspect’s Merkury identity solution as the connective backbone",
    "locator": "Paragraph on Hy-Vee’s intended use of Merkury"
   }
  ],
  "scope_time": "2025-10-16 announcement",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "On 16 October 2025 iProspect announced its appointment as Hy-Vee’s media agency. Use of Merkury across enterprise media, RedMedia and loyalty is described in the future tense. This statement is from the dentsu group and is not independent confirmation of its earlier test.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Future-tense deployment plan. The source is a dentsu company, so it is not independent replication of the earlier test.",
  "final_wording": "iProspect’s October 2025 agency appointment announcement calls for Merkury to connect Hy-Vee enterprise media, RedMedia and loyalty programs.",
  "counterevidence": "Future-tense deployment plan. The source is a dentsu company, so it is not independent replication of the earlier test.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-I-F08",
  "headline": false,
  "claim": "Hy-Vee’s RedMedia describes combining its first-party shopper data with outside advertising-firm data for off-site targeting.",
  "chapter": "12",
  "source_ids": [
   "IDN-I-S06"
  ],
  "passage": "We mesh Hy-Vee exclusive first-party data with data from leading advertising firms.",
  "support": [
   {
    "source_id": "IDN-I-S06",
    "passage": "We mesh Hy-Vee exclusive first-party data with data from leading advertising firms.",
    "locator": "Solutions, off-site audience targeting"
   }
  ],
  "scope_time": "Page read 2026-11-11",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "RedMedia’s off-site advertising section says it combines Hy-Vee’s exclusive first-party data with information from advertising firms to target shoppers on websites and social feeds. Its own page does not name Merkury, UID2 or this test.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "This retailer-owned page does not name UID2, so it corroborates the buyer task but cannot corroborate that technical integration.",
  "final_wording": "Hy-Vee’s RedMedia describes combining its first-party shopper data with outside advertising-firm data for off-site targeting.",
  "counterevidence": "This retailer-owned page does not name UID2, so it corroborates the buyer task but cannot corroborate that technical integration.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-I-F09",
  "headline": false,
  "claim": "Disney’s July 2022 release announced an agreement to connect its Audience Graph to UID2 and placed the advertiser rollout in the following months.",
  "chapter": "",
  "source_ids": [
   "IDN-I-S07"
  ],
  "passage": "implementing this expanded capability with advertisers over the next several months",
  "support": [
   {
    "source_id": "IDN-I-S07",
    "passage": "implementing this expanded capability with advertisers over the next several months",
    "locator": "Final implementation paragraph"
   }
  ],
  "scope_time": "2022-07-12 announcement",
  "scope_geo": "United States launch announcement",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The July 2022 agreement names Disney’s Audience Graph and UID2. Disney says implementation with advertisers is underway over the next several months. It gives no completion date, coverage total or observed transaction for that route.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "An agreement and rollout plan cannot demonstrate completed advertiser activation or graph lineage.",
  "final_wording": "Disney’s July 2022 release announced an agreement to connect its Audience Graph to UID2 and placed the advertiser rollout in the following months.",
  "counterevidence": "An agreement and rollout plan cannot demonstrate completed advertiser activation or graph lineage.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-I-F10",
  "headline": false,
  "claim": "Roku documented a buyer path from The Trade Desk through Roku Exchange to activate against Roku first-party data using UID2.",
  "chapter": "6, 12",
  "source_ids": [
   "IDN-I-S08"
  ],
  "passage": "The Trade Desk's advertisers can use UID2 to activate against Roku’s first-party data through Roku Exchange.",
  "support": [
   {
    "source_id": "IDN-I-S08",
    "passage": "The Trade Desk's advertisers can use UID2 to activate against Roku’s first-party data through Roku Exchange.",
    "locator": "Here’s how it works"
   }
  ],
  "scope_time": "2024-08-01 publication",
  "scope_geo": "US-facing Roku Advertising offer; specific impression geography not given",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Roku’s 1 August 2024 operational explanation identifies TTD advertisers, UID2 keyed to Roku first-party data and the Roku Exchange. Roku’s headline streaming-household total is not the number of UID2 matches or advertising customers.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Publisher’s named route, not a bid-level observation, household truth test or measured conversion increase.",
  "final_wording": "Roku documented a buyer path from The Trade Desk through Roku Exchange to activate against Roku first-party data using UID2.",
  "counterevidence": "Publisher’s named route, not a bid-level observation, household truth test or measured conversion increase.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-I-F11",
  "headline": false,
  "claim": "In April 2021 Mediavine said its Grow.me toolkit had active integrations with LiveRamp ATS, UID2 and ID5 Universal ID.",
  "chapter": "5",
  "source_ids": [
   "IDN-I-S09"
  ],
  "passage": "active integrations with LiveRamp’s ATS, The Trade Desk’s UID 2.0 and ID5’s Universal ID.",
  "support": [
   {
    "source_id": "IDN-I-S09",
    "passage": "active integrations with LiveRamp’s ATS, The Trade Desk’s UID 2.0 and ID5’s Universal ID.",
    "locator": "Datelined opening paragraph"
   }
  ],
  "scope_time": "2021-04-22 announcement",
  "scope_geo": "US publisher ad-management company; network traffic not geographically isolated",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Mediavine specifically says Grow.me is integrated with ID5 Universal ID. The next sentence attributes three active integrations, including ATS and UID2, to Mediavine. The announcement does not expressly assign all three integrations to Grow.me or confirm use by every publisher.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Historical, operator-reported integration. Neither all-network deployment nor the recipient’s rights-handling path is established.",
  "final_wording": "In April 2021 Mediavine said Grow.me was integrated with ID5 Universal ID. It also reported that Mediavine had active integrations with LiveRamp ATS, UID2 and ID5.",
  "counterevidence": "Historical, operator-reported integration. Neither all-network deployment nor the recipient’s rights-handling path is established.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-I-F12",
  "headline": false,
  "claim": "In November 2022 TelevisaUnivision announced an intended clean-room integration between its US Hispanic household graph and Omnicom’s Omni ID.",
  "chapter": "",
  "source_ids": [
   "IDN-I-S10"
  ],
  "passage": "will integrate with OMG’s identity solution, Omni ID, via privacy-oriented clean room technology",
  "support": [
   {
    "source_id": "IDN-I-S10",
    "passage": "will integrate with OMG’s identity solution, Omni ID, via privacy-oriented clean room technology",
    "locator": "Opening paragraph, prospective integration"
   }
  ],
  "scope_time": "2022-11-17 announcement",
  "scope_geo": "US Hispanic households",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The publisher’s 17 November 2022 statement says its Hispanic household graph will integrate with Omnicom Media Group’s Omni ID using a clean room. Announced use cases include targeting and measurement. No proof of completed activation or verified coverage is supplied.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Commercial plan rather than a commissioned accuracy test. No IP-to-household assignment or refresh interval is disclosed here.",
  "final_wording": "In November 2022 TelevisaUnivision announced an intended clean-room integration between its US Hispanic household graph and Omnicom’s Omni ID.",
  "counterevidence": "Commercial plan rather than a commissioned accuracy test. No IP-to-household assignment or refresh interval is disclosed here.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-I-F13",
  "headline": false,
  "claim": "Publicis announced in 2021 that its trading partnership would connect Epsilon CORE ID with UID2.",
  "chapter": "",
  "source_ids": [
   "IDN-I-S11"
  ],
  "passage": "The partnership will bring interoperability between Epsilon CORE ID and Unified ID 2.0",
  "support": [
   {
    "source_id": "IDN-I-S11",
    "passage": "The partnership will bring interoperability between Epsilon CORE ID and Unified ID 2.0",
    "locator": "Partnership description"
   }
  ],
  "scope_time": "2021 announcement",
  "scope_geo": "Announced in Paris; US Publicis Media business discussed",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The Publicis release frames CORE ID/UID2 interoperability as what the partnership will deliver and ties a planned personalized-media platform to TTD’s DSP. The alliance is not evidence that all agency transactions used this route or that interoperability was already live.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "A future integration of separate identifiers. Does not show that the two identifiers share predecessor edges. Agency owns Epsilon.",
  "final_wording": "Publicis announced in 2021 that its trading partnership would connect Epsilon CORE ID with UID2.",
  "counterevidence": "A future integration of separate identifiers. Does not show that the two identifiers share predecessor edges. Agency owns Epsilon.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-I-F14",
  "headline": false,
  "claim": "Trusted Media Brands’ privacy notice describes a possible LiveRamp handoff that returns a code the publisher may store in its own cookie.",
  "chapter": "5",
  "source_ids": [
   "IDN-I-S12"
  ],
  "passage": "LiveRamp returns an online identification code that we may store in our first-party cookie",
  "support": [
   {
    "source_id": "IDN-I-S12",
    "passage": "LiveRamp returns an online identification code that we may store in our first-party cookie",
    "locator": "Online advertising notice, passage immediately above LiveRamp opt-out link"
   }
  ],
  "scope_time": "Privacy policy updated 2026-07-14; read 2026-11-11.",
  "scope_geo": "US publisher website; precise route/jurisdiction depends on user",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "TMB’s notice, last updated 14 July 2026, describes possible supply of hashed email, IP and browser/OS information to identity partners including LiveRamp. The returned code may be kept in a first-party cookie, and the notice supplies an opt-out. It does not expressly identify the code as RampID. Direct record of the publisher’s own terms or the company’s policy under this paper’s platform-policy rule. It does not establish compliance or actual execution.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Notice says may. No evidence of all-site issuance or actual deletion or downstream honor after opt-out.",
  "final_wording": "Trusted Media Brands’ privacy notice describes a possible LiveRamp handoff that returns a code the publisher may store in its own cookie.",
  "counterevidence": "Notice says may. No evidence of all-site issuance or actual deletion or downstream honor after opt-out.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-I-F15",
  "headline": false,
  "claim": "Nasdaq’s third-party participant list says it may share hashed email, IP and advertising identifiers with LiveRamp for targeted advertising.",
  "chapter": "",
  "source_ids": [
   "IDN-I-S13"
  ],
  "passage": "We may share hashed and de-identified email addresses, IP address, and advertising identifiers with LiveRamp",
  "support": [
   {
    "source_id": "IDN-I-S13",
    "passage": "We may share hashed and de-identified email addresses, IP address, and advertising identifiers with LiveRamp",
    "locator": "LiveRamp subsection"
   }
  ],
  "scope_time": "Participant list updated 2023-12-01; read 2026-11-11.",
  "scope_geo": "Nasdaq website; visitors not geographically isolated",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Nasdaq’s list dated 1 December 2023 names LiveRamp and conditionally describes sharing de-identified/hashed email, IP addresses and ad IDs for linkage and targeting. It links an opt-out. Separate sections for other partners do not establish that the exact same IDs were sent to each. Direct record of the publisher’s own terms or the company’s policy under this paper’s platform-policy rule. It does not establish compliance or actual execution.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Policy establishes disclosure language and directs users to an opt-out URL. It does not show event frequency or a tested recipient-side consequence.",
  "final_wording": "Nasdaq’s third-party participant list says it may share hashed email, IP and advertising identifiers with LiveRamp for targeted advertising.",
  "counterevidence": "Policy establishes disclosure language and directs users to an opt-out URL. It does not show event frequency or a tested recipient-side consequence.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-I-F16",
  "headline": false,
  "claim": "Roku announced that its inventory would be available for encrypted identity matching through Google Display & Video 360 as a Confidential Publisher Match launch partner.",
  "chapter": "6",
  "source_ids": [
   "IDN-I-S14"
  ],
  "passage": "Roku will provide Display & Video 360 advertisers with greater access",
  "support": [
   {
    "source_id": "IDN-I-S14",
    "passage": "Roku will provide Display & Video 360 advertisers with greater access",
    "locator": "Opening description of Roku participation"
   }
  ],
  "scope_time": "2026-03-23 announcement",
  "scope_geo": "US-facing Roku Media offering",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Roku’s 23 March 2026 article reports it joined Google’s deterministic launch and describes encrypted matching between advertisers’ first-party data and Roku Media inventory via DV360. Availability is framed prospectively for the launch partnership. No numeric gain, completed match or availability across all inventory is established.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited primary text establishes the attributed statement; scope follows the source and the stated limits.",
  "limitations": "Prospective announcement. Publisher-side statement does not establish export of a reusable person-level identifier or a measured improvement over another destination.",
  "final_wording": "On 23 March 2026 Roku announced it was a launch partner for Google’s Confidential Publisher Match and described a route for DV360 advertisers to match first-party data to Roku Media inventory.",
  "counterevidence": "Prospective announcement. Publisher-side statement does not establish export of a reusable person-level identifier or a measured improvement over another destination.",
  "stream": "I",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-J-F01",
  "headline": false,
  "claim": "AdCP’s 3.2.8 Trusted Match specification defines a publisher-to-buyer identity request carrying opaque tokens while prohibiting page context on that path.",
  "chapter": "10, 12",
  "source_ids": [
   "IDN-J-S01"
  ],
  "passage": "one or more opaque identity tokens, and an optional package ID list. MUST NOT contain page context.",
  "support": [
   {
    "source_id": "IDN-J-S01",
    "passage": "one or more opaque identity tokens, and an optional package ID list. MUST NOT contain page context.",
    "locator": "IdentityMatchRequest, description immediately before field table"
   }
  ],
  "scope_time": "AdCP 3.2.8 Trusted Match documentation revised 2026-10-29 and read 2026-11-11.",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "The IdentityMatchRequest section in the 3.2.8 documentation specifies the publisher as caller, routing via the TMP router to buyer agents, one or more opaque identity tokens, and no page context. The page marks Trusted Match experimental. Its consent object includes regulated-jurisdiction handling. This is schema-level evidence.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "A specification sets interface behavior; it does not demonstrate that any buyer used it.",
  "final_wording": "The experimental Trusted Match specification in AdCP 3.2.8 defines an identity request from a publisher via a router to buyer agents. The request carries one or more opaque identity tokens and must omit page context.",
  "counterevidence": "A specification sets interface behavior; it does not demonstrate that any buyer used it.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F02",
  "headline": false,
  "claim": "The AdCP issuer described clean-room activation as experimental in its October 22 account of the 3.2 release.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S02"
  ],
  "passage": "Reliable reporting, clean-room activation and rights attestations are experimental in 3.2",
  "support": [
   {
    "source_id": "IDN-J-S02",
    "passage": "Reliable reporting, clean-room activation and rights attestations are experimental in 3.2",
    "locator": "The protocol: AdCP 3.2 is live, final paragraph"
   }
  ],
  "scope_time": "2026-10-22, AdCP 3.2",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The October 22, 2026 town hall report explicitly classifies clean-room activation, reliable reporting and rights attestations as experimental in AdCP 3.2 and says they may change with six weeks’ notice. General language about campaigns does not identify an identity payload.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "A specification sets interface behavior; it does not demonstrate that any buyer used it.",
  "final_wording": "The AdCP issuer described clean-room activation as experimental in its October 22 account of the 3.2 release.",
  "counterevidence": "A specification sets interface behavior; it does not demonstrate that any buyer used it.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F03",
  "headline": false,
  "claim": "The September 11 AdCP Go publisher client builds a typed request from a user token and its namespace type and posts the request to its Trusted Match identity route.",
  "chapter": "abstract, 10, 12, 13",
  "source_ids": [
   "IDN-J-S03",
   "IDN-JV-S01",
   "IDN-JV-S02"
  ],
  "passage": "[IDN-J-S03, tmpclient/client.go, Activate, lines 126–133] {UserToken: params.UserToken, UIDType: params.UIDType}, [IDN-J-S03, same file, IdentityMatch, line 99] c.routerURL+\"/tmp/identity\"",
  "support": [
   {
    "source_id": "IDN-J-S03",
    "passage": "{UserToken: params.UserToken, UIDType: params.UIDType},",
    "locator": "tmpclient/client.go, Activate, lines 126–133"
   },
   {
    "source_id": "IDN-J-S03",
    "passage": "c.routerURL+\"/tmp/identity\"",
    "locator": "same file, IdentityMatch, line 99"
   }
  ],
  "scope_time": "Reference code commit a6c741b, 2026-09-11",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "At the September 11, 2026 commit, Activate constructs identities with UserToken and UIDType, carries consent, validates, and invokes IdentityMatch; the latter posts to the configured router at /tmp/identity. Activate joins the context and identity results locally. The same commit’s test file describes a local mock server with a typed test token and an expected eligible package. The commit record dates the source snapshot to 2026-09-11. The commit date is distinct from the date the verifier read the 3.2.8 documentation.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "The checked code is a published connector path; no live publisher, user identifiers or advertising spend are observed.",
  "final_wording": "The September 11 AdCP Go publisher client builds a typed request from a user token and its namespace type and posts the request to its Trusted Match identity route.",
  "counterevidence": "The checked code is a published connector path; no live publisher, user identifiers or advertising spend are observed.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F04",
  "headline": false,
  "claim": "The AdCP reference identity engine builds lookups for request identities and target audience IDs and submits them to the audience service’s membership check.",
  "chapter": "abstract, 10, 12, 13",
  "source_ids": [
   "IDN-J-S05",
   "IDN-JV-S01"
  ],
  "passage": "[IDN-J-S05, targeting/identity_engine.go, resolveUserSegments, lines 131–144] results, err := e.audience.IsMemberBatch(ctx, lookups) [IDN-J-S05, same block, lines 136–141; inspected with UserToken] AudienceID: seg,",
  "support": [
   {
    "source_id": "IDN-J-S05",
    "passage": "results, err := e.audience.IsMemberBatch(ctx, lookups)",
    "locator": "targeting/identity_engine.go, resolveUserSegments, lines 131–144"
   },
   {
    "source_id": "IDN-J-S05",
    "passage": "AudienceID: seg,",
    "locator": "same block, lines 136–141; inspected with UserToken"
   }
  ],
  "scope_time": "Reference code commit a6c741b, 2026-09-11",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "The pinned engine takes the Cartesian product of identities and target audience IDs and calls IsMemberBatch, then uses returned memberships to evaluate package eligibility. The function returns before any lookup when the audience service, identities or target segments are missing. This is source-code evidence of an implemented identity check. The commit record dates the source snapshot to 2026-09-11. The commit date is distinct from the date the verifier read the 3.2.8 documentation.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "The service must be configured with an audience backend, request identities and target segments. No independently measured match accuracy or commercial use follows.",
  "final_wording": "At the September 11, 2026 adcp-go commit, the reference identity engine submits request tokens and target audience IDs for a batch membership check when an audience service, identities and target segments are present.",
  "counterevidence": "The service must be configured with an audience backend, request identities and target segments. No independently measured match accuracy or commercial use follows.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F05",
  "headline": false,
  "claim": "The AdCP reference HTTP identity handler can pass a decoded request to its service for evaluation and constructs a response carrying eligible package IDs.",
  "chapter": "10, 13",
  "source_ids": [
   "IDN-J-S04",
   "IDN-JV-S01"
  ],
  "passage": "[IDN-J-S04, targeting/identityagent/handler.go, ServeHTTP, lines 223–229] result = h.service.Evaluate(ctx, serviceReq) [IDN-J-S04, same file, provider identity response, line 271] EligiblePackageIDs: eligible,",
  "support": [
   {
    "source_id": "IDN-J-S04",
    "passage": "result = h.service.Evaluate(ctx, serviceReq)",
    "locator": "targeting/identityagent/handler.go, ServeHTTP, lines 223–229"
   },
   {
    "source_id": "IDN-J-S04",
    "passage": "EligiblePackageIDs: eligible,",
    "locator": "same file, provider identity response, line 271"
   }
  ],
  "scope_time": "Reference code commit a6c741b, 2026-09-11",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The handler parses the HTTP request, validates it and sends the prepared request to Evaluate or EvaluateWithDecode, depending on canonicalizer configuration. On the normal path it filters eligible packages into EligiblePackageIDs. Terminal timeout or provider failure yields a typed error. The code does not establish a successful external exchange. The commit record dates the source snapshot to 2026-09-11. The commit date is distinct from the date the verifier read the 3.2.8 documentation. The executable error path takes precedence over a stale file-header comment on timeouts.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "A source-level reference implementation furnishes no two-party interoperability transcript or commercial transaction.",
  "final_wording": "The AdCP reference HTTP identity handler can pass a decoded request to its service for evaluation and constructs a response carrying eligible package IDs.",
  "counterevidence": "A source-level reference implementation furnishes no two-party interoperability transcript or commercial transaction.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F06",
  "headline": false,
  "claim": "The September 11 adcp-go code includes UID2 and EUID decoders that call the configured client to decrypt an incoming advertising token.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S06",
   "IDN-JV-S01"
  ],
  "passage": "[IDN-J-S06, targeting/tmpxdecoders/uid2.go, UID2.Decode and EUID.Decode, lines 25–55] uid2Lookup is the shared decrypt-and-map helper used by both UID2 and [IDN-J-S06, uid2Lookup, lines 73–85] raw, err := client.Decrypt(ctx, token)",
  "support": [
   {
    "source_id": "IDN-J-S06",
    "passage": "uid2Lookup is the shared decrypt-and-map helper used by both UID2 and",
    "locator": "targeting/tmpxdecoders/uid2.go, UID2.Decode and EUID.Decode, lines 25–55"
   },
   {
    "source_id": "IDN-J-S06",
    "passage": "raw, err := client.Decrypt(ctx, token)",
    "locator": "uid2Lookup, lines 73–85"
   }
  ],
  "scope_time": "Reference code commit a6c741b, 2026-09-11",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The pinned UID2 and EUID Decode methods both delegate to uid2Lookup, which checks for a configured client and calls Decrypt on the token. The implemented switch maps invalid, expired, missing-key, unsupported-version and scope-mismatch errors to a dropped entry. Other errors propagate. The file contains no evidence of a live operator transaction. The commit record dates the source snapshot to 2026-09-11. The commit date is distinct from the date the verifier read the 3.2.8 documentation. In the switch, five explicit error conditions drop entries. The file’s lead comment is insufficient evidence of operator opt-out processing.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "The path depends on a configured client and matching operator scope. The finding describes implementation, not a live UID2 or EUID transaction.",
  "final_wording": "The September 11 adcp-go code includes UID2 and EUID decoders that call the configured client to decrypt an incoming advertising token.",
  "counterevidence": "The path depends on a configured client and matching operator scope. The finding describes implementation, not a live UID2 or EUID transaction.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F07",
  "headline": false,
  "claim": "The IAB Tech Lab repository labels the AAMP 3.0 OpenProposal public-comment object model a draft.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S07"
  ],
  "passage": "Nothing here is a ratified IAB Tech Lab standard.",
  "support": [
   {
    "source_id": "IDN-J-S07",
    "passage": "Nothing here is a ratified IAB Tech Lab standard.",
    "locator": "README, draft warning; record checked at cutoff"
   }
  ],
  "scope_time": "v3.0-draft-1 and repository status read 2026-11-11",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The issuer’s repository README identifies v3.0-draft-1 as the published comment draft, lists September 22 through October 22, 2026 as the comment window and still describes the object model as unratified. The end date does not itself ratify the specification.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "The end of a comment window does not by itself establish ratification or market deployment.",
  "final_wording": "The IAB Tech Lab repository labels the AAMP 3.0 OpenProposal public-comment object model a draft.",
  "counterevidence": "The end of a comment window does not by itself establish ratification or market deployment.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F08",
  "headline": false,
  "claim": "In the OpenProposal draft, the seller supplies the expected match rate, while the buyer can populate segments and a suppression list.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S08"
  ],
  "passage": "`match_rate_expected` is the seller's stated expectation; `segments[]` and `suppression_list` are buyer-populated",
  "support": [
   {
    "source_id": "IDN-J-S08",
    "passage": "`match_rate_expected` is the seller's stated expectation; `segments[]` and `suppression_list` are buyer-populated",
    "locator": "OpenProposal v3.0-draft-1 §5.3, Audience reach, buyer_supplied row"
   }
  ],
  "scope_time": "OpenProposal v3.0-draft-1",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Section 5.3, Audience reach, puts match_rate_expected, segments[] and suppression_list in buyer_supplied. Its text attributes the expectation to the seller and the latter two fields to the buyer; it also includes segments_allowed and suppression_allowed. The expected rate is not a measurement.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "The expected rate is a proposal field. It is neither an observed rate nor the denominator of a measurement.",
  "final_wording": "In the OpenProposal draft, the seller supplies the expected match rate, while the buyer can populate segments and a suppression list.",
  "counterevidence": "The expected rate is a proposal field. It is neither an observed rate nor the denominator of a measurement.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F09",
  "headline": false,
  "claim": "The IAB OpenRTB Agentic Audiences community extension assigns integer type 1 to identity embeddings and allows a segment entry to carry multiple signal types.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S09"
  ],
  "passage": "Embedding type(s): 1 = identity, 2 = contextual, 3 = reinforcement. An entry may encode multiple signal types.",
  "support": [
   {
    "source_id": "IDN-J-S09",
    "passage": "Embedding type(s): 1 = identity, 2 = contextual, 3 = reinforcement. An entry may encode multiple signal types.",
    "locator": "Object: Data.segment.ext.aa, type row"
   }
  ],
  "scope_time": "Extension text read 2026-11-11",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The community extension’s type field supports multiple integer categories on a segment. Type 1 denotes identity, type 2 contextual information and type 3 reinforcement. The embedding is carried in segment.ext.aa, and model compatibility affects interpretation. The classification does not itself establish who processed it.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "A specification sets interface behavior; it does not demonstrate that any buyer used it.",
  "final_wording": "The IAB OpenRTB Agentic Audiences community extension assigns integer type 1 to identity embeddings and allows a segment entry to carry multiple signal types.",
  "counterevidence": "A specification sets interface behavior; it does not demonstrate that any buyer used it.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F10",
  "headline": false,
  "claim": "The Prebid Agentic Audiences RTD implementation copies an input entry’s type and vector into the outbound OpenRTB user-data segment, according to its merged code and module documentation.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S10",
   "IDN-J-S12",
   "IDN-J-S11"
  ],
  "passage": "[IDN-J-S10, PR #14626 diff, modules/agenticAudienceAdapter.js, mapEntryToOpenRtbSegment and getBidRequestData] type: entry.type [IDN-J-S12, Overview, second paragraph, segment.ext.aa] Embedding fields from each stored entry are placed under",
  "support": [
   {
    "source_id": "IDN-J-S10",
    "passage": "type: entry.type",
    "locator": "PR #14626 diff, modules/agenticAudienceAdapter.js, mapEntryToOpenRtbSegment and getBidRequestData"
   },
   {
    "source_id": "IDN-J-S12",
    "passage": "Embedding fields from each stored entry are placed under",
    "locator": "Overview, second paragraph, segment.ext.aa"
   }
  ],
  "scope_time": "PR #14626 merged 2026-04-14; integration reference read at cutoff",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "The merged module copies vector and type into ext.aa. When qualifying stored entries are present it merges the segment list into ortb2Fragments.global.user.data. The PR includes isolated tests using stubbed storage. The observed code boundary is construction of the shared auction fragment; actual buyer delivery and consumption need separate evidence.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "This code can carry type 1 when supplied. An OpenRTB auction can run without an agent, so this connector remains an adjacent H7 case unless an agent-mediated workflow is documented.",
  "final_wording": "Prebid’s merged Agentic Audiences module copies a stored entry’s type and vector into the global OpenRTB auction fragment under user.data[].segment[].ext.aa. The code and module guide establish this handoff within Prebid.",
  "counterevidence": "This code can carry type 1 when supplied. An OpenRTB auction can run without an agent, so this connector remains an adjacent H7 case unless an agent-mediated workflow is documented.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F11",
  "headline": false,
  "claim": "Prebid merged its Agentic Audiences RTD module into the project’s main development branch on April 14, 2026.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S11"
  ],
  "passage": "merged 12 commits into",
  "support": [
   {
    "source_id": "IDN-J-S11",
    "passage": "merged 12 commits into",
    "locator": "PR #14626, merge header and date"
   }
  ],
  "scope_time": "2026-04-14",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The GitHub merge header and event both identify April 14, 2026. Twelve commits merged into prebid:master under PR 14626. No release-tag date, installed module count or live auction follows from the merge.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "A merged change is not a deployment or verified exchange between independent actors.",
  "final_wording": "Prebid merged its Agentic Audiences RTD module into the project’s main development branch on April 14, 2026.",
  "counterevidence": "A merged change is not a deployment or verified exchange between independent actors.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F12",
  "headline": false,
  "claim": "IAB Tech Lab explicitly describes an ordinary programmatic use for Agentic Audiences that is separate from its agentic advertising use.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S16"
  ],
  "passage": "Agentic Audiences can add value in the existing programmatic ecosystem",
  "support": [
   {
    "source_id": "IDN-J-S16",
    "passage": "Agentic Audiences can add value in the existing programmatic ecosystem",
    "locator": "Operationalizing Agentic Audiences, OpenRTB extension discussion"
   }
  ],
  "scope_time": "Published 2026-08-04, revised 2026-08-08 and read 2026-11-11.",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The issuer’s August 4, 2026 article separates early agentic use from the existing programmatic ecosystem. Its section on OpenRTB and Prebid describes how the extension supports that distinct use. This is a stated use case without a transaction record.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "The scope distinction matters for H7; do not assume every use of the Prebid module was an agent-mediated buy.",
  "final_wording": "IAB Tech Lab explicitly describes an ordinary programmatic use for Agentic Audiences that is separate from its agentic advertising use.",
  "counterevidence": "The scope distinction matters for H7; do not assume every use of the Prebid module was an agent-mediated buy.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F13",
  "headline": false,
  "claim": "IAB Tech Lab lists the August 2026 Agentic Audiences release as v1.1 and the AAMP September 2026 umbrella release as v3.0.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S17"
  ],
  "passage": "[IDN-J-S17, Major Agentic and LLM Initiatives, Agentic Audiences row] August 2026  | v1.1 [IDN-J-S17, same table, AAMP row] September 22, 2026  | v3.0",
  "support": [
   {
    "source_id": "IDN-J-S17",
    "passage": "August 2026  | v1.1",
    "locator": "Major Agentic and LLM Initiatives, Agentic Audiences row"
   },
   {
    "source_id": "IDN-J-S17",
    "passage": "September 22, 2026  | v3.0",
    "locator": "same table, AAMP row"
   }
  ],
  "scope_time": "Issuer listing revised 2026-09-23 and read 2026-11-11. Release dates are those in the individual rows.",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The IAB initiative table lists Agentic Audiences, formerly UCP, v1.1 for August 2026 and the separate AAMP initiative v3.0 on September 22, 2026. The version applies to each named initiative, not to every adapter, extension or underlying specification.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "Separate workstreams and version lines. A shared governance body does not make every OpenRTB connector an AAMP transaction.",
  "final_wording": "IAB Tech Lab lists the August 2026 Agentic Audiences release as v1.1 and the AAMP September 2026 umbrella release as v3.0.",
  "counterevidence": "Separate workstreams and version lines. A shared governance body does not make every OpenRTB connector an AAMP transaction.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F14",
  "headline": false,
  "claim": "PubMatic reported an AdCP-enabled CTV campaign for Clubtails on its Activate platform in December 2025.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S13"
  ],
  "passage": "The campaign is running through PubMatic’s Activate platform",
  "support": [
   {
    "source_id": "IDN-J-S13",
    "passage": "The campaign is running through PubMatic’s Activate platform",
    "locator": "Campaign announcement, paragraph describing the Activate platform"
   }
  ],
  "scope_time": "2025-12-15 participant report",
  "scope_geo": "US campaign context",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "PubMatic’s December 15, 2025 release identifies Clubtails, agency Butler/Till and a CTV campaign on Activate. It describes AdCP and a Claude brief, geo targeting and age-appropriate controls. It gives no named identity token, buyer/seller payload or identity-linked transaction trace.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "The announcement names an advertiser, agency and campaign but does not establish which audience identity field, if any, crossed the protocol boundary.",
  "final_wording": "PubMatic reported an AdCP-enabled CTV campaign for Clubtails on its Activate platform in December 2025.",
  "counterevidence": "The announcement names an advertiser, agency and campaign but does not establish which audience identity field, if any, crossed the protocol boundary.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F15",
  "headline": false,
  "claim": "Optable said its March 2026 PubMatic integration gave buyers access to publisher first-party audience planning without transferring the underlying data.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S14"
  ],
  "passage": "without exposing or transferring underlying data.",
  "support": [
   {
    "source_id": "IDN-J-S14",
    "passage": "without exposing or transferring underlying data.",
    "locator": "Partnership announcement, paragraph describing the integration"
   }
  ],
  "scope_time": "2026-03-12 participant report",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Optable’s March 12, 2026 release describes Audience Agent integrated into PubMatic AgenticOS. It claims access to publisher first-party planning without disclosure or transfer of underlying data. It does not show an identity-bearing request, a buyer receipt or a completed identity-specific purchase.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted implementation or product description.",
  "limitations": "This is seller-described functionality. The examined release provides neither an inspectable identity-bearing message nor a completed identity-specific purchase receipt.",
  "final_wording": "Optable said its March 2026 PubMatic integration gave buyers access to publisher first-party audience planning without transferring the underlying data.",
  "counterevidence": "This is seller-described functionality. The examined release provides neither an inspectable identity-bearing message nor a completed identity-specific purchase receipt.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-J-F16",
  "headline": false,
  "claim": "IAB Tech Lab describes an AAMP reference-SDK demonstration in which a buyer and seller negotiate and push the confirmed transaction to Google Ad Manager.",
  "chapter": "10",
  "source_ids": [
   "IDN-J-S15"
  ],
  "passage": "confirm the transaction and push it to Google Ad Manager (GAM).",
  "support": [
   {
    "source_id": "IDN-J-S15",
    "passage": "confirm the transaction and push it to Google Ad Manager (GAM).",
    "locator": "Watch the Buyer and Seller Agents in action!"
   }
  ],
  "scope_time": "AAMP overview revised 2026-10-27 and read 2026-11-11. Demonstration date unspecified.",
  "scope_geo": "Cross-market interface",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "IAB’s AAMP page, last updated October 27, 2026, describes a reference-SDK demonstration of planning, buyer/seller negotiation, confirmation and sending the transaction to Google Ad Manager. It names OpenDirect, AdCOM and taxonomies. The text does not identify an actual media purchase or exchanged person/household identity field.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named publisher supplies the quoted record for this scoped statement.",
  "limitations": "An issuer demo does not establish a production transaction, its identity semantics, or a public message trace tying a person or household ID to the campaign.",
  "final_wording": "IAB Tech Lab describes an AAMP reference-SDK demonstration in which a buyer and seller negotiate and push the confirmed transaction to Google Ad Manager.",
  "counterevidence": "An issuer demo does not establish a production transaction, its identity semantics, or a public message trace tying a person or household ID to the campaign.",
  "stream": "J",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H7"
 },
 {
  "id": "IDN-U-F01",
  "headline": false,
  "claim": "LiveRamp describes RampID as the label for a record in its identity graph.",
  "chapter": "1",
  "source_ids": [
   "IDN-C-S03",
   "IDN-U-S02"
  ],
  "passage": "[IDN-C-S03, About RampIDs, rendered line 21 (locate by quoted text)] tied to a record in the LiveRamp identity graph [IDN-U-S02, RampID Methodology, rendered line 14 (locate by quoted text)] connected U.S.-based devices",
  "support": [
   {
    "source_id": "IDN-C-S03",
    "passage": "tied to a record in the LiveRamp identity graph",
    "locator": "About RampIDs, rendered line 21 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S02",
    "passage": "connected U.S.-based devices",
    "locator": "RampID Methodology, rendered line 14 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2025-08-20; read 2026-11-11",
  "scope_geo": "A US identity-graph scope is documented; the exact interoperable route still needs a US partner check.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "LiveRamp's API distinguishes individual and household RampIDs, client encodings, and maintained versus derived matches. A returned derived ID persists for equal input even without a graph match. An ID returned is not a validated identity. LiveRamp describes deterministic offline PII merging, online device linking and joining the two, including US-based devices. Correctness and completeness are vendor goals. Its graph is a technology/data asset rather than a second name for every use of RampID. A blanket reading that all returned IDs label records already in the graph fails on the documented derived-ID exception.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Keep RampID as the interoperability lead; treat ATS as an implementation route unless a separate purchased deliverable can be shown.",
  "final_wording": "LiveRamp describes RampIDs as pseudonymous identifiers. Its API can return a maintained RampID for an identity graph match or a derived RampID when it finds no match.",
  "counterevidence": "Boundary or alternative interpretation: Keep RampID as the interoperability lead; treat ATS as an implementation route unless a separate purchased deliverable can be shown.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F02",
  "headline": false,
  "claim": "UID2 documentation identifies The Trade Desk as a public operator and lists a production endpoint in Ohio.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S03",
   "IDN-U-S04"
  ],
  "passage": "[IDN-U-S03, The UID2 Operator, rendered line 92 (locate by quoted text)] The Trade Desk currently serves as a Public Operator [IDN-U-S04, Environments, rendered line 75 (locate by quoted text)] Production | AWS US East (Ohio)",
  "support": [
   {
    "source_id": "IDN-U-S03",
    "passage": "The Trade Desk currently serves as a Public Operator",
    "locator": "The UID2 Operator, rendered line 92 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S04",
    "passage": "Production | AWS US East (Ohio)",
    "locator": "Environments, rendered line 75 (locate by quoted text)"
   }
  ],
  "scope_time": "Documentation footer last updated November 11, 2026; read November 11, 2026.",
  "scope_geo": "US production endpoint documented; an endpoint identifies hosting rather than geographic reach.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "UID2 documentation distinguishes public and privately operated instances. The Trade Desk operates a public instance. The operator hashes input, encrypts identifiers and manages keys; it is not the only possible operator. The production endpoint table includes Ohio and Oregon as well as Asia Pacific and global routing. Ohio also hosts the separate testing endpoint. Hosting geography identifies an available service route and does not give an audience count.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Profile the operator role; keep private operators, governance and publisher integration separate.",
  "final_wording": "UID2 documentation identifies The Trade Desk as a public operator and lists a production endpoint in Ohio.",
  "counterevidence": "Boundary or alternative interpretation: Profile the operator role; keep private operators, governance and publisher integration separate.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F03",
  "headline": false,
  "claim": "EUID publishes a coverage list that includes EU member states and the United Kingdom.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S05"
  ],
  "passage": "[IDN-U-S05, EUID areas of coverage, rendered line 68 (locate by quoted text)] EUID is supported for use in the following European Union countries [IDN-U-S05, EUID areas of coverage, rendered line 118 (locate by quoted text)] United Kingdom",
  "support": [
   {
    "source_id": "IDN-U-S05",
    "passage": "EUID is supported for use in the following European Union countries",
    "locator": "EUID areas of coverage, rendered line 68 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S05",
    "passage": "United Kingdom",
    "locator": "EUID areas of coverage, rendered line 118 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2024-07-18; read 2026-11-11",
  "scope_geo": "EU/EEA and named additional territories; United Kingdom explicitly listed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "EUID's published list includes EU and other EEA countries, Switzerland, the UK and specified territories. It omits the US. The list states its coverage information as of July 18, 2024 and shows a November 2, 2026 page update. The coverage list is geographically scoped; the site update date is distinct from the date the coverage list states. No US eligibility is established.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "The US does not appear on the opened coverage list. Keep as a territorial comparator pending a separately evidenced US offer.",
  "final_wording": "EUID publishes a coverage list that includes EU member states and the United Kingdom.",
  "counterevidence": "Boundary or alternative interpretation: The US does not appear on the opened coverage list. Keep as a territorial comparator pending a separately evidenced US offer.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F04",
  "headline": false,
  "claim": "ID5 describes a publisher-issued common ID and reports a substantial US client base.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S06",
   "IDN-D-S09",
   "IDN-ID5-S07"
  ],
  "passage": "[IDN-U-S06, Publisher, rendered line 90 (locate by quoted text)] generate and distribute a common first-party identifier [IDN-D-S09, ID5 Acquires TrueData - ID5, rendered line 25 (locate by quoted text)] strong foothold in the US",
  "support": [
   {
    "source_id": "IDN-U-S06",
    "passage": "generate and distribute a common first-party identifier",
    "locator": "Publisher, rendered line 90 (locate by quoted text)"
   },
   {
    "source_id": "IDN-D-S09",
    "passage": "strong foothold in the US",
    "locator": "ID5 Acquires TrueData - ID5, rendered line 25 (locate by quoted text)"
   }
  ],
  "scope_time": "Acquisition announced October 30, 2025; publisher requirements page displays February 1, 2026; read November 11, 2026.",
  "scope_geo": "The ID5 ID Service specifies publisher requirements for traffic originating in the United States. ID5 also reports a US client base across the business.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "ID5 publisher instructions distinguish the shared encrypted ID from the optional ID5 Identity Graph. Publishers can pass the ID in bid requests through supported integrations, with authorized partners able to decrypt subject to consent. ID5's October 30, 2025 release reports acquiring the US graph provider TrueData and describes an existing US business. A unified offering was put in future tense. The acquired graph and publisher ID have distinct functions. Partner agreement implementation requirements, section 2 explicitly applies the ID5 ID Service to US-originating traffic. It does not identify a particular publisher deployment. Publisher generation through ID5 is an integration role. It does not make each publisher the issuer of a new namespace or attribute company-wide US clients to a particular integration.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "The issuer terms cover the US publisher side of the ID5 ID. Verify a named receiving deployment separately. The acquired TrueData graph is not an alias of the ID.",
  "final_wording": "ID5 says publishers can generate and distribute its common first-party identifier. Its publisher requirements cover US-originating traffic. Its 2025 acquisition release describes a US client base for ID5 as a business.",
  "counterevidence": "The issuer terms cover the US publisher side of the ID5 ID. Verify a named receiving deployment separately. The acquired TrueData graph is not an alias of the ID.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F05",
  "headline": false,
  "claim": "Yahoo documents a server-to-server ConnectID lookup using a hashed email and a publisher ID, and the joint issuer release describes a US user base.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S23",
   "IDN-U-S09",
   "IDN-UV-S07"
  ],
  "passage": "[IDN-C-S23, Integrate with ConnectID: Server-to-Server Method, rendered line 161 (locate by quoted text)] hashed user email and the Publisher ID [IDN-C-S23, Integrate with ConnectID: Server-to-Server Method, rendered line 161 (locate by quoted text)] containing the ConnectID [IDN-U-S09, LiveRamp and Yahoo Partner to Scale Addressability Across the Ad Ecosystem, rendered line 31 (locate by quoted text)] authenticated users in the U.S.",
  "support": [
   {
    "source_id": "IDN-C-S23",
    "passage": "hashed user email and the Publisher ID",
    "locator": "Integrate with ConnectID: Server-to-Server Method, rendered line 161 (locate by quoted text)"
   },
   {
    "source_id": "IDN-C-S23",
    "passage": "containing the ConnectID",
    "locator": "Integrate with ConnectID: Server-to-Server Method, rendered line 161 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S09",
    "passage": "authenticated users in the U.S.",
    "locator": "LiveRamp and Yahoo Partner to Scale Addressability Across the Ad Ecosystem, rendered line 31 (locate by quoted text)"
   }
  ],
  "scope_time": "Joint release October 16, 2023; technical documentation read November 11, 2026.",
  "scope_geo": "The 2023 joint release describes US authenticated consumer relationships behind Yahoo ConnectID. It does not measure current reachable users.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Yahoo describes server-to-server ConnectID generation using credentials, a required hashed email and publisher ID, with an optional device signal, opt-out returning an empty response, and OpenRTB 2.5/2.6 transmission through different EID paths. A joint Yahoo/LiveRamp announcement in 2023 says ATS publishers can integrate ConnectID and cites Yahoo's own estimate of nearly 200 million authenticated US users across its relationships. A joint announcement is not an independent performance check. Issuer-distributed PDF dates the original joint communication. Same evidence origin as IDN-U-S09; no additional reach corroboration. The historical joint release dates the scope. The same communication was reopened from LiveRamp’s PDF after Yahoo’s direct version was blocked.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Retain Yahoo ConnectID. Validate a named publisher/recipient before treating the route as production evidence for scoring.",
  "final_wording": "Yahoo documents a server-to-server ConnectID lookup using a hashed email and publisher ID. In an October 16, 2023 joint release, Yahoo and LiveRamp attributed ConnectID’s US base to Yahoo’s authenticated consumer relationships.",
  "counterevidence": "Boundary or alternative interpretation: Retain Yahoo ConnectID. Validate a named publisher/recipient before treating the route as production evidence for scoring.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F06",
  "headline": false,
  "claim": "Lotame’s SSP instructions describe an unencrypted Panorama ID in the EID array.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S10"
  ],
  "passage": "64 character unencrypted Panorama ID in the EID array",
  "support": [
   {
    "source_id": "IDN-U-S10",
    "passage": "64 character unencrypted Panorama ID in the EID array",
    "locator": "Instructions for SSPs Adopting the Panorama ID in the Bidstream - Lotame Panorama ID—Prebid, Google ESP & Amazon CxM - Lotame Knowledge Base, rendered line 31 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US offer not established by the quoted integration record.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Lotame instructs SSPs to receive a 64-character unencrypted Panorama ID in Prebid EIDs, with no translation or envelope required. The page gives neither a US audience count nor a corporate ownership record. The former-employer flag applies to this row; its own integration manual cannot establish independent performance.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Retain the Lotame interest flag. Check production, consent chain, geography and current ownership separately.",
  "final_wording": "Lotame’s SSP instructions describe an unencrypted Panorama ID in the EID array.",
  "counterevidence": "Boundary or alternative interpretation: Retain the Lotame interest flag. Check production, consent chain, geography and current ownership separately.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F07",
  "headline": false,
  "claim": "Prebid names a Criteo ID for Exchanges module and describes its use by bidders.",
  "chapter": "",
  "source_ids": [
   "IDN-A-S17"
  ],
  "passage": "[IDN-A-S17, Criteo ID for Exchanges for Header Bidding, rendered line 117 (locate by quoted text)] provided that bidders use it in their adapters [IDN-A-S17, Criteo ID for Exchanges for Header Bidding, rendered line 108 (locate by quoted text)] Criteo ID for Exchanges module",
  "support": [
   {
    "source_id": "IDN-A-S17",
    "passage": "provided that bidders use it in their adapters",
    "locator": "Criteo ID for Exchanges for Header Bidding, rendered line 117 (locate by quoted text)"
   },
   {
    "source_id": "IDN-A-S17",
    "passage": "Criteo ID for Exchanges module",
    "locator": "Criteo ID for Exchanges for Header Bidding, rendered line 108 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US commercial eligibility unresolved.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Prebid lists Criteo ID for Exchanges as a module for publisher exchange inventory and Criteo-specific demand. The Direct Bidder is another route to Criteo demand. Integration instructions alone do not prove US use or cross-exchange recognition. The conditional instruction refers to what bidders can implement. It is not observed adapter use, an equivalence with OneTag, or evidence that unrelated demand receives the ID.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Prebid documents Criteo ID for Exchanges as a route to Criteo demand. OneTag was the provisional seed label. Neither an alias nor independent downstream use is established.",
  "final_wording": "Prebid documents a Criteo ID for Exchanges module that bidders can use in their adapters to access Criteo demand on exchange inventory.",
  "counterevidence": "Prebid documents Criteo ID for Exchanges as a route to Criteo demand. OneTag was the provisional seed label. Neither an alias nor independent downstream use is established.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F08",
  "headline": false,
  "claim": "Amazon describes Signal IQ as a publisher measurement tool for bidstream signals.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S12"
  ],
  "passage": "a measurement tool empowering web publishers to analyze the individual impact of their bidstream signals",
  "support": [
   {
    "source_id": "IDN-U-S12",
    "passage": "a measurement tool empowering web publishers to analyze the individual impact of their bidstream signals",
    "locator": "Signal IQ - Amazon Publisher Services, rendered line 25 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "Amazon cites US publisher data for its measurement tool; proprietary interoperable ID unconfirmed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Amazon's Signal IQ is a web publisher measurement tool. It compares bidstream signals through A/B tests. Dated US APS/TAM sample figures have distinct cohorts; third-party IDs measured are not a proprietary Amazon identifier. A measurement product cannot substantiate the name or existence of the seed’s hypothesized Amazon-issued ID.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Searches for an APS-issued publisher ID returned Signal IQ and marketplace integration materials. These documents justify neither a new proprietary ID nor scoring Amazon as its issuer.",
  "final_wording": "Amazon describes Signal IQ as a publisher measurement tool for bidstream signals.",
  "counterevidence": "Boundary or alternative interpretation: Searches for an APS-issued publisher ID returned Signal IQ and marketplace integration materials. These documents justify neither a new proprietary ID nor scoring Amazon as its issuer.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F09",
  "headline": false,
  "claim": "Prebid says SharedID sets a user ID cookie on the publisher domain.",
  "chapter": "11",
  "source_ids": [
   "IDN-U-S13"
  ],
  "passage": "sets a user id cookie in the publisher’s domain",
  "support": [
   {
    "source_id": "IDN-U-S13",
    "passage": "sets a user id cookie in the publisher’s domain",
    "locator": "SharedID for Header Bidding, rendered line 133 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US eligibility unconfirmed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Prebid owns SharedID, a random first-party identifier set on the publisher domain. The guide compares configurations and Safari cookie lifetimes, including server-side persistence. First-party scope matters for interpretation of sharing. A publisher first-party identifier can be exposed in requests without identifying one person across publishers.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Check cross-party consumption, first-party scope and treatment of former PubCommon ID before matrix admission.",
  "final_wording": "Prebid says SharedID sets a user ID cookie on the publisher domain.",
  "counterevidence": "Boundary or alternative interpretation: Check cross-party consumption, first-party scope and treatment of former PubCommon ID before matrix admission.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-U-F10",
  "headline": false,
  "claim": "Utiq’s coverage announcement names Germany, Austria, France, Spain, the UK and Italy.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S14"
  ],
  "passage": "across Germany, Austria, France, Spain, the UK and Italy",
  "support": [
   {
    "source_id": "IDN-U-S14",
    "passage": "across Germany, Austria, France, Spain, the UK and Italy",
    "locator": "70 million users: Advertising. Reconnected. - Utiq, rendered line 22 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2025-11-15; read 2026-11-11",
  "scope_geo": "Named European markets; US eligibility unconfirmed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Utiq reports deployment in Germany, Austria, France, Spain, UK and Italy and a marketing figure described as both users and consentpasses. Its telco-supported consented signal is distinct from a deduplicated US audience.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "The published markets are territory evidence. The screened Utiq records do not establish a US service.",
  "final_wording": "Utiq’s coverage announcement names Germany, Austria, France, Spain, the UK and Italy.",
  "counterevidence": "Boundary or alternative interpretation: The published markets are territory evidence. The screened Utiq records do not establish a US service.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F11",
  "headline": false,
  "claim": "Prebid describes Parrable’s identifier as working across browsers and webviews on one device.",
  "chapter": "2",
  "source_ids": [
   "IDN-A-S16"
  ],
  "passage": "across different browsers and webviews on a single device",
  "support": [
   {
    "source_id": "IDN-A-S16",
    "passage": "across different browsers and webviews on a single device",
    "locator": "Parrable ID, module description, current HTML line 109"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US eligibility unconfirmed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Prebid documents a Parrable full-device identifier spanning browsers/webviews on the same device; timed encryption changes the visible ID, integration uses partner client IDs. No user-level cross-device or US coverage follows. Current Prebid HTML states this under the Parrable ID module description; browser and webview scope is one device.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Preserve the device unit. Verify availability and independent recipient use before scoring.",
  "final_wording": "Prebid describes Parrable’s identifier as working across browsers and webviews on one device.",
  "counterevidence": "Boundary or alternative interpretation: Preserve the device unit. Verify availability and independent recipient use before scoring.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F12",
  "headline": false,
  "claim": "LiveRamp documents a known-identity service that maps consumer PII into AbiliTec Links or Known IDs.",
  "chapter": "1",
  "source_ids": [
   "IDN-U-S16"
  ],
  "passage": "into AbiliTec Links or Known IDs",
  "support": [
   {
    "source_id": "IDN-U-S16",
    "passage": "into AbiliTec Links or Known IDs",
    "locator": "Known Identity Resolution, rendered line 10 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2026-03-19; read 2026-11-11",
  "scope_geo": "US availability of this exact delivery route needs confirmation.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "LiveRamp known resolution returns AbiliTec Links via API or LiveRamp Known IDs in cloud environments. The product family groups distinct outputs. RampID circulation is a different task. The two choices have named route-specific outputs. The singular wording could attribute both output types to one interface.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Known Identity Resolution is the service family. Attribute AbiliTec Links to the API and Known IDs to the cloud route. Confirm the exact purchased output before any score.",
  "final_wording": "LiveRamp documents two known-identity resolution routes. Its API takes consumer PII and returns AbiliTec Links. Its cloud service takes PII or email addresses and returns Known IDs.",
  "counterevidence": "Known Identity Resolution is the service family. Attribute AbiliTec Links to the API and Known IDs to the cloud route. Confirm the exact purchased output before any score.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-U-F13",
  "headline": false,
  "claim": "Experian offers household- or individual-level linking in Digital Graph and labels a US edition.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S17"
  ],
  "passage": "[IDN-U-S17, Digital Graph, rendered line 93 (locate by quoted text)] connect identifiers at the household or individual level [IDN-U-S17, Digital Graph, rendered line 49 (locate by quoted text)] U.S. Digital Graph",
  "support": [
   {
    "source_id": "IDN-U-S17",
    "passage": "connect identifiers at the household or individual level",
    "locator": "Digital Graph, rendered line 93 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S17",
    "passage": "U.S. Digital Graph",
    "locator": "Digital Graph, rendered line 49 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US Digital Graph is explicitly labeled.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Experian explicitly names its US Digital Graph and offers licensed data or matching against customer files. Its machine learning links MAIDs, CTV IDs, universal IDs and hashed emails at household/individual level. Counts are Experian's marketing claims. Licensing the full Digital Graph and having first-party records appended are separate purchase modes; the named US edition is documented.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Use Digital Graph as the confirmed product lead for the Experian profile. Check how it differs from offline identity and enrichment.",
  "final_wording": "Experian offers household- or individual-level linking in Digital Graph and labels a US edition.",
  "counterevidence": "Boundary or alternative interpretation: Use Digital Graph as the confirmed product lead for the Experian profile. Check how it differs from offline identity and enrichment.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-U-F14",
  "headline": false,
  "claim": "TransUnion describes TruAudience marketing identity as deduplicating records to an individual or household.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S18"
  ],
  "passage": "Unify and deduplicate customer identities across channels and partners to a single individual or household",
  "support": [
   {
    "source_id": "IDN-U-S18",
    "passage": "Unify and deduplicate customer identities across channels and partners to a single individual or household",
    "locator": "Marketing Identity, rendered line 136 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "Omnichannel marketing identity documented; verify current US buying and receiving path.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "TruAudience's TransUnion product page offers cross-channel person and household deduplication and enrichment. US-site navigation is context, not a count or proof any partner can buy each component.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Keep the omnichannel resolution service here and test whether its TV route can qualify as a second purchase.",
  "final_wording": "TransUnion describes TruAudience marketing identity as deduplicating records to an individual or household.",
  "counterevidence": "Boundary or alternative interpretation: Keep the omnichannel resolution service here and test whether its TV route can qualify as a second purchase.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-U-F15",
  "headline": false,
  "claim": "Epsilon’s US processing description identifies a United States identity-resolution location for its Core ID Services.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S19",
   "IDN-U-S20"
  ],
  "passage": "[IDN-U-S19, Epsilon Legal, rendered line 23 (locate by quoted text)] United States of America [identity resolution] [IDN-U-S20, Identity Resolution, rendered line 104 (locate by quoted text)] U.S. consumers",
  "support": [
   {
    "source_id": "IDN-U-S19",
    "passage": "United States of America [identity resolution]",
    "locator": "Epsilon Legal, rendered line 23 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S20",
    "passage": "U.S. consumers",
    "locator": "Identity Resolution, rendered line 104 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US identity-resolution processing location expressly documented; US consumer scope described by Epsilon.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Epsilon's description of processing specifies US identity resolution versus local pseudonymization and profile/RTB hosting, with conditions for US and non-US subjects. It distinguishes persistent consumer links from client-scoped first-party cookies. Epsilon markets its COREid services to recognize and reach over 200 million US consumers. This is seller-reported scale, without validation or a comparable accuracy denominator. Epsilon distinguishes the location of processing, client-specific first-party cookies and US consumer reach. None supplies a measured accuracy rate.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Record the legal description as a product-processing representation only. Independently test accuracy and distinguish processing location from geographic coverage.",
  "final_wording": "Epsilon’s US processing description identifies a United States identity-resolution location for its Core ID Services.",
  "counterevidence": "Boundary or alternative interpretation: Record the legal description as a product-processing representation only. Independently test accuracy and distinguish processing location from geographic coverage.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-U-F16",
  "headline": false,
  "claim": "Acxiom describes Real ID in the cloud as a brand-cloud identity-resolution application.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S21",
   "IDN-U-S22"
  ],
  "passage": "[IDN-U-S21, IPG unveils cloud-based identity resolution platform, rendered line 173 (locate by quoted text)] designed to seamlessly integrate with a brand’s secure cloud ecosystem [IDN-U-S22, Acxiom launches digital recognition, connecting online and offline identity for true omnichannel personalization - Omnicom, rendered line 7 (locate by quoted text)] Digital Recognition solution, powered by Real ID",
  "support": [
   {
    "source_id": "IDN-U-S21",
    "passage": "designed to seamlessly integrate with a brand’s secure cloud ecosystem",
    "locator": "IPG unveils cloud-based identity resolution platform, rendered line 173 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S22",
    "passage": "Digital Recognition solution, powered by Real ID",
    "locator": "Acxiom launches digital recognition, connecting online and offline identity for true omnichannel personalization - Omnicom, rendered line 7 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2023-10-17, 2026-07-14; read 2026-11-11",
  "scope_geo": "A US retailer is named for Digital Recognition powered by Real ID; a standalone US sale of the cloud app is unconfirmed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "An Acxiom release dated October 17, 2023 names Real ID as an Acxiom-built identity resolution app launched by IPG within a client's cloud. Historical issuer naming is not proof of 2026 ultimate ownership. A July 14, 2026 release hosted by Omnicom describes an expanded Acxiom Digital Recognition offering powered by Real ID and a US early adopter, Guitar Center. A powered-by relationship is not product identity; reported uplift is promotional. The 2026 US Guitar Center deployment belongs to powered-by Digital Recognition. It is not proof of a standalone purchase of Real ID in the cloud.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Reconcile Real ID and Digital Recognition, which Omnicom describes as powered by Real ID. Do not duplicate the underlying product.",
  "final_wording": "Acxiom describes Real ID in the cloud as a brand-cloud identity-resolution application.",
  "counterevidence": "Boundary or alternative interpretation: Reconcile Real ID and Digital Recognition, which Omnicom describes as powered by Real ID. Do not duplicate the underlying product.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F17",
  "headline": false,
  "claim": "Merkle positioned Merkury at launch as a way to build private identity graphs for brands and publishers.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S23"
  ],
  "passage": "creation of first-party, “private identity graphs” for both brands and publishers",
  "support": [
   {
    "source_id": "IDN-U-S23",
    "passage": "creation of first-party, “private identity graphs” for both brands and publishers",
    "locator": "dentsu, rendered line 11 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2020-02-11; read 2026-11-11",
  "scope_geo": "Historical United States launch record.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Merkle dated its launch of the Merkury identity resolution and data platform to February 11, 2020. It said brands/publishers can build private first-party graphs and cited Cadillac. That launch does not settle present availability. A US page and dated launch describe a prior offer. A named customer and the publisher’s dateline do not by themselves date 2026 contracting rights.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "The 2020 launch documents the historical offer; confirm a current US contract path and graph lineage.",
  "final_wording": "Merkle positioned Merkury at launch as a way to build private identity graphs for brands and publishers.",
  "counterevidence": "Boundary or alternative interpretation: The 2020 launch documents the historical offer; confirm a current US contract path and graph lineage.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F18",
  "headline": false,
  "claim": "Zeta describes each Zeta ID as a cluster linked to the same individual.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S24"
  ],
  "passage": "a cluster of linked identifiers associated with the same individual",
  "support": [
   {
    "source_id": "IDN-U-S24",
    "passage": "a cluster of linked identifiers associated with the same individual",
    "locator": "Data and Identity Resolution - Zeta Global, rendered line 28 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US eligibility unconfirmed from product page.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Zeta describes Zeta ID as persistent person-level resolution within Zeta Data Cloud. Its product description does not establish a separately marketed bidstream ID or a retirement of the named service.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "The search for Zeta retirement produced active product documentation; it did not identify a distinct retired service or show uninterrupted operation of prior versions.",
  "final_wording": "Zeta describes each Zeta ID as a cluster linked to the same individual.",
  "counterevidence": "Boundary or alternative interpretation: The search for Zeta retirement produced active product documentation; it did not identify a distinct retired service or show uninterrupted operation of prior versions.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F19",
  "headline": false,
  "claim": "Permutive documents cohort activation with publishers on its platform.",
  "chapter": "1, 12",
  "source_ids": [
   "IDN-U-S25",
   "IDN-U-S26",
   "IDN-UV-S02",
   "IDN-UV-S03"
  ],
  "passage": "[IDN-U-S25, Activation Guide for Advertisers – Advertiser Support, rendered line 23 (locate by quoted text)] activating a cohort with Publishers through the Permutive platform [IDN-U-S26, Explainer: What Are Publisher Cohorts? - Permutive, rendered line 93 (locate by quoted text)] First-party data can be made targetable as a cohort [IDN-UV-S02, Activating audiences in Ad Manager, paras. 1–2, cohort key-values in requests; Exhaustive signal coverage, first paragraph, explicitly US inventory.] an average of 1.24 audience categories per impression [IDN-UV-S03, Dated November 3, 2022, opening three paragraphs; US and international marketers, third-party cookies and device IDs.] Activation is easily enabled through OpenX Deal IDs",
  "support": [
   {
    "source_id": "IDN-U-S25",
    "passage": "activating a cohort with Publishers through the Permutive platform",
    "locator": "Activation Guide for Advertisers – Advertiser Support, rendered line 23 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S26",
    "passage": "First-party data can be made targetable as a cohort",
    "locator": "Explainer: What Are Publisher Cohorts? - Permutive, rendered line 93 (locate by quoted text)"
   },
   {
    "source_id": "IDN-UV-S02",
    "passage": "an average of 1.24 audience categories per impression",
    "locator": "Activating audiences in Ad Manager, paras. 1–2, cohort key-values in requests; Exhaustive signal coverage, first paragraph, explicitly US inventory."
   },
   {
    "source_id": "IDN-UV-S03",
    "passage": "Activation is easily enabled through OpenX Deal IDs",
    "locator": "Dated November 3, 2022, opening three paragraphs; US and international marketers, third-party cookies and device IDs."
   }
  ],
  "scope_time": "OpenX announcement November 3, 2022; advertiser guide January 13, 2023; undated Google partner case read November 11, 2026.",
  "scope_geo": "Google reports a measure for TelevisaUnivision’s US inventory. OpenX separately announced a buying route for US marketers in 2022.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The Permutive guide gives the steps for selecting a connected publisher, creating a cohort and setting up its deal. Google reports that TelevisaUnivision sent Permutive cohorts to Ad Manager. Its US measure is the mean number of audience categories per impression. OpenX separately announced a US buying route for Permutive audiences without third-party cookies or device IDs.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Google counted audience categories per impression on TelevisaUnivision’s US inventory. The case gives no country-by-country scope for the whole test, market coverage or current buying terms. OpenX described its own Deal ID route.",
  "final_wording": "Permutive documents activating publisher cohorts through deals. Google says TelevisaUnivision sent Permutive’s standard cohorts in Ad Manager requests. It reports a mean of 1.24 audience categories per impression on the publisher’s US inventory. OpenX separately announced a US buying route for Permutive audiences without third-party cookies or device IDs.",
  "counterevidence": "Google counted audience categories per impression on TelevisaUnivision’s US inventory. The case gives no country-by-country scope for the whole test, market coverage or current buying terms. OpenX described its own Deal ID route.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F20",
  "headline": false,
  "claim": "Audigent describes a cookieless media-curation route using TransUnion audiences.",
  "chapter": "1",
  "source_ids": [
   "IDN-U-S27",
   "IDN-UV-S05",
   "IDN-UV-S06",
   "IDN-A-S06"
  ],
  "passage": "cookieless media and data curation",
  "support": [
   {
    "source_id": "IDN-U-S27",
    "passage": "cookieless media and data curation",
    "locator": "Over 300 SmartPMPs Powered by Syndicated TransUnion Audiences Now Available, rendered line 43 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US service terms unresolved.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Audigent's partner release offers TruAudience data combined with publisher audiences or contextual data in SmartPMPs and ContextualPMPs. It expressly sells cookieless media/data curation; Hadron appears separately in navigation. US audience statements describe TransUnion data. Implementation reference documents a separate Hadron ID namespace and module. SmartPMP is a media deal, not its alias. The beta curation partner table lists Hadron ID by Audigent as a secure signal for Experian – Audience. Evidence of a named receiving route, not a nationwide production census. Prebid lists Fabrick ID by Neustar separately, another discovery lead, without proving current operation. A separately named identity module exists. Do not move its integration or audience identifier into this SmartPMP row.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "SmartPMP is a curated media deal. Hadron ID is a separately documented identity module. Do not transfer its features to SmartPMP or count the two names as aliases.",
  "final_wording": "Audigent describes a cookieless media-curation route using TransUnion audiences.",
  "counterevidence": "SmartPMP is a curated media deal. Hadron ID is a separately documented identity module. Do not transfer its features to SmartPMP or count the two names as aliases.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F21",
  "headline": false,
  "claim": "Ogury says the airline campaign used Personified Advertising to reach travelers without relying on their advertising IDs.",
  "chapter": "1, 13",
  "source_ids": [
   "IDN-U-S28"
  ],
  "passage": "targeting them independently of their advertising identifiers",
  "support": [
   {
    "source_id": "IDN-U-S28",
    "passage": "targeting them independently of their advertising identifiers",
    "locator": "Soaring Above The Rest: ANA Lands Big Wins With Ogury’s Personas – Ogury, rendered line 8 (locate by quoted text)"
   }
  ],
  "scope_time": "Campaign January 17–February 15, 2025; read November 11, 2026.",
  "scope_geo": "The Jan 17–Feb 15, 2025 campaign reached inbound travelers in Japan, including visitors from the US. It does not establish US ad delivery.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Ogury reports a Jan 17–Feb 15, 2025 campaign reaching inbound travelers in Japan, including travelers from the US. Ogury's personas use survey signals, without targeting on individual ad IDs. Nationality/source market does not prove US campaign delivery. Travelers from the US were reached in Japan. This is not a domestic US campaign.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Nationality is not targeting geography. Keep the campaign scope attached and verify a US-delivered persona buy.",
  "final_wording": "Ogury says it used Personified Advertising to target travelers arriving in Japan without relying on their advertising IDs during an All Nippon Airways campaign from January 17 to February 15, 2025. The travelers included visitors from the United States.",
  "counterevidence": "Boundary or alternative interpretation: Nationality is not targeting geography. Keep the campaign scope attached and verify a US-delivered persona buy.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F22",
  "headline": false,
  "claim": "Verve announced Moments.AI as a contextual service formerly called Beemray and described targeting without identifiers.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S29"
  ],
  "passage": "[IDN-U-S29, March 8, 2022 news release, opening paragraph.] launch of Moments.AI™ (formerly Beemray) [IDN-U-S29, Verve Group launches Moments.AI™ (formerly Beemray), expanding contextual targeting capabilities to North America, rendered line 8 (locate by quoted text)] without cookies or identifiers",
  "support": [
   {
    "source_id": "IDN-U-S29",
    "passage": "launch of Moments.AI™ (formerly Beemray)",
    "locator": "March 8, 2022 news release, opening paragraph."
   },
   {
    "source_id": "IDN-U-S29",
    "passage": "without cookies or identifiers",
    "locator": "Verve Group launches Moments.AI™ (formerly Beemray), expanding contextual targeting capabilities to North America, rendered line 8 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2022-03-08; read 2026-11-11",
  "scope_geo": "North American launch; US-specific availability requires evidence.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Verve's March 8, 2022 release calls Moments.AI formerly Beemray and describes a North American contextual launch for brands without cookies or identifiers. The region does not specify US campaign delivery, and the launch does not demonstrate 2026 availability. The full-text source has a trademark glyph (™); use it if reproducing the Stage 2 excerpt, rather than the normalised TM. Verve remains flagged for prior employment.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Mark the former-employer interest. Validate current offer and eligible replacement positioning; this rebrand alone does not show continuity of an identity graph.",
  "final_wording": "Verve announced Moments.AI as a contextual service formerly called Beemray and described targeting without identifiers.",
  "counterevidence": "Boundary or alternative interpretation: Mark the former-employer interest. Validate current offer and eligible replacement positioning; this rebrand alone does not show continuity of an identity graph.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F23",
  "headline": false,
  "claim": "Seedtag describes a Henkel contextual campaign as a substitute for a cookie-based strategy.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S30"
  ],
  "passage": "a meaningful alternative to a strategy based on cookies",
  "support": [
   {
    "source_id": "IDN-U-S30",
    "passage": "a meaningful alternative to a strategy based on cookies",
    "locator": "Seedtag, rendered line 14 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US scope unconfirmed for the cited campaign.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Seedtag describes a Pril/Henkel comparison of contextual campaign tactics with and without cookies. LIZ is its enabling AI. The case does not establish the site or market of campaign delivery absent explicit geography. Henkel’s A/B-style media tactics are a vendor case, without a disclosed delivery geography or independent test of graph accuracy.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Test whether the seller offers a defined audience replacement in the US; a plain contextual classification service remains outside the IQ.",
  "final_wording": "Seedtag describes a Henkel contextual campaign as a substitute for a cookie-based strategy.",
  "counterevidence": "Boundary or alternative interpretation: Test whether the seller offers a defined audience replacement in the US; a plain contextual classification service remains outside the IQ.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F24",
  "headline": false,
  "claim": "TransUnion describes Epsilon audiences mapped across its US connected-home graph through the TruAudience Data Marketplace.",
  "chapter": "1, 7",
  "source_ids": [
   "IDN-G-S17",
   "IDN-G-S01",
   "IDN-G-S02"
  ],
  "passage": "[IDN-G-S17, TransUnion and Epsilon Collaborate to Bring ID-Agnostic Audiences to Connected TV and Streaming Audio Campaigns, rendered line 111 (locate by quoted text)] TransUnion’s household identity graph covering more than 80 million U.S. connected homes [IDN-G-S01, TransUnion Introduces TruAudience Marketing Solutions to Power Privacy-Centric Identity and Data Capabilities for Omnichannel Advertising, rendered line 117 (locate by quoted text)] TruAudience Identity, TruAudience Data Marketplace and TruAudience Platform",
  "support": [
   {
    "source_id": "IDN-G-S17",
    "passage": "TransUnion’s household identity graph covering more than 80 million U.S. connected homes",
    "locator": "TransUnion and Epsilon Collaborate to Bring ID-Agnostic Audiences to Connected TV and Streaming Audio Campaigns, rendered line 111 (locate by quoted text)"
   },
   {
    "source_id": "IDN-G-S01",
    "passage": "TruAudience Identity, TruAudience Data Marketplace and TruAudience Platform",
    "locator": "TransUnion Introduces TruAudience Marketing Solutions to Power Privacy-Centric Identity and Data Capabilities for Omnichannel Advertising, rendered line 117 (locate by quoted text)"
   }
  ],
  "scope_time": "TruAudience launch August 24, 2021; Epsilon June 7, 2022; Comcast June 6, 2024. Read November 11, 2026.",
  "scope_geo": "US household graph and CTV audience route explicitly described.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "TransUnion reports that Epsilon audiences became available through its marketplace, matching a vendor-stated 250 million US consumers against a TransUnion household graph covering over 80 million US connected homes. The data, graph and distribution channel differ. TransUnion's launch names three offerings, Identity, Data Marketplace (formerly Tru Optik), and Platform. It rolls up Tru Optik, Signal Digital and TruSignal capabilities across the suite. That sentence does not make the Tru Optik marketplace an alias of the household graph. Comcast and TransUnion’s June 6, 2024 release documents TV activation via Comcast using TransUnion’s graph, rather than a right to acquire a separate streaming graph. Tru Optik is named as the former Data Marketplace. Do not convert that fact into a graph alias, second household SKU or second score.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Epsilon via the TruAudience Data Marketplace and Comcast addressable campaigns establish TV activation routes. Tru Optik is the former marketplace name. Neither release confirms a separately purchasable household resolution service distinct from TruAudience Identity.",
  "final_wording": "TransUnion said Epsilon audiences were available through the TruAudience Data Marketplace using its US connected-home graph. A separate Comcast agreement described using TransUnion’s graph to build segments for TV campaigns on Comcast. Both records describe audience activation.",
  "counterevidence": "Epsilon via the TruAudience Data Marketplace and Comcast addressable campaigns establish TV activation routes. Tru Optik is the former marketplace name. Neither release confirms a separately purchasable household resolution service distinct from TruAudience Identity.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F25",
  "headline": false,
  "claim": "Blockgraph announced a FullThrottle TV integration in which customers could use its Identity Operating System to match and activate data.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S33"
  ],
  "passage": "[IDN-U-S33, Blockgraph and FullThrottle Announce Integration to Unlock New Levels of Addressable Targeting for TV Advertisements, rendered line 17 (locate by quoted text)] FullThrottle’s customers will be able to match and activate [IDN-U-S33, Blockgraph and FullThrottle Announce Integration to Unlock New Levels of Addressable Targeting for TV Advertisements, rendered line 17 (locate by quoted text)] using Blockgraph’s Identity Operating System (IDoS)",
  "support": [
   {
    "source_id": "IDN-U-S33",
    "passage": "FullThrottle’s customers will be able to match and activate",
    "locator": "Blockgraph and FullThrottle Announce Integration to Unlock New Levels of Addressable Targeting for TV Advertisements, rendered line 17 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S33",
    "passage": "using Blockgraph’s Identity Operating System (IDoS)",
    "locator": "Blockgraph and FullThrottle Announce Integration to Unlock New Levels of Addressable Targeting for TV Advertisements, rendered line 17 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2022-06-09; read 2026-11-11",
  "scope_geo": "US-facing launch dateline is not proof of geographic service availability.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Blockgraph's June 9, 2022 release announces FullThrottle's agreement to match/activate household data via the Identity Operating System and participating partners. It discusses future operations. Partnership geography and issuer location do not establish current availability. Future tense is explicit in the partnership release: planned customer capability is not independently established deployment.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Check actual implementation and buyer right to acquire the household-link output for this TV route.",
  "final_wording": "In June 2022, Blockgraph announced an agreement under which FullThrottle customers would be able to match and activate household data through Blockgraph’s Identity Operating System with participating partners.",
  "counterevidence": "Boundary or alternative interpretation: Check actual implementation and buyer right to acquire the household-link output for this TV route.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F26",
  "headline": false,
  "claim": "Viant describes a Household ID service that uses IP addresses and other identifiers to represent homes.",
  "chapter": "7",
  "source_ids": [
   "IDN-U-S34",
   "IDN-U-S35"
  ],
  "passage": "[IDN-U-S34, Viant Household ID™: Precise Household Advertising, rendered line 85 (locate by quoted text)] IP addresses and other identifiers and translates them into [IDN-U-S35, Viant and TransUnion Partner to Enrich Viant Household ID, rendered line 15 (locate by quoted text)] Viant can match its Household ID to 95% of U.S. adults (18+)",
  "support": [
   {
    "source_id": "IDN-U-S34",
    "passage": "IP addresses and other identifiers and translates them into",
    "locator": "Viant Household ID™: Precise Household Advertising, rendered line 85 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S35",
    "passage": "Viant can match its Household ID to 95% of U.S. adults (18+)",
    "locator": "Viant and TransUnion Partner to Enrich Viant Household ID, rendered line 15 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2025-01-28; read 2026-11-11",
  "scope_geo": "US adult scope claimed in a Viant/TransUnion partner release.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Viant markets its Household ID as native to its DSP. Its footnote says the ID itself does not travel in a bid request; the DSP detects associated profiles. Marketing claims for 125 million homes and 115 million addressable homes have different wording. Viant's January 28, 2025 release says it can match its Household ID to 95% of US adults 18+ using TransUnion data. This is a claim about adults, not a 95% household match rate from an independent test. The seller says its profile can be recognized from a bid request, and the Household ID itself is not transmitted in that request. Viant’s US adult match claim is a separate unit.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Viant says its DSP recognizes a Household ID profile from bid request inputs, rather than receiving the Household ID in the bidstream. The US adult figure is a vendor reach assertion. Verify a separate household deliverable.",
  "final_wording": "Viant describes a Household ID service that uses IP addresses and other identifiers to represent homes.",
  "counterevidence": "Viant says its DSP recognizes a Household ID profile from bid request inputs, rather than receiving the Household ID in the bidstream. The US adult figure is a vendor reach assertion. Verify a separate household deliverable.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F27",
  "headline": false,
  "claim": "OpenAP defined OpenID as a person-level audience construct across linear and digital video.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S36",
   "IDN-C-S17"
  ],
  "passage": "[IDN-U-S36, OpenAP, rendered line 16 (locate by quoted text)] a consistent person-level audience definition [IDN-C-S17, OpenAP unveils Open Identity, a Converged ID Solution that Enables Consistency of Audience Identity in Streaming Video, rendered line 15 (locate by quoted text)] a federated identity data infrastructure",
  "support": [
   {
    "source_id": "IDN-U-S36",
    "passage": "a consistent person-level audience definition",
    "locator": "OpenAP, rendered line 16 (locate by quoted text)"
   },
   {
    "source_id": "IDN-C-S17",
    "passage": "a federated identity data infrastructure",
    "locator": "OpenAP unveils Open Identity, a Converged ID Solution that Enables Consistency of Audience Identity in Streaming Video, rendered line 15 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2021-04-28, 2025-04-15; read 2026-11-11",
  "scope_geo": "US publisher adoption claimed in 2021.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "OpenAP's April 28, 2021 release calls OpenID a person-level common TV identifier and names US publishers able to accept it for cross-platform audiences. Its unit is not automatically a household. OpenAP's April 15, 2025 release calls Open Identity an evolution of OpenID and a federated interoperability infrastructure without a central identity spine. Several vendors are named as participating data suppliers. This is not evidence that both names denote an unchanged identifier or one can buy their vendors' products as part of it. The 2025 issuer explicitly supplies a lineage relationship, not a statement of identical product function or household assignment.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "OpenAP called Open Identity a 2025 evolution of its 2021 person-level OpenID. The later product is federated infrastructure, not evidence that OpenID assigns a household. Keep a separate household purchase unconfirmed.",
  "final_wording": "OpenAP described OpenID as a person-level identifier for linear and digital TV in 2021. In 2025 it described Open Identity as an evolution of OpenID, with federated matching that does not require a central identity spine.",
  "counterevidence": "OpenAP called Open Identity a 2025 evolution of its 2021 person-level OpenID. The later product is federated infrastructure, not evidence that OpenID assigns a household. Keep a separate household purchase unconfirmed.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F28",
  "headline": false,
  "claim": "FreeWheel describes its Identity Network as embedded in its platform and connecting identity signals across devices, households and screens.",
  "chapter": "",
  "source_ids": [
   "IDN-G-S08",
   "IDN-U-S39"
  ],
  "passage": "[IDN-G-S08, FreeWheel Identity Network: Smarter Identity for Better Outcomes, rendered line 43 (locate by quoted text)] directly into FreeWheel [IDN-G-S08, www.freewheel.com, rendered line 43 (locate by quoted text)] devices, households, and screens [IDN-U-S39, Identity Network, rendered line 19 (locate by quoted text)] monitoring ID onboarding and match performance data",
  "support": [
   {
    "source_id": "IDN-G-S08",
    "passage": "directly into FreeWheel",
    "locator": "FreeWheel Identity Network: Smarter Identity for Better Outcomes, rendered line 43 (locate by quoted text)"
   },
   {
    "source_id": "IDN-G-S08",
    "passage": "devices, households, and screens",
    "locator": "www.freewheel.com, rendered line 43 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S39",
    "passage": "monitoring ID onboarding and match performance data",
    "locator": "Identity Network, rendered line 19 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US service geography unresolved for the specific implementation.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "FreeWheel's Identity Network page describes CTV identity signal integration across devices, households and screens using Comcast signals, publisher partner IDs and buyer data. The page advertises capabilities, not performance or geographic coverage. FreeWheel documents advertiser API resources to monitor ID onboarding/match status, export mapping reports and inspect permissions. This is a reporting/monitoring interface, not direct evidence of a request that resolves a household. An API to monitor third-party ID mapping is distinct from an API that resolves household identities.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "A network of third-party and operator signals is not sufficient to establish delivery of a distinct household graph product.",
  "final_wording": "FreeWheel describes its Identity Network as embedded in its platform and connecting identity signals across devices, households and screens.",
  "counterevidence": "Boundary or alternative interpretation: A network of third-party and operator signals is not sufficient to establish delivery of a distinct household graph product.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F29",
  "headline": false,
  "claim": "Cadent documents an IP-to-household Viewer Graph and describes the integration of its graph in a Premion partnership.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S10",
   "IDN-U-S41",
   "IDN-UV-S04"
  ],
  "passage": "[IDN-G-S10, Aperture Platform — Next Gen Contextual Targeting, rendered line 11 (locate by quoted text)] IP-to-household Viewer Graph [IDN-U-S41, Cadent Announces Expansion of TV, rendered line 14 (locate by quoted text)] Cadent Viewer Graph, Cadent's proprietary and cookieless",
  "support": [
   {
    "source_id": "IDN-G-S10",
    "passage": "IP-to-household Viewer Graph",
    "locator": "Aperture Platform — Next Gen Contextual Targeting, rendered line 11 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S41",
    "passage": "Cadent Viewer Graph, Cadent's proprietary and cookieless",
    "locator": "Cadent Announces Expansion of TV, rendered line 14 (locate by quoted text)"
   }
  ],
  "scope_time": "Premion agreement announced February 2, 2021; Aperture sales sheet dated 2024; current Total Video offer read November 11, 2026.",
  "scope_geo": "Cadent markets US CTV buying using its Viewer Graph within Total Video. Separate graph access or licensing is unconfirmed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Cadent's 2024 Aperture product PDF says audience targeting can use its IP-to-household Viewer Graph alongside contextual targeting and also independently. Aperture is the platform; Viewer Graph is the graph. In its February 2, 2021 Premion announcement, Cadent describes a graph that connects TV devices to households from first- and third-party data, claiming a 104-million-household graph. An earlier partner project is not proof of the current census, market or rate. The current Total Video offer names the proprietary Viewer Graph and markets US CTV buying. Only the integrated media route is established. The historical Premion release speaks in future tense. Direct live PDF fetches redirected unsuccessfully; search-indexed copies of both exact issuer PDFs reopened with the quoted text. Cadent’s current offering is a media buy.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Viewer Graph is the named graph. Aperture’s 2024 targeting sheet and the current Total Video offer are platforms or routes using it. Premion’s 2021 announcement described planned integration.",
  "final_wording": "Cadent identified its IP-to-household Viewer Graph in a 2024 Aperture product sheet. A 2021 release announced its planned use with Premion. As of November 11, 2026, Cadent also names Viewer Graph in its US CTV media offer.",
  "counterevidence": "Viewer Graph is the named graph. Aperture’s 2024 targeting sheet and the current Total Video offer are platforms or routes using it. Premion’s 2021 announcement described planned integration.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F30",
  "headline": false,
  "claim": "Samba describes its own graph as using the TV as an anchor.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S42"
  ],
  "passage": "it uses the TV as an anchor",
  "support": [
   {
    "source_id": "IDN-U-S42",
    "passage": "it uses the TV as an anchor",
    "locator": "Samba TV Identity, first page, opening paragraph, lines 4–5"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US eligibility immaterial to exclusion.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Samba TV's sales sheet describes the TV as the graph's anchor and claims reach over 500 million digital devices. It is a vendor asset documenting TV identity, not a source for the author's current job or a measured graph validation. Author-declared current employer. The exclusion is an author-method decision, not a finding contained in the vendor PDF. No IQ row or profile.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Retain the author's current employer as a declared interest. No scored row, band, or deep profile. The separate H6 legal screen remains available.",
  "final_wording": "Samba describes its own graph as using the TV as an anchor.",
  "counterevidence": "Boundary or alternative interpretation: Retain the author's current employer as a declared interest. No scored row, band, or deep profile. The separate H6 legal screen remains available.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F31",
  "headline": false,
  "claim": "AWS describes a Clean Rooms query as accessing and analyzing configured tables in a collaboration.",
  "chapter": "1",
  "source_ids": [
   "IDN-U-S43"
  ],
  "passage": "access and analyze configured tables in a collaboration",
  "support": [
   {
    "source_id": "IDN-U-S43",
    "passage": "access and analyze configured tables in a collaboration",
    "locator": "Analyze data in a collaboration - AWS Clean Rooms, rendered line 7 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "Product territory outside IQ scope.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "AWS Clean Rooms' analysis guide describes SQL queries or approved PySpark jobs on configured tables within a collaboration. It does not market a cross-site identifier by that name. Vendor technical documentation (grade C), not direct_record. The company’s user guide establishes a function of its own product and supplies no regulatory, independent, or standards-body finding.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Keep the collaboration service outside the IQ. Separately sold identity-resolution services would need their own screening record.",
  "final_wording": "AWS describes a Clean Rooms query as accessing and analyzing configured tables in a collaboration.",
  "counterevidence": "Boundary or alternative interpretation: Keep the collaboration service outside the IQ. Separately sold identity-resolution services would need their own screening record.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-U-F32",
  "headline": false,
  "claim": "Microsoft documents Curate as enabling curators to enhance a seller’s inventory with their own assets.",
  "chapter": "1",
  "source_ids": [
   "IDN-U-S44"
  ],
  "passage": "enhance the value of a seller’s inventory",
  "support": [
   {
    "source_id": "IDN-U-S44",
    "passage": "enhance the value of a seller’s inventory",
    "locator": "Microsoft Curate - Curated Deals, rendered line 32 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2025-10-21; read 2026-11-11",
  "scope_geo": "Product territory outside IQ scope.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Microsoft Curate documentation lets curators enrich sellers' inventory and sell deals. The October 2025 page describes a curation route, not an identity product; it does not establish 2026 operation of Microsoft Invest. Vendor technical documentation (grade C), not direct_record. The October 2025 guide supports the curation function. It is corporate product documentation and cannot alone establish the present status of a named buying platform.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Keep the deal curation service outside IQ. Check platform availability separately before referring to a live offer.",
  "final_wording": "Microsoft documents Curate as enabling curators to enhance a seller’s inventory with their own assets.",
  "counterevidence": "Boundary or alternative interpretation: Keep the deal curation service outside IQ. Check platform availability separately before referring to a live offer.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-U-F33",
  "headline": false,
  "claim": "OneTrust describes its CMP as capturing and signaling purpose-based consent.",
  "chapter": "1",
  "source_ids": [
   "IDN-U-S45"
  ],
  "passage": "Capture and signal purpose-based consent",
  "support": [
   {
    "source_id": "IDN-U-S45",
    "passage": "Capture and signal purpose-based consent",
    "locator": "Consent Management Platform, rendered line 205 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "Product territory outside IQ scope.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "OneTrust describes purpose-based consent, preference capture, receipts and signaling. This is consent management infrastructure. No cross-partner identity graph or identifier is established.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Record this as an upstream signal dependency only.",
  "final_wording": "OneTrust describes its CMP as capturing and signaling purpose-based consent.",
  "counterevidence": "Boundary or alternative interpretation: Record this as an upstream signal dependency only.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F34",
  "headline": false,
  "claim": "IAB Tech Lab records that Seller Defined Audiences was renamed Curated Audiences in December 2024.",
  "chapter": "",
  "source_ids": [
   "IDN-A-S19"
  ],
  "passage": "In December 2024, Seller Defined Audiences was renamed Curated Audiences",
  "support": [
   {
    "source_id": "IDN-A-S19",
    "passage": "In December 2024, Seller Defined Audiences was renamed Curated Audiences",
    "locator": "Curated Audiences - IAB Tech Lab, rendered line 25 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2024-12; read 2026-11-11",
  "scope_geo": "Standards document; no US product assumption.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "IAB Tech Lab says Seller Defined Audiences was renamed Curated Audiences in December 2024. The specification arose under Project Rearc and combines existing interfaces for first-party cohorts. A rename is not a retirement. A renamed framework is an ongoing standards item, with no extra vendor row created by its previous title.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Do not count the renamed specification as a retired vendor or as a separate cohort service. Its own description identifies its Project Rearc origin.",
  "final_wording": "IAB Tech Lab records that Seller Defined Audiences was renamed Curated Audiences in December 2024.",
  "counterevidence": "Boundary or alternative interpretation: Do not count the renamed specification as a retired vendor or as a separate cohort service. Its own description identifies its Project Rearc origin.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F35",
  "headline": false,
  "claim": "Google included Topics on Chrome and Android in its announced technology retirements.",
  "chapter": "5",
  "source_ids": [
   "IDN-U-S47"
  ],
  "passage": "[IDN-U-S47, Update on Plans for Privacy Sandbox Technologies, rendered line 46 (locate by quoted text)] Topics (Chrome and Android) [IDN-U-S47, Update on Plans for Privacy Sandbox Technologies, rendered line 46 (locate by quoted text)] we've decided to retire the following Privacy Sandbox technologies",
  "support": [
   {
    "source_id": "IDN-U-S47",
    "passage": "Topics (Chrome and Android)",
    "locator": "Update on Plans for Privacy Sandbox Technologies, rendered line 46 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S47",
    "passage": "we've decided to retire the following Privacy Sandbox technologies",
    "locator": "Update on Plans for Privacy Sandbox Technologies, rendered line 46 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2025-10-17; read 2026-11-11",
  "scope_geo": "Chrome and Android named separately in the announcement.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Google's October 17, 2025 decision lists specific Sandbox technologies to retire, including Topics and Protected Audience on Chrome and Android. Google explicitly continues CHIPS, FedCM and Private State Tokens. A decision does not prove a rollout end date. An announced retirement of named APIs is a dated Google platform decision. APIs expressly continuing prevent a claim of wholesale shutdown.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "The announcement establishes a decision. Use stream E for separately qualified release or removal evidence.",
  "final_wording": "Google included Topics on Chrome and Android in its announced technology retirements.",
  "counterevidence": "Boundary or alternative interpretation: The announcement establishes a decision. Use stream E for separately qualified release or removal evidence.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-U-F36",
  "headline": false,
  "claim": "Chrome 153 release notes describe Protected Audience as planned for deprecation and removal.",
  "chapter": "5",
  "source_ids": [
   "IDN-U-S48"
  ],
  "passage": "the Protected Audience API is planned for deprecation and removal",
  "support": [
   {
    "source_id": "IDN-U-S48",
    "passage": "the Protected Audience API is planned for deprecation and removal",
    "locator": "Chrome 153  |  Release notes  |  Chrome for Developers, rendered line 119 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2026-09-08; read 2026-11-11",
  "scope_geo": "Chrome 153 release note; distinct from Android.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Chrome 153 stable is dated September 8, 2026. A section titled deprecation and removal of Protected Audience still describes removal as planned. A heading alone does not date a completed removal on all clients or systems. Topics is not named in the opened Chrome 153 entry. The release heading and its future-tense body differ in force; do not turn the stable release date into proof of universal removal.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Record this precise scope and refer to stream E for other endpoint or version milestones. A headline alone cannot establish removal from every installation.",
  "final_wording": "Chrome 153 release notes describe Protected Audience as planned for deprecation and removal.",
  "counterevidence": "Boundary or alternative interpretation: Record this precise scope and refer to stream E for other endpoint or version milestones. A headline alone cannot establish removal from every installation.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-U-F37",
  "headline": false,
  "claim": "Google said Topics replaced its FLoC proposal following FLoC trials.",
  "chapter": "5",
  "source_ids": [
   "IDN-U-S49"
  ],
  "passage": "and replaces our FLoC proposal",
  "support": [
   {
    "source_id": "IDN-U-S49",
    "passage": "and replaces our FLoC proposal",
    "locator": "Get to know the new Topics API for Privacy Sandbox, rendered line 228 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2022-01-25; read 2026-11-11",
  "scope_geo": "Chrome proposal; no vendor admission.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Google's January 2022 article says Topics was proposed in place of the earlier FLoC proposal after FLoC trials. Neither an open-market product nor a separate GA FLoC service follows. FLoC was the replaced trial proposal. This record does not date removal of Topics, or Protected Audience.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Classify the replaced proposal as historical and keep trial, replacement and later Topics events separate.",
  "final_wording": "Google said Topics replaced its FLoC proposal following FLoC trials.",
  "counterevidence": "Boundary or alternative interpretation: Classify the replaced proposal as historical and keep trial, replacement and later Topics events separate.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-U-F38",
  "headline": false,
  "claim": "Prebid documents a 33Across User ID module that uses Lexicon technology.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S50"
  ],
  "passage": "33Across User ID sub-module utilizes Lexicon technology",
  "support": [
   {
    "source_id": "IDN-U-S50",
    "passage": "33Across User ID sub-module utilizes Lexicon technology",
    "locator": "33Across ID for Header Bidding, rendered line 103 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "Prebid expressly lists United States, Canada, Australia and Japan as Lexicon support markets. Current commercial terms and named US deployments are unverified.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Prebid documents 33Across' module, which uses probabilistic Lexicon technology, with stated support for US, Canada, Australia and Japan. A module name and its enabling technology are not two eligible products by default. The table previously missed explicit US support in the same guide. Manufacturer support and actual US deployment remain separate.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "The documented module uses Lexicon technology with US support. Check named receiving deployments and present commercial terms. No reach claim is taken from the blocked launch page.",
  "final_wording": "Prebid documents a 33Across User ID module that uses Lexicon technology. Its guide lists support in the US, Canada, Australia and Japan.",
  "counterevidence": "The documented module uses Lexicon technology with US support. Check named receiving deployments and present commercial terms. No reach claim is taken from the blocked launch page.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-U-F39",
  "headline": false,
  "claim": "Zeotap describes ID+ as a first-party identity layer and dates its announcement to July 2020.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S51"
  ],
  "passage": "[IDN-U-S51, Section 3, PDF page 8, principle 2 (Simplicity).] as a standalone first-party identity layer [IDN-U-S51, Section 3, PDF page 8, introductory paragraph.] In July 2020, Zeotap announced its own solution",
  "support": [
   {
    "source_id": "IDN-U-S51",
    "passage": "as a standalone first-party identity layer",
    "locator": "Section 3, PDF page 8, principle 2 (Simplicity)."
   },
   {
    "source_id": "IDN-U-S51",
    "passage": "In July 2020, Zeotap announced its own solution",
    "locator": "Section 3, PDF page 8, introductory paragraph."
   }
  ],
  "scope_time": "Dated records 2020-07; read 2026-11-11",
  "scope_geo": "Historical issuer document; current US offer unknown.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Zeotap's PDF describes ID+ announced July 2020, based on deterministic offline identifiers, and distributed via a Prebid user ID module. The North America/Latin America/Europe/India passage refers to the underlying graph. Hosting path is not reliable for original publication year. The US geography of the underlying graph has not been shown for ID+ specifically. The printed PDF puts launch and standalone design in section 3, printed p. 8 (PDF page 8 of 12).",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Investigate current delivery and territorial restrictions. Do not import the document's historical forecasts as current browser policy.",
  "final_wording": "Zeotap describes ID+ as a first-party identity layer and dates its announcement to July 2020.",
  "counterevidence": "Boundary or alternative interpretation: Investigate current delivery and territorial restrictions. Do not import the document's historical forecasts as current browser policy.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F40",
  "headline": false,
  "claim": "PubMatic describes Proximic by Comscore’s solutions as contextual alternatives to ID-based targeting and names Predictive Audiences.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S52"
  ],
  "passage": "[IDN-U-S52, Scalable, ID-less Targeting Solutions for Media Buyers, rendered line 164 (locate by quoted text)] contextually driven alternatives to ID-based targeting [IDN-U-S52, Scalable, ID-less Targeting Solutions for Media Buyers, rendered line 166 (locate by quoted text)] our Predictive Audiences easily accessible",
  "support": [
   {
    "source_id": "IDN-U-S52",
    "passage": "contextually driven alternatives to ID-based targeting",
    "locator": "Scalable, ID-less Targeting Solutions for Media Buyers, rendered line 164 (locate by quoted text)"
   },
   {
    "source_id": "IDN-U-S52",
    "passage": "our Predictive Audiences easily accessible",
    "locator": "Scalable, ID-less Targeting Solutions for Media Buyers, rendered line 166 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2023-03-23; read 2026-11-11",
  "scope_geo": "US dateline and partnership; US deployments need confirmation.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "PubMatic announced March 23, 2023 that Proximic Predictive Audiences and Content Targeting had been integrated into Connect. Its partner describes them as context-based alternatives to ID targeting. This proves an announced available partner route at that date, not current US delivery. PubMatic reported a route through Connect at the 2023 announcement. Current territorial coverage and usage are separate questions.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Check the Predictive Audiences deliverable apart from PubMatic's marketplace, and confirm subsequent US availability.",
  "final_wording": "PubMatic describes Proximic by Comscore’s solutions as contextual alternatives to ID-based targeting and names Predictive Audiences.",
  "counterevidence": "Boundary or alternative interpretation: Check the Predictive Audiences deliverable apart from PubMatic's marketplace, and confirm subsequent US availability.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F41",
  "headline": false,
  "claim": "The Trade Desk describes Galileo as first-party data activation that works with UID2.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S53"
  ],
  "passage": "Galileo works in concert with new cross-channel identity solutions, including Unified ID 2.0",
  "support": [
   {
    "source_id": "IDN-U-S53",
    "passage": "Galileo works in concert with new cross-channel identity solutions, including Unified ID 2.0",
    "locator": "The Trade Desk Announces Galileo, a New Approach for Activating Advertiser Data, rendered line 146 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2023-01-05; read 2026-11-11",
  "scope_geo": "US-specific eligibility not tested for distinct identifier.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The Trade Desk's January 5, 2023 release describes Galileo as an advertiser first-party activation approach with UID2 and onboarding integrations. Galileo is an activation workflow; UID2 supplies the identifier. Galileo is an activation route using UID2. The release establishes no separate exchange identifier for a second cohort A row.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Do not double-count a UID2 integration as a second interoperable ID. Reopen if a distinct service meets a registered task.",
  "final_wording": "The Trade Desk describes Galileo as first-party data activation that works with UID2.",
  "counterevidence": "Boundary or alternative interpretation: Do not double-count a UID2 integration as a second interoperable ID. Reopen if a distinct service meets a registered task.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F42",
  "headline": false,
  "claim": "Deep Sync describes using its identity graph to resolve the CRM of a US retailer in its Profile Hygiene and Enrichment case.",
  "chapter": "11",
  "source_ids": [
   "IDN-C-S19"
  ],
  "passage": "[IDN-C-S19, Retail case study: 4.9× device IDs per customer, Deep Sync, rendered line 51 (locate by quoted text)] U.S. seller of recreational vehicles [IDN-C-S19, Retail case study: 4.9× device IDs per customer, Deep Sync, rendered line 57 (locate by quoted text)] identifier type against the identity graph",
  "support": [
   {
    "source_id": "IDN-C-S19",
    "passage": "U.S. seller of recreational vehicles",
    "locator": "Retail case study: 4.9× device IDs per customer, Deep Sync, rendered line 51 (locate by quoted text)"
   },
   {
    "source_id": "IDN-C-S19",
    "passage": "identifier type against the identity graph",
    "locator": "Retail case study: 4.9× device IDs per customer, Deep Sync, rendered line 57 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US retailer explicitly identified by geography.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Deep Sync reports a US RV retailer CRM test with 19 matching rules active. Its overview rounds the file to 885,000 rows and results say 884K. 83.5% is a vendor match claim. Device append rates, 510K UUID-matched rows and 4.9 device IDs are different metrics. The retail case gives rounded 885K and 884K CRM bases in different places. If a subsequent claim quotes a match rate, preserve both, the 19 rules, the row unit and the sponsor.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Screen as a distinct US graph resolution offer; carry its stated base, unit and setup to the match-rate test in stream C.",
  "final_wording": "Deep Sync describes using its identity graph to resolve the CRM of a US retailer in its Profile Hygiene and Enrichment case.",
  "counterevidence": "Boundary or alternative interpretation: Screen as a distinct US graph resolution offer; carry its stated base, unit and setup to the match-rate test in stream C.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-U-F43",
  "headline": false,
  "claim": "Deep Sync describes a US grocery case in which it resolved transactions with payment signals and its identity graph.",
  "chapter": "11",
  "source_ids": [
   "IDN-C-S20"
  ],
  "passage": "[IDN-C-S20, Grocery case study: Transaction Matching, Deep Sync, rendered line 75 (locate by quoted text)] matches payment card signals against our identity graph [IDN-C-S20, Grocery case study: Transaction Matching, Deep Sync, rendered line 51 (locate by quoted text)] grocery retailers in the United States",
  "support": [
   {
    "source_id": "IDN-C-S20",
    "passage": "matches payment card signals against our identity graph",
    "locator": "Grocery case study: Transaction Matching, Deep Sync, rendered line 75 (locate by quoted text)"
   },
   {
    "source_id": "IDN-C-S20",
    "passage": "grocery retailers in the United States",
    "locator": "Grocery case study: Transaction Matching, Deep Sync, rendered line 51 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US grocery retailer explicitly identified by geography.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Deep Sync describes one monthly US grocery POS file and three matching passes, ending with probabilistic store-catchment assignment. It mixes volumes processed, resolved, and cumulative rates with conflicting headline labels. The grocery outcome is not interchangeable with retail CRM graph match accuracy. Payment-card matching is only one stage. The publisher’s ~70%/73% and processed/resolved counts do not independently validate identity or reconcile the different denominators.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Test whether identifying transactions is a separately purchased US identity service or the attribution output of another product. Do not pool its rate with Profile Hygiene and Enrichment.",
  "final_wording": "Deep Sync describes three matching passes on a US grocer’s transaction file. The second matched payment-card signals against its identity graph. The third used store geography and household data to infer a buyer.",
  "counterevidence": "Boundary or alternative interpretation: Test whether identifying transactions is a separately purchased US identity service or the attribution output of another product. Do not pool its rate with Profile Hygiene and Enrichment.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-U-F44",
  "headline": false,
  "claim": "Kochava describes a household graph used in an advanced CTV measurement case.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S56"
  ],
  "passage": "A primary IP/household identity graph",
  "support": [
   {
    "source_id": "IDN-U-S56",
    "passage": "A primary IP/household identity graph",
    "locator": "Kochava QSR case, The solution, paragraph 1, current rendered line 154."
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "Kochava describes a US QSR CTV campaign using household mapping. The source does not establish a Kochava Collective product or standalone graph licence.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Kochava reports a US QSR CTV campaign with about 1.7M exposed/300K holdout hashed primary IPs and 66.1% graph matching against both groups. A campaign use case is not independent accuracy nor proof of licensing the graph standalone. Kochava’s QSR case identifies a US measurement campaign. It does not name Kochava Collective as provider of the graph in that case.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Trace the relation of that deployment to Kochava Collective and to independently purchasable household mapping; a CTV measurement case cannot establish a current graph licence. Track legal scope separately in H.",
  "final_wording": "Kochava describes a household graph used in an advanced CTV measurement case.",
  "counterevidence": "Boundary or alternative interpretation: Trace the relation of that deployment to Kochava Collective and to independently purchasable household mapping; a CTV measurement case cannot establish a current graph licence. Track legal scope separately in H.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F45",
  "headline": false,
  "claim": "LtvAdx documents a household ID lookup or creation route in its Identity API.",
  "chapter": "7, 13",
  "source_ids": [
   "IDN-G-S13",
   "IDN-GV-S01",
   "IDN-GV-S02",
   "IDN-GV-S03"
  ],
  "passage": "nothing matched — a new household is created",
  "support": [
   {
    "source_id": "IDN-G-S13",
    "passage": "nothing matched — a new household is created",
    "locator": "Resolving a HouseholdID, match-order table, row 3."
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "LtvAdx markets a US TV campaign route with HouseholdID targeting in a paid-impression plan. Separate licensing of household resolution is unconfirmed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "LtvAdx documents VAST request household resolution, including an optional shared-IP-protected fallback disabled by default, and separate Identity API behavior. It drops device links 30 days and households 90 days after last seen. No US availability or observed calibration is established. LtvAdx offers US household targeting and frequency in an advertiser plan billed on delivered impressions. Its product page describes household segments; no rate or right is given for a standalone graph licence. The old quoted sentence is absent in the reopened revision, but the resolving table confirms the function. Its quoted replacement is “nothing matched — a new household is created” under Resolving a HouseholdID, table row 3. VAST serving fallback and the Identity API are different interfaces.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "The US TV media offer includes HouseholdID targeting. A separate resolution licence or independently documented US deployment remains unconfirmed. In VAST serving, IP fallback is off by default and requires exactly one known household at that IP. The Identity API separately allows a probabilistic IP match.",
  "final_wording": "LtvAdx documents an Identity API that returns an existing HouseholdID or creates a new one. It markets household targeting in US TV campaigns and includes HouseholdID targeting in a plan billed on delivered impressions. The plan does not establish a separately licensed graph.",
  "counterevidence": "The US TV media offer includes HouseholdID targeting. A separate resolution licence or independently documented US deployment remains unconfirmed. In VAST serving, IP fallback is off by default and requires exactly one known household at that IP. The Identity API separately allows a probabilistic IP match.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F46",
  "headline": false,
  "claim": "LiveRamp documents a programmer workflow that resolves IP-based CTV viewer data to RampID.",
  "chapter": "",
  "source_ids": [
   "IDN-G-S11"
  ],
  "passage": "[IDN-G-S11, Programmer’s Guide to Connected TV Audience Recognition, rendered line 11 (locate by quoted text)] IP address-based TV viewer data [IDN-G-S11, Programmer’s Guide to Connected TV Audience Recognition, rendered line 11 (locate by quoted text)] to LiveRamp RampID",
  "support": [
   {
    "source_id": "IDN-G-S11",
    "passage": "IP address-based TV viewer data",
    "locator": "Programmer’s Guide to Connected TV Audience Recognition, rendered line 11 (locate by quoted text)"
   },
   {
    "source_id": "IDN-G-S11",
    "passage": "to LiveRamp RampID",
    "locator": "Programmer’s Guide to Connected TV Audience Recognition, rendered line 11 (locate by quoted text)"
   }
  ],
  "scope_time": "Dated records 2021-05-25; read 2026-11-11",
  "scope_geo": "US purchase or deployment unconfirmed for this programmer workflow.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "LiveRamp's May 25, 2021 programmer guide describes IP-based matching specifically for CTV viewer data to RampIDs for Advanced TV activation. It recommends daily/weekly fresh files after initial history; this is not a graph decay or link expiry period. Recommended file delivery is an ingestion interval, not a household-edge expiry. The 2021 guide leaves current standalone purchase unresolved.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Check separate TV purchase and deliverable to avoid duplicating P001 or P012; the guide establishes a named workflow.",
  "final_wording": "LiveRamp documents a programmer workflow that resolves IP-based CTV viewer data to RampID.",
  "counterevidence": "Boundary or alternative interpretation: Check separate TV purchase and deliverable to avoid duplicating P001 or P012; the guide establishes a named workflow.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F47",
  "headline": false,
  "claim": "Factori describes its CTV graphs as identifying household users across devices.",
  "chapter": "7",
  "source_ids": [
   "IDN-G-S12",
   "IDN-GV-S04"
  ],
  "passage": "build CTV graphs by identifying household users across devices",
  "support": [
   {
    "source_id": "IDN-G-S12",
    "passage": "build CTV graphs by identifying household users across devices",
    "locator": "Cross Device / CTV Graph, rendered line 22 (locate by quoted text)"
   }
  ],
  "scope_time": "Documentation explicitly last updated September 2026; read November 11, 2026.",
  "scope_geo": "Factori markets the CTV/cross-device dataset globally through AWS Marketplace. The listing does not identify US dataset coverage or a US deployment.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Factori describes encrypted MAID/IP-linked devices, household CTV graph and daily S2S data delivery. Its three-billion figure is records, not unique US homes; daily update/feed is not a link decay term. Factori’s AWS Marketplace listing offers a contract for its CTV/cross-device dataset. The listing describes global scope without a US data breakout. The reopened page explicitly says “Last Updated on September, 2026”; January 2026 is not the version date shown. Daily feed delivery is not link decay.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "A contract subscription for the cross-device/CTV data is documented. Confirm US-specific records or a US use case, and a rule for household-link aging. The daily feed cadence does not document that rule.",
  "final_wording": "Factori’s cross-device and CTV graph guide, marked last updated in September 2026, describes identifying household users across devices and delivering a daily data feed. Its AWS Marketplace listing offers a contract for the dataset and describes global coverage without a US breakout.",
  "counterevidence": "A contract subscription for the cross-device/CTV data is documented. Confirm US-specific records or a US use case, and a rule for household-link aging. The daily feed cadence does not document that rule.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-U-F48",
  "headline": false,
  "claim": "Datonics describes Cookieless Audience Targeting as being in limited release for existing Datonics and Intent IQ clients.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S60"
  ],
  "passage": "under limited release for current Datonics and Intent IQ clients",
  "support": [
   {
    "source_id": "IDN-U-S60",
    "passage": "under limited release for current Datonics and Intent IQ clients",
    "locator": "Cookieless Audience Targeting, rendered line 79 (locate by quoted text)"
   }
  ],
  "scope_time": "Public documentation read 2026-11-11; see per-source dates",
  "scope_geo": "US eligibility unconfirmed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Datonics markets limited-release cookieless 1:1 targeting to existing Datonics/Intent IQ clients using an ID graph with IP, hashed email, mobile IDs and cookies. It is not inherently a mostly contextual cohort, a released interest cohort standard, or proof of general availability. The offer describes graph-based one-to-one audience targeting under limited release. Modelled or cohort output and US access remain unproved.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "Datonics describes 1:1 targeting through an ID graph and a limited release for existing clients. The record does not identify a buyable cohort, modelled audience or seller-defined output meeting the registered C task.",
  "final_wording": "Datonics describes Cookieless Audience Targeting as being in limited release for existing Datonics and Intent IQ clients.",
  "counterevidence": "Datonics describes 1:1 targeting through an ID graph and a limited release for existing clients. The record does not identify a buyable cohort, modelled audience or seller-defined output meeting the registered C task.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-U-F49",
  "headline": false,
  "claim": "IAB Tech Lab's Accountability Platform document is marked as a 2021 public-comment draft.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S61"
  ],
  "passage": "Draft in Request for Public Comment until May 7, 2021",
  "support": [
   {
    "source_id": "IDN-U-S61",
    "passage": "Draft in Request for Public Comment until May 7, 2021",
    "locator": "Cover, PDF page 1, draft/public-comment line."
   }
  ],
  "scope_time": "Public-comment draft March 2021; comment deadline May 7, 2021. Read November 11, 2026.",
  "scope_geo": "Standards proposal; no US availability assigned.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "IAB Tech Lab's March 2021 Accountability Platform proposal was a request for comment until May 7, 2021 from the Rearc Accountability Working Group. It describes data structures/practices for conformity, not a later ratification, adoption, abandonment or retirement. March 2021 is the draft date; May 7 is the close of the comment window, not adoption or withdrawal.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer or implementation record directly supports the bounded statement; service-specific eligibility is recorded separately.",
  "limitations": "No dated withdrawal was located in the registered IAB searches. Keep publication of the draft and possible retirement as distinct questions.",
  "final_wording": "IAB Tech Lab's Accountability Platform document is marked as a 2021 public-comment draft.",
  "counterevidence": "Boundary or alternative interpretation: No dated withdrawal was located in the registered IAB searches. Keep publication of the draft and possible retirement as distinct questions.",
  "stream": "U",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F01",
  "headline": false,
  "claim": "Blockgraph identified the United States as the territory for its commercial peer-to-peer TV resolution service in its 2021 notice.",
  "chapter": "7",
  "source_ids": [
   "IDN-CTV-S01"
  ],
  "passage": "currently available only in the United States",
  "support": [
   {
    "source_id": "IDN-CTV-S01",
    "passage": "currently available only in the United States",
    "locator": "Introduction, paragraph defining Services"
   }
  ],
  "scope_time": "2021-01-21",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Blockgraph’s notice effective January 21, 2021 names its peer-to-peer offering for TV and premium video, then expressly limits the service to the US. It separately addresses UK and European website visitors.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "The notice also addresses European website visitors. Website accessibility does not confer a European product entitlement.",
  "final_wording": "Blockgraph identified the United States as the territory for its commercial peer-to-peer TV resolution service in its 2021 notice.",
  "counterevidence": "The notice also addresses European website visitors. Website accessibility does not confer a European product entitlement.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F02",
  "headline": false,
  "claim": "TVSquared reported using Blockgraph’s IDoS for converged-TV identity resolution in its February 2022 response to NBCUniversal.",
  "chapter": "7",
  "source_ids": [
   "IDN-CTV-S02"
  ],
  "passage": "TVSquared leverages Blockgraph’s Identity Operating System",
  "support": [
   {
    "source_id": "IDN-CTV-S02",
    "passage": "TVSquared leverages Blockgraph’s Identity Operating System",
    "locator": "TVSquared, Identity Solution, printed page 99, first answer"
   }
  ],
  "scope_time": "2022-02",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "TVSquared supplied its own answer on printed page 99. It says it leverages IDoS and identifies other providers. Its reference to hashed IP fallback for unauthenticated CTV does not identify Blockgraph as the source of that fallback.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "TVSquared identified multiple other providers. Its fallback use of hashed IP cannot automatically be attributed to Blockgraph.",
  "final_wording": "TVSquared reported using Blockgraph’s IDoS for converged-TV identity resolution in its February 2022 response to NBCUniversal.",
  "counterevidence": "TVSquared identified multiple other providers. Its fallback use of hashed IP cannot automatically be attributed to Blockgraph.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F03",
  "headline": false,
  "claim": "Blockgraph’s general manager described a software subscription to join its network in February 2020.",
  "chapter": "7, 8",
  "source_ids": [
   "IDN-CTV-S03"
  ],
  "passage": "software licensing costs to join our network",
  "support": [
   {
    "source_id": "IDN-CTV-S03",
    "passage": "software licensing costs to join our network",
    "locator": "Interview, answer to “What’s the revenue model?”"
   }
  ],
  "scope_time": "2020-02-27",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "In the February 27 interview the general manager calls the business subscription-based. Software licence costs to join varied with the type and size of the customer’s data. This predates the joint venture and discloses no current subscription price.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "The account predates the joint venture. The reviewed sources provide no current enterprise schedule, revenue or margin.",
  "final_wording": "Blockgraph’s general manager described a software subscription to join its network in February 2020.",
  "counterevidence": "The account predates the joint venture. The reviewed sources provide no current enterprise schedule, revenue or margin.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F04",
  "headline": false,
  "claim": "Neustar’s 2022 TV Analytics sheet described household-level TV measurement and assigned the identity-linking role to OneID.",
  "chapter": "",
  "source_ids": [
   "IDN-CTV-S04"
  ],
  "passage": "[IDN-CTV-S04, Page 2, Neustar OneID] Leverage our industry-leading, authoritative identity to link TV viewing to households [IDN-CTV-S04, Page 1, opening heading] A Holistic TV Measurement Solution",
  "support": [
   {
    "source_id": "IDN-CTV-S04",
    "passage": "Leverage our industry-leading, authoritative identity to link TV viewing to households",
    "locator": "Page 2, Neustar OneID"
   },
   {
    "source_id": "IDN-CTV-S04",
    "passage": "A Holistic TV Measurement Solution",
    "locator": "Page 1, opening heading"
   }
  ],
  "scope_time": "2022 solution sheet; document identifier ends in 01.21.2022",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The two-page sheet is for Neustar TV Analytics. Page 1 describes granular household measurement of TV impressions and page 2 assigns TV-to-household linking to OneID. It supplies no independently orderable CTV-resolution SKU. The direct CDN request returned 503; web PDF extraction provided both original pages. The 01.21.2022 document code is not a signed publication timestamp.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "The sheet does not identify a separately purchasable US streaming household graph. The older TransUnion candidate remains unresolved.",
  "final_wording": "Neustar’s 2022 TV Analytics sheet described household-level TV measurement and assigned the identity-linking role to OneID.",
  "counterevidence": "The sheet does not identify a separately purchasable US streaming household graph. The older TransUnion candidate remains unresolved.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F05",
  "headline": false,
  "claim": "In May 2020, Comcast, Charter and ViacomCBS announced an agreement for equal ownership of Blockgraph, an initiative Charter dates to 2017.",
  "chapter": "8",
  "source_ids": [
   "IDN-CTV-S05",
   "IDN-VCTV-S01"
  ],
  "passage": "[IDN-CTV-S05, Joint release, first paragraph in the Blockgraph issuer copy under IDN-VCTV-S01; original Charter URL redirects.] entered into an agreement to take equal ownership [IDN-CTV-S05, Joint release, history paragraph beginning with the 2017 launch, Blockgraph issuer copy under IDN-VCTV-S01.] Blockgraph was first launched in 2017",
  "support": [
   {
    "source_id": "IDN-CTV-S05",
    "passage": "entered into an agreement to take equal ownership",
    "locator": "Joint release, first paragraph in the Blockgraph issuer copy under IDN-VCTV-S01; original Charter URL redirects."
   },
   {
    "source_id": "IDN-CTV-S05",
    "passage": "Blockgraph was first launched in 2017",
    "locator": "Joint release, history paragraph beginning with the 2017 launch, Blockgraph issuer copy under IDN-VCTV-S01."
   }
  ],
  "scope_time": "2017 and 2020-05-29",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The Charter link now redirects to its newsroom. The same joint release is intact on Blockgraph’s site. Dated May 29, 2020, it records the equal-ownership agreement and dates the initiative’s launch to 2017 with incubation inside FreeWheel. Both URLs are retained so the redirected original and working copy can be audited.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "The release dates the agreement. The current ownership percentages and legal formation date were not verified.",
  "final_wording": "In a May 29, 2020 joint release, Comcast, Charter and ViacomCBS announced an agreement for equal ownership of Blockgraph and dated the original FreeWheel initiative to 2017.",
  "counterevidence": "The release dates the agreement. The current ownership percentages and legal formation date were not verified.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F06",
  "headline": false,
  "claim": "Blockgraph names Comcast NBCUniversal, Charter Communications and Paramount as owners, while Comscore’s FY2025 filing identifies Blockgraph as private.",
  "chapter": "8",
  "source_ids": [
   "IDN-CTV-S06",
   "IDN-CTV-S18"
  ],
  "passage": "[IDN-CTV-S06, Backed by the Industry] Blockgraph is owned by Comcast NBCUniversal, Charter Communications Inc., and Paramount. [IDN-CTV-S18, Non-Executive Directors, David Kline biography, printed page 9] private company Blockgraph",
  "support": [
   {
    "source_id": "IDN-CTV-S06",
    "passage": "Blockgraph is owned by Comcast NBCUniversal, Charter Communications Inc., and Paramount.",
    "locator": "Backed by the Industry"
   },
   {
    "source_id": "IDN-CTV-S18",
    "passage": "private company Blockgraph",
    "locator": "Non-Executive Directors, David Kline biography, printed page 9"
   }
  ],
  "scope_time": "2026-03-25 to 2026-11-11",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "Blockgraph’s ownership section lists three names without percentages. Comscore’s FY2025 Form 10-K, in its David Kline biography, calls Blockgraph a private company. The filing does not establish present equity shares or operating results for IDoS.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "The sources name the parties at different dates and do not identify a current allocation or separate product income.",
  "final_wording": "Blockgraph names Comcast NBCUniversal, Charter Communications and Paramount as owners, while Comscore’s FY2025 filing identifies Blockgraph as private.",
  "counterevidence": "The sources name the parties at different dates and do not identify a current allocation or separate product income.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F07",
  "headline": false,
  "claim": "The v2.29 enterprise guide requires a household record ID and postal address and permits additional signals for that household, including IP and set-top-box IDs.",
  "chapter": "7, 11",
  "source_ids": [
   "IDN-CTV-S11"
  ],
  "passage": "[IDN-CTV-S11, How it works, mandatory fields immediately below Supported Data Types] Household ID and Address (i.e., Postal Address) are mandatory fields. [IDN-CTV-S11, How it works, Supported Data Types] Set top box ID (STB ID)",
  "support": [
   {
    "source_id": "IDN-CTV-S11",
    "passage": "Household ID and Address (i.e., Postal Address) are mandatory fields.",
    "locator": "How it works, mandatory fields immediately below Supported Data Types"
   },
   {
    "source_id": "IDN-CTV-S11",
    "passage": "Set top box ID (STB ID)",
    "locator": "How it works, Supported Data Types"
   }
  ],
  "scope_time": "Release 2.29, 2026-08",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Version 2.29 specifies a household record ID plus a valid postal address when establishing identity. It lists optional IP, email, device and set-top-box signals. The rule establishes the documented input contract, without testing the resulting links. The deciding source is the seller’s technical manual or release note (grade C). It establishes the documented behavior of the specified version; execution or accuracy has not been independently observed.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "The household comes from the supplying node’s records. An optional signal on that record is not evidence that a particular person watched.",
  "final_wording": "The v2.29 enterprise guide requires a household record ID and postal address and permits additional signals for that household, including IP and set-top-box IDs.",
  "counterevidence": "The household comes from the supplying node’s records. An optional signal on that record is not evidence that a particular person watched.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F08",
  "headline": false,
  "claim": "Blockgraph’s v2.29 manual distinguishes deleting a subscriber record from opting it out: opt-out makes existing segments and matches stale until refreshed.",
  "chapter": "7",
  "source_ids": [
   "IDN-CTV-S12"
  ],
  "passage": "[IDN-CTV-S12, Manual Identity Upload, Remove Data, Opt Out] marks existing segments and matches as stale [IDN-CTV-S12, Manual Identity Upload, Remove Data, Delete] Existing segments and matches remain available",
  "support": [
   {
    "source_id": "IDN-CTV-S12",
    "passage": "marks existing segments and matches as stale",
    "locator": "Manual Identity Upload, Remove Data, Opt Out"
   },
   {
    "source_id": "IDN-CTV-S12",
    "passage": "Existing segments and matches remain available",
    "locator": "Manual Identity Upload, Remove Data, Delete"
   }
  ],
  "scope_time": "Release 2.29, 2026-08",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The two removal paths differ. Delete leaves existing segments and matches available. Opt Out removes the record from the subscriber file, marks affected existing segments and matches stale, and requires refresh before later use. Recall of previously exported copies is unspecified. The deciding source is the seller’s technical manual or release note (grade C). It establishes the documented behavior of the specified version; execution or accuracy has not been independently observed.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "Delete leaves existing segments and matches available. The manual does not specify removal from past exports or a bar on reappearance.",
  "final_wording": "Blockgraph’s v2.29 manual distinguishes deleting a subscriber record from opting it out: opt-out makes existing segments and matches stale until refreshed.",
  "counterevidence": "Delete leaves existing segments and matches available. The manual does not specify removal from past exports or a bar on reappearance.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F09",
  "headline": false,
  "claim": "For historical IP lookup, Blockgraph documents optional row timestamps and configurable lookback periods of 30, 60 or 90 days when the provider maintains household signal history.",
  "chapter": "abstract, 1, 7, 12, 13",
  "source_ids": [
   "IDN-CTV-S16"
  ],
  "passage": "within the past 30, 60, or 90 days, depending on the configured history retention period",
  "support": [
   {
    "source_id": "IDN-CTV-S16",
    "passage": "within the past 30, 60, or 90 days, depending on the configured history retention period",
    "locator": "ID Resolution, Other Info, final paragraph on row-based timestamps"
   }
  ],
  "scope_time": "Release 2.29, 2026-08",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Version 2.29 permits a per-row optional timestamp for IP. Historical signal resolution depends on the provider keeping a household’s earlier signal values and on its configured 30-, 60- or 90-day retention. No current-link maximum age is supplied. The deciding source is the seller’s technical manual or release note (grade C). It establishes the documented behavior of the specified version; execution or accuracy has not been independently observed. Time-indexed historical lookups, post-impression attribution and expiry of the currently accepted link are separate objects.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "The lookback bounds history available for lookup. The source does not specify an upper age for the current IP-to-household edge.",
  "final_wording": "For historical IP lookup, Blockgraph documents optional row timestamps and configurable lookback periods of 30, 60 or 90 days when the provider maintains household signal history.",
  "counterevidence": "The lookback bounds history available for lookup. The source does not specify an upper age for the current IP-to-household edge.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-CTV-F10",
  "headline": false,
  "claim": "Blockgraph’s v2.29 Universe Match workflow lists partners that granted permission and specifies a downloadable file containing one column of Blockgraph IDs.",
  "chapter": "7, 8, 11",
  "source_ids": [
   "IDN-CTV-S13",
   "IDN-CTV-S14"
  ],
  "passage": "[IDN-CTV-S13, Identity Universe Match Steps] Partners who have granted permissions will appear on the list. [IDN-CTV-S14, Universe Match Download, File Content] Single column of BG IDs, no header.",
  "support": [
   {
    "source_id": "IDN-CTV-S13",
    "passage": "Partners who have granted permissions will appear on the list.",
    "locator": "Identity Universe Match Steps"
   },
   {
    "source_id": "IDN-CTV-S14",
    "passage": "Single column of BG IDs, no header.",
    "locator": "Universe Match Download, File Content"
   }
  ],
  "scope_time": "Release 2.29, 2026-08",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The v2.29 workflow lists participants that granted permission. A participant can calculate or refresh the match count, then obtain the universe match result. The output guide specifies a headerless CSV column of BG IDs. The deciding source is the seller’s technical manual or release note (grade C). It establishes the documented behavior of the specified version; execution or accuracy has not been independently observed.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "Technical permission to match two nodes leaves individual consent, entitlement for other uses and downstream withdrawal open.",
  "final_wording": "Blockgraph’s v2.29 Universe Match workflow lists partners that granted permission and specifies a downloadable file containing one column of Blockgraph IDs.",
  "counterevidence": "Technical permission to match two nodes leaves individual consent, entitlement for other uses and downstream withdrawal open.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F11",
  "headline": false,
  "claim": "Kantar reported a greater-than-tenfold rise in its TV partner match rates after integrating Blockgraph’s IDoS.",
  "chapter": "3, 7",
  "source_ids": [
   "IDN-CTV-S07",
   "IDN-CTV-S17"
  ],
  "passage": "Kantar match rates with TV partners have increased over 10x",
  "support": [
   {
    "source_id": "IDN-CTV-S07",
    "passage": "Kantar match rates with TV partners have increased over 10x",
    "locator": "Opening release paragraphs, immediately after description of panel/client matching"
   }
  ],
  "scope_time": "Release 2022-11-01, baseline and follow-up periods undisclosed",
  "scope_geo": "North America publication; case sample geography undisclosed",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Kantar’s November 1 release reports more than ten times the prior rate in its integration with TV partners and notes direct matching of panel and client data. Neither absolute rate, test period, denominator nor correctness is provided. Blockgraph’s CEO later rounds the same result to tenfold. The Kantar release says over tenfold. The CEO’s rounded wording and his later November 7 article are not separate study results.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "Kantar and Blockgraph published the comparison without either absolute rate, counts, eligibility rules or a test of false links. Sample geography was not stated.",
  "final_wording": "Kantar reported that its match rates with TV partners rose to more than ten times their prior level after integrating Blockgraph’s IDoS. The partners disclosed neither absolute rate nor the eligible record counts.",
  "counterevidence": "Kantar and Blockgraph published the comparison without either absolute rate, counts, eligibility rules or a test of false links. Sample geography was not stated.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-CTV-F12",
  "headline": false,
  "claim": "Spectrum Reach describes a production workflow in which it supplies household TV exposure, Innovid supplies household website visits and Blockgraph performs the match.",
  "chapter": "1, 7, 8, 12",
  "source_ids": [
   "IDN-CTV-S08",
   "IDN-CTV-S09"
  ],
  "passage": "matching one household level ad exposure to one household level website visit",
  "support": [
   {
    "source_id": "IDN-CTV-S08",
    "passage": "matching one household level ad exposure to one household level website visit",
    "locator": "FAQ, What data sources power Spectrum Reach’s multiscreen attribution?"
   }
  ],
  "scope_time": "2024-03-07 article, FAQ as read 2026-11-11",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Spectrum says its set-top-box and streaming-device data supply household exposure, Innovid collects visits, and Blockgraph performs the household join. It sells reporting based on this workflow. This is evidence from a participating seller, not independently observed production performance.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "The join concerns the household. It does not identify which viewer visited, establish causal lift or validate the household edge.",
  "final_wording": "Spectrum Reach describes a production workflow in which it supplies household TV exposure, Innovid supplies household website visits and Blockgraph performs the match.",
  "counterevidence": "The join concerns the household. It does not identify which viewer visited, establish causal lift or validate the household edge.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F13",
  "headline": false,
  "claim": "Spectrum Reach’s showcase describes visits counted within seven days of a TV exposure in its multiscreen attribution workflow.",
  "chapter": "1, 7, 12, 13",
  "source_ids": [
   "IDN-CTV-S09",
   "IDN-CTV-S08"
  ],
  "passage": "within 7 days of a Traditional TV or STV ad exposure",
  "support": [
   {
    "source_id": "IDN-CTV-S09",
    "passage": "within 7 days of a Traditional TV or STV ad exposure",
    "locator": "Printed p. 240, Spectrum Reach, Measuring Multiscreen Attribution, fifth process column (Analytics show)."
   }
  ],
  "scope_time": "2025-02 showcase",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The Spectrum contribution on printed page 240 says reporting counted site visits within seven days of a traditional or streaming TV exposure. On Spectrum’s separate FAQ, seven concurrent days of input data before reporting is a different clock. Printed PDF page 240 was rendered and read because normal text extraction misdecodes its typeface.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "This is a post-exposure visit window. It does not establish household link expiry or accuracy.",
  "final_wording": "Spectrum Reach’s showcase describes visits counted within seven days of a TV exposure in its multiscreen attribution workflow.",
  "counterevidence": "This is a post-exposure visit window. It does not establish household link expiry or accuracy.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-CTV-F14",
  "headline": false,
  "claim": "Kochava reported updating its Blockgraph implementation for converged-TV measurement in its October 2023 product bulletin.",
  "chapter": "",
  "source_ids": [
   "IDN-CTV-S15"
  ],
  "passage": "updated its Blockgraph implementation to continue providing support for advanced measurement",
  "support": [
   {
    "source_id": "IDN-CTV-S15",
    "passage": "updated its Blockgraph implementation to continue providing support for advanced measurement",
    "locator": "BlockGraph for advanced convergent TV measurement, first paragraph"
   }
  ],
  "scope_time": "2023-10-25",
  "scope_geo": "US market context; geography of the cited implementation unspecified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Kochava’s October 25 bulletin reports updating its existing Blockgraph implementation for convergent TV measurement. It specifies that both advertising and publishing parties may elect this route; no universal integration, deployment count or outcome is reported.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "Kochava describes a participant-elected path. Availability of a historic integration does not give a current production customer count.",
  "final_wording": "Kochava reported updating its Blockgraph implementation for converged-TV measurement in its October 2023 product bulletin.",
  "counterevidence": "Kochava describes a participant-elected path. Availability of a historic integration does not give a current production customer count.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F15",
  "headline": false,
  "claim": "The August 2026 release added SHA256-hashed email as a preset signal for identity upload, batch resolution and other workflows.",
  "chapter": "7",
  "source_ids": [
   "IDN-CTV-S10",
   "IDN-VCTV-S02"
  ],
  "passage": "SHA256 hashed email (HEM) is now available as a preset identity signal.",
  "support": [
   {
    "source_id": "IDN-CTV-S10",
    "passage": "SHA256 hashed email (HEM) is now available as a preset identity signal.",
    "locator": "Release 2.29, HEM as an Identity Signal"
   }
  ],
  "scope_time": "2026-08",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Release 2.29 is marked August 2026. It introduces pre-hashed SHA256 email as a preset option for identity upload, segment creation, batch identity resolution and measurement data processing. Later release 3.0.0 does not change this historical introduction date. The deciding source is the seller’s technical manual or release note (grade C). It establishes the documented behavior of the specified version; execution or accuracy has not been independently observed.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "This changes supported input. The record reports neither additional accepted households nor a measured reduction in error.",
  "final_wording": "The August 2026 release added SHA256-hashed email as a preset signal for identity upload, batch resolution and other workflows.",
  "counterevidence": "This changes supported input. The record reports neither additional accepted households nor a measured reduction in error.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F16",
  "headline": false,
  "claim": "An April 2025 CIMM report describes an IDoS footprint above 130 million households without specifying the active-period count, deduplication procedure or US eligible base for that figure.",
  "chapter": "7",
  "source_ids": [
   "IDN-CTV-S19"
  ],
  "passage": "across 130M+ households for converged TV",
  "support": [
   {
    "source_id": "IDN-CTV-S19",
    "passage": "across 130M+ households for converged TV",
    "locator": "Printed p. 26, section 3 Addressability, Blockgraph bullet at left."
   }
  ],
  "scope_time": "2025-04 publication; underlying counting period unspecified",
  "scope_geo": "US market report; geography of the reported 130M+ households unspecified",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "Printed page 26 of CIMM’s April 2025 report describes use across 130M+ households. It gives no study, cited census, deduplication rule, national eligible universe or counting period for the number. Neither current reachable US households nor accuracy follows. CIMM’s descriptive report supplies a figure with no identified underlying count or named source in this bullet. Use synthesis for the report plus the disclosure check; retain a D-grade footprint claim. Single-column raw PDF text and the page layout place 130M+ in the same Blockgraph bullet.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The number is present on page 26; its original provenance, period and population are not reported.",
  "limitations": "The geography of the numerical base is not expressly defined in the bullet. The number cannot be substituted for unique US households addressable for a given buyer.",
  "final_wording": "An April 2025 CIMM report describes IDoS as operating across 130 million-plus households. It gives no geography, active period, deduplication rule or eligible household base for that figure.",
  "counterevidence": "The geography of the numerical base is not expressly defined in the bullet. The number cannot be substituted for unique US households addressable for a given buyer.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F17",
  "headline": false,
  "claim": "Blockgraph’s 2021 notice directs clients’ customers to the client and describes assistance with removal or amendment at the client’s direction.",
  "chapter": "",
  "source_ids": [
   "IDN-CTV-S01"
  ],
  "passage": "only do so at the direction of the client",
  "support": [
   {
    "source_id": "IDN-CTV-S01",
    "passage": "only do so at the direction of the client",
    "locator": "Section 6, Our Role as a Service Provider and Processor to Our Clients"
   }
  ],
  "scope_time": "Effective 2021-01-21",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "Section 6 explicitly concerns data received from clients. It directs a customer seeking to stop contact back to the client. If that client requests help removing or amending its data, Blockgraph will cooperate under its contract. No deadline or automatic signal propagation is specified.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "The policy does not set a household deletion deadline or confirm recall of copies already exported.",
  "final_wording": "Blockgraph’s 2021 notice directs customers seeking to stop contact to the client they deal with and says Blockgraph will assist with removing or amending client data at that client’s direction under its contract.",
  "counterevidence": "The policy does not set a household deletion deadline or confirm recall of copies already exported.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F18",
  "headline": false,
  "claim": "Blockgraph’s CEO gave a broad match-rate definition in the commentary about Kantar, without specifying how that case counted eligible or matched records.",
  "chapter": "7",
  "source_ids": [
   "IDN-CTV-S17",
   "IDN-CTV-S07"
  ],
  "passage": "the percentage of a marketer’s audience data that can be tied to its media buys",
  "support": [
   {
    "source_id": "IDN-CTV-S17",
    "passage": "the percentage of a marketer’s audience data that can be tied to its media buys",
    "locator": "Opening discussion, immediately before The Match Rate Breakthrough"
   }
  ],
  "scope_time": "2022-11-07",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "The CEO defines match rate generically as the share of a marketer’s audience data linkable to media purchases. Neither his account nor the original Kantar release says how Kantar counted eligible records or matched households. The accounts describe one relationship.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "The definition does not identify whether Kantar counted submitted rows, distinct households or eligible panel records. It is a second account of the same partnership.",
  "final_wording": "Blockgraph’s CEO gave a broad match-rate definition in the commentary about Kantar, without specifying how that case counted eligible or matched records.",
  "counterevidence": "The definition does not identify whether Kantar counted submitted rows, distinct households or eligible panel records. It is a second account of the same partnership.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-CTV-F19",
  "headline": false,
  "claim": "Spectrum Reach claims a 95% addressable match rate for its own MVPD service in its multiscreen-attribution FAQ.",
  "chapter": "7",
  "source_ids": [
   "IDN-CTV-S08"
  ],
  "passage": "Spectrum Reach’s addressable match rate is 95%",
  "support": [
   {
    "source_id": "IDN-CTV-S08",
    "passage": "Spectrum Reach’s addressable match rate is 95%",
    "locator": "FAQ, How accurate is multiscreen attribution and what are its limitations?"
   }
  ],
  "scope_time": "FAQ accessed 2026-11-11; calculation period unspecified",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Spectrum’s FAQ attributes 95% to its own MVPD addressable match rate. It omits the denominator, base counts, period, sampling rule and an independent truth test. The percentage does not attach to customers across Blockgraph’s network.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "Neither a graph-wide rate for IDoS nor an independent person/household accuracy result is established by this scope.",
  "final_wording": "Spectrum Reach claims a 95% addressable match rate for its own MVPD service in its multiscreen-attribution FAQ.",
  "counterevidence": "Neither a graph-wide rate for IDoS nor an independent person/household accuracy result is established by this scope.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-CTV-F20",
  "headline": false,
  "claim": "Spectrum Reach describes its first-party multiscreen data as coming from over 30 million households.",
  "chapter": "7",
  "source_ids": [
   "IDN-CTV-S08"
  ],
  "passage": "from over 30 million households",
  "support": [
   {
    "source_id": "IDN-CTV-S08",
    "passage": "from over 30 million households",
    "locator": "FAQ, What data sources power Spectrum Reach’s multiscreen attribution?"
   }
  ],
  "scope_time": "FAQ accessed 2026-11-11; counting period unspecified",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Spectrum’s FAQ attributes its set-top-box and connected-streaming-device input to more than 30 million households. Collection footprint is upstream of attribution and matching. No IDoS unique eligible or reached population is given.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "This is Spectrum’s input footprint. The claim gives no share that subsequently matched Blockgraph household IDs and no national eligible base.",
  "final_wording": "Spectrum Reach describes its first-party multiscreen data as coming from over 30 million households.",
  "counterevidence": "This is Spectrum’s input footprint. The claim gives no share that subsequently matched Blockgraph household IDs and no national eligible base.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-CTV-F21",
  "headline": false,
  "claim": "A complete manual refresh in version 2.29 replaces the node’s identity layer and omits records absent from the replacement file.",
  "chapter": "abstract, 7, 12, 13",
  "source_ids": [
   "IDN-CTV-S12"
  ],
  "passage": "replaces the entire identity layer",
  "support": [
   {
    "source_id": "IDN-CTV-S12",
    "passage": "replaces the entire identity layer",
    "locator": "Manual Identity Upload, Refresh of Identity Data"
   }
  ],
  "scope_time": "Release 2.29, 2026-08",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "A complete v2.29 manual refresh replaces the whole identity layer. Records absent from the new file are removed; users can run the refresh at any time. It is distinct from the separate Delete and Opt Out actions. The deciding source is the seller’s technical manual or release note (grade C). It establishes the documented behavior of the specified version; execution or accuracy has not been independently observed.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source identifies the named actor and its own reported rule or result. The scope and limits are recorded alongside the claim.",
  "limitations": "A client can trigger a refresh at any time. No mandatory maximum age for accepted links is given by this event-driven operation.",
  "final_wording": "A complete manual refresh in version 2.29 replaces the node’s identity layer and omits records absent from the replacement file.",
  "counterevidence": "A client can trigger a refresh at any time. No mandatory maximum age for accepted links is given by this event-driven operation.",
  "stream": "blockgraph",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H5"
 },
 {
  "id": "IDN-EXP-F01",
  "headline": false,
  "claim": "Experian offers its US Digital Graph as a whole dataset or as links appended to a buyer’s own records.",
  "chapter": "1, 8, 11, 12",
  "source_ids": [
   "IDN-U-S17"
  ],
  "passage": "[IDN-U-S17, FAQ, How do I get started with Digital Graph?, second step. See Define for the full-graph license.] as a full dataset or appended to your own records [IDN-U-S17, Digital Graph, rendered line 49 (locate by quoted text)] U.S. Digital Graph",
  "support": [
   {
    "source_id": "IDN-U-S17",
    "passage": "as a full dataset or appended to your own records",
    "locator": "FAQ, How do I get started with Digital Graph?, second step. See Define for the full-graph license."
   },
   {
    "source_id": "IDN-U-S17",
    "passage": "U.S. Digital Graph",
    "locator": "Digital Graph, rendered line 49 (locate by quoted text)"
   }
  ],
  "scope_time": "As read 2026-11-11",
  "scope_geo": "US Digital Graph",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Define and the FAQ offer a full license or an append to the customer’s records. The adjacent image headings expressly identify the US edition. The seller provides a contact route, with no fixed price or signed contract. US offer at cutoff. A public offer does not establish every buyer’s entitlement.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "Public sales contact and delivery options establish a buying route. The landing page gives no price, contract or entitlement by platform.",
  "final_wording": "Experian offers its US Digital Graph as a whole dataset or as links appended to a buyer’s own records.",
  "counterevidence": "Public sales contact and delivery options establish a buying route. The landing page gives no price, contract or entitlement by platform.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F02",
  "headline": false,
  "claim": "Experian markets a separate Offline Graph for names, addresses and emails, and a joint offering pairs Digital Graph with Marketing Attributes.",
  "chapter": "1, 8",
  "source_ids": [
   "IDN-EXP-S11",
   "IDN-EXP-S12"
  ],
  "passage": "[IDN-EXP-S11, Connect offline data with reliable identity resolution. See How to use Offline Graph for separately licensed products.] Offline Graph connects names, addresses, and emails to persistent IDs [IDN-EXP-S12, Product sheet, p. 1, middle panel. The two columns separate identifiers from descriptive attributes.] Digital Graph and Marketing Attributes joint solution provides",
  "support": [
   {
    "source_id": "IDN-EXP-S11",
    "passage": "Offline Graph connects names, addresses, and emails to persistent IDs",
    "locator": "Connect offline data with reliable identity resolution. See How to use Offline Graph for separately licensed products."
   },
   {
    "source_id": "IDN-EXP-S12",
    "passage": "Digital Graph and Marketing Attributes joint solution provides",
    "locator": "Product sheet, p. 1, middle panel. The two columns separate identifiers from descriptive attributes."
   }
  ],
  "scope_time": "Joint product sheet ©2024 and current Offline Graph offer read 2026-11-11.",
  "scope_geo": "US Digital Graph",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The Offline Graph page names names, addresses and emails as source identifiers. The joint product sheet places Digital Graph IDs and descriptive Marketing Attributes in separate columns. These sources do not show an entitlement to offline records or attributes in a standalone Digital Graph license. The source supports the attributed statement at this scope.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "The product portfolio supports offline onboarding and audience enrichment. Those functions and data assets are not automatically entitled by a license to Digital Graph alone.",
  "final_wording": "Experian markets a separate Offline Graph for names, addresses and emails, and a joint offering pairs Digital Graph with Marketing Attributes.",
  "counterevidence": "The product portfolio supports offline onboarding and audience enrichment. Those functions and data assets are not automatically entitled by a license to Digital Graph alone.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-EXP-F03",
  "headline": false,
  "claim": "Experian says it clusters digital identifiers into household or individual links using signals that include timing, IP addresses and browser or device identifiers.",
  "chapter": "1, 11",
  "source_ids": [
   "IDN-EXP-S14",
   "IDN-U-S17"
  ],
  "passage": "[IDN-EXP-S14, What is Experian’s Digital Graph?, paragraph on clustering algorithms and model inputs.] timestamps, IP addresses, user agents, cookie IDs, and device identifiers [IDN-U-S17, Digital Graph, rendered line 93 (locate by quoted text)] connect identifiers at the household or individual level",
  "support": [
   {
    "source_id": "IDN-EXP-S14",
    "passage": "timestamps, IP addresses, user agents, cookie IDs, and device identifiers",
    "locator": "What is Experian’s Digital Graph?, paragraph on clustering algorithms and model inputs."
   },
   {
    "source_id": "IDN-U-S17",
    "passage": "connect identifiers at the household or individual level",
    "locator": "Digital Graph, rendered line 93 (locate by quoted text)"
   }
  ],
  "scope_time": "October 1, 2025 methodology description and product page read 2026-11-11.",
  "scope_geo": "US Digital Graph",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The product page lets buyers choose household or individual resolution. The 2025 post describes clustering observed timestamps, IP addresses, user agents, cookies and device IDs. It gives no acceptance threshold, truth labels, conflict logic or separate accuracy for either level. The source supports the attributed statement at this scope.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "The model uses observations about devices. The public account supplies neither the acceptance threshold nor a way to validate a specific link. No person’s identity is confirmed by an IP alone.",
  "final_wording": "Experian says it clusters digital identifiers into household or individual links using signals that include timing, IP addresses and browser or device identifiers.",
  "counterevidence": "The model uses observations about devices. The public account supplies neither the acceptance threshold nor a way to validate a specific link. No person’s identity is confirmed by an IP alone.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-EXP-F04",
  "headline": false,
  "claim": "Experian says an unnamed DSP synced its cookies and received a weekly graph file linking them to cookies, mobile ad IDs, CTV IDs and IP addresses.",
  "chapter": "13",
  "source_ids": [
   "IDN-EXP-S01",
   "IDN-EXP-S14"
  ],
  "passage": "[IDN-EXP-S01, Case PDF, printed p. 3, Solution, first sentence and returned-ID list.] The DSP used Graph to sync their cookies to Experian's digital IDs. [IDN-EXP-S01, Case PDF, printed p. 3, Solution, last sentence.] we deliver an updated Graph file to this DSP weekly.",
  "support": [
   {
    "source_id": "IDN-EXP-S01",
    "passage": "The DSP used Graph to sync their cookies to Experian's digital IDs.",
    "locator": "Case PDF, printed p. 3, Solution, first sentence and returned-ID list."
   },
   {
    "source_id": "IDN-EXP-S01",
    "passage": "we deliver an updated Graph file to this DSP weekly.",
    "locator": "Case PDF, printed p. 3, Solution, last sentence."
   }
  ],
  "scope_time": "Case described October 1, 2025. The PDF does not identify the service interval.",
  "scope_geo": "Customer engagement. Sample geography undisclosed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The anonymous customer’s PDF names its cookies as the sync input. It lists Experian cookies, MAIDs, CTV IDs and IPs returned and weekly file delivery. The issuer’s companion post confirms the description. Neither identifies the cookie setting in the browser, the DSP, the country, the physical file schema or edge lifetime. Apply the route only to this example. The recipient_interface field incorrectly identified the input as first-party.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "One working recipient route is described. The customer remains unnamed and the public material does not supply a file schema or edge-age rule.",
  "final_wording": "Experian says an unnamed DSP synced its cookies and received a weekly graph file linking them to cookies, mobile ad IDs, CTV IDs and IP addresses.",
  "counterevidence": "One working recipient route is described. The customer remains unnamed and the public material does not supply a file schema or edge-age rule.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F05",
  "headline": false,
  "claim": "Experian says it rebuilds Digital Graph weekly and has added IPv6 and phone-based UID2 identifiers.",
  "chapter": "11, 12",
  "source_ids": [
   "IDN-EXP-S03"
  ],
  "passage": "[IDN-EXP-S03, Which alternative IDs does Experian’s Digital Graph support?, paragraph after the list.] Our Digital Graph is rebuilt weekly [IDN-EXP-S03, How is Experian’s Digital Graph evolving in a multi-signal world?, first bullet.] We added IPv6 and phone-based UID2s to our Digital Graph",
  "support": [
   {
    "source_id": "IDN-EXP-S03",
    "passage": "Our Digital Graph is rebuilt weekly",
    "locator": "Which alternative IDs does Experian’s Digital Graph support?, paragraph after the list."
   },
   {
    "source_id": "IDN-EXP-S03",
    "passage": "We added IPv6 and phone-based UID2s to our Digital Graph",
    "locator": "How is Experian’s Digital Graph evolving in a multi-signal world?, first bullet."
   }
  ],
  "scope_time": "Issuer article updated October 20, 2026. Original article June 13, 2024.",
  "scope_geo": "US Digital Graph",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The product article explicitly calls its Digital Graph a weekly rebuild and says it added IPv6 and phone-based UID2s as well as email-based UID2s previously supported. Its masthead says updated October 20, 2026, originally June 13, 2024. This does not date the individual rollouts or set a link expiry. The source supports the attributed statement at this scope.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "The article supplies the weekly rebuild interval and labels the identifiers as additions. It omits individual link decay, effective rollout dates, recipient versioning and a migration rule.",
  "final_wording": "Experian says it rebuilds Digital Graph weekly and has added IPv6 and phone-based UID2 identifiers.",
  "counterevidence": "The article supplies the weekly rebuild interval and labels the identifiers as additions. It omits individual link decay, effective rollout dates, recipient versioning and a migration rule.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F06",
  "headline": false,
  "claim": "Experian says MiQ licensed hashed emails, UID2s and partner cookies for its Identity Spine, which its traders and analysts use for targeting and measurement.",
  "chapter": "3, 8",
  "source_ids": [
   "IDN-C-S06",
   "IDN-VEXP-S01"
  ],
  "passage": "[IDN-C-S06, p. 4, Solution] MiQ incorporated Experian’s Digital Graph, licensing HEMs, UID2s, and third-party partner cookies [IDN-C-S06, Case PDF, printed p. 4, Solution, numbered uses below the licensed IDs.] MiQ traders and analysts use Experian data",
  "support": [
   {
    "source_id": "IDN-C-S06",
    "passage": "MiQ incorporated Experian’s Digital Graph, licensing HEMs, UID2s, and third-party partner cookies",
    "locator": "p. 4, Solution"
   },
   {
    "source_id": "IDN-C-S06",
    "passage": "MiQ traders and analysts use Experian data",
    "locator": "Case PDF, printed p. 4, Solution, numbered uses below the licensed IDs."
   }
  ],
  "scope_time": "MiQ case available by the cutoff. Experiment dates undisclosed.",
  "scope_geo": "Customer engagement. Sample geography undisclosed.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The PDF reports that MiQ licensed HEMs, UID2s and third-party partner cookies. MiQ itself confirms putting Experian’s IDs into its multi-source Identity Spine and describes traders’ and analysts’ audience and measurement uses. Neither report locates the tested data in the US or establishes paid transaction counts. The buyer supplies first-hand implementation evidence but is commercially interested. Count this as one customer engagement.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "The seller names a recipient and its uses. The case does not identify a US-only implementation or a count of distinct US-supported destinations.",
  "final_wording": "Experian says MiQ licensed hashed emails, UID2s and partner cookies for its Identity Spine, which its traders and analysts use for targeting and measurement.",
  "counterevidence": "The seller names a recipient and its uses. The case does not identify a US-only implementation or a count of distinct US-supported destinations.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F07",
  "headline": false,
  "claim": "Experian reports a 70% match rate from MiQ-supplied IP addresses to cookieless identifiers in the MiQ engagement.",
  "chapter": "3",
  "source_ids": [
   "IDN-C-S05",
   "IDN-C-S06"
  ],
  "passage": "70% match rate between MiQ-provided IP addresses and cookieless IDs",
  "support": [
   {
    "source_id": "IDN-C-S05",
    "passage": "70% match rate between MiQ-provided IP addresses and cookieless IDs",
    "locator": "Case study resources, “Experian’s Graph increases reach and scale: Case study with MiQ”, descriptive paragraph (line 218)."
   }
  ],
  "scope_time": "MiQ case read 2026-11-11. Observation window undisclosed.",
  "scope_geo": "Customer engagement. Sample geography undisclosed.",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The seller’s MiQ directory entry identifies the direction of matching and 70%. Page 5 of the full case reports the same rate. Neither supplies submitted or eligible record counts, selection rules, test dates or a geography-specific denominator. The named customer independently describes use, not a labeled audit or the 70% rate. This is a seller-reported match yield. The 6.5 devices per matched IP has a different base, and 51% and 64% reach changes have different units.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "The input class and direction are public. Eligible versus submitted IPs, the count, repeat observations, exclusions and acceptance rule are unspecified. The percentage measures linkage yield, not correctness.",
  "final_wording": "Experian reports a 70% match rate from MiQ-supplied IP addresses to cookieless identifiers in the MiQ engagement.",
  "counterevidence": "The input class and direction are public. Eligible versus submitted IPs, the count, repeat observations, exclusions and acceptance rule are unspecified. The percentage measures linkage yield, not correctness.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "Seller case for a programmatic partner. Input is MiQ IPs and output is cookieless IDs. No published holdout, ground truth, or raw row counts.",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-EXP-F08",
  "headline": false,
  "claim": "Experian says the unnamed DSP synced 84% of IDs within weeks of using its Digital Graph.",
  "chapter": "13",
  "source_ids": [
   "IDN-EXP-S14",
   "IDN-EXP-S01"
  ],
  "passage": "84% of IDs synced",
  "support": [
   {
    "source_id": "IDN-EXP-S14",
    "passage": "84% of IDs synced",
    "locator": "Results, Within weeks, the DSP saw measurable improvements, first bullet."
   }
  ],
  "scope_time": "October 1, 2025 report. Exact start and finish not stated.",
  "scope_geo": "Customer engagement. Sample geography undisclosed.",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The October 2025 Results section reports within weeks 84% of IDs synced. The same case’s slide deck labels 84% synced IDs and separately reports a 9% match-rate increase. Neither defines the eligible denominator, baseline, relative/percentage-point treatment, ground truth or sampling error. One unnamed DSP case, reported twice. Accuracy language in the headlines is not a measured rate of correct links.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "The report does not identify the precise eligible ID base, counts, exclusions or decision threshold for that figure. A synced ID alone does not establish a correct person or household link.",
  "final_wording": "Experian says the unnamed DSP synced 84% of IDs within weeks of using its Digital Graph.",
  "counterevidence": "The report does not identify the precise eligible ID base, counts, exclusions or decision threshold for that figure. A synced ID alone does not establish a correct person or household link.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "Unnamed DSP case described by Experian. Cookie sync followed by graph delivery. No controlled evaluation of correct vs incorrect links.",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-EXP-F09",
  "headline": false,
  "claim": "Experian advertises 250 million individuals in its US Digital Graph.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S17",
   "IDN-EXP-S02"
  ],
  "passage": "[IDN-U-S17, US Digital Graph, third counter image and adjacent caption “individuals in our” above the efficiency section.] 250 million [IDN-EXP-S02, Product sheet, p. 1, Expansive reach and scale, individuals row.] 250M individuals",
  "support": [
   {
    "source_id": "IDN-U-S17",
    "passage": "250 million",
    "locator": "US Digital Graph, third counter image and adjacent caption “individuals in our” above the efficiency section."
   },
   {
    "source_id": "IDN-EXP-S02",
    "passage": "250M individuals",
    "locator": "Product sheet, p. 1, Expansive reach and scale, individuals row."
   }
  ],
  "scope_time": "Current product counters read 2026-11-11. Sheet bears 2025 copyright.",
  "scope_geo": "US Digital Graph",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The US landing-page image and heading show 250 million individuals represented. The 2025 sheet lists 250M individuals. No counting period, active-use criterion, edge count or deduplication rule accompanies the claim. The landing page separately reports 4.2bn IDs and 300m CTV IDs. The 2025 sheet reports 275m CTV IDs. Do not blend these undated bases. US geography derives from the web page. The sheet does not independently label its country. The figure is an advertised quantity, not reach in a period.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "The US product page gives a graph count, with no count date, deduplication rule, eligible US population or active-in-period definition. A percentage of the US population cannot be inferred.",
  "final_wording": "Experian advertises 250 million individuals in its US Digital Graph.",
  "counterevidence": "The US product page gives a graph count, with no count date, deduplication rule, eligible US population or active-in-period definition. A percentage of the US population cannot be inferred.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F10",
  "headline": false,
  "claim": "Experian’s US privacy notice says an opt-out signal in covered states attaches to the browser identifier unless it is already linked to other personal information.",
  "chapter": "",
  "source_ids": [
   "IDN-EXP-S04"
  ],
  "passage": "Your request to opt-out will be linked to your browser identifier only, unless it is already linked to other personal information.",
  "support": [
   {
    "source_id": "IDN-EXP-S04",
    "passage": "Your request to opt-out will be linked to your browser identifier only, unless it is already linked to other personal information.",
    "locator": "Opt-Out Preference Signals, after discussion of GPC in certain states. See opening scope and section 5 for service-provider data."
   }
  ],
  "scope_time": "Notice updated June 24, 2026.",
  "scope_geo": "US. Certain states within the scope of the notice.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The notice updated June 24 says a GPC preference can opt out of sale, sharing and targeted advertising in certain states. It binds to the browser identifier unless already linked to other personal information. The notice covers named Experian entities and separately discusses client-controlled processing. It reports no Digital Graph recipient execution. Evidence of a published policy. Do not use this as an affirmative permission signal, legal-basis finding or measured suppression time.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named primary record directly establishes the scoped event or amount.",
  "limitations": "The notice includes Experian Marketing Solutions, LLC and other entities. It does not show a Digital Graph permission field, a missing-signal default, recipient suppression or withdrawal timing on a graph license.",
  "final_wording": "Experian’s US privacy notice says an opt-out signal in covered states attaches to the browser identifier unless it is already linked to other personal information.",
  "counterevidence": "The notice includes Experian Marketing Solutions, LLC and other entities. It does not show a Digital Graph permission field, a missing-signal default, recipient suppression or withdrawal timing on a graph license.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F11",
  "headline": false,
  "claim": "Tapad’s own Graph notice says it permanently opts out a submitted identifier and can remove related identifiers for 60 days, subject to reassessment of the link.",
  "chapter": "",
  "source_ids": [
   "IDN-EXP-S13"
  ],
  "passage": "[IDN-EXP-S13, 2. Offer Meaningful Choice, paragraph beginning When you opt out via one Identifier.] that Identifier will be opted out in perpetuity. [IDN-EXP-S13, IP Address Opt-out, first sentence. For related devices see 2. Offer Meaningful Choice, immediately after the permanent opt-out paragraph.] Tapad will opt-out the IP address registered for the twelve (12) months",
  "support": [
   {
    "source_id": "IDN-EXP-S13",
    "passage": "that Identifier will be opted out in perpetuity.",
    "locator": "2. Offer Meaningful Choice, paragraph beginning When you opt out via one Identifier."
   },
   {
    "source_id": "IDN-EXP-S13",
    "passage": "Tapad will opt-out the IP address registered for the twelve (12) months",
    "locator": "IP Address Opt-out, first sentence. For related devices see 2. Offer Meaningful Choice, immediately after the permanent opt-out paragraph."
   }
  ],
  "scope_time": "Privacy notice updated June 24, 2026.",
  "scope_geo": "Tapad’s Graph, US included.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "Tapad distinguishes a submitted identifier already in its Graph from other identifiers it associates with it. Related IDs can reenter if the link is reassessed. The IP-specific section limits an IPv4 opt-out to 12 months. A cleared browser cookie can require another opt-out. Clients are instructed to discard removed IDs on receipt of refreshed data. No per-recipient timing is reported. These are Tapad’s stated rules. Client obligations, performed deletions and US Digital Graph license terms are distinct.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named primary record directly establishes the scoped event or amount.",
  "limitations": "This rule is expressly scoped to Tapad’s products and probabilistic associations. The sources reviewed do not state that each US Experian Digital Graph file or buyer inherits these rules.",
  "final_wording": "Tapad’s Graph notice describes permanent opt-out for an identifier already in its graph and conditional 60-day suppression of related device IDs. It specifies 12 months for a registered IPv4 address.",
  "counterevidence": "This rule is expressly scoped to Tapad’s products and probabilistic associations. The sources reviewed do not state that each US Experian Digital Graph file or buyer inherits these rules.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F12",
  "headline": false,
  "claim": "After Experian announced Snowflake clean-room access in 2024, Snowflake removed its Experian connector from the legacy provider and consumer web interface in September 2026 while preserving existing configurations.",
  "chapter": "",
  "source_ids": [
   "IDN-EXP-S07",
   "IDN-EXP-S06",
   "IDN-VEXP-S02"
  ],
  "passage": "[IDN-EXP-S07, September 18, 2024, opening paragraph.] collaboration in Snowflake Data Clean Rooms using Experian’s offline or digital graph is now generally available [IDN-EXP-S06, September 10, 2026 notes, Clean Rooms API Version 18.2, Legacy identity connectors removed.] Experian, and The Trade Desk UID 2.0 connectors have been removed from the provider and consumer web interface. [IDN-EXP-S06, Same release-note bullet, final sentence.] does not delete existing connector configurations.",
  "support": [
   {
    "source_id": "IDN-EXP-S07",
    "passage": "collaboration in Snowflake Data Clean Rooms using Experian’s offline or digital graph is now generally available",
    "locator": "September 18, 2024, opening paragraph."
   },
   {
    "source_id": "IDN-EXP-S06",
    "passage": "Experian, and The Trade Desk UID 2.0 connectors have been removed from the provider and consumer web interface.",
    "locator": "September 10, 2026 notes, Clean Rooms API Version 18.2, Legacy identity connectors removed."
   },
   {
    "source_id": "IDN-EXP-S06",
    "passage": "does not delete existing connector configurations.",
    "locator": "Same release-note bullet, final sentence."
   }
  ],
  "scope_time": "September 18, 2024 access announcement and September 10, 2026 interface update.",
  "scope_geo": "Snowflake Data Clean Rooms, legacy UI.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "The vendor announced generally available offline/digital collaboration in September 2024. Snowflake’s September 10, 2026 note specifically removes Experian from both legacy web interfaces without deleting configurations in that release. Snowflake’s dated end-of-life schedule separately blocked new legacy rooms in the web app on October 1 and scheduled later retirements. There is no confirmation here of transactions in a saved setup, Experian connector support in the replacement API, or termination of directly licensed graph delivery.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "The release concerns the legacy interface alone. It does not retire direct graph licensing, prove use of any remaining configuration or establish a US buyer count.",
  "final_wording": "Experian announced Snowflake clean-room access in 2024. On September 10, 2026, Snowflake removed the Experian connector from its legacy web interface without deleting existing configurations. From October 1, the web app could no longer create new legacy rooms.",
  "counterevidence": "The release concerns the legacy interface alone. It does not retire direct graph licensing, prove use of any remaining configuration or establish a US buyer count.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F13",
  "headline": false,
  "claim": "Experian’s account of Truthset’s Q1 2026 results describes its hashed-email data and marketing attributes.",
  "chapter": "",
  "source_ids": [
   "IDN-EXP-S10"
  ],
  "passage": "[IDN-EXP-S10, Experian’s commitment to data accuracy, Q1 2026 results, first bullet.] largest volume of high-accuracy hashed emails [IDN-EXP-S10, Same section, second bullet.] accuracy for ten marketing data attributes",
  "support": [
   {
    "source_id": "IDN-EXP-S10",
    "passage": "largest volume of high-accuracy hashed emails",
    "locator": "Experian’s commitment to data accuracy, Q1 2026 results, first bullet."
   },
   {
    "source_id": "IDN-EXP-S10",
    "passage": "accuracy for ten marketing data attributes",
    "locator": "Same section, second bullet."
   }
  ],
  "scope_time": "Q1 2026 results as characterized in October 2026 article.",
  "scope_geo": "Seller’s marketing datasets. Graph edge, evaluation cohort and US stratum not specified.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The article calls Experian part of the Truthset Data Collective and reports an email-volume ranking and accuracy rankings for ten marketing attributes in Q1 2026. Those targets are not independently labeled person-to-device or household-to-device edges from the named Digital Graph. No separate edge-specific sample or current product score is supplied. Vendor assertion about a named evaluator’s work. An evaluator name does not make this independent measurement of the Digital Graph.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "The report does not give separately labeled device-to-person or device-to-household edges for the named US Digital Graph. A ranking of demographic attributes is a different test.",
  "final_wording": "Experian’s account of Truthset’s Q1 2026 results describes its hashed-email data and marketing attributes.",
  "counterevidence": "The report does not give separately labeled device-to-person or device-to-household edges for the named US Digital Graph. A ranking of demographic attributes is a different test.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "Seller account of Truthset’s dataset rankings. No identified Digital Graph edge sample, count, labels, accuracy metric or funding disclosure for such an evaluation.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-EXP-F14",
  "headline": false,
  "claim": "Tapad reported that its Device Graph had twice the precision of the next competitor in a 2016 Hotels.com evaluation.",
  "chapter": "3",
  "source_ids": [
   "IDN-B-S05",
   "IDN-VEXP-S03"
  ],
  "passage": "Tapad achieved twice the precision of the next highest-scoring cross-screen offering",
  "support": [
   {
    "source_id": "IDN-B-S05",
    "passage": "Tapad achieved twice the precision of the next highest-scoring cross-screen offering",
    "locator": "Opening paragraph, New York, September 14, 2016"
   }
  ],
  "scope_time": "September 14, 2016 publication.",
  "scope_geo": "Historical case. Evaluation geography unspecified.",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The 2016 issuer report describes Hotels.com’s three-and-a-half-month comparison with two unnamed rivals and a twofold precision result relative to the next-highest offering. There is no absolute precision, holdout construction, sample size or known financial sponsor. Experian acquired Tapad in November 2020. Historical commercial-buyer comparison reported by the winner. It does not validate the later US Digital Graph.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "The three-way buyer evaluation described by the winning vendor reports a relative comparison, no absolute precision or current Digital Graph version. It does not validate the US Digital Graph in 2026.",
  "final_wording": "Tapad reported that its Device Graph had twice the precision of the next competitor in a 2016 Hotels.com evaluation.",
  "counterevidence": "The three-way buyer evaluation described by the winning vendor reports a relative comparison, no absolute precision or current Digital Graph version. It does not validate the US Digital Graph in 2026.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "Seller report of a three-and-a-half-month comparison for Hotels.com. Two competitors unnamed. Construction of truth labels and sample size not supplied.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-EXP-F15",
  "headline": false,
  "claim": "The Digital Graph sheet credits Experian Marketing Services, Inc., while the US marketing data-practices notice names Experian Marketing Solutions, LLC.",
  "chapter": "8",
  "source_ids": [
   "IDN-EXP-S02",
   "IDN-EXP-S05",
   "IDN-EXP-S08"
  ],
  "passage": "[IDN-EXP-S02, Digital Graph product sheet, p. 1, copyright attribution in footer.] Experian Marketing Services, Inc. [IDN-EXP-S05, US marketing data-practices notice, opening section.] About Experian Marketing Solutions, LLC",
  "support": [
   {
    "source_id": "IDN-EXP-S02",
    "passage": "Experian Marketing Services, Inc.",
    "locator": "Digital Graph product sheet, p. 1, copyright attribution in footer."
   },
   {
    "source_id": "IDN-EXP-S05",
    "passage": "About Experian Marketing Solutions, LLC",
    "locator": "US marketing data-practices notice, opening section."
   }
  ],
  "scope_time": "Sheet ©2025 and data-practices notice updated April 14, 2026.",
  "scope_geo": "US marketing business",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "The ©2025 Digital Graph sheet identifies Experian Marketing Services, Inc. The 2026 marketing-data notice names Experian Marketing Solutions, LLC. The plc annual report lists the latter and Tapad as distinct US subsidiaries. A product-sheet copyright, related undertaking and privacy-notice entity are insufficient to identify the signer of a specific US graph license. The source supports the attributed statement at this scope.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The cited text supports the attributed statement within the stated product and source boundaries.",
  "limitations": "A copyright owner and publisher of a notice can be identified from these documents. The source set does not include a signed US graph license naming its legal counterparty.",
  "final_wording": "The Digital Graph sheet credits Experian Marketing Services, Inc., while the US marketing data-practices notice names Experian Marketing Solutions, LLC.",
  "counterevidence": "A copyright owner and publisher of a notice can be identified from these documents. The source set does not include a signed US graph license naming its legal counterparty.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F16",
  "headline": false,
  "claim": "Experian plc, the group parent headquartered in Dublin, reports a London Stock Exchange listing under EXPN.",
  "chapter": "8",
  "source_ids": [
   "IDN-EXP-S08",
   "IDN-EXP-S09"
  ],
  "passage": "[IDN-EXP-S08, Notes to the Group financial statements, note 1, Corporate information.] Experian plc (the Company) is the ultimate parent company [IDN-EXP-S09, Full-year results for FY26, About Experian, final paragraph.] listed on the London Stock Exchange (EXPN) [IDN-EXP-S09, Same paragraph, after the global employee count.] Our corporate headquarters are in Dublin, Ireland.",
  "support": [
   {
    "source_id": "IDN-EXP-S08",
    "passage": "Experian plc (the Company) is the ultimate parent company",
    "locator": "Notes to the Group financial statements, note 1, Corporate information."
   },
   {
    "source_id": "IDN-EXP-S09",
    "passage": "listed on the London Stock Exchange (EXPN)",
    "locator": "Full-year results for FY26, About Experian, final paragraph."
   },
   {
    "source_id": "IDN-EXP-S09",
    "passage": "Our corporate headquarters are in Dublin, Ireland.",
    "locator": "Same paragraph, after the global employee count."
   }
  ],
  "scope_time": "Financial records for FY26. Status as read 2026-11-11.",
  "scope_geo": "Global group",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Note 1 identifies Experian plc as the ultimate parent. The results release identifies EXPN on the London Stock Exchange and the corporate headquarters in Dublin, Ireland. The annual report distinguishes the Jersey registered office. No product-level corporate fact is inferred. The source supports the attributed statement at this scope.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named primary record directly establishes the scoped event or amount.",
  "limitations": "The listing and headquarters belong to the parent. They do not establish the legal signer of a US Digital Graph license.",
  "final_wording": "Experian plc, the group parent headquartered in Dublin, reports a London Stock Exchange listing under EXPN.",
  "counterevidence": "The listing and headquarters belong to the parent. They do not establish the legal signer of a US Digital Graph license.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F17",
  "headline": false,
  "claim": "Experian plc reported worldwide statutory revenue of US$8,445 million for the year ended March 31, 2026.",
  "chapter": "8",
  "source_ids": [
   "IDN-EXP-S08",
   "IDN-EXP-S09"
  ],
  "passage": "Revenue 8,445 7,523",
  "support": [
   {
    "source_id": "IDN-EXP-S08",
    "passage": "Revenue 8,445 7,523",
    "locator": "Strategic report, Financial review, statutory results table, Revenue row, FY26 and FY25 columns (US$m)."
   }
  ],
  "scope_time": "Fiscal year ended March 31, 2026.",
  "scope_geo": "Global consolidated group",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The Financial review statutory table reports $8,445m for FY26 and $7,523m for FY25. The FY26 results release confirms a year ended March 31 and distinguishes $8,425m ongoing revenue from $8,445m statutory. Neither table separates US Digital Graph revenue. The source supports the attributed statement at this scope.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named primary record directly establishes the scoped event or amount.",
  "limitations": "Includes all group businesses. The financial review table does not break out Digital Graph revenue, US graph sales or market share.",
  "final_wording": "Experian plc reported worldwide statutory revenue of US$8,445 million for the year ended March 31, 2026.",
  "counterevidence": "Includes all group businesses. The financial review table does not break out Digital Graph revenue, US graph sales or market share.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-EXP-F18",
  "headline": false,
  "claim": "The UK Upper Tribunal dismissed the Commissioner’s appeal in April 2024, leaving a substituted notice covering certain open-source records used by Experian Limited for direct marketing.",
  "chapter": "9",
  "source_ids": [
   "IDN-H-S05",
   "IDN-H-S04",
   "IDN-VEXP-S04"
  ],
  "passage": "[IDN-H-S05, Decision date and Judicial Summary] Information Commissioner’s appeal dismissed. [IDN-H-S04, Judgment paragraph 47, substituted notice paragraphs 1–3, pp. 20–21 (printed)] their personal data has been obtained by Experian and is being processed by it for direct marketing purposes",
  "support": [
   {
    "source_id": "IDN-H-S05",
    "passage": "Information Commissioner’s appeal dismissed.",
    "locator": "Decision date and Judicial Summary"
   },
   {
    "source_id": "IDN-H-S04",
    "passage": "their personal data has been obtained by Experian and is being processed by it for direct marketing purposes",
    "locator": "Judgment paragraph 47, substituted notice paragraphs 1–3, pp. 20–21 (printed)"
   }
  ],
  "scope_time": "Decision April 22, 2024. Read 2026-11-11.",
  "scope_geo": "United Kingdom. Experian Limited.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The April 22 Upper Tribunal decision dismissed the ICO appeal. Paragraph 47 reproduces the FTT substitute notice for direct marketing from three public sources, subject to enumerated exceptions. The ICO confirmed on May 24 it would not pursue further appeal. Neither instrument identifies the US Digital Graph or demonstrates completed notice delivery. Legal record outside IQ. Public-register sourcing is distinct from digital open-source software. The order regulates Experian Limited in the UK.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The named primary record directly establishes the scoped event or amount.",
  "limitations": "Paragraph 47 defines the open sources and exclusions. The decision does not concern the US Digital Graph or prove subsequent compliance. This is a legal record outside IQ.",
  "final_wording": "The UK Upper Tribunal dismissed the Commissioner’s appeal in April 2024, leaving a substituted notice covering certain open-source records used by Experian Limited for direct marketing.",
  "counterevidence": "Paragraph 47 defines the open sources and exclusions. The decision does not concern the US Digital Graph or prove subsequent compliance. This is a legal record outside IQ.",
  "stream": "experian-resolution",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-ID5-F01",
  "headline": false,
  "claim": "As read on 11 November 2026, Companies House lists ID5 Technology Limited (10735438) as an active UK private limited company incorporated on 21 April 2017, with its registered office in London.",
  "chapter": "",
  "source_ids": [
   "IDN-ID5-S01"
  ],
  "passage": "Private limited Company",
  "support": [
   {
    "source_id": "IDN-ID5-S01",
    "passage": "Private limited Company",
    "locator": "Company type; adjacent Company status, company number, registered office and Incorporated on fields"
   }
  ],
  "scope_time": "2017-04-21; as of 2026-11-11",
  "scope_geo": "UK",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Company 10735438 is active, private, incorporated on April 21, 2017, registered at 8 Devonshire Square, London; the current register was read on the freeze date. The registry address does not settle the location of an operational headquarters.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer record states the scoped fact.",
  "limitations": "The registry address does not settle the location of an operational headquarters.",
  "final_wording": "As read on 11 November 2026, Companies House lists ID5 Technology Limited (10735438) as an active UK private limited company incorporated on 21 April 2017, with its registered office in London.",
  "counterevidence": "The registry address does not settle the location of an operational headquarters.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": ""
 },
 {
  "id": "IDN-ID5-F02",
  "headline": false,
  "claim": "The UK register names French ID5 Technology SAS as the active controlling entity for ID5 Technology Limited and places its shareholding and voting rights at 75% or more.",
  "chapter": "8",
  "source_ids": [
   "IDN-ID5-S02",
   "IDN-ID5-S19"
  ],
  "passage": "[IDN-ID5-S02, Active Id5 Technology Sas entry, Nature of control; next row for voting rights] Ownership of shares – 75% or more [IDN-ID5-S19, Printed p. 8 (PDF p. 9), note 9, Controlling party] its majority shareholding",
  "support": [
   {
    "source_id": "IDN-ID5-S02",
    "passage": "Ownership of shares – 75% or more",
    "locator": "Active Id5 Technology Sas entry, Nature of control; next row for voting rights"
   },
   {
    "source_id": "IDN-ID5-S19",
    "passage": "its majority shareholding",
    "locator": "Printed p. 8 (PDF p. 9), note 9, Controlling party"
   }
  ],
  "scope_time": "2025-06-30 accounts; register as of 2026-11-11",
  "scope_geo": "UK / France",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The active French entity entry reports at least 75% of UK shares and votes. Note 9 independently identifies ID5 Technology SAS as controlling via its majority shareholding. Ceased lines refer to historical entries. Neither source gives the beneficial ownership of the French entity or the shareholders’ individual percentages.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer record states the scoped fact.",
  "limitations": "Neither source gives the beneficial ownership of the French entity or the shareholders’ individual percentages.",
  "final_wording": "The UK register names French ID5 Technology SAS as the active controlling entity for ID5 Technology Limited and places its shareholding and voting rights at 75% or more.",
  "counterevidence": "Neither source gives the beneficial ownership of the French entity or the shareholders’ individual percentages.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-ID5-F03",
  "headline": false,
  "claim": "On 9 April 2024 ID5 announced a $20 million Series B and named TransUnion and S4S Ventures among its investors.",
  "chapter": "8",
  "source_ids": [
   "IDN-ID5-S18"
  ],
  "passage": "a Series B funding round of $20 million",
  "support": [
   {
    "source_id": "IDN-ID5-S18",
    "passage": "a Series B funding round of $20 million",
    "locator": "First datelined paragraph and next paragraph naming investors"
   }
  ],
  "scope_time": "2024-04-09",
  "scope_geo": "Corporate, geography not allocated",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "ID5’s April 9 announcement identifies a $20m Series B, naming S4S Ventures and TransUnion as new investors alongside existing investors. Funding proceeds are neither product sales nor evidence of an investor’s controlling stake.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "Funding proceeds are neither product sales nor evidence of an investor’s controlling stake.",
  "final_wording": "On 9 April 2024 ID5 announced a $20 million Series B and named TransUnion and S4S Ventures among its investors.",
  "counterevidence": "Funding proceeds are neither product sales nor evidence of an investor’s controlling stake.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-ID5-F04",
  "headline": false,
  "claim": "For the year ended 30 June 2025, ID5 Technology Limited reported £702,598 in cash at bank and in hand and elected to omit its profit and loss account from the filed statements.",
  "chapter": "8",
  "source_ids": [
   "IDN-ID5-S19"
  ],
  "passage": "Cash at bank and in hand",
  "support": [
   {
    "source_id": "IDN-ID5-S19",
    "passage": "Cash at bank and in hand",
    "locator": "Printed p. 2 (PDF p. 3), Current assets, 2025 column and final paragraph on omitting the profit and loss account"
   }
  ],
  "scope_time": "2025-06-30",
  "scope_geo": "UK entity",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "The UK entity’s unaudited balance sheet shows £702,598 cash in the 2025 column as of 30 June. Its small-company filing election omits the profit and loss account. This is a date-specific stock and not annual cash received. The balance sheet describes one company. It gives no ID5 ID revenue, contract price or US product sales.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer record states the scoped fact.",
  "limitations": "The balance sheet describes one company. It gives no ID5 ID revenue, contract price or US product sales.",
  "final_wording": "ID5 Technology Limited reported £702,598 in cash at bank and in hand as of 30 June 2025. The UK company elected to exclude its profit and loss account from the unaudited public filing.",
  "counterevidence": "The balance sheet describes one company. It gives no ID5 ID revenue, contract price or US product sales.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-ID5-F05",
  "headline": false,
  "claim": "ID5’s JavaScript guide says publishers can register to distribute ID5 ID without charge and that platforms and intermediaries need a commercial license for use beyond the standard publisher integration.",
  "chapter": "8, 12",
  "source_ids": [
   "IDN-ID5-S03",
   "IDN-VID5-S01"
  ],
  "passage": "[IDN-ID5-S03, §1 Register with ID5, first paragraph] free to distribute [IDN-ID5-S03, §1, Commercial Use paragraph] execute a commercial license",
  "support": [
   {
    "source_id": "IDN-ID5-S03",
    "passage": "free to distribute",
    "locator": "§1 Register with ID5, first paragraph"
   },
   {
    "source_id": "IDN-ID5-S03",
    "passage": "execute a commercial license",
    "locator": "§1, Commercial Use paragraph"
   }
  ],
  "scope_time": "2026-02-05 guide, read 2026-11-11",
  "scope_geo": "Global",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The JS guide requires a commercial licence for platforms, intermediaries, or other commercial use beyond standard publisher integration. The linked agreement limits the no-charge entitlement to encrypted ID delivery and offers decryption, connections and data use for purchase. No enterprise rate card is given. Individual enterprise fees, volume tiers and revenue recognition are not specified in this guide.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "Individual enterprise fees, volume tiers and revenue recognition are not specified in this guide.",
  "final_wording": "ID5 offers registered publishers encrypted ID delivery without charge. Its guide requires a commercial licence for platforms, intermediaries or commercial uses beyond standard publisher integration. The agreement offers decryption, connections between IDs and use of ID5 data for purchase.",
  "counterevidence": "Individual enterprise fees, volume tiers and revenue recognition are not specified in this guide.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": ""
 },
 {
  "id": "IDN-ID5-F06",
  "headline": false,
  "claim": "ID5 describes using deterministic signals across domains and devices and combining signals in a model that infers identity; its publisher guide names hashed email and first-party IDs as partner inputs when available.",
  "chapter": "",
  "source_ids": [
   "IDN-ID5-S04",
   "IDN-ID5-S03",
   "IDN-VID5-S02",
   "IDN-VID5-S03"
  ],
  "passage": "[IDN-ID5-S04, Concluding ID5-specific approach, first paragraph] we use deterministic signals to reconcile users across domains and devices [IDN-ID5-S03, §3 Optimize ID5 JS API Configuration, Configuring the pd parameter] First Party user IDs",
  "support": [
   {
    "source_id": "IDN-ID5-S04",
    "passage": "we use deterministic signals to reconcile users across domains and devices",
    "locator": "Concluding ID5-specific approach, first paragraph"
   },
   {
    "source_id": "IDN-ID5-S03",
    "passage": "First Party user IDs",
    "locator": "§3 Optimize ID5 JS API Configuration, Configuring the pd parameter"
   }
  ],
  "scope_time": "2022-03-24 method account; 2026-02-05 integration guide",
  "scope_geo": "Global",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The March 2022 vendor explanation says it uses deterministic signals across domains and devices and probabilistic modeling. Its later integration guide identifies hashed email and first-party user IDs as inputs when available. The competing BidPulse test concerns ID5-bridged identifiers and a geographic proxy, and cannot validate the identity of the person or household behind the ID. Retain the two source dates. The competitor study uses fixed-line location history, not independent truth labels for the sold identifier.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "The paired sources do not provide the model weights, acceptance threshold, or validation against an independently labeled US person or household.",
  "final_wording": "ID5 describes using deterministic signals across domains and devices and combining signals in a model that infers identity; its publisher guide names hashed email and first-party IDs as partner inputs when available.",
  "counterevidence": "Competitor Intent IQ benchmarks IDs that ID5 bridges into bid requests against fixed-line IP location histories. The period-specific result provides a geographic disagreement measure, without independently labeled US person/household truth for ID5 ID.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-ID5-F07",
  "headline": false,
  "claim": "ID5’s 19 October 2026 platform policy says that Twine Data, formerly TrueData Solutions, runs a separate US licensing business and that neither side uses the other’s data for its stated client services or data licensing.",
  "chapter": "",
  "source_ids": [
   "IDN-ID5-S05"
  ],
  "passage": "ID5 Platform does not use Twine Data's data",
  "support": [
   {
    "source_id": "IDN-ID5-S05",
    "passage": "ID5 Platform does not use Twine Data's data",
    "locator": "PDF p. 9, ID5 Affiliates, in particular the former name, 5 October name change, and both restrictions on use"
   }
  ],
  "scope_time": "2026-10-19 policy; name change stated as 2026-10-05",
  "scope_geo": "US affiliate / ID5 platform",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "The October 19 v4.4 public policy names Twine Data, formerly TrueData Solutions, as an affiliate with a separately operated US licensing business and expressly describes both data-use boundaries as current policy. It is direct evidence of what ID5 published, not independent observation of its systems. Classify the published policy as a direct record of ID5’s statement; enforcement and technical separation are self-described. This dated disclosure is a vendor statement about data use. It does not establish the lineage of every historical edge.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "This dated disclosure is a vendor statement about data use. It does not establish the lineage of every historical edge.",
  "final_wording": "In its 19 October 2026 platform privacy policy, ID5 states that its platform does not use data from Twine Data, formerly TrueData Solutions, in client or partner services, and that Twine does not use ID5 platform data in its separate US licensing business.",
  "counterevidence": "ID5’s acquisition announcement described plans to combine offerings. Its later platform policy describes separate data sets and operations.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-ID5-F08",
  "headline": false,
  "claim": "The Prebid ID5 module guide uses the id5-sync.com EID source and documents a value of 0 where consent is absent or the user has opted out.",
  "chapter": "4, 5",
  "source_ids": [
   "IDN-ID5-S06"
  ],
  "passage": "in case of no consent or optout",
  "support": [
   {
    "source_id": "IDN-ID5-S06",
    "passage": "in case of no consent or optout",
    "locator": "Provided eids, example source and paragraph immediately below the example"
   }
  ],
  "scope_time": "Current module guide read 2026-11-11",
  "scope_geo": "Global web module",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The Prebid module documentation says the id5-sync.com entry should still be present, with the ID in its uids array set to the string “0” for no consent or opt-out. Sender behavior in documentation does not prove recipient execution. A sender-side sentinel does not prove a specific DSP received it or removed an earlier ID.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "A sender-side sentinel does not prove a specific DSP received it or removed an earlier ID.",
  "final_wording": "Prebid documents that the id5-sync.com EID should remain present, with its ID set to the string “0” when consent is absent or the user opts out.",
  "counterevidence": "A sender-side sentinel does not prove a specific DSP received it or removed an earlier ID.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-ID5-F09",
  "headline": false,
  "claim": "ID5 instructs publishers with US-originating traffic to include it in their do-not-sell/share signal flow, such as GPP or GPC, and gives separate TCF or opt-in instructions for EEA and UK traffic.",
  "chapter": "4",
  "source_ids": [
   "IDN-ID5-S07",
   "IDN-ID5-S05"
  ],
  "passage": "e.g., GPP string, GPC Signal",
  "support": [
   {
    "source_id": "IDN-ID5-S07",
    "passage": "e.g., GPP string, GPC Signal",
    "locator": "§2 US Publisher Requirements, A, Signal Flow; §3 B, TCF and non-TCF instructions"
   }
  ],
  "scope_time": "2026-02-01 guide",
  "scope_geo": "US; separately EEA and UK",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The US publisher instructions call for ID5 in GPP/GPC or equivalent opt-out flows. EEA and UK instructions require purpose-specific signals for TCF participants or prior valid opt-in for non-TCF participants, and ID5 approval for non-TCF EEA processing. The policy separately identifies purposes using consent versus legitimate interest. Instructions to publishers document collection and signaling responsibilities. They do not certify the legal basis or verify a receiving DSP’s actions.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "Instructions to publishers document collection and signaling responsibilities. They do not certify the legal basis or verify a receiving DSP’s actions.",
  "final_wording": "ID5 instructs publishers with US-originating traffic to include it in their do-not-sell/share signal flow, such as GPP or GPC, and gives separate TCF or opt-in instructions for EEA and UK traffic.",
  "counterevidence": "Instructions to publishers document collection and signaling responsibilities. They do not certify the legal basis or verify a receiving DSP’s actions.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-ID5-F10",
  "headline": false,
  "claim": "ID5 describes an SSP sending the ID in an OpenRTB request and a DSP separately obtaining decryption keys and merge instructions that link publisher-specific IDs.",
  "chapter": "4",
  "source_ids": [
   "IDN-A-S11"
  ],
  "passage": "keys from ID5",
  "support": [
   {
    "source_id": "IDN-A-S11",
    "passage": "keys from ID5",
    "locator": "Solution Overview, RTB Process steps 3–5, including the next sentence about publisher-specific IDs"
   }
  ],
  "scope_time": "2025-11-25 guide, read 2026-11-11",
  "scope_geo": "Global",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The ID5 DSP guide maps publisher, SSP and DSP handoffs, shows different OpenRTB field locations by version, and specifies out-of-band keys and merge instructions to link publisher-specific IDs. The actual decryption manual is login-restricted. The workflow does not identify a completed auction, a per-seat permission outcome or a bid-to-conversion match.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "The workflow does not identify a completed auction, a per-seat permission outcome or a bid-to-conversion match.",
  "final_wording": "ID5 describes an SSP sending the ID in an OpenRTB request and a DSP separately obtaining decryption keys and merge instructions that link publisher-specific IDs.",
  "counterevidence": "The workflow does not identify a completed auction, a per-seat permission outcome or a bid-to-conversion match.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-ID5-F11",
  "headline": false,
  "claim": "Adobe documents ID5 ID as a universal-ID targeting option for DSP placements, with one universal-ID type per placement and available choices dependent on the selected geography.",
  "chapter": "",
  "source_ids": [
   "IDN-ID5-S10"
  ],
  "passage": "Targets ID5 IDs created probabilistically from email addresses and other signals.",
  "support": [
   {
    "source_id": "IDN-ID5-S10",
    "passage": "Targets ID5 IDs created probabilistically from email addresses and other signals.",
    "locator": "Audience Targeting → Targeting → Universal ID, intro and ID5 bullet"
   }
  ],
  "scope_time": "2026-10-02",
  "scope_geo": "Geo-targeted Adobe DSP placements; no US-specific use count",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Adobe’s placement instructions allow one universal ID type at a time with choices constrained by geo-targets, and explicitly say ID5 IDs are available at no fee within this Adobe offering. This resolves the route-specific availability of the ID free of charge, not the fees paid by a DSP to ID5. The settings describe a selectable buy-side feature, not its use by every seat, a national coverage estimate or an exported cross-platform identifier.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "The settings describe a selectable buy-side feature, not its use by every seat, a national coverage estimate or an exported cross-platform identifier.",
  "final_wording": "Adobe lists ID5 ID as a no-fee universal-ID option in its DSP placement settings. A buyer selects one universal-ID type, and available options depend on the placement’s geographical targets.",
  "counterevidence": "The settings describe a selectable buy-side feature, not its use by every seat, a national coverage estimate or an exported cross-platform identifier.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": ""
 },
 {
  "id": "IDN-ID5-F12",
  "headline": false,
  "claim": "Adform says its site-tracking tag can associate an ID5 ID with a visitor for retargeting and that ID Fusion connects the identifier with its DSP, SSP, DMP and ad server.",
  "chapter": "",
  "source_ids": [
   "IDN-ID5-S11"
  ],
  "passage": "automatically associate an ID5 ID with their visitors",
  "support": [
   {
    "source_id": "IDN-ID5-S11",
    "passage": "automatically associate an ID5 ID with their visitors",
    "locator": "Why ID5?, final two paragraphs; One Tag. Full Power. No Extra Work."
   }
  ],
  "scope_time": "Adform newsroom HTML dates the announcement to 2025-05-28; read 2026-11-11.",
  "scope_geo": "Location of use unspecified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Adform reports that one tag can activate tracking and associate ID5 IDs with visitors for retargeting. Its ID Fusion integration spans its DSP, SSP, DMP and ad server. The native publisher HTML dates this announcement to 28 May 2025. No production volume or US seat is identified. One operator describes multiple products. The partner release gives no US transaction count or independently observed campaign delivery.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "One operator describes multiple products. The partner release gives no US transaction count or independently observed campaign delivery.",
  "final_wording": "Adform says its site-tracking tag can associate an ID5 ID with a visitor for retargeting and that ID Fusion connects the identifier with its DSP, SSP, DMP and ad server.",
  "counterevidence": "One operator describes multiple products. The partner release gives no US transaction count or independently observed campaign delivery.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": ""
 },
 {
  "id": "IDN-ID5-F13",
  "headline": false,
  "claim": "ID5 specifies S3 feeds for opt-outs every 30 minutes and deletion requests hourly and expects its partners to ingest and process the lists.",
  "chapter": "4, 12",
  "source_ids": [
   "IDN-ID5-S09"
  ],
  "passage": "every 30 minutes on a rolling basis for opt-outs and on a hourly basis for deletion requests",
  "support": [
   {
    "source_id": "IDN-ID5-S09",
    "passage": "every 30 minutes on a rolling basis for opt-outs and on a hourly basis for deletion requests",
    "locator": "Propagation Details, Frequency; Partner Responsibility & S3 Bucket Setup; Privacy Feeds, delivery-delay note"
   }
  ],
  "scope_time": "2026-03-31 guide",
  "scope_geo": "Partner feed, including US-facing workflows",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The regular partner lists update every 30 minutes for opt-outs and hourly for routine deletion. A separate on-demand deletion feed is best-effort, without a fixed schedule; file delivery can lag and actual recipient processing is separate. The feeds may arrive late; publication time is distinct from partner completion, deletion of derivatives and independent proof of suppression.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "ID5 also describes best-effort, on-demand deletions with no fixed schedule. Files can arrive late. Publication time does not establish partner deletion, suppression of derived outputs, or measured completion.",
  "final_wording": "ID5 specifies 30-minute opt-out updates, hourly routine deletion updates and a separate best-effort feed for on-demand deletions. Partners are expected to ingest and process these S3 lists; their completion time is unverified.",
  "counterevidence": "The feeds may arrive late; publication time is distinct from partner completion, deletion of derivatives and independent proof of suppression.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-ID5-F14",
  "headline": false,
  "claim": "Sovrn and ID5 describe a participating-publisher test with US audiences that compared a control with conditions in which hashed email was linked and either sent into the auction or withheld.",
  "chapter": "5",
  "source_ids": [
   "IDN-ID5-S12",
   "IDN-ID5-S22"
  ],
  "passage": "[IDN-ID5-S12, PDF p. 2, Methodology & Testing, groups A–C; p. 1, Overview for US scope] Group C - HEM linked and withheld from auction [IDN-ID5-S22, Sovrn Team, 21 September 2022, A Smarter Data Feed, opening paragraph] passed to buyers for evaluation",
  "support": [
   {
    "source_id": "IDN-ID5-S12",
    "passage": "Group C - HEM linked and withheld from auction",
    "locator": "PDF p. 2, Methodology & Testing, groups A–C; p. 1, Overview for US scope"
   },
   {
    "source_id": "IDN-ID5-S22",
    "passage": "passed to buyers for evaluation",
    "locator": "Sovrn Team, 21 September 2022, A Smarter Data Feed, opening paragraph"
   }
  ],
  "scope_time": "Reported 2022-09-21; fieldwork period unreported",
  "scope_geo": "US audiences of participating publishers",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The joint case identifies US audiences of participating publishers and describes three groups (control, linked and withheld, linked and passed). The reported 72% and 98% CPM uplifts are commercial comparisons by interested partners. Raw CPMs, impression counts, field dates, randomization and household/person links with truth labels are not reported. The companion post is the same result, dated September 21, 2022. The case reports CPM differences for bundled Sovrn and ID5 treatments. There is no count of labeled true or false person links, representative national base, or stated randomization.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "The case reports CPM differences for bundled Sovrn and ID5 treatments. There is no count of labeled true or false person links, representative national base, or stated randomization.",
  "final_wording": "Sovrn and ID5 describe a participating-publisher test with US audiences that compared a control with conditions in which hashed email was linked and either sent into the auction or withheld.",
  "counterevidence": "The case reports CPM differences for bundled Sovrn and ID5 treatments. There is no count of labeled true or false person links, representative national base, or stated randomization.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "Joint partner comparison across three publisher traffic groups. CPM is the outcome. Test duration, publisher count, traffic count, assignment procedure, independent funding and error labels are not specified.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-ID5-F15",
  "headline": false,
  "claim": "ID5’s Match Preview defines a rate for each output ID type by dividing distinct submitted hashed emails having at least one match by all distinct input identifiers; the table illustrates the calculation.",
  "chapter": "3",
  "source_ids": [
   "IDN-C-S31"
  ],
  "passage": "the count and percentage of HEMs with at least one match",
  "support": [
   {
    "source_id": "IDN-C-S31",
    "passage": "the count and percentage of HEMs with at least one match",
    "locator": "§3 Match Test Output, first sentence and Fields table (match_rate_pct); Example output; §1 Configuration for country and method"
   }
  ],
  "scope_time": "2026-10-01 guide",
  "scope_geo": "Country configurable; example unspecified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The format defines per-ID-type coverage as distinct input IDs with at least one match divided by distinct submitted input IDs. The 80% row is an example. No observed US cohort-A reach, identity accuracy or bidstream outcome follows. The example gives no real US fieldwork period or observed production population. It concerns Data Onboarding, a related service, and cannot be assigned to the cohort-A bidstream buying task.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "The example gives no real US fieldwork period or observed production population. It concerns Data Onboarding, a related service, and cannot be assigned to the cohort-A bidstream buying task.",
  "final_wording": "ID5’s Match Preview defines a rate for each output ID type by dividing distinct submitted hashed emails having at least one match by all distinct input identifiers; the table illustrates the calculation.",
  "counterevidence": "The example gives no real US fieldwork period or observed production population. It concerns Data Onboarding, a related service, and cannot be assigned to the cohort-A bidstream buying task.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-ID5-F16",
  "headline": false,
  "claim": "ID5’s statement datelined 30 October 2025 announced its acquisition of TrueData and described a future combination of the offerings.",
  "chapter": "",
  "source_ids": [
   "IDN-D-S09"
  ],
  "passage": "announced the acquisition of TrueData",
  "support": [
   {
    "source_id": "IDN-D-S09",
    "passage": "announced the acquisition of TrueData",
    "locator": "First datelined paragraph; fourth paragraph on planned combination"
   }
  ],
  "scope_time": "2025-10-30 dateline, posted 2025-11-04",
  "scope_geo": "US / global",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The 4 November 2025 ID5 page contains a London/New York dateline of 30 October and reports the acquisition. It forecasts a combination of offerings without documenting link migrations or the 2025 price. This is the announcement date; the release does not document a completed technical migration or identify link-level continuity.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "This is the announcement date; the release does not document a completed technical migration or identify link-level continuity.",
  "final_wording": "ID5’s statement datelined 30 October 2025 announced its acquisition of TrueData and described a future combination of the offerings.",
  "counterevidence": "This is the announcement date; the release does not document a completed technical migration or identify link-level continuity.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-ID5-F17",
  "headline": false,
  "claim": "On 1 October 2026 ID5 described the sale of the former TrueData third-party audience business and brand to Cloud Technologies.",
  "chapter": "",
  "source_ids": [
   "IDN-D-S10",
   "IDN-ID5-S16",
   "IDN-ID5-S17"
  ],
  "passage": "acquired TrueData’s third-party audience business",
  "support": [
   {
    "source_id": "IDN-D-S10",
    "passage": "acquired TrueData’s third-party audience business",
    "locator": "Opening paragraph; third paragraph separates audience and identity businesses"
   }
  ],
  "scope_time": "2026-10-01 seller statement",
  "scope_geo": "North American audience business",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "ID5’s 1 October 2026 account explicitly scopes its sale description to the third-party audience business and TrueData brand. Independent of that statement, the buyer filed the conditional agreement and then its 5 October completion. The dated seller statement is separate from the date the buyer reported completion. It does not describe the sale of ID5 ID.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "The dated seller statement is separate from the date the buyer reported completion. It does not describe the sale of ID5 ID.",
  "final_wording": "On 1 October 2026 ID5 described the sale of the former TrueData third-party audience business and brand to Cloud Technologies.",
  "counterevidence": "The dated seller statement is separate from the date the buyer reported completion. It does not describe the sale of ID5 ID.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-ID5-F18",
  "headline": false,
  "claim": "Cloud Technologies reported a conditional 30 September 2026 agreement with TrueData Solutions Inc. covering a new US vehicle, with $1.1 million of agreed consideration for the shares and technology license.",
  "chapter": "8",
  "source_ids": [
   "IDN-ID5-S16"
  ],
  "passage": "1,1 mln dolarów amerykańskich za nabycie udziałów oraz licencji",
  "support": [
   {
    "source_id": "IDN-ID5-S16",
    "passage": "1,1 mln dolarów amerykańskich za nabycie udziałów oraz licencji",
    "locator": "ESPI 23/2026, Treść raportu, paragraphs 1–2; comma is Polish decimal separator"
   }
  ],
  "scope_time": "2026-09-30 signing",
  "scope_geo": "Polish-listed buyer / US vehicle",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "ESPI 23/2026 reports a conditional agreement on 30 September with TrueData Solutions Inc for 100% of a new US SPV. USD 1.1m covers both shares and a technology licence for the data business. Neither ID5’s 2025 purchase price nor an operating revenue measure is disclosed. The agreement concerns the audience-data business transfer. The disclosed consideration is not the price ID5 paid in 2025, recurring revenue or ID5 ID’s valuation.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer record states the scoped fact.",
  "limitations": "The agreement concerns the audience-data business transfer. The disclosed consideration is not the price ID5 paid in 2025, recurring revenue or ID5 ID’s valuation.",
  "final_wording": "Cloud Technologies reported a conditional 30 September 2026 agreement with TrueData Solutions Inc. covering a new US vehicle, with $1.1 million of agreed consideration for the shares and technology license.",
  "counterevidence": "The agreement concerns the audience-data business transfer. The disclosed consideration is not the price ID5 paid in 2025, recurring revenue or ID5 ID’s valuation.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-ID5-F19",
  "headline": false,
  "claim": "Cloud Technologies reported that it completed the acquisition of all shares in the new US vehicle on 5 October 2026 after conditions including transfer of specified contracts were met.",
  "chapter": "8",
  "source_ids": [
   "IDN-ID5-S17"
  ],
  "passage": "w dniu 5 października 2026 roku doszło do realizacji umowy",
  "support": [
   {
    "source_id": "IDN-ID5-S17",
    "passage": "w dniu 5 października 2026 roku doszło do realizacji umowy",
    "locator": "ESPI 24/2026, Treść raportu, first paragraph"
   }
  ],
  "scope_time": "2026-10-05 close",
  "scope_geo": "Polish-listed buyer / US vehicle",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "ESPI 24/2026 reports completion of the acquisition of 100% of the US SPV on 5 October once conditions including transfer of specified contracts were met. It does not say Cloud Technologies bought the ID5 group or core ID. This establishes completion for the vehicle. It does not show migration of identity links or a transfer of the ID5 identifier.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The issuer record states the scoped fact.",
  "limitations": "This establishes completion for the vehicle. It does not show migration of identity links or a transfer of the ID5 identifier.",
  "final_wording": "Cloud Technologies reported that it completed the acquisition of all shares in the new US vehicle on 5 October 2026 after conditions including transfer of specified contracts were met.",
  "counterevidence": "This establishes completion for the vehicle. It does not show migration of identity links or a transfer of the ID5 identifier.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-ID5-F20",
  "headline": false,
  "claim": "The Prebid example sets local storage to 90 days and refresh to two hours; ID5 separately reports a maximum 100-day retention period for data used to provide its live ID service before deletion or aggregation.",
  "chapter": "5, 11",
  "source_ids": [
   "IDN-ID5-S06",
   "IDN-ID5-S05"
  ],
  "passage": "[IDN-ID5-S06, Publisher wants to retrieve the ID5 ID through Prebid.js, storage.expires and storage.refreshInSeconds; earlier note recommends two hours or less] refresh ID every 2 hours [IDN-ID5-S05, PDF pp. 9–10, Retention, separate limited security data described immediately afterward] 100 days before being deleted or aggregated",
  "support": [
   {
    "source_id": "IDN-ID5-S06",
    "passage": "refresh ID every 2 hours",
    "locator": "Publisher wants to retrieve the ID5 ID through Prebid.js, storage.expires and storage.refreshInSeconds; earlier note recommends two hours or less"
   },
   {
    "source_id": "IDN-ID5-S05",
    "passage": "100 days before being deleted or aggregated",
    "locator": "PDF pp. 9–10, Retention, separate limited security data described immediately afterward"
   }
  ],
  "scope_time": "Prebid guide read 2026-11-11; platform policy 2026-10-19",
  "scope_geo": "Web cache / ID5 live-service data",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "The example storage.expires and refreshInSeconds are 90 days and 7,200 seconds; preceding advice recommends two hours or less. The policy gives a separate maximum of 100 days for live-service data before aggregation/deletion. The 90-day third-party cookie and restricted security data up to 18 months are separately described. None supplies general graph-edge expiry. Client refresh, storage expiry and operator data retention use different clocks. These sources do not give a lifetime for every individual graph edge.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "Client refresh, storage expiry and operator data retention use different clocks. These sources do not give a lifetime for every individual graph edge.",
  "final_wording": "The Prebid example sets local storage to 90 days and refresh to two hours; ID5 separately reports a maximum 100-day retention period for data used to provide its live ID service before deletion or aggregation.",
  "counterevidence": "Client refresh, storage expiry and operator data retention use different clocks. These sources do not give a lifetime for every individual graph edge.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-ID5-F21",
  "headline": false,
  "claim": "The April 2025 and November 2026 ID5 publisher SDK guides both set maxCascades to eight by default when cookie sync is needed and specify minus one to disable syncing.",
  "chapter": "",
  "source_ids": [
   "IDN-E-S21",
   "IDN-E-S23",
   "IDN-ID5-S06"
  ],
  "passage": "[IDN-E-S21, README, Available Configuration Options, maxCascades row, commit bd6c891f2c63] will disable cookie syncing altogether. [IDN-E-S23, README, Available Configuration Options, maxCascades row, commit 576fd16780a9] will disable cookie syncing altogether.",
  "support": [
   {
    "source_id": "IDN-E-S21",
    "passage": "will disable cookie syncing altogether.",
    "locator": "README, Available Configuration Options, maxCascades row, commit bd6c891f2c63"
   },
   {
    "source_id": "IDN-E-S23",
    "passage": "will disable cookie syncing altogether.",
    "locator": "README, Available Configuration Options, maxCascades row, commit 576fd16780a9"
   }
  ],
  "scope_time": "2025-04-18 and 2026-11-06 snapshots",
  "scope_geo": "Publisher SDK; no US deployment observation",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "Both immutable release README files state that maxCascades defaults to 8 when sync is required, and a value of -1 disables it. GitHub commit metadata independently yields v1.0.83 April 18, 2025 and v1.0.100 November 6, 2026. The Prebid integration’s separate canCookieSync switch defaults to false. This demonstrates continuity of one configurable parameter. Actual use, browser settings and assignment decisions may differ.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "This demonstrates continuity of one configurable parameter. Actual use, browser settings and assignment decisions may differ.",
  "final_wording": "The 18 April 2025 and 6 November 2026 ID5 JavaScript SDK guides specify the same default maximum of eight cookie syncs when syncing is required. Setting maxCascades to −1 disables sync on this route.",
  "counterevidence": "This demonstrates continuity of one configurable parameter. Actual use, browser settings and assignment decisions may differ.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-ID5-F22",
  "headline": false,
  "claim": "The Prebid guide identifies v8.33.0 as the version from which publishers can configure externalModuleUrl so the ID5 module interoperates with the ID5 API.",
  "chapter": "",
  "source_ids": [
   "IDN-ID5-S06"
  ],
  "passage": "As of Prebid.js v8.33.0",
  "support": [
   {
    "source_id": "IDN-ID5-S06",
    "passage": "As of Prebid.js v8.33.0",
    "locator": "Example publisher configuration, ATTENTION note immediately following the sample"
   }
  ],
  "scope_time": "Version 8.33.0 onward; guide read 2026-11-11",
  "scope_geo": "Publisher-side web integration",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "After the configuration sample, the module guide dates optional externalModuleUrl configuration for ID5 API interoperability to Prebid.js v8.33.0. The external script is separately supplied. This does not date individual publisher upgrades. The version identifies a client configuration change. The guide does not date each publisher’s upgrade or the release of graph-model changes.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named parties describe the specified method or observation directly; the scope and limits below apply.",
  "limitations": "The version identifies a client configuration change. The guide does not date each publisher’s upgrade or the release of graph-model changes.",
  "final_wording": "The Prebid guide identifies v8.33.0 as the version from which publishers can configure externalModuleUrl so the ID5 module interoperates with the ID5 API.",
  "counterevidence": "The version identifies a client configuration change. The guide does not date each publisher’s upgrade or the release of graph-model changes.",
  "stream": "id5-id",
  "study_id": "",
  "study_design": "",
  "claim_status": "n/a",
  "hypothesis": ""
 },
 {
  "id": "IDN-LR-F01",
  "headline": false,
  "claim": "LiveRamp describes ATS as a publisher route in which an SSP decrypts an envelope and passes a DSP-specific RampID in a bid request.",
  "chapter": "abstract, 1, 2, 4, 5",
  "source_ids": [
   "IDN-LR-S08"
  ],
  "passage": "passes the RampID in bid requests to DSP",
  "support": [
   {
    "source_id": "IDN-LR-S08",
    "passage": "passes the RampID in bid requests to DSP",
    "locator": "How ATS Works, step 3; Glossary, Sidecar"
   }
  ],
  "scope_time": "Guide modified 2026-09-22",
  "scope_geo": "US and other markets as specified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The publisher flow explicitly has the SSP open the envelope with Sidecar and forward a RampID in a bid request. Its Sidecar glossary specifies DSP-specific encodings. This is the vendor’s interface design. No universal bidder access is stated. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "This documents the intended handoff. It does not measure bid delivery or identity accuracy.",
  "final_wording": "LiveRamp describes ATS as a publisher route in which an SSP decrypts an envelope and passes a DSP-specific RampID in a bid request.",
  "counterevidence": "The SSP needs an enabled Sidecar and keys. A publisher can also use other delivery paths.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-LR-F02",
  "headline": false,
  "claim": "LiveRamp’s ATS security guide says an input hash can yield a derived RampID even when its representation is absent from the offline graph.",
  "chapter": "1, 3",
  "source_ids": [
   "IDN-LR-S01"
  ],
  "passage": "this ARL does not exist within the offline graph",
  "support": [
   {
    "source_id": "IDN-LR-S01",
    "passage": "this ARL does not exist within the offline graph",
    "locator": "RampID Resolution and Encryption, unmatched lookup"
   }
  ],
  "scope_time": "Guide modified 2025-08-04",
  "scope_geo": "US and other markets as specified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "If no corresponding offline RampID exists, the guide describes deriving a consistent RampID from a salted hashed representation. Equal inputs can still be matched. A derived ID is no proof of an observed offline identity. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "A repeatable hash-level match does not verify the person or an observed graph edge.",
  "final_wording": "LiveRamp’s ATS security guide says an input hash can yield a derived RampID even when its representation is absent from the offline graph.",
  "counterevidence": "The same guide describes lookup of a corresponding graph RampID when one exists.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-LR-F03",
  "headline": false,
  "claim": "LiveRamp says its graph uses observed links from match partners and that its separate Known Identity Resolution API and cloud service return AbiliTec Links and Known IDs respectively.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S02",
   "IDN-U-S16"
  ],
  "passage": "[IDN-U-S02, RampID Methodology, Online Device Linking] deterministically observed linkages of devices and pseudonymized PII touchpoints [IDN-U-S16, Known Identity Resolution, introduction and two route bullets] into AbiliTec Links or Known IDs",
  "support": [
   {
    "source_id": "IDN-U-S02",
    "passage": "deterministically observed linkages of devices and pseudonymized PII touchpoints",
    "locator": "RampID Methodology, Online Device Linking"
   },
   {
    "source_id": "IDN-U-S16",
    "passage": "into AbiliTec Links or Known IDs",
    "locator": "Known Identity Resolution, introduction and two route bullets"
   }
  ],
  "scope_time": "2025-08-20 methodology; 2026-03-19 product guide",
  "scope_geo": "US and other markets as specified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Device linking uses observed partner device-to-pseudonymized-PII links. The other product separately offers AbiliTec Links via API and Known IDs in cloud. Householding and offline consolidation described on the graph page do not validate a bidstream person. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "Issuer documents separate delivery tasks. The upstream graph and its claimed precision do not become separate cohort A products.",
  "final_wording": "LiveRamp says its graph uses observed links from match partners and that its separate Known Identity Resolution API and cloud service return AbiliTec Links and Known IDs respectively.",
  "counterevidence": "AbiliTec Links can translate to RampIDs in a separate technical step.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-LR-F04",
  "headline": false,
  "claim": "The ATS API storage guide gives its envelopes a 15-day lifetime in California and 30 days elsewhere, and advises updating the stored expiry when refreshing.",
  "chapter": "5",
  "source_ids": [
   "IDN-LR-S02"
  ],
  "passage": "for California (U.S.) and a 30-day TTL for all other countries and regions.",
  "support": [
   {
    "source_id": "IDN-LR-S02",
    "passage": "for California (U.S.) and a 30-day TTL for all other countries and regions.",
    "locator": "Envelope Expiration Times, first paragraph; Storing the Envelope TTL, calculateEnvelopeTTL code"
   }
  ],
  "scope_time": "2026-05-04 guide revision",
  "scope_geo": "US and other markets as specified",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Both time constants and the instruction to update expiry at refresh appear in the storage and TTL sections. They concern API envelopes and do not specify a graph-edge lifetime. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "Envelope TTL describes when a transported token can be decrypted. It is not a lifetime for a person, household, login, database record or graph edge.",
  "final_wording": "The ATS API storage guide gives its envelopes a 15-day lifetime in California and 30 days elsewhere, and advises updating the stored expiry when refreshing.",
  "counterevidence": "Renewal can issue a fresh envelope and reset the timestamp.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-LR-F05",
  "headline": false,
  "claim": "LiveRamp says US ATS.js checks the national GPP signal or a legacy CCPA fallback, and that the UK/EU flow specifies a TCF v2.3 consent check for vendor 97 and purpose 1.",
  "chapter": "4",
  "source_ids": [
   "IDN-LR-S03"
  ],
  "passage": "a GPP National String is present before checking for the CCPA Privacy String as a fallback",
  "support": [
   {
    "source_id": "IDN-LR-S03",
    "passage": "a GPP National String is present before checking for the CCPA Privacy String as a fallback",
    "locator": "For Users in the U.S. (GPP and CCPA), first paragraph; For Users in the UK or EU (GDPR), EU and EEA wording; regional diagram."
   }
  ],
  "scope_time": "Guide last modified November 3, 2026; checked November 11, 2026.",
  "scope_geo": "US and UK/EU as labeled in guide",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The guide’s November 3 revision labels a UK/EU branch in its diagram. Its prose specifically names v2.3 in the EU and the EEA note, then states vendor 97 and purpose 1 for retrieval. US checks try national GPP, then legacy CCPA with soft enforcement. A missing US string differs from an affirmative opt-in. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "Origin checks describe retrieval. The legacy CCPA string has soft enforcement when absent in the US. Login and a hash do not establish a lawful basis for every use.",
  "final_wording": "LiveRamp says US ATS.js checks national GPP first and falls back to its legacy CCPA string, whose presence is optional. Its guide groups the UK and EU in one consent branch and specifies TCF v2.3 for the EU/EEA, with vendor 97 and purpose 1 for envelope retrieval.",
  "counterevidence": "The same page says a negative DNT/GPC signal overrides a positive consent signal and removes existing local envelopes.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-LR-F06",
  "headline": false,
  "claim": "For a publisher-managed opt-out, LiveRamp instructs the publisher to delete the local envelope and keep a flag to prevent its recreation until the user opts back in.",
  "chapter": "4, 12, 13",
  "source_ids": [
   "IDN-LR-S04"
  ],
  "passage": "flag that user as opted out, so as to not re-create the envelope",
  "support": [
   {
    "source_id": "IDN-LR-S04",
    "passage": "flag that user as opted out, so as to not re-create the envelope",
    "locator": "Publisher 1p Opt-Out"
   }
  ],
  "scope_time": "Guide modified 2026-08-31",
  "scope_geo": "US and other markets as specified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The publisher first-party implementation should delete and flag on opt-out to prevent regeneration unless the user opts in again. It is separate from the beta publisher-specific route and from receipts at destinations. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "This is origin-side suppression; a browser deletion does not confirm removal from each already-receiving bidder.",
  "final_wording": "For a publisher-managed opt-out, LiveRamp instructs the publisher to delete the local envelope and keep a flag to prevent its recreation until the user opts back in.",
  "counterevidence": "The same guide also describes a per-publisher beta and a North American token-based DAA option.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-LR-F07",
  "headline": false,
  "claim": "LiveRamp’s Activation documentation makes deletion and opt-out requests available to destinations and describes direct delivery to The Trade Desk for specified audiences and marketplace segments.",
  "chapter": "4, 13",
  "source_ids": [
   "IDN-LR-S05"
  ],
  "passage": "the processing of these requests are at the discretion of the destination",
  "support": [
   {
    "source_id": "IDN-LR-S05",
    "passage": "the processing of these requests are at the discretion of the destination",
    "locator": "Opening destination policy; The Trade Desk ID Deletion and Opt Out API"
   }
  ],
  "scope_time": "Guide modified 2026-02-25",
  "scope_geo": "US and other markets as specified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The guide covers destination retrieval of files and separately describes delivery to The Trade Desk for advertiser first-party audiences and third-party marketplace segments. It expressly leaves processing to each destination. Making a request available does not establish that recipients have completed it. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "This adjacent workflow is not a receipt for an ATS bid. It supplies no recipient-wide proof of completion or elapsed time to final deletion.",
  "final_wording": "LiveRamp publishes opt-out and deletion requests for activation destinations and describes direct delivery to The Trade Desk for advertiser first-party audiences and third-party marketplace segments. Its guide leaves processing to the destination.",
  "counterevidence": "The direct Trade Desk delivery path is more specific than a general request to retrieve files.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-LR-F08",
  "headline": false,
  "claim": "LiveRamp publishes country-specific US terms for SSP Sidecar and RampID use and makes its US DSP/DMP client responsible for handling rights requests within that agreement.",
  "chapter": "",
  "source_ids": [
   "IDN-LR-S12",
   "IDN-LR-S11"
  ],
  "passage": "[IDN-LR-S12, Introduction, country selection USA and United States section] SSPs may use the LiveRamp Services [IDN-LR-S11, United States of America, client responsibilities] responsible for dealing with and responding to all rights requests",
  "support": [
   {
    "source_id": "IDN-LR-S12",
    "passage": "SSPs may use the LiveRamp Services",
    "locator": "Introduction, country selection USA and United States section"
   },
   {
    "source_id": "IDN-LR-S11",
    "passage": "responsible for dealing with and responding to all rights requests",
    "locator": "United States of America, client responsibilities"
   }
  ],
  "scope_time": "Public terms read 2026-11-11",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The Sidecar page’s US clause applies subject to an SSP SOW. The DSP/DMP page assigns covered US rights requests to the client and says LiveRamp will give required assistance. These published terms document duties; no processing trace or universal signed contract is shown. The subject of this claim is the content of the contracting party’s own published terms. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "A named right and recipient duty establish contractual scope, not a GPP field parsed by a specific bidder for a particular bid.",
  "final_wording": "LiveRamp publishes country-specific US terms for SSP Sidecar and RampID use and makes its US DSP/DMP client responsible for handling rights requests within that agreement.",
  "counterevidence": "The SSP terms also require LiveRamp to assist with covered requests where necessary and required.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-LR-F09",
  "headline": false,
  "claim": "In its May 2023 earnings release, LiveRamp said its ATS publisher integrations connected to more than 90% of US consumer time spent online.",
  "chapter": "",
  "source_ids": [
   "IDN-LR-S09"
  ],
  "passage": "connected to over 90% of consumer time spent online in the US",
  "support": [
   {
    "source_id": "IDN-LR-S09",
    "passage": "connected to over 90% of consumer time spent online in the US",
    "locator": "Furnished Exhibit 99.1, p. 3, Additional Business Highlights & Metrics, publisher-domains bullet."
   }
  ],
  "scope_time": "As of May 24, 2023; underlying observation window not stated",
  "scope_geo": "United States",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The furnished press release expressly refers to the share of US time spent online associated with publisher integrations. It does not give the population of consumers authenticating, the observation period or an independent measurement; the exhibit is an issuer assertion. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "The unit is time. The release supplies no count of authenticated people, eligible users, impressions or successfully decrypted IDs. It does not disclose time-panel method or date range.",
  "final_wording": "In its May 2023 earnings release, LiveRamp said its ATS publisher integrations connected to more than 90% of US consumer time spent online.",
  "counterevidence": "Its worldwide domain count measures a second population; wholesale conversion into US unique user coverage is unsupported.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "Issuer attribution to publisher integrations; sample, deduplication and denominator computation unavailable.",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-LR-F10",
  "headline": false,
  "claim": "Google reports that New York Times Advertising used Secure Signals with both RampID and UID2 and reports an 81% revenue gain on restricted-cookie browsers in its 2025 publisher results.",
  "chapter": "3, 5",
  "source_ids": [
   "IDN-LR-S06"
  ],
  "passage": "including UID2 and RampID",
  "support": [
   {
    "source_id": "IDN-LR-S06",
    "passage": "including UID2 and RampID",
    "locator": "The approach; The results, +81%, Increase in revenue on browsers with restricted cookies; note 1"
   }
  ],
  "scope_time": "Publisher results 2025, finer period unstated",
  "scope_geo": "Publisher inventory; geography not specified",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The Google case names ATS, RampID and UID2, describes Ad Manager impact estimates, labels the restricted-cookie result +81%, and gives a 2025 publisher-results footnote. It neither isolates RampID’s contribution nor discloses the impression population or a randomized comparison. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "This is a platform case based on impact estimates. The page does not report a single-ID control, US-only sample, independently audited lift or person-level truth set.",
  "final_wording": "Google reports that New York Times Advertising used Secure Signals with both RampID and UID2 and reports an 81% revenue gain on restricted-cookie browsers in its 2025 publisher results.",
  "counterevidence": "Two IDs and the delivery platform shared the implementation; the metric cannot isolate a RampID effect.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "Interested platform case using Ad Manager impact estimates. Sample size, statistical uncertainty, randomization and cell allocation not specified.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-LR-F11",
  "headline": false,
  "claim": "LiveRamp’s published Activation match-rate formula divides eligible unique records matched to at least one device at a chosen destination by the eligible unique input records.",
  "chapter": "3, 13",
  "source_ids": [
   "IDN-C-S01"
  ],
  "passage": "percentage of total unique, identifiable records",
  "support": [
   {
    "source_id": "IDN-C-S01",
    "passage": "percentage of total unique, identifiable records",
    "locator": "How LiveRamp Calculates Match Rates, definition"
   }
  ],
  "scope_time": "Connect documentation read 2026-11-11",
  "scope_geo": "Destination-specific; example does not specify US sample",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The numerator is eligible unique identifiable records matched to one or more devices at a specified destination. Non-distributed records are excluded, and the guide expressly has a different Facebook account-based method. This is a measure of file-to-destination addressability. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "The input base differs from all submissions. Measurement Enablement has a separate valid-row recognition rate. Neither definition is an observed US ATS envelope match rate.",
  "final_wording": "For its standard activation rate, LiveRamp divides unique identifiable records matched to one or more online devices at a destination by eligible unique identifiable records, excluding records not being distributed. Facebook uses a separate calculation.",
  "counterevidence": "The guide separately describes destinations with different counting rules, including Facebook.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-LR-F12",
  "headline": false,
  "claim": "LiveRamp attributes 95%–98.9% precision for its historical graph to a comScore test; the reviewed note does not establish current US ATS person accuracy.",
  "chapter": "3",
  "source_ids": [
   "IDN-B-S04"
  ],
  "passage": "LiveRamp’s graph was tested by comScore to have an industry leading 95%-98.9% precision",
  "support": [
   {
    "source_id": "IDN-B-S04",
    "passage": "LiveRamp’s graph was tested by comScore to have an industry leading 95%-98.9% precision",
    "locator": "Deterministic Matching, Note; page last modified August 19, 2020"
   }
  ],
  "scope_time": "Historical graph claim in 2020 guide; measurement period undisclosed",
  "scope_geo": "Test geography unspecified",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "An issuer note last modified in August 2020 attributes the precision range to comScore using a panel of approximately twelve million verified devices and individuals. It gives no test period, error counts, independence or separate ATS handoff results. A targeted search did not yield the underlying report for this range. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "The seller describes about 12 million verified devices and individuals and range variation by sample quality. The primary protocol, label construction, named current output, funding, period and error counts were not established in this screen.",
  "final_wording": "LiveRamp attributes 95%–98.9% precision for its historical graph to a comScore test; the reviewed note does not establish current US ATS person accuracy.",
  "counterevidence": "A named reviewer and panel constitute a lead for a graph test. They cannot attribute the test to current ATS bid handoffs.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "Vendor summary, named comScore, approximately 12 million devices and individuals, no public panel construction or error counts in the opened note.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-LR-F13",
  "headline": false,
  "claim": "LiveRamp announced the IdentityLink-to-RampID name change in May 2021, and its v1.0 Prebid example still uses the legacy identityLink module and idl_env storage name.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S13",
   "IDN-C-S14"
  ],
  "passage": "[IDN-C-S13, Announcement dated May 24, 2021, opening paragraph] formerly known as \"IdentityLink\" or \"IDL\" [IDN-C-S14, Configuring Prebid for ATS, userSync.userIds storage and identityLink name] name: 'idl_env'",
  "support": [
   {
    "source_id": "IDN-C-S13",
    "passage": "formerly known as \"IdentityLink\" or \"IDL\"",
    "locator": "Announcement dated May 24, 2021, opening paragraph"
   },
   {
    "source_id": "IDN-C-S14",
    "passage": "name: 'idl_env'",
    "locator": "Configuring Prebid for ATS, userSync.userIds storage and identityLink name"
   }
  ],
  "scope_time": "Notice 2021-05-24; v1.0 guide read 2026-11-11",
  "scope_geo": "US and other markets as specified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The 2021 announcement renames the existing ID; the v1.0 guide shows identityLink and idl_env and directs developers to migrate to v2. This confirms the historical example, not graph-edge continuity. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "Code-level naming continuity and an issuer rename do not establish persistent underlying edges for the post-2020 replacement-launch population.",
  "final_wording": "LiveRamp announced the IdentityLink-to-RampID name change in May 2021, and its v1.0 Prebid example still uses the legacy identityLink module and idl_env storage name.",
  "counterevidence": "The documented Legacy v1.0 storage key should not be substituted for the current API storage example in every integration.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-LR-F14",
  "headline": false,
  "claim": "The issuer markets authenticated cookieless inventory via ATS and separately instructs implementers to use a pixel for its cookie-to-RampID mapping-file workflow.",
  "chapter": "5",
  "source_ids": [
   "IDN-LR-S08",
   "IDN-E-S18",
   "IDN-LR-S01"
  ],
  "passage": "[IDN-LR-S08, Authenticated Traffic Solution, introduction] authenticated, cookieless inventory [IDN-E-S18, RampID Mapping Files, Mapping File Types, Cookie file note.] implementing a cookie sync with us through the use of a pixel",
  "support": [
   {
    "source_id": "IDN-LR-S08",
    "passage": "authenticated, cookieless inventory",
    "locator": "Authenticated Traffic Solution, introduction"
   },
   {
    "source_id": "IDN-E-S18",
    "passage": "implementing a cookie sync with us through the use of a pixel",
    "locator": "RampID Mapping Files, Mapping File Types, Cookie file note."
   }
  ],
  "scope_time": "Product pages read 2026-11-11",
  "scope_geo": "US and other markets as specified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "The offer describes cookieless authenticated inventory. The mapping-file page calls for a cookie-sync pixel for cookie mappings. The ATS security guide also expressly describes an optional third-party-cookie endpoint. Neither coexistence nor this endpoint establishes a dated change in Chrome practice. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. Scope and limitations retained below.",
  "limitations": "Different workflows. No like-for-like pre/post policy-event guide pair was identified in the scoped screen. No direction of change or policy causation can be assigned from these pages.",
  "final_wording": "LiveRamp describes ATS for authenticated inventory without third-party cookies and also documents an optional third-party-cookie endpoint for ATS. Its separate cookie-to-RampID mapping-file workflow uses a cookie-sync pixel. These sources do not date a change in either workflow.",
  "counterevidence": "The older ATS security guide also mentions an optional third-party-cookie endpoint. It gives no before/after change.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-LR-F15",
  "headline": false,
  "claim": "AWS documents a MediaTailor example that sends a viewer’s hashed email to LiveRamp ATS and requires a domain placement ID and active agreement.",
  "chapter": "",
  "source_ids": [
   "IDN-LR-S14"
  ],
  "passage": "An active LiveRamp Authenticated Traffic Solution (ATS) agreement and a placement ID for your domain.",
  "support": [
   {
    "source_id": "IDN-LR-S14",
    "passage": "An active LiveRamp Authenticated Traffic Solution (ATS) agreement and a placement ID for your domain.",
    "locator": "Prerequisites, second bullet; Walkthrough: Enrich ad requests with LiveRamp identity data using MediaTailor Monetization Functions."
   }
  ],
  "scope_time": "2026-05-28",
  "scope_geo": "AWS workflow; viewer country not specified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The AWS walkthrough needs an active ATS agreement, a domain placement ID and a viewer hash. Its sample also includes consent parameters and shows an envelope passed on ad requests. AWS does not name a live end-customer deployment or measured household outcome. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "The external platform is a commercial integrator. The example gives an implementable route, not a count of actual viewers, purchases or campaigns.",
  "final_wording": "AWS documents a MediaTailor example that sends a viewer’s hashed email to LiveRamp ATS and requires a domain placement ID and active agreement.",
  "counterevidence": "A client app must supply the hashed email at session initialization.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-LR-F16",
  "headline": false,
  "claim": "LiveRamp’s publisher ATS documents tie service to a statement of work and limit passing the envelope to enabled parties; service fees under its general terms are specified in the order form.",
  "chapter": "8, 12",
  "source_ids": [
   "IDN-LR-S15",
   "IDN-LR-S10",
   "IDN-LR-S13",
   "IDN-VLR-S01"
  ],
  "passage": "[IDN-LR-S15, Introductory paragraph] When you execute an SOW for Authenticated Traffic Solution [IDN-LR-S10, Section 3(b) Restrictions, p. 2] Publisher may not pass the RAMPID Envelope to non-RAMPID enabled platforms [IDN-LR-S13, Section 1.1 Services] Each Order Form will identify and describe the Services and associated fees",
  "support": [
   {
    "source_id": "IDN-LR-S15",
    "passage": "When you execute an SOW for Authenticated Traffic Solution",
    "locator": "Introductory paragraph"
   },
   {
    "source_id": "IDN-LR-S10",
    "passage": "Publisher may not pass the RAMPID Envelope to non-RAMPID enabled platforms",
    "locator": "Section 3(b) Restrictions, p. 2"
   },
   {
    "source_id": "IDN-LR-S13",
    "passage": "Each Order Form will identify and describe the Services and associated fees",
    "locator": "Section 1.1 Services"
   }
  ],
  "scope_time": "2020 general ATS terms and public contract texts read 2026-11-11",
  "scope_geo": "US/general terms, country restrictions apply",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "The publisher SOW and its referenced terms govern the licence and recipients. A separate umbrella agreement calls for fees to be identified in the relevant order. On a 2021 earnings call the CEO said the strategy was to drive usage and cross-sales without charging publishers or media-platform partners for ATS. None of these sources fixes a current per-envelope fee. The corrected claim combines written contractual records with a separately attributed historical statement of commercial intent. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "Sample and umbrella terms give no universal dollar rate or executed buyer price. A fee line varies by order.",
  "final_wording": "LiveRamp’s publisher ATS form limits envelope use to enabled parties under a statement of work. Its separate general service terms put any associated fees in the order form. In 2021 its CEO said LiveRamp did not intend to charge publishers or media-platform partners for ATS and expected more platform use and cross-sales.",
  "counterevidence": "In May 2021, the CEO said LiveRamp expected platform usage and cross-sales to benefit without charging publishers or media-platform partners for ATS. That historical position does not set a current order price.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-LR-F17",
  "headline": false,
  "claim": "Publicis acquired LiveRamp Holdings through MMS USA Holdings on November 2, 2026, and trading in LiveRamp common stock stopped before the NYSE opened that day.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S02",
   "IDN-D-S03"
  ],
  "passage": "[IDN-D-S02, Items 2.01, 3.01 and 5.01] removed from trading on the NYSE [IDN-D-S03, Part III, identification of MMS USA Holdings] a wholly owned subsidiary of Publicis Groupe S.A.",
  "support": [
   {
    "source_id": "IDN-D-S02",
    "passage": "removed from trading on the NYSE",
    "locator": "Items 2.01, 3.01 and 5.01"
   },
   {
    "source_id": "IDN-D-S03",
    "passage": "a wholly owned subsidiary of Publicis Groupe S.A.",
    "locator": "Part III, identification of MMS USA Holdings"
   }
  ],
  "scope_time": "2026-11-02 closing; checked 2026-11-11",
  "scope_geo": "US target, French ultimate parent",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "November 2 Form 8-K identifies the surviving corporation, MMS as direct parent and Publicis as ultimate owner. It confirms removal from trading before the NYSE opened. The November 10 notification subsequently says Form 25 was filed and that securities were no longer listed or traded. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. Scope and limitations retained below.",
  "limitations": "The surviving company is a wholly owned direct subsidiary of MMS USA Holdings. Ownership is separate from product-level revenues or technical integration.",
  "final_wording": "Publicis acquired LiveRamp Holdings through MMS USA Holdings on November 2, 2026, and trading in LiveRamp common stock stopped before the NYSE opened that day.",
  "counterevidence": "The still-visible historical FAQ uses RAMP in the present tense. The closing filing and November 10 filing supersede it.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-LR-F18",
  "headline": false,
  "claim": "LiveRamp reported $812.9 million in consolidated revenue for the year ended March 31, 2026 and $214.0 million for the quarter ended June 30, 2026.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S04",
   "IDN-LR-S16"
  ],
  "passage": "[IDN-D-S04, Item 7, Revenues; Note 16 (Segment and Geographic Information), one operating segment] Total revenues were $812.9 million for the twelve months ended March 31, 2026 [IDN-LR-S16, Item 2, Revenues] Total revenues were $214.0 million for the three months ended June 30, 2026",
  "support": [
   {
    "source_id": "IDN-D-S04",
    "passage": "Total revenues were $812.9 million for the twelve months ended March 31, 2026",
    "locator": "Item 7, Revenues; Note 16 (Segment and Geographic Information), one operating segment"
   },
   {
    "source_id": "IDN-LR-S16",
    "passage": "Total revenues were $214.0 million for the three months ended June 30, 2026",
    "locator": "Item 2, Revenues"
   }
  ],
  "scope_time": "FY ended 2026-03-31; quarter ended 2026-06-30",
  "scope_geo": "Worldwide consolidated registrant",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Income statements (in thousands) show 812,940 in the March fiscal year and 213,986 in the June quarter. Both round as stated in millions. These are worldwide consolidated revenues before the closing; the quarterly statements are unaudited. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. Scope and limitations retained below.",
  "limitations": "One reported operating segment. Neither period gives standalone RampID or ATS revenue. FY and the following quarter are different intervals.",
  "final_wording": "LiveRamp reported $812.9 million in consolidated revenue for the year ended March 31, 2026 and $214.0 million for the quarter ended June 30, 2026.",
  "counterevidence": "The later September-quarter notification does not supply audited product revenues.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-LR-F19",
  "headline": false,
  "claim": "On November 10, 2026, LiveRamp notified the SEC that it had been unable to file its September-quarter 10-Q on time after the acquisition required reassessing its auditor relationship.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S03"
  ],
  "passage": "required the Registrant to reassess its auditor relationship",
  "support": [
   {
    "source_id": "IDN-D-S03",
    "passage": "required the Registrant to reassess its auditor relationship",
    "locator": "Form 12b-25, Part III and signature date"
   }
  ],
  "scope_time": "10-Q due for three months ended 2026-09-30; notice 2026-11-10",
  "scope_geo": "US registrant",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The November 10 signature and Part III say the acquisition before the filing deadline required reassessment of the auditor relationship with respect to the new owners. This was a delay notification for the September quarter. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. Scope and limitations retained below.",
  "limitations": "The late-filing notice is not the missing quarterly report. The profile uses the March annual and June interim figures as dated.",
  "final_wording": "On November 10, 2026, LiveRamp notified the SEC that it had been unable to file its September-quarter 10-Q on time after the acquisition required reassessing its auditor relationship.",
  "counterevidence": "The notice distinguishes the November closing from the September reporting period.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-LR-F20",
  "headline": false,
  "claim": "The FTC issued an interim Order to Maintain Assets on October 19 requiring continued access to LiveRamp standalone services, while its separate proposed five-year order remained under public comment at the cutoff.",
  "chapter": "9",
  "source_ids": [
   "IDN-LR-S18",
   "IDN-LR-S19",
   "IDN-LR-S17",
   "IDN-VLR-S02"
  ],
  "passage": "[IDN-LR-S18, Section II.D pp. 2–3; issued October 19 on p. 9; XI termination] continued access to LiveRamp’s standalone products and services [IDN-LR-S19, Part I, p. 1, five years and comment period] proposed Decision and Order [IDN-LR-S17, Case Status, C-4841; October 19 filings] Pending",
  "support": [
   {
    "source_id": "IDN-LR-S18",
    "passage": "continued access to LiveRamp’s standalone products and services",
    "locator": "Section II.D pp. 2–3; issued October 19 on p. 9; XI termination"
   },
   {
    "source_id": "IDN-LR-S19",
    "passage": "proposed Decision and Order",
    "locator": "Part I, p. 1, five years and comment period"
   },
   {
    "source_id": "IDN-LR-S17",
    "passage": "Pending",
    "locator": "Case Status, C-4841; October 19 filings"
   }
  ],
  "scope_time": "Order issued 2026-10-19; docket checked 2026-11-11",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The Commission actually issued the interim order on October 19. The contemporaneous analysis calls the separate five-year remedy proposed, and the official October 23 Federal Register notice sets November 23 as the deadline. The merger closed November 2, while docket C-4841 still showed pending. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. Scope and limitations retained below.",
  "limitations": "A competition remedy. The interim order includes confidentiality safeguards. These records establish duties, not completed changes to RampID data handling. The final proposed decision is a separate instrument.",
  "final_wording": "The FTC issued an interim Order to Maintain Assets on October 19 requiring continued access to LiveRamp standalone services, while its separate proposed five-year order remained under public comment at the cutoff.",
  "counterevidence": "The merits proposal and partner expectations cannot be read as proof of operational compliance.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-LR-F21",
  "headline": false,
  "claim": "Open Rights Group reported complaints to the UK ICO and French CNIL in February 2024 following its commissioned review of European RampID processing documentation.",
  "chapter": "9",
  "source_ids": [
   "IDN-LR-S20",
   "IDN-LR-S07"
  ],
  "passage": "[IDN-LR-S20, Opening paragraph, also names CNIL] Today, Open Rights Group has submitted complaints [IDN-LR-S07, Report details; subtitle and 2023 research period] commissioned by Open Rights Group",
  "support": [
   {
    "source_id": "IDN-LR-S20",
    "passage": "Today, Open Rights Group has submitted complaints",
    "locator": "Opening paragraph, also names CNIL"
   },
   {
    "source_id": "IDN-LR-S07",
    "passage": "commissioned by Open Rights Group",
    "locator": "Report details; subtitle and 2023 research period"
   }
  ],
  "scope_time": "Research 2023-09; complaints reported 2024-02-28",
  "scope_geo": "UK and France",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "ORG announced two submissions on February 28, 2024; the linked European research was commissioned by ORG and based on a September 2023 review of software documentation. It is evidence of allegations and third-party criticism, not an ICO/CNIL finding or an independent accuracy study. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. Scope and limitations retained below.",
  "limitations": "The complainant is the source. A documentary critique is distinct from a regulator ruling or US product validation. The screen identified no linked decision plus separate implemented change for these complaints.",
  "final_wording": "Open Rights Group reported complaints to the UK ICO and French CNIL in February 2024 following its commissioned review of European RampID processing documentation.",
  "counterevidence": "The FTC merger remedy concerns competition in the US and is a separate proceeding.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-LR-F22",
  "headline": false,
  "claim": "The group’s US services terms identify LiveRamp, Inc. as the Delaware contracting entity with a San Francisco principal place of business; LiveRamp Holdings, Inc. is the merger registrant.",
  "chapter": "8",
  "source_ids": [
   "IDN-LR-S13",
   "IDN-D-S02"
  ],
  "passage": "[IDN-LR-S13, Opening paragraph, principal place of business] LiveRamp, Inc., a Delaware corporation [IDN-D-S02, Item 2.01, parties] LiveRamp Holdings, Inc.",
  "support": [
   {
    "source_id": "IDN-LR-S13",
    "passage": "LiveRamp, Inc., a Delaware corporation",
    "locator": "Opening paragraph, principal place of business"
   },
   {
    "source_id": "IDN-D-S02",
    "passage": "LiveRamp Holdings, Inc.",
    "locator": "Item 2.01, parties"
   }
  ],
  "scope_time": "Terms and closing filing read 2026-11-11",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "The umbrella order-form terms specifically identify LiveRamp, Inc., its Delaware incorporation and San Francisco principal place of business. The merger filing identifies LiveRamp Holdings, Inc. as the acquired SEC registrant. A service contract and the subsidiary chain are separate records. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Directly attributed to the named records within the stated scope. Scope and limitations retained below.",
  "limitations": "Specific signed contracts can name other entities, particularly outside the US. The US umbrella terms do not establish a universal contracting entity worldwide.",
  "final_wording": "The group’s US services terms identify LiveRamp, Inc. as the Delaware contracting entity with a San Francisco principal place of business; LiveRamp Holdings, Inc. is the merger registrant.",
  "counterevidence": "The legal names denote two distinct roles.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-LR-F23",
  "headline": false,
  "claim": "LiveRamp’s investor FAQ dates the operating business to 2012, Acxiom’s purchase to 2014 and its return to standalone status to October 1, 2018.",
  "chapter": "",
  "source_ids": [
   "IDN-LR-S21"
  ],
  "passage": "LiveRamp was founded in 2012 and was acquired by Acxiom in 2014.",
  "support": [
   {
    "source_id": "IDN-LR-S21",
    "passage": "LiveRamp was founded in 2012 and was acquired by Acxiom in 2014.",
    "locator": "When was LiveRamp incorporated, and in which state?"
   }
  ],
  "scope_time": "Historical account, 2012–2018",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The FAQ attributes 2012, 2014 and October 1, 2018 to the business history. Its separately displayed ticker answer has been superseded by the November filings. No corporate charter or RampID launch date is inferred. Passage and scope checked against the reopened original.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Directly attributed to the named records within the stated scope. The cited protocol or duty describes prescribed behavior.",
  "limitations": "This is issuer history for the business. It is not the date the pseudonymous identifier or ATS launched.",
  "final_wording": "LiveRamp’s investor FAQ dates the operating business to 2012, Acxiom’s purchase to 2014 and its return to standalone status to October 1, 2018.",
  "counterevidence": "The historical standalone description ended with the November 2026 Publicis transaction.",
  "stream": "liveramp-rampid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F01",
  "headline": false,
  "claim": "The Trade Desk, Inc., originally incorporated in November 2009, reports as a Nevada corporation with principal offices in Ventura, California and Nasdaq-listed Class A shares under TTD.",
  "chapter": "",
  "source_ids": [
   "IDN-D-S18",
   "IDN-UID-S16"
  ],
  "passage": "[IDN-D-S18, FY2025 Form 10-K, Note 1, Organization and Description of Business] November 2009 [IDN-UID-S16, Form 10-Q cover, jurisdiction, principal executive offices and securities table] Ventura, California 93001",
  "support": [
   {
    "source_id": "IDN-D-S18",
    "passage": "November 2009",
    "locator": "FY2025 Form 10-K, Note 1, Organization and Description of Business"
   },
   {
    "source_id": "IDN-UID-S16",
    "passage": "Ventura, California 93001",
    "locator": "Form 10-Q cover, jurisdiction, principal executive offices and securities table"
   }
  ],
  "scope_time": "Originally incorporated November 2009. Latest cover signed 2026-11-09.",
  "scope_geo": "US issuer",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The FY25 organization note dates incorporation to November 2009. Both filing covers identify the Nevada registrant and its Ventura principal executive offices. The securities table identifies Class A stock, Nasdaq and TTD. These are corporate attributes.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "The registrant is the company. UID2 is a framework and operating service.",
  "final_wording": "The Trade Desk, Inc., originally incorporated in November 2009, reports as a Nevada corporation with principal offices in Ventura, California and Nasdaq-listed Class A shares under TTD.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F02",
  "headline": false,
  "claim": "For FY2025 The Trade Desk reported $2,896,284,000 in worldwide consolidated revenue in one advertising technology segment. Its platform fees generally depend on client spend and it also earns from services and data. The filings give no separate UID2 revenue.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S18",
   "IDN-UID-S16"
  ],
  "passage": "[IDN-D-S18, Consolidated Statements of Operations, Revenue, FY2025 column, USD thousands. Note 12, Segment and Geographic Information, one segment.] 2,896,284 [IDN-UID-S16, Part I, Item 2, Executive Summary. Note on Segment Information, consolidated advertising technology business.] platform fee generally based on a percentage",
  "support": [
   {
    "source_id": "IDN-D-S18",
    "passage": "2,896,284",
    "locator": "Consolidated Statements of Operations, Revenue, FY2025 column, USD thousands. Note 12, Segment and Geographic Information, one segment."
   },
   {
    "source_id": "IDN-UID-S16",
    "passage": "platform fee generally based on a percentage",
    "locator": "Part I, Item 2, Executive Summary. Note on Segment Information, consolidated advertising technology business."
   }
  ],
  "scope_time": "FY ended 2025-12-31. Q3 2026 filing confirms platform fee model.",
  "scope_geo": "Global consolidated issuer",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The FY25 filings give one consolidated advertising-technology platform segment. The audited revenue table is in thousands of US dollars; 2,896,284 thousand equals $2,896,284,000. MD&A describes platform fees based on spend and service/data revenue. Neither filing itemizes UID2 receipts.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "Gross platform spend includes inventory and other items. Neither the platform fee nor the FY2025 total identifies a UID2 price, budget or profit.",
  "final_wording": "For FY2025 The Trade Desk reported $2,896,284,000 in worldwide consolidated revenue in one advertising technology segment. Its platform fees generally depend on client spend and it also earns from services and data. The filings give no separate UID2 revenue.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F03",
  "headline": false,
  "claim": "The Trade Desk says it committed internal resources to building UID2. Its investor slide labels Identity Alliance as its separate proprietary cross-device graph.",
  "chapter": "",
  "source_ids": [
   "IDN-UID-S10"
  ],
  "passage": "[IDN-UID-S10, Q4 2024 investor presentation, identity slide headed “The what and why…”] We dedicated internal resources to build the technology. [IDN-UID-S10, Q4 2024 investor presentation, following slide headed “A better foundation for identity”, footnote on Identity Alliance] Our proprietary cross-device graph.",
  "support": [
   {
    "source_id": "IDN-UID-S10",
    "passage": "We dedicated internal resources to build the technology.",
    "locator": "Q4 2024 investor presentation, identity slide headed “The what and why…”"
   },
   {
    "source_id": "IDN-UID-S10",
    "passage": "Our proprietary cross-device graph.",
    "locator": "Q4 2024 investor presentation, following slide headed “A better foundation for identity”, footnote on Identity Alliance"
   }
  ],
  "scope_time": "Q4 2024 investor presentation, issued in 2025",
  "scope_geo": "Global corporate statement",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The investor deck attributes development resources to TTD. The next slide footnotes Identity Alliance as TTD’s proprietary cross-device graph. The words are verified in the original indexed issuer PDF. The original second locator points to the preceding slide. Only the supporting locator changes. No budget or UID2 household-link capability follows from the graph slide.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "The issuer supplies no UID2 investment amount on this slide. Do not transfer Identity Alliance’s household or device links to the UID2 row.",
  "final_wording": "The Trade Desk says it committed internal resources to building UID2. Its investor slide labels Identity Alliance as its separate proprietary cross-device graph.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F04",
  "headline": false,
  "claim": "IAB Tech Lab recorded The Trade Desk’s UID2 source-code contribution to the PRAM technical working group in May 2021, then said in February 2022 that it would steward the broader Tokenization Framework and decline the UID2 technical administrator role at that time.",
  "chapter": "",
  "source_ids": [
   "IDN-UID-S08",
   "IDN-UID-S09"
  ],
  "passage": "[IDN-UID-S08, Opening paragraph, PRAM working group and contribution] contributing the Unified ID 2.0 (UID 2.0) source code to the Technical Working Group [IDN-UID-S09, Paragraph beginning “Given this expanded mission” and preceding Tokenization Framework paragraphs] it will not be taking on the technical administrator role for UID 2.0 at this point",
  "support": [
   {
    "source_id": "IDN-UID-S08",
    "passage": "contributing the Unified ID 2.0 (UID 2.0) source code to the Technical Working Group",
    "locator": "Opening paragraph, PRAM working group and contribution"
   },
   {
    "source_id": "IDN-UID-S09",
    "passage": "it will not be taking on the technical administrator role for UID 2.0 at this point",
    "locator": "Paragraph beginning “Given this expanded mission” and preceding Tokenization Framework paragraphs"
   }
  ],
  "scope_time": "May 2021 and February 2022",
  "scope_geo": "US industry initiative",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "IAB Tech Lab describes the code contribution to the PRAM working group. Article metadata dates that publication May 25, 2021. The February 28, 2022 update names the broader Tokenization Framework and expressly declines UID2 technical administration at that point.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "Source-code and standards stewardship are historical roles. The present service and access roles are documented separately.",
  "final_wording": "IAB Tech Lab recorded The Trade Desk’s UID2 source-code contribution to the PRAM technical working group in May 2021, then said in February 2022 that it would steward the broader Tokenization Framework and decline the UID2 technical administrator role at that time.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F05",
  "headline": false,
  "claim": "The UID2 guide names The Trade Desk as Core Administrator and a public operator. The core supplies keys and salts. Public or private operators create raw IDs and encrypt them for token issuance. Publishers send tokens via SSPs, and DSPs can use them for bidding.",
  "chapter": "1, 8, 11",
  "source_ids": [
   "IDN-UID-S01"
  ],
  "passage": "[IDN-UID-S01, UID2 component services, Core Administrator and Operators rows, including public/private operators] An organization (currently, The Trade Desk) that manages the UID2 Core Service [IDN-UID-S01, UID2 external participants, Publishers and DSPs rows] propagate UID2 tokens to the bidstream via SSPs",
  "support": [
   {
    "source_id": "IDN-UID-S01",
    "passage": "An organization (currently, The Trade Desk) that manages the UID2 Core Service",
    "locator": "UID2 component services, Core Administrator and Operators rows, including public/private operators"
   },
   {
    "source_id": "IDN-UID-S01",
    "passage": "propagate UID2 tokens to the bidstream via SSPs",
    "locator": "UID2 external participants, Publishers and DSPs rows"
   }
  ],
  "scope_time": "As read on 2026-11-11",
  "scope_geo": "US-relevant UID2 implementation",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The role tables assign The Trade Desk both the Core Administrator and a Public Operator role. They assign salts, keys, hashing and encryption to the named components and describe issuer-to-DSP carriage through SSPs. These are documented roles, uncounted here as observed transactions.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "Publisher or SSO supplies the input and requests issuance. A publisher may also operate a private instance. The Trade Desk’s DSP is a recipient in a separate capacity.",
  "final_wording": "The UID2 guide names The Trade Desk as Core Administrator and a public operator. The core supplies keys and salts. Public or private operators create raw IDs and encrypt them for token issuance. Publishers send tokens via SSPs, and DSPs can use them for bidding.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F06",
  "headline": false,
  "claim": "UID2’s permission matrix lets a publisher request tokens, a mapper submit email addresses, phone numbers or their hashes for raw IDs, and a bidder decrypt tokens. The FAQ illustrates an encrypted token in user.ext.eids with uidapi.com as its source.",
  "chapter": "1, 2, 11",
  "source_ids": [
   "IDN-UID-S02",
   "IDN-UID-S03"
  ],
  "passage": "[IDN-UID-S02, API permissions, Generator, Mapper and Bidder rows. Client-side web integrations use a separate credential.] Permission to decrypt UID2 tokens coming in from the bidstream [IDN-UID-S03, FAQ, What does a UID2 token look like in the bidstream?, example user.ext.eids[].uids[].id] \"source\": \"uidapi.com\"",
  "support": [
   {
    "source_id": "IDN-UID-S02",
    "passage": "Permission to decrypt UID2 tokens coming in from the bidstream",
    "locator": "API permissions, Generator, Mapper and Bidder rows. Client-side web integrations use a separate credential."
   },
   {
    "source_id": "IDN-UID-S03",
    "passage": "\"source\": \"uidapi.com\"",
    "locator": "FAQ, What does a UID2 token look like in the bidstream?, example user.ext.eids[].uids[].id"
   }
  ],
  "scope_time": "As read on 2026-11-11",
  "scope_geo": "US-relevant UID2 implementation",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The credential-permission table describes Generator, Mapper and Bidder, and separately identifies the client-side publisher credential route. The FAQ sample carries the token at user.ext.eids[].uids[].id with uidapi.com as source. The sample provides no auction execution or consent enforcement.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "This is the product’s illustrated transport. A field and API permission do not prove a bid, a clearing price or a user’s choices.",
  "final_wording": "UID2’s permission matrix lets a publisher request tokens, a mapper submit email addresses, phone numbers or their hashes for raw IDs, and a bidder decrypt tokens. The FAQ illustrates an encrypted token in user.ext.eids with uidapi.com as its source.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F07",
  "headline": false,
  "claim": "The UID2 FAQ says two participants mapping the same email at the same time obtain the same raw ID. Newly generated advertising tokens differ even for that raw ID. It recommends hourly token refresh and a daily audience check against raw-ID refresh timestamps, with raw IDs changing roughly yearly.",
  "chapter": "2",
  "source_ids": [
   "IDN-UID-S03",
   "IDN-UID-S05"
  ],
  "passage": "[IDN-UID-S03, FAQs, Does the same DII always result in the same raw UID2? and token uniqueness and rotation policy] the same raw UID2 in response [IDN-UID-S03, FAQs for publishers, If I choose to manually refresh the token…] The recommended refresh interval is hourly. [IDN-UID-S03, FAQs for advertisers and data providers, How often should raw UID2s be refreshed for incremental updates?] roughly once per year [IDN-UID-S05, Response body elements, r field. The timestamp can advance without a raw-ID change.] might or might not change",
  "support": [
   {
    "source_id": "IDN-UID-S03",
    "passage": "the same raw UID2 in response",
    "locator": "FAQs, Does the same DII always result in the same raw UID2? and token uniqueness and rotation policy"
   },
   {
    "source_id": "IDN-UID-S03",
    "passage": "The recommended refresh interval is hourly.",
    "locator": "FAQs for publishers, If I choose to manually refresh the token…"
   },
   {
    "source_id": "IDN-UID-S03",
    "passage": "roughly once per year",
    "locator": "FAQs for advertisers and data providers, How often should raw UID2s be refreshed for incremental updates?"
   },
   {
    "source_id": "IDN-UID-S05",
    "passage": "might or might not change",
    "locator": "Response body elements, r field. The timestamp can advance without a raw-ID change."
   }
  ],
  "scope_time": "As read on 2026-11-11",
  "scope_geo": "US-relevant UID2 implementation",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The FAQ matches the same DII at the same instant across participants, differentiates token values by generation, recommends an hourly cadence specifically for manual publisher refresh, and daily audience timestamp checks. It describes approximate yearly raw-ID change. V3 remapping after a timestamp can leave the raw ID unchanged.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "Refresh guidance is not a token expiry guarantee or a measure of whether the email belongs to the same person over time.",
  "final_wording": "UID2 says participants mapping the same email at the same time get the same raw ID. Each generated advertising token differs. The FAQ recommends hourly refresh for publishers who refresh tokens manually, and daily raw-ID timestamp checks for audience updates. A raw ID changes roughly once a year.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-UID-F08",
  "headline": false,
  "claim": "On July 11, 2025 UID2 announced v3 identity mapping for advertisers and data providers. The migration guide replaces v2 salt-bucket monitoring with per-ID refresh timestamps and makes the prior raw ID available for 90 days after rotation.",
  "chapter": "2",
  "source_ids": [
   "IDN-UID-S04",
   "IDN-UID-S05"
  ],
  "passage": "[IDN-UID-S04, Q3 2025, POST /v3/identity/map (endpoint doc), July 11, 2025] a new version of the Identity Map API (v3) [IDN-UID-S05, Migration from POST /v2/identity/map, Version 3 improvements, Key differences and Required changes. Code examples show both parsers.] You can see the previous UID2 for 90 days after rotation.",
  "support": [
   {
    "source_id": "IDN-UID-S04",
    "passage": "a new version of the Identity Map API (v3)",
    "locator": "Q3 2025, POST /v3/identity/map (endpoint doc), July 11, 2025"
   },
   {
    "source_id": "IDN-UID-S05",
    "passage": "You can see the previous UID2 for 90 days after rotation.",
    "locator": "Migration from POST /v2/identity/map, Version 3 improvements, Key differences and Required changes. Code examples show both parsers."
   }
  ],
  "scope_time": "V3 release July 11, 2025. Current v3 guide last updated November 11, 2026.",
  "scope_geo": "US-relevant UID2 implementation",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The change log dates the v3 release to July 11, 2025. A mapper can replace its old salt-bucket refresh checks with a timestamp for each mapping. A previous ID can be returned for 90 days after rotation. V2 is still documented. The current v3 page footer gives Nov 11, 2026. Finding wording stands; the scope-time field and capability date are corrected separately.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "Applies to the mapping route. Ninety days is the prior-ID lookup window, not a token lifetime.",
  "final_wording": "On July 11, 2025 UID2 announced v3 identity mapping for advertisers and data providers. The migration guide replaces v2 salt-bucket monitoring with per-ID refresh timestamps and makes the prior raw ID available for 90 days after rotation.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F09",
  "headline": false,
  "claim": "The Trade Desk’s UID2 license matrix covers approved API access to generate and maintain identifiers. Under its separate CRM onboarding route, advertisers or their agencies may target within their platform account but do not receive the underlying UID2-to-customer mapping.",
  "chapter": "1, 8, 12",
  "source_ids": [
   "IDN-UID-S11",
   "IDN-U-S03"
  ],
  "passage": "[IDN-UID-S11, v10.1.24, UID2 API and CRM Data Onboarding Service columns] will not receive a mapping of the Company Data to associated UID2s. [IDN-U-S03, Public Operator: Benefits, then Private Operators and Summary] There is no cost, to the participant, for using a Public Operator.",
  "support": [
   {
    "source_id": "IDN-UID-S11",
    "passage": "will not receive a mapping of the Company Data to associated UID2s.",
    "locator": "v10.1.24, UID2 API and CRM Data Onboarding Service columns"
   },
   {
    "source_id": "IDN-U-S03",
    "passage": "There is no cost, to the participant, for using a Public Operator.",
    "locator": "Public Operator: Benefits, then Private Operators and Summary"
   }
  ],
  "scope_time": "License matrix v10.1.24 as read at cutoff",
  "scope_geo": "US-relevant UID2 implementation",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The approval matrix distinguishes an API that returns associated identifiers from an accessory CRM service that deposits them into the platform account and does not provide the customer a mapping. The separate operator reference expressly offers public-operator use at no cost to the participant, under contract with credentials. A private operator supplies its own resources. The disclosed public-operator price cannot be extended to TTD media buys or third-party services.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "The license matrix provides no fee schedule. The operator guide separately discloses a free public-operator route and participant-funded private infrastructure. Ancillary fees, commercial arrangements and product margin remain undisclosed in these records.",
  "final_wording": "The Trade Desk’s license matrix distinguishes approved API access from CRM onboarding. CRM onboarding permits targeting in the platform account without returning the IDs or customer mapping. UID2 also says a contracted participant can use a Public Operator at no charge. Private operators provide their own hosting and engineering resources.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F10",
  "headline": false,
  "claim": "UID2 lists production operator endpoints in Ohio and Oregon. Roku describes using The Trade Desk’s DSP to activate against Roku first-party data through Roku Exchange.",
  "chapter": "11",
  "source_ids": [
   "IDN-U-S04",
   "IDN-I-S08"
  ],
  "passage": "[IDN-U-S04, UID2 integration and production environments, Ohio and Oregon production rows rather than testing row] AWS US East (Ohio) [IDN-I-S08, Roku Advertising, Benefits for advertisers, “Here’s how it works”] The Trade Desk's advertisers can use UID2 to activate against Roku’s first-party data through Roku Exchange.",
  "support": [
   {
    "source_id": "IDN-U-S04",
    "passage": "AWS US East (Ohio)",
    "locator": "UID2 integration and production environments, Ohio and Oregon production rows rather than testing row"
   },
   {
    "source_id": "IDN-I-S08",
    "passage": "The Trade Desk's advertisers can use UID2 to activate against Roku’s first-party data through Roku Exchange.",
    "locator": "Roku Advertising, Benefits for advertisers, “Here’s how it works”"
   }
  ],
  "scope_time": "Roku published 2024-08-01. Endpoint table checked 2026-11-11.",
  "scope_geo": "US production regions. Roku US publisher-facing account.",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "US East (Ohio) and US West (Oregon) are marked production separately from the integration endpoint. In its August 2024 account, Roku announced UID2 adoption and described how TTD advertisers could buy Roku Media through Roku Exchange. The article identifies available activation rather than disclosing bid logs for a particular advertiser.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "An available endpoint is not a measured volume. Roku is a commercial participant and supplies no UID2-only transaction logs.",
  "final_wording": "UID2 lists production operator endpoints in Ohio and Oregon. In August 2024, Roku announced UID2 adoption across its premium streaming inventory and described how The Trade Desk advertisers could activate against Roku first-party data through Roku Exchange.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F11",
  "headline": false,
  "claim": "The Trade Desk distinguishes UID2 and EUID by namespace and territory. EUID covers the listed European territories, including the UK. Its publisher guidance describes joint control at creation and return, and asks for specific, affirmative consent to convert the identifier.",
  "chapter": "",
  "source_ids": [
   "IDN-UID-S06",
   "IDN-U-S05",
   "IDN-UID-S07"
  ],
  "passage": "[IDN-UID-S06, Unified IDs, introduction and EUID vs. UID2. Each framework has its own namespace.] each framework offers user transparency and privacy controls [IDN-U-S05, EUID areas of coverage, EU countries, non-EU EEA and additional countries/regions] United Kingdom [IDN-UID-S07, Publisher information §1. See §§4.2–4.3 for affirmative consent and the limits of existing CMP consents.] a joint controller with each publisher that submits an identifier for conversion into an EUID",
  "support": [
   {
    "source_id": "IDN-UID-S06",
    "passage": "each framework offers user transparency and privacy controls",
    "locator": "Unified IDs, introduction and EUID vs. UID2. Each framework has its own namespace."
   },
   {
    "source_id": "IDN-U-S05",
    "passage": "United Kingdom",
    "locator": "EUID areas of coverage, EU countries, non-EU EEA and additional countries/regions"
   },
   {
    "source_id": "IDN-UID-S07",
    "passage": "a joint controller with each publisher that submits an identifier for conversion into an EUID",
    "locator": "Publisher information §1. See §§4.2–4.3 for affirmative consent and the limits of existing CMP consents."
   }
  ],
  "scope_time": "As read on 2026-11-11",
  "scope_geo": "EUID’s listed Europe/UK territories and separate UID2 service",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "TTD’s glossary gives EUID and UID2 separate namespaces. The geographic list expressly includes the UK. EUID publisher guidance assigns joint control for creation and return to the rule owner and submitting publisher and asks for specific consent by affirmative action. The publisher’s later advertising use is outside that joint responsibility.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "This is the operator’s description of EUID obligations. It does not establish a US EUID service, a court ruling or consent for a US UID2 impression.",
  "final_wording": "The Trade Desk distinguishes UID2 and EUID by namespace and territory. EUID covers the listed European territories, including the UK. Its publisher guidance describes joint control at creation and return, and asks for specific, affirmative consent to convert the identifier.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-UID-F12",
  "headline": false,
  "claim": "A site-level opt-out stops that participant from generating UID2 for the user and is not relayed across UID2. A consumer can use an email address or phone number in the global portal. The operator sends opt-out responses when publishers generate or refresh and distributes a separate DSP webhook.",
  "chapter": "4, 12",
  "source_ids": [
   "IDN-A-S08",
   "IDN-UID-S18"
  ],
  "passage": "[IDN-A-S08, User opt-out, Difference between opting out from a single participant and opting out of UID2, and Opt-out workflow steps 1–3/table] via a webhook provided for the purpose [IDN-UID-S18, Disclosure of data by UID2 administrator, first bullet. Policy covers administrator only.] so they can honor your choice",
  "support": [
   {
    "source_id": "IDN-A-S08",
    "passage": "via a webhook provided for the purpose",
    "locator": "User opt-out, Difference between opting out from a single participant and opting out of UID2, and Opt-out workflow steps 1–3/table"
   },
   {
    "source_id": "IDN-UID-S18",
    "passage": "so they can honor your choice",
    "locator": "Disclosure of data by UID2 administrator, first bullet. Policy covers administrator only."
   }
  ],
  "scope_time": "As read on 2026-11-11",
  "scope_geo": "US-relevant UID2 implementation",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "review_note": "The US opt-out guide requires a participant to stop generating UID2 after its own opt-out; the local decision is not relayed to UID2. Portal requests apply to one input at a time. The operator describes per-identifier responses on token generate/refresh and DSP webhook dispatch. Implementation and participant compliance are not observed.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "The operator acknowledges propagation delay. Its notice refers readers to each participant’s privacy policy for that participant’s practices.",
  "final_wording": "UID2 requires a participant to stop generating the identifier after a site-level opt-out. That request is not relayed to UID2. For ecosystem-wide suppression, a consumer submits each email or phone number separately. The guide describes opt-out responses to publisher generation or refresh requests and a webhook to DSPs.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-UID-F13",
  "headline": false,
  "claim": "UID2’s DSP guide describes a webhook sent typically within a few minutes, with the raw ID and opt-out time. It instructs a bidder to suppress UID2 for that user but permits another identifier or a no-bid.",
  "chapter": "4, 12",
  "source_ids": [
   "IDN-A-S09"
  ],
  "passage": "[IDN-A-S09, Honor user opt-outs, Opt-out webhook and identity / timestamp rows] typically within a few minutes [IDN-A-S09, Bidding opt-out logic, immediately after DSP opt-out check diagram] If the user has opted out, the UID2 must not be used for RTB.",
  "support": [
   {
    "source_id": "IDN-A-S09",
    "passage": "typically within a few minutes",
    "locator": "Honor user opt-outs, Opt-out webhook and identity / timestamp rows"
   },
   {
    "source_id": "IDN-A-S09",
    "passage": "If the user has opted out, the UID2 must not be used for RTB.",
    "locator": "Bidding opt-out logic, immediately after DSP opt-out check diagram"
   }
  ],
  "scope_time": "As read on 2026-11-11",
  "scope_geo": "US-relevant UID2 implementation",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The DSP guide specifies the raw ID, Unix-seconds opt-out time and usual dispatch within a few minutes. The recipient must exclude that opted-out UID2 from RTB; it may bid using a different ID or decline to bid. The evidence is a DSP instruction, not an enforcement audit.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "Typical webhook dispatch time is not a maximum, a deletion guarantee for past impressions, or proof all recipients acted. This out-of-band procedure does not establish TCF/GPP handling on an observed request.",
  "final_wording": "UID2’s DSP guide describes a webhook sent typically within a few minutes, with the raw ID and opt-out time. It instructs a bidder to suppress UID2 for that user but permits another identifier or a no-bid.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-UID-F14",
  "headline": false,
  "claim": "Google announced on April 22, 2025 that it would retain Chrome’s existing third-party cookie choice. On October 17 it announced the retirement of named technologies including Topics and Protected Audience, subject to platform phase-out processes.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S01",
   "IDN-E-S02"
  ],
  "passage": "[IDN-E-S01, April 22 post, paragraph beginning “Taking all of these factors”] maintain our current approach to offering users third-party cookie choice in Chrome [IDN-E-S02, October 17 post, list of technologies to retire and paragraph immediately following] We will follow Chrome and Android processes for phasing out these technologies",
  "support": [
   {
    "source_id": "IDN-E-S01",
    "passage": "maintain our current approach to offering users third-party cookie choice in Chrome",
    "locator": "April 22 post, paragraph beginning “Taking all of these factors”"
   },
   {
    "source_id": "IDN-E-S02",
    "passage": "We will follow Chrome and Android processes for phasing out these technologies",
    "locator": "October 17 post, list of technologies to retire and paragraph immediately following"
   }
  ],
  "scope_time": "2025-04-22 and 2025-10-17",
  "scope_geo": "Global Chrome platform policy",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Google’s April 22 decision retained its Chrome cookie choice with no new standalone prompt. Its October 17 announcement lists Topics and Protected Audience for retirement and says phase-outs follow platform processes. Neither establishes a UID2 change.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "These are Google decisions. Neither directly demonstrates a UID2 product change or a migration back to cookie syncing.",
  "final_wording": "Google announced on April 22, 2025 that it would retain Chrome’s existing third-party cookie choice. On October 17 it announced the retirement of named technologies including Topics and Protected Audience, subject to platform phase-out processes.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-UID-F15",
  "headline": false,
  "claim": "After WebKit described its identity-resolution network block on October 19, 2026, UID2’s Prebid guide identified client-side uidapi.com requests as blocked on all iOS 27+ browsers and Safari on macOS 27+. It directs affected publishers to server-side token handling.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S14",
   "IDN-E-S16",
   "IDN-UID-S04"
  ],
  "passage": "[IDN-E-S14, Blocking Identity Resolution Infrastructure, October 19, protection scope] Safari and WebKit block network access to identity resolution infrastructure to prevent cross-site tracking. [IDN-E-S16, Web integration limitations on iOS 27 and macOS 27, affected browsers and Action required] WebKit blocks client-side requests to [IDN-UID-S04, Documentation updates, Q4 2026, iOS 27 and macOS 27 web integration limitations.] October 9, 2026",
  "support": [
   {
    "source_id": "IDN-E-S14",
    "passage": "Safari and WebKit block network access to identity resolution infrastructure to prevent cross-site tracking.",
    "locator": "Blocking Identity Resolution Infrastructure, October 19, protection scope"
   },
   {
    "source_id": "IDN-E-S16",
    "passage": "WebKit blocks client-side requests to",
    "locator": "Web integration limitations on iOS 27 and macOS 27, affected browsers and Action required"
   },
   {
    "source_id": "IDN-UID-S04",
    "passage": "October 9, 2026",
    "locator": "Documentation updates, Q4 2026, iOS 27 and macOS 27 web integration limitations."
   }
  ],
  "scope_time": "UID2 product notice October 9, 2026. WebKit post October 19, 2026. Prebid guide reopened November 11, 2026.",
  "scope_geo": "Specified Apple OS/browser paths worldwide including US",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "contradicted",
  "review_note": "The UID2 release log specifically dates its product warning to October 9, 2026. The WebKit announcement is dated October 19. The current Prebid guide confirms the affected browsers and advises server-side generation and refresh. The product documentation predates the cited WebKit announcement. The original text reverses the dates. Neither source measures affected impressions.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "UID2 describes lost browser generation and refresh. The sources do not report server-side adoption or lost impressions.",
  "final_wording": "On October 9, 2026, UID2 documented that browser requests to uidapi.com were blocked in all iOS 27+ browsers and in Safari on macOS 27+. Its Prebid guide directs publishers on those paths to generate and refresh tokens server-side. On October 19, WebKit described its broader domain-level protection.",
  "counterevidence": "UID2 dated its own notice October 9, ten days before the WebKit post. No adoption or lost-impression count was disclosed.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-UID-F16",
  "headline": false,
  "claim": "For one US retailer, Deep Sync reports 73.2 million matched UID2 records (51%) before enrichment and 94.4 million (66%) afterward. Its nominal CRM file held 141.7 million records. The case does not explain the whole-percent rounding or exact destination denominator.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S30"
  ],
  "passage": "94.4M · 66%",
  "support": [
   {
    "source_id": "IDN-C-S30",
    "passage": "94.4M · 66%",
    "locator": "The challenge, nominal file. The results, Social & identity platforms, UID2 row."
   }
  ],
  "scope_time": "Public by cutoff. Observation and campaign dates unspecified.",
  "scope_geo": "One unnamed US national mass-market retailer",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The enrichment provider shows one retailer’s 141.7m-record file and prints 73.2m matched (51%) and 94.4m (66%) for the UID2 destination. Dividing the displayed counts by the nominal file would not reproduce the printed whole percentages using ordinary rounding. Eligibility, rounding, deduplication and test period remain unknown. Attribution to the case author is verified. Its status as financial sponsor is not disclosed.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The originating seller gives the nominal file and exact row, so the attribution is clear.",
  "limitations": "Seller of enrichment reports the comparison. Counts refer to CRM records, not distinct people, eligible US impressions or confirmed identities.",
  "final_wording": "For one US retailer, Deep Sync reports 73.2 million matched UID2 records (51%) before enrichment and 94.4 million (66%) afterward. Its nominal CRM file held 141.7 million records. The case does not explain the whole-percent rounding or exact destination denominator.",
  "counterevidence": "A positive match count can coexist with incorrect person assignments. Exact per-destination eligibility and rounding are unstated.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "Same retailer’s original and enriched files at five destinations. No labelled truth set, error matrix or randomized holdout disclosed.",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-UID-F17",
  "headline": false,
  "claim": "In its 2024 US report, The Trade Desk says HP used device-registration data for a UID2 campaign on Disney+ and Hulu through its DSP and reached 8% of an estimated 12.5 million target households.",
  "chapter": "3",
  "source_ids": [
   "IDN-UID-S12"
  ],
  "passage": "reaching 8% of an estimated 12.5 million targeted households",
  "support": [
   {
    "source_id": "IDN-UID-S12",
    "passage": "reaching 8% of an estimated 12.5 million targeted households",
    "locator": "Identity Report 2024 | USA, p. 8, How HP activated its first-party data with a new ID, campaign description and result"
   }
  ],
  "scope_time": "2024 publication. Campaign window unspecified.",
  "scope_geo": "US edition, one HP CTV campaign",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The named HP case identifies its own device registration inputs and its use of The Trade Desk to reach Disney+ and Hulu audiences. The denominator was an estimated 12.5m targeted households, and the publisher of the US-edition report says the campaign reached 8%. The report methodology names The Trade Desk Intelligence and Hypothesis Group, seven brand/agency leaders, and four interview markets. Campaign geography and dates are not separately specified. The claim correctly recognizes the edition. Do not relabel it a verified US-only campaign or a national reach estimate.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "The denominator is HP’s estimated target group. No US inventory universe, unique national UID2 base, labelled test or incremental counterfactual is supplied.",
  "final_wording": "In its 2024 US report, The Trade Desk says HP used device-registration data for a UID2 campaign on Disney+ and Hulu through its DSP and reached 8% of an estimated 12.5 million target households.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "Platform-published HP case in an interview report by The Trade Desk Intelligence and Hypothesis Group. Q1 2024 fieldwork covered seven brand and agency leaders in four markets. HP’s campaign dates, geography and control group were unspecified.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-UID-F18",
  "headline": false,
  "claim": "An unfunded 2025 academic study examined technical documentation and code for identity architectures including UID2. It described how a credential-derived token permits linkage across participants. The study did not test UID2 assignments against labelled people or households.",
  "chapter": "",
  "source_ids": [
   "IDN-UID-S13"
  ],
  "passage": "[IDN-UID-S13, p. 1, Funding and Competing Interests] The authors did not receive any funding for this research. [IDN-UID-S13, p. 1, Abstract. See §4.1.1 for UID2 token and DSP mechanism.] We analyse technical documentation and code repositories",
  "support": [
   {
    "source_id": "IDN-UID-S13",
    "passage": "The authors did not receive any funding for this research.",
    "locator": "p. 1, Funding and Competing Interests"
   },
   {
    "source_id": "IDN-UID-S13",
    "passage": "We analyse technical documentation and code repositories",
    "locator": "p. 1, Abstract. See §4.1.1 for UID2 token and DSP mechanism."
   }
  ],
  "scope_time": "Published 2025-08-06",
  "scope_geo": "Peer-reviewed architecture analysis, cross-market",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "Sivan-Sevilla, Parham and McGuigan identify their funding and conflicts, describe a literature/code/document study and discuss UID2 explicitly at §4.1.1. There is no sample of verified individuals, no tested false link rate and no demonstration of current DSP compliance. Synthesis here describes the architecture, not independent measurement.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "Independent analysis of the design, with no per-person ground truth, pass rate or observation of current recipient compliance.",
  "final_wording": "An unfunded 2025 academic study examined technical documentation and code for identity architectures including UID2. It described how a credential-derived token permits linkage across participants. The study did not test UID2 assignments against labelled people or households.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "Literature review and typology applied to public technical descriptions and code repositories. UID2 examined as one architecture.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-UID-F19",
  "headline": false,
  "claim": "In May 2026 AdExchanger reported that an unnamed CTV publisher operating privately found an encryption error after three months. A Trade Desk engineering executive confirmed the faulty tokens could not be reconciled for targeting.",
  "chapter": "",
  "source_ids": [
   "IDN-UID-S14"
  ],
  "passage": "would have made its UID2 tokens irreconcilable for ad targeting",
  "support": [
   {
    "source_id": "IDN-UID-S14",
    "passage": "would have made its UID2 tokens irreconcilable for ad targeting",
    "locator": "Encryption error, publisher account and confirmation from Waseem Basheer. Duration under Fixing the error changed nothing."
   }
  ],
  "scope_time": "Article 2026-05-07. Incident dates not specified.",
  "scope_geo": "One unnamed national CTV publisher, market not specified",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "AdExchanger quotes an anonymous private-operator publisher that says it addressed faulty encryption after three months. Its named TTD engineering source agrees that those tokens were irreconcilable for targeting. The publisher reported no noticeable revenue movement and TTD said it lacked enough information to flag the issue. No independent logs verify frequency or financial effect.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "The named engineering executive corroborates the technical consequence. The publisher alone supplies the time to discovery.",
  "limitations": "Reporter interviewed both sides. The report contains no bid-log sample, general failure rate or paid-media counterfactual.",
  "final_wording": "In May 2026 AdExchanger reported that an unnamed CTV publisher operating privately found an encryption error after three months. A Trade Desk engineering executive confirmed the faulty tokens could not be reconciled for targeting.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "Interviews with an anonymous publisher and named company officers. No released test dataset.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-UID-F20",
  "headline": false,
  "claim": "FTC technology staff cautioned in July 2024 that hashing personal information does not make it anonymous. The staff post does not name UID2 or impose a UID2-specific remedy.",
  "chapter": "",
  "source_ids": [
   "IDN-UID-S17"
  ],
  "passage": "Companies should not act or claim as if hashing personal information renders it anonymized.",
  "support": [
   {
    "source_id": "IDN-UID-S17",
    "passage": "Companies should not act or claim as if hashing personal information renders it anonymized.",
    "locator": "Office of Technology blog, paragraph beginning “This logic is as old as it is flawed”"
   }
  ],
  "scope_time": "2024-07-24",
  "scope_geo": "United States",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "FTC Office of Technology staff warn that hashing does not assure anonymity and discuss other companies. The visible article byline displays July 24, 2024. It neither names UID2 nor imposes an obligation on the product.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "General regulatory context. No finding of a product-specific violation or technical capability.",
  "final_wording": "FTC technology staff cautioned in July 2024 that hashing personal information does not make it anonymous. The staff post does not name UID2 or impose a UID2-specific remedy.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-UID-F21",
  "headline": false,
  "claim": "Lead plaintiffs’ counsel says a private US privacy action alleges that UID2 and data-broker partnerships enabled profiles without consent. In its November 9, 2026 Form 10-Q The Trade Desk reported the case in discovery after the court denied dismissal except for the declaratory-relief claim.",
  "chapter": "",
  "source_ids": [
   "IDN-UID-S15",
   "IDN-UID-S16"
  ],
  "passage": "[IDN-UID-S15, Privacy & Cybersecurity, In re The Trade Desk, Inc. Data Privacy Litigation] Plaintiffs allege the company’s “Unified ID 2.0” system and data broker partnerships [IDN-UID-S16, Litigation Related to the Company’s Platform and Related Offerings, N.D. Cal. No. 3:25-cv-2889, December 2025 dismissal order and current status] The case is now in the discovery phase",
  "support": [
   {
    "source_id": "IDN-UID-S15",
    "passage": "Plaintiffs allege the company’s “Unified ID 2.0” system and data broker partnerships",
    "locator": "Privacy & Cybersecurity, In re The Trade Desk, Inc. Data Privacy Litigation"
   },
   {
    "source_id": "IDN-UID-S16",
    "passage": "The case is now in the discovery phase",
    "locator": "Litigation Related to the Company’s Platform and Related Offerings, N.D. Cal. No. 3:25-cv-2889, December 2025 dismissal order and current status"
   }
  ],
  "scope_time": "July 18, 2025 consolidated amended complaint, December 18, 2025 motion order. Status in filing signed November 9, 2026.",
  "scope_geo": "US private federal litigation, Northern District of California",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "Plaintiffs’ counsel identifies UID2 and data-broker partnerships in the allegations. Note 11 of the 10-Q signed November 9, 2026 records a partial December 2025 dismissal ruling, the declaratory claim dismissed with prejudice and discovery in the private action. The issuer disputes the claims. No evidence of a court-ordered UID2 operational change.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "The company disputes the claims. Discovery and partial dismissal are procedural. This private action is outside H6’s regulator population and the IQ.",
  "final_wording": "Lead plaintiffs’ counsel says a private US privacy action alleges that UID2 and data-broker partnerships enabled profiles without consent. In its November 9, 2026 Form 10-Q The Trade Desk reported the case in discovery after the court denied dismissal except for the declaratory-relief claim.",
  "counterevidence": "The company disputes the pending claims. The court dismissed the declaratory-relief claim with prejudice, and one plaintiff was later dismissed without prejudice.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-UID-F22",
  "headline": false,
  "claim": "The HP reach case counts targeted households, Deep Sync counts matched CRM records and the academic analysis examines architecture. In these sources the review found no product-wide US coverage estimate with a national eligible base or independent UID2 accuracy test against labelled individuals.",
  "chapter": "",
  "source_ids": [
   "IDN-UID-S12",
   "IDN-C-S30",
   "IDN-UID-S13"
  ],
  "passage": "[IDN-UID-S12, US Identity Report, p. 8, HP case denominator] estimated 12.5 million targeted households [IDN-C-S30, Results, UID2 row, original-file column] 73.2M · 51% [IDN-UID-S13, Abstract, data and approach. §4.1.1, UID2.] technical documentation and code repositories",
  "support": [
   {
    "source_id": "IDN-UID-S12",
    "passage": "estimated 12.5 million targeted households",
    "locator": "US Identity Report, p. 8, HP case denominator"
   },
   {
    "source_id": "IDN-C-S30",
    "passage": "73.2M · 51%",
    "locator": "Results, UID2 row, original-file column"
   },
   {
    "source_id": "IDN-UID-S13",
    "passage": "technical documentation and code repositories",
    "locator": "Abstract, data and approach. §4.1.1, UID2."
   }
  ],
  "scope_time": "Review bounded to named documents by 2026-11-11",
  "scope_geo": "Two US-relevant commercial cases and one academic architecture review",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "HP reports reach as a fraction of its campaign target households; Deep Sync reports matched retailer CRM records; the 2025 academic source examines code and documentation. None supplies a nationwide eligible UID2 population or tests person-link accuracy against labeled individuals. A search for named independent accuracy tests yielded generic or anonymous-provider benchmarks, without refuting this bounded statement.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "The search also screened issuer documentation and web queries recorded below. This is an evidence boundary. Distinct US people, all eligible US auctions and recipient correctness are different possible denominators.",
  "final_wording": "The HP reach case counts targeted households, Deep Sync counts matched CRM records and the academic analysis examines architecture. In these sources the review found no product-wide US coverage estimate with a national eligible base or independent UID2 accuracy test against labelled individuals.",
  "counterevidence": "The cases establish bounded usage and reported reach or match counts. The adverse publisher report describes one failure without an error-rate denominator.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-UID-F23",
  "headline": false,
  "claim": "The UID2 administrator’s privacy notice covers its own role, including sharing an opt-out choice with participants. The publisher/DSP guides describe suppression, but neither the FAQ’s sample bid request nor the DSP guide demonstrates per-impression transfer and enforcement of a TCF or GPP string.",
  "chapter": "4",
  "source_ids": [
   "IDN-UID-S18",
   "IDN-UID-S03",
   "IDN-A-S09",
   "IDN-VUID-S02"
  ],
  "passage": "[IDN-UID-S18, Introduction, scope and Disclosure of data by UID2 administrator] only in its role as UID2 administrator [IDN-UID-S03, FAQ, What does a UID2 token look like in the bidstream?, entire example] \"source\": \"uidapi.com\" [IDN-A-S09, Bidding opt-out logic and separate opt-out webhook] Bidding opt-out logic [IDN-VUID-S02, §2.2 Processor and Controller Responsibilities; §§2.3, 3, 6 and Exhibit A] TD is a Processor or the equivalent of Company Personal Data",
  "support": [
   {
    "source_id": "IDN-UID-S18",
    "passage": "only in its role as UID2 administrator",
    "locator": "Introduction, scope and Disclosure of data by UID2 administrator"
   },
   {
    "source_id": "IDN-UID-S03",
    "passage": "\"source\": \"uidapi.com\"",
    "locator": "FAQ, What does a UID2 token look like in the bidstream?, entire example"
   },
   {
    "source_id": "IDN-A-S09",
    "passage": "Bidding opt-out logic",
    "locator": "Bidding opt-out logic and separate opt-out webhook"
   },
   {
    "source_id": "IDN-VUID-S02",
    "passage": "TD is a Processor or the equivalent of Company Personal Data",
    "locator": "§2.2 Processor and Controller Responsibilities; §§2.3, 3, 6 and Exhibit A"
   }
  ],
  "scope_time": "Privacy notice effective 2025-04-01. Guides sampled 2026-11-11.",
  "scope_geo": "US-relevant UID2 implementation",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_with_qualification",
  "review_note": "The administrator policy describes opt-out recording and onward notices. The FAQ sample illustrates identifier carriage and the DSP guide specifies an out-of-band withdrawal action. No observed TCF/GPP string evaluation per impression is shown. Separately, the UID2 client DPA assigns processing roles for Company Personal Data, cooperation on rights requests and conditional data destruction. It provides no observed downstream erasure.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "The cited source describes the named role, field or evidence directly.",
  "limitations": "The bidder guide and FAQ do not demonstrate purpose-string handling on a US impression. The separate client DPA assigns processing obligations for covered company data. It is not an audit or a promise of erasure throughout the recipient chain.",
  "final_wording": "The UID2 administrator says it records opt-outs and shares them with participants. Its US-relevant client addendum separately describes the company and The Trade Desk as controller and processor for covered customer data. These terms and the bidder guide describe obligations. The FAQ’s sample bid request and DSP guide do not demonstrate per-impression TCF or GPP enforcement.",
  "counterevidence": "None found in the cited record for this narrow description.",
  "stream": "ttd-uid2",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-YAH-F01",
  "headline": false,
  "claim": "The US ConnectID agreement names Yahoo Ad Tech LLC as signatory and lists its principal place of business in New York, New York.",
  "chapter": "8",
  "source_ids": [
   "IDN-YAH-S01"
  ],
  "passage": "Yahoo Ad Tech LLC",
  "support": [
   {
    "source_id": "IDN-YAH-S01",
    "passage": "Yahoo Ad Tech LLC",
    "locator": "Opening paragraph, legal name and principal place of business, 770 Broadway, New York, NY 10003"
   }
  ],
  "scope_time": "2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The preamble names the Delaware LLC, supplies its New York principal address and permits performance by an affiliate. The address is for the signatory. Public agreement takes effect on each company’s acceptance and allows delivery by Yahoo affiliates. It does not show which affiliate delivered a particular impression.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "Public agreement takes effect on each company’s acceptance and allows delivery by Yahoo affiliates. It does not show which affiliate delivered a particular impression.",
  "final_wording": "The US ConnectID agreement names Yahoo Ad Tech LLC as signatory and lists its principal place of business in New York, New York.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F02",
  "headline": false,
  "claim": "At the September 2021 closing, Apollo Funds took over Yahoo and Verizon retained a 10% interest; Verizon later reported $4.1 billion of cash proceeds net of cash transferred for the sale of Verizon Media.",
  "chapter": "8",
  "source_ids": [
   "IDN-D-S17",
   "IDN-YAH-S02",
   "IDN-VYAH-S05"
  ],
  "passage": "[IDN-D-S17, Apollo closing release, p. 1, first paragraph including retained percentage] under Apollo Funds [IDN-YAH-S02, Form 10-K, Cash Flows Used in Investing Activities, Disposition of Business (net cash transferred). Compare Note 3, Verizon Media Divestiture (cash at close).] $4.1 billion, net of cash transferred",
  "support": [
   {
    "source_id": "IDN-D-S17",
    "passage": "under Apollo Funds",
    "locator": "Apollo closing release, p. 1, first paragraph including retained percentage"
   },
   {
    "source_id": "IDN-YAH-S02",
    "passage": "$4.1 billion, net of cash transferred",
    "locator": "Form 10-K, Cash Flows Used in Investing Activities, Disposition of Business (net cash transferred). Compare Note 3, Verizon Media Divestiture (cash at close)."
   }
  ],
  "scope_time": "Closing 2021-09-01; fiscal 2021",
  "scope_geo": "United States buying task",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "Apollo identified its affiliate-managed funds as acquirers of the former Verizon Media and Verizon’s retained stake at closing. Verizon reports $4.1bn net in liquidity disclosures and $4.3bn at closing before the cash-transferred adjustment in Note 3. The 2025 docket identifies the signatory’s disclosed parent. Dates distinguish group ownership at closing and the later signatory disclosure. Neither supplies a current cap table or ID-specific financials.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "Cash proceeds are one component of consideration. This amount does not value ConnectID, disclose its sales, or establish a current equity percentage.",
  "final_wording": "Apollo’s funds acquired Yahoo in September 2021, when Verizon retained 10%. Verizon reported $4.1 billion in cash proceeds net of cash transferred for Verizon Media. In September 2025 Yahoo Ad Tech LLC identified College Parent, L.P. as its corporate parent in a court disclosure.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F03",
  "headline": false,
  "claim": "Verizon Media launched ConnectID in December 2020 as a way to buy and measure ads without third-party cookies, using its graph built from direct consumer relationships.",
  "chapter": "",
  "source_ids": [
   "IDN-C-S24"
  ],
  "passage": "all without third-party cookies",
  "support": [
   {
    "source_id": "IDN-C-S24",
    "passage": "all without third-party cookies",
    "locator": "2020-12-01, paragraph preceding the three launch bullets; Diverse ID graph bullet identifies the graph and deterministic source data"
   }
  ],
  "scope_time": "2020-12-01",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Verizon’s dated launch release markets ad buying, measurement and optimization without third-party cookies and attributes its graph to direct relationships. It supplies no edge-level lineage or independent result. The launch supports US offer eligibility for H8. The launch, later Yahoo DSP account and ATS rollout do not supply an operational map of the predecessor’s core edges or a documented independent rebuild. Lineage is unknown.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "The launch supports US offer eligibility for H8. The launch, later Yahoo DSP account and ATS rollout do not supply an operational map of the predecessor’s core edges or a documented independent rebuild. Lineage is unknown.",
  "final_wording": "Verizon Media launched ConnectID in December 2020 as a way to buy and measure ads without third-party cookies, using its graph built from direct consumer relationships.",
  "counterevidence": "The explicit graph reference supports a graph connection at launch. It lacks an edge migration or namespace crosswalk proving retention of the primary linkage.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H8"
 },
 {
  "id": "IDN-YAH-F04",
  "headline": false,
  "claim": "Yahoo’s US agreement defines the returned value as an encrypted identifier under a company- or publisher-specific key and restricts sharing to the agreed supply relationship.",
  "chapter": "abstract, 8",
  "source_ids": [
   "IDN-YAH-S01"
  ],
  "passage": "[IDN-YAH-S01, Service §1(c), company-specific or publisher-specific encryption, approved publisher and sharing clauses] a Publisher-specific key [IDN-YAH-S01, §1(c), final sentence on sharing] non-approved Publishers",
  "support": [
   {
    "source_id": "IDN-YAH-S01",
    "passage": "a Publisher-specific key",
    "locator": "Service §1(c), company-specific or publisher-specific encryption, approved publisher and sharing clauses"
   },
   {
    "source_id": "IDN-YAH-S01",
    "passage": "non-approved Publishers",
    "locator": "§1(c), final sentence on sharing"
   }
  ],
  "scope_time": "2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Under the contract the returned ID is an encrypted hashed identifier keyed by company or publisher. The company must include it on bids to Yahoo; its right to distribute is restricted to agreed participants. The text does not grant unrelated DSPs use rights. The contract describes one implementation. Encryption specifies the representation, not how Yahoo verifies that two graph records belong to the same person.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "The contract describes one implementation. Encryption specifies the representation, not how Yahoo verifies that two graph records belong to the same person.",
  "final_wording": "Yahoo’s US agreement defines the returned value as an encrypted identifier under a company- or publisher-specific key and restricts sharing to the agreed supply relationship.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F05",
  "headline": false,
  "claim": "Yahoo’s server integration accepts a publisher ID and a hashed email, then supplies the ConnectID for the ad request; its Prebid workflow can instead start with a domain-specific user identifier.",
  "chapter": "4",
  "source_ids": [
   "IDN-C-S23",
   "IDN-YAH-S16",
   "IDN-YAH-S15"
  ],
  "passage": "[IDN-C-S23, Get the ConnectID, required he and pi; integration overview, then ConnectID in OpenRTB and the v2.5/v2.6 examples] hashed user email and the Publisher ID [IDN-YAH-S16, Configuration table, params.puid] A domain-specific user identifier such as a first-party cookie. [IDN-YAH-S15, Configure Hashed Emails to Generate ConnectIDs, Important note for Magnite wrapper when email unavailable] the ConnectID script auto-generates first-party cookies",
  "support": [
   {
    "source_id": "IDN-C-S23",
    "passage": "hashed user email and the Publisher ID",
    "locator": "Get the ConnectID, required he and pi; integration overview, then ConnectID in OpenRTB and the v2.5/v2.6 examples"
   },
   {
    "source_id": "IDN-YAH-S16",
    "passage": "A domain-specific user identifier such as a first-party cookie.",
    "locator": "Configuration table, params.puid"
   },
   {
    "source_id": "IDN-YAH-S15",
    "passage": "the ConnectID script auto-generates first-party cookies",
    "locator": "Configure Hashed Emails to Generate ConnectIDs, Important note for Magnite wrapper when email unavailable"
   }
  ],
  "scope_time": "2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "The authenticated S2S endpoint requires he and pi and documents a ConnectID on an eligible request. Success may instead carry an empty object under opt-out. The Prebid configuration accepts puid, and the Magnite guide describes first-party-cookie fallback. Documented interface behavior only. Neither successful issuance nor first-party state establishes person-link correctness.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "A domain-specific input does not show that Yahoo found an authenticated person. The API example identifies its issuing and receiving system, not every recipient’s production configuration.",
  "final_wording": "Yahoo documents an authenticated server lookup using a hashed email and publisher ID. An eligible lookup can return a ConnectID for a bid, while an opted-out lookup returns an empty object. Its Prebid route can instead start with a domain-specific publisher ID.",
  "counterevidence": "Prebid and Magnite support a non-email path. Requiring an email on the server lookup does not establish a universal requirement.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F06",
  "headline": false,
  "claim": "Yahoo’s JavaScript module returns a cached ConnectID if available and refreshes it when missing or stale; for its server integration Yahoo recommends a 24-hour cache.",
  "chapter": "",
  "source_ids": [
   "IDN-YAH-S05",
   "IDN-C-S23",
   "IDN-VYAH-S04"
  ],
  "passage": "[IDN-YAH-S05, Implementation overview, callback and asynchronous refetch bullet] a locally cached ConnectID (when available) [IDN-C-S23, Caching, first paragraph (24 hours). Best Practices, instruction to refresh for recent consent changes. OAuth lifetime is covered separately.] ConnectID",
  "support": [
   {
    "source_id": "IDN-YAH-S05",
    "passage": "a locally cached ConnectID (when available)",
    "locator": "Implementation overview, callback and asynchronous refetch bullet"
   },
   {
    "source_id": "IDN-C-S23",
    "passage": "ConnectID",
    "locator": "Caching, first paragraph (24 hours). Best Practices, instruction to refresh for recent consent changes. OAuth lifetime is covered separately."
   }
  ],
  "scope_time": "2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "The standalone getIds module is documented to return a local cached value immediately and asynchronously fetch an absent or not-recent value. The S2S recommendation is a 24-hour cache. A distinct pinned Prebid module uses response TTL/default staleness logic and can hand the cached ID back with a refresh callback. Cache freshness is distinct from a guarantee that all recipients reject an old token.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "The 24-hour recommendation concerns the publisher’s S2S cache. In the examined Prebid client, a stale ID can accompany a resync; its client TTL does not establish downstream token validity, graph-edge age or maximum lifetime of a previously transmitted copy.",
  "final_wording": "Yahoo documents immediate use of the standalone JavaScript module’s cached ConnectID and an asynchronous fetch when it is missing or stale. It recommends a 24-hour server cache. A separately versioned Prebid module can return a cached value while refreshing it.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F07",
  "headline": false,
  "claim": "Yahoo instructs sites to honor user choices, provides an email confirmation form for opting out of ConnectID-based targeting, and documents an empty response for an opted-out server lookup.",
  "chapter": "4",
  "source_ids": [
   "IDN-YAH-S01",
   "IDN-YAH-S18",
   "IDN-C-S23"
  ],
  "passage": "[IDN-YAH-S01, Privacy Protections §2(a)–(b), collection, transmission and preference forwarding] relay applicable user privacy preferences to Yahoo [IDN-YAH-S18, Portal purpose text and confirmation email field] opt-out of targeted advertising based on Yahoo Connect ID [IDN-C-S23, GET Yahoo ConnectID, Query Parameters: gpp and gpp_sid. HTTP Status Return Codes, 200. Opt-Out Handling, empty object after opt-out.] ConnectID",
  "support": [
   {
    "source_id": "IDN-YAH-S01",
    "passage": "relay applicable user privacy preferences to Yahoo",
    "locator": "Privacy Protections §2(a)–(b), collection, transmission and preference forwarding"
   },
   {
    "source_id": "IDN-YAH-S18",
    "passage": "opt-out of targeted advertising based on Yahoo Connect ID",
    "locator": "Portal purpose text and confirmation email field"
   },
   {
    "source_id": "IDN-C-S23",
    "passage": "ConnectID",
    "locator": "GET Yahoo ConnectID, Query Parameters: gpp and gpp_sid. HTTP Status Return Codes, 200. Opt-Out Handling, empty object after opt-out."
   }
  ],
  "scope_time": "2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The agreement assigns notice, control and forwarding duties to the supplier; the inspected portal includes an email field for opt-out and confirmation. Yahoo’s S2S documentation specifies HTTP 200 with an empty JSON object after the stated opt-out. No live request or prior-copy erasure was observed. The publisher is responsible for controls and the applicable preferences. An empty response establishes suppression at lookup. It does not establish deletion from recipients that already received the token. No live opt-out transaction was performed.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "The service agreement assigns controls to publishers. The API specifies an empty result on a new opted-out lookup. No live request was tested, and removal of historical copies at recipients was not demonstrated.",
  "final_wording": "Yahoo instructs sites to honor user choices, provides an email confirmation form for opting out of ConnectID-based targeting, and documents an empty response for an opted-out server lookup.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-YAH-F08",
  "headline": false,
  "claim": "A publisher can also set a local opt-out flag that stops the ConnectID JavaScript module from issuing further IDs on that domain.",
  "chapter": "4",
  "source_ids": [
   "IDN-A-S13",
   "IDN-YAH-S04",
   "IDN-VYAH-S04"
  ],
  "passage": "[IDN-A-S13, Local-storage key connectIdOptOut, first paragraph and value 1] domain specific opt-out signal [IDN-YAH-S04, Honoring Privacy Choices, opt-out behavior] stop generating ConnectIDs for users who have opted-out",
  "support": [
   {
    "source_id": "IDN-A-S13",
    "passage": "domain specific opt-out signal",
    "locator": "Local-storage key connectIdOptOut, first paragraph and value 1"
   },
   {
    "source_id": "IDN-YAH-S04",
    "passage": "stop generating ConnectIDs for users who have opted-out",
    "locator": "Honoring Privacy Choices, opt-out behavior"
   }
  ],
  "scope_time": "2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The publisher example sets a domain-local storage value to 1 and describes disabling new JS generation. In the 2026 pinned Prebid code getId and decode check the same key and stop when the opt-out is read. Local browser enforcement and a vendor-described server rule do not show retrieval from downstream recipients.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "Device/domain control and the public email portal have different scopes. The local toggle describes future issuance, not retroactive cross-partner deletion.",
  "final_wording": "A publisher can also set a local opt-out flag that stops the ConnectID JavaScript module from issuing further IDs on that domain.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H3"
 },
 {
  "id": "IDN-YAH-F09",
  "headline": false,
  "claim": "Google lists ConnectID as a secure-signal provider and Yahoo instructs Ad Manager publishers to route it to Yahoo’s App & Display and Video bidders.",
  "chapter": "4, 12",
  "source_ids": [
   "IDN-YAH-S06",
   "IDN-YAH-S07"
  ],
  "passage": "[IDN-YAH-S06, Secure signals providers, RTB bidders table, Yahoo ConnectID row. Read App and Web, the three Web integration deployment columns, and Bidder availability (Authorized Buyers + Open Bidding).] Yahoo ConnectID [IDN-YAH-S07, Share ConnectID with Yahoo DSP, step 7 for Authorized Buyers; step 8 names Yahoo DSP as recipient] Yahoo - App & Display and Yahoo - Video",
  "support": [
   {
    "source_id": "IDN-YAH-S06",
    "passage": "Yahoo ConnectID",
    "locator": "Secure signals providers, RTB bidders table, Yahoo ConnectID row. Read App and Web, the three Web integration deployment columns, and Bidder availability (Authorized Buyers + Open Bidding)."
   },
   {
    "source_id": "IDN-YAH-S07",
    "passage": "Yahoo - App & Display and Yahoo - Video",
    "locator": "Share ConnectID with Yahoo DSP, step 7 for Authorized Buyers; step 8 names Yahoo DSP as recipient"
   }
  ],
  "scope_time": "2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "review_note": "Google’s provider row marks the signal supported for web and unsupported for app in this table. In the Authorized Buyers branch Yahoo names two Yahoo bidders. Open Bidding instead uses a signal-sharing toggle. Two bidder configurations in one operator’s DSP. Google’s table describes transport availability, not contract rights for each listed demand channel.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "This documents Google’s brokered transport and Yahoo’s two bidder names. It does not establish that Google Ads, Display & Video 360 or an unrelated DSP can consume the Yahoo ID. The two Yahoo endpoints represent one operator.",
  "final_wording": "Google lists ConnectID as a web secure signal. For Authorized Buyers, Yahoo tells Ad Manager publishers to select the Yahoo App & Display and Yahoo Video bidders. Its Open Bidding instructions use a sharing toggle.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F10",
  "headline": false,
  "claim": "Yahoo and LiveRamp announced an ATS route in October 2023; their July 2024 release described publisher availability, and Allen Media Group identified its own integration.",
  "chapter": "",
  "source_ids": [
   "IDN-U-S09",
   "IDN-YAH-S09"
  ],
  "passage": "[IDN-U-S09, October joint release, paragraph beginning Publishers who have adopted, and Yahoo DSP brand/customer passage] will be able to integrate with Yahoo ConnectID [IDN-YAH-S09, July 17, availability announcement, then Allen Media Group quotation] Our integration with Yahoo ConnectID, powered by LiveRamp",
  "support": [
   {
    "source_id": "IDN-U-S09",
    "passage": "will be able to integrate with Yahoo ConnectID",
    "locator": "October joint release, paragraph beginning Publishers who have adopted, and Yahoo DSP brand/customer passage"
   },
   {
    "source_id": "IDN-YAH-S09",
    "passage": "Our integration with Yahoo ConnectID, powered by LiveRamp",
    "locator": "July 17, availability announcement, then Allen Media Group quotation"
   }
  ],
  "scope_time": "2023-10-16 to 2024-07-17",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "October 2023 joint release describes an expanded partnership and planned access for ATS publishers. July 2024 issuer release calls the integration available and quotes the Allen Media Group vice president about its use. ATS eligibility and partner testimony do not count all eligible sites as live. The two announcements document stages of one partnership. They do not show all ATS domains adopted Yahoo ConnectID, that RampID and ConnectID are the same identifier, or that LiveRamp is another buying DSP.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "The two announcements document stages of one partnership. They do not show all ATS domains adopted Yahoo ConnectID, that RampID and ConnectID are the same identifier, or that LiveRamp is another buying DSP.",
  "final_wording": "Yahoo and LiveRamp announced an ATS route in October 2023; their July 2024 release described publisher availability, and Allen Media Group identified its own integration.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F11",
  "headline": false,
  "claim": "Yahoo’s October 2024 announcement identified Amazon Publisher Services, InMobi, Magnite and PubMatic as publisher integration routes, including bidding through Amazon’s Transparent Ad Marketplace.",
  "chapter": "12",
  "source_ids": [
   "IDN-YAH-S14"
  ],
  "passage": "[IDN-YAH-S14, Subheading and four partner sections; APS representative describes Connections Marketplace and Transparent Ad Marketplace] Amazon Publisher Services, InMobi Advertising, Magnite and PubMatic [IDN-YAH-S14, APS subsection before Scott Siegler quotation] available for bidding through APS’ Transparent Ad Marketplace",
  "support": [
   {
    "source_id": "IDN-YAH-S14",
    "passage": "Amazon Publisher Services, InMobi Advertising, Magnite and PubMatic",
    "locator": "Subheading and four partner sections; APS representative describes Connections Marketplace and Transparent Ad Marketplace"
   },
   {
    "source_id": "IDN-YAH-S14",
    "passage": "available for bidding through APS’ Transparent Ad Marketplace",
    "locator": "APS subsection before Scott Siegler quotation"
   }
  ],
  "scope_time": "2024-10-17",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The announcement identifies each partner, with specific ConnectID sections: APS Connections Marketplace and Transparent Ad Marketplace bidding, InMobi UnifID for in-app use, Magnite and PubMatic wrappers/SSPs. Amazon DSP is not identified as a consumer by the APS paragraphs. These are publisher access, in-app exchange or SSP paths. The release does not show Amazon DSP or four independent DSPs recognized the returned token. Includes named partner representatives in one release.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "These are publisher access, in-app exchange or SSP paths. The release does not show Amazon DSP or four independent DSPs recognized the returned token. Includes named partner representatives in one release.",
  "final_wording": "Yahoo’s October 2024 announcement identified Amazon Publisher Services, InMobi, Magnite and PubMatic as publisher integration routes, including bidding through Amazon’s Transparent Ad Marketplace.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F12",
  "headline": false,
  "claim": "Yahoo’s Merkle announcement describes advertisers selecting audiences built on Merkury IDs for activation in Yahoo DSP using ConnectID.",
  "chapter": "",
  "source_ids": [
   "IDN-YAH-S10"
  ],
  "passage": "activate them within Yahoo's DSP through Yahoo ConnectID",
  "support": [
   {
    "source_id": "IDN-YAH-S10",
    "passage": "activate them within Yahoo's DSP through Yahoo ConnectID",
    "locator": "October 28 release, paragraph beginning This collaboration and Merkury representative’s following quotation"
   }
  ],
  "scope_time": "2021-10-28",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Yahoo described Merkury audiences entering its DSP using ConnectID and exposure data flowing back. Merkle’s quoted representative participates in the announcement, which does not document an extra DSP or completed campaign. Merkle is the upstream audience/agency partner. This is a historical buyer workflow, with no buyer-signed purchase order, spend, or evidence of Merkury consuming ConnectID in its own DSP.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "Merkle is the upstream audience/agency partner. This is a historical buyer workflow, with no buyer-signed purchase order, spend, or evidence of Merkury consuming ConnectID in its own DSP.",
  "final_wording": "Yahoo’s Merkle announcement describes advertisers selecting audiences built on Merkury IDs for activation in Yahoo DSP using ConnectID.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F13",
  "headline": false,
  "claim": "In July 2026 Truthset said its Data Rated Audiences could be activated in Yahoo DSP through ConnectID; the accuracy ratings it described apply to its audiences.",
  "chapter": "",
  "source_ids": [
   "IDN-YAH-S11"
  ],
  "passage": "[IDN-YAH-S11, July 23, opening paragraph, named DSP and ID] activate Truthset’s Data Rated Audiences [IDN-YAH-S11, Following paragraph, immediately after the matching claim] Truthset’s audiences are independently scored for accuracy",
  "support": [
   {
    "source_id": "IDN-YAH-S11",
    "passage": "activate Truthset’s Data Rated Audiences",
    "locator": "July 23, opening paragraph, named DSP and ID"
   },
   {
    "source_id": "IDN-YAH-S11",
    "passage": "Truthset’s audiences are independently scored for accuracy",
    "locator": "Following paragraph, immediately after the matching claim"
   }
  ],
  "scope_time": "2026-07-23",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The integration partner says its own Data Rated Audiences can be used in Yahoo DSP with ConnectID. Its statements about scoring and 1:1 matching supply no truth-set labels, error counts or audit of Yahoo’s identity links. This partner announcement reports a buyer route, not a disinterested experiment with labeled correct and incorrect Yahoo person links. No such test appears in the screened partner, issuer and publisher records.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "This partner announcement reports a buyer route, not a disinterested experiment with labeled correct and incorrect Yahoo person links. No such test appears in the screened partner, issuer and publisher records.",
  "final_wording": "In July 2026 Truthset said its Data Rated Audiences could be activated in Yahoo DSP through ConnectID; the accuracy ratings it described apply to its audiences.",
  "counterevidence": "Truthset uses 1:1 matching language and says it scores audience accuracy; those statements concern the partner audience and activation method.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-YAH-F14",
  "headline": false,
  "claim": "Yahoo reported 232 million logged-in US users when it announced its Conversion API in April 2025 and described a US base of 213 million users in its October 2026 ConnectID article.",
  "chapter": "11",
  "source_ids": [
   "IDN-YAH-S12",
   "IDN-YAH-S13"
  ],
  "passage": "[IDN-YAH-S12, April 28 launch, opening two paragraphs and internal-data footnotes] 232 million logged-in users in the U.S. [IDN-YAH-S13, October 1, How Yahoo ConnectID Helps You Reach Your Goals; opening takeaways characterize these as logged-in users] 213 million users in the U.S.",
  "support": [
   {
    "source_id": "IDN-YAH-S12",
    "passage": "232 million logged-in users in the U.S.",
    "locator": "April 28 launch, opening two paragraphs and internal-data footnotes"
   },
   {
    "source_id": "IDN-YAH-S13",
    "passage": "213 million users in the U.S.",
    "locator": "October 1, How Yahoo ConnectID Helps You Reach Your Goals; opening takeaways characterize these as logged-in users"
   }
  ],
  "scope_time": "Publications 2025-04-28 and 2026-10-01; quantitative observation windows not specified",
  "scope_geo": "United States buying task",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "The April 28, 2025 CAPI launch uses 232 million U.S. logged-in users. The October 1, 2026 DSP article gives 213 million U.S. users and calls the base logged-in in its takeaways. No common counting window or deduplication rules are supplied. The publisher does not give a common counting window, deduplication method or eligible base. These are two issuer snapshots, not an estimate of unique reachable people on one campaign or proof of a measured decline.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "The publisher does not give a common counting window, deduplication method or eligible base. These are two issuer snapshots, not an estimate of unique reachable people on one campaign or proof of a measured decline.",
  "final_wording": "Yahoo reported 232 million logged-in US users when it announced its Conversion API in April 2025 and described a US base of 213 million users in its October 2026 ConnectID article.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "Issuer population descriptions. Sample, counted event, observation window, holdout, comparator and deduplication rule not disclosed in these passages.",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F15",
  "headline": false,
  "claim": "Mediavine said its Grow integration saw an 80% increase in eCPM on Safari and Firefox in November 2021.",
  "chapter": "",
  "source_ids": [
   "IDN-YAH-S08"
  ],
  "passage": "an 80% increase in eCPM rates on Safari and Firefox",
  "support": [
   {
    "source_id": "IDN-YAH-S08",
    "passage": "an 80% increase in eCPM rates on Safari and Firefox",
    "locator": "Newsroom post dated December 2, 2021; December 1 press dateline, first two paragraphs on eCPM and the Grow integration."
   }
  ],
  "scope_time": "November 2021 performance result; published 2021-12-01",
  "scope_geo": "US-based publisher network; measured traffic geography not specified",
  "figure_kind": "original",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "review_note": "Mediavine’s December 1, 2021 statement, posted December 2, says it saw an 80% November eCPM increase on Safari and Firefox when using ConnectID. Baseline, impression counts, holdout, location of all impressions and identity-error labels are unspecified. Mediavine participated in the integration. Its release does not define a counterfactual, impression count, sample geography or holdout, and does not test whether accepted person links were correct.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "Mediavine participated in the integration. Its release does not define a counterfactual, impression count, sample geography or holdout, and does not test whether accepted person links were correct.",
  "final_wording": "Mediavine said its Grow integration saw an 80% increase in eCPM on Safari and Firefox in November 2021.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "Publisher self-report for Safari and Firefox. Outcome is effective CPM. No specified comparison group, truth labels, error counts or uncertainty.",
  "claim_status": "actual",
  "hypothesis": "H2"
 },
 {
  "id": "IDN-YAH-F16",
  "headline": false,
  "claim": "Yahoo’s DataX file-match reporting and its ConnectID integration check measure different outcomes: one returns partner onboarding results and the other checks whether an ID appears on a bid request.",
  "chapter": "11, 13",
  "source_ids": [
   "IDN-C-S27",
   "IDN-YAH-S04"
  ],
  "passage": "[IDN-C-S27, Match Rates overview, immediately after the per-file and aggregated reporting statement] successful matched Partner IDs [IDN-YAH-S04, Implementation Verification, step 4 and yahoo.com EID payload check] Verify that ConnectID is successfully included in the ad requests.",
  "support": [
   {
    "source_id": "IDN-C-S27",
    "passage": "successful matched Partner IDs",
    "locator": "Match Rates overview, immediately after the per-file and aggregated reporting statement"
   },
   {
    "source_id": "IDN-YAH-S04",
    "passage": "Verify that ConnectID is successfully included in the ad requests.",
    "locator": "Implementation Verification, step 4 and yahoo.com EID payload check"
   }
  ],
  "scope_time": "2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "DataX reports per-job and aggregate counts in worked API examples and downloads matched partner IDs. The ConnectID Prebid check uses browser tools to inspect the network payload for a yahoo.com EID. Those endpoints have different units and purposes. Neither source supplies a realized US publisher-lookup match rate with units, denominator, exclusions and sample period. The screen included the server, Prebid and JS guides, DataX, Truthset, Mediavine and Yahoo’s buyer coverage accounts.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "Neither source supplies a realized US publisher-lookup match rate with units, denominator, exclusions and sample period. The screen included the server, Prebid and JS guides, DataX, Truthset, Mediavine and Yahoo’s buyer coverage accounts.",
  "final_wording": "Yahoo’s DataX file-match reporting and its ConnectID integration check measure different outcomes: one returns partner onboarding results and the other checks whether an ID appears on a bid request.",
  "counterevidence": "DataX does expose match percentages and result files. They are tied to a partner onboarding service; the guide does not document a denominator for the main ConnectID issuance task.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H1"
 },
 {
  "id": "IDN-YAH-F17",
  "headline": false,
  "claim": "Yahoo’s Prebid guide identifies version 7.52 as the boundary below which publishers must supply the hashed email parameter.",
  "chapter": "5, 13",
  "source_ids": [
   "IDN-YAH-S04",
   "IDN-YAH-S16",
   "IDN-VYAH-S01",
   "IDN-VYAH-S02",
   "IDN-VYAH-S03"
  ],
  "passage": "[IDN-YAH-S04, Configuration table, params.he row and sample 2 without email] Required if using prebid version below 7.52 [IDN-YAH-S16, Prebid project-hosted Configuration table, params.he (optional) and adjacent params.puid; the numbered boundary is in Yahoo’s own guide, not in the pinned April 2025 guide.] params.he",
  "support": [
   {
    "source_id": "IDN-YAH-S04",
    "passage": "Required if using prebid version below 7.52",
    "locator": "Configuration table, params.he row and sample 2 without email"
   },
   {
    "source_id": "IDN-YAH-S16",
    "passage": "params.he",
    "locator": "Prebid project-hosted Configuration table, params.he (optional) and adjacent params.puid; the numbered boundary is in Yahoo’s own guide, not in the pinned April 2025 guide."
   }
  ],
  "scope_time": "Prebid.js 7.51.0 released May 25, 2023; 7.52.0 released June 1, 2023; Yahoo guide read November 11, 2026.",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "contradicted",
  "review_note": "The help table does print a below-7.52 email requirement. The executable 7.51.0 configuration accepts a string-valued he OR puid; 7.52.0 removed the requirement for either. The release explicitly dates that change to June 1, 2023. The attributed guide wording is accurate; its operational claim is refuted by the tagged code. This is an input-validation change in the integration, not an upstream person-graph change or evidence of a 2025 Chrome sync transition.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "High confidence in the released client rule from a comparison of tagged versions and the June 1, 2023 release note. The help article’s required-email statement conflicts with that rule.",
  "limitations": "The dated release changes client input validation. It does not show production uptake, person-link accuracy, new graph edges or a shift in the primary US Chrome sync path.",
  "final_wording": "Yahoo’s guide says an email hash is required below Prebid 7.52. The released 7.51.0 module accepts either an email hash or a publisher user ID. Version 7.52.0, released June 1, 2023, removed the requirement to supply either value.",
  "counterevidence": "Published Prebid.js 7.51.0 accepts either he or puid; the 7.52.0 source and release notes remove the requirement for either. Yahoo’s undated help wording is contradicted for 7.51.0.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-YAH-F18",
  "headline": false,
  "claim": "Prebid’s April 2025 module guide describes ConnectID as able to work without third-party cookies, while Yahoo’s publisher guide offers multiple implementation paths.",
  "chapter": "5",
  "source_ids": [
   "IDN-E-S28",
   "IDN-YAH-S03"
  ],
  "passage": "[IDN-E-S28, Pinned project documentation revision 6439acd8, Yahoo ConnectID section] does not depend on 3rd party cookies. [IDN-YAH-S03, Yahoo ConnectID Integration Methods, introductory sentence] the choice is yours",
  "support": [
   {
    "source_id": "IDN-E-S28",
    "passage": "does not depend on 3rd party cookies.",
    "locator": "Pinned project documentation revision 6439acd8, Yahoo ConnectID section"
   },
   {
    "source_id": "IDN-YAH-S03",
    "passage": "the choice is yours",
    "locator": "Yahoo ConnectID Integration Methods, introductory sentence"
   }
  ],
  "scope_time": "2025-04-04 pinned Prebid document and issuer guide inspected 2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The exact April 4, 2025 Prebid documentation snapshot says the ID does not depend on third-party cookies. The Yahoo catalog lists several routes, regardless of its internal count mismatch. Neither record designates the primary US Chrome route. The dates of the input changes do not bridge that gap. No dated post-event edition of an issuer-designated main US Chrome workflow was established in the pinned path, current rendered guide or issuer integration index. Ability to operate without third-party cookies does not specify the default sync setting. The H4 direction stays unknown.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "No dated post-event edition of an issuer-designated main US Chrome workflow was established in the pinned path, current rendered guide or issuer integration index. Ability to operate without third-party cookies does not specify the default sync setting. The H4 direction stays unknown.",
  "final_wording": "Prebid’s April 2025 module guide describes ConnectID as able to work without third-party cookies, while Yahoo’s publisher guide offers multiple implementation paths.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H4"
 },
 {
  "id": "IDN-YAH-F19",
  "headline": false,
  "claim": "The public contract contains conflicting directions about EU GDPR, UK and Brazilian jurisdictions within the same paragraph.",
  "chapter": "",
  "source_ids": [
   "IDN-YAH-S01"
  ],
  "passage": "[IDN-YAH-S01, Privacy Protections §2(c), opening prohibition] may not be used [IDN-YAH-S01, Immediately following representation in the same §2(c)] it shall use",
  "support": [
   {
    "source_id": "IDN-YAH-S01",
    "passage": "may not be used",
    "locator": "Privacy Protections §2(c), opening prohibition"
   },
   {
    "source_id": "IDN-YAH-S01",
    "passage": "it shall use",
    "locator": "Immediately following representation in the same §2(c)"
   }
  ],
  "scope_time": "2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "The first sentence bars use for covered publishers or end users within GDPR/UK-equivalent/Brazilian jurisdiction. The following representation uses affirmative wording about use for such users. The competing text cannot establish regional permission to deploy. The public US contract cannot settle deployment eligibility in these territories. The existence of a GDPR parameter in the US-facing API does not resolve the conflict. No claim of legal compliance or regional live availability.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "The public US contract cannot settle deployment eligibility in these territories. The existence of a GDPR parameter in the US-facing API does not resolve the conflict. No claim of legal compliance or regional live availability.",
  "final_wording": "The public contract contains conflicting directions about EU GDPR, UK and Brazilian jurisdictions within the same paragraph.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "id": "IDN-YAH-F20",
  "headline": false,
  "claim": "On August 26, 2026, the Southern District of New York ordered five plaintiffs’ claims in the private ConnectID suit into arbitration and stayed litigation of those claims.",
  "chapter": "9, 13",
  "source_ids": [
   "IDN-YAH-S17",
   "IDN-VYAH-S06"
  ],
  "passage": "[IDN-YAH-S17, Docket 103, Opinion and Order, pp. 1–2, 23–24; p. 23 identifies the five plaintiffs whose claims must be arbitrated.] five of the six plaintiffs [IDN-YAH-S17, Docket 103, signed Conclusion, p. 24; see also § II, Motion to Stay Litigation, pp. 22–23.] to stay the litigation of their claims pending arbitration is granted",
  "support": [
   {
    "source_id": "IDN-YAH-S17",
    "passage": "five of the six plaintiffs",
    "locator": "Docket 103, Opinion and Order, pp. 1–2, 23–24; p. 23 identifies the five plaintiffs whose claims must be arbitrated."
   },
   {
    "source_id": "IDN-YAH-S17",
    "passage": "to stay the litigation of their claims pending arbitration is granted",
    "locator": "Docket 103, signed Conclusion, p. 24; see also § II, Motion to Stay Litigation, pp. 22–23."
   }
  ],
  "scope_time": "2026-08-26 order only",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "review_note": "Signed document 103 grants arbitration and stays the claims of five of six plaintiffs. Separate order 104 instructed parties to confer about possible limited discovery of Baker’s arbitration status; neither decides the merits of privacy allegations. A dated account of the August orders. No verified determination of the sixth plaintiff’s status at the cutoff.",
  "checked_independently": true,
  "confidence": "high",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "This is a procedural order. It does not decide the merits, constitute public enforcement, or establish an implemented product change. The sixth plaintiff was addressed separately.",
  "final_wording": "On August 26, 2026, the Southern District of New York ordered five plaintiffs’ claims in the private ConnectID suit into arbitration and stayed litigation of those claims.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": "H6"
 },
 {
  "id": "IDN-YAH-F21",
  "headline": false,
  "claim": "Yahoo markets ConnectID as active inside its DSP and describes separate Next-Gen tools for unaddressable inventory.",
  "chapter": "",
  "source_ids": [
   "IDN-YAH-S13",
   "IDN-YAH-S09",
   "IDN-YAH-S03"
  ],
  "passage": "[IDN-YAH-S13, How Yahoo ConnectID Helps You Reach Your Goals, paragraph after US user figure] always active within Yahoo DSP [IDN-YAH-S09, Product description after rollout statement] ConnectID for addressable environments and Next-Gen Solutions for non-addressable [IDN-YAH-S03, Publisher integration methods, note on contracting and umbrella agreements] requires a new contract or addendum",
  "support": [
   {
    "source_id": "IDN-YAH-S13",
    "passage": "always active within Yahoo DSP",
    "locator": "How Yahoo ConnectID Helps You Reach Your Goals, paragraph after US user figure"
   },
   {
    "source_id": "IDN-YAH-S09",
    "passage": "ConnectID for addressable environments and Next-Gen Solutions for non-addressable",
    "locator": "Product description after rollout statement"
   },
   {
    "source_id": "IDN-YAH-S03",
    "passage": "requires a new contract or addendum",
    "locator": "Publisher integration methods, note on contracting and umbrella agreements"
   }
  ],
  "scope_time": "2024-07-17 to 2026-11-11",
  "scope_geo": "United States buying task",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "review_note": "Yahoo says ConnectID is always active in its DSP, and its LiveRamp communication distinguishes the addressable product from Next-Gen for non-addressable supply. The onboarding page describes separate licensing and Next-Gen activation. This is the seller’s positioning, not telemetry. The offer combines a publisher integration with an advertiser DSP use. Neither the issuer guide, release, contract nor Verizon filing provides standalone ConnectID prices, product revenue, margins or buyer spend.",
  "checked_independently": true,
  "confidence": "medium",
  "confidence_reason": "Attribution, scope and caveats follow the linked sections; issuer, partner and court records establish different propositions.",
  "limitations": "The offer combines a publisher integration with an advertiser DSP use. Neither the issuer guide, release, contract nor Verizon filing provides standalone ConnectID prices, product revenue, margins or buyer spend.",
  "final_wording": "Yahoo markets ConnectID as active inside its DSP and describes separate Next-Gen tools for unaddressable inventory.",
  "counterevidence": "No contrary product-specific record found in the named sources.",
  "stream": "yahoo-connectid",
  "study_id": "",
  "study_design": "",
  "claim_status": "actual",
  "hypothesis": ""
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Last Updated April 2026; Identity Solutions and Partners, introductory paragraph and country/type rows.. For passthrough, the publisher has the relationship with the ID provider. It establishes exchange support in the named country, not domestic issuance, completed bids or receipt by each listed DSP. The Utiq operator separately requires a connection from a participating telecom.",
  "checked_independently": true,
  "id": "IDN-A5-F01",
  "claim": "TripleLift’s April 2026 exchange table lists US passthrough for Lotame Panorama ID, SharedID, Audigent Hadron ID, Criteo ID, Neustar Fabrik ID (exchange spelling) and UTIQ ID. It lists US bridging for 33Across Lexicon ID. The same US table lists Epsilon PubLink and Flashtalking FTrack for passthrough and LiveIntent for bridging. The exchange labels that row by provider.",
  "final_wording": "TripleLift’s April 2026 exchange table lists US passthrough for Lotame Panorama ID, SharedID, Audigent Hadron ID, Criteo ID, Neustar Fabrik ID (exchange spelling) and UTIQ ID. It lists US bridging for 33Across Lexicon ID. The same US table lists Epsilon PubLink and Flashtalking FTrack for passthrough and LiveIntent for bridging. The exchange labels that row by provider.",
  "source_ids": [
   "IDN-A5-S01"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S01",
    "passage": "TripleLift facilitates the forwarding of these identifiers to specific Demand Side Platforms (DSPs).",
    "locator": "Last Updated April 2026; Identity Solutions and Partners, introductory paragraph and country/type rows."
   }
  ],
  "passage": "TripleLift facilitates the forwarding of these identifiers to specific Demand Side Platforms (DSPs).",
  "scope_geo": "Table specifies geography per exchange route",
  "scope_time": "2026-04",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "For passthrough, the publisher has the relationship with the ID provider. It establishes exchange support in the named country, not domestic issuance, completed bids or receipt by each listed DSP. The Utiq operator separately requires a connection from a participating telecom.",
  "claim_status": "actual",
  "chapter": "4, 11",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. p. 2, Panorama ID Test Setup and test parameters; Michigan/MLive audience, PubMatic SSP. Case linked from Lotame’s May 19, 2023 article of same name.. Targeting logic was in the SSP. DSP campaign delivery does not prove those two DSPs independently used or resolved a raw ID, or remain current-cutoff recipients.",
  "checked_independently": true,
  "id": "IDN-A5-F02",
  "claim": "Lotame’s Michigan case with Advance Local and Rush Street Interactive reports that the publisher used its PubMatic SSP seat for a Panorama ID-enabled private marketplace and that the campaign delivered through Xandr and Adelphic.",
  "final_wording": "Lotame’s Michigan case with Advance Local and Rush Street Interactive reports that the publisher used its PubMatic SSP seat for a Panorama ID-enabled private marketplace and that the campaign delivered through Xandr and Adelphic.",
  "source_ids": [
   "IDN-A5-S02"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S02",
    "passage": "Delivery was completed through Xandr and Adelphic",
    "locator": "p. 2, Panorama ID Test Setup and test parameters; Michigan/MLive audience, PubMatic SSP. Case linked from Lotame’s May 19, 2023 article of same name."
   }
  ],
  "passage": "Delivery was completed through Xandr and Adelphic",
  "scope_geo": "United States, Michigan",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Targeting logic was in the SSP. DSP campaign delivery does not prove those two DSPs independently used or resolved a raw ID, or remain current-cutoff recipients.",
  "claim_status": "actual",
  "chapter": "4, 11",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Reporting table, mapped Provider (source field), Provider name and Equativ Id; OneCall example for criteo.com.. Supports namespace/product identification; a table entry is not proof of a named DSP using an ID in a US auction.",
  "checked_independently": true,
  "id": "IDN-A5-F03",
  "claim": "Equativ maps criteo.com to its Criteo provider and separately lists esp.criteo.com. It maps neustar.biz to Neustar Fabrick, sharedid.org to Shared Id, parrable.com to Parrable ID, and zeotap.com to Zeotap IDplus.",
  "final_wording": "Equativ maps criteo.com to its Criteo provider and separately lists esp.criteo.com. It maps neustar.biz to Neustar Fabrick, sharedid.org to Shared Id, parrable.com to Parrable ID, and zeotap.com to Zeotap IDplus.",
  "source_ids": [
   "IDN-A5-S03"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S03",
    "passage": "Equativ Id assigned to the provider by Equativ.",
    "locator": "Reporting table, mapped Provider (source field), Provider name and Equativ Id; OneCall example for criteo.com."
   }
  ],
  "passage": "Equativ Id assigned to the provider by Equativ.",
  "scope_geo": "Platform integration; US territory supplied separately by TripleLift when applicable",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Supports namespace/product identification; a table entry is not proof of a named DSP using an ID in a US auction.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. London dateline, first two paragraphs describing PubMatic Identity Hub.. Not a global exclusion or a current list of all eligible markets.",
  "checked_independently": true,
  "id": "IDN-A5-F04",
  "claim": "PubMatic’s May 2021 announcement names five European markets for Zeotap ID+ in its Identity Hub. It does not establish a US ID+ route.",
  "final_wording": "PubMatic’s May 2021 announcement names five European markets for Zeotap ID+ in its Identity Hub. It does not establish a US ID+ route.",
  "source_ids": [
   "IDN-A5-S04"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S04",
    "passage": "Publishers in the UK, France, Germany, Italy, and Spain",
    "locator": "London dateline, first two paragraphs describing PubMatic Identity Hub."
   }
  ],
  "passage": "Publishers in the UK, France, Germany, Italy, and Spain",
  "scope_geo": "UK, France, Germany, Italy and Spain",
  "scope_time": "2021-05-18",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Not a global exclusion or a current list of all eligible markets.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Publisher Link; Publisher Link Registration, Configuration and Examples.. The publisher selects a distinct integration with registration. The ID and the underlying CORE ID graph are different units, and no link accuracy statistic is given.",
  "checked_independently": true,
  "id": "IDN-A5-F05",
  "claim": "Epsilon’s PubLink registration lets a publisher connect its authenticated first-party data and an encrypted ID to Epsilon CORE ID, then supply a PubLink identifier in the bidder field.",
  "final_wording": "Epsilon’s PubLink registration lets a publisher connect its authenticated first-party data and an encrypted ID to Epsilon CORE ID, then supply a PubLink identifier in the bidder field.",
  "source_ids": [
   "IDN-A5-S05"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S05",
    "passage": "linked to an existing people-based Epsilon CORE ID",
    "locator": "Publisher Link; Publisher Link Registration, Configuration and Examples."
   }
  ],
  "passage": "linked to an existing people-based Epsilon CORE ID",
  "scope_geo": "US route separately listed by TripleLift",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "The publisher selects a distinct integration with registration. The ID and the underlying CORE ID graph are different units, and no link accuracy statistic is given.",
  "claim_status": "actual",
  "chapter": "13",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. FTrack ID overview, configuration parameters and HTML5 storage example.. Both intervals are local module recommendations; neither establishes link accuracy, a universal identifier lifetime or the household-edge lifetime.",
  "checked_independently": true,
  "id": "IDN-A5-F06",
  "claim": "The FTrack publisher module uses probabilistic device recognition, can return a device ID to the bidder, and recommends an eight-hour refresh and 90-day local storage period.",
  "final_wording": "The FTrack publisher module uses probabilistic device recognition, can return a device ID to the bidder, and recommends an eight-hour refresh and 90-day local storage period.",
  "source_ids": [
   "IDN-A5-S06"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S06",
    "passage": "probabilistic device recognition",
    "locator": "FTrack ID overview, configuration parameters and HTML5 storage example."
   }
  ],
  "passage": "probabilistic device recognition",
  "scope_geo": "US route separately listed by TripleLift",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Both intervals are local module recommendations; neither establishes link accuracy, a universal identifier lifetime or the household-edge lifetime.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. What is it; Registration; How does it work; GDPR and CCPA; Configuration.. A claimed integration control is not proof of actual recipient compliance or deletion. Other namespaces optionally returned are not nonID.",
  "checked_independently": true,
  "id": "IDN-A5-F07",
  "claim": "LiveIntent’s module uses a publisher-side identifier and an API to resolve nonID, linked to an active encrypted email. Adapters can receive the result for the bid request. LiveConnect receives a US privacy string and the guide says it honors opt-outs.",
  "final_wording": "LiveIntent’s module uses a publisher-side identifier and an API to resolve nonID, linked to an active encrypted email. Adapters can receive the result for the bid request. LiveConnect receives a US privacy string and the guide says it honors opt-outs.",
  "source_ids": [
   "IDN-A5-S07"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S07",
    "passage": "a user identifier tied to an active, encrypted email in the graph",
    "locator": "What is it; Registration; How does it work; GDPR and CCPA; Configuration."
   }
  ],
  "passage": "a user identifier tied to an active, encrypted email in the graph",
  "scope_geo": "Includes CCPA/US Privacy integration; US route separately identified by TripleLift",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "A claimed integration control is not proof of actual recipient compliance or deletion. Other namespaces optionally returned are not nonID.",
  "claim_status": "actual",
  "chapter": "4",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Merkle ID overview, storage, and Prebid.js configuration.. The module documentation does not establish a distinct A product that a buyer can select independently of the registered B offer.",
  "checked_independently": true,
  "id": "IDN-A5-F08",
  "claim": "Prebid identifies the Merkle ID module and its merkleinc.com source as a publisher route for Merkury’s private identity graph.",
  "final_wording": "Prebid identifies the Merkle ID module and its merkleinc.com source as a publisher route for Merkury’s private identity graph.",
  "source_ids": [
   "IDN-A5-S08"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S08",
    "passage": "Publisher stores Merkury by Merkle in local storage for 30 days",
    "locator": "Merkle ID overview, storage, and Prebid.js configuration."
   }
  ],
  "passage": "Publisher stores Merkury by Merkle in local storage for 30 days",
  "scope_geo": "US scope of the parent service supplied by Merkle’s own US notice",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "The module documentation does not establish a distinct A product that a buyer can select independently of the registered B offer.",
  "claim_status": "actual",
  "chapter": "13",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Coverage, Identity and Media product descriptions; introductory US scope paragraphs.. The wording is a US service description. It is not a reach metric with a national denominator or a separate purchase of an exchange ID.",
  "checked_independently": true,
  "id": "IDN-A5-F09",
  "claim": "Merkle’s US notice explicitly covers the Merkury brand and describes matching its clients’ identity signals to US adults through its identity service.",
  "final_wording": "Merkle’s US notice explicitly covers the Merkury brand and describes matching its clients’ identity signals to US adults through its identity service.",
  "source_ids": [
   "IDN-A5-S09"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S09",
    "passage": "product offerings in the United States, including those under our “Merkury” brand",
    "locator": "Coverage, Identity and Media product descriptions; introductory US scope paragraphs."
   }
  ],
  "passage": "product offerings in the United States, including those under our “Merkury” brand",
  "scope_geo": "United States",
  "scope_time": "2026-07-07",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "The wording is a US service description. It is not a reach metric with a national denominator or a separate purchase of an exchange ID.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Overview and glossary; Sidecar’s role for supply-side platforms.. A Sidecar deployment belongs to the RampID route. It is not a new scored identifier.",
  "checked_independently": true,
  "id": "IDN-A5-F10",
  "claim": "LiveRamp Sidecar lets an SSP decrypt a LiveRamp envelope into DSP-specific RampIDs and other people-based IDs for RTB.",
  "final_wording": "LiveRamp Sidecar lets an SSP decrypt a LiveRamp envelope into DSP-specific RampIDs and other people-based IDs for RTB.",
  "source_ids": [
   "IDN-A5-S10"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S10",
    "passage": "decrypt the identity envelopes LiveRamp has provided them",
    "locator": "Overview and glossary; Sidecar’s role for supply-side platforms."
   }
  ],
  "passage": "decrypt the identity envelopes LiveRamp has provided them",
  "scope_geo": "SSP-to-DSP bidstream interface, separately identified in TripleLift’s geography table",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "A Sidecar deployment belongs to the RampID route. It is not a new scored identifier.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Supported countries/regions, prerequisites and configure the connection; tested field mapping and results sections.. Include as US LiveRamp Known Identity Resolution via the AbiliTec API, with Microsoft’s US-specific preview of profile enrichment separately identified. The standalone API guide covers real-time service, OAuth2, maintained US links and match response. The Dynamics integration’s preview label applies to the Microsoft feature.",
  "checked_independently": true,
  "id": "IDN-SB-F01",
  "claim": "Microsoft documents a US-only AbiliTec preview that requires active LiveRamp and AbiliTec subscriptions and credentials. A buyer maps profile fields to retrieve person-level AbiliTec IDs.",
  "final_wording": "Microsoft documents a US-only AbiliTec preview that requires active LiveRamp and AbiliTec subscriptions and credentials. A buyer maps profile fields to retrieve person-level AbiliTec IDs.",
  "source_ids": [
   "IDN-SB-S01"
  ],
  "support": [
   {
    "source_id": "IDN-SB-S01",
    "passage": "You can currently enrich customer profiles with LiveRamp data in the United States only.",
    "locator": "Supported countries/regions, prerequisites and configure the connection; tested field mapping and results sections."
   }
  ],
  "passage": "You can currently enrich customer profiles with LiveRamp data in the United States only.",
  "scope_geo": "United States expressly identified.",
  "scope_time": "2026-07-14",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Include as US LiveRamp Known Identity Resolution via the AbiliTec API, with Microsoft’s US-specific preview of profile enrichment separately identified. The standalone API guide covers real-time service, OAuth2, maintained US links and match response. The Dynamics integration’s preview label applies to the Microsoft feature.",
  "claim_status": "actual",
  "chapter": "1",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. About AbiliTec, introductory paragraphs and API Calls. Fields and match information are returned; HTTP REST with OAuth2.. Include as US LiveRamp Known Identity Resolution via the AbiliTec API, with Microsoft’s US-specific preview of profile enrichment separately identified. The standalone API guide covers real-time service, OAuth2, maintained US links and match response. The Dynamics integration’s preview label applies to the Microsoft feature.",
  "checked_independently": true,
  "id": "IDN-SB-F02",
  "claim": "LiveRamp’s OAuth2 REST API accepts personal identifiers and returns AbiliTec identifiers and match information for matched records, using single or batch calls.",
  "final_wording": "LiveRamp’s OAuth2 REST API accepts personal identifiers and returns AbiliTec identifiers and match information for matched records, using single or batch calls.",
  "source_ids": [
   "IDN-SB-S02"
  ],
  "support": [
   {
    "source_id": "IDN-SB-S02",
    "passage": "The AbiliTec API responds with the AbiliTec identifiers for each matched record",
    "locator": "About AbiliTec, introductory paragraphs and API Calls. Fields and match information are returned; HTTP REST with OAuth2."
   }
  ],
  "passage": "The AbiliTec API responds with the AbiliTec identifiers for each matched record",
  "scope_geo": "Scope of the stated technical route; no region stated on this record.",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Include as US LiveRamp Known Identity Resolution via the AbiliTec API, with Microsoft’s US-specific preview of profile enrichment separately identified. The standalone API guide covers real-time service, OAuth2, maintained US links and match response. The Dynamics integration’s preview label applies to the Microsoft feature.",
  "claim_status": "actual",
  "chapter": "1",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. AbiliTec Link Structure, Country Code row.. Include as US LiveRamp Known Identity Resolution via the AbiliTec API, with Microsoft’s US-specific preview of profile enrichment separately identified. The standalone API guide covers real-time service, OAuth2, maintained US links and match response. The Dynamics integration’s preview label applies to the Microsoft feature.",
  "checked_independently": true,
  "id": "IDN-SB-F03",
  "claim": "LiveRamp documents that maintained AbiliTec links carry the US code for the underlying data and describes the output structure.",
  "final_wording": "LiveRamp documents that maintained AbiliTec links carry the US code for the underlying data and describes the output structure.",
  "source_ids": [
   "IDN-SB-S03"
  ],
  "support": [
   {
    "source_id": "IDN-SB-S03",
    "passage": "For maintained links, this will be \"US\" for the United States.",
    "locator": "AbiliTec Link Structure, Country Code row."
   }
  ],
  "passage": "For maintained links, this will be \"US\" for the United States.",
  "scope_geo": "United States expressly identified.",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Include as US LiveRamp Known Identity Resolution via the AbiliTec API, with Microsoft’s US-specific preview of profile enrichment separately identified. The standalone API guide covers real-time service, OAuth2, maintained US links and match response. The Dynamics integration’s preview label applies to the Microsoft feature.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Real ID free trial, following Acxiom Native Apps. Direct linked Marketplace page returned no readable lines.. Cloud app is offered through the native Snowflake marketplace trial. Exact market is unconfirmed in those records; the geographic condition belongs to a separate real-time Acxiom Sync service. Preserve the listed status for the brand-cloud app unless the freeze owner chooses a distinct US Acxiom Real ID sync product.",
  "checked_independently": true,
  "id": "IDN-SB-F04",
  "claim": "Acxiom offers a trial of its Real ID native application to Snowflake Marketplace clients. The offer does not specify US availability.",
  "final_wording": "Acxiom offers a trial of its Real ID native application to Snowflake Marketplace clients. The offer does not specify US availability.",
  "source_ids": [
   "IDN-SB-S04"
  ],
  "support": [
   {
    "source_id": "IDN-SB-S04",
    "passage": "Snowflake Marketplace clients can access Acxiom Real ID’s free trial app now.",
    "locator": "Real ID free trial, following Acxiom Native Apps. Direct linked Marketplace page returned no readable lines."
   }
  ],
  "passage": "Snowflake Marketplace clients can access Acxiom Real ID’s free trial app now.",
  "scope_geo": "Scope of the stated technical route; no region stated on this record.",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Cloud app is offered through the native Snowflake marketplace trial. Exact market is unconfirmed in those records; the geographic condition belongs to a separate real-time Acxiom Sync service. Preserve the listed status for the brand-cloud app unless the freeze owner chooses a distinct US Acxiom Real ID sync product.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Partner prerequisites and Geographic Availability. Integration details list household/person data and REST callback.. Cloud app is offered through the native Snowflake marketplace trial. Exact market is unconfirmed in those records; the geographic condition belongs to a separate real-time Acxiom Sync service. Preserve the listed status for the brand-cloud app unless the freeze owner chooses a distinct US Acxiom Real ID sync product.",
  "checked_independently": true,
  "id": "IDN-SB-F05",
  "claim": "MetaRouter documents a separate US-only Acxiom identity sync. Its endpoint returns person and household identity attributes. The guide does not establish geographic availability of the Acxiom native cloud application.",
  "final_wording": "MetaRouter documents a separate US-only Acxiom identity sync. Its endpoint returns person and household identity attributes. The guide does not establish geographic availability of the Acxiom native cloud application.",
  "source_ids": [
   "IDN-SB-S05"
  ],
  "support": [
   {
    "source_id": "IDN-SB-S05",
    "passage": "The Acxiom identity sync integration is currently supported only within the United States.",
    "locator": "Partner prerequisites and Geographic Availability. Integration details list household/person data and REST callback."
   }
  ],
  "passage": "The Acxiom identity sync integration is currently supported only within the United States.",
  "scope_geo": "United States expressly identified.",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Cloud app is offered through the native Snowflake marketplace trial. Exact market is unconfirmed in those records; the geographic condition belongs to a separate real-time Acxiom Sync service. Preserve the listed status for the brand-cloud app unless the freeze owner chooses a distinct US Acxiom Real ID sync product.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Regional scope at opening; Customer Matcher at lines 78–106; CGI-specific Glossary and Using the Application, lines 163–184.. The two named applications have distinct outputs. Do not assign the pair-matching threshold to the CGI graph-enrichment service.",
  "checked_independently": true,
  "id": "IDN-SB-F06",
  "claim": "Zeta documents US-only Streamlit applications. Its Customer Growth Intelligence workflow takes first-party data through a Snowflake share and exposes enriched views. The same guide separately describes Customer Matcher scoring and pairing two client tables.",
  "final_wording": "Zeta documents US-only Streamlit applications. Its Customer Growth Intelligence workflow takes first-party data through a Snowflake share and exposes enriched views. The same guide separately describes Customer Matcher scoring and pairing two client tables.",
  "source_ids": [
   "IDN-SB-S06"
  ],
  "support": [
   {
    "source_id": "IDN-SB-S06",
    "passage": "Streamlit Applications is currently available exclusively in the U.S.",
    "locator": "Regional scope at opening; Customer Matcher at lines 78–106; CGI-specific Glossary and Using the Application, lines 163–184."
   }
  ],
  "passage": "Streamlit Applications is currently available exclusively in the U.S.",
  "scope_geo": "United States expressly identified.",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "The two named applications have distinct outputs. Do not assign the pair-matching threshold to the CGI graph-enrichment service.",
  "claim_status": "actual",
  "chapter": "1",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Opening account of Growth Intelligence native app using the same brand’s graph in 2023. Do not transpose counts to the different Customer Matcher.. Include when narrowed to the verified Zeta Customer Matcher application on Snowflake, a US-only separately obtainable resolution service that returns pairs of records. Do not apply the 235m US population from the 2023 CGI announcement to Customer Matcher. Generic Zeta ID and this matching route must not share untested metrics.",
  "checked_independently": true,
  "id": "IDN-SB-F07",
  "claim": "In 2023 Zeta announced a separate Customer Growth Intelligence Snowflake Native App for first-party enrichment against its graph of over 235 million US people. This is not a count of Customer Matcher clients or records.",
  "final_wording": "In 2023 Zeta announced a separate Customer Growth Intelligence Snowflake Native App for first-party enrichment against its graph of over 235 million US people. This is not a count of Customer Matcher clients or records.",
  "source_ids": [
   "IDN-SB-S07"
  ],
  "support": [
   {
    "source_id": "IDN-SB-S07",
    "passage": "Zeta’s identity graph of over 235M people in the U.S.",
    "locator": "Opening account of Growth Intelligence native app using the same brand’s graph in 2023. Do not transpose counts to the different Customer Matcher."
   }
  ],
  "passage": "Zeta’s identity graph of over 235M people in the U.S.",
  "scope_geo": "United States expressly identified.",
  "scope_time": "2023-08-28",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Include when narrowed to the verified Zeta Customer Matcher application on Snowflake, a US-only separately obtainable resolution service that returns pairs of records. Do not apply the 235m US population from the 2023 CGI announcement to Customer Matcher. Generic Zeta ID and this matching route must not share untested metrics.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Verve at a glance, printed p. 5, bottom of left-hand narrative and following line naming Moments.AI.. Read alongside IDN-U-S29, March 8, 2022 closing paragraph, which explicitly named a US managed or programmatic buy of contextual audience segments. No US volume is implied.",
  "checked_independently": true,
  "id": "IDN-SCD-F01",
  "claim": "Verve still identifies Moments.AI in its Q1 2026 corporate product description for environments losing identifiers.",
  "final_wording": "Verve still identifies Moments.AI in its Q1 2026 corporate product description for environments losing identifiers.",
  "source_ids": [
   "IDN-SCD-S01"
  ],
  "support": [
   {
    "source_id": "IDN-SCD-S01",
    "passage": "developed innovative products such as ATOM and",
    "locator": "Verve at a glance, printed p. 5, bottom of left-hand narrative and following line naming Moments.AI."
   }
  ],
  "passage": "developed innovative products such as ATOM and",
  "scope_geo": "US where specified; other territories only as cited.",
  "scope_time": "2026-05-27",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Read alongside IDN-U-S29, March 8, 2022 closing paragraph, which explicitly named a US managed or programmatic buy of contextual audience segments. No US volume is implied.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Location-specific SmartReach and custom/off-the-shelf segments; Activation Platform; concluding call to action.. Contemporaneously read on the cutoff. No national or per-partner deployment count implied.",
  "checked_independently": true,
  "id": "IDN-SCD-F02",
  "claim": "Proximic currently markets custom ID-free predictive audiences via its activation platform.",
  "final_wording": "Proximic currently markets custom ID-free predictive audiences via its activation platform.",
  "source_ids": [
   "IDN-SCD-S02"
  ],
  "support": [
   {
    "source_id": "IDN-SCD-S02",
    "passage": "Start building custom segments today to push directly to your platform of choice.",
    "locator": "Location-specific SmartReach and custom/off-the-shelf segments; Activation Platform; concluding call to action."
   }
  ],
  "passage": "Start building custom segments today to push directly to your platform of choice.",
  "scope_geo": "US where specified; other territories only as cited.",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Contemporaneously read on the cutoff. No national or per-partner deployment count implied.",
  "claim_status": "actual",
  "chapter": "11",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Political TV Ad Exposure custom segments, two paragraphs after release dateline; adjoining presidential, senate, house and gubernatorial scope.. Historical launch channel, not proof of a US buyer transaction in November 2026.",
  "checked_independently": true,
  "id": "IDN-SCD-F03",
  "claim": "Comscore offered US political buyers on The Trade Desk an ID-free Predictive Audience based on TV ad exposure alongside its ID-based option.",
  "final_wording": "Comscore offered US political buyers on The Trade Desk an ID-free Predictive Audience based on TV ad exposure alongside its ID-based option.",
  "source_ids": [
   "IDN-SCD-S03"
  ],
  "support": [
   {
    "source_id": "IDN-SCD-S03",
    "passage": "The political TV ad exposure custom segments are available as ID-based audiences and ID-free contextual Predictive Audiences.",
    "locator": "Political TV Ad Exposure custom segments, two paragraphs after release dateline; adjoining presidential, senate, house and gubernatorial scope."
   }
  ],
  "passage": "The political TV ad exposure custom segments are available as ID-based audiences and ID-free contextual Predictive Audiences.",
  "scope_geo": "US where specified; other territories only as cited.",
  "scope_time": "2023-10-24",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Historical launch channel, not proof of a US buyer transaction in November 2026.",
  "claim_status": "actual",
  "chapter": "8, 11",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Opening explanation and availability of the client-facing platform, including API-integrated and self-serve options.. Separate the original Japanese case from this offer and the 2026 partner-described US data route.",
  "checked_independently": true,
  "id": "IDN-SCD-F04",
  "claim": "Ogury offers its persona groups as a replacement for tracking individuals. Brands and agencies can plan and activate on Ogury One, its self-serve and API delivery route.",
  "final_wording": "Ogury offers its persona groups as a replacement for tracking individuals. Brands and agencies can plan and activate on Ogury One, its self-serve and API delivery route.",
  "source_ids": [
   "IDN-SCD-S04"
  ],
  "support": [
   {
    "source_id": "IDN-SCD-S04",
    "passage": "hands-on direct access to Personified Advertising",
    "locator": "Opening explanation and availability of the client-facing platform, including API-integrated and self-serve options."
   }
  ],
  "passage": "hands-on direct access to Personified Advertising",
  "scope_geo": "US where specified; other territories only as cited.",
  "scope_time": "2025-04-08",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Separate the original Japanese case from this offer and the 2026 partner-described US data route.",
  "claim_status": "actual",
  "chapter": "8, 12",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Lead, second and fifth paragraphs; FAQs on geography and audience activation.. A US product input and purchasable platform, not an observed US ad impression. No production count supplied.",
  "checked_independently": true,
  "id": "IDN-SCD-F05",
  "claim": "NIQ names the US as a market for its purchase insights for Ogury’s persona engine and describes brands activating the resulting audiences in digital campaigns.",
  "final_wording": "NIQ names the US as a market for its purchase insights for Ogury’s persona engine and describes brands activating the resulting audiences in digital campaigns.",
  "source_ids": [
   "IDN-SCD-S05"
  ],
  "support": [
   {
    "source_id": "IDN-SCD-S05",
    "passage": "as well as the United States and Canada",
    "locator": "Lead, second and fifth paragraphs; FAQs on geography and audience activation."
   }
  ],
  "passage": "as well as the United States and Canada",
  "scope_geo": "US where specified; other territories only as cited.",
  "scope_time": "2026-06-18",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "A US product input and purchasable platform, not an observed US ad impression. No production count supplied.",
  "claim_status": "actual",
  "chapter": "8, 13",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. The challenge and Our solution.. This one placement case does not establish the sale of a separate modeled audience, and an offer of lookalikes elsewhere does not establish that this US customer used one. Keep outside C absent a stronger exact-offer link.",
  "checked_independently": true,
  "id": "IDN-SCD-F06",
  "claim": "Seedtag ran a US contextual placement campaign for Eurail.",
  "final_wording": "Seedtag ran a US contextual placement campaign for Eurail.",
  "source_ids": [
   "IDN-SCD-S06"
  ],
  "support": [
   {
    "source_id": "IDN-SCD-S06",
    "passage": "digital native audience based in the USA",
    "locator": "The challenge and Our solution."
   }
  ],
  "passage": "digital native audience based in the USA",
  "scope_geo": "US where specified; other territories only as cited.",
  "scope_time": "as read 2026-11-11",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "This one placement case does not establish the sale of a separate modeled audience, and an offer of lookalikes elsewhere does not establish that this US customer used one. Keep outside C absent a stronger exact-offer link.",
  "claim_status": "actual",
  "chapter": "",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Final example names Michigan; preceding paragraphs identify managed and curation routes and optional voter audience combinations.. Aristotle’s voter IDs are a separate, optional combined offering; neither attribute them to the cookieless segment nor classify the entire curated deal as the sold audience.",
  "checked_independently": true,
  "id": "IDN-SCD-F07",
  "claim": "Seedtag’s October 2026 announcement describes an available managed US political targeting route and gives a Michigan example combining separate Aristotle voter audiences and Seedtag contextual segments.",
  "final_wording": "Seedtag’s October 2026 announcement describes an available managed US political targeting route and gives a Michigan example combining separate Aristotle voter audiences and Seedtag contextual segments.",
  "source_ids": [
   "IDN-SCD-S07"
  ],
  "support": [
   {
    "source_id": "IDN-SCD-S07",
    "passage": "Seedtag’s Housing & Affordability contextual segments",
    "locator": "Final example names Michigan; preceding paragraphs identify managed and curation routes and optional voter audience combinations."
   }
  ],
  "passage": "Seedtag’s Housing & Affordability contextual segments",
  "scope_geo": "US where specified; other territories only as cited.",
  "scope_time": "2026-10-21",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Aristotle’s voter IDs are a separate, optional combined offering; neither attribute them to the cookieless segment nor classify the entire curated deal as the sold audience.",
  "claim_status": "actual",
  "chapter": "8",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "Register-freeze second read of the original. Launch opening and Custom Audiences bullet; adjacent segments include Signature and Seasonal Audiences.. Historical launch and later named segments. Model threshold, US national footprint and current client ledgers undisclosed.",
  "checked_independently": true,
  "id": "IDN-SCD-F08",
  "claim": "Seedtag sells selectable audience groups as an alternative to third-party tracking. Custom Audiences derive URL scores from the advertiser’s brief. The 2026 Michigan targeting option corroborates the US buying path.",
  "final_wording": "Seedtag sells selectable audience groups as an alternative to third-party tracking. Custom Audiences derive URL scores from the advertiser’s brief. The 2026 Michigan targeting option corroborates the US buying path.",
  "source_ids": [
   "IDN-SCD-S08"
  ],
  "support": [
   {
    "source_id": "IDN-SCD-S08",
    "passage": "This model analyzes every URL and provides a score based on the most relevant content",
    "locator": "Launch opening and Custom Audiences bullet; adjacent segments include Signature and Seasonal Audiences."
   }
  ],
  "passage": "This model analyzes every URL and provides a score based on the most relevant content",
  "scope_geo": "US where specified; other territories only as cited.",
  "scope_time": "2023-10-18",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Specific provider, recipient, route and territory where known.",
  "limitations": "Historical launch and later named segments. Model threshold, US national footprint and current client ledgers undisclosed.",
  "claim_status": "actual",
  "chapter": "8, 12",
  "stream": "register freeze"
 },
 {
  "headline": false,
  "review_note": "The November 19, 2024 issuer release puts 90% on the joint MediaWallah–Lexicon onboarding and real-time identity offering. No observed geography, measurement period, eligible record count or method for averaging the individual rates is supplied.",
  "checked_independently": true,
  "id": "IDN-HX-F01",
  "claim": "A 2024 joint announcement claims a 90% average bidstream match rate for the MediaWallah and 33Across Lexicon offering. It does not identify the eligible records, averaging weights or test geography.",
  "final_wording": "A 2024 joint announcement claims a 90% average bidstream match rate for the MediaWallah and 33Across Lexicon offering. It does not identify the eligible records, averaging weights or test geography.",
  "source_ids": [
   "IDN-HX-S01"
  ],
  "support": [
   {
    "source_id": "IDN-HX-S01",
    "passage": "an average 90% match rate in the bidstream",
    "locator": "Opening announcement, first paragraph."
   }
  ],
  "passage": "an average 90% match rate in the bidstream",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Combined offering; not a measured Lexicon-only rate. The 33Across web version returned 403 in the web reader; the wire service carried the issuers’ original release.",
  "hypothesis": "H1",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "A US national QSR used an OTT/CTV platform which supplied over 2 million hashed primary IPs: 1.7M in exposure and approximately 300K control. The graph reportedly achieved 66.1% against both groups. No acceptance rule, absolute matched counts, distinctness rule or campaign dates are given. The confidence interval and purchases reported later concern campaign lift.",
  "checked_independently": true,
  "id": "IDN-HX-F02",
  "claim": "Kochava reports a 66.1% graph match against the exposure and control groups in one US restaurant campaign. Its case names hashed primary IPs and a household graph but does not specify a match-acceptance rule.",
  "final_wording": "Kochava reports a 66.1% graph match against the exposure and control groups in one US restaurant campaign. Its case names hashed primary IPs and a household graph but does not specify a match-acceptance rule.",
  "source_ids": [
   "IDN-U-S56"
  ],
  "support": [
   {
    "source_id": "IDN-U-S56",
    "passage": "a 66.1% match rate against both groups",
    "locator": "Solution, first paragraph, after the exposure and control group figures."
   }
  ],
  "passage": "a 66.1% match rate against both groups",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "The OTT platform supplied about two million hashed primary IPs. The case describes a managed measurement engagement; no separate licensed graph SKU was confirmed.",
  "hypothesis": "H1",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Lotame provides a browser-specific opt-out. A stored Panorama ID can take up to seven days to expire, and the platform may take several hours to process the request. If third-party cookies are unavailable, probabilistic browser recognition can fail and a new ID can be assigned. The platform policy describes a service rule without supplying a bidder receipt.",
  "checked_independently": true,
  "id": "IDN-HX-F03",
  "claim": "Lotame says its browser opt-out stops its use of Panorama ID and that a previously stored ID may take up to seven days to expire. This describes Lotame’s browser handling; the notice does not demonstrate a bidder acting on the same choice.",
  "final_wording": "Lotame says an opt-out applies to the requesting browser and a stored Panorama ID can take up to seven days to expire. If third-party cookies are blocked, Lotame says its probabilistic recognition may fail and it may assign a new ID. The notice does not demonstrate a bidder acting on the request.",
  "source_ids": [
   "IDN-HX-S03"
  ],
  "support": [
   {
    "source_id": "IDN-HX-S03",
    "passage": "up to 7-days for that Panorama ID to expire",
    "locator": "Global Opt-Out Tools, Browser Opt-Out Tools, third-party-cookie browser."
   }
  ],
  "passage": "up to 7-days for that Panorama ID to expire",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "US/EU self-regulatory tools, and restrictions when third-party cookies are blocked, are separate from receipt of an opt-out by a DSP.",
  "hypothesis": "H3",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": "4"
 },
 {
  "headline": false,
  "review_note": "The source lists all five parameters and shows an example ID-resolution URL. Where its blocked-call handler applies, it says identity resolution and other network calls are blocked entirely. It names no downstream bidder treatment of a particular nonID.",
  "checked_independently": true,
  "id": "IDN-HX-F04",
  "claim": "LiveIntent documents sending the GDPR flag and consent string, US Privacy string, GPP string and applicable sections to its identity-resolution endpoint. The guide does not prescribe how a downstream bidder must act on a particular nonID.",
  "final_wording": "LiveIntent’s guide lists a GDPR flag and consent string, US Privacy string, GPP string and applicable sections on eligible identity-resolution requests; in privacy mode, the guide says the hub blocks identity-resolution requests. It gives no downstream bidder rule for a particular nonID.",
  "source_ids": [
   "IDN-HX-S04"
  ],
  "support": [
   {
    "source_id": "IDN-HX-S04",
    "passage": "GPP applicable sections",
    "locator": "Identity Resolution (Idres) URLs, gpp_as."
   }
  ],
  "passage": "GPP applicable sections",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Identity endpoint, not the buying platform. Current public guide and separate programmatic API reviewed.",
  "hypothesis": "H3",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": "4"
 },
 {
  "headline": false,
  "review_note": "Page 1, lines 14–20 of the publisher PDF assign interpretation of the 2020 US privacy signal to the recipient. That statement is historical and cannot establish GPP rules at the 2026 cutoff.",
  "checked_independently": true,
  "id": "IDN-HX-F05",
  "claim": "TripleLift’s California FAQ says it forwards consent status with the bid request and leaves the targeting response to the DSP. Its exchange listing of an identifier in a US bid path does not alone establish how a recipient must use that identifier after refusal.",
  "final_wording": "In a 2020 California publisher FAQ, TripleLift said it forwarded the bid request and the consent status to the DSP and left targeting to the DSP. This historical exchange policy does not identify how a particular bidder handles a particular advertising ID.",
  "source_ids": [
   "IDN-HX-S05"
  ],
  "support": [
   {
    "source_id": "IDN-HX-S05",
    "passage": "it is up to the DSP to interpret in their platform how to target.",
    "locator": "Single-page PDF, answer to “If a user opts out, how does TripleLift action off of that signal?”"
   }
  ],
  "passage": "it is up to the DSP to interpret in their platform how to target.",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "A historical US Privacy string route. The current user-rights policy also treats GPC as a distinct signal. No common configured GPC-to-ID bid mapping across named products follows.",
  "hypothesis": "H3",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": "4"
 },
 {
  "headline": false,
  "review_note": "33Across announced Lexicon June 2, 2021 as a cookie-replacement, graph-based publisher offer. The release itself explicitly names the US browser launch footprint, the built-in graph and the Pub Token. Neither the advertised reach nor the New York Post quote measures actual link accuracy or demonstrates the continued use of a predecessor graph.",
  "checked_independently": true,
  "id": "IDN-HY-F01",
  "claim": "33Across introduced Lexicon for publishers without cookies. The publisher graph and its output token are explicitly described. A US media buyer route is separately established by the Prebid market list and TripleLift.",
  "final_wording": "33Across introduced Lexicon for publishers without cookies. The publisher graph and its output token are explicitly described. A US media buyer route is separately established by the Prebid market list and TripleLift.",
  "source_ids": [
   "IDN-HY-S01"
  ],
  "support": [
   {
    "source_id": "IDN-HY-S01",
    "passage": "Built-in Publisher Graph",
    "locator": "Dateline and first paragraph; New York Post participant quotation; KEY CAPABILITIES, item 1."
   }
  ],
  "passage": "Built-in Publisher Graph",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "33Across introduced Lexicon for publishers without cookies. The publisher graph and its output token are explicitly described. A US media buyer route is separately established by the Prebid market list and TripleLift.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "The December 16, 2020 body says the Fabrick ID accepts phone/email and links a consumer/household graph to publisher data; SSPs can substitute an ID via API. The December release is specifically for the ID, not the earlier suite. Its Virginia dateline alone does not establish the population of buyers at launch; the later TripleLift table records US passthrough. It does not establish continuity of an identified set of edges.",
  "checked_independently": true,
  "id": "IDN-HY-F02",
  "claim": "Neustar launched the particular Fabrick ID in December, distinguished from its July Fabrick platform launch. The release markets a consumer- and household-graph identifier to publishers as an alternative to third-party cookies.",
  "final_wording": "On December 16, 2020, Neustar announced Fabrick ID for graph-based linkage of publisher and advertiser data without third-party cookies. The later TripleLift table documents a US passthrough route. The announcement does not show a US deployment at launch or continued predecessor edges.",
  "source_ids": [
   "IDN-HY-S02"
  ],
  "support": [
   {
    "source_id": "IDN-HY-S02",
    "passage": "our unique consumer and household graph",
    "locator": "Opening ID launch, Steve Silvers quotation and next paragraph on publisher API; PubMatic quotation."
   }
  ],
  "passage": "our unique consumer and household graph",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Neustar launched the particular Fabrick ID in December, distinguished from its July Fabrick platform launch. The release markets a consumer- and household-graph identifier to publishers as an alternative to third-party cookies.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "The June 9, 2020 multinational announcement differs from a later July retrospective. It states that ID+ extends a graph available across North America, Latin America, Europe and India. Neither the region list nor its joint US dateline confirms that ID+ was a specifically US commercial offer on that date. It contains no operational lineage mapping.",
  "checked_independently": true,
  "id": "IDN-HY-F03",
  "claim": "Zeotap announced ID+ June 9, 2020, earlier than the retrospective July description. The launch calls it an extension of a graph available across North America, Latin America, Europe and India. The graph’s geography and New York dateline do not prove a US ID+ launch.",
  "final_wording": "Zeotap announced ID+ June 9, 2020, earlier than the retrospective July description. The launch calls it an extension of a graph available across North America, Latin America, Europe and India. The graph’s geography and New York dateline do not prove a US ID+ launch.",
  "source_ids": [
   "IDN-HY-S03"
  ],
  "support": [
   {
    "source_id": "IDN-HY-S03",
    "passage": "demise of third-party cookies",
    "locator": "Lead datelined New York/Berlin/London/Bengaluru; paragraph after founding principles describing geographic scope of the underlying graph."
   }
  ],
  "passage": "demise of third-party cookies",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Zeotap announced ID+ June 9, 2020, earlier than the retrospective July description. The launch calls it an extension of a graph available across North America, Latin America, Europe and India. The graph’s geography and New York dateline do not prove a US ID+ launch.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Permutive’s own July 26, 2024 changelog lists Topics-based custom cohorts and an optional Prebid bid-request path. After workspace enablement opted-in Topics are automatically synced via the SDK; making them available in bid requests additionally depends on Prebid integration and the option selected. These are Topics, not third-party cookie ID sync. The record supplies no US-standard-cohort implementation, general US default, before/after pair or TV household accuracy test.",
  "checked_independently": true,
  "id": "IDN-HY-F04",
  "claim": "The SDK integration offered custom cohort creation from Topics and optional Topics retrieval for bid requests. It does not establish use in the US standard-cohort PPS route, a US default, or third-party-cookie syncing.",
  "final_wording": "Permutive’s July 26, 2024 product changelog describes optional Topics-based custom cohorts and conditional sending of opted-in Topics through Prebid. It supplies H4 implementation context, not an H8 US graph launch, a US Chrome cookie-sync default, or H5 link validation.",
  "source_ids": [
   "IDN-HY-S04"
  ],
  "support": [
   {
    "source_id": "IDN-HY-S04",
    "passage": "create custom cohorts",
    "locator": "Original HTML time datetime and datePublished, then numbered use-case 3."
   }
  ],
  "passage": "create custom cohorts",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "The SDK integration offered custom cohort creation from Topics and an optional Prebid path for adding Topics to bid requests if the publisher selected the setting. It does not establish use in the US standard-cohort PPS route, a US default, or third-party-cookie syncing.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "qualified",
  "checked_independently": true,
  "id": "IDN-B5-F01",
  "claim": "On January 4, 2024, TransUnion said its enhanced marketing identity graph represented 250 million adults and 98% of US adults. Its Snowflake Resolution & Enrichment offer uses that graph to match client records.",
  "final_wording": "On January 4, 2024, TransUnion said the enhanced graph used by TruAudience Identity Resolution represented 250 million adults and 98% of US adults. In its January 2026 Snowflake guide, it said the Resolution & Enrichment offer matched client records using its identity graph.",
  "source_ids": [
   "IDN-C-S12",
   "IDN-CV-S02"
  ],
  "support": [
   {
    "source_id": "IDN-C-S12",
    "locator": "Key performance indicators, first bullet on coverage and list of identity solutions",
    "passage": "98% of the U.S. adult population"
   },
   {
    "source_id": "IDN-CV-S02",
    "locator": "TruAudience Identity Resolution & Enrichment, second paragraph",
    "passage": "250M US consumers."
   }
  ],
  "passage": "98% of the U.S. adult population | 250M US consumers.",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Issuer snapshot of adults in the reference graph. The denominator is US adults. No client-file match rate or separately verified count, sampling, deduplication or exact census date.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "confirmed",
  "checked_independently": true,
  "id": "IDN-B5-F02",
  "claim": "TransUnion’s Snowflake Resolution & Enrichment offer describes an individual identifier that customers can use to unify customer records and digital engagement data.",
  "final_wording": "TransUnion’s Snowflake Resolution & Enrichment offer describes an individual identifier that customers can use to unify customer records and digital engagement data.",
  "source_ids": [
   "IDN-CV-S02"
  ],
  "support": [
   {
    "source_id": "IDN-CV-S02",
    "locator": "TruAudience Identity Resolution & Enrichment, last paragraph before Extracts",
    "passage": "same individual identifier"
   }
  ],
  "passage": "same individual identifier",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "A customer-facing individual key on the resolution workflow. No physical column name, versioned output schema or concrete valid row.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "confirmed",
  "checked_independently": true,
  "id": "IDN-B5-F03",
  "claim": "Epsilon says it cleans and matches contact data from the client’s offline file to Core IDs and associates the client’s customer IDs and transactions with those Core IDs.",
  "final_wording": "Epsilon says it cleans and matches contact data from the client’s offline file to Core IDs and associates the client’s customer IDs and transactions with those Core IDs.",
  "source_ids": [
   "IDN-U-S19"
  ],
  "support": [
   {
    "source_id": "IDN-U-S19",
    "locator": "Core ID Services, Nature of the Processing, first file-onboarding bullet and subsequent tracking-code bullet",
    "passage": "The customer IDs and transactions will be placed into Client’s client-profile tied to the assigned Core IDs."
   }
  ],
  "passage": "The customer IDs and transactions will be placed into Client’s client-profile tied to the assigned Core IDs.",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "The client supplies the file. Its original collection events are not specified. Tagged digital events and client-exclusive first-party cookies occur in the separately described tag flow. The specification establishes a contracted workflow, not a test of a live client file.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Independent read of the Prebid.js 5.0.0 release and the version-specific Prebid guide confirmed the pre/post-merge EID.",
  "checked_independently": true,
  "id": "IDN-VA5-F01",
  "claim": "Prebid.js 5.0.0, released June 10, 2021, merged the PubCommon and SharedID submodules. Prebid’s identity guide illustrates the earlier sharedid.org EID and third-party sync, and a later first-party path with a pubcid.org EID.",
  "final_wording": "Prebid.js 5.0.0, released June 10, 2021, merged the PubCommon and SharedID submodules. Prebid’s identity guide illustrates the earlier sharedid.org EID and third-party sync, and a later first-party path with a pubcid.org EID.",
  "source_ids": [
   "IDN-VA5-S01",
   "IDN-U-S13"
  ],
  "support": [
   {
    "source_id": "IDN-VA5-S01",
    "passage": "Pubcommon id and shared id submodules: merge into one submodule",
    "locator": "Release 5.0.0, June 10, 2021; item linked to PR 6808"
   },
   {
    "source_id": "IDN-U-S13",
    "passage": "PubCommon was folded into SharedID",
    "locator": "SharedID and Prebid.js, before Before Prebid.js 5.0; adjacent sample EIDs"
   }
  ],
  "passage": "Pubcommon id and shared id submodules: merge into one submodule | PubCommon was folded into SharedID",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "The release dates the merge; the Prebid project’s separate version-specific guide describes old and new EID payloads.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": "5"
 },
 {
  "headline": false,
  "review_note": "The module explains a request-derived identifier for a device and a separate modeled relationship between devices. IP, user agent and timestamp can inform the request. A publisher requests a Lotame client ID.",
  "checked_independently": true,
  "id": "IDN-AS5-F01",
  "claim": "The Panorama module generates a device-representing ID from request signals. Lotame’s graph uses hashed email, browser and device data with predictive models. Publishers register for a client ID.",
  "final_wording": "The Panorama module generates a device-representing ID from request signals. Lotame’s graph uses hashed email, browser and device data with predictive models. Publishers register for a client ID.",
  "source_ids": [
   "IDN-A-S15"
  ],
  "support": [
   {
    "source_id": "IDN-A-S15",
    "locator": "Overview; Registration & Implementation",
    "passage": "a group of devices may be used by the same user"
   }
  ],
  "passage": "a group of devices may be used by the same user",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Lotame’s October 28, 2020 launch statement promoted high targeting accuracy and a one-time, persistent opt-out. It reports no test of Panorama’s right-person link accuracy and gives no implementation sequence establishing enforcement.",
  "checked_independently": true,
  "id": "IDN-AS5-F02",
  "claim": "Lotame’s launch statement claimed higher accuracy for Panorama ID and a persistent consumer opt-out across touchpoints. The statement supplies no reference accuracy test or enforcement sequence.",
  "final_wording": "Lotame’s October 28, 2020 launch statement promoted high targeting accuracy and a one-time, persistent opt-out. It reports no test of Panorama’s right-person link accuracy and gives no implementation sequence establishing enforcement.",
  "source_ids": [
   "IDN-C-S15"
  ],
  "support": [
   {
    "source_id": "IDN-C-S15",
    "locator": "October 2020 launch, opening and targeting/accuracy bullet",
    "passage": "universal and persistent opt-out"
   }
  ],
  "passage": "universal and persistent opt-out",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "On the first-party SharedID path the module can read or set a random ID. Its TCF check can skip reading and setting cookies when Purpose 1 consent is absent, the publisher opt-out cookie prevents further cookie setting, and the COPPA flag suppresses the ID. Prebid’s versioned walkthrough distinguishes the older sharedid.org EID from the pubcid.org EID after the 5.0 merge.",
  "checked_independently": true,
  "id": "IDN-AS5-F03",
  "claim": "SharedID reads or sets a random first-party ID. Permitted publisher page loads can set the cookie, while missing Purpose 1 consent with the TCF module, an opt-out marker, or a COPPA flag inhibits specified activity.",
  "final_wording": "On the first-party SharedID path the module can read or set a random ID. Its TCF check can skip reading and setting cookies when Purpose 1 consent is absent, the publisher opt-out cookie prevents further cookie setting, and the COPPA flag suppresses the ID. Prebid’s versioned walkthrough distinguishes the older sharedid.org EID from the pubcid.org EID after the 5.0 merge.",
  "source_ids": [
   "IDN-U-S13",
   "IDN-VA5-S01"
  ],
  "support": [
   {
    "source_id": "IDN-U-S13",
    "locator": "What is it? Detailed Walkthrough; Privacy Discussion and Opt-Out",
    "passage": "when the COPPA flag is set."
   }
  ],
  "passage": "when the COPPA flag is set.",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "The module is available without registration. A publisher can configure the storage period and choose per-load expiry extension. The sample bidRequest.userId.sharedid is an adapter-facing field. Prebid’s versioned guide uses pubcid.org as the later outgoing EID source.",
  "checked_independently": true,
  "id": "IDN-AS5-F04",
  "claim": "The SharedID configuration defines per-page-load extension, configurable storage lifetime and a sample bidRequest.userId.sharedid object. Unrestricted publishers can install the module.",
  "final_wording": "The module is available without registration. A publisher can configure the storage period and choose per-load expiry extension. The sample bidRequest.userId.sharedid is an adapter-facing field. Prebid’s versioned guide uses pubcid.org as the later outgoing EID source.",
  "source_ids": [
   "IDN-A-S18",
   "IDN-U-S13",
   "IDN-VA5-S01"
  ],
  "support": [
   {
    "source_id": "IDN-A-S18",
    "locator": "Header; SharedID ID Configuration; Examples",
    "passage": "refreshed during each page load."
   }
  ],
  "passage": "refreshed during each page load.",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "33Across describes Lexicon’s publisher-to-demand connection as probabilistic. The optional SHA-256 email lookup checks configured hem, global _33across.hem.sha256 and then browser storage. The external source is 33across.com and the adapter field is 33acrossId.",
  "checked_independently": true,
  "id": "IDN-AS5-F05",
  "claim": "33Across calls its Lexicon connection probabilistic, accepts optional SHA256 hashed email, and lists prioritized publisher settings, a global variable and browser storage as sources.",
  "final_wording": "33Across describes Lexicon’s publisher-to-demand connection as probabilistic. The optional SHA-256 email lookup checks configured hem, global _33across.hem.sha256 and then browser storage. The external source is 33across.com and the adapter field is 33acrossId.",
  "source_ids": [
   "IDN-U-S50"
  ],
  "support": [
   {
    "source_id": "IDN-U-S50",
    "locator": "Overview; HEM Collection",
    "passage": "configuration parameter, global"
   }
  ],
  "passage": "configuration parameter, global",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "The partner ID identifies an authorized publisher. The module lists US, Canada, Australia and Japan, shows the bidder key and sample value, and recommends an eight-hour refresh interval for the local ID.",
  "checked_independently": true,
  "id": "IDN-AS5-F06",
  "claim": "The 33Across module recommends refreshing the ID after eight hours, shows its bidder field and sample value, and accepts US publishers through partner ID authorization.",
  "final_wording": "The 33Across module recommends refreshing the ID after eight hours, shows its bidder field and sample value, and accepts US publishers through partner ID authorization.",
  "source_ids": [
   "IDN-U-S50"
  ],
  "support": [
   {
    "source_id": "IDN-U-S50",
    "locator": "Overview; header example; 33Across ID Configuration, storage.refreshInSeconds and params.pid",
    "passage": "For Lexicon, we only support US/CAN/AUS/JP."
   }
  ],
  "passage": "For Lexicon, we only support US/CAN/AUS/JP.",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Audigent requires a partner key. The module shows a hadronId object and recommends 14 days for optional storage.expires on the publisher side. This time applies to storage of the returned value.",
  "checked_independently": true,
  "id": "IDN-AS5-F07",
  "claim": "Audigent’s partner-keyed module supplies a sample resolved Hadron ID object to bidders. Its optional 14-day setting concerns publisher-side storage.",
  "final_wording": "Audigent’s partner-keyed module supplies a sample resolved Hadron ID object to bidders. Its optional 14-day setting concerns publisher-side storage.",
  "source_ids": [
   "IDN-UV-S05"
  ],
  "support": [
   {
    "source_id": "IDN-UV-S05",
    "locator": "HadronId Configuration: example result and storage.expires",
    "passage": "How long (in days) the user ID information will be stored."
   }
  ],
  "passage": "How long (in days) the user ID information will be stored.",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "The module accepts hashed email, phone and other eligible first-party inputs. The sample passes an API key and hashed email. Its module header names the Fabrick bidder field and gives a value.",
  "checked_independently": true,
  "id": "IDN-AS5-F08",
  "claim": "Fabrick links hashed email, phone and other submitted identifiers to the Fabrick ID. A publisher passes its API key and a hashed email in the example. The provider documents the bidder field and specimen output.",
  "final_wording": "Fabrick links hashed email, phone and other submitted identifiers to the Fabrick ID. A publisher passes its API key and a hashed email in the example. The provider documents the bidder field and specimen output.",
  "source_ids": [
   "IDN-UV-S08"
  ],
  "support": [
   {
    "source_id": "IDN-UV-S08",
    "locator": "Header; Fabrick Configuration (e, p, 1pd); Fabrick Examples",
    "passage": "hashed email address"
   }
  ],
  "passage": "hashed email address",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "The tracking-limit instruction on params.lmt requires the sender to withhold the real IFA from ia when tracking is limited. The guide permits a synthetic or session IFA.",
  "checked_independently": true,
  "id": "IDN-AS5-F09",
  "claim": "When a user requests tracking limitation, the submitting party must withhold the real IFA from the Fabrick ia parameter. A synthetic or session IFA is allowed.",
  "final_wording": "When a user requests tracking limitation, the submitting party must withhold the real IFA from the Fabrick ia parameter. A synthetic or session IFA is allowed.",
  "source_ids": [
   "IDN-UV-S08"
  ],
  "support": [
   {
    "source_id": "IDN-UV-S08",
    "locator": "Fabrick Configuration, params.lmt",
    "passage": "the real IFA must not be sent"
   }
  ],
  "passage": "the real IFA must not be sent",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "The publisher submits authenticated-user email as a supported hash. Epsilon marks the site ID and API key it supplies as required and links a Publisher Link opt-out.",
  "checked_independently": true,
  "id": "IDN-AS5-F10",
  "claim": "PubLink’s guide identifies a publisher’s hashed email for authenticated users and requires an issuer-provided site ID and API key. It directs users to its product opt-out.",
  "final_wording": "PubLink’s guide identifies a publisher’s hashed email for authenticated users and requires an issuer-provided site ID and API key. It directs users to its product opt-out.",
  "source_ids": [
   "IDN-A5-S05"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S05",
    "locator": "Publisher Link; Publisher Link Registration; Publisher Link Configuration, params.e, params.site_id and params.api_key",
    "passage": "The Publisher Link opt-out is included here"
   }
  ],
  "passage": "The Publisher Link opt-out is included here",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "FTrack describes probabilistic device recognition and configurable output selection. The header explicitly lists no EID source or bidder userId field.",
  "checked_independently": true,
  "id": "IDN-AS5-F11",
  "claim": "FTrack identifies its probabilistic device output and ID selection controls. The guide lists no external EID namespace or bidder userId field in its header.",
  "final_wording": "FTrack identifies its probabilistic device output and ID selection controls. The guide lists no external EID namespace or bidder userId field in its header.",
  "source_ids": [
   "IDN-A5-S06"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S06",
    "locator": "Header; opening; FTrack configuration, params.ids and storage.refreshInSeconds",
    "passage": "uses probabilistic device recognition"
   }
  ],
  "passage": "uses probabilistic device recognition",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Prebid shows the shape of the sample request object and describes how adapters can send the ID. The guide gives no observed bid request, bidder receipt or auction outcome for the sample.",
  "checked_independently": true,
  "id": "IDN-AS5-F12",
  "claim": "Prebid’s LiveIntent guide describes a model built from calls on each page load. The module uses first-party cookies and requests a nonID from the resolution API. The guide shows an example value in request.userId.lipb.lipbid.",
  "final_wording": "Prebid’s LiveIntent guide describes a model built from calls on each page load. The module uses first-party cookies and requests a nonID from the resolution API. The guide shows an example value in request.userId.lipb.lipbid.",
  "source_ids": [
   "IDN-A5-S07"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S07",
    "locator": "How LiveIntent user ID sub-module works, first paragraph; Identity resolution, first paragraph; LiveIntent nonID, example request.userId.lipb object and lipbid field.",
    "passage": "data collected through an additional call issued on each page load"
   }
  ],
  "passage": "data collected through an additional call issued on each page load",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "The publisher can set the opt-out marker to prevent further cookie setting on module runs. Separately, an example normal script configuration lets an existing cookie expire before creating another. It describes ordinary expiry with that configuration, not recreation after opt-out.",
  "checked_independently": true,
  "id": "IDN-AS5-F13",
  "claim": "The SharedID guide describes publisher-side opt-out input and suppression at forthcoming module runs. Its script example allows the cookie to expire and then be created again.",
  "final_wording": "The publisher can set the opt-out marker to prevent further cookie setting on module runs. Separately, an example normal script configuration lets an existing cookie expire before creating another. It describes ordinary expiry with that configuration, not recreation after opt-out.",
  "source_ids": [
   "IDN-U-S13"
  ],
  "support": [
   {
    "source_id": "IDN-U-S13",
    "locator": "Opt-Out; SharedId Script, Example Configurations; Privacy Discussion",
    "passage": "allowed to expire"
   }
  ],
  "passage": "allowed to expire",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_with_qualification",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Equativ’s worked OneCall POST contains a Criteo source and specimen ID. Network-level enablement for frequency capping is separately qualified. The sample illustrates transport and does not document a production impression.",
  "checked_independently": true,
  "id": "IDN-AS5-F14",
  "claim": "Equativ gives a concrete Criteo namespace example in a OneCall POST ad request. Its guide distinguishes provider-level support and per-network frequency-capping enablement.",
  "final_wording": "Equativ gives a concrete Criteo namespace example in a OneCall POST ad request. Its guide distinguishes provider-level support and per-network frequency-capping enablement.",
  "source_ids": [
   "IDN-A5-S03"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S03",
    "locator": "Example OneCall POST; Frequency capping based on extended IDs",
    "passage": "my_ID_from_Criteo"
   }
  ],
  "passage": "my_ID_from_Criteo",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "No module-specific configuration parameter is needed to install the Criteo module. It gives a bidder key and sample value, describes its own caching and conditions bidder use on adapter implementation.",
  "checked_independently": true,
  "id": "IDN-AS5-F15",
  "claim": "Criteo’s Prebid module labels the Criteo bidder key and gives its value, permits installation without parameters, and uses its own caching mechanism.",
  "final_wording": "Criteo’s Prebid module labels the Criteo bidder key and gives its value, permits installation without parameters, and uses its own caching mechanism.",
  "source_ids": [
   "IDN-A-S17"
  ],
  "support": [
   {
    "source_id": "IDN-A-S17",
    "locator": "Header; Criteo ID Configuration and Example",
    "passage": "provided that bidders use it in their adapters"
   }
  ],
  "passage": "provided that bidders use it in their adapters",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Lotame’s SSP instructions describe receiving a 64-character, unencrypted Panorama ID in the EID list. Lotame states no fee for publishers or SSPs to use the ID.",
  "checked_independently": true,
  "id": "IDN-AS5-F16",
  "claim": "Lotame describes how SSPs accept its 64-character unencrypted EID and states that the publisher and SSP do not pay to use Panorama ID.",
  "final_wording": "Lotame describes how SSPs accept its 64-character unencrypted EID and states that the publisher and SSP do not pay to use Panorama ID.",
  "source_ids": [
   "IDN-U-S10"
  ],
  "support": [
   {
    "source_id": "IDN-U-S10",
    "locator": "Instructions for SSPs Adopting the Panorama ID in the Bidstream; numbered step 1",
    "passage": "64 character unencrypted Panorama ID"
   }
  ],
  "passage": "64 character unencrypted Panorama ID",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "The publisher’s FTrack library URL must be present. The ids settings select which identifiers can be returned. The guide does not state the underlying signals used for the probabilistic device model.",
  "checked_independently": true,
  "id": "IDN-AS5-F17",
  "claim": "Mode selection in the FTrack module changes which identifiers may be returned. The publisher must supply the library URL; no input signal used by the probabilistic device model is named.",
  "final_wording": "Mode selection in the FTrack module changes which identifiers may be returned. The publisher must supply the library URL; no input signal used by the probabilistic device model is named.",
  "source_ids": [
   "IDN-A5-S06"
  ],
  "support": [
   {
    "source_id": "IDN-A5-S06",
    "locator": "FTrack device ID configuration, params.url and params.ids",
    "passage": "If not populated, ftrack will not run."
   }
  ],
  "passage": "If not populated, ftrack will not run.",
  "scope_geo": "United States buying task; scope limited to the named record.",
  "scope_time": "Through 2026-11-11; see dated source and locator",
  "figure_kind": "none",
  "derivation": "",
  "evidence_class": "direct_record",
  "review_outcome": "supported_as_stated",
  "confidence": "medium",
  "confidence_reason": "Independent reading of the underlying source. Publicly described scope retained.",
  "limitations": "Product- and version-specific technical guidance; it does not certify production enforcement.",
  "hypothesis": "",
  "claim_status": "actual",
  "stream": "supplemental verification",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Second source reader independently opened the May 18, 2016 repost, lines 33–35; small subset and tier selection are explicit. H2 historical study lead only.",
  "checked_independently": true,
  "id": "IDN-HX-F06",
  "claim": "A 2016 repost of a Conversant announcement describes comScore validating a subset of historical cross-device links and reports a range for the top four of six tiers. It does not identify a current Epsilon CORE ID version or supply an independent US person-level test denominator.",
  "final_wording": "A 2016 repost of a Conversant announcement describes comScore validating a subset of historical cross-device links and reports a range for the top four of six tiers. It does not identify a current Epsilon CORE ID version or supply an independent US person-level test denominator.",
  "source_ids": [
   "IDN-HX-S06"
  ],
  "support": [
   {
    "source_id": "IDN-HX-S06",
    "passage": "a subset of these for cross-device matching",
    "locator": "May 18 repost of the April 7 announcement, opening three paragraphs, web reader lines 33–39."
   }
  ],
  "passage": "a subset of these for cross-device matching",
  "evidence_class": "vendor_assertion",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "hypothesis": "H2",
  "chapter": ""
 },
 {
  "headline": true,
  "review_note": "Separate readers of the abstract and method verified the declaration, named employer boundaries and public working-group biography.",
  "checked_independently": true,
  "id": "IDN-METHOD-F01",
  "claim": "Evgeny Popov has worked at Samba TV since May 2025. Samba operates a household graph and sells TV measurement and ACR data. His former employers include Lotame, Verve Group and Hearts & Science. He co-leads the Signals & Measurement working group at AgenticAdvertising.org. Samba is excluded from IQ scoring. Lotame Panorama ID and Verve Moments.AI are flagged. His published positions motivated tests and did not supply product proof.",
  "final_wording": "Evgeny Popov has worked at Samba TV since May 2025. Samba operates a household graph and sells TV measurement and ACR data. His former employers include Lotame, Verve Group and Hearts & Science. He co-leads the Signals & Measurement working group at AgenticAdvertising.org. Samba is excluded from IQ scoring. Lotame Panorama ID and Verve Moments.AI are flagged. His published positions motivated tests and did not supply product proof.",
  "source_ids": [
   "IDN-METHOD-S01",
   "IDN-METHOD-S02"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S01",
    "passage": "Signals & Measurement working group",
    "locator": "Biography, introduction and career history; dates and disclosures supplemented by author’s signed-off project brief."
   },
   {
    "source_id": "IDN-METHOD-S02",
    "passage": "Samba TV",
    "locator": "Stable product rows: Samba, Lotame and Verve, relationship and status. See also RESEARCH-BRIEF.md, interests."
   }
  ],
  "passage": "Signals & Measurement working group | Samba TV",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "chapter": "abstract, 9, 10, 13"
 },
 {
  "headline": true,
  "review_note": "Independent method-chapter reviewer read the actual registered rule, cohort masks, admission and index files.",
  "checked_independently": true,
  "id": "IDN-METHOD-F02",
  "claim": "The frozen study evaluates public evidence for separate US buying tasks. The preregistration supplies populations and decision rules. Depth, Reach and Standing use cohort-specific scores, masks and caps. Legal records and author opinions are outside the IQ. Research, refutation and citation checks retain traceable source passages and dispositions, as recorded in the retained study files.",
  "final_wording": "The frozen study evaluates public evidence for separate US buying tasks. The preregistration supplies populations and decision rules. Depth, Reach and Standing use cohort-specific scores, masks and caps. Legal records and author opinions are outside the IQ. Research, refutation and citation checks retain traceable source passages and dispositions, as recorded in the retained study files.",
  "source_ids": [
   "IDN-METHOD-S03",
   "IDN-METHOD-S04"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S03",
    "passage": "assignment_method",
    "locator": "dimensions, cohort masks and index groups. RESEARCH-BRIEF.md and checks/stage-1.md document the registered workflow."
   },
   {
    "source_id": "IDN-METHOD-S04",
    "passage": "No scored product publishes",
    "locator": "H1–H8: full statements, populations, rules and tests."
   }
  ],
  "passage": "assignment_method | No scored product publishes",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "chapter": "abstract, 11, 13, appendix"
 },
 {
  "headline": true,
  "review_note": "Independent IQ-chapter reviewer recomputed all 24 admitted k values, excluded six unverified numerical cells and checked field bounds.",
  "checked_independently": true,
  "id": "IDN-IQ-F01",
  "claim": "The frozen register contains 57 records and 27 eligible products. Of these, 24 attained at least four counted cells. The IQ uses 142 counted cells across the admitted products and reports seven documentation bands, all in cohort A. Fourteen admitted products have thin records and three cannot receive a band because their cohort is too small. Each group, sensitivity result and cell is recorded in the official matrix.",
  "final_wording": "The frozen register contains 57 records and 27 eligible products. Of these, 24 attained at least four counted cells. The IQ uses 142 counted cells across the admitted products and reports seven documentation bands, all in cohort A. Fourteen admitted products have thin records and three cannot receive a band because their cohort is too small. Each group, sensitivity result and cell is recorded in the official matrix.",
  "source_ids": [
   "IDN-METHOD-S05",
   "IDN-METHOD-S07",
   "IDN-METHOD-S03"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S05",
    "passage": "coverage_by_group",
    "locator": "rows, scores, k, band, group means; quotient.cohorts including tests of weights, missingness and the prior"
   },
   {
    "source_id": "IDN-METHOD-S07",
    "passage": "counted_cells",
    "locator": "All 27 product IDs, admission floors and counts"
   },
   {
    "source_id": "IDN-METHOD-S03",
    "passage": "assignment_method",
    "locator": "Frozen anchors, IQ groups, weights, priors, masks and bands"
   }
  ],
  "passage": "coverage_by_group | counted_cells | assignment_method",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "chapter": "abstract, 11, 13, appendix"
 },
 {
  "headline": true,
  "review_note": "Independent adjudicator recomputed the frame or reviewed its case pairs and applied the frozen rule. Compare stage-7-rules-h123.json and the final clause.",
  "checked_independently": true,
  "id": "IDN-HYP-H1",
  "claim": "One admitted US case contradicted H1. Deep Sync reported matching 73.0% of one grocery chain’s monthly POS transactions to an inferred buyer through sequential loyalty, payment and household/location matching. The disclosed denominator, output population and method count as yield. Correct-person accuracy was not tested by that rate.",
  "final_wording": "One admitted US case contradicted H1. Deep Sync reported matching 73.0% of one grocery chain’s monthly POS transactions to an inferred buyer through sequential loyalty, payment and household/location matching. The disclosed denominator, output population and method count as yield. Correct-person accuracy was not tested by that rate.",
  "source_ids": [
   "IDN-METHOD-S06",
   "IDN-METHOD-S04",
   "IDN-C-S20"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S06",
    "passage": "H1",
    "locator": "H1: verdict, cases, eligible frame, unknowns and sensitivity. See verifying originals linked in the individual case records."
   },
   {
    "source_id": "IDN-METHOD-S04",
    "passage": "No",
    "locator": "H1, literal rule_contradicted and population"
   },
   {
    "source_id": "IDN-C-S20",
    "passage": "store-level geographic catchment modeling combined with household identity data",
    "locator": "The solution, pass 3, and cumulative result directly below"
   }
  ],
  "passage": "H1 | No | store-level geographic catchment modeling combined with household identity data",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "hypothesis": "H1",
  "derivation": "Apply the frozen H1 decision to product- or case-level results in data/hypothesis-results.json, including registered sensitivity tests.",
  "chapter": "abstract, 3, 11"
 },
 {
  "headline": true,
  "review_note": "Independent adjudicator recomputed the frame or reviewed its case pairs and applied the frozen rule. Compare stage-7-rules-h123.json and the final clause.",
  "checked_independently": true,
  "id": "IDN-HYP-H2",
  "claim": "H2 remains unresolved. No retrieved public test established independently labelled US person or household accuracy for an admitted named graph with the required attribution. Missing protocols, sponsor and unit information for credible historical cases prevent the negative claim from passing. The expanded eligible graph frame yielded the same verdict.",
  "final_wording": "H2 remains unresolved. No retrieved public test established independently labelled US person or household accuracy for an admitted named graph with the required attribution. Missing protocols, sponsor and unit information for credible historical cases prevent the negative claim from passing. The expanded eligible graph frame yielded the same verdict.",
  "source_ids": [
   "IDN-METHOD-S06",
   "IDN-METHOD-S04",
   "IDN-B-S01",
   "IDN-B-S02",
   "IDN-B-S04",
   "IDN-B-S05",
   "IDN-HX-S06"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S06",
    "passage": "H2",
    "locator": "H2: verdict, cases, eligible frame, unknowns and sensitivity. See verifying originals linked in the individual case records."
   },
   {
    "source_id": "IDN-METHOD-S04",
    "passage": "No",
    "locator": "H2, literal rule_unresolved and population"
   },
   {
    "source_id": "IDN-B-S01",
    "passage": "On average, across all providers, IP-to-postal linkages are accurate only 13% of the time",
    "locator": "Significant Variation Across Providers: IP-to-Postal"
   },
   {
    "source_id": "IDN-B-S02",
    "passage": "commissioned jointly by CIMM and Go Addressable",
    "locator": "Report introduction, second paragraph"
   },
   {
    "source_id": "IDN-B-S04",
    "passage": "LiveRamp’s graph was tested by comScore to have an industry leading 95%-98.9% precision",
    "locator": "Deterministic Matching, Note"
   },
   {
    "source_id": "IDN-B-S05",
    "passage": "Tapad achieved twice the precision of the next highest-scoring cross-screen offering",
    "locator": "Opening paragraph, New York, September 14, 2016"
   },
   {
    "source_id": "IDN-HX-S06",
    "passage": "a subset of these for cross-device matching",
    "locator": "May 18 repost of the April 7 announcement, opening three paragraphs, web reader lines 33–39."
   }
  ],
  "passage": "H2 | No | On average, across all providers, IP-to-postal linkages are accurate only 13% of the time | commissioned jointly by CIMM and Go Addressable | LiveRamp’s graph was tested by comScore to have an industry leading 95%-98.9% precision | Tapad achieved twice the precision of the next highest-scoring cross-screen offering | a subset of these for cross-device matching",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "hypothesis": "H2",
  "derivation": "Apply the frozen H2 decision to product- or case-level results in data/hypothesis-results.json, including registered sensitivity tests.",
  "chapter": "abstract, 3"
 },
 {
  "headline": true,
  "review_note": "Independent adjudicator recomputed the frame or reviewed its case pairs and applied the frozen rule. Compare stage-7-rules-h123.json and the final clause.",
  "checked_independently": true,
  "id": "IDN-HYP-H3",
  "claim": "H3 was contradicted in the confirmed US-available product frame. Two of thirteen products documented all links in at least one applicable jurisdiction, nine did not meet the test and two remained unknown. Even counting those two as successes gives four of thirteen. Six more products had unresolved eligibility, and the expanded bounds of two to ten out of nineteen cross half. Jurisdiction-specific scopes are reported separately.",
  "final_wording": "H3 was contradicted in the confirmed US-available product frame. Two of thirteen products documented all links in at least one applicable jurisdiction, nine did not meet the test and two remained unknown. Even counting those two as successes gives four of thirteen. Six more products had unresolved eligibility, and the expanded bounds of two to ten out of nineteen cross half. Jurisdiction-specific scopes are reported separately.",
  "source_ids": [
   "IDN-METHOD-S06",
   "IDN-METHOD-S04",
   "IDN-A-S08",
   "IDN-UID-S18",
   "IDN-A-S09",
   "IDN-ID5-S06",
   "IDN-ID5-S09",
   "IDN-LR-S03",
   "IDN-HX-S04"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S06",
    "passage": "H3",
    "locator": "H3: verdict, cases, eligible frame, unknowns and sensitivity. See verifying originals linked in the individual case records."
   },
   {
    "source_id": "IDN-METHOD-S04",
    "passage": "More",
    "locator": "H3, literal rule_contradicted and population"
   },
   {
    "source_id": "IDN-A-S08",
    "passage": "via a webhook provided for the purpose",
    "locator": "User opt-out, Difference between opting out from a single participant and opting out of UID2, and Opt-out workflow steps 1–3/table"
   },
   {
    "source_id": "IDN-UID-S18",
    "passage": "so they can honor your choice",
    "locator": "Disclosure of data by UID2 administrator, first bullet. Policy covers administrator only."
   },
   {
    "source_id": "IDN-A-S09",
    "passage": "typically within a few minutes",
    "locator": "Honor user opt-outs, Opt-out webhook and identity / timestamp rows"
   },
   {
    "source_id": "IDN-ID5-S06",
    "passage": "in case of no consent or optout",
    "locator": "Provided eids, example source and paragraph immediately below the example"
   },
   {
    "source_id": "IDN-ID5-S09",
    "passage": "every 30 minutes on a rolling basis for opt-outs and on a hourly basis for deletion requests",
    "locator": "Propagation Details, Frequency; Partner Responsibility & S3 Bucket Setup; Privacy Feeds, delivery-delay note"
   },
   {
    "source_id": "IDN-LR-S03",
    "passage": "a GPP National String is present before checking for the CCPA Privacy String as a fallback",
    "locator": "For Users in the U.S. (GPP and CCPA), first paragraph; For Users in the UK or EU (GDPR), EU and EEA wording; regional diagram."
   },
   {
    "source_id": "IDN-HX-S04",
    "passage": "GPP applicable sections",
    "locator": "Identity Resolution (Idres) URLs, gpp_as."
   }
  ],
  "passage": "H3 | More | via a webhook provided for the purpose | so they can honor your choice | typically within a few minutes | in case of no consent or optout | every 30 minutes on a rolling basis for opt-outs and on a hourly basis for deletion requests | a GPP National String is present before checking for the CCPA Privacy String as a fallback | GPP applicable sections",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "hypothesis": "H3",
  "derivation": "Apply the frozen H3 decision to product- or case-level results in data/hypothesis-results.json, including registered sensitivity tests.",
  "chapter": "abstract, 4"
 },
 {
  "headline": true,
  "review_note": "Independent adjudicator recomputed the frame or reviewed its case pairs and applied the frozen rule. Compare stage-7-rules-h458.json and the final clause.",
  "checked_independently": true,
  "id": "IDN-HYP-H4",
  "claim": "H4 remains unresolved. In the confirmed cookie-capable scored web frame, the public record did not establish a complete before-and-after comparison of the same primary guide and route. Browser announcements and code defaults alone could not establish that a majority of product guides shifted to more cookie-based syncing. The expanded bounds also span the decision threshold.",
  "final_wording": "H4 remains unresolved. In the confirmed cookie-capable scored web frame, the public record did not establish a complete before-and-after comparison of the same primary guide and route. Browser announcements and code defaults alone could not establish that a majority of product guides shifted to more cookie-based syncing. The expanded bounds also span the decision threshold.",
  "source_ids": [
   "IDN-METHOD-S06",
   "IDN-METHOD-S04",
   "IDN-E-S01",
   "IDN-E-S02",
   "IDN-E-S17",
   "IDN-E-S18",
   "IDN-E-S21",
   "IDN-E-S22",
   "IDN-E-S23",
   "IDN-E-S24",
   "IDN-E-S25",
   "IDN-E-S26"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S06",
    "passage": "H4",
    "locator": "H4: verdict, cases, eligible frame, unknowns and sensitivity. See verifying originals linked in the individual case records."
   },
   {
    "source_id": "IDN-METHOD-S04",
    "passage": "For",
    "locator": "H4, literal rule_unresolved and population"
   },
   {
    "source_id": "IDN-E-S01",
    "passage": "maintain our current approach to offering users third-party cookie choice in Chrome",
    "locator": "April 22 post, paragraph beginning “Taking all of these factors”"
   },
   {
    "source_id": "IDN-E-S02",
    "passage": "We will follow Chrome and Android processes for phasing out these technologies",
    "locator": "October 17 post, paragraphs beginning “CHIPS”, “After evaluating” and “We will follow”"
   },
   {
    "source_id": "IDN-E-S17",
    "passage": "While third-party cookies are still in use, ID5 can synchronize with ad tech vendors",
    "locator": "Initiate Cookie Sync to ID5 / Process Overview"
   },
   {
    "source_id": "IDN-E-S18",
    "passage": "You enable this by implementing a cookie sync with us through the use of a pixel.",
    "locator": "RampID Mapping Files / cookie file and site traffic"
   },
   {
    "source_id": "IDN-E-S21",
    "passage": "A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified",
    "locator": "README / Configuration table / maxCascades"
   },
   {
    "source_id": "IDN-E-S22",
    "passage": "A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified",
    "locator": "README / Configuration table / maxCascades"
   },
   {
    "source_id": "IDN-E-S23",
    "passage": "A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified",
    "locator": "README / Configuration table / maxCascades"
   },
   {
    "source_id": "IDN-E-S24",
    "passage": "To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage.",
    "locator": "Client-side JavaScript guide / step checking token generation"
   },
   {
    "source_id": "IDN-E-S25",
    "passage": "To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage.",
    "locator": "Client-side JavaScript guide / step checking token generation"
   },
   {
    "source_id": "IDN-E-S26",
    "passage": "To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage.",
    "locator": "Client-side JavaScript guide / step checking token generation"
   }
  ],
  "passage": "[IDN-METHOD-S06 | Evgeny Popov / No Fluff Advisory | H4: verdict, cases, eligible frame, unknowns and sensitivity. See verifying originals linked in the individual case records.] H4\n[IDN-METHOD-S04 | Evgeny Popov / No Fluff Advisory | H4, literal rule_unresolved and population] For\n[IDN-E-S01 | Google | April 22 post, paragraph beginning “Taking all of these factors”] maintain our current approach to offering users third-party cookie choice in Chrome\n[IDN-E-S02 | Google | October 17 post, paragraphs beginning “CHIPS”, “After evaluating” and “We will follow”] We will follow Chrome and Android processes for phasing out these technologies\n[IDN-E-S17 | ID5 | Initiate Cookie Sync to ID5 / Process Overview] While third-party cookies are still in use, ID5 can synchronize with ad tech vendors\n[IDN-E-S18 | LiveRamp | RampID Mapping Files / cookie file and site traffic] You enable this by implementing a cookie sync with us through the use of a pixel.\n[IDN-E-S21 | ID5 | README / Configuration table / maxCascades] A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified\n[IDN-E-S22 | ID5 | README / Configuration table / maxCascades] A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified\n[IDN-E-S23 | ID5 | README / Configuration table / maxCascades] A value of `-1` will disable cookie syncing altogether. Defaults to `8` if not specified\n[IDN-E-S24 | Unified ID 2.0 documentation | Client-side JavaScript guide / step checking token generation] To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage.\n[IDN-E-S25 | Unified ID 2.0 documentation | Client-side JavaScript guide / step checking token generation] To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage.\n[IDN-E-S26 | Unified ID 2.0 documentation | Client-side JavaScript guide / step checking token generation] To check that the token was successfully generated, use the browser's developer tools to look for the token in local storage.",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "hypothesis": "H4",
  "derivation": "Apply the frozen H4 decision to product- or case-level results in data/hypothesis-results.json, including registered sensitivity tests.",
  "chapter": "abstract, 5"
 },
 {
  "headline": true,
  "review_note": "Post-handoff scope and source review. The signed-off H5 decision rule and primary outcome are preserved.",
  "checked_independently": true,
  "id": "IDN-HYP-H5",
  "claim": "Only Blockgraph met the US buying test for a CTV household-resolution service. Its public guides document IP as an input and give no elapsed-time rule for refreshing or expiring the live link. The registered majority claim was contradicted in that one-product frame (0 of 1). Eight other candidates had uncertain eligibility. Counting all eight as in scope gives a range of 0 of 9 to 8 of 9, which leaves the broader market result unresolved. LtvAdx documents a 30-day device-link rule and paid US household targeting. The records reviewed did not establish a separate US purchase of household resolution.",
  "final_wording": "Only Blockgraph met the US buying test for a CTV household-resolution service. Its public guides document IP as an input and give no elapsed-time rule for refreshing or expiring the live link. The registered majority claim was contradicted in that one-product frame (0 of 1). Eight other candidates had uncertain eligibility. Counting all eight as in scope gives a range of 0 of 9 to 8 of 9, which leaves the broader market result unresolved. LtvAdx documents a 30-day device-link rule and paid US household targeting. The records reviewed did not establish a separate US purchase of household resolution.",
  "source_ids": [
   "IDN-METHOD-S06",
   "IDN-METHOD-S04",
   "IDN-CTV-S11",
   "IDN-CTV-S16",
   "IDN-CTV-S12",
   "IDN-G-S13",
   "IDN-G-S14",
   "IDN-GV-S01",
   "IDN-GV-S02",
   "IDN-GV-S03"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S06",
    "passage": "No numerical maximum for the current edge found",
    "locator": "H5 evidence: records, Blockgraph IDN-P025 edge_clock and LtvAdx IDN-P045 eligibility; primary_min, primary_max, expanded_min, expanded_max."
   },
   {
    "source_id": "IDN-METHOD-S04",
    "passage": "More than half of US CTV household-graph products",
    "locator": "H5 statement, population and registered rule_contradicted."
   },
   {
    "source_id": "IDN-CTV-S11",
    "passage": "Household ID and Address (i.e., Postal Address) are mandatory fields.",
    "locator": "How it works, mandatory fields immediately below Supported Data Types"
   },
   {
    "source_id": "IDN-CTV-S16",
    "passage": "within the past 30, 60, or 90 days, depending on the configured history retention period",
    "locator": "ID Resolution, Other Info, final paragraph on row-based timestamps"
   },
   {
    "source_id": "IDN-CTV-S12",
    "passage": "replaces the entire identity layer",
    "locator": "Manual Identity Upload, Refresh of Identity Data"
   },
   {
    "source_id": "IDN-G-S13",
    "passage": "two devices are joined to one household only through a shared device id or IP",
    "locator": "Identity API: matching order, text following the priority table"
   },
   {
    "source_id": "IDN-G-S14",
    "passage": "30 days after the device was last seen.",
    "locator": "What is kept, and for how long: A device linked to a household"
   },
   {
    "source_id": "IDN-GV-S01",
    "passage": "Reach US households on the big screen",
    "locator": "For Advertisers, US market offer"
   },
   {
    "source_id": "IDN-GV-S02",
    "passage": "HouseholdID & ACR segment targeting",
    "locator": "Advertiser plan, included capabilities"
   },
   {
    "source_id": "IDN-GV-S03",
    "passage": "Buyer-facing segment IDs, not raw graphs",
    "locator": "How it works on your stack, Stage 01"
   }
  ],
  "passage": "[IDN-METHOD-S06, H5 evidence: records, Blockgraph IDN-P025 edge_clock and LtvAdx IDN-P045 eligibility; primary_min, primary_max, expanded_min, expanded_max.] No numerical maximum for the current edge found | [IDN-METHOD-S04, H5 statement, population and registered rule_contradicted.] More than half of US CTV household-graph products | [IDN-CTV-S11, How it works, mandatory fields immediately below Supported Data Types] Household ID and Address (i.e., Postal Address) are mandatory fields. | [IDN-CTV-S16, ID Resolution, Other Info, final paragraph on row-based timestamps] within the past 30, 60, or 90 days, depending on the configured history retention period | [IDN-CTV-S12, Manual Identity Upload, Refresh of Identity Data] replaces the entire identity layer | [IDN-G-S13, Identity API: matching order, text following the priority table] two devices are joined to one household only through a shared device id or IP | [IDN-G-S14, What is kept, and for how long: A device linked to a household] 30 days after the device was last seen. | [IDN-GV-S01, For Advertisers, US market offer] Reach US households on the big screen | [IDN-GV-S02, Advertiser plan, included capabilities] HouseholdID & ACR segment targeting | [IDN-GV-S03, How it works on your stack, Stage 01] Buyer-facing segment IDs, not raw graphs",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Single confirmed case. Eligibility uncertainty precludes a majority conclusion for the US market. The documented device-link timing is distinct from the 90-day household-profile timer.",
  "hypothesis": "H5",
  "derivation": "Apply the frozen H5 decision to product- or case-level results in data/hypothesis-results.json, including registered sensitivity tests.",
  "chapter": "abstract, 7"
 },
 {
  "headline": true,
  "review_note": "Independent adjudicator recomputed the frame or reviewed its case pairs and applied the frozen rule. Compare stage-7-rules-h67.json and the final clause.",
  "checked_independently": true,
  "id": "IDN-HYP-H6",
  "claim": "The reviewed enforcement records establish duties and some operational changes. For the identity products in scope, the search could not tie an operative order to a separately corroborated change in the named service. H6 remains unresolved.",
  "final_wording": "The reviewed enforcement records establish duties and some operational changes. For the identity products in scope, the search could not tie an operative order to a separately corroborated change in the named service. H6 remains unresolved.",
  "source_ids": [
   "IDN-METHOD-S06",
   "IDN-METHOD-S04",
   "IDN-H-S03",
   "IDN-H-S06",
   "IDN-H-S08",
   "IDN-H-S15"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S06",
    "passage": "H6",
    "locator": "H6: verdict, cases, eligible frame, unknowns and sensitivity. See verifying originals linked in the individual case records."
   },
   {
    "source_id": "IDN-METHOD-S04",
    "passage": "Since",
    "locator": "H6, literal rule_unresolved and population"
   },
   {
    "source_id": "IDN-H-S03",
    "passage": "implementing an audit program to scan the compliance of its partners since 2020",
    "locator": "Findings, Article 7(1) paragraph"
   },
   {
    "source_id": "IDN-H-S06",
    "passage": "have complied with its obligations under the substituted enforcement notice by 24 July 2025.",
    "locator": "Use of personal data for direct marketing, fifth sentence; read immediately after “Experian Limited will”"
   },
   {
    "source_id": "IDN-H-S08",
    "passage": "provide a simple, easily located means for consumers to withdraw consent",
    "locator": "Provision VIII, withdrawing consent, pp. 18–19; signature p. 30"
   },
   {
    "source_id": "IDN-H-S15",
    "passage": "cookies intended for advertising purposes will necessarily be deposited when creating a Google account.",
    "locator": "Decision paragraph 269 and operative injunction, advertising-cookie limb"
   }
  ],
  "passage": "H6 | Since | implementing an audit program to scan the compliance of its partners since 2020 | have complied with its obligations under the substituted enforcement notice by 24 July 2025. | provide a simple, easily located means for consumers to withdraw consent | cookies intended for advertising purposes will necessarily be deposited when creating a Google account.",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "hypothesis": "H6",
  "derivation": "Apply the frozen H6 decision to product- or case-level results in data/hypothesis-results.json, including registered sensitivity tests.",
  "chapter": "abstract, 9"
 },
 {
  "headline": true,
  "review_note": "Checked the pinned publisher client, router destination, conditional membership lookup and explicit author-interest disclosure.",
  "checked_independently": true,
  "id": "IDN-HYP-H7",
  "claim": "The AdCP Go publisher client sends a typed ID token to the Trusted Match router. With an audience service, a token and a target segment, the reference engine can check audience membership. This implementation contradicts the registered schema-only claim. The reviewed records did not establish a paid purchase that used this ID path. The author co-leads the Signals & Measurement working group at AgenticAdvertising.org.",
  "final_wording": "The AdCP Go publisher client sends a typed ID token to the Trusted Match router. With an audience service, a token and a target segment, the reference engine can check audience membership. This implementation contradicts the registered schema-only claim. The reviewed records did not establish a paid purchase that used this ID path. The author co-leads the Signals & Measurement working group at AgenticAdvertising.org.",
  "source_ids": [
   "IDN-METHOD-S06",
   "IDN-METHOD-S04",
   "IDN-J-S03",
   "IDN-J-S05",
   "IDN-J-S04",
   "IDN-J-S16",
   "IDN-METHOD-S01"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S06",
    "passage": "H7",
    "locator": "H7: verdict, cases, eligible frame, unknowns and sensitivity. See verifying originals linked in the individual case records."
   },
   {
    "source_id": "IDN-METHOD-S04",
    "passage": "In",
    "locator": "H7, literal rule_contradicted and population"
   },
   {
    "source_id": "IDN-J-S03",
    "passage": "{UserToken: params.UserToken, UIDType: params.UIDType},",
    "locator": "tmpclient/client.go, Activate, lines 126–133"
   },
   {
    "source_id": "IDN-J-S05",
    "passage": "results, err := e.audience.IsMemberBatch(ctx, lookups)",
    "locator": "targeting/identity_engine.go, resolveUserSegments, lines 131–144"
   },
   {
    "source_id": "IDN-J-S04",
    "passage": "result = h.service.Evaluate(ctx, serviceReq)",
    "locator": "targeting/identityagent/handler.go, ServeHTTP, lines 223–229"
   },
   {
    "source_id": "IDN-J-S16",
    "passage": "Agentic Audiences can add value in the existing programmatic ecosystem",
    "locator": "Operationalizing Agentic Audiences, OpenRTB extension discussion"
   },
   {
    "source_id": "IDN-METHOD-S01",
    "passage": "Signals & Measurement working group",
    "locator": "Biography, introduction and career history; dates and disclosures supplemented by author’s signed-off project brief."
   }
  ],
  "passage": "[IDN-METHOD-S06, H7: verdict, cases, eligible frame, unknowns and sensitivity. See verifying originals linked in the individual case records.] H7 | [IDN-METHOD-S04, H7, literal rule_contradicted and population] In | [IDN-J-S03, tmpclient/client.go, Activate, lines 126–133] {UserToken: params.UserToken, UIDType: params.UIDType}, | [IDN-J-S05, targeting/identity_engine.go, resolveUserSegments, lines 131–144] results, err := e.audience.IsMemberBatch(ctx, lookups) | [IDN-J-S04, targeting/identityagent/handler.go, ServeHTTP, lines 223–229] result = h.service.Evaluate(ctx, serviceReq) | [IDN-J-S16, Operationalizing Agentic Audiences, OpenRTB extension discussion] Agentic Audiences can add value in the existing programmatic ecosystem | [IDN-METHOD-S01, Biography, introduction and career history; dates and disclosures supplemented by author’s signed-off project brief.] Signals & Measurement working group",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "hypothesis": "H7",
  "derivation": "Apply the frozen H7 decision to product- or case-level results in data/hypothesis-results.json, including registered sensitivity tests.",
  "chapter": "abstract, 10"
 },
 {
  "headline": true,
  "review_note": "Independent adjudicator recomputed the frame or reviewed its case pairs and applied the frozen rule. Compare stage-7-rules-h458.json and the final clause.",
  "checked_independently": true,
  "id": "IDN-HYP-H8",
  "claim": "H8 remains unresolved. Five confirmed change cases lacked decisive evidence that the named service continued, or replaced, a specific predecessor’s graph links. Ownership, continuity of a key, common household data and migration of software did not settle reuse. The primary and expanded ranges cross the registered threshold.",
  "final_wording": "H8 remains unresolved. Five confirmed change cases lacked decisive evidence that the named service continued, or replaced, a specific predecessor’s graph links. Ownership, continuity of a key, common household data and migration of software did not settle reuse. The primary and expanded ranges cross the registered threshold.",
  "source_ids": [
   "IDN-METHOD-S06",
   "IDN-METHOD-S04",
   "IDN-YAH-S01",
   "IDN-D-S05",
   "IDN-D-S06",
   "IDN-D-S08",
   "IDN-D-S10"
  ],
  "support": [
   {
    "source_id": "IDN-METHOD-S06",
    "passage": "H8",
    "locator": "H8: verdict, cases, eligible frame, unknowns and sensitivity. See verifying originals linked in the individual case records."
   },
   {
    "source_id": "IDN-METHOD-S04",
    "passage": "More",
    "locator": "H8, literal rule_unresolved and population"
   },
   {
    "source_id": "IDN-YAH-S01",
    "passage": "Yahoo Ad Tech LLC",
    "locator": "Opening paragraph, legal name and principal place of business, 770 Broadway, New York, NY 10003"
   },
   {
    "source_id": "IDN-D-S05",
    "passage": "entered into an agreement to acquire Lotame",
    "locator": "opening paragraph"
   },
   {
    "source_id": "IDN-D-S06",
    "passage": "in April 2025, 100% of Lotame Solutions, Inc.",
    "locator": "Note 3.1, Acquisitions in financial year 2025, first bullet"
   },
   {
    "source_id": "IDN-D-S08",
    "passage": "enrich their first-party data with RampID and Epsilon’s Identity",
    "locator": "section 1, Immediate Scale & Activation"
   },
   {
    "source_id": "IDN-D-S10",
    "passage": "acquired TrueData’s third-party audience business, along with the TrueData brand",
    "locator": "opening paragraph"
   }
  ],
  "passage": "[IDN-METHOD-S06 | Evgeny Popov / No Fluff Advisory | H8: verdict, cases, eligible frame, unknowns and sensitivity. See verifying originals linked in the individual case records.] H8\n[IDN-METHOD-S04 | Evgeny Popov / No Fluff Advisory | H8, literal rule_unresolved and population] More\n[IDN-YAH-S01 | Yahoo Ad Tech LLC | Opening paragraph, legal name and principal place of business, 770 Broadway, New York, NY 10003] Yahoo Ad Tech LLC\n[IDN-D-S05 | Publicis Groupe | opening paragraph] entered into an agreement to acquire Lotame\n[IDN-D-S06 | Publicis Groupe | Note 3.1, Acquisitions in financial year 2025, first bullet] in April 2025, 100% of Lotame Solutions, Inc.\n[IDN-D-S08 | Publicis Groupe | section 1, Immediate Scale & Activation] enrich their first-party data with RampID and Epsilon’s Identity\n[IDN-D-S10 | ID5 | opening paragraph] acquired TrueData’s third-party audience business, along with the TrueData brand",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Public record through 2026-11-11",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "paper synthesis",
  "confidence": "medium",
  "confidence_reason": "Reread in context of the defined buying task and registered test.",
  "limitations": "Study-population finding subject to its reported scope and unknowns.",
  "hypothesis": "H8",
  "derivation": "Apply the frozen H8 decision to product- or case-level results in data/hypothesis-results.json, including registered sensitivity tests.",
  "chapter": "abstract"
 },
 {
  "headline": false,
  "review_note": "Researchers recovered the alternate publisher copy. A separate reader opened it, located the deciding paragraph and verified against an independent HTTP fetch. Qualification retained.",
  "checked_independently": true,
  "id": "IDN-SW-F01",
  "claim": "33Across says participating DSPs resolve nearly 90% of one publisher’s traffic to their own IDs. The case does not specify its country, eligible counting unit, acceptance rule or observation period. This is a separate case from the MediaWallah release and does not meet H1.",
  "final_wording": "33Across says participating DSPs resolve nearly 90% of one publisher’s traffic to their own IDs. The case does not specify its country, eligible counting unit, acceptance rule or observation period. This is a separate case from the MediaWallah release and does not meet H1.",
  "source_ids": [
   "IDN-SW-S01"
  ],
  "support": [
   {
    "source_id": "IDN-SW-S01",
    "passage": "nearly 90% of a publisher’s traffic",
    "locator": "Solution section, line 63; Results section, line 65"
   }
  ],
  "passage": "nearly 90% of a publisher’s traffic",
  "evidence_class": "vendor_assertion",
  "scope_geo": "Case or route only; territory unresolved.",
  "scope_time": "At the date of the source, available by the cutoff.",
  "claim_status": "actual",
  "figure_kind": "none",
  "confidence": "medium",
  "confidence_reason": "Identical issuer-hosted publication read via indexed page and direct HTTP body.",
  "limitations": "Seller account; no independent validation.",
  "review_outcome": "supported_with_qualification",
  "hypothesis": "H1",
  "stream": "final source recovery",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Researchers recovered the alternate publisher copy. A separate reader opened it, located the deciding paragraph and verified against an independent HTTP fetch. Qualification retained.",
  "checked_independently": true,
  "id": "IDN-SW-F02",
  "claim": "A June 2021 interview republished by 33Across described the Pub Token as probabilistic and limited its use at that time to the 33Across exchange. The account does not establish technical continuity with current graph links.",
  "final_wording": "A June 2021 interview republished by 33Across described the Pub Token as probabilistic and limited its use at that time to the 33Across exchange. The account does not establish technical continuity with current graph links.",
  "source_ids": [
   "IDN-SW-S02"
  ],
  "support": [
   {
    "source_id": "IDN-SW-S02",
    "passage": "only work within the company’s ad exchange",
    "locator": "June 2 2021 repost, lines 67–68 in current index"
   }
  ],
  "passage": "only work within the company’s ad exchange",
  "evidence_class": "vendor_assertion",
  "scope_geo": "Case or route only; territory unresolved.",
  "scope_time": "At the date of the source, available by the cutoff.",
  "claim_status": "actual",
  "figure_kind": "none",
  "confidence": "medium",
  "confidence_reason": "Identical issuer-hosted publication read via indexed page and direct HTTP body.",
  "limitations": "Seller account; no independent validation.",
  "review_outcome": "supported_with_qualification",
  "hypothesis": "H8",
  "stream": "final source recovery",
  "chapter": ""
 },
 {
  "headline": false,
  "review_note": "Process declaration added and checked in the post-handoff editorial review. The historical seven-stage sweep predates it.",
  "checked_independently": false,
  "id": "IDN-PROC-F01",
  "claim": "OpenAI models carried out registration, research, verification, profiling, scoring, drafting and the final source check. The second pass used other model runs within the same process. No independent human peer review or second human scoring exercise is documented. The plan ran through the end of the New York calendar day. The original sweep closed at 8:37 a.m. EST on November 11, 2026. A later Claude Code session sampled 36 claims: 28 supported as written, two slightly overstated, one partly supported and five whose sources that reviewer could not open.",
  "final_wording": "OpenAI models carried out registration, research, verification, profiling, scoring, drafting and the final source check. The second pass used other model runs within the same process. No independent human peer review or second human scoring exercise is documented. The plan ran through the end of the New York calendar day. The original sweep closed at 8:37 a.m. EST on November 11, 2026. A later Claude Code session sampled 36 claims: 28 supported as written, two slightly overstated, one partly supported and five whose sources that reviewer could not open.",
  "source_ids": [
   "IDN-PROC-S01"
  ],
  "support": [
   {
    "source_id": "IDN-PROC-S01",
    "passage": "OpenAI models ran the seven research stages.",
    "locator": "research_process and stages"
   },
   {
    "source_id": "IDN-PROC-S01",
    "passage": "A separate Claude Code session spot-checked 36 claims after the handoff.",
    "locator": "post_handoff_review, sample and four dispositions"
   },
   {
    "source_id": "IDN-PROC-S01",
    "passage": "The source sweep closed at 8:37 a.m. EST on November 11, 2026.",
    "locator": "cutoff_deviation and observed_snapshot; registered plan in RESEARCH-BRIEF.md and observed close in checks/stage-7.md"
   }
  ],
  "passage": "[IDN-PROC-S01, research_process and stages] OpenAI models ran the seven research stages. | [IDN-PROC-S01, post_handoff_review, sample and four dispositions] A separate Claude Code session spot-checked 36 claims after the handoff. | [IDN-PROC-S01, cutoff_deviation and observed_snapshot; registered plan in RESEARCH-BRIEF.md and observed close in checks/stage-7.md] The source sweep closed at 8:37 a.m. EST on November 11, 2026.",
  "evidence_class": "synthesis",
  "review_outcome": "supported_as_stated",
  "scope_geo": "US purchasing frame; other jurisdictions only where named.",
  "scope_time": "Morning of 2026-11-11; the editorial sample followed the handoff.",
  "claim_status": "actual",
  "figure_kind": "none",
  "stream": "post-handoff editorial disclosure",
  "confidence": "high",
  "confidence_reason": "Contemporaneous run records and the dated quality review agree.",
  "limitations": "This record documents roles and scope only. It supplies no independent product evidence.",
  "chapter": "abstract, 13"
 }
]