Deploying Changes
Push your configuration changes to production. In Anima, configuration edits don't go live on their own — they stage until you create and deploy a release.
When to deploy
Deploy after making changes to:
- Ad slots (new, edited, deleted)
- Layouts (targeting, slots)
- Demand partners (enabled, configured)
- Global settings
All configuration edits — ad slots, layouts, demand seats, wrapper settings — stage until you deploy a release. There are no changes that apply to your live site automatically on save.
How to deploy
Step 1: Review your staged changes
Before releasing, confirm what's changed. Your unshipped edits accumulate in the current draft config — open Wrapper → Configs to review them, so you know exactly what the next release will include.
Step 2: Create release
- Click Create Release
- Add Release Notes (recommended):
- What changed
- Why it changed
- Any expected impact
Example notes:
Added new in-content slot to article layout.
Increased floor price to $1.25 for sidebar slots.
Step 3: Deploy
- Click Deploy
- Wait for the deploy to complete — config-only changes propagate through the CDN in seconds; a change that rebuilds the wrapper library takes a few minutes
- Confirmation appears when live
Using the AI Assistant
In Operator mode, the assistant can help you stage changes into a release — for example:
- "Draft a release with my pending changes"
It proposes the change and asks for your approval first. You still deploy the release here in the release flow. See the AI Assistant overview for how Operator mode works.
After deploying
Verify deployment
- Clear browser cache or use incognito
- Visit your site
- Check that changes are working
- Monitor for errors in console
Monitor performance
For the first 1-2 hours:
- Watch analytics for anomalies
- Check fill rates and CPM
- Monitor page speed
Deployment timing
Best times to deploy
| Change type | Recommended timing |
|---|---|
| Minor tweaks | Anytime |
| New slots/layouts | Low traffic period |
| Floor changes | Morning (before peak) |
| Major overhaul | Weekend or low-traffic |
Avoid deploying during
- Peak traffic hours (unless urgent)
- Active experiments (may invalidate results)
- Revenue-critical events
Troubleshooting
Deployment stuck
| Check | Solution |
|---|---|
| Network issue | Refresh and retry |
| Large change | Wait a few minutes |
| System issue | Check status page |
Changes not appearing
| Cause | Solution |
|---|---|
| Caching | Clear browser/CDN cache |
| Deployment pending | Wait for completion |
| Wrong domain | Check domain selector |
Something broke
Don't panic:
- Check browser console for errors
- Compare with previous version
- Rollback if needed
Release notes best practices
Good release notes help you track changes:
Do include
- What changed
- Why it changed
- Expected impact
- Related ticket/request
Example
Release: 2024-01-15
- Added article_incontent_3 slot (ticket #123)
- Raised floors from $0.75 to $1.00 for premium slots
- Enabled lazy loading for below-fold slots
Expected: +10% page speed, neutral revenue
Common questions
How quickly do changes go live?
Usually 1-5 minutes after deployment. CDN propagation may add slight delay for some users.
Can I deploy specific changes only?
No, releases include all pending changes. If you want to deploy selectively, revert unwanted changes before deploying.
What if I deploy a mistake?
There's no one-click rollback. Copy your previous good release forward into a new release and deploy it — see Rolling back.