How to Run Meta Ads for Mobile Apps (Install and In-App Event Campaigns)

How to Run Meta Ads for Mobile Apps (Install and In-App Event Campaigns)

1. 1

   Register the app and decide which in-app event counts as success

   In Meta for Developers, register your app (iOS and/or Android) and add the store URLs. Then decide the one event that best signals a valuable user: a completed registration, a trial start, a first purchase or a completed tutorial. Installs alone are cheap to buy and often low quality. Write the event down before you build anything else, because every later step depends on it.

2. 2

   Install the Meta SDK or connect your mobile measurement partner

   Have your developer add the Meta SDK to the app and log the event you chose in step 1 (plus standard events such as purchase and its value, if relevant). If you already use a mobile measurement partner such as AppsFlyer, Adjust or Branch, connect it to Meta instead of or alongside the SDK, following that partner's setup guide. In Events Manager, confirm test events arrive from a real test device before you spend anything. On iOS, expect to configure event priority under Meta's aggregated event measurement and to rely on modelled results for users who decline tracking.

3. 3

   Create an App promotion campaign in Meta Ads Manager

   In Ads Manager choose Create, select the App promotion objective, and pick your app and its store. Meta currently offers an automated app campaign format (Advantage+ app campaign) that lets Meta choose placements and audiences, alongside manual setups. For a first launch the automated format is simpler to run, but check which option is available for your app and region. Choose the optimisation goal: app installs to get started, or an in-app event once the SDK reports enough of that event. Optimising for a deeper event usually needs a minimum volume of those events before the delivery system stabilises, so many teams start on installs and graduate.

4. 4

   Set the budget, schedule and audience guardrails

   Set a daily budget you can sustain for at least a week without editing, since frequent edits reset learning. Choose countries deliberately, because cost per install varies a lot by country and one low-cost country can swallow the budget with low-value users. Exclude existing users if your SDK or partner supports it, and set minimum age to match the app's store rating. Avoid heavy interest narrowing; with app campaigns Meta tends to perform better when creative does the targeting work.

5. 5

   Prepare vertical video and static creative that shows the app in use

   Upload several distinct creatives rather than several variations of one idea: a short screen-recorded demo, a problem-led hook, a user-benefit statement and a static screenshot with a single claim. Use 9:16 for Stories and Reels placements and a square or 4:5 version for feed. Show the real interface within the first seconds, put key text inside the safe zone, and keep claims to what the app does today. Add a clear store call to action. Infinall AI can generate the research, copy and image or video drafts for this step, which land in an Approval Queue for you to edit before you export anything.

6. 6

   Launch, wait through the learning period, then judge by cost per valuable event

   Publish the campaign and avoid changing budget or creative for the first several days. Read results as cost per your chosen event (cost per registration, per trial, per purchase), not only cost per install, and compare each creative on that basis. Cut creatives that spend without producing the event, add new concepts rather than minor tweaks of winners, and cross-check Meta's numbers against your measurement partner or store analytics because attribution windows and iOS modelling mean the dashboards will not match exactly.