Unity SDK Analytics

Preparation

Remember, you need to configure and initialize the Magify Service to collect analytics.

You may also want to pass some configuration parameters to better collect analytics:

• Set iOS ATT status on initialization or later in runtime;
• Set GDPR agreement status on initialization;
• Set media source in runtime.

What analytics does the SDK collect?

There are several analytical models built into the SDK that are built automatically. You will not interact with them directly, but some SDK settings may affect the content of the collected data.

Start of sessions

This kind of analytics is collected every time a new session starts. This also collects information about the InApp status and Subscription status of the user.

Going to the background

Events are collected to understand when the user minimized the application or closed it.

Applovin Max/LevelPlay ads impressions

When a banner/interstitial/reward ad is shown, we collect analytics. For correct operation you need to select and install the mediator you will use and link it with Magify SDK.

• To implement it see MagifyService.SetAdsMediator and IMinimalAdsMediator;
• Also should check default implementations of this mediators: for Applovin Max and for LevelPlay.

Your own ads impressions

When you use an ad mediation service other than Applovin or IronSource and want to track ads impressions, then you need:

• Only for advanced verison SDK: Implement ICampaignHandler for each campaign type you use (banner, interstitial, reward ad);
• Use MagifyManager.TrackCustomAdsImpression method for track ads impressions.

InApp / Subscription

These types of analytics are collected when InApp products are purchased or Subscription purchase are made. For correct operation you need to select and install the purchasing provider you will use and link it with Magify SDK.

• To implement it see MagifyService.SetPurchasingProvider and IMinimalInAppStore.

Paying state notes

You can read about paying statuses here.