This checklist adapts Xiao Wei's 2023 article about preparing Facebook ads for teams launching Meta app campaigns. Its developer-console screenshots show an older interface. Use the current workflow and labels in your own account.
Download the launch checklist
Meta App Ads Launch Checklist (PDF, English and Simplified Chinese). Use this worksheet to assign owners and check assets, permissions, event tests, and launch sign-off. Do not enter account passwords.
1. Collect account and app details
- Business identity: legal company details, contact email, billing information, and documents needed for verification.
- Assets: Meta business portfolio (formerly BM), ad account, Facebook Page, and appropriate administrator access.
- App: Meta developer App ID, app name, iOS or Android platform, store URL, and package or bundle ID.
- Campaign plan: target markets, creative, copy, budget, payment method, and optimization event.
Record the owner and permissions for each asset in one handover sheet. See our Facebook account guide and product catalog.
2. Set up the developer app
- Create the app using an authorized account and choose the current flow that matches its actual use. Do not rely on the 2023 screenshot's app-type labels.
- Add app name, contact email, business details, platform, bundle or package ID, and store URL.
- Complete any current verification, permission, and policy checks. Confirm the app is eligible for ad delivery and event integration.
- Authorize the correct ad account and verify that the app appears in Ads Manager.
Keep app secrets, attribution keys, and administrator credentials out of public documents and chats.
3. Prepare attribution and events
Have developers, measurement owners, and media buyers agree on install, first-open, registration, and purchase event definitions and value fields. If using AppsFlyer, connect Meta ads, map events, set lookback windows, and verify with a test device. See the AppsFlyer integration guide.
Choose an optimization event that matches the business goal and has sufficient volume. Define CPI, CPA, and ROAS consistently before launch. For campaign setup, see our Meta app ads guide.
4. Final launch check
- Ad account and asset permissions work; the Page is available and users in the target markets can download the app.
- Store listing, creative, copy, and CTA reflect the product and comply with policy.
- Test installs and core events are received, and the optimization event is selectable.
- Budget, currency, time zone, attribution window, markets, and links have been checked.
The source article's comments about credit-approved audiences and AI video were open questions, not validated performance findings.
FAQ
Are a BM, ad account, and Page enough?
App campaigns also need a usable app asset, correct authorization, and reliable event reporting.
Can I follow the old developer-app screenshots?
Use the current console prompts and your actual use case; labels and steps may have changed.
Who should validate events?
Developers check triggers and parameters, measurement owners check receipt and mapping, and media buyers confirm that the event can be used for optimization.