1 / 9

WEBINAR Revenue validation

Join our informative webinar on revenue validation processes for mobile games, focusing on Apple App Store configurations. Discover how to integrate receipt validation using the deltaDNA platform and enhance your game's revenue tracking capabilities. We will cover essential topics like transaction events, data structure, segment filtering, and hacker identification strategies. Learn how to utilize server-to-server validation to ensure only authentic revenue is displayed in your dashboards. Engage with our experts during the Q&A session to address any questions about effective revenue management.

aloha
Télécharger la présentation

WEBINAR Revenue validation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WEBINARRevenue validation

  2. Agenda • Revenue Validation Overview • Revenue Validation Process. • Apple - App Store Configuration • Transaction Event • QA • Data Structure • Queries / Segments / Filters • Questions….

  3. Revenue Validation Process Apple Receipt Validation Service deltaDNA platform Game ID saved on platform Valid Transaction ? Validation Result Game sends transaction event to deltaDNA Invalid revenue excluded from charts transactionReceipt and transactionServer parameters

  4. Overview • Server to Server revenue validation • Only genuine, verified revenue displayed in dashboards • Supports Apple App Store / Amazon • Not Currently supported on Google Play. Due to security concerns with Google implementation • Data can be analysed, segmented to identify hackers.Hackers could be targeted with Engage to modify their game behaviour

  5. Apple - App Store Configuration • Add App Store details to your Game Details page Apple Validation Service URL :: https://buy.itunes.apple.com/verifyReceipt Apple ID for game :: e.g. 971883677

  6. Your Transaction Event • Transaction event from client device includes- transactionServer- transactionReceipt • Transaction receipt is Base 64 Encoded receipt that was returned from Apple IAP Validating Receipts With the App Store https://developer.apple.com/library/ios/releasenotes/General/ValidateAppStoreReceipt/Chapters/ValidateRemotely.html#//apple_ref/doc/uid/TP40010573-CH104-SW1

  7. QA • Revenue Validation on DEV should be manually confirmed- Apple Sandbox service doesn’t reveal Game ID in receipt • Check using something like http://hurl.it Failed validation ! – valid receipt from a different game! Validating Receipts With the App Store https://developer.apple.com/library/ios/releasenotes/General/ValidateAppStoreReceipt/Chapters/ValidateRemotely.html#//apple_ref/doc/uid/TP40010573-CH104-SW1

  8. Data Structure • RevenueValidated flag automatically appended to transaction events by event validation processor. RevenueValidated • 0 – no validation performed • 1 – validated successfully • 2 – failed validation • Only revenue validated 0 and 1 is displayed in dashboards

  9. Filters & Segments • Build a segment based on RevenueValidated metric = 2 and you can isolate users who have performed an invalid transaction. • Use this segment to filter Measure dashboards or Analyze tools like Slice and Dice • With Targeting you could even modify game behaviour for Hacked Accounts!

More Related