Introduction

The Magify Unity SDK enables you to track analytics, validate purchases, restore user progress, provode remote features and content, configure offers, and more in your Unity app.

Before you begin

Here's what you need to know before you get started:

Magify Manager and Magify Service

Magify SDK actually consists of 2 layers: Magify Manager and Magify Service:

• Magify Manager is a low-level API that provides direct access to various data and methods that are a minimal unit of SDK logic;
• Magify Service is a kit of different entities and services that are wrappers over Magify Manager. They are basic implementations of the game elements as we see them. For example:
  • An advertising service responsible for integration with advertising mediators, as well as implementing methods for displaying ads and tracking analytics related to advertising;
  • A purchasing service responsible for uploading products and initiating purchases, as well as tracking analytics related to purchases;
  • A campaign processing service responsible for launching campaigns, displaying creatives and charging campaign products. It is also responsible for tracking analytics related to campaigns.

Depending on what stage your application is at and how low-level you want to interact with our API you can choose one of these two levels to work with the SDK.

Recommendations for choosing between Magify Manager and Magify Service

We highly recommend opting for Magify Service, and most likely this option will suit your project better. The criteria you can use to see which option is best for you are described below.

Choose Magify Manager if:

• Your app already has a big infrastructure in place to handle different ad mediators, purchasing libraries, and you don't want to use our services to interact with it, you just want to do tracking analytics related to that;
• You realize that in this case all the responsibility for collecting analytics, for proper processing of campaigns is on your side.

Choose Magify Service if:

• You want to get as many ready-made implementations of different game features as possible using our SDK;
• You want to have access to all of our default implementations of integration with ad mediation, purchasing services, which includes initiating ad impressions, fetching products for purchase, initiating purchases, errors handling, and correct collecting of analytics;
• You want to have a set of standard campaign handlers and also be able to implement custom handlers;
• You want to have access to various auxiliary services: checking network status, getting real server time, updating subscription status, ads preloading, popups system, and others;
• You don't want to be responsible for collecting analytics correctly, you just want to receive app content in a usable form.