Skip to main content

I am trying to keep track of which consumables have been awarded to the player and need to track it with a unique identifier for each purchase. In the Unity SDK, the StoreTransactions that I get in the CustomerInfo.NonSubscriptionsTransactions have a property called TransactionIdentifier. However, this does not match the transaction_id I see online in RevenueCats front end.

Question 1: Why does the TransactionIdentifier not match the tranaction_id that i see in RevenueCat online?

Question 2: Since I cannot access the tranaction_id in Unity, is the TransactionIdentifer that right way to uniquely track a consumable purchase and will this value persist for the lifetime of the user?

Hi ​@Jaime! Yes, the transactionIdentifier is the correct way to track consumption of consumable products. Instead of the dashboard, consider using RevenueCat's GET /subscribers endpoint instead. You can utilize RevenueCat's unique identifier, id, in the non-subscription object to track consumption of all your consumable products.

​@jeffrey_bunn ,

I am using the Unity C# sdk. The CustomerInfo for a nonsubscription transaction provides a transactionidentifier which does not match transaction_id in your dashboard.

Why don’t they match?

Let’s say that I keep an online database of all of the consumables that the user has been awarded in the app. If the user has an issue with not being awarded a consumable, now I can’t compare what is in my online database with the revenuecat dashboard to troubleshoot the issue and possibly send them a promo code to award the missing transaction. But without them matching, the transactionidentifier is useless in this situation and I will have to come up with a different way of matching the transactions. Time purchased might be a viable candidate but why don’t the transactionidentifier and transaction_id match?

 

 

​@Jaime We should probably improve the naming, as I understand your confusion. The transactionIdentifier from the SDK will correspond with the id returned from our GET /subscribers endpoint. So what you’ll want to do is save the transactionIdentifier from the SDK and call the API endpoint to verify, if desired.

The transaction_id in the dashboard is taken from a different place. For Google, for example, it corresponds to the Order ID from the Google Play Console (i.e., GPA.3423...).

For matching transactions, the API route is the way to go at this point rather than the dashboard.

Reply


Terms & ConditionsCookie settings