Hi,
This library currently does not support TCF 2.3, which introduced a mandatory Disclosed Vendors segment. The current implementation only parses the Core String segment and ignores additional segments, making it non-compliant with TCF 2.3 requirements.
TCF 2.3 made the Disclosed Vendors segment mandatory to resolve ambiguity about whether vendors (especially those declaring only Special Purposes) were actually disclosed to users. The segment is needed to verify vendor legitimacy before allowing data processing.
Question
Is there a plan to add TCF 2.3 support to this library? This would involve:
- Parsing the mandatory Disclosed Vendors segment (second segment in TC strings)
- Exposing vendor disclosure information via the API
- Maintaining backward compatibility with TCF 2.0/2.2 strings
References
Hi,
This library currently does not support TCF 2.3, which introduced a mandatory Disclosed Vendors segment. The current implementation only parses the Core String segment and ignores additional segments, making it non-compliant with TCF 2.3 requirements.
TCF 2.3 made the Disclosed Vendors segment mandatory to resolve ambiguity about whether vendors (especially those declaring only Special Purposes) were actually disclosed to users. The segment is needed to verify vendor legitimacy before allowing data processing.
Question
Is there a plan to add TCF 2.3 support to this library? This would involve:
References