1. Core Message

Facebook's Audience Network (AN) team is embedded inside a major publisher relationship — the Call of Duty mobile launch — and performing below potential. Two specific technical settings, a high CPM floor (~7% fill rate) and a poor caching strategy (~2.5% show rate), are throttling revenue. The team initially gave advice, was ignored, and is now returning with live data to force the conversation.

2. What the Executive Is Really Thinking

Morgan is managing two problems at once. The first is internal: his team gave good advice, the publisher only "met us halfway," and now there's a live revenue gap that proves the team was right. The second is external: a competitor, IronSource, may be "getting the last look and outbidding us" — meaning it could be winning auctions that Facebook should win. The $15k/day figure is framed not as success but as a floor. The phrase "much larger opportunity" signals that Morgan sees the gap between current and potential as the real story. Speed matters here because the game is already live and every day of underperformance is permanent lost revenue.

3. Key Management Lessons

Let Data Do the Arguing You Can't Win Alone

What it means

Morgan's team gave a recommendation upfront. The publisher partially ignored it. Now the team has real performance data — and they're using it to re-open the conversation. The document says: "Now that we have data backing up our recommendations, we are again asking them to set price targets that will inflect revenue contribution."

Why it matters

In partner relationships, early recommendations are often discounted because there's no proof yet. Data from a live deployment changes the power dynamic. You stop being a vendor with an opinion and become an advisor with evidence.

MBA Perspective

This is a classic move in Switching Costs and Platform Strategy thinking. The more a publisher optimizes their setup around your recommendations, the more embedded your platform becomes in their operations. Every setting they change on your advice is a step toward deeper lock-in.

Real-world application

A SaaS startup advising a client on configuration should document every recommendation they make and track the delta in outcomes. When results underperform because advice was ignored, return with the data — not frustration. The numbers make the next meeting easier.

Name the Competitor and Build Around Them

What it means

Morgan doesn't just say "we're underperforming." He names IronSource specifically and describes the mechanism: they may be getting a "last look," a structural auction advantage that lets them see competing bids and respond. This is precise competitive intelligence, not vague worry.

Why it matters

Vague competitive anxiety leads to vague responses. Naming the threat and the mechanism — last-look bidding — lets the team build a concrete counter-strategy: close a bidding partnership with IronSource (mentioned as already in progress) and fix the technical settings that reduce Facebook's competitiveness.

MBA Perspective

Porter's Five Forces — specifically the bargaining power of rivals in a real-time auction market — is exactly what's being analyzed here. IronSource's last-look advantage is a structural force that reduces Facebook's win rate regardless of bid quality.

Real-world application

Before any competitive response meeting, require the team to name the specific mechanism by which the competitor is winning — not just that they're winning. "They have better pricing" is weak. "They get to see our bid before they respond" is actionable.

Technical Settings Are Strategy

What it means

The two performance problems Morgan identifies are both technical: CPM floor targets set too high, and a caching strategy that requests ads from all networks simultaneously regardless of priority. These aren't engineering bugs — they're configuration choices the publisher made, and they directly determine who wins.

Why it matters

In ad tech and platform businesses generally, the person who sets the defaults wins. A 7% fill rate isn't a market failure — it's a number someone typed into a settings field. Changing that number changes the business outcome.

MBA Perspective

Platform Strategy: platforms that control configuration defaults gain structural revenue advantages. The publisher's arbitrary CPM targets are acting as an unintentional barrier that benefits networks willing to pay whatever it takes — not necessarily the best long-term partner.

Real-world application

If you sell software or run a platform, audit what your customers' default settings actually are. A misconfigured integration is an invisible revenue leak — for both sides. Proactive configuration reviews are a growth lever, not just a support task.

Cross-Functional War Rooms Work — If You Staff Them Right

What it means

Morgan describes a "Strike Force workplace chat" that includes PSM/Tech Ops, Partner Engineering, and a business development contact (John Wren) working to close a bidding partnership. This is a purpose-built, cross-functional response team for a single priority account.

Why it matters

Most partner problems stall because they require coordination across teams that don't normally talk. By putting everyone in one channel with one named mission, Morgan removes that friction.

MBA Perspective

This is Resource-Based View in practice: assembling a bundle of capabilities — technical ops, engineering, BD — that no single team has alone, and deploying them against a specific opportunity.

Real-world application

When a high-value customer or partner relationship is underperforming, create a named, time-boxed task force with one person accountable for the outcome. Don't route it through normal account management queues.

Acknowledge What You Couldn't Control

What it means

Morgan is direct that his team gave advice and the publisher "only met us halfway on most of the changes." He doesn't obscure this or spin it. He also credits Heath Schindler by name for relationship-building.

Why it matters

Internal communications that acknowledge partial failures are more credible than those that don't. Sean Ryan (the recipient) can evaluate the situation accurately. Credibility in internal reporting is a compounding asset.

MBA Perspective

No named framework fits perfectly here, but this connects to Resource-Based View: a team's credibility and track record are genuine strategic resources. Burning them with spin is expensive.

Real-world application

In your next internal update on a struggling initiative, lead with what you advised, what was accepted, and what wasn't — before the results. It signals analytical honesty and protects your credibility when outcomes are mixed.

4. Strategic Analysis (MBA Style)

Competitive Strategy

Facebook AN is competing in a real-time ad auction where structural advantages — like last-look bidding — can override pure price competition. The strategy here is two-pronged: fix the publisher's technical setup to increase Facebook's fill and show rates, and simultaneously close a bidding partnership with IronSource to neutralize their structural edge. Morgan is addressing both the symptom (low fill rate) and the cause (IronSource's auction position).

Risk Analysis

The immediate risk is that IronSource deepens its relationship with Activision while Facebook AN is still optimizing basic settings. A game launch is a narrow window — early monetization partners get data advantages, relationship equity, and potentially preferred status in future integrations. Every week of underperformance is also a week of data that IronSource is accumulating and Facebook is not.

Build vs Buy Analysis

The document doesn't describe an acquisition. The relevant build vs. buy question here is about bidding infrastructure: rather than building a first-party last-look capability, Facebook appears to be pursuing a partnership with IronSource to level the playing field. Context on whether this is a mediation partnership or something else is unclear from the document alone.

Market Dynamics

The mobile ad market for a game of Call of Duty's scale is a high-stakes, competitive auction environment where technical configuration — not just bid price — determines who wins. Multiple networks bid simultaneously. Caching strategies, CPM floors, and auction timing all affect outcomes. This is a market where product and engineering decisions are inseparable from commercial outcomes.

Long-Term Strategic Implications

If Facebook AN successfully optimizes this account and closes the IronSource partnership, it likely strengthens its position as a preferred mobile ad network for major game publishers. Mobile gaming is a large and growing ad inventory category. Losing this account — or underperforming in it — signals to other publishers that Facebook AN is not the default choice for premium game launches.

5. Hidden Insights

• The caching strategy detail is a tell. Morgan describes IronSource requesting "ads from all networks at the same time regardless of priority level." This means the publisher's setup is not giving Facebook preferential treatment even if Facebook is supposed to be a priority partner. Fixing this isn't just a technical optimization — it's a power negotiation about auction sequencing.
• The iOS/Android gap (2x revenue difference) is unresolved. Morgan flags it but says only "working on understanding and unblocking Android." This is an open risk. If Android is structurally disadvantaged for Facebook AN on this title, the revenue ceiling is lower than the internal target assumes.
• The Strike Force framing signals internal stakes. You don't name a chat "Strike Force" for a routine account. The language signals to everyone added — including Sean Ryan — that this is a priority relationship and that performance here has visibility at a senior level. That pressure is intentional.
• Heath Schindler's name appears twice. In a short internal email, naming someone twice is a deliberate signal. Morgan is credit-flagging a team member's relationship work to a senior leader. This is internal talent visibility management, embedded in a business update.