Server-to-Server Callback Settings

LevelPlay reward-based ad units support server-side events to notify you of rewards that must be granted to your users after successful ad completion events.

Note: You can also use client-side events to grant rewards to users after successful ad completion events.

Enable Server-to-Server Callbacks on the ironSource Platform

• Log in to your Unity LevelPlat account and navigate to the Apps section in the left sidebar.

•  From the list of apps, click the action button of the app that you want to enable server-to-server callback for and select Set S2S callback.

• On the Create S2S reward callback page fill in the necessary information to enable server-to-toserver callbacks.

1. • In the Callback URL field, construct the callback for LevelPlay to send you after a user performs an ad unit completion, for example:
     http://www.mysite.com/granting.php?appUserId=[USER_ID]&rewards=[REWARDS]&eventId=[EVENT_ID]&itemName=[ITEM_NAME

See the section below for which parameters are mandatory for server-to-server callbacks.

• Next, add the private key (optional). A private key is a string that is only known by you and LevelPlay, which adds an extra layer of protection.5. In the parameters section, click on the dropdown menu and select the optional parameters you want to include in the callback. Once you select the optional parameter, they will automatically appear in the callback URL. 
• In the Callback test section, enter the User ID and the Reward amount to test the callback. You also have the option to enter the optional fields (Application ID, Ad provider, Item name and Placement name) but are not required to test the callback. 

• Click Save and your callback will instantly be activated. You can confirm the status of the callback on the Apps page. We recommend testing the callback before saving. 

Mandatory Parameters

Mandatory parameters that must be included in your callback string:

1. [USER_ID]: The unique identifier of a user of your application. The system uses it to know which user to reward upon successful ad completion.
2. [REWARDS]: The number of credit units rewarded to the user.
3. [EVENT_ID]: A unique identifier of the completed event, generated by ironSource, so that you can verify that you have not already rewarded the user for the event.

Optional Parameters

Optional parameters that may be used if needed, for your own internal use:

1. [ITEM_NAME] – Virtual item name, in the case the reward is a virtual item rather than an in-game currency.
2. [APPLICATION_KEY] – ApplicationKey.
3. [PLACEMENT_NAME] – Placement name.
4. [AD_PROVIDER] – Relevant for Mediation integrations, and specifies the provider’s name (e.g Vungle).
5. [DELIVERY_TYPE] – This parameter specifies the ad unit from which the completion was reported. Possible values are Offerwall or Rewarded Video.
6. [MULTI_CREDIT_PROMO_MULTIPLIER] – For Offerwall only, this parameter specifies if this offer was delivered during a “multi credit promotion” and what the promotion value was. In the case of a 2X promotion, this parameter will return “2”. In the case of a 2.5X promotion, this parameter will return “2.5”. In the case where there was no promotion active, this parameter will return “1”.

Signature Validation with Private Key

Your signature represents a MD5 of the following:  md5([TIMESTAMP][EVENTID][USER_ID][REWARDS][PRIVATE_KEY]). The private key is a string known only by you and ironSource, while all other signature components are part of the URL.  The private key is thus added for additional security as it makes the signature harder to reproduce. If you’d like to use this extra layer of security, enter a private key to be sent along with the callback URL.