Hello, we are integrating our game with Twitch Drops and after the very 1st drop campaign we have noticed that get-drops-entitlements API returns drops for users which have NOT linked their twitch account with game account.
Is it normal behavior? What should we do with such drops?
I can assume that this data can be used to grant rewards if user linked their account later.
But what if it will never happen? Will this drop-entitlements expire after some period of time? Or maybe we can mark it as fulfilled after reasonable period of time? And what period of time can be considered as reasonable? is it 14 days as mentioned in Claiming a Drop
Users could link later (months later) to get their drops. (or days after the period closes)
Often people will claim drops for games they don’t own yet and then buy the game during a steam sale later and then link their accounts for example. (if they can still get to the claim button in the UI)
IMO: Game Developer’s choice.
IMO: Conceptually you don’t have to mark it as fulfilled at all.
This is just for your own reference to say if you were using Twitch API as a source of what you have or have not processed internally.
A fulfilled/unfulflled drop doesn’t show any different to a viewer, it’s just for Twitch data tracking (probably) and your own ease of API use. Since you could catch up filter on “pending” drops if your eventsub consumer was down.
Thank you for so quick response!
Our initial plan was to use get-drops-entitlements API as safety-net to cover cases when eventsub webhook is unavailable.
But if there are no expiration for drop-entitlements then such drops will “pollute” the data we receiving from get-drops-entitlements API. Furthermore the amount of such “dangling” drops will be increased after each stream.
At the same time as I understand we have to support “late account linking” (when user links account after the stream) I have not found any specific numbers but some user-support articles mention “14 days” period.
Is it OK to just ignore all drop-entitlements older then 14 days?
And another one concern: at the 1st glance it looks like we violated our obligation to reward Drop-campaign participants but we can NOT reward users if they have not linked their accounts (as we simply have no information what game account to reward). Is it possible that such drop-entitlements will lead to penalties/complains from Twitch side?
As long as it’s documented in your drop help documentation and/or information presented about reward validatity sure.
You’ll likely still get support tickets from customers asking about where their drops are even after the 14 days.
But you can set whatever days you want a long as you documentat it to customers.
I’d potentially collect all drops rewarded into datablase so that I have logs and/or analtyics on the difference between claimed/unclaimed (outside of stats that Twitch provides)
So I would have the full history if I was designing such a system.
I don’t know
But I doubt it.
Schedule 3 of the Twitch Developer Agreement states:
c. Allow Linked Users who have achieved the Milestones to redeem Drops. This obligation shall exist so long as any Drops are able to be redeemed by the applicable users. You shall ensure that delivery of Drops to Linked Users are in accordance with your policies, and any applicable terms of service or official rules of your Drops Campaign (“Campaign Terms”).
So from my understanding (and I’m not a legal expert so I suggest you seek your own legal advice) Your obligations are to fulfil Drops Rewards for LINKED users, and then how/when that fulfilment happens has to be in accordance with policies that you set out for your campaign. There are no obligations from my reading of the agreement for unlinked users.
The FAQ sections of the Drops Documentation states:
How long do I need to support a user claiming a Drop and linking their account after claiming for fulfillment?
In most circumstances, developers are required to fulfill viewer rewards that claim and link their accounts at least 14 days from the campaign ending. For certain time sensitive campaigns, such as a limited time beta, this requirement may be waived.
Thank you @BarryCarlyon and @Dist for the responses!
One more question get-drops-entitlements API does not document any filters by date or sort fields.
From my observation it returns “fresh” drops first.
Do you have any information about this part?
Is it safe to assume that here we have sorting by “timestamp” (or “last_updated”) field in descending order?
In this case we will be able to avoid retrieval of too old data from Twitch (instead of retrieving all data from Twitch and filter it)
As the docs don’t specify an order, it’s not safe to assume that any particular order will always be returned as while it may currently seem like the most recent redemptions are first there’s no guarantee on that.
One thing I’d recommend is using the first=1000 param, as that endpoint supports returning 1000 results at a time so it should be quite quick to page though large numbers of results and then do anything filtering/sorting on your side.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.