Skip to content

The transparency panel and audience switcher

A hand-picked switch is honored even before consent, unlike the audience the runtime resolves on its own — and a pin is only ever honored for this site.

The transparency panel is one persistent control a visitor can always reach, not a banner that shows up once — it's how they see that a page has been personalized, see which audience it was personalized for, and switch, reset, or opt out.

Three states, not a dismiss button

The panel is either not shown at all (nothing to be transparent about), collapsed to a small pill, or expanded to show the audience name, a switcher, a reset, and opt-out. Collapsing it is not the same as the old permanent-dismiss behavior — a visitor who collapses the panel can always reopen it from the pill. A promise of transparency a visitor can silence forever isn't really a promise.

The switcher itself is only drawn while personalization is on. A visitor who has opted out still gets the panel, still sees that personalization is off, and can turn it back on — but there is nothing to switch to while opting out is beating any pin they might set, so the audience list isn't shown.

Picking an audience from the switcher writes to the exact same cookie the runtime's own automatic resolution writes — what differs is a tag recording how the pin got there: the runtime's own resolution, or a visitor's deliberate choice. That tag is the entire reason a hand-picked switch survives an undecided consent state while an automatically-resolved pin doesn't: a deliberate choice is treated as essential, the same way opting out is, while an automatic pin needs the same consent any other stored signal does.

A pin is honored, not merely remembered

Two different checks sit either side of that cookie, and the difference matters when you are trying to work out why a switch did nothing.

At the moment of switching, an audience that doesn't exist or isn't active is refused outright: an archived or deleted audience comes back as an invalid choice rather than being written.

At every render afterwards, the stored pin is checked again — this time against the audiences that are active for the site being rendered. A pin naming an audience from a different site is not rejected when it's set; it is written, and then simply never honored, because it never appears in the list the renderer matches against. The same is true of an audience archived after the pin was written. Nothing errors and nothing is announced: the visitor falls back to ordinary signal-based resolution, exactly as if they had no pin at all. If a switch appears to have been ignored, the audience is the thing to check, not the cookie.