Editing an Ad Slot
Open an existing ad slot and change its configuration. The form is the same tabbed layout as Create — Insert · Media · Auction · Targeting · History — just pre-populated with the current values.
How to edit
- In Ad Manager (main) mode, confirm the right domain is selected.
- Go to Inventory → Ad Slots.
- Click the slot row, or use the Edit action in the row's actions column.
- Make your changes across the tabs.
- Click Save.
Changes don't affect your site until you ship a release from Wrapper → Releases.
What each tab changes
| Tab | What's editable |
|---|---|
| Insert | GAM ad unit, load type, placement (anchor, window reference, element reference, div ID, minimize / dismiss) |
| Media | Format, sizes (all-devices or per-device), refresh, custom CSS |
| Auction | Floor, auction timeout, tag-ID assignments |
| Targeting | Key-value pairs |
| History | Read-only audit trail of prior changes |
The slot name is editable from the title field at the top of the form.
Common edits
Add or remove a size
- Open the slot.
- Go to Media.
- In the Sizes fieldset, edit the size list (all-devices or per-device depending on the toggle).
- Save, then ship a release.
Trade-off: more sizes widen competition but can introduce layout shift and slow the auction. Remove sizes only after reviewing performance data in Dashboard → Monetization.
Enable or adjust refresh
- Media tab → refresh fieldset.
- Set trigger, interval, and max times — separately for mobile and desktop if the device toggle is on per-device.
- Save, release.
See Refresh for trade-offs.
Change the floor
- Auction tab → Floor.
- Update value.
- Save, release.
Trade-off: higher floors lift CPM but can drop fill rate. Test at a traffic slice via Wrapper → Experiments before changing everywhere.
Update tag IDs
Tag IDs are managed on the Auction tab (via the Tag IDs table) and from the demand-seat side (Demand → Prebid → seat → Tag IDs). Changing on either side updates the same mapping.
Adjust targeting key-values
Targeting tab. Page-level or slot-level key-values that get passed into GAM alongside the auction.
When changes take effect
Staged changes don't go live until you create a release in Wrapper → Releases. Previous releases remain available for rollback. Config-only changes propagate through the CDN in seconds once released; library rebuilds (code/module changes) take longer.
Reverting
Before saving — click Cancel to discard changes.
After saving but before release — edit again and restore prior values, or discard the staged change.
After release — either edit and ship a corrective release, or roll back by copying the last known-good deployed release into a new draft and deploying the copy. See Rolling back.
The History tab records prior states; the audit log is your reference for what a field used to be.
Best practices
Do
- Make one change at a time so the impact is measurable
- Use an experiment (Wrapper → Experiments) for any change that could move revenue — floor, timeout, size additions
- Note the current release before shipping a big change, so rollback is easy
Don't
- Remove all but one size — you lose competition
- Raise floors without checking fill-rate data
- Disable lazy loading on below-fold slots without a concrete reason
Common questions
Will editing affect historical data?
No. Reports reflect the configuration at the time of each impression. Edits only change future impressions.
Can I edit multiple slots at once?
Use the AI Assistant: "Update floor price to $1.50 for all article slots" is the usual shortcut. Otherwise, edit slot-by-slot and ship one release once the set is done.
What if I break something?
Before release — discard the staged edit. After release — roll back by copying the previous known-good deployed release into a new draft and deploying the copy. See Rolling back.