Use Cases - plenigo IAP

    Content of this article

    1. Preliminary Remarks
    2. Use Anonymous User Data (Apps without Login Function)
    3. Connection with Known User Data (Apps with Login Function)

    1. Preliminary Remarks

     In-App Purchases refer to purchases that are made by someone within an app, usually on a mobile phone or tablet. IAP can differ from app category to app category. Common examples are:

    • Selling single products, such as time passes, files or access to a stream
    • Selling subscriptions for tracking and advertising freedom within the app
    • Selling comprehensive subscriptions with various service areas
    IAP make it possible to offer an app free of charge and to generate revenue through paid functions and products once the app has been installed.

    Note:  When designing an app, the question arises as to whether the app user can or should also log into the SSO within the app.
    The answer to this question determines additional functions:
    • A login function can be used to link an IAP with a registered customer in the plenigo system.
    • This means that customers who already have access to a service via an app, for example, can also view it on a website.

    2. Use Anonymous User Data (Apps without Login Function)

     "Orders" does not show all store orders, but only the connected subscriptions.

    Procedure:
    • IAP from a store is added to the plenigo system (add purchase) 
    • The data can be called in the Merchant Backend.
    • The data is anonymous and cannot be associated with a user.
    • This creates an overview of all purchases from the individual stores in the Merchant Backend.

    3. Connection with Known User Data (Apps with Login Function)

    By logging in, an e-mail address can be associated with the app user. If this e-mail address is identical to an address stored in the Merchant Backend, the anonymous IAP can be linked with the existing customer data set.

    Advantages:
    • By purchasing within an app, the customer can also access the service via a web browser if desired without having to purchase a separate offer again.
    • The IAPs are visible directly on the customer data record in the Merchant Backend.
    • The terms of the access rights from IAP can be viewed.
    Procedure: 
    • add purchase - IAP from a store is added to the plenigo system.
    • associate purchase - The added IAP connects the app store purchase with an existing customer in the plenigo system. The e-mail addresses must be identical.
    • dissociate purchase - removes an app store purchase from an existing customer in the plenigo system.
    Published