Subscription Loyalty Program
This feature is a new opportunity for game developers – the ability to know if a player is a Nutaku Subscriber.
Our primary aim with this initiative is to forge mutually beneficial partnerships that will benefit the game developers.
Subscribers are vastly more inclined to allocate funds towards their gaming experiences, leading to heightened revenue opportunities for developers.
Subscribers are also more active players, having a community of active Nutaku subscribers playing the game will boost earnings longevity.
In-game, you may want to give Nutaku Subscribers certain benefits. Some examples: special item pricing, special rewards received after each in-game purchase, battle pass style systems (or extra rewards for subscribers on top of regular battle pass rewards), in-game calendar bonuses, in-game store exclusive items for subscribers, bonus retries in minigames.
Sometime in the future, the Nutaku platform may add a dedicated system on the platform which would highlight games that offer benefits to subscribers.
Note: if your game is not actively making use of this feature, we kindly ask that you do NOT request this field value from our servers. You can always integrate this field at a later time when you will have use cases implemented for the feature. Until then, there is no need to add processing times to API calls if they are not actively used.
How to query if the user has an active Nutaku Subscription?
This is done by requesting the “activeSub” field from People API, similar how the user id or nickname are obtained. This field is not served automatically, it must be specifically requested.
Please be aware that our Sandbox environment does not have a Subscription concept, so the field won’t actually be returned in the response.
For SP and DL games, add it to the fields parameter when making the OSAPI request:
Example:
/social_sp/rest/people/123/@self?xoauth_requestor_id=123&fields=id,nickname,userType,activeSub
For PC browser (and SP with Mobile platform unification enabled), add it to the array of requested fields (as a raw string):
var params = {};
params[opensocial.DataRequest.PeopleRequestFields.PROFILE_DETAILS] = [
nutaku.Person.Field.USER_TYPE,
nutaku.Person.Field.GRADE,
opensocial.Person.Field.NICKNAME,
'activeSub'
];
var req = opensocial.newDataRequest();
req.add(req.newFetchPersonRequest(opensocial.IdSpec.PersonId.VIEWER, params), "viewer");
For APK:
Native variant: use NutakuApi.requestProfileAndActiveSub() - see sample app code.
Unity variant: use RestApiHelper.GetMyProfileAndSub(this, TestGetMyProfileAndSubCallback) - see code in our sample scene (or TestUIController.cs).
How to interpret the activeSub parameter value?
If the activeSub returned field is missing entirely (sandbox), OR has null value, OR has empty string value OR comes as a “0”, you should treat this as not subscribed.
If the above condition is not met, the user has an active subscription.