BLOG - Passendo vs. LiveIntent: A Publisher’s Guide to Choosing an Email Monetization Platform
Let’s imagine a media group running three newsletters: a property portal, a job board, a travel guide, and gets about four million impressions a month. The ad slots are in all the emails. The audience is opted-in and engaged. So, the media group already set the inbox monetization in motion, but one question remains: who runs the machinery behind it?
That usually comes down to a single name of the chosen email monetization platform.
Today, we’re comparing two of them to reveal which one is better for your business: LiveIntent and Passendo.
LiveIntent has been turning email addresses into ad inventory for almost two decades, a network model built for the web-era internet, and hasn’t really changed how it runs.
Passendo is an innovative and refined ad server that publishers use to control and run their inventory themselves.
Both put ads in the newsletter and target real, opted-in people instead of cookie guesses. But the core difference is who runs the operation, and that one thing changes what you control, how your reader data is used, and who picks the advertiser that lands in the inbox. And, of course, how much revenue you achieve.
The Core Difference: A Network You Join Vs. An Ad Server You Run
LiveIntent is a demand network. You drop its tag in, and it fills your inventory from its own advertiser pool and identity graph. Reach, and buyers come from LiveIntent’s ecosystem; you plug in and take a share of what fills, without any control over which advertiser gets selected for which newsletter. Fast to start, because there is little you are allowed to manage, let alone curate. The terms, the demand, and who gets matched to your readers all sit on LiveIntent’s side, not yours.
Passendo is an ad server you operate yourself. Your advertisers, your direct-sold deals, your targeting rules, your first-party data, and external programmatic demand only when you choose to bring it in. More to operate, sure, but the inventory and the reader relationship stay yours end to end.
That core difference decides the rest.
A network optimizes to fill your slots from a shared pool without considering relevance or personalization.
An ad server optimizes to put you in charge of what ad runs, for whom, and at what price.
And the distinction shows up the moment something changes. When a network revises its terms, adjusts its take, or shifts which advertisers flow to your inventory, a publisher on the network adapts to it, complicating the ad operations.
A publisher running an ad server sets those terms in the first place and thinks about scaling, not reorganizing.
These are different business models, and the choice commits you to one: rent your inventory to a network, or run it yourself.
Passendo Vs. Liveintent At A Glance
The table below breaks down where that lands for a working publisher.
Category
LiveIntent
Passendo
Model
Demand network built on an identity graph, little to no changes possible
Ad server the publisher runs. You set up your own operation.
Where demand comes from
LiveIntent’s advertiser pool and exchange
Your direct-sold advertisers, plus external programmatic demand when you choose to add it
Who approves the advertiser
Network-mediated; you set brand-level controls
You select and approve every advertiser
Fill logic
Direct-sold, then house, then exchange backfill; the platform optimizes toward network demand and discourages custom floors
You define the waterfall, which advertiser sits in each tier, your floors, what backfills, so every filled slot runs on your terms
Targeting basis
LiveConnect identity graph resolves email to cross-device profiles
Your own first-party and key-value data
Personalization
People-based, graph-driven across the network
Segment, context and split delivery, set by you
Data
Email matched into a cross-publisher graph
First-party data stays inside your operation
Revenue model
Revenue share on each impression
SaaS platform fee, you keep the ad revenue you sell
Best starting point
Large general-interest list wanting instant demand
Publisher wanting control over advertisers, data and pricing
Which Platform Fits Your Newsletter Operation
Both platforms will fill your ad slots. Only one lets you decide what goes in them, and if you care who shows up in your reader’s inbox, the choice cannot be random. The real question isn’t how big your operation is, it’s how much control and how much revenue you want to build.
Like most things, the more you put in, the more you get back: a refined ad operation earns more than an automated one. Simple to say, less trivial to do.
LiveIntent fits when you are willing to hand over the decisions. You give up saying who advertises to your readers in exchange for not having to think about it, which is fine if your newsletter doesn’t call for precise personalization, but costly if it does. The tag goes in, demand arrives from LiveIntent’s pool, and revenue starts without anyone selling a thing. Your slots get filled reliably, but the ad in any given slot won’t always be closely matched to the reader. It’s the faster path, and a coarser one: reach over relevance, speed over fine control.
Passendo fits when you want to control the quality and the relevance of ads served in your newsletters. You approve every advertiser, set your own floors, and run a priority waterfall that fills direct-sold sponsorships first, preferred-partner deals next, and house ads before any slot goes empty, so premium inventory keeps its value, and nothing is wasted. Targeting runs on segments you build from your own data: engagement, topic affinity, declared interests, geography, so the ad a reader sees actually fits them. The reader relationship and the first-party data behind it never leave your operation, which is why the same audience is worth more to the advertisers you choose. It’s the more refined solution, and it asks more of you to run.
Both platforms fill up ad slots; the difference is who sets the rules for how and how well the ad fits the reader.
On a network, high fill rate comes from opening inventory to exchange demand, and the platform steers toward filling it the fastest and most convenient way, which is not always the most relevant one.
With Passendo, you decide the order, the floors, and which advertiser earns each impression, so maximizing fill never means ceding control or settling for a lower quality match.
There’s a middle path worth naming: the two models aren’t mutually exclusive. A publisher can run Passendo as the ad server and connect external programmatic demand, such as LiveIntent, among the possible sources, as a lower waterfall tier that fills what direct sales don’t. That keeps direct-sold and audience deals in the premium position while still capturing network demand on the remainder. Control where it matters, fill where it doesn’t.
The practical read: a network trades control and relevance for convenience; an ad server trades convenience for control, precision, and, over time, better revenue.
Publishers who want to scale are usually willing to invest the effort and to outgrow the network. They want the email ad server.
Moving from LiveIntent to Passendo
If you’ve read this comparison carefully, you already know which way you lean: more control, more precise personalization, more of the revenue your list can actually command. The only thing standing between that and where you are now is the switch itself, and it’s a smaller step than it looks.
Onboarding lasts 1 to 4 weeks, depending on your setup, with hands-on support to migrate your placements and get your team selling. You don’t flip a switch and go dark on network revenue while you figure it out. Most publishers keep their existing demand running as a backfill tier, build direct-sold and audience products alongside it, and then shift the balance as their own pipeline fills. The move is an addition before it’s a replacement; you grow into control rather than gambling on it.
That’s the logical next step for any publisher whose list has outgrown a hands-off setup: the audience is already yours, the data is already yours, and the revenue should be too.
Passendo is the ad server built to make that shift: purpose-built for email, designed around publisher control, and staffed by people who migrate publishers off networks for a living.
When you’re ready to run your inventory instead of renting it out, that’s when you should reach out to us.
Frequently Asked Questions
Is Passendo a LiveIntent alternative?
Yes, for publishers who want to run their own email ad operation rather than plug into a demand network. Passendo is an ad server: you manage your own advertisers, targeting, and pricing, and bring in external demand only when you choose. LiveIntent is a demand network that fills your inventory from its own advertiser pool. Both serve ads inside newsletters to opted-in readers; they differ in who runs the operation.
Does Passendo use an identity graph like LiveIntent?
No. LiveIntent’s LiveConnect resolves email addresses into cross-device profiles across its publisher network. Passendo targets on your own first-party and key-value data — engagement, topic affinity, declared interests, geography — which stays inside your operation and is never matched into a cross-publisher graph.
Who keeps the ad revenue — Passendo or LiveIntent?
With Passendo you keep the ad revenue you sell; you pay a platform fee based on email volume. LiveIntent operates on a revenue-share model, taking a share of each impression in exchange for network demand and identity resolution. The structural difference matters more as your volume grows.
Does Passendo support programmatic demand?
Yes, when you want it. Passendo is built around direct-sold and publisher-controlled campaigns, but you can connect external programmatic demand as a tier in your waterfall — so it fills after your direct deals rather than competing with them. You decide whether external demand runs at all.
Which is better for European and GDPR-focused publishers?
Publishers with strict data requirements often prefer a model where first-party data stays in-house. Because Passendo targets on your own consented data without matching it into a third-party identity graph, the data path is simpler to account for under GDPR. LiveIntent’s identity resolution can still be run compliantly, but it involves more parties in the data chain. The right answer depends on your consent setup and legal guidance.