> 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/analytics/conversion-metrics.md). # Key Metrics ### Why set key metrics * Exposure and recommendation optimization: Find users similar to active users, and show and recommend our app to users who are likely to like it. * Performance analysis: You can check not just one-time visits, but how much the number of users who actually return frequently is increasing. * Operations and improvement: It also serves as a shared standard within partner companies for agreeing on what the key metrics are. *** ### Set it up in the console Please select Appintoss Console → Select Workspace → Select Mini App → Left menu 'Key Metrics'.
#### Active metrics Active metrics are the criteria used to define users who frequently use my app. You can set only one per app. Active metrics are used like this. * Exposure and recommendation: Toss finds users similar to active users, and shows and recommends our app to users who are likely to like it. * Performance analysis: You can check not just one-time visits, but how much the number of users who actually return frequently is increasing. **1) Choose a template** You can choose from three templates. After selecting one, enter the desired values and register immediately. **2) Combine manually** If there is no template you want, you can set a custom event as an active metric. * Metric name: Please write it so that the team can tell what the metric is. * Description: Please write a short description so the metric can be understood at a glance. * You can combine events with OR conditions and define parameters as well. #### Conversion metrics Conversion metrics are the criteria used to define the user actions you want to focus on most in the mini app (core target actions). Rather than simply opening the app or viewing screens, it is better to set moments that are closer to the service goal—such as completing sign-up, completing the first payment, or consuming core content—as conversions. You can register up to three conversion metrics. **1) Choose a template** Toss team has created templates for commonly used metrics. You can register them right away by simply selecting one. **2) Combine manually** * Metric name: Please write it so that the team can tell which conversion it is. * Description: Please write a short description so the metric can be understood at a glance. * You can combine events with OR conditions and define parameters as well. If there is no template you want, you can select 'I don't see the metric I want' below the list and request the metric you need from the Toss team.
TemplateDescription
Users with revenueThese are users who generated revenue through one or more of in-app ads, in-app purchases, or Toss Pay.
Users who paid with Toss PayThese are users who completed payment with Toss Pay.
Users who purchased in-app itemsThese are users who paid for in-app items.
Users who watched in-app adsThese are users who watched in-app ads at least once.
Average revenue per user (ARPU)This is the average amount of revenue divided by the number of users.
Average order value (AOV)This is the average amount per payment.
Users who completed Toss LoginThese are users who completed login with a Toss account.
Users who received a user identification keyThese are users who received a user identification key without a separate server.
Users who completed a game playThese are users who completed a game at least once.
Users who agreed to receive notificationsThese are users who agreed to receive notifications sent by the mini app.
Users who entered through a specific pathThese are users who entered the mini app through a specific path.
**Primary conversions and secondary conversions** Among conversion metrics, only one primary conversion can be set. * Primary conversion: This is the conversion that has the highest priority in this mini app. It becomes the default metric used for optimization such as exposure and recommendation, as well as for analysis. * Other conversions: These are metrics used to view the process leading up to the primary conversion. For example, if the primary conversion is payment completion, you can set adding to cart or attempting payment as secondary conversions to see at which stage users drop off. The first conversion metric you create is automatically set as the primary conversion. If you want to change it, you can select another conversion metric and check it as the primary conversion. {% hint style="warning" %} **Please be sure to check** * The changed metric will be applied starting tomorrow. * Key metrics are used as the basis for exposure, recommendation, and performance analysis, so please set them carefully. {% endhint %} *** ### View metrics You can view the registered key metrics as charts on the list screen. * You can query the data by selecting the date range and time unit at the top (daily, weekly, monthly). * Active metrics show the number of active users, and conversion metrics show the number of converted users.
--- # 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/analytics/conversion-metrics.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.