> 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/marketing/share-reward.md).
# Share rewards
By introducing Apps in Toss's share rewards feature, create a natural viral virtuous cycle that leads from inviting existing users to new user acquisition, revisits, and reshares.
### What is a sharing reward?
Sharing rewards is a feature that uses the contacts module to import the contacts of Toss users and provides rewards to users who complete sharing. Sharing is carried out via Toss notification push.
Sharing rewards can be used for both game services and non-game services. The push message shown to users varies depending on the service type.
***
### Benefits of sharing rewards
* By linking rewards to friend invitations, you can naturally drive traffic.
* By encouraging sharing based on rewards, you can achieve marketing effects without additional cost.
* You can encourage repeat visits by providing currency that can only be used within the service.
***
### Sending limits and reset criteria
The sending limit for sharing rewards resets daily.
* Based on a single reward ID, you can send a sharing reward to one user only once per day.
* For example, if you sent a sharing reward to User A today with a specific reward ID, you can send it again tomorrow with the same reward ID.
* If you use a different reward ID, the sending limit is also calculated separately for each reward ID.
{% hint style="info" %}
**Please note**
* Please avoid excessive pop-ups or coercive sharing prompts.
* Please explain the conditions for receiving rewards accurately so users can easily understand them.
* Cash-equivalent rewards or gambling-related rewards cannot be registered.
{% endhint %}
***
### Set up in the console
In the left menu of the Apps in Toss console, please select 'Sharing Reward'.
**Reward name**
This is the reward name the administrator will use internally to distinguish it. Please choose a name that is easy to identify in the operations screen or during settlement. It may differ from the text shown to users, so it’s best to write it specifically according to your operational purpose.
* Example) attendance check reward 100 hearts / friend invitation event gem payout / new signup welcome reward
**Reward screen**
Enter the reward information that will actually be given to users.
* Reward: Enter the unit of reward to be granted. Please enter the reward name users recognize, such as hearts, gems, or points.
* Quantity and amount: This is the amount of reward to be given to users. Please enter the exact quantity and amount according to the event or policy. For example, to give 100 hearts, enter 100 in the quantity field.
***
### Integrate with development
Sharing reward [SDK integration method and event handling code examples](https://developers-apps-in-toss.toss.im/documentation/common/growth/share/reward)You can check it.
---
# 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/marketing/share-reward.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.
.png?alt=media&token=1ac7828e-63e3-4458-91d6-38c7433a0a46)