> 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
### What are share rewards?
Share rewards is a feature that uses the contacts module to load the contacts of Toss users and provides rewards to users who complete sharing. Sharing is carried out through Toss notification pushes.
Share 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 share rewards
* You can naturally drive traffic by linking rewards to friend invitations.
* By encouraging sharing based on rewards, you can gain marketing effects without additional costs.
* 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 share rewards resets on a daily basis.
* Based on a single reward ID, you can send a share reward to one user only once per day.
* For example, if you send a share reward to User A today with a certain reward ID, you can send it again tomorrow with the same reward ID.
* If you use a different reward ID, the sending limit is applied independently for each one.
{% hint style="info" %}
**Please make sure to note**
* Please avoid excessive pop-ups or forcing users to share.
* Please make sure the conditions for receiving rewards are explained accurately so users can easily understand them.
* Cash-equivalent rewards or gambling-related rewards cannot be registered.
{% endhint %}
***
### Set up in the console
Select 'Share rewards' from the left menu in the App in Toss console.
**Reward name**
This is the reward name that an administrator will use to distinguish it internally. Please choose a name that is easy to identify in the operations screen or during settlement. It may differ from the message shown to users, so it's best to be specific according to your operational purpose.
* Example: 100 hearts for attendance check reward / gems for friend invitation event / welcome reward for new sign-ups
**Reward screen**
Enter the reward information that will actually be given to users.
* Reward: Enter the unit of the reward to be given. Please specify the reward name that users recognize, such as hearts, gems, or points.
* Quantity and amount: This is the quantity of the reward to be given to users. Please enter the exact quantity and amount that match the event or policy. For example, to give 100 hearts, enter 100 for the quantity.
***
### Developer integration
Share rewards [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.