GoGo CTV is an independent CTV ad server: unified auction, pod construction, server-side insertion, sold as software. Publica is a strong CTV-first ad server with a real technical advantage most competitors cannot match. The reason to look elsewhere is rarely the product. It is who owns it, what it is bundled with, and where the roadmap is decided.
This page is about ad serving. If what you want to replace is IAS's verification and measurement (brand safety, viewability, invalid traffic), that is a different decision and we are not a candidate for it. We wrote up how verification and ad serving fit together, including what stays and what changes if you move ad servers.
Publica was acquired by Integral Ad Science (IAS) in 2021. IAS is a measurement and verification company: its core business is telling advertisers whether an impression was real, viewable and brand-safe, and its core customers are buyers.
IAS was then taken private by Novacap, a private equity firm, in a roughly $1.9bn deal announced 24 September 2025 and completed 23 December 2025. So the ad server has changed hands twice in five years, and its current owner's owner is a financial sponsor rather than an operating company.
Ownership verified September 2026 from PPC Land's 2025 video ad server survey, which describes Publica as a CTV-first ad server for unified auctions with transparent reporting, aimed at FAST channels, CTV publishers and mid-to-large AVOD services. Deal dates from IAS's own releases: the September 2025 announcement and the December 2025 completion. An announcement and a closing are not the same event, and we do not treat them as one.
This is the case where the parent company is an asset rather than a conflict, and it would be dishonest to frame it otherwise.
An ad server owned by a verification company can build brand safety and measurement into the serving path rather than bolting it on. If your advertisers demand third-party verification, and premium buyers increasingly do, having it in the same product as the ad decision is a real reduction in integration work, contracts and finger-pointing when numbers disagree.
IAS does not sell demand. It is not bidding into your auction. On the specific conflict that matters most in ad serving, the referee owning a team, Publica is cleaner than an SSP-owned ad server.
Publishers who talk to us about moving off Publica rarely complain about the decisioning. The reasons they give cluster around the parent, and they are worth separating so you can tell which ones an independent ad server actually fixes.
| What you are hearing | What it usually means | Does an independent ad server fix it? |
|---|---|---|
| "Serving and verification are one contract." | Renewals, price changes and product changes to one arrive attached to the other. You cannot renegotiate or replace either on its own. | Yes. Ad serving becomes its own contract; verification stays with whichever vendor you choose, connected through the creative and the beacon. |
| "The roadmap seems to be set by the buy side." | IAS's customers are mostly advertisers and agencies. Features that serve buyers (measurement, brand safety scoring) can be prioritised over features that serve your yield (pod construction, floors, fill). | Partly. An independent has no buy-side parent to answer to, but you should still ask any vendor, including us, who decides the roadmap and how publishers get onto it. |
| "We are not the anchor customer." | Publica's public reference points are very large: Samsung TV Plus under a renewed exclusive global partnership, Vevo, and large broadcasters. A mid-size FAST or AVOD operator is not the account the product is tuned around. | Depends on the vendor's size. A smaller independent can make you a reference account; it also has a shorter track record. Ask both of us which customers are your shape. |
| "Two ownership changes in five years." | Each change resets priorities, and a private equity owner implies a return horizon and, reasonably, another ownership event. | Only if the independent is stable itself. Ask what in the contract survives a change of control, and ask us the same question. |
| "We are paying for verification we do not use." | You already have a measurement partner, or your buyers do not require one, and native verification is a feature you fund without switching on. | Yes. You pay for ad serving as software and nothing else. |
Publica's publicly announced reference accounts are drawn from IAS's own releases: the September 2025 Samsung Ads renewal and the 2023 Vevo announcement. Contract structure varies by account; the bundling description above is the pattern publishers describe to us, not a statement about any specific contract.
"Since the Novacap transaction, who owns the Publica roadmap, and what has changed in your published plans?" A straight answer is reassuring. A vague one tells you the roadmap is being decided somewhere above the product team.
Both platforms are CTV-first, do unified auctions, server-side insertion and the standard protocol set. These are the differences that follow from how each company is built rather than from a feature backlog.
| Dimension | Publica | GoGo CTV |
|---|---|---|
| Owner | IAS, a measurement and verification vendor, itself taken private by Novacap in December 2025 | Independent |
| Owns competing demand | No. IAS does not sell demand into your auction | No |
| Native verification | Yes, and it is their principal advantage | No. We carry your verification partner's tags rather than owning one |
| Ad serving contracted separately from verification | Varies by account; ask | Always. We do not sell verification |
| Ownership changes since 2021 | Two | None |
| Commercial model | Not publicly published; ask them directly | Software licence. No percentage of media |
| Operating history | Longer, with substantial deployed scale | Shorter. We are the newer entrant |
Publica rows reflect public information as of September 2026 and are not a substitute for asking them directly. Commercial terms in this category are negotiated and rarely published, including ours. Performance figures on our product page are internally measured, not audited.
Start with a shadow test, not a migration. We mirror a slice of your live ad requests and show you fill, latency and pod construction against what Publica actually did on the same traffic. Nothing reaches a viewer.
Direct campaigns and their priorities, pod rules (competitive separation, frequency caps, category exclusions), floors, and every demand connection: which SSPs, over which protocol, with which deal IDs. This list is the scope of the migration and most of the surprises live in it.
Your verification vendor measures through tags in the creative and the impression beacon, not through the ad server that made the decision. Those tags move with the creative. If verification was bundled in your Publica contract, this is the point to separate it; see our note on verification and ad serving.
GoGo CTV decides in parallel on mirrored requests while Publica keeps serving. When fill, latency and pod fit hold on your traffic, live traffic moves in slices, one channel or one device family at a time, so a problem is small and attributable.
Run both delivery records side by side for a full billing cycle. Discrepancies between two ad servers on the same inventory tell you more about beaconing than either vendor's deck will.
If verification is why you are on Publica, say so early. We will tell you honestly whether carrying your existing verification partner's tags gets you to the same place, and if it does not, you should stay.
GoGo CTV can participate as a demand source into your existing ad server over OpenRTB or Prebid Server: incremental demand, no migration. See server-side bidding.
To Publica. GoGo CTV is an independent CTV ad server: it decides which ad plays in which slot, builds the pod and handles server-side insertion. It is not a verification or measurement product and does not replace IAS's brand safety, viewability or fraud measurement. Publishers who need third-party verification keep their verification partner and connect it to the ad server.
Yes, if verification is contracted separately from ad serving. Verification vendors measure through tags and pixels carried in the creative and the impression beacon, not through the ad server that made the decision, so an independent ad server can carry the same tags. Check whether your Publica contract bundles the two before you plan a move.
It starts with a shadow test, not a cutover. A slice of live ad requests is mirrored to GoGo CTV, which decides in parallel while Publica continues to serve. Fill, latency and pod construction are compared on identical requests, nothing reaches a viewer, and traffic moves in slices only once the numbers hold. Direct campaigns, rules and demand connections are rebuilt before the first slice moves.
Bring your demand list, pod rules and verification setup. We will tell you what moves, what stays, what a shadow test on your traffic would show, and whether you should stay where you are.