As more publishers evaluate their options beyond PubMatic OpenWrap, having a clear migration plan can help reduce implementation risk and minimize unnecessary disruption. Whether you’re preparing to make the switch or simply exploring alternative header bidding solutions, understanding the process upfront can help you avoid unnecessary downtime and implementation issues.
This guide walks through what a migration to MonetizeMore looks like in practice; from granting account access on day one to implementing the new setup, validating performance, and finally removing the last line of legacy code once the migration is complete.
Before diving into the details, here’s how the 10 steps break down across the three phases of a typical migration:
| Phase | What Happens | Steps |
| Setup | Adserver Access is granted, ad placements are mapped, and both ads.txt and the new script are put in place | 1–4 |
| Implementation & Testing | New code goes live on test pages alongside the old setup, and performance is verified | 5–7 |
| Cleanup | Old PubMatic code, line items, and ads.txt entries are fully removed | 8–10 |
You could choose to run both integrations in parallel during the test or entirely replace Pubmatic setup with that of MonetizeMore.
Give the MonetizeMore team “Manager” or “Administrator” access to your Google Ad Manager (GAM) account. They need this to build your new behind-the-scenes settings (line items and key-values).
Review your current website layout with your Account Manager. Make sure all your current mobile and desktop ad spots are mapped to the new setup so you don’t lose your best-performing placements.
Copy the new authorized seller lines from MonetizeMore and paste them into your live ads.txt file. Important: do not delete your PubMatic lines yet. Keeping both allows revenue to flow seamlessly during the switch and gives the MonetizeMore team time to get your sites approved by demand partners.
Log into your MonetizeMore dashboard and copy your new custom header bidding script. This can also be provided directly by your Account Manager.
Paste that script into the <head> section of your website’s code. Put it as high up as possible so the ad auction starts immediately when a page loads. This goes into the pages where you intend to test the new setup, not necessarily your entire site right away.
Replace your old PubMatic body tags with the new MonetizeMore div tags (the placeholders where ads actually show up) in your website’s content, on pages you would like to test.
Once the ad codes are in place, the Line items can be taken live and the integration can be tested to confirm bid requests and responses are flowing as intended.
Once you see MonetizeMore winning auctions and displaying ads correctly, completely delete the old PubMatic OpenWrap scripts from your website’s code.
Go into Google Ad Manager and pause/archive all your old PubMatic line items, orders, and key-values. This keeps your ad server clean and prevents old code from interfering with your new setup.
Finally, delete the old PubMatic lines from your live ads.txt file. Leave only MonetizeMore and any other active direct partners you work with.
Migrating a header bidding wrapper is a meaningful decision, so it’s worth knowing what you’re moving to. MonetizeMore is a Google Certified Publishing Partner with over a decade of ad operations experience, and its PubGuru header bidding wrapper is built to run simultaneous auctions across a wide range of demand partners without adding drag to your page load times.
A few things publishers consistently point to:
Once you have a migration plan, the next step is putting it into action. Our team at MonetizeMore works with you throughout the implementation process, helping configure your setup, validate performance, and ensure your new header bidding wrapper is ready for production.
Talk to the MonetizeMore team to get your Account Manager assigned and start Step 1 today.
Do I need to take my site offline during the migration?
No. The process is designed to run in parallel. Your existing PubMatic setup keeps serving ads while the new MonetizeMore configuration is built, tested, and verified on select pages first.
Why do I need to keep both PubMatic and MonetizeMore lines in ads.txt during the switch?
Removing your PubMatic lines too early can cut off revenue from that source before the new setup is fully approved by demand partners. Keeping both live during the transition avoids that gap.
Will I lose historical reporting data when I switch?
Your GAM historical data stays intact since you’re not changing ad servers, only the header bidding wrapper feeding into it. Your MonetizeMore Account Manager can walk you through how reporting looks going forward.
Do I need developer resources to complete the migration?
Some code implementation is required—placing the script and swapping placement tags—but MonetizeMore’s Account Management team provides the code and guidance needed, so it’s typically a lightweight lift for whoever manages your site.
Product Marketing @ MonetizeMore
10X your ad revenue with our award-winning solutions.
