Liftoff

Case breakdown · 9 Nov 2026

Case breakdown: MFour survey acquisition with Liftoff

The US iOS campaign increased spend while holding CPI constant, but missing measurement details limit interpretation of survey engagement rates.

G2P Media · · 3 min read

Case breakdown: MFour survey acquisition with LiftoffLiftoff

At a glance

FieldDetail
BrandMFour
App categoryMobile research and surveys
MarketUS; iOS
ChannelsLiftoff, using real-time bidding exchanges and mobile ad networks; individual inventory sources: Not specified
GoalAcquire new users who complete 3 surveys within Surveys On The Go
Reported resultLiftoff reports that spend increased three-fold while cost per install held constant during CPA optimization

The MFour user acquisition case concerns Surveys On The Go, the mobile research app created by MFour. Liftoff’s official account describes a campaign aimed at acquiring users who completed surveys after installing. Its useful operational detail is the sequence: profile engaged users, optimize acquisition, iterate creative, and then scale toward daily volume targets. Campaign dates and duration are Not specified.

What they did

Before launch, Liftoff matched device IDs from Surveys On The Go users against its user data store. It used those matches to build audience profiles, including a view of other apps installed on users’ phones. Those profiles supported targeting look-alike users across exchanges and mobile ad networks.

The initial phase optimized cost per install (CPI). Liftoff reports that the campaigns generated over 100 installs per day and that its install-to-action (ITA) rate improved during this phase. Creative iterations and A/B testing accompanied the optimization work.

The campaign subsequently moved into cost-per-action (CPA) optimization, with a focus on increasing daily volume while maintaining acquisition costs. Liftoff reports that spend increased three-fold and CPI held constant. The page does not provide an absolute CPA or a quantified change in CPA, so the phase’s name should not be read as evidence of a particular action cost.

Results

All figures below are reported by Liftoff for the US iOS campaign.

MetricReported figureBasis and scope
Early install volumeOver 100 installs per dayBeginning of CPI optimization; Liftoff describes these installs as high quality. Reporting duration: Not specified
Initial ITA rate196%Start of the campaign’s CPI optimization phase. Action-counting rules and observation window: Not specified
ITA during CPI optimization300%Reached over the CPI optimization phase; the stated acquisition goal involved completing 3 surveys. Measurement window: Not specified
SpendIncreased three-foldCPA optimization phase. Absolute spend, exact comparison period and duration: Not specified
CPIHeld constantDuring the reported spend increase. Absolute CPI: Not specified

The page gives inconsistent final ITA values, so that endpoint is excluded here. It also leaves the treatment of repeated survey actions unspecified. The reported ITA rates therefore should not be presented as percentages of unique users completing the acquisition goal.

What app advertisers can take from it

These suggested checks are our interpretation of the case:

  • Check the action definition before comparing engagement rates. Establish whether your report counts survey completions, unique users reaching a milestone, or another event basis. A review of event definitions and reporting paths can help make that distinction explicit.
  • Compare install volume, CPI and the intended post-install outcome together. The case reports constant CPI during increased spend, but supplies no absolute CPA with which another advertiser could compare its own action costs.
  • Keep audience profiling, creative changes and optimization phases in the campaign record. All appeared in Liftoff’s approach, but the page does not isolate their individual contributions. Treat them as components to examine rather than independently established causes of the reported performance.

Sources

Liftoff: Mfour - Liftoff · 9 Nov 2026

Web Summit (CC BY 4.0): PD1_9428 | 12 November 2026; Volunteers during day three of …

Discuss your app.

Discuss your app