Liftoff

Case breakdown · 5 Nov 2026

Case breakdown: Talabat’s shift from installs to food orders

Liftoff’s case describes a Saudi Arabian iOS campaign that moved from install targets to food-order optimization, alongside separate creative tests.

G2P Media · · 3 min read

Case breakdown: Talabat’s shift from installs to food ordersLiftoff

At a glance

FieldDetail
BrandTalabat, owned by Delivery Hero
App categoryFood ordering mobile app
MarketSaudi Arabia
ChannelsLiftoff mobile user acquisition on iOS
GoalLower cost per install and cost per action; increase the share of installers who place an order
Reported resultLiftoff reports a 72.2% increase in install-to-action rate. Baseline and comparison period: Not specified

The Talabat user acquisition case describes Liftoff’s work on the Talabat food ordering mobile app in Saudi Arabia on iOS. The campaign connected install acquisition with subsequent food orders, then changed its optimization focus after reaching its install-cost target. Liftoff reports the campaign actions and results on its official case page. Campaign dates and duration: Not specified.

What they did

According to Liftoff, the campaign began by sending install and post-install food-order postbacks from Adjust to Liftoff. Those events supplied the measurement inputs for evaluating acquisition and ordering behavior.

After an initial exploration period involving testing and modeling, Liftoff built lookalike profiles of people considered likely to install and order food. Its platform then bid programmatically for that audience while optimizing cost per install. Alongside audience targeting and bidding, Liftoff tested creative to improve install costs and install-to-order rates.

The campaign subsequently changed its commercial and optimization focus. Once the target cost per install was reached, Talabat moved to a cost-per-action payout, and Liftoff focused on acquiring people who placed food orders, reducing acquisition costs for that action and scaling the campaign.

The creative work included separate comparisons of an animated banner against a static banner, and an image of a Middle-Eastern feast against an image of pizza. These tests addressed format and imagery within the reported campaign.

Results

Liftoff reports the following results for the Saudi Arabian iOS campaign. The page does not provide campaign dates, absolute starting values or a common comparison window. The creative tests also lack sample sizes and a defined conversion event.

MetricReported figureBasis and scope
Cost per actionDecreased by 15.5%Campaign food-order acquisition; starting cost and comparison period: Not specified
Post-install events completedIncreased by 48.5%Food orders in the campaign; absolute totals and comparison period: Not specified
Install-to-action rateIncreased by 72.2%Progression from install to food order; starting rate and comparison period: Not specified
Animated banner conversion rateImproved by 172%Animated versus static banner; conversion event, sample size and test period: Not specified
Feast image conversion rateImproved by 23%Middle-Eastern feast versus pizza image; conversion event, sample size and test period: Not specified
Average daily ad spendIncreased by 25.5%Reported after CPI targets were reached and optimization shifted to CPA; spend amounts and comparison period: Not specified

The spend increase describes campaign expansion. It does not supply a revenue or profitability result. Similarly, the creative comparisons lack the event definitions needed to connect their conversion-rate improvements precisely to the reported install-to-order change.

What app advertisers can take from it

The following checks are our interpretation of the case, rather than additional campaign findings:

  • Review the event definitions behind installs, food orders and cost per action. Check that the postbacks used for optimization match the outcomes being evaluated. The measurement data-path review provides a way to organize that check.
  • Compare the criteria for an optimization change with the intended business outcome. Talabat’s reported sequence moved from reaching an install-cost target to optimizing food orders. Check what evidence would justify a similar transition for your app.
  • Keep format and imagery comparisons distinct in a creative test plan. Before applying either reported creative result elsewhere, check the conversion event, audience, test period and sample size.
  • Review scaling against downstream outcomes. Request absolute acquisition costs, order totals and comparable observation periods before using these reported changes as planning benchmarks. The case supports examining the relationship between acquisition and ordering; it supplies no universal budget rule.

Sources

Liftoff: Talabat - Liftoff · 5 Nov 2026

RG TLV (CC BY 2.0): Untitled | RG TLV

Discuss your app.

Discuss your app