> 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 Key metrics are the criteria for defining a mini app's active users and core goal actions. Based on these metrics, we find, expose, and recommend users who are likely to like our app. The better you set your key metrics, the greater the chance your app has of being shown to more suitable users. ### Why set key metrics * Exposure and recommendation optimization: Find users similar to active users, and expose 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 standard for internal agreement within partner companies on “what the key metrics are.” *** ### Set up in the console Apps in Toss Console → Select workspace → Select mini app → Select 'Key Metrics' from the left menu.

#### Active metrics Active metrics are the criteria for defining users who use my app frequently. You can set only one per app. Active metrics are used like this. * Exposure and recommendation: Toss finds users similar to active users and exposes 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 3 templates. After selecting one, enter the desired values and register it right away. **2) Build it yourself** If there is no template you want, you can set a custom event as an active metric. * Metric name: Write it so the team can distinguish it and see what metric it is. * Description: 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 for defining the user actions you most want to track in a mini app (core goal actions). Rather than simply launching the app or viewing screens, it’s better to use as conversions the moments that are closer to the service’s purpose (e.g. completing signup, completing the first payment, consuming core content, etc.). You can register up to 3 conversion metrics. **1) Choose a template** The Toss team has prepared commonly used metrics as templates. You can register them right away by simply selecting one. **2) Build it yourself** * Metric name: Write it so the team can distinguish it and see what conversion it is. * Description: 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 'There is no metric I want' below the list and request the needed metric from the Toss team.

Templates	Description
Users who generated revenue	Users who generated revenue through one or more of in-app ads, in-app purchases, or Toss Pay
Users who paid with Toss Pay	Users who completed payment with Toss Pay
Users who purchased in-app items	Users who paid for in-app items
Users who watched in-app ads	Users who watched in-app ads at least once
Average revenue per user (ARPU)	The average amount of revenue divided by the number of users
Average order value per transaction (AOV)	The average amount per payment transaction
Users who completed Toss Login	Users who completed login with a Toss account
Users who received a user identification key	Users who received a user identification key without a separate server
Users who completed game play	Users who completed a game at least once
Users who agreed to receive notifications	Users who agreed to receive notifications sent by the mini app
Users who came in through a specific path	Users who entered the mini app through a specific path

**Primary conversions and secondary conversions** Among conversion metrics, you can have only one primary conversion. * Primary conversion: The conversion this mini app prioritizes the most. It becomes the default metric used for optimization and analysis such as exposure and recommendation. * Other conversions: Metrics used to view the process leading up to the primary conversion together. For example, if the primary conversion is payment completion, you can set add to cart and payment attempt 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 the next day. * Key metrics are used as the basis for exposure, recommendation, and performance analysis, so please set them carefully. {% endhint %} *** ### Check metrics You can view the registered key metrics as charts on the list screen. * You can view 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.