Server Side Rewarding

Providing incentives for app users is a great way of encouraging customer engagement with your app. With Rewarded Ads, incentives come in the form of in-app rewards that are offered to users in exchange for watching a video ad in full.

To enable Server Side Rewarding you must first integrate rewarded ads, for a detailed guide click on the relevant OS:

Initializing the SDK

When initializing the SDK, there are no changes to be taken into consideration. The rewarded ad completion itself triggers Server Side Rewarding. However, you must make sure the User ID is set before this action happens. It can be set before or after initialization of the SDK.

Setting the User ID

Implement according to the correct operating system to set the User ID.

Android iOS Unity

The User ID length must not exceed 256 characters. If it does, the Server Side Reward callback will not contain a User ID value.

If no User ID is set, the DT FairBid SDK uses:

  • The IDFV, for an iOS device.
  • The GAID, for an Android device.

Showing a Rewarded Ad

There is no change to consider when showing a rewarded ad since the callback is always triggered upon video completion.

You must make sure that the User ID is set to the value you are interested in before showing your rewarded ad.

Appending Custom Parameters

Use the code samples below to send extra parameters into your completion callback.

To do this, create an object with your custom parameters, which you pass using the show method.

The total length of characters in the custom parameters collection must not exceed 4096. If it does, an empty collection of custom parameters is sent.

Android iOS Unity
Map<String, String> customParameters = new HashMap<>();
customParameters.put("myCustomKey", "myCustomValue");
customParameters.put("anotherCustomKey", "anotherCustomValue");
RewardedOptions rewardedOptions = new RewardedOptions();
rewardedOptions.setCustomParameters(customParameters);"placementID", rewardedOptions, activity);

Configuring Endpoints in the Console

  1. Log in to your DT account
  2. You can configure the endpoint in the Callback URL under Configure Placement in the console
  3. Under Server Side Rewarding, click Edit Server to Server Callback. The Callback URL and Security Token are displayed
  4. Copy your security token. It is sent in each callback to enable you to validate that the response is coming from DT’s server
  5. Click Save


  • The Security token should be kept secret between your servers and DT's. Ensure that there is no possible way that any of your users can access it.
  • There is a significance to the order of the parameters in the Callback URL when computing the SHA1 hash of the request parameters.

Callback Structure and Behavior

DT calls your endpoint with the URL configured in the console.

Before performing the GET request with the URL, DT replaces the following macros with information related to the video completion event.

Parameter Mandatory Description
USER_ID Yes The ID of the user to be credited

The value of the SIG macro is the SHA1 Hash of the values of all parameters (including the customized params even if they are not configured in the callback URL) in the URL (alphabetically sorted by parameter name) and the Security token displayed in the UI.

For example, if the callback URL is:

('data' is the custom params in the project) and the security token in the UI is:


Then the string (URL Decoded) to be encrypted is: 

123456Get currencytest123456test1.00000012345678901234567891234567890123test123456abcdefgh

The SIG appears as:

AMOUNT Yes The amount of virtual currency the user is to be credited.
CURRENCY_NAME No The name of the virtual currency being rewarded as it appears in the console.
APP_ID No The Application ID as it appears in the console.
SESSION_ID No The unique transaction ID in the form of an int64. Use this to check whether the transaction has already been processed in your system.
TIMESTAMP No Indicates the time stamp when the completion event occurred.

Response Options

DT expects to receive a HTTP 200 response to indicate that the publisher has successfully processed the callback. If a HTTP 302 response is received, it is redirected a maximum of three times.

If the response is HTTP 400 or HTTP 401, DT does not retry that attempt. For any other response, DT continues to resend the callback at increasing intervals until it receives a HTTP 200 response or until the maximum 10 tries limit is reached.

DT's server decides whether the callback request was successful based on the HTTP status code of your response.

Callback Request Type Description
Response A successful callback must return an empty response and a HTTP 200 status code. This indicates to our servers that you have successfully processed the callback. Any other response is interpreted as an unsuccessful callback (see below).
Redirects DT’s servers follow HTTP redirects (status code 301 or 302), however, all redirect locations must be absolute URLs, as specified in the W3C standard.
Unsuccessful Callbacks If an error occurs on your side, you may send any status code other than HTTP 200 to indicate to our servers that the callback was not processed successfully.

Any response other than HTTP 200 causes our system to resend the callback up to 10 additional times with an exponentially increasing delay between each attempt.
Duplicates and Rejected Callbacks If you identify the callback request as a duplicate based on the SESSION_ID, or if you choose to reject the callback intentionally, we recommend you to send an HTTP 200 status code response. In this way, this indicates to us that the callback was processed and there is no need to resend it.


To ensure the security of your reward callbacks, our servers send a sig (signature) parameter to authenticate the event. We highly recommend you verify this on your end.

Whitelist DT IPs

If your server has restrictive security settings and/or is protected by a firewall, you may have to unblock DT’s servers’ IP addresses to receive callback requests.

The IP ranges and addresses that you must whitelist are provided below.

We have added a new list of IPs. They are due to come into effect over the next few months.

New DT IP Address Old DT IP Address  

Back to Top ⇧