Wrapper Configuration
Your wrapper configuration is the single artifact Anima builds and deploys to your site — the one script that runs the header-bidding auction on every page. Lots of settings across the portal feed into it, which is why "configuring the wrapper" spans several areas. This page is the map: what goes in, where you set it, and how a change reaches your live site.
What feeds your wrapper configuration
| Part of the config | What it controls | Where you set it |
|---|---|---|
| The tag | The inline script that loads the wrapper on your pages | Install the tag |
| Ad slots & layouts | Which slots exist, their sizes, and which load on which pages | Inventory |
| Demand partners | Which bidders compete, and their per-slot tag IDs | Demand |
| Auction timeout | How long the auction waits for bids | Timeout settings |
| Floors | Minimum bid prices, per slot | Creating an ad slot → Auction tab · Floors concept |
| Refresh | Whether and how slots refresh | Refresh concept |
| Identity modules | User-ID solutions (SharedID, ID5, UID2) | Integrations |
| Privacy & consent | GPP consent module and GPT privacy flags | Privacy |
| Supply chain (schain) | The seller nodes disclosed in bid requests | Supply Chain |
| User sync | Cookie/ID sync timing and limits | User Sync |
| Custom dimensions | Your own metadata for the auction, ad server, and reporting | Custom Dimensions |
| Core Web Vitals tracking | RUM measurement on pages with the wrapper | Enabling CWV tracking |
| Reusable config templates | A house baseline you can apply to many configs | Templates |
How changes go live
No configuration edit reaches your live site on its own. Edits accumulate in your draft config; you then bundle them into a release and deploy it:
- Make your changes across the areas above.
- Review the draft config under Wrapper → Configs.
- Create a release, then deploy it — see Deploying changes.
- To test a change on a slice of traffic first, use an experiment; to undo a deployed change, copy a previous release forward and deploy it (see Rolling back).
Verifying the live config
After deploying, confirm the wrapper is running the config you expect — append ?pbjs_debug=true to a page and check the console. See Verifying installation and Wrapper Debugging.