Banner library: saving and reusing banners
- Written for
- + Written for
- Deprecated
- + Deprecated
- Applies to
- + Applies to
Banner library: saving and reusing banners
If you manage more than one property in Cookie Munch, you shouldn't have to rebuild the same banner from scratch on every domain. The banner library is where your reusable banner designs live at the organization level — design a banner once, assign it to as many properties as you like, and publish an update to all of them in a single click.
You don't navigate to a separate "library" page for this — it lives right at the top of Banner Studio, in the sub-bar just below the toolbar.
Designs vs. properties
It helps to keep two things distinct:
A design is a saved banner — its theme, categories, and full screen flow — identified by a name you choose, independent of any single domain.
A property (a site or app you've connected) can have zero or one design assigned to it at a time.
If a property has no design assigned, Banner Studio doesn't leave you with nothing — it falls back to that property's own previously stored configuration, or the polished default banner if it's brand new.
Switching between saved designs
At the top of Studio, the banner switcher dropdown lists every design saved in your organization. Steps:
Click the dropdown — you'll see every saved design by name.
Select one to load it straight into the editor, replacing whatever was on the canvas.
Keep editing as usual; nothing is sent to your live site until you publish.
Creating a new design
Open the banner switcher and choose ➕ New banner at the bottom of the list.
In the dialog that appears, type a name for the design (something that describes its purpose, e.g. "EU opt-in" or "Marketing sites bar").
Click Create.
The new design starts from the default template and saves immediately — there's no separate "save" step to remember. If the property you were viewing when you created it had no design assigned yet, the new design is automatically assigned to that property, so it's remembered the next time you open Studio.
Renaming a design
Click the rename icon next to the banner switcher, edit the name inline, and press Enter (or click away) to commit. The name updates immediately — again, no extra save step.
Assigning a design to properties
This is the step that turns one design into "many sites, one banner":
With a design loaded, click Active on these sites (n) in the sub-bar. A popover opens listing every property in your organization as a checkbox.
Check a property to assign the current design to it; uncheck it to remove the assignment.
Each toggle writes straight to the server the moment you click it — there's no "save assignments" button, and if a request fails the checkbox reverts on its own so you always see an accurate state. A single design can be assigned to any number of properties at once; that's the whole point of the library.
Publishing to everywhere it's assigned
Click Publish in the Studio toolbar and it goes live on every property the currently loaded design is assigned to, in one action. There's no separate publish step per property — assignment is what determines how wide a publish reaches.
One nuance worth remembering: reassigning a design to a new property doesn't retroactively publish your last draft to it. If you add a property to an already-published design, click Publish again so that property picks up the current, live version of the banner.
When to use one shared design vs. several
One shared design is the right call for a fleet of similar sites — same brand, same legal posture. You get consistency, and a copy or category fix only has to happen once.
Separate designs make sense when properties need genuinely different flows — for example, an EU-facing opt-in banner (built from the GDPR Opt-In template) for one property, and a US "Do Not Sell" modal (built from the CCPA template) for another.
Tips
Name designs by their purpose, not by a single site — it keeps the switcher readable once you have more than a couple of properties in play.
Use Active on these sites as your audit trail: before making a wide-reaching change to a shared design, check the list so you know exactly which domains will change the moment you hit Publish.
Pair the library with templates — clone a template into a new design, tailor it, and it's immediately reusable across every property that needs that same posture.