App Campaigns are Google’s black box: you supply creative assets and a goal, it buys Search, Play, YouTube and Display inventory automatically. For Nepali fintech, e-commerce and utility apps that automation works — provided the listing converts, the goal is activation (not installs), and fraud gets watched. Organic foundations first: the ASO playbook and fintech ASO section. This post is the paid companion.

1. Structure before spend: listing first, campaigns second

Never launch paid volume into an unconverted listing. Pre-flight checklist:

• Title + short description rewritten against your keyword set, first two screenshots carrying the value prop, rating at 4.0+ (see the ASO playbook).
• Firebase + GA4 linked, in-app events defined: at minimum sign_up, plus one activation event that means business value (KYC submitted, first transaction, first order).
• Billing ready in USD with a backup payment method — paused-for-billing campaigns lose learning that money cannot instantly rebuild (same rule as dollar-card billing).

2. Campaign architecture for one Nepali app

• One campaign per goal tier: installs (learning + volume), then a second campaign bidding to the activation event once install volume supports it. Do not mix install-bidding and action-bidding in one campaign.
• Geo: Nepal-wide for digital goods; serviceable-regions-only for delivery, agent or branch-dependent apps. City splits only when budgets justify separate learning per geo.
• Language and creative sets: separate asset groups for English-first vs Nepali-first creative where the audiences genuinely differ (urban fintech vs Valley-outside utility) — same logic as the listing localisation in the ASO guide.
• Start bids on tCPI for volume, migrate to tCPA on activation once 30+ monthly conversions exist for the action. Migrating early on thin data is the most common failure mode.

3. Assets that survive automation

App Campaigns remix what you upload — quality in, quality out:

• Text: multiple headlines and descriptions spanning use cases (pay bills, shop online, track orders), not five variants of one slogan.
• Images and video: portrait and landscape sets, real app UI (not stock lifestyle), captions burned in for sound-off, prices in NPR where relevant.
• Video minimum that matters: one 30-second flow demo; portrait cutdowns for Shorts/Discover inventory per the Shorts guide logic.
• HTML5/interactive assets only where your team can maintain them — unmaintained playables rot into misleading demos and review complaints.

4. Nepal-specific targeting and budget notes

• Language layering: English + Romanized Nepali ad text variants where your buyers type that way; verify against your own search-term and review language, not assumptions.
• Festival seasonality: pre-Dashain/Tihar install demand rises with shopping and gifting intent — lock budgets and creative before the peak window; CPMs spike with everyone else’s money.
• Starter budgets: fund learning fully or do not start — a daily budget that cannot buy double-digit installs teaches the algorithm nothing. Consolidate into one campaign rather than splitting across three starved ones.
• Placement vigilance: review where installs originate; exclude sources delivering install-farm patterns (instant uninstalls, zero activation) on sight, weekly.

5. Measure to activation, reconcile like revenue

• Primary: cost per activated user (registered, KYC-complete, first-transaction — your definition, written down), not CPI.
• Join ad-side installs to in-app activation by user/tool ID; report the activation rate per campaign weekly.
• Reconcile three lists monthly: platform installs, analytics activations, business outcomes (funded wallets, first orders) — per the COD playbook’s join routine.
• Fraud watch: install-to-activation collapse, geo anomalies outside service areas, device/OS skews with no business explanation. Pause first, investigate with data, document.

What to do this week

1. Confirm the listing converts (rating, screenshots, keywords) before spending a rupee on installs.
2. Define the single activation event and wire it end-to-end into Firebase/GA4.
3. Launch one tCPI campaign, one geo, one budget that can learn — then migrate winners to activation bidding on evidence.

Related reading: ASO playbook, fintech marketing, Google Ads management pricing, COD attribution, and hire a digital marketing expert.