TCF v2 vs US Privacy string: don't run one framework everywhere

TCF v2 vs US Privacy string: don't run one framework everywhere
Confirmed: shops force a single CMP config global and either over-block US demand or under-comply in the EU.
— TCF v2 (Europe): granular vendor consent, required for EEA demand — missing it = bidders drop you silently.
— US Privacy / GPP: opt-out signal model, lighter, but state laws (CPRA et al.) now ride the GPP string.
— Geo-routing the CMP framework is non-optional; one-size config leaks revenue on both sides.
Impact: Serve TCF in EEA, GPP/USP stateside — a global single-string setup quietly suppresses bids. (confirmed)