Earnings

All three exist: a fixed monthly payout, a per-app fee, or a share of the ad revenue the published apps earn. The right model depends on the publisher and what they're putting on your account.

To receive money from paid apps or in-app purchases you need a Google payments profile linked to an Indian bank account, and Google collects your PAN for tax reporting. Free apps with no in-app purchases need no payments profile at all — only the one-time $25 registration. Earnings are paid out monthly once your balance crosses the payout threshold, converted to INR at Google’s exchange rate.

A typical free Android app earns roughly $0.50–$3.00 per 1,000 daily active users per day from in-app advertising, which works out to about $15–$90 per 1,000 DAU per month. The spread is enormous because earnings are the product of three numbers: how many ad impressions each user sees, what advertisers pay for that audience, and what share of requests actually get filled. A casual game in the United States showing rewarded video can clear $5 per 1,000 DAU per day; the same game in a low-CPM market showing only banners may make $0.10. Ad income also ramps — a brand-new app earns very little in month one because ad networks need install volume and retention data before they bid seriously on its inventory.

eCPM is effective cost per mille — the ad revenue an app earns per 1,000 ad impressions. The formula is eCPM = (total ad revenue ÷ total impressions) × 1000. If an app served 240,000 impressions last month and earned $720, its eCPM is $3.00. eCPM is the single most useful monetization number because it normalises across formats, countries and networks: it lets you compare a rewarded-video placement against a banner, or US traffic against Indian traffic, on one scale. Watch eCPM per placement, not just per app — one badly positioned banner can drag the whole average down while looking fine in aggregate.

Rewarded video earns the most per impression, interstitials are second, and banners are the lowest. Rough 2026 global averages: rewarded video $8–$20 eCPM, interstitial $4–$12, native $2–$6, banner $0.20–$1.50. Rewarded wins because the user opts in and watches to completion, so advertisers pay for genuine attention. Banners earn least per impression but fire constantly, so they still contribute real volume. The best-earning apps do not pick one — they run rewarded video at natural opt-in moments, an interstitial on a session or level boundary, and reserve banners for screens where a full-screen ad would break the flow.

Indian traffic typically earns $0.30–$1.50 eCPM on banners and $1–$4 on interstitials, with rewarded video reaching $2–$6. That is roughly a quarter to a tenth of United States rates, because eCPM tracks what local advertisers will pay to reach that audience. Two practical consequences: an India-first app needs far more daily active users to hit the same revenue as a US-first one, and format mix matters more — leaning on rewarded video instead of banners can double effective earnings on the same user base. Payments from Google are made in local currency once the account passes the $100 payment threshold.

Expect meaningful ad revenue from roughly month three, not week one. The ramp has three stages: for the first few weeks the app has too few impressions for networks to bid confidently, so eCPM sits well below its eventual level; by month two, install and retention data lets mediation price the inventory properly; by month three or four, earnings stabilise and track daily active users. This ramp is why app monetization partnerships often start on a fixed monthly payout while installs build, then move to a revenue share once the ad income is real and measurable.

An ad revenue share agreement pays each party a fixed percentage of the in-app advertising income an app generates, instead of a flat fee. In the Android publishing world the common shape is: one party builds, publishes and maintains the app and runs its ad monetization; the publishing partner whose Google Play account distributes it receives an agreed percentage of net ad revenue. Net matters — the split is normally applied after the ad network's own cut and after Google's platform fees, so ask explicitly which line the percentage applies to. A well-written agreement names the ad networks in use, the reporting dashboard both sides can read, the payout day, and what happens to the app if either side exits. Full explainer here.

No — past a point, extra ads reduce total revenue by driving users away. Ad income is impressions multiplied by eCPM, but impressions depend on retention, and aggressive ad load is one of the top reasons users uninstall. Google Play also enforces this directly: ads that interrupt without warning, appear outside the app, or cover content are policy violations that get an app removed. The pattern that actually earns is fewer, better-placed ads at natural breaks — a session boundary, a level end, an opt-in reward — measured on revenue per daily active user over 30 days rather than impressions per session.

AdMob pays monthly once your balance passes the $100 payment threshold, with payments normally issued between the 21st and 26th of the following month. The cycle is worth understanding because it delays first income far more than most people expect. Earnings accrue through a calendar month, are finalised in the first days of the next month after invalid-traffic deductions, and are only released if the balance has crossed $100 and the account has completed identity verification, address (PIN) verification, and tax form submission. An app earning $30 a month therefore sees nothing until month four. Payment is made in local currency by bank transfer for most countries, including India. If a payment is held, it is almost always one of those three verification steps sitting incomplete rather than a problem with the earnings themselves.

A sudden ad revenue drop is almost always one of five things: a seasonal advertiser-spend fall, a change in the country mix of your users, a broken or misconfigured ad unit, a policy restriction placed on the app, or an invalid-traffic deduction. Diagnose in that order. Check the calendar first — global eCPM falls sharply in January after Q4 advertiser budgets reset, and dips again mid-year. Then compare impressions against eCPM: if impressions held but eCPM fell, it is a demand or geography issue; if impressions fell, it is a traffic, SDK or fill problem. Open the policy centre in both AdMob and Play Console, because an app-level ad serving restriction shows there and nowhere else. Finally check whether a recent app release changed ad placement or SDK version. Revenue that halves overnight with no impression change is the classic signature of a policy restriction, not a market move.

None of them wins outright — AdMob tends to lead on banner and interstitial demand breadth, Unity Ads and AppLovin usually beat it on rewarded video in games, and the highest earners run all three through mediation rather than choosing. The useful way to read the difference is by demand type: AdMob draws on Google's enormous advertiser pool, which fills reliably in almost every country and format; Unity Ads is built around game advertisers and performs strongest on rewarded video in a gaming audience; AppLovin MAX is primarily a mediation platform with its own strong rewarded and interstitial demand. In a mediated stack they bid against each other per impression, which is where the commonly reported 15–40% eCPM uplift comes from. Pick a single network only while volume is small; once an app has a few thousand daily users, the question stops being “which one” and becomes “which mediation layer”.

CPM is what an advertiser pays per 1,000 impressions, eCPM is what the publisher actually earns per 1,000 impressions after fill and mediation, and RPM is revenue per 1,000 sessions or users rather than per impression. They are easy to confuse because all three are “per thousand” numbers. CPM is a buy-side price and includes the network's cut. eCPM is the sell-side reality and is the number to optimise: eCPM = (revenue ÷ impressions) × 1000. RPM changes the denominator to something user-shaped, which makes it better for judging whether an ad layout is working, because it captures the case where more ads per session raise impressions while driving users away. A practical habit: optimise eCPM to judge a placement, and RPM or revenue per daily active user to judge the whole app.

Roughly 1,500 to 3,500 daily active users for a US-heavy audience, and 15,000 to 50,000 for an India-heavy one. The arithmetic is simple: monthly ad revenue is approximately daily active users × ARPDAU × 30, where ARPDAU is average revenue per daily active user. Typical ARPDAU for a modestly monetised app runs about $0.01–$0.02 on Indian traffic and $0.10–$0.30 on United States traffic, with well-tuned games reaching higher. So $1,000 a month needs about 1,700 daily users at $0.02 ARPDAU, or 33,000 at $0.001. Two conclusions fall out of that: geography changes the answer by an order of magnitude, and raising ARPDAU through format mix and placement is usually cheaper than buying ten times the users.

Advertising earns a small amount from almost every user; in-app purchases earn a large amount from a very small minority — and for most non-game utility apps, advertising is the more reliable of the two. The reason is conversion: typical in-app purchase conversion on a free app is around 1–3% of users, and in many utility categories well under 1%, so purchase revenue depends on a handful of paying users you may not have. Advertising monetises the other 97% at a low but predictable rate. The strongest apps combine them deliberately: ads as the default revenue floor, plus a paid “remove ads” or premium tier for the minority who dislike them, which converts precisely the users whose ad revenue you lose. Games are the exception where purchases can dominate, because the reward loop creates genuine willingness to pay.

ARPDAU is average revenue per daily active user — total daily revenue divided by daily active users — and the fastest ways to raise it are format mix, mediation and placement, in that order. It is the cleanest single measure of how well an app monetises, because it is independent of how many users you have. Improving it has a reliable sequence: add rewarded video at natural opt-in moments, since it carries several times a banner's eCPM; turn on mediation so networks compete per impression; move interstitials to genuine session or level boundaries where they do not interrupt a task; then tune eCPM floors by country rather than globally. Measure over a 30-day window, not a day — an aggressive change can lift ARPDAU for a week while quietly cutting retention, which reduces total revenue even as the per-user number improves.

A standard ad network keeps a mediation/platform cut and pays the rest to whoever owns the ad units, typically 60–80% to the publisher depending on the network and format. That share arrives from day one of live traffic, so a brand-new app with no installs earns close to nothing at first — the split is real but there is nothing yet to split. ConsoleMint's revenue-share model is structured differently because it is also the one paying for the app to be built and maintained: it pays a fixed monthly payout during the app's ramp-up months (while installs and ad revenue are still small), then converts to a performance-based share of ad revenue as the app matures, reviewed roughly every 45 days. The publishing partner is never asked to fund or wait out the ramp-up period unpaid.

There is no single benchmark because it depends entirely on country mix and ad format, but a rough planning range is $1–$5 of monthly ad revenue per 1,000 active installs for a US-heavy audience, and a fraction of that for India-heavy traffic. Revenue per install is a noisier metric than eCPM because it bundles retention, session frequency and ad format together — an install that opens the app once contributes almost nothing, while a daily active user with rewarded video exposure can be worth many times an average install. Use it only as a directional planning number, and track eCPM and ARPDAU for the metrics that actually diagnose a monetization problem.

By becoming a publishing partner for a company that builds and maintains the apps and monetizes them with ads — you supply the account, they supply the product and engineering work. Ownership of the account never changes hands: you grant scoped Developer-role access (not owner access), the partner publishes and updates apps under that access, and you're paid from the ad revenue the apps generate. This is different from selling or handing over an account, which is unsupported by Google and irreversible. With ConsoleMint specifically, an account can carry up to 10 apps, and payouts move through a fixed-payout ramp-up phase into a revenue share as the apps mature — see the payout structure question below for the numbers.

Fixed payout is better while an app is new and unproven; revenue share is better once it has real installs and ad traffic — which is why the strongest structures use both, in sequence. A pure revenue-share deal from day one means the publishing partner is paid a percentage of nothing, because a brand-new app has no installs yet. A pure fixed-fee deal caps the upside once the app is genuinely earning. ConsoleMint's staged model exists to solve exactly this: a fixed monthly payout during the ramp-up phase while installs build, then a step up into a performance-based revenue share reviewed roughly every 45 days as ad revenue becomes real — so the partner is paid through the slow start and still keeps the uncapped upside later. Be wary of any offer that calls a revenue share “guaranteed regardless of performance” — a genuine share always moves with actual ad earnings.

Published rates run roughly ₹3–7 lakh a year, depending on account age, app count and install volume — older or organisation-type Play accounts earn faster because they reach install scale sooner. For an established or organisation account (registered before November 2023, or an org-type account), the rate is roughly ₹5,000–7,000 per app per year, because these accounts clear review and scale faster. For a newer personal account, payouts are staged: a fixed ₹8,000–10,000 a month in months 1–2 while apps ramp up, stepping through revenue-share bands of roughly ₹12,000–19,000 in months 3–5, ₹20,000–40,000 in months 6–8, and ₹50,000–80,000 in months 9–12 as installs and ad revenue mature. An account can carry up to 10 apps, and every stage after ramp-up is performance-driven — it moves with actual ad revenue, not a fixed promise.

Yes — ConsoleMint publishes USD-native payout terms alongside its India/INR rate card, so it works with international Google Play account holders, not only India-based partners. On USD-native surfaces, established accounts are paid $10 per app on go-live plus $10 per app transferred, and newer accounts receive a $20 one-time payment when the first app goes live (once, not per app, up to the 10-app ceiling), then $100 a month from that date, stepping up every 45 days on performance — mirroring the same fixed-payout-then-revenue-share structure used for INR partners.

Any Google Play developer account in good standing qualifies, but the payout structure differs by account age and type. Established or organisation-type accounts — registered before November 2023, or org-type accounts — earn a flat rate per app per year because they clear review and reach install scale faster. Newer personal accounts go through the staged model instead: a fixed monthly payout during ramp-up, then a revenue share that steps up roughly every 45 days as the apps mature. Either way, the account must be in good standing; a suspended or policy-flagged account isn't eligible.

Payouts are made between the 1st and 5th of each month, by UPI or bank transfer, with an earnings statement. The first payout depends on the phase: during ramp-up the partner receives a fixed monthly amount from the moment the first app goes live, and once the apps earn real ad revenue the payout moves to a revenue-share basis. The payment mechanics stay the same in both phases, so a partner can plan around a predictable monthly window rather than waiting for an ad network's own payment threshold. See fixed payout vs revenue share for how the two phases fit together.

Payouts are reviewed on a performance schedule roughly every 45 days, and step up as installs and ad revenue grow. The ramp-up phase is fixed; after that the payout converts into a share of the ad revenue the apps generate, so a bigger install base means a bigger payout with no cap. On USD-native terms the same 45-day cadence applies to the $100 monthly figure. Step-ups are performance-driven, which is why the later stages are described as ranges rather than promises.

Only the ramp-up payout is fixed; everything after it is performance-driven and not guaranteed. While a new app has too few installs to earn meaningful ad revenue, ConsoleMint carries that risk and pays a fixed monthly amount from the first app going live. Once the payout moves to a revenue share, it depends on installs and ad revenue, so it can rise — and is not promised to rise by any particular amount. Treat any offer that ignores app performance entirely with caution. For how the stages are structured, see app ad revenue share explained.

Newer personal accounts move through four stages from a fixed ₹8,000–10,000 a month up to ₹50,000–80,000 a month in the mature stage, while established or organisation accounts are paid ₹5,000–7,000 per app per year. For a newer personal account the stages are: months 1–2 ramp-up (fixed), ₹8,000–10,000 a month; months 3–5 early revenue share, ₹12,000–19,000; months 6–8 growing revenue share, ₹20,000–40,000; months 9–12 mature revenue share, ₹50,000–80,000. Established accounts — registered before November 2023, or organisation-type — are paid per app because they reach install scale faster. Across the book the annual range is roughly ₹3–7 lakh depending on account age, app count and install volume, and only the ramp-up stage is fixed.

ConsoleMint grows revenue by adding apps to the partner's account, up to the 10-app ceiling, and by letting installs on existing apps accumulate. As an account matures, ConsoleMint either publishes more apps to it or transfers apps across, so total ad revenue compounds without the partner needing a second account. On the payout side, the amount is reviewed roughly every 45 days and moves from the fixed ramp-up payout to a share of the ad revenue the apps generate, which is why more installs means a bigger payout. Later stages are performance-driven, so they rise with real results and are not guaranteed.

Because a brand-new app has almost no installs, so its ad revenue on day one is close to zero, and ConsoleMint chooses to carry that ramp-up risk instead of the partner. From the moment the first app goes live, the partner receives a fixed monthly payout (₹8,000–10,000 a month in months 1–2 for newer personal accounts), paid between the 1st and 5th by UPI or bank transfer. After ramp-up the payout converts to a share of real ad revenue. The fixed guarantee applies only to the ramp-up phase; later stages depend on how the apps perform.

ConsoleMint uses both, matched to the account: a flat per-app yearly fee for established or organisation accounts and a staged fixed-then-revenue-share payout for newer personal accounts. Established accounts (registered before November 2023, or organisation-type) are paid ₹5,000–7,000 per app per year, because they reach install scale faster. Newer personal accounts start on a fixed monthly payout and step up through revenue-share stages as installs grow. The across-the-book annual range is ₹3–7 lakh, depending on account age, app count and install volume, and only the ramp-up payout is fixed.