> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/guide/en/monetization/in-app-ad.md). # In-app Ads ### What is in-app advertising? In-app ads are advertisements shown to users inside the app screen. They appear naturally without disrupting the service flow, and generate revenue from those impressions. Ad revenue is determined by two factors. * How many times it was shown **(impressions)** * How much is earned per view **(eCPM)**
Impressions This is the number of times an ad actually appears on the user's screen. The more impressions, the more revenue opportunities there are, but too many can hurt the user experience.
eCPM This is the revenue per 1,000 ad impressions. The higher it is, the greater the revenue, and it is affected by ad type and user attention. The more focused users are, the greater the ad effectiveness and the higher the unit price; if attention is low, the unit price goes down.
Multiply these two to get estimated revenue. `Estimated revenue = impressions × eCPM ÷ 1,000` For example, if ads were shown 100,000 times today and the eCPM was 5,000 won, then 100,000 × 5,000 ÷ 1,000 = 500,000 won. *** ### In-app ad types It is most effective to use the three ad types below together. Using them in combination rather than just one can significantly increase overall revenue. #### Interstitial ads These are full-screen ads shown at screen transitions. * Feature: forced exposure (users must see it) * Recommended placement: right before or after a screen transition (e.g., from a results screen to the next step) * Impressions: medium * eCPM: medium * Suitable situations: points where the flow pauses (level complete, reservation complete, etc.), moments when users naturally stop
#### Reward ads These are ads played when the user voluntarily chooses 'Watch ad'. * Feature: voluntary viewing, high engagement * Recommended placement: when a reward is needed (e.g., extra benefits, continue) * Impressions: low * eCPM: highest * Suitable situations: point rewards, additional feature access, structures like 'watch an ad to get benefits'
#### Banner ads These are ads fixed at the top or bottom of the screen and shown continuously. * Feature: always visible (traffic accumulates automatically) * Recommended placement: main screen, list screen * Impressions: highest * eCPM: lowest * Suitable situations: screens with long usage time, screens revisited repeatedly
*** ### Benefits of in-app ads * You can choose interstitial, reward, and banner ads and display them in places that fit the service flow. * Ad revenue starts from the first day of app launch, so monetization can begin right away. * Ads can encourage users to keep using the service, increasing retention. * In game services, 'watch an ad to continue' can get users to keep playing the stage they were attempting, naturally encouraging re-use. *** ### Set it up in the console #### 1. Register business information To integrate in-app ads, you must first register your business information. Business information must be registered before you can proceed to the next steps: agreeing to the terms and entering settlement information. The registration method is [guide](https://developers-apps-in-toss.toss.im/prepare/register-business.html)for details. #### 2. Enter settlement information When you integrate in-app ads, ad revenue is generated. To receive settlements for that revenue, you must [register settlement information](https://developers-apps-in-toss.toss.im/guide/settlement)Please enter the settlement information in the 'Info' tab of your workspace, then request review. Review usually takes 2 to 3 business days on average. {% hint style="warning" %} **Please be sure to check** Please enter the account holder name exactly as written on the copy of the bankbook, without changing even a single character. If it is entered differently, settlement may be delayed. {% endhint %} #### 3. Create an ad group Appintos in-app ads follow Google AdMob ad policies. If you do not comply with the policies, ads may be restricted or suspended.
**3-1. Ad group name** It is easier to manage if you include both the ad type and placement. Since you will need to manage multiple ad groups during operations, please name them so they are immediately understandable later. * Ex) main\_interstitial, gameover\_rewardad **3-2. Ad type** **Banner** * An ad that stays visible at the top or bottom of the screen. * It accumulates automatically while the app is being used, creating steady revenue. * However, once users get used to it, they stop noticing it easily, so the unit price is the lowest. **Interstitial** * An ad that appears full-screen at the moment of a screen transition. * Because users cannot ignore it, the unit price is higher than banners. * It feels natural when placed at moments when the flow is interrupted, such as level clears or content transitions. **Reward** * An ad that starts only when the user directly taps 'Watch ad'. * Because users watch it all the way through to receive the reward, the unit price is the highest. * It is effective when linked to moments that benefit the user, such as giving points or items. **3-3. Reward** Enter this only when Reward Ads are selected. Please enter the exact reward name and quantity that users actually receive. Since this is shown on the user's screen, it is best to use the same terminology as in the service. * Ex) Service reward unit: chance / quantity and amount: 1 **3-4. Mediation** Mediation is a technology that connects multiple ad networks and automatically selects, in real time, the ad with the highest revenue. The ad networks matching the category registered in 'App Info' are set automatically. You can switch to another category, but the changed category will not be reflected in app info and applies only when creating an ad group. After registration, you can check the ad group ID on the detail screen. * It may take up to 2 hours for the ad group ID to be registered with Google. * Please develop using the ad group ID provided after creating the ad group. *** ### Ad operation policy #### Toss Ads SSP policy Please make sure to follow the policy below. Violations may restrict ad impressions. Even if it is not written in this policy, **acts that artificially induce ad impressions, clicks, or performance, or mislead users, may be considered policy violations.** If the service is terminated due to a policy violation, all partners must comply with the service termination policy. | Type | Prohibited action | Specific example | Policy standard | | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Degradation of UI/UX quality | Actions that make the distinction between ads and content unclear, induce users to consume or click ads unrelated to their intent, or configure the UI to interfere with normal service use |

|

| | Modifying ad call behavior | Changing or bypassing the SDK's default event flow or ad call method | |

| | Abnormal traffic and performance manipulation | Acts that distort traffic and ad performance through automation or artificial means | | | | Reward-based / participation-based click inducement | Providing rewards or benefits at the same time as an ad click | | | | Hiding or overlapping ads | Acts of intentionally hiding ads or covering them with other UI elements so users cannot clearly recognize the existence of the ads |

• Transparent ads

• Inserting ad DOM behind another card UI

| • The ad must be clearly visible as exposed | #### UX / Product Principle operating principles Ads must also follow Toss's UX principles. | **Toss Principle** | **Application standard** | **example** | | ------------------------------ | --------------------------------------------------------------------------------------------- | ---------------------------------------------------- | | **Simplicity** | Ads must be clear and understandable without additional explanation | Clear CTA such as "View now" or "Watch ad" | | **Clear Action** | Users should be able to predict what will happen after clicking the ad | Provide notice when moving externally | | **No Deception (UX Red Rule)** | Ads must not appear at unexpected moments, in unexpected forms or locations, or mislead users | When ads are disguised as content | | **Value First** | Ads must not interfere with the customer's service goals | No ad insertion during payment/account opening flows | #### Usage restrictions and sanctions If the Appintos ad inventory or service violates this policy, it may be sanctioned. **Restriction procedure** In principle, restrictions are applied step by step according to the accumulation of violations. Depending on the type or severity of the violation, a single violation may result in an immediate 30-day restriction or a permanent restriction. ※ Violations confirmed at the same time are treated as one violation regardless of the number of violation slots. If violations are confirmed separately later, the number of violations will accumulate.
**Handling of improper revenue** Revenue generated through policy violations, invalid traffic, or other improper means may be considered improper revenue. If improper revenue is identified, payment of that amount may be withheld or denied. Amounts already paid may also be recovered. **Appeal process** * If you receive a notice of restriction, **you can file an appeal within 30 days**. * Appeal materials can be submitted via Channel Talk. * The submitted materials will be reviewed according to internal standards, and additional materials may be requested if necessary. * Review may take about one week in business days. * Appeals are **reviewed mainly based on whether the sanction was appropriate**. The sanction will not be lifted just because the violation has been corrected or a recurrence prevention plan has been submitted. * If the submitted materials do not 인정? Actually translate: if the violation facts that formed the basis for the sanction are not substantiated, or if there is a clear error in the sanction decision, the sanction may be lifted. * Repeated or serious violations may result in permanent restriction from using the service. *** ### Integrate development Please make sure users are not shown ads too frequently. For in-app ad testing, you must use test IDs. Using production IDs may result in sanctions. Please make the app sound pause temporarily while the ad is playing, and automatically resume after the ad ends. [Interstitial/Reward ads Interstitial/reward ad load and display API and SDK integration method](/documentation/api-and-sdk-en/common/monetization/iaa/interstitial-rewarded-ad.md) [Banner ads (WebView) WebView banner ad SDK initialization, attachment, and event callback API](/documentation/api-and-sdk-en/common/monetization/iaa/web-banner.md) [Banner ads (React Native) How to use the React Native banner ad InlineAd component](/documentation/api-and-sdk-en/common/monetization/iaa/rn-banner.md) *** ### Check ad performance and settlement details You can check the items below by selecting a period and operating system (OS). * Total ad impressions, eCPM, total estimated revenue * Performance data is updated every day at 10:00 AM.
**Settlement details** * Revenue from the 1st to the last day of each month is updated on the 1st of the following month. * Confirmed revenue on the 1st of the following month is deposited on the last day of that month. The settlement structure is [guide](https://developers-apps-in-toss.toss.im/guide/settlement#id-1)for details. *** ### Analyze ads You can check whether the ads in my mini app are being displayed correctly, and see trends in ad frequency and eCPM. Use the data to check whether you are showing too many ads and which ad types are most effective for revenue. {% hint style="info" %} **Please note** To see actual data in the analytics tab, you need to update to SDK 2.7.0 or later. Data accumulates only after the SDK update, so please update the SDK first. {% endhint %} #### Ad impression status You can see how far ads reach through each stage, from request to impression.
| Stage | Description | | ------------------ | ---------------------------------------------------------------------------------------- | | Ad request | The number of times the app requested an ad from the ad server. | | Ad received | The number of times the ad was successfully received from the ad server. | | Impression attempt | The number of times an attempt was made to display the received ad on the user's screen. | | Impression success | The number of times the ad was actually shown on the user's screen. | {% hint style="info" %} **How to use this** * If ad reception is low compared to ad requests: there may be insufficient ads to fill the ad network (No Fill). * If impression attempts are low compared to ad reception: the ad was received but not actually shown. `load`and `show` Please check the timing of the call. * If impression success is low compared to attempts: there is a failure in the rendering process. Please check the SDK version or call order. {% endhint %} #### Ad impression frequency and eCPM You can check the impression frequency and eCPM trends by ad type (banner, interstitial, reward) together. * Bar graph (left Y-axis): average daily ad impressions per user (by ad type) * Line graph (right Y-axis): eCPM (in won)
{% hint style="info" %} **How to use this** * If impressions increased but eCPM dropped, ad fatigue may be the cause. * If reward ad eCPM is higher than other types, it may be a good idea to increase the share of reward ads. * If you turn on 'View by OS,' you can check performance differences between iOS and Android. {% endhint %} #### Ad impression share and eCPM You can check the share of ad impressions relative to app usage time and the eCPM trend together. * Bar graph (left Y-axis): impression share by ad type (%) * Line graph (right Y-axis): eCPM (in won)
{% hint style="info" %} **How to use this** * Ad impression share is the ratio of ad display time to total time spent. * If the ad share is too high, the user experience may worsen and churn may increase. * If there is an ad type with low eCPM relative to its share, reduce its placement and switch to a type with higher eCPM. * Usually, reward ads have a high eCPM even with a low share, while banner ads have a low eCPM even with a high share. * Banner ads are not yet supported. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developers-apps-in-toss.toss.im/guide/en/monetization/in-app-ad.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.