Same transaction_id in different SSV callbacks

[Ben Liao]

Hello AdMob Team,

We have been using SSV callbacks to verify our users' rewarded ad interactions for a few months.

However within the last few weeks, we are seeing increased occurrences of different SSV callbacks that contain same transaction_id.

We think these callbacks are abnormal, and not just re-attempt/retried callbacks because:

1) the callbacks that contain the same transaction_id have different custom data

2) the interval between the callbacks that contain the same transaction_id are 2 to 3 weeks. According to the SSV guide, the re-attempts callbacks would be sent up to five times in one-second intervals.

Please look into this and let us know if there's any more info required from our side.

Thanks.

Regards,

Ben

[Ben Liao]

One possibility we think of is the scope of the uniqueness of transaction_id.

The guide of SSV states that transaction_id is an "Unique hex encoded identifier for each reward grant event generated by AdMob".

Perhaps it is only unique on a certain scope? e.g. unique on the same ad_network

Ben Liao於 2019年10月23日星期三 UTC+8下午4時03分12秒寫道：

[Mobile Ads SDK Forum Advisor Prod]

Hi Ben,

Thank you for reaching out to us. As per the documentation, the transaction_id should be a unique hex encoded identifier and it's odd that you are getting callbacks that contains the same transaction_id. With this, let me raise this concern to the rest of the team and get back to you the soonest they provide their feedback.

Regards,
Teejay Pimentel
Mobile Ads SDK Team

ref:_00D1U1174p._5001UKOCZy:ref

[Mobile Ads SDK Forum Advisor Prod]

Hey Ben, 
Are there any logs you can send us so we can pass this on to our engineering team?
Thanks.

Jon

ref:_00D1U1174p._5001UKOCZy:ref