TCF String Decoder Guide

Use the TCF String Decoder to validate consent strings from CMPs and understand which purposes and vendors are consented.

Quick steps

  1. Paste a TCF v2 string (e.g., euconsent-v2) into the input.
  2. Click Decode to parse the string locally.
  3. Review CMP metadata, purpose consents, and vendor lists.

Best uses

  • Verify CMP configuration before launch.
  • Confirm purpose and vendor consent signals in QA.
  • Share decoded output with privacy or ops teams.

Common issues

  • Truncated strings will fail to decode.
  • Publisher-specific segments may be absent in some strings.
  • Vendor names depend on the cached GVL version.

Support