At a glance
| Field | Detail |
|---|---|
| Brand | Bitsmedia |
| App category | Muslim lifestyle app |
| Market | Not specified |
| Channels | Liftoff Monetize |
| Goal | Grow Muslim Pro’s ad revenue while protecting user satisfaction and cultural sensitivity |
| Reported result | Liftoff reports a 20% increase in eCPM and a 10% lift in ARPDAU; measurement period and comparison baseline: Not specified |
Bitsmedia ad monetization for Muslim Pro combined placement testing, frequency limits and user-facing ad information, according to Liftoff’s case study. The Singapore-based company wanted to increase revenue while respecting the expectations of its global faith-based audience. The page identifies Ramadan as a period of peak engagement, but does not establish that the reported results were measured during Ramadan.
What they did
Liftoff says Bitsmedia worked with Liftoff Monetize following a broader monetization restructure. The approach addressed ad placement, frequency and transparency together. App-open ads became a core revenue driver, while a custom Ad Counter showed users how many ads they would encounter. Bitsmedia also capped interstitials at three per day.
The teams used continuous A/B testing to refine placements, formats and frequencies based on engagement data. Liftoff also describes regular collaboration with Bitsmedia to keep served creatives culturally appropriate and aligned with Muslim Pro’s audience.
Partner evaluation extended beyond reported ad pricing. Bitsmedia assessed delivery scale, inventory control, technical support and whether formats suited the app’s content. The case also describes a delivery problem encountered with some ad networks: high eCPMs could coincide with slow ad delivery, reducing total impressions and hurting monetization. Those networks are not identified, and the page supplies no quantified latency comparison.
Results
Liftoff attributes the following results to its work with Bitsmedia on Muslim Pro:
| Metric | Reported figure | Basis and scope |
|---|---|---|
| eCPM | 20% increase | Muslim Pro monetization case; market, platform, measurement period and comparison baseline: Not specified |
| ARPDAU | 10% lift | Muslim Pro monetization case; market, platform, measurement period and comparison baseline: Not specified |
| App-open share of ad impressions | Nearly 50% | Share of total ad impressions described in the case; market, platform and measurement period: Not specified |
The impression share describes the placement mix, not its share of revenue. The page does not isolate the contribution of app-open ads, frequency limits, the Ad Counter or creative review to the reported gains.
Liftoff describes retention and satisfaction as remaining high, but provides no numerical retention or satisfaction results. The case therefore supports reviewing the combined approach while leaving the size of those experience outcomes unquantified.
What app advertisers can take from it
Our interpretation is to assess delivery, monetization and user experience together when reviewing an app’s ad strategy. Suggested checks include:
- Compare placement share with revenue and engagement outcomes. An impression share alone does not establish a placement’s revenue contribution.
- Review whether users can understand expected ad frequency, using Bitsmedia’s Ad Counter as a concrete example to evaluate.
- Check frequency limits against your app’s usage patterns. The reported interstitial cap is Bitsmedia’s implementation, not a universal recommendation.
- Compare ad delivery speed alongside eCPM when evaluating partners, following the delivery issue described in the case.
- Keep the market, platform, measurement period and baseline explicit in your own readout. Use an agreed measurement data path to align event definitions and reporting basis before interpreting changes.



