At a glance
| Field | Detail |
|---|---|
| Brand | Bigo Live |
| App category | Live-streaming community |
| Market | Test campaigns in multiple markets, including the US; headline retention results concern the US |
| Channels | Liftoff user acquisition and re-engagement |
| Goal | Acquire highly retaining users, with a target D2 retention rate of 30% |
| Reported result | Liftoff reports US D2 retention above 30% for over four months |
The Bigo Live retention case published by Liftoff describes how the live-streaming app Bigo Live combined acquisition, re-engagement and creative testing around a day-two (D2) retention target. Liftoff attributes the reported results to that combined approach. The page does not establish the separate contribution of each activity.
What they did
Bigo Live wanted a programmatic partner to expand its user acquisition efforts while bringing in users who would remain active. Liftoff set up test campaigns across different markets, including the US, against the stated retention target.
According to Liftoff, its account team optimized campaigns to manage cost per install (CPI) fluctuations after ATT. It also ran ongoing tests across geographies, experimenting with optimization toward post-install events to maintain and improve retention. The specific events and optimization settings are not specified.
Acquisition and re-engagement ran together. The page says a third of the total budget went to re-engagement, while most spending supported acquisition. Liftoff describes this allocation as supporting both new-user acquisition and bringing existing users back. The page does not provide a comparison against an acquisition-only campaign.
Bigo Live also worked with Liftoff’s creative team. One reported test added a text call-to-action overlay and featured three content creators instead of one. Because both elements changed in the described test, the page does not establish which element contributed to the reported install increase.
Results
These are Liftoff-reported campaign outcomes. Calendar dates, operating-system coverage and underlying cohort sizes are not specified.
| Metric | Reported figure | Basis and scope |
|---|---|---|
| D2 retention | Above 30% for over four months | US results; cohort sizes and calendar dates: Not specified |
| User acquisition spend | 2x increase in four months | US results; starting spend and calendar dates: Not specified |
| Installs in a creative test | 23% increase | Test combined a text call-to-action overlay with three creators instead of one; market, duration and install counts: Not specified |
The spending result describes a change in acquisition investment. It does not supply a corresponding CPI or revenue result. The retention result gives a sustained period above the target, but the page does not provide a full cohort series for checking variation within that period.
What app advertisers can take from it
Our interpretation is to use the case as a set of testing questions:
- Check whether the acquisition goal names a post-install outcome. Define the retention event and cohort basis before comparing your app with this case. The measurement data path can help structure that review.
- Compare acquisition and re-engagement results separately before adopting the reported budget split. Review the audience and intended return action through the re-engagement planning checks.
- Review creative changes as a combined treatment when several elements change together. A follow-up test could separate the overlay from the creator mix.
- Keep market scope attached to every result. The US retention findings do not establish the same outcome for every geography tested.



