1. Core Message

Eisar Lipkovitz wants Google's ad tech team to be "crisp" about how its ad server (DFP) and demand products (GDN, DBM) work together. The strategic prize is keeping the ad server as the "decision-maker" so Google's own demand gets "first look" at publisher inventory. He also reports recent wins and losses against AppNexus at three large publishers and asks for a clear playbook for the sales team.

2. What the Executive Is Really Thinking

Lipkovitz is thinking about control of the choke point. In ad tech, whoever runs the ad server decides which buyer sees the impression first. He wants that role locked to Google. He also segments Google's four demand sources by role — DBM as buyer-agnostic, GDN as AdX-only, AwBid as narrowly scoped, and a RMKT tag as a workaround to keep first look even when publishers use a rival exchange. The AppNexus anecdotes (Axel Springer, Orange, Fairfax) show he treats this as a hand-to-hand competitive fight where publishers are picking sides, sometimes explicitly to balance Google's power ("counter-weight to Google").

3. Key Management Lessons

Own the decision-maker, not just the inventory

What it means

In any stack with multiple players, the component that decides who gets to act first is the most valuable. Lipkovitz says it plainly: "it's strategic for us to have the AdServer being the decision-maker to ensure GDN and DBM has first look access."

Why it matters

Demand without privileged access is a commodity. Privileged access without demand is wasted. Combining both compounds the advantage.

MBA Perspective

This is Platform Strategy plus Competitive Moats. The ad server is the platform's routing layer; controlling it creates structural advantage for adjacent products.

Real-world application

A fintech building both a payments rail and a lending product should make sure the rail decides routing — so its own lending offers get shown first.

Give every product a clear job

What it means

Lipkovitz lists four demand sources and assigns each a narrow role: DBM is "supply source agnostic," GDN buys "only inventory we fully understand, i.e. AdX," AwBid is "limited to RMKT," and the RMKT tag is a workaround for first look.

Why it matters

When products overlap, sales teams freelance, customers get confused, and internal cannibalization erodes margin. Clear lanes prevent that.

MBA Perspective

Resource-Based View: each asset should have a defined strategic role that the others do not duplicate.

Real-world application

A SaaS company with a free tier, self-serve plan, and enterprise plan should write a one-page rule for which customer goes where — and enforce it.

A playbook beats heroics

What it means

Lipkovitz asks for a "clear playbook to the pub sales team" for cases where a publisher prefers a rival product.

Why it matters

Frontline teams make hundreds of small calls per week. Without a written rule, they will improvise — and lose deals like Fairfax, where "AppNexus did not take no for an answer."

MBA Perspective

This is operational discipline supporting Competitive Strategy. Strategy that does not reach the sales rep is not strategy.

Real-world application

Write a one-page "if competitor X shows up, here's our response" doc. Update it monthly with the latest wins and losses.

Track the scoreboard publisher by publisher

What it means

Lipkovitz names three specific deals — Axel Springer (lost), Orange (won), Fairfax (likely lost) — and the reason behind each.

Why it matters

Account-level after-action notes turn anecdotes into pattern recognition. The Axel Springer note — "their board decided to go with AppNexus as a counter-weight to Google" — is a strategic signal, not just a loss.

MBA Perspective

Market intelligence as a feedback loop. Each deal is a data point about how the market perceives your power.

Real-world application

After every major lost deal, log the stated reason in one sentence. Review the list quarterly to spot themes.

4. Strategic Analysis (MBA Style)

Competitive Strategy

Google is using vertical integration. By owning the ad server (DFP), the exchange (AdX), and demand products (GDN, DBM), it can prioritize its own demand at the decision point. AppNexus is fighting back by selling itself as a neutral alternative — explicitly, per the Axel Springer note, as a "counter-weight to Google."

Risk Analysis

The risk Lipkovitz sees: publishers defecting to rival ad servers, which would remove Google's first-look advantage. The RMKT tag idea — "a way to retain the need for first look access to all inventory but avoid going through a different Exchange" — is a hedge against exactly that scenario.

Build vs Buy Analysis

The document does not discuss acquisitions. Google has already built (and previously bought) the pieces it needs. The strategic question here is how to coordinate owned assets, not whether to acquire more.

Market Dynamics

The industry has a small number of integrated stacks and a contested middle layer (the ad server). Large publishers have enough power to pick sides, and some are choosing diversification on principle. AppNexus's win at Axel Springer shows that being the non-dominant player is itself a value proposition to buyers worried about concentration.

Long-Term Strategic Implications

If Google's decision-maker position holds, demand and exchange revenues compound. If publishers increasingly view Google as a power to be balanced — as the Axel Springer board apparently did — defections accelerate and the moat erodes from the publisher side, regardless of product quality. This tension between commercial dominance and customer trust is the strategic crux.

5. Hidden Insights

• Power has become a sales objection. When a publisher's board chooses a rival as a "counter-weight," the competitor's product no longer has to be better — being independent is enough.
• First look is treated as the prize. Every product role in the four-network framework is designed around preserving or routing around first-look access.
• The RMKT tag is a defensive workaround. It exists to keep Google's access advantage even when a publisher picks a rival exchange — a tell that Lipkovitz expects some losses and wants to soften them.
• Internal clarity is lacking. The need to ask for a "crisp" position and a "playbook" suggests the field team has been making inconsistent calls, which itself is a competitive vulnerability.
• AppNexus is gaining momentum. Two losses (or near-losses) versus one win in a single pre-holiday stretch, against named tier-one publishers, is enough to prompt an internal reset.