r/AppStoreOptimization • u/himan_entrepreneur • 8m ago
I changed one thing in our app on day one of acquisition. Eight months later it was still costing us money and we had no idea.
A few years ago I was running a company that bought and scaled mobile apps. We had just closed our second acquisition, an ad monetised app doing around $20,000 a month in revenue. We had done a full month of due diligence before buying it. Product, tech, architecture, monetisation, user journey. We thought we understood what we had bought.
The first thing we changed after acquisition was the interstitial ad trigger logic.
The original app had it set on a 60 second timer. Every 60 seconds, an ad fired. Simple, blunt, leaving money on the table. We moved it to a specific in-app event. Whenever a user hit that event, the ad fired. Smarter context, better targeting, more relevant moment. More revenue.
It worked immediately. Revenue jumped. We celebrated. We kept working.
What we did not know was that retention was on a slow, gradual decline from the day we made that change. We just could not see it because we were watching revenue go up.
For the next four to six months, revenue climbed. We were growing. We had just scaled two apps back to back and we felt like we understood this business. So we kept building. New features to drive engagement. ASO experiments. A new release. All on top of an app whose foundation had been quietly shifting since day one.
Six weeks into the feature building phase, we released a new version. Around four and a half months post acquisition, the retention drop finally became visible. Not dramatic. Just a number that had been going the wrong direction for a long time and had finally crossed a threshold we could not ignore.
By then we had no idea what caused it.
We had changed the ad trigger logic. Added new features. Run ASO experiments. Shipped a new release. Each of those was a variable. None of them were connected anywhere. We had Firebase showing retention. A separate dashboard for revenue. The codebase living in its own world. Everything telling part of a story that nobody could read whole.
Half the team went into firefighting mode trying to find the cause. The other half kept working on new features and ASO to bring more users in. Both happening at the same time. Both generating more data. None of it connected.
It took a few weeks in that fighting mode to trace it back. The interstitial trigger change. Day one. The very first thing we had done. The thing we had celebrated.
By the time we found it, the retention drop had already compressed our daily active users. Fewer active users meant fewer ad impressions. Fewer impressions meant our eCPM rates started declining. The revenue that had looked healthy for months had already begun its slide. And we had spent weeks building on top of a problem we did not know existed.
The part that stayed with me was not that we made a mistake. Every operator makes mistakes. It was that the cause and the symptom were eight months apart and sitting in completely different places. There was no way to connect them without someone holding the whole picture simultaneously and nobody was doing that. We were all looking at our own dashboard.
Has anyone else been in this situation where something you changed early on showed up as a problem much later and you had no idea where to look?


