Migration to 4.7.0

Note: This migration guide covers the changes introduced in version 4.7.0. Migration guides are incremental, so if you are upgrading from an earlier version, please review all intermediate migration guides to ensure you account for any required changes between your current version and 4.7.0.

1. The logic for selecting test group added in 4.6.0 is now clearer: https://docs.nefta.io/update/docs/nefta-ab-testing-data-integration-guide
   Deprecated old methods for passing which ad strategy is selected, the decision should be now passed at Nefta initialization:
   C#SwiftJava

   // old Init:
   NeftaAdapterEvents.InitWithAppId(_neftaAppId, (InitConfiguration config) => { });
   
   // new Init:
   NeftaAdapterEvents.InitWithAppId(_neftaAppId, optimizationType, (InitConfiguration config) => {
      // in case you don't want to make decision, you provide:
      // OptimizationType.Unknown and then select ad strategy based on:
      // config._isSessionOptimized
   });
   
   // Removed:
   // NeftaAdapterEvents.SetInterstitialLogic(isOptimized);
   // NeftaAdapterEvents.SetRewardedLogic(isOptimized);

   // Old init:
   ALNeftaMediationAdapter.Init(appId: "5661184053215232", onReady: { initConfig in })
   
   // New init:
   ALNeftaMediationAdapter.Init(appId: "5661184053215232", optimizationType: optimizationType, onReady: { config in
     // in case you don't want to make decision, you provide:
      // OptimizationType.Unknown and then select ad strategy based on:
      // config._isSessionOptimized
   });
   
   // Removed:
   // NeftaPlugin.SetInterstitialLogic(isOptimized);
   // NeftaPlugin.SetRewardedLogic(isOptimized);

   // Old init:
   NeftaMediationAdapter.InitWithAppId(getApplicationContext(), "5632029345447936", (InitConfiguration config) -> { });
   
   // New init:
   NeftaMediationAdapter.InitWithAppId(getApplicationContext(), "5632029345447936", optimizationType, (InitConfiguration config) -> {
     // in case you don't want to make decision, you provide:
      // OptimizationType.Unknown and then select ad strategy based on:
      // config._isSessionOptimized
   });
   
   // Removed:
   // NeftaPlugin.SetInterstitialLogic(isOptimized);
   // NeftaPlugin.SetRewardedLogic(isOptimized);

2. MAX can be initialized at any time and not after Nefta initialization callback.
3. We now require 3 ad units per ad format.
4. Used ad units are now always either optimized (with dynamic floor) or without (or with hardcoded floor in dashbaord).
   • Disable Back to Back preloading should be set only for dynamic ad units.
5. Updated dual track logic for wrapper:
   C#

   // Old:
   //NeftaSdk.Interstitial.Initialize(isOptimized, InterstitialUi.OptimizedAdUnitIdA, InterstitialUi.OptimizedAdUnitIdB); 
   //NeftaSdk.Rewarded.Initialize(isOptimized, RewardedUi.OptimizedAdUnitIdA, RewardedUi.OptimizedAdUnitIdB);
   
   // New:
   NeftaSdk.Interstitial.Initialize(isOptimized, InterstitialUi.DefaultAdUnitId, InterstitialUi.OptimizedAdUnitIdA, InterstitialUi.OptimizedAdUnitIdB); 
   NeftaSdk.Rewarded.Initialize(isOptimized, RewardedUi.DefaultAdUnitId, RewardedUi.OptimizedAdUnitIdA, RewardedUi.OptimizedAdUnitIdB);

6. Improved behaviour of players without consent, the SDK won't just forget all the data and shut down, but will optimized with anonymized data
7. Removed game events
8. For manual integration please check the updated code samples