Skip to content

TCF v2.3: Unable to encode additional segments (e.g., vendorsDisclosed) when isServiceSpecific=true #83

@Lokesh-Singh-WBD

Description

@Lokesh-Singh-WBD

When encoding TCF v2.3 with isServiceSpecific=true, the GPP Java encoder only allows one additional segment to the core segments. This makes it impossible to include additional valid segments as needed in our requirements. This functionality is not documented in the GPP specification.

Expected
Support encoding additional TCF v2.3 segments (disclosedVendors) regardless of isServiceSpecific.
Actual
Only one additional segment can be added with the core segment when isServiceSpecific as true; more than one additional segments is blocked.

Code Reference
Segment restriction appears here:
https://github.com/IABTechLab/iabgpp-java/blob/master/iabgpp-encoder/src/main/java/com/iab/gpp/encoder/section/TcfEuV2.java#L106

Question
Is restricting segments under isServiceSpecific=true intentional? If not, can segment extension be enabled?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinginvestigateTo validate if still an issuereviewedFor library maintainers only. Indicates that this issue was reviewed.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions