Cross-domain consent currently transfers only the CookieScript consent cookie. When IAB TCF is enabled, the receiving domain finds no TC string / Google AC string in its localStorage and resets the imported consent, so the banner is shown again on every domain in the group — the feature effectively does not work for publishers using TCF.

IAB TCF Policies allow a group-specific scope (a pre-defined group of properties under the same organisation), so transferring the TC string within a declared domain group is compliant; the banner already discloses the group to the user.

Request: include the TC string and Google AC string in the cross-domain payload (/setCookie → /getCookie), or regenerate them on the receiving domain from the transferred consent, so that TCF banners in a group share consent the same way non-TCF banners do.