Mobile

Mobile Game UA: Why Your MMP Needs Revenue Signals, Not Just Installs

Mobile games optimized for installs find more installs, not paying players. Learn how server-side IAP and ad revenue signals work with your MMP.

Berkay Demirbas
2 min read
Tilted phone mockup of a mobile game revenue dashboard

Sometimes a mobile game studio fixes its MMP setup. Cost per install drops, and the UA dashboard looks great. Then day 7 ROAS doesn't move. The reason is usually simple: the ad network learned exactly what it was told to find. It was told to find installs.

Why don't install-optimized campaigns bring paying players?

In mobile games, an install is the cheapest event in the funnel. Value comes later, from in-app purchases and ad revenue together. Most installs never pay back their campaign. If the ad network only sees installs and a few in-app events, it can't tell a player who churns on day 1 from one who becomes a whale.

Where does the revenue signal live?

Much of it lives outside the game SDK. Ad revenue sits in the mediation platform. Refunds come from the stores. Web shop purchases happen outside the app. Most of it settles days after the install, and none of it reaches your MMP or the ad networks on its own.

How do server-side signals work with your MMP?

Your MMP keeps handling attribution, SKAN, and its ad network integrations. A first-party data layer next to it sends blended revenue (IAP plus ad revenue), refunds, and web shop purchases back through the MMP's server-to-server API, with a shared event ID so each event is counted once. Value-based and pLTV bidding then learns from paying players, not from installs. Because the data is first-party, you also control what leaves your infrastructure, which matters under KVKK and GDPR.

How can a studio check its signal quality?

Ask three questions:

  • Does our MMP send ad networks revenue, or only installs and level events?
  • Does that revenue include ad revenue, refunds, and web shop sales?
  • Do events arrive from the SDK and the server without a shared event ID?

If the answers are "only installs", "no", and "probably", your gap isn't attribution. It's signal quality.

To see how Hardal can improve the signals your game sends to ad networks, book a demo.


Hardal is the first-party data and agentic analytics platform. We help enterprises send accurate signals to their ad platforms and grow revenue, using server-side data from their websites, mobile apps, and AI agents.

FAQs
4 Questions

Frequently Asked Questions

Direct answers on install-optimized campaigns, where revenue signals live, and how server-side events work with an MMP.

Why don't install-optimized campaigns bring paying players?
In mobile games, an install is the cheapest event in the funnel. Value comes later, from in-app purchases and ad revenue together, and most installs never pay back their campaign. If the ad network only sees installs and a few in-app events, it can't tell a player who churns on day 1 from one who becomes a whale.
Where does the revenue signal live?
Much of it lives outside the game SDK. Ad revenue sits in the mediation platform, refunds come from the stores, and web shop purchases happen outside the app. Most of it settles days after the install, and none of it reaches your MMP or the ad networks on its own.
How do server-side signals work with your MMP?
Your MMP keeps handling attribution, SKAN, and its ad network integrations. A first-party data layer next to it sends blended revenue (IAP plus ad revenue), refunds, and web shop purchases back through the MMP's server-to-server API, with a shared event ID so each event is counted once. Value-based and pLTV bidding then learns from paying players, not from installs. Because the data is first-party, you also control what leaves your infrastructure, which matters under KVKK and GDPR.
How can a studio check its signal quality?
Ask three questions. Does our MMP send ad networks revenue, or only installs and level events? Does that revenue include ad revenue, refunds, and web shop sales? Do events arrive from the SDK and the server without a shared event ID? If the answers are "only installs", "no", and "probably", your gap isn't attribution. It's signal quality.