Glossary #
General #
Publisher – the person who owns the Telegram Mini App and wants to monetize their Telegram audience using Monetag.
CPM (Cost per mille) – the cost for 1,000 impressions of an ad.
Average CPM – the average CPM across all Monetag publishers. It varies depending on country, format, and traffic quality.
Skin – a visual theme or template applied to the appearance of an ad (mainly used in some interstitial formats).
Format – a type of ad integration. Monetag supports:
- Rewarded Interstitial
- Rewarded Popup
- In-App Interstitial
Stats #
Country – the country where the user saw the ad. This is determined by their IP address and shown in your statistics.
Impression – one successful ad display in the app.
Zone – a configured ad placement in the Monetag system. Each SDK integration starts with a main zone, which may link to sub-zones depending on format.
Zone ID – the numeric identifier of the zone. Developers must use the main zone ID when integrating the SDK.
SDK Terminology #
Main Zone – the primary ad zone connected to the SDK. All SDK scripts and createAdHandler()
calls must reference this ID.
Sub-Zone – a linked zone used internally by the platform (e.g., for specific ad formats like Rewarded Popup). Developers should not use sub-zone IDs in the SDK.
SDK – Monetag’s JavaScript library that controls ad display logic, tracks events, and handles formatting. It works with both <script>
tag and npm package.
show_XXX – the global method created by the SDK (via data-sdk="show_XXX"
). Developers use it to trigger ads. The suffix XXX
is replaced by the zone ID.
ymid – an optional identifier passed to show_XXX()
to help track ad events. It can be a user ID, session ID, or custom value and appears in the postback.
requestVar – an optional value passed to the SDK to differentiate between placements (e.g. button A vs. button B). It appears in your analytics, not in postbacks.
preload – a special mode that loads the ad in advance, improving display speed. Triggered via show_XXX({ type: 'preload' })
.
pop – a mode that opens a new tab or browser window with an ad. Used in Rewarded Popup via show_XXX({ type: 'pop' })
.
inApp – a mode for In-App Interstitials that configures auto-showing ads in the background. Called with show_XXX({ type: 'inApp', inAppSettings: {...} })
.
data-auto – an HTML attribute used in the <script>
tag to configure automatic In-App Interstitials without writing JS logic.
Monetag SDK npm package – official SDK for modern front-end frameworks. Installable via:
npm install monetag-tg-sdk --save
createAdHandler() – a function provided by the SDK npm package. It returns a handler that behaves like show_XXX()
.
Telegram Web App API – Telegram’s JavaScript interface that enables the Mini App environment to access Telegram user data. Required for automatic Telegram ID detection.
Postback – a server-to-server callback that notifies Monetag (and optionally the publisher) that a monetizable event occurred.
Integration Behaviors #
Promise – all SDK ad calls return a Promise. It resolves when the ad is completed (for Rewarded Interstitial), or when the action is triggered (for Popup). Use .catch()
to handle errors.
Auto-Session Logic – in In-App Interstitials, ads are shown automatically based on frequency, session length, and interval — all of which are configured either via JS or data-auto
.
Main SDK Script – a single, lightweight file that powers all formats. Include only once per page or app.
Fallback – custom logic that runs if the ad fails (e.g. show other content or a message).
Popup Blocking – Rewarded Popup requires a direct user gesture (like a click
) or it will be blocked by the browser.