Tripledot's AppLovin Apps Portfolio: A Buyer's Guide

Tripledot Studios said on 1 July that its integration of AppLovin's former Apps business, Lion Studios included, is complete. The deal itself closed a day earlier, on 30 June. So the Tripledot AppLovin apps portfolio now sits under one roof, and for any buyer who has spent against titles that used to live inside AppLovin's games division, this is the point where the paperwork catches up with the business logic.

The deal's shape changed twice before it closed. AppLovin first said in February it would sell its Apps business to Tripledot for roughly $900M in a mix of cash and equity, freeing it to concentrate on advertising technology alone. By May, with AppLovin's Q1 results confirming how fast its Axon-driven ad revenue was growing, the terms had moved to roughly $400M in cash plus a 20% stake in Tripledot, with closing set for 30 June. As we wrote in AppLovin's pure ad tech business model, after Tripledot, the restructured deal reflected AppLovin's growing confidence that ad tech alone, not games publishing, was the more valuable business to run.

What ownership actually changes

For a UA manager or growth lead with campaigns running against ex-AppLovin titles, the ownership change is not cosmetic.

Start with the paperwork. The publisher entity on insertion orders and revenue share agreements now reads Tripledot rather than AppLovin's Apps division, so anyone holding standing contracts with minimum spend commitments or rebate structures tied to the old entity needs those novated or reconfirmed in writing. Don't assume they carry over.

Reporting access changes too. AppLovin's Apps titles previously reported through AppLovin's internal BI stack, which had visibility into Axon bidding data because publisher and network sat inside the same company. Tripledot runs its own measurement stack, so expect a period where historical trend lines do not stitch together cleanly across the ownership boundary, particularly for anyone running longer lookback cohort analysis.

The change that matters most to buyers, rather than to the studios themselves, is that the ad network relationship is no longer vertically integrated. AppLovin's Apps titles got a structural advantage from sitting inside the same company as Axon: tighter bidding feedback loops and early access to new ad formats, with less friction between demand and supply teams. That advantage disappears the moment Tripledot becomes an arm's length customer of AppLovin's ad network, buying inventory like any other publisher.

A buyer's checklist for the transition

Anyone with active spend or planned campaigns touching former AppLovin Apps titles should work through a short list before assuming continuity.

• Confirm which legal entity now holds the publishing agreement, and whether any volume-based terms need renegotiating under Tripledot's contracts.
• Re-pull baseline performance data for the two weeks either side of 1 July, since a reporting-stack handover is a common point for silent gaps or double counting.
• Ask whether SDK versions or mediation configurations changed as part of the migration; a publisher integration project is a common moment for an unannounced SDK bump.
• Check whether creative approval workflows moved from AppLovin's internal process to Tripledot's, since approval turnaround times can shift materially between teams.
• Watch bid density and eCPMs on ex-AppLovin inventory over the following four to six weeks for any drift, now that the demand side is a separate commercial relationship rather than an internal one.

The Lion Studios question

Lion Studios is the highest-profile name in the portfolio Tripledot now owns, and it is also the clearest test case for how much of AppLovin's old creative and publishing playbook survives the move. Lion built its reputation on rapid hyper-casual and hybrid-casual testing cycles, run with AppLovin's own ad stack feeding signal back into creative decisions in close to real time. Whether that loop holds up once Lion is buying media as an external customer, rather than as a sibling business unit, is the detail worth watching over the two quarters ahead rather than assuming away.

Buyers with existing relationships into Lion or the wider ex-AppLovin catalogue should treat the coming reporting cycle, not the announcement itself, as the real test. Integration announcements are clean. Reconciled cohort data, stable eCPMs against unchanged service terms: that's the actual proof the portfolio has landed intact.

A precedent worth remembering

This is not the first time the mobile UA market has watched a publisher-network relationship get pulled apart or stitched together. Unity's 2022 merger with ironSource ran the process in the opposite direction, folding a large ad network into a company that also sold the engine much of the industry built on, and buyers spent the better part of a year working out which parts of the combined stack had actually changed and which had simply picked up a new name. The lesson that carries over to the Tripledot AppLovin apps portfolio is the same one. A corporate integration announcement describes intent, not the operational reality a buyer experiences three or four reporting cycles later. Treat the first month's numbers as a baseline to interrogate, not a result to accept at face value.

The practical difference this time is direction. Unity was combining a network with an engine and a publisher-facing monetisation stack, adding complexity to a single company's offering. Tripledot's move separates a publisher from the network it used to share a balance sheet with, which is a cleaner split in principle but still introduces exactly the kind of reporting and contractual seams that took the ironSource integration months to smooth out. Buyers who lived through that earlier transition already know what to look for: unexplained gaps in historical trend data, support tickets that bounce between two teams because ownership of an issue is unclear, and SLA commitments that technically still apply but nobody has confirmed in writing under the new structure.

What the Tripledot AppLovin apps portfolio means for Q3

Tripledot now runs one of the larger hybrid-casual and casual portfolios in the market. It built that from its own titles plus what used to be two separate publishing operations. The scale gives it more room to negotiate network terms and more data to inform creative testing across a wider slate. It also means any single vendor decision Tripledot makes now touches a meaningfully larger share of total mobile UA spend than it did in June. Buyers who track publisher concentration as part of vendor risk planning should update that model this week, rather than waiting for the quarterly review.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• AppLovin's Q1 2025 Earnings and the Revised Tripledot Deal
• Tripledot's AppLovin games portfolio, one week in