What's New in v6​

App Open Ads​

Version 6 adds support for App Open Ads, a full-screen ad format designed for app launch moments. App open ads are displayed when users open your app or return to it from the background, making use of a natural transition point rather than interrupting an active session.

Why App Open Ads?​

App open ads address a monetization window that other formats do not cover well. Unlike interstitial ads, which appear mid-session, app open ads are shown during moments when users already expect a brief pause before content loads. This makes them a practical addition to an existing ad strategy.

To get started, check out the full integration guide:

• iOS App Open Ads Documentation
• Android App Open Ads Documentation

Renamed Classes and Constants​

Version 6 removes the BlueStack and MNG prefixes from all public API classes and constants. The underlying functionality remains the same — only the names have changed. Here are the key renames:

iOS​

Android​

For a complete list of all renamed classes, constants, and step-by-step migration instructions, see the migration guides:

• iOS Migration Guide
• Android Migration Guide

What about BlueStack v5 ?​

The old Public API as used in version 5 of the SDK is still accessible, but it is highly advised to switch to the v6 API whenever possible. In the future we will remove the old usages. We have also made the old documentation available on this site, you can find them here:

• Android
• iOS

What's Next?​

Version 6 adds App Open Ads and establishes a more consistent API surface as a foundation for further format support in upcoming releases. Publishers are encouraged to migrate to the v6 API at their earliest convenience.

For full documentation, visit:

• Android Documentation
• iOS Documentation

If you encounter issues or have questions, please reach out to us.

Framework integrations such as React Native will also be updated to support version 6 in the near term. Going forward, framework integration packages will follow the same major version scheme as the native SDK, so that version alignment is straightforward and there is no ambiguity about which SDK version a given package targets.

Overview​

BlueStack SDK v6 introduces an update that removes the BlueStack and MNG prefixes from all public API classes and constants. The underlying functionality remains the same — only the names have changed. This makes the SDK more neutral and easier to integrate across different publishing environments.

SDK Initialization​

The main entry point for initializing the SDK has been renamed from BlueStack to MobileAds.

Before (v5)​

import com.azerion.bluestack.BlueStack;
import com.azerion.bluestack.initialization.InitializationListener;
import com.azerion.bluestack.initialization.InitializationStatus;

class MainActivity extends AppCompatActivity {
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        
        BlueStack.INSTANCE.initialize(this, "YOUR_APP_ID", initializationStatus -> {
            initializationStatus.getAdapterStatusMap().forEach((adNetworkName, adapterStatus) -> 
                Log.d(TAG, "name: " + adapterStatus.getName() + ", state: " + adapterStatus.getState())
            );
        });
    }
}

import com.azerion.bluestack.BlueStack
import com.azerion.bluestack.initialization.InitializationListener
import com.azerion.bluestack.initialization.InitializationStatus

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        
        BlueStack.initialize(this, "YOUR_APP_ID", object : InitializationListener {
            override fun onInitialized(status: InitializationStatus) {
                status.adapterStatusMap.forEach { (adNetworkName, adapterStatus) ->
                    Log.d(TAG, "name: ${adapterStatus.name}, state: ${adapterStatus.state}")
                }
            }
        })
    }
}

After (v6)​

import com.azerion.bluestack.MobileAds;
import com.azerion.bluestack.initialization.InitializationListener;
import com.azerion.bluestack.initialization.SDKInitializationStatus;

class MainActivity extends AppCompatActivity {
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        
        MobileAds.INSTANCE.initialize(this, "YOUR_APP_ID", initializationStatus -> {
            initializationStatus.getMediationAdapterStatusMap().forEach((adNetworkName, adapterStatus) ->
                Log.d(TAG, "name: " + adapterStatus.getName() + ", state: " + adapterStatus.getState())
            );
        });
    }
}

import com.azerion.bluestack.MobileAds
import com.azerion.bluestack.initialization.InitializationListener
import com.azerion.bluestack.initialization.SDKInitializationStatus

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        
        MobileAds.initialize(this, "YOUR_APP_ID", object : InitializationListener {
            override fun onInitialized(status: SDKInitializationStatus) {
                status.mediationAdapterStatusMap.forEach { (adNetworkName, adapterStatus) ->
                    Log.d(TAG, "name: ${adapterStatus.name}, state: ${adapterStatus.state}")
                }
            }
        })
    }
}

Privacy Settings​

The privacy settings class has been renamed from BlueStackPrivacySettings to PrivacySettings.

Before (v5)​

BlueStackPrivacySettings.setIsAgeRestrictedUser(true, context);
BlueStackPrivacySettings.setIsUserOptOut(true, context);

BlueStackPrivacySettings.setIsAgeRestrictedUser(true, context)
BlueStackPrivacySettings.setIsUserOptOut(true, context)

After (v6)​

PrivacySettings.setIsAgeRestrictedUser(true, context);
PrivacySettings.setIsUserOptOut(true, context);

PrivacySettings.setIsAgeRestrictedUser(true, context)
PrivacySettings.setIsUserOptOut(true, context)

Error Handling​

The error class AdError and all error constant names remain unchanged in v6. All existing error constants from v5 work exactly the same way in v6.

Error Constants (Unchanged)​

New Error in v6​

:::tip No Migration Needed Since error constants are unchanged, your existing error handling code will work without modifications in v6. :::

Native Ads​

The native ad classes have been renamed to remove the MNG prefix. The ad loading, rendering, and interaction logic remains the same.

Class Renames​

Factory Initialization​

Before (v5)​

MNGAdsFactory mngAdsNativeAdsFactory = new MNGAdsFactory(getActivity());
mngAdsNativeAdsFactory.setPlacementId("/YOUR_APP_ID/PLACEMENT_ID");

val mngAdsNativeAdsFactory = MNGAdsFactory(activity)
mngAdsNativeAdsFactory.setPlacementId("/YOUR_APP_ID/PLACEMENT_ID")

After (v6)​

AdsFactory adsNativeAdsFactory = new AdsFactory(getActivity());
adsNativeAdsFactory.setPlacementId("/YOUR_APP_ID/PLACEMENT_ID");

val adsNativeAdsFactory = AdsFactory(activity)
adsNativeAdsFactory.setPlacementId("/YOUR_APP_ID/PLACEMENT_ID")

Loading with Preferences​

Before (v5)​

MNGPreference mngPreference = new MNGPreference();
mngPreference.setAge(28);
mngPreference.setGender(MNGGender.MNGGenderFemale);
mngAdsNativeAdsFactory.loadNative(mngPreference);

val mngPreference = MNGPreference()
mngPreference.setAge(28)
mngPreference.setGender(MNGGender.MNGGenderFemale)
mngAdsNativeAdsFactory.loadNative(mngPreference)

After (v6)​

Preference preference = new Preference();
preference.setAge(28);
preference.setGender(Gender.GenderFemale);
adsNativeAdsFactory.loadNative(preference);

val preference = Preference()
preference.setAge(28)
preference.setGender(Gender.GenderFemale)
adsNativeAdsFactory.loadNative(preference)

Native Ad Callbacks​

Before (v5)​

mngAdsNativeAdsFactory.setNativeListener(new NativeListener() {
    @Override
    public void nativeObjectDidLoad(MNGNativeObject nativeObject) {
        Log.d(TAG, "Native ad loaded");
        // Use nativeObject to render your custom ad view
    }

    @Override
    public void nativeObjectDidFail(Exception adsException) {
        Log.e(TAG, "Native ad failed to load: " + adsException.toString());
    }
});

mngAdsNativeAdsFactory.setNativeListener(object : NativeListener {
    override fun nativeObjectDidLoad(nativeObject: MNGNativeObject) {
        Log.d(TAG, "Native ad loaded")
        // Use nativeObject to render your custom ad view
    }

    override fun nativeObjectDidFail(adsException: Exception) {
        Log.e(TAG, "Native ad failed to load: $adsException")
    }
})

After (v6)​

adsNativeAdsFactory.setNativeListener(new NativeListener() {
    @Override
    public void nativeObjectDidLoad(NativeObject nativeObject) {
        Log.d(TAG, "Native ad loaded");
        // Use nativeObject to render your custom ad view
    }

    @Override
    public void nativeObjectDidFail(Exception adsException) {
        Log.e(TAG, "Native ad failed to load: " + adsException.toString());
    }
});

adsNativeAdsFactory.setNativeListener(object : NativeListener {
    override fun nativeObjectDidLoad(nativeObject: NativeObject) {
        Log.d(TAG, "Native ad loaded")
        // Use nativeObject to render your custom ad view
    }

    override fun nativeObjectDidFail(adsException: Exception) {
        Log.e(TAG, "Native ad failed to load: $adsException")
    }
})

AdChoice Position​

Before (v5)​

mngPreference.setAdChoicePosition(MNGPreference.TOP_LEFT);

mngPreference.setAdChoicePosition(MNGPreference.TOP_LEFT)

After (v6)​

preference.setAdChoicePosition(Preference.TOP_LEFT);

preference.setAdChoicePosition(Preference.TOP_LEFT)

Other Ad Format Classes​

The other ad format classes (InterstitialAd, RewardedAd, BannerView) and their listener interfaces remain unchanged in v6. No migration is needed for those formats.

Quick Find-and-Replace Summary​

For most projects, the migration can be completed with a few find-and-replace operations:

Need Help?​

If you encounter issues during migration, please reach out to us. The v5 documentation is still available at Android v5 for reference.

Overview​

BlueStack SDK v6 introduces an update that removes the BlueStack and MNG prefixes from all public API classes and constants. The underlying functionality remains the same — only the names have changed. This makes the SDK more neutral and easier to integrate across different publishing environments.

SDK Initialization​

The main entry point for initializing the SDK has been renamed from BlueStack to MobileAds.

Before (v5)​

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
    [[BlueStack sharedInstance] initializeWithAppID:@"YOUR_APP_ID_HERE" completion:^(InitializationStatus * _Nonnull initializationStatus) {

    }];
    return YES;
}

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
    BlueStack.sharedInstance().initialize(appID: "YOUR_APP_ID_HERE") { initializationStatus in
            
    }
    return true
}

After (v6)​

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
    [[BLSMobileAds sharedInstance] initializeWithAppID:@"YOUR_APP_ID_HERE" completion:^(InitializationStatus * _Nonnull initializationStatus) {

    }];
    return YES;
}

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
    MobileAds.sharedInstance().initialize(appID: "YOUR_APP_ID_HERE") { initializationStatus in
            
    }
    return true
}

Privacy Settings​

The privacy settings class has been renamed from BlueStackPrivacySettings to PrivacySettings.

Before (v5)​

[BlueStackPrivacySettings setIsAgeRestrictedUser:YES];
[BlueStackPrivacySettings setUserOptout:YES];

BlueStackPrivacySettings.setIsAgeRestrictedUser(true)
BlueStackPrivacySettings.setUserOptout(true)

After (v6)​

[PrivacySettings setIsAgeRestrictedUser:YES];
[PrivacySettings setUserOptout:YES];

PrivacySettings.setIsAgeRestrictedUser(true)
PrivacySettings.setUserOptout(true)

Error Handling​

Error classes and constants have been renamed to remove the BlueStack prefix.

Error Constants​

All error constants have been renamed from the BlueStack* prefix to the AdError* prefix:

New Error Codes in v6​

The following error codes are new in v6 and do not have v5 equivalents:

Before (v5)​

- (void)bannerView:(BannerView * _Nonnull)bannerView didFailedToLoadWithError:(NSError * _Nonnull)error { 
    switch (error.code) {
        case BlueStackErrorWrongPlacement:
            NSLog(@"Wrong placement Id. %@", error.localizedDescription);
            break;
        case BlueStackErrorSDKUninitialized:
            NSLog(@"BlueStackSDK is not initialized. %@", error.localizedDescription);
            break;
        default:
            NSLog(@"Unhandled error");
            break;
    }
}

func onFailedToLoad(_ bannerView: BlueStackSDK.BannerView, _ error: any Error) {
    guard let error = error as? BlueStackError, let errorCode = BlueStackErrorCode(rawValue: error.code) else { return }
    switch errorCode {
        case .BlueStackErrorWrongPlacement:
            print("Wrong placement Id. \(error.localizedDescription)")
        case .BlueStackErrorSDKUninitialized:
            print("BlueStackSDK is not initialized. \(error.localizedDescription)")
        default:
            print("Unhandled error. \(error.localizedDescription)")
    }
}

After (v6)​

- (void)bannerView:(BLSBannerView * _Nonnull)bannerView didFailedToLoadWithError:(NSError * _Nonnull)error { 
    switch (error.code) {
        case AdErrorWrongPlacement:
            NSLog(@"Wrong placement Id. %@", error.localizedDescription);
            break;
        case AdErrorSDKUninitialized:
            NSLog(@"BlueStack SDK is not initialized. %@", error.localizedDescription);
            break;
        default:
            NSLog(@"Unhandled error");
            break;
    }
}

func onFailedToLoad(_ bannerView: BlueStackSDK.BannerView, _ error: any Error) {
    guard let error = error as? AdError, let errorCode = AdErrorCode(rawValue: error.code) else { return }
    switch errorCode {
        case .wrongPlacement:
            print("Wrong placement Id. \(error.localizedDescription)")
        case .sdkUninitialized:
            print("BlueStack SDK is not initialized. \(error.localizedDescription)")
        default:
            print("Unhandled error. \(error.localizedDescription)")
    }
}

Native Ads​

The native ad classes and delegate protocols have been renamed to remove the MNG prefix. The ad loading, rendering, and interaction logic remains the same.

Class and Protocol Renames​

Factory Initialization​

Before (v5)​

nativeAdsFactory = [[MNGAdsSDKFactory alloc] init];
nativeAdsFactory.nativeDelegate = self;
nativeAdsFactory.placementId = @"/YOUR_APP_ID/PLACEMENT_ID";

nativeAdFactory = MNGAdsSDKFactory()
nativeAdFactory.nativeDelegate = self
nativeAdFactory.placementId = "/YOUR_APP_ID/PLACEMENT_ID"

After (v6)​

nativeAdsFactory = [[AdsSDKFactory alloc] init];
nativeAdsFactory.nativeDelegate = self;
nativeAdsFactory.placementId = @"/YOUR_APP_ID/PLACEMENT_ID";

nativeAdFactory = AdsSDKFactory()
nativeAdFactory.nativeDelegate = self
nativeAdFactory.placementId = "/YOUR_APP_ID/PLACEMENT_ID"

Loading with Preferences​

Before (v5)​

MNGPreference *preferences = [[MNGPreference alloc] init];
[nativeAdsFactory loadNativeWithPreferences:preferences];

let preferences = MNGPreference()
nativeAdFactory.loadNative(withPreferences: preferences)

After (v6)​

Preference *preferences = [[Preference alloc] init];
[nativeAdsFactory loadNativeWithPreferences:preferences];

let preferences = Preference()
nativeAdFactory.loadNative(withPreferences: preferences)

Delegate Callbacks​

Before (v5)​

- (void)adsAdapter:(MNGAdsAdapter *)adsAdapter nativeObjectDidLoad:(MNGNAtiveObject *)nativeObject {
    NSLog(@"Native ad loaded");
    // Use nativeObject to render your custom ad view
}

- (void)adsAdapter:(MNGAdsAdapter *)adsAdapter nativeObjectDidFailWithError:(NSError *)error withCover:(BOOL)cover {
    NSLog(@"Native ad failed to load: %@", error.localizedDescription);
}

func adsAdapter(_ adsAdapter: MNGAdsAdapter!, nativeObjectDidLoad nativeObject: MNGNAtiveObject!) {
    print("Native ad loaded")
    // Use nativeObject to render your custom ad view
}

func adsAdapter(_ adsAdapter: MNGAdsAdapter!, nativeObjectDidFailWithError error: Error!, withCover cover: Bool) {
    print("Native ad failed to load: \(error.localizedDescription)")
}

After (v6)​

- (void)adsAdapter:(AdsAdapter *)adsAdapter nativeObjectDidLoad:(NativeObject *)nativeObject {
    NSLog(@"Native ad loaded");
    // Use nativeObject to render your custom ad view
}

- (void)adsAdapter:(AdsAdapter *)adsAdapter nativeObjectDidFailWithError:(NSError *)error withCover:(BOOL)cover {
    NSLog(@"Native ad failed to load: %@", error.localizedDescription);
}

func adsAdapter(_ adsAdapter: AdsAdapter!, nativeObjectDidLoad nativeObject: NativeObject!) {
    print("Native ad loaded")
    // Use nativeObject to render your custom ad view
}

func adsAdapter(_ adsAdapter: AdsAdapter!, nativeObjectDidFailWithError error: Error!, withCover cover: Bool) {
    print("Native ad failed to load: \(error.localizedDescription)")
}

Other Ad Format Classes​

The other ad format classes (InterstitialAd, RewardedAd, BannerView) and their delegate protocols remain unchanged in v6. No migration is needed for those formats.

Quick Find-and-Replace Summary​

For most projects, the migration can be completed with a few find-and-replace operations:

Need Help?​

If you encounter issues during migration, please reach out to us. The v5 documentation is still available at iOS v5 for reference.

We're excited to announce the release of BlueStackSDK version 5.4.0 for both Android and iOS. This release focuses on enhancing our mediation capabilities and improving the overall adapter architecture.

Highlights​

• Enhanced Mediation: Significant improvements to adapter support and bidding separation for better flexibility.
• Improved Stability: Continued focus on minor fixes and internal refactors for a more robust SDK.

Changes​

Android​

• Added:
  • Introduced Validator interface and ValidationError data class for improved data validation.
  • Added necessary classes to support new adapter implementations.
• Updated:
  • Enhanced Ad Presenter support for adapters, streamlining ad presentation logic.

iOS​

• Added:
  • Separated bidding adapter from the core SDK, allowing for more modular and flexible bidding integrations.

How to upgrade​

Update your project dependencies to BlueStackSDK 5.4.0 and the corresponding mediation adapters:

// Android
dependencies {
    implementation "com.azerion:bluestack-sdk-core:5.4.0"
    implementation 'com.azerion:bluestack-mediation-bidding:5.4.0.0'
    // Update other mediation adapters as needed, e.g., Google, Equativ
    // implementation 'com.azerion:bluestack-mediation-google:X.Y.Z.A'
    // implementation 'com.azerion:bluestack-mediation-equativ:X.Y.Z.A'
}

# iOS
pod 'BlueStackSDK', '5.4.0'
pod 'BlueStackBiddingAdapter', '5.4.0'
# Update other mediation adapters as needed, e.g., Google, Equativ
# pod 'BlueStackGoogleAdapter', '>= X.Y.Z'
# pod 'BlueStackEquativAdapter', '>= X.Y.Z'

For exact artifact names and latest versions, always consult the Android and iOS mediation documentation linked above.

If you encounter issues or have questions, please reach out to us. We'll continue to iterate based on your feedback.

We're releasing BlueStackSDK version 5.3.0 for both Android and iOS. This release includes stability improvements, minor fixes, and compatibility updates across ad formats.

Highlights​

• Quality & stability: Minor bug fixes, logging improvements, and internal refactors
• Mediation readiness: Validated with our latest mediation adapters

IMPORTANT: If you use Google mediation or the BlueStack Google adapter, you must update it alongside SDK 5.3.0. See the note below for details.

Changes​

• Stability improvements across interstitial, rewarded, and banner flows
• Minor fixes to lifecycle and presentation timing for fullscreen formats
• Internal dependency and maintenance updates for 5.3.0 parity across Android and iOS

Critical note about the Google adapter​

To ensure full compatibility with BlueStackSDK 5.3.0, you must also update the Google adapter packages on both platforms:

• Android: bluestack-google-adapter (update to a version supporting 5.3.0)
• iOS: BlueStackGoogleAdapter (update to a version supporting 5.3.0)

Refer to our documentation for the latest adapter coordinates and setup:

• Android — Google mediation
• iOS — Google mediation

If you're migrating from older adapter names, see also: Mediation Package Updates for Android and iOS

How to upgrade​

Update your project dependencies to BlueStackSDK 5.3.0 and the corresponding Google adapter:

// Android
dependencies {
    implementation "com.azerion:bluestack-sdk-core:5.3.0"
    implementation 'com.azerion:bluestack-mediation-google:5.3.0.0'
    implementation 'com.azerion:bluestack-mediation-bidding:5.3.0.0'
}

# iOS
pod 'BlueStackSDK', '5.3.0'
pod 'BlueStackGoogleAdapter', '>= 5.3.0'

For exact artifact names and latest versions, always consult the Android and iOS mediation documentation linked above.

If you encounter issues or have questions, please reach out to us. We'll continue to iterate based on your feedback.

We're releasing BlueStackSDK version 5.2.0 on Android and iOS, focusing on a significant enhancement to how we handle interstitial ad delivery. This update introduces preloading for both static (HTML) and VAST/Video interstitial ad formats. This has been implemented without any changes to our public API.

Understanding the Change​

In v5.2.0, we've integrated preloading mechanism. This means the SDK now attempts to fetch and prepare interstitial ad assets in the background so that your ad content becomes ready before you show the ad.

Key Technical Benefits​

• Reduced Display Latency: By having the ad creative and its necessary resources (HTML, video assets, etc.) already downloaded and parsed, the time from calling show to the ad being presented is significantly minimized. This is particularly noticeable for video-based interstitial ads, where buffering can be an issue.

• Enhanced Reliability in Variable Network Conditions: If a user temporarily experiences a network dip, the ad may already be loaded and ready, preventing a failed display or a prolonged loading spinner.

Impact on Your Implementation​

The most important takeaway for developers is that no changes are required to your existing BlueStackSDK integration. Our public APIs remain consistent. You simply need to update your SDK dependency to v5.2.0. The preloading logic is entirely encapsulated within the SDK.

BlueStackSDK v5.2.0 is a performance-focused update designed to deliver seamless and reliable ad experience without introducing any integration complexities.

Android​

BlueStack Medation: Google​

bluestack-mediation-gma has been renamed to bluestack-mediation-google. If you're already using bluestack-mediation-gma, simply update your dependencies to bluestack-mediation-google, and you're good to go.

BlueStack Medation: Equativ​

bluestack-mediation-smartadserver has been renamed to bluestack-mediation-equativ. If you're already using bluestack-mediation-smartadserver, simply update your dependencies to bluestack-mediation-equativ, and you're good to go.

Google mediation​

Our Google Mediation adapter is used for when Google is your main SDK, it will mediate BlueStack. We've also changed the name of this implementation:

bluestack-gam-adapter has been renamed to bluestack-google-adapter. If you're already using bluestack-gam-adapter, simply update your dependencies to bluestack-google-adapter, and follow the Yield setup described in our documentation

Documentation​

For detailed integration instructions, please refer to our documentation:

• Google Adapter
• Equativ Adapter
• Google Mediation

Stay tuned for more updates, and as always, feel free to reach out with any questions. 🚀

iOS​

BlueStack Medation: Google​

BlueStackDFPMediationAdapter has been renamed to BlueStackGoogleMediationAdapter. If you're already using BlueStackDFPMediationAdapter, simply update your dependencies to BlueStackGoogleMediationAdapter, and you're good to go.

BlueStack Medation: Equativ​

BlueStackSASAdapter and BlueStackSASBiddingAdapter have been merged into BlueStackEquativAdapter. If you're already using the old adapters, simply replace them with BlueStackEquativAdapter, and you're good to go.

Google mediation​

Our Google Mediation adapter is used for when Google is your main SDK, it will mediate BlueStack. We've also changed the name of this implementation:

BlueStackGMAAdapter has been renamed to BlueStackGoogleAdapter. If you're already using BlueStackGMAAdapter, update your dependencies to BlueStackGoogleAdapter, and follow the Yield setup described in our documentation

Documentation​

For detailed integration instructions, please refer to our documentation:

• Google Adapter
• Equativ Adapter
• Google Mediation

Stay tuned for more updates, and as always, feel free to reach out with any questions. 🚀

Key Improvements in v5​

1. Streamlined API for Ad Integration​

With version 5, we've refined the public API, making it easier than ever to integrate ads into your app. The updated API offers a more intuitive interface for configuring, loading, and displaying ads. Whether you’re working with interstitial, rewarded video, or banner ads, the process is now more straightforward, reducing the amount time required to integrate the SDK.

2. Improved Interstitial Ads​

Interstitial ads are an effective tool for monetizing mobile apps, and in version 5, we've made it even easier to manage their lifecycle. Developers now have enhanced control over the timing and behavior of interstitial ads, allowing for more seamless user experiences without compromising revenue potential. The new API simplifies the handling of ad loading, showing, and dismissing, ensuring better performance across devices.

3. Better Rewarded Video Experience​

Rewarded video ads offer an excellent way to engage users by providing incentives in exchange for watching ads. The improvements in v5 make the rewarded video ad flow smoother similar to the changes we've done to the interstitial ad format. This version also introduces improved error handling, ensuring that any issues are caught and logged, making it easier to debug and improve app performance.

4. Optimized Banner Ads​

Banner ads continue to be a staple for mobile monetization, and in this update, we've improved how they interact with your app’s layout. With version 5, banner ads can now be more easily customized to fit seamlessly into your app’s UI, offering a better user experience while still maximizing ad revenue. The new API also ensures better ad loading performance, reducing delays that could affect your app’s responsiveness.

Why These Changes Matter​

Our focus in version 5 was to streamline the ad integration process, improve performance, and enhance user experience across various ad formats. By refining the public API for interstitial, rewarded video, and banner ads, we’ve made it easier for developers to integrate high-performing ads without compromising the quality of the app or the user experience.

What about BlueStack v4 ?​

The old Public API as used in version 4 of the SDK is still accessible, but it highly advised to switch to the v5 API when ever possible. In the future we will remove the old usages. We also have made the old documentation available on this site, you can find them here:

• Android
• iOS

Changes to Documentation​

Apart from updating our SDK, we also simplified our documentation in this version 5 release:

• We've added a dedicated Privacy and Compliance section to both native platforms
• Release notes have been cleaned up
• We created a copy of the old v4 documentation and made it available for you on both native platforms
• Error handling and error codes now have a dedicated section as well
• Improved the Mediation & Bidding section

What's Next?​

As always, we are committed to providing cutting-edge solutions for app monetization. With version 5 of our Mobile Ad SDK, we’ve laid the groundwork for more features and enhancements in future releases. We encourage all Publishers to upgrade to the latest version of the SDK to take advantage of these improvements and continue to deliver the best possible experiences for their users.

For more details on the changes in version 5, including the full release notes, check out our official documentation for Android and iOS.

Stay tuned for more exciting updates coming soon!

We're thrilled to announce the latest release of our BlueStack SDK, version 4.4.0! This update brings a modular architecture to our ad mediation framework, making it even more flexible and developer-friendly. With a core SDK and individual adapter SDKs for supported ad networks, BlueStackSDK v4.4.0 gives you the option to choose and integrate only what you need, making the ad integration process easier than before.

What's new?​

1. Modularization for Enhanced Flexibility​

In response to developer feedback, we've modularized BlueStack SDK into following components:

• BlueStackSDK Core: This core sdk provides public APIs for showing Ads and all the essentials for waterfall logic.
• Third-party Ad Network Adapters: Individual SDKs for each supported ad network that handles integration specifics for that network. This modular approach allows for easier updates, maintenance, and customization.

2. Adapter Architecture for Simplicity​

BlueStack adapter architecture simplifies the integration process. Developers can now integrate specific ad network adapters based on their requirements. This also separates the third party ad network implementation from the core, which improves the performance of the BlueStack SDK.

3. Improved Flexibility​

With BlueStackSDK v4.4.0, now you have the power to choose. Integrate only the ad network adapters you need, avoiding unnecessary dependencies. This flexibility gives significant advantage, especially for apps where app size and performance is crucial.

Why upgrading to v4.4.0​

1.Reduced App Size​

By allowing developers to selectively integrate only the specific ad network adapters they need, unnecessary dependencies are avoided. This will make the app more lightweight.

2.Future-Proof Scalability​

Adding or removing adapters is now a breeze! By updating your app's build.gradle dependencies you can easily achieve that.

Supported Third-party Network Adapters​

BlueStack supports third-party ad network adapters, which are accessible through the Maven Central Repository. These adapters are published under the group ID com.azerion. All adapters use a four-number versioning scheme. The initial three numbers signify the BlueStack core SDK version, while the final number denotes the adapter release. For instance, the first release of the Google Mobile Ads (GMA) adapter, built on BlueStack core 4.4.0, would be labeled as 4.4.0.0. Below is a list of BlueStack-supported third-party network adapters, each accompanied by its corresponding Maven artifact ID.

Note: In-App-Bidding has a default dependency with Amazon and Smart Display SDK. So adding In-App-Bidding will automatically include these three SDKs.

Integrate BlueStackSDK v4.4.0​

Integrate BlueStackSDK Core: Add BlueStackSDK dependency in your app's build.gradle

dependencies {
   implementation 'com.azerion:bluestack-sdk-core:4.4.0'
}

Integrate Required Adapters: Choose your required adapters from the above list and add the dependency in your app's build.gradle

dependencies {
   ...
   implementation 'com.azerion:bluestack-mediation-gma:4.4.0.0'
   implementation 'com.azerion:bluestack-mediation-bidding:4.4.0.0'
   ...
}

We are thrilled to announce the release of the React Native BlueStack SDK! This powerful new React Native plugin allows you to seamlessly integrate BlueStack Ads into your React Native mobile applications. It provides a robust and flexible way to monetize your apps on both iOS and Android platforms: premium sales with rich media, video and innovative formats as well all standard display formats, ensuring a smooth user experience and maximizing your revenue potential.

Why Choose BlueStack Ads?​

BlueStack Ads are known for their effectiveness and versatility. By using our SDK, you can leverage three distinct ad formats to engage users and drive monetization:

1. Component-Based Banner Ads:

   • Display banner ads seamlessly within your app’s interface.
   • Easily customizable to match the look and feel of your app.
   • Ideal for non-intrusive, continuous ad revenue.

2. Full-Screen Interstitial Ads:

   • Engage users with full-screen ads during natural app transitions.
   • Perfect for maximizing revenue during breaks or level changes.

3. Full-Screen Rewarded Ads:

   • Offer users rewards in exchange for watching ads.
   • Boost user engagement by providing valuable in-app incentives.

Key Features​

• Cross-Platform Support: Fully supports both iOS and Android platforms.
• Easy Integration: Designed for simplicity, making it easy to get started and integrate into existing projects.
• Flexible and Customizable: Tailor the appearance and behavior of ads to fit your app's design and user experience.
• Comprehensive Documentation: Step-by-step guides, API references, and example projects to help you get started quickly.

Getting Started​

Installation​

To install the React Native BlueStack SDK, you can use either npm or yarn:

npm install @azerion/bluestack-sdk-react-native

or

yarn add @azerion/bluestack-sdk-react-native

Usage​

Here's a quick example to get you started with banner ads:

import React from "react";
import { View, StyleSheet } from "react-native";
import {
  BluestackSDK,
  BannerAdView,
} from "@azerion/bluestack-sdk-react-native";

const App = () => {
  return (
    <View style={styles.container}>
      <BannerAdView
        type="standard"
        shouldLoadWhenReady={true}
        placementId={"/" + appId + "/banner"}
        onAdLoaded={(object: any) => {
          console.log("Banner Ad Loaded");
        }}
        onAdFailedToLoad={(error: any) => {
          console.log(
            "Banner Ad failed to load : " + error?.nativeEvent?.error
          );
        }}
        ref={refBanner}
      />
    </View>
  );
};

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: "center",
    alignItems: "center",
  },
});

export default App;

For interstitial and rewarded ads, the process is just as simple. Check out our documentation for more detailed examples and comprehensive guides.

Demo App​

We are excited to announce that we have also released a Demo App, designed to demonstrate the full capabilities of the newly launched React Native BlueStack SDK. The Demo App serves as a practical example of how to implement and utilize the BlueStack Ads within a React Native project. It highlights the integration process and demonstrates the functionality of the three primary ad formats supported by the SDK.

Start by cloning the demo app repository from GitHub:

git clone https://github.com/azerion/bluestack-demo-react-native.git
cd bluestack-demo-react-native

In summary​

The React Native BlueStack SDK opens up new opportunities for app developers to monetize their applications efficiently and effectively. We can't wait to see the innovative ways you'll use this SDK to enhance your apps and boost your revenue. Get started today and take your app monetization to the next level with BlueStack!

Happy coding!

documentation

We're thrilled to announce the latest release of our BlueStack SDK, version 4.4.0! This update brings a modular architecture to our ad mediation framework, making it even more flexible and developer-friendly. With a core SDK and individual adapter SDKs for supported ad networks, B lueStackSDK v4.4.0 gives you the option to choose and integrate only what you need, making the ad integration process easier than before.

Previously this set-up was only supported via SPM, now we are also providing support for this flexibility using [Cocoapods].

What's new?​

1. Modularization for Enhanced Flexibility​

In response to developer feedback, we've modularized BlueStack SDK into following components:

• BlueStackSDK Core: This core sdk provides public APIs for showing Ads and all the essentials for waterfall logic.
• Third-party Ad Network Adapters: Individual SDKs for each supported ad network that handles integration specifics for that network. This modular approach allows for easier updates, maintenance, and customization.

2. Adapter Architecture for Simplicity​

BlueStack adapter architecture simplifies the integration process. Developers can now integrate specific ad network adapters based on their requirements. This also separates the third party ad network implementation from the core, which improves the performance of the BlueStack SDK.

3. Improved Flexibility​

With BlueStackSDK v4.4.0, now you have the power to choose. Integrate only the ad network adapters you need, avoiding unnecessary dependencies. This flexibility gives significant advantage, especially for apps where app size and performance is crucial.

Why upgrading to v4.4.0​

1.Reduced App Size​

By allowing developers to selectively integrate only the specific ad network adapters they need, unnecessary dependencies are avoided. This will make the app more lightweight.

2.Future-Proof Scalability​

Adding or removing adapters is now a breeze! By updating the podfile or selecting the dependencies using SPM you can easily achieve that.

Supported Third-party Network Adapters​

Below are the BlueStack supported third-party network adapters along with their sub-specs name for integrating using [Cocoapods] Please reach out to our Publishing team when you are in doubt as too inclusion of which Adapter is best for you.

Note: In-App-Bidding has a default dependency with Criteo, Amazon and Smart Display SDK. So adding In-App-Bidding will automatically include these three SDKs.

Integrate BlueStackSDK v4.4.0​

Using Cocoapods​

Integrate BlueStackSDK Core: Add BlueStackSDK to your podfile

pod 'BlueStackSDK', '4.4.0'

Integrate Required Adapters: Choose your required adapters from the above list and add the subsepc to your pod file like below

pod 'BlueStackSDK', '4.4.0', :subspecs=>['Google-Mobile-Ads-SDK', 'In-App-Bidding']

Using SPM​

You will find integration process and requirements through SPM here

Cocoapods.