Telegram Mini App Ad Frequency: Revenue and Retention
The right ad frequency for a Telegram Mini App depends on when users see an ad, what they receive and whether they return. Start with deliberate placements and measured limits, then test revenue and retention together. GigaPub is an ad network and ad-mediation platform for Telegram Mini Apps. This guide explains how to design your app's frequency rules without treating more ad requests as a guaranteed increase in revenue.
Key takeaways
- Offer rewarded ads at a clear moment of value and interstitials at natural pauses.
- Define both a cooldown between ads and a cap over a session or day.
- Apply product limits across placements so several screens do not overwhelm the same user.
- Judge experiments using revenue and returning users, not eCPM alone.
Why can more ad impressions reduce long-term revenue?
More impressions can increase today's ad revenue, but only while users continue to use the app. An interruption before the first useful action or repeated prompts during a short session can make the product less appealing. The size of that effect depends on the app and needs measurement.
Ad ARPDAU is daily ad revenue divided by daily active users. It can also be written as impressions per DAU multiplied by eCPM and divided by 1,000, using the same period and revenue basis.
That daily metric does not tell you whether a frequency change causes fewer users to return. A smaller group of heavy users can generate higher ARPDAU while cumulative revenue from the original audience declines. Track monetization metrics alongside cohort retention to see both effects.
Where should rewarded and interstitial ads appear?
Rewarded ads fit a voluntary exchange with a visible benefit. Interstitial ads fit a completed action and a natural break. Decide the placement before choosing its frequency.
| Placement | User expectation | Suggested product rule |
|---|---|---|
| Extra attempt after a round | Choose an optional way to continue | Explain the benefit and allow one request at a time |
| Optional bonus in a shop | Choose whether the reward is worth the ad | Display the reward and remaining eligibility clearly |
| Break between completed rounds | Continue after a finished action | Apply a cooldown and a shared interstitial cap |
| First visit before the core experience | Understand what the app does | Let the user reach the product's value before testing interruptions |
| Return from an advertiser or external page | Resume the previous activity | Avoid immediately triggering another full-screen ad |
These are starting hypotheses for product design, not universal performance benchmarks. A fast puzzle game and a utility app with short visits need different rules. See the rewarded video and interstitial comparison for the roles of each format.
For rewarded ads, describe the benefit before the user opts in. Keep declining possible and grant the reward through the supported completion flow. Do not make a button promise an ad or reward before availability has been established.
What is the difference between a frequency cap and a cooldown?
A frequency cap limits the number of ads a user can see within a defined period. A cooldown sets the minimum interval before another ad may appear. Use both when the product needs to prevent a short burst as well as excessive total exposure.
Define what counts toward each limit: successful displays, accepted attempts or both. You may need a separate short cooldown for failed attempts so repeated taps do not create a request loop. A failed load should not be recorded as a completed rewarded view.
Decide whether limits are per placement, per format or shared across the app. If the home screen, shop and game each allow an interstitial independently, users can receive several interruptions in quick succession despite each screen following its own rule.
For cross-session or cross-device limits, use authenticated server-side state appropriate to your product. Browser storage alone can be reset and should not be the sole authority for valuable rewards. These are app-level design choices; they are not additional parameters to window.showGiga().
How should you test an increase in ad frequency?
Change one rule at a time and compare stable groups of users. For example, keep the reward and placements the same while testing a different cooldown. If you change the reward, entry point and frequency together, the result will not tell you which change mattered.
Assign users consistently to a control and a test group. Keep country mix, acquisition source and platform comparable, and avoid judging a short experiment from one unusually strong day of advertiser demand.
Measure accepted attempts, successful displays, failures, time to display, rewarded completions where available, and ad revenue. Add product metrics: completed core actions, session behavior and D1/D7 retention. Define retention consistently; for example, D1 is the share of a signup cohort active the following day, and D7 is the share active on the seventh day.
For the business result, compare cumulative revenue over the same observation window per user originally assigned to each group. Include relevant purchase revenue if ads could affect it. This helps catch a treatment that earns more from surviving users but loses more of the original audience.
Choose your acceptable retention and reliability limits before the experiment starts. Wait until the retention windows you intend to evaluate have matured, and consider sample size and uncertainty before calling a small difference a win. There is no defensible universal cap or test duration for every Mini App.
How do you handle no fill without making the experience worse?
Restore the interface and let the user continue. Do not silently turn a failed rewarded attempt into a forced interstitial or keep retrying until an ad appears.
Use a clear availability message and a pause before another attempt. If you offer a different task or bonus, describe it as a separate choice with its own conditions. Our guide to ads not showing explains how to separate SDK errors from no fill.
Measure waiting time as well as the number of successful ads. A placement that eventually shows an ad after a long delay can still make a short session frustrating.
What does GigaPub handle, and what should your app control?
GigaPub provides ad delivery through its SDK and ad mediation. Your app should decide when to offer an ad, explain a reward, prevent simultaneous attempts and restore its interface after the result. Demand sources can also impose their own eligibility and frequency restrictions.
Follow the current SDK integration guide for loading and showing ads. Keep your product's cooldown and cap logic around that integration. Adding a frequency rule should not require inventing undocumented SDK options.
Start with a placement you can explain to a user in one sentence. Connect it through the GigaPub publisher dashboard, measure the complete flow and expand only when the revenue and product data support the change.
What are the most common questions about ad frequency?
How often should a Telegram Mini App show ads?
There is no universal number. Start with a small set of deliberate placements, use cooldowns and per-user limits, and adjust frequency using revenue, completion and retention data from comparable cohorts.
What is an ad frequency cap?
A frequency cap limits how many ads a user can see within a defined period, such as a session or day. A cooldown limits how soon the next ad may appear. Both need clear rules across all placements.
Where should rewarded ads appear?
Offer rewarded ads when a user can choose a clear benefit, such as an extra attempt or optional bonus. Explain the reward before the tap, preserve the choice to decline and handle unavailable ads gracefully.
Does a higher eCPM prove that a frequency change worked?
No. Evaluate ad revenue per active user, retention and cumulative revenue per user assigned to the experiment. A higher eCPM can coexist with fewer returning users or fewer total impressions.
Does GigaPub replace the app's frequency rules?
Your app should control its own placement timing, loading state and product limits. GigaPub provides ad delivery through its SDK and mediation; provider-side limits may also affect availability.