Assetario Documentation
  • Overview
    • Assetario Overview
    • Predicted Life-Time Value (pLTV)
    • In-App Purchase Personalization (IAP Recommendation)
  • Integration
    • Assetario onboarding
    • Data Requirements
    • Data input integration guides
      • DeltaDNA integration
      • Amplitude AWS integration
      • Google BigQuery access share
      • AWS S3 Bucket access share
      • Scheduling Queries in BigQuery
    • PLTV: Setup
    • IAP Personalization: Setup
      • Dynamic offer personalization
        • Offers definition table
        • API reference
      • Contextual price personalization
        • Price levels definition
        • API reference
      • A/B tests
      • Third Party Integrations
        • RevenueCat
  • FAQ
    • IAP Personalization FAQ
  • Dashboards
    • PLTV Dashboard
    • IAP Personalization Dashboard
  • Best practices
    • PLTV: Google Adwords
      • Offline conversions
    • PLTV: Facebook
      • Offline conversions
      • Value-Based Lookalikes
  • Data Security
  • Dictionary
Powered by GitBook
On this page
  1. Integration

IAP Personalization: Setup

PreviousPLTV: SetupNextDynamic offer personalization

Last updated 1 year ago

IAP Recommendation is driving optimal offers to the right users based on user behavior and metadata to unlock organic uplift.

We highly recommend that the customer calls the Assetario API for all users and then decides which users to show the Assetario predictions to. This allows the Assetario algorithm to learn faster as it can easily compare the control and personalized user-level inputs and predictions with very high accuracy.

Steps you need to follow after the data preparation:

  • Define who creates and manages the A/B test. Oftentimes, you already have a tool to run A/B tests, be it Leanplum, DeltaDNA, or a custom internal solution. At Assetario, we built our own A/B Testing solution which will help you understand the impact of the RecIAP product on your ARPDAU and retention. More on how we run our A/B tests can be found in .

  • Once you decide who manages the A/B Test, we need to select a cohort of players to test RecIAP on. The questions we need to answer are the following:

    • What is the ratio of control to personalized users? We typically recommend that at least 30% of your users are personalized by Assetario.

    • Will we test only on new users or only on existing users or both?

  • Check out the API and define the final API signature .

  • Implementing the logic for calling the Assetario Prediction API and the Assetario A/B Test API.

  • We always make predictions only from the offer catalog you share with us. We don't generate new offers. This way you have full control over the quality, content, and price of all offers your users see. Please, share those offers with us in an Assetario-friendly format defined in .

  • If you are using the IAP Recommendation Engine for country-level personalization, you might need to create new SKUs, please follow for more details.

A/B tests
here
the Offers table
SKUs creation