How an Advantage+ app campaign works
An Advantage+ app campaign promotes a mobile app on Meta’s surfaces with most of the setup handed to the delivery system. You connect the app, choose the store, name the event you want more of — an install, a registration, a purchase inside the app — set a budget, and upload creative. Meta then decides which people to show it to, on which placement, and in which format.
The important difference from a website campaign is measurement. A browser campaign can rely on the pixel and the Conversions API. An app campaign relies on Meta’s own SDK inside the app, or on a mobile measurement partner that passes events back. Nothing works until that connection is live and sending real events, and no amount of creative will rescue a campaign whose events never arrive.
Apple’s app tracking rules add a second layer. On iOS, event data is limited and delayed, so reporting is coarser than advertisers who came from web campaigns expect. Android reporting is closer to what you are used to. Judging the two together in one column will mislead you.
Why it matters
App promotion is unforgiving because the sale sits behind an app store you do not control. Someone can tap your advert, land on the store listing, read a poor rating and leave, and you pay for that tap. Automated campaigns amplify this: they will find people willing to tap, which makes the listing itself part of the campaign.
It also matters because the automation removes the arguments advertisers usually have about audiences. With targeting largely gone, the levers that remain are the event you optimise towards, the creative you supply, and the quality of the store listing. That is a shorter list, which makes accountability clearer.
Common mistakes
Optimising for installs when the business needs paying users is the usual one. Installs are cheap to buy and easy to buy badly, and a campaign told to maximise them will do exactly that. If your app makes money on a subscription or a purchase, tell the campaign that, once you have enough of those events for it to learn from.
The next mistake is launching before the measurement chain is verified end to end. The other is comparing in-app revenue reported by Meta with revenue in your own dashboard and assuming one of them is broken; different attribution windows and platform rules make a gap normal rather than suspicious.
How to act on it
Verify events first. Install the app from a test device, complete the action you care about, and confirm it appears in Events Manager before any money is spent. Then decide the single event the campaign should chase, and leave it alone long enough to stabilise.
Treat the store listing as part of the advert: screenshots, first lines of description and ratings all decide whether a paid tap becomes an install. Report iOS and Android separately, and if your app monetises unevenly across countries, split those too. Where an app is the main channel rather than a side project, it is worth building the measurement properly before scaling app install advertising.