gpp-audit-compare

To audit and compare GPP signals across multiple websites, you can run a parallel Chrome Incognito postMessage ping to retrieve CMP IDs, USNAT section data, and cookie architectures. This generates a structured cross-site comparison report detailing opt-out postures and MSPA fields.

A GPP string encodes Global Privacy Platform signals, including USNAT and MSPA opt-out fields. You can check its posture by performing a postMessage ping to collect and parse the section data, revealing the site's consent state and provider configuration.

You can detect which CMP provider a website is using by executing a Chrome Incognito postMessage ping to collect the site's GPP status and section data. The parsed signals reveal the specific CMP ID alongside the site's cookie architecture.

Yes, you can extract MSPA fields and cookie architectures for USNAT compliance checks by applying a GPP signal audit to a set of URLs. This process collects parsed section data, cookie names, and banner states for cross-site comparison.

Yes, this GPP signal audit works with multiple URLs in parallel, collecting postMessage ping responses and USNAT section data simultaneously. It applies to a set of domains to compare CMP IDs, opt-out fields, and cookie architectures efficiently.

The best way to compare cross-site privacy banner states and consent configurations is to run a parallel GPP signal audit across target URLs. This collects CMP provider data, parsed GPP strings, and cookie names into a concise cross-site comparison report.