This is a followup on ticket #24464:

The storage size is now increased to 1200 characters for the consent information. unfortunatelly the google additional consent information is not stored in a compressed way and therefore results in a very long string. for most publishers both (TCF v2 string and additional consent string) are important for their monetization. Hence the feature request is to

a) further increase storage size for consent information
or
b) separate storage size rules for each part (e.g. 1000 chars for tcf tcstring and 1000 chars for google add.consent string)
or
c) compress the information that is in the google additional consent string (e.g. similar to the bit-logic in TCF)