BIGO Ads

Use this guide to configure BIGO Ads bidding in CloudX.

Keep using the platform integration guides for SDK installation and ad loading:

• Android integration guide

For platform-specific BIGO Ads adapter requirements, see:

• Android BIGO Ads Adapter page

The BIGO Ads adapter is currently available for Android.

Overview

Use the following values:

• Bigo App ID in CloudX app mapping
• Bigo Slot ID in CloudX ad-unit mapping
• CloudX app_key and CloudX ad unit identifiers in app code

CloudX uses the bidder name Bigo Ads in the dashboard. It is the same network as BIGO Ads on the BIGO Ads platform.

CloudX collects BIGO Ads bidder tokens internally, so you do not need to fetch BIGO Ads bidder tokens in your app code.

Supported ad formats:

• Banner (320x50)
• MREC (300x250)
• Interstitial
• Rewarded

Native and App Open are not supported.

Step 1. Complete BIGO Ads-side setup

1. Sign in to the BIGO Ads platform.
2. Add the app you want to monetize with its store listing URL. The app domain you enter must match the developer website on the app’s store listing; BIGO Ads verifies the two against each other.
3. Copy the BIGO Ads App ID for that app.
4. Add the app-ads.txt entries that the BIGO Ads platform lists for your account to the app-ads.txt file hosted on that developer website.
5. Create a slot for each ad format you want to use, with the Server Bidding auction type. Only Server Bidding slots work with CloudX.
6. Keep banner auto-refresh switched off on the BIGO Ads platform for slots used with CloudX. The CloudX SDK owns banner refresh; a second refresh loop inside the BIGO Ads SDK would load creatives that never won a CloudX auction.
7. Copy each Slot ID.
8. Complete BIGO Ads app review and payout setup before expecting live demand.

Step 2. Enable BIGO Ads in CloudX

Go to Bidders in the dashboard navigation, select Bigo Ads in the bidder list, and click Enable.

If Bigo Ads is disabled, CloudX will not request bids even if your mappings are correct. If Bigo Ads is not visible in the Bidders section, contact your CloudX account manager.

After enabling, you can enter Bigo App IDs and Slot IDs from this same page: search for an app, select it, and fill in the App ID plus Slot IDs for each eligible ad unit. You can also configure the same values from the app and ad-unit pages in the next steps.

Step 3. Configure your CloudX app

Go to Inventory -> Apps and create or open the app that matches your mobile application. Enter the Bigo App ID for that app.

Also copy the CloudX app_key from the app details page. Use the CloudX app_key in Android code.

Step 4. Configure CloudX ad units

Go to Inventory -> Ad units and add the mapping below for each eligible ad unit.

• Treat Bigo Slot ID as required.
• Match the slot’s ad format to the CloudX ad-unit format.
• Use a separate Server Bidding slot for each CloudX ad unit or format as needed.

Step 5. Add BIGO Ads line items

Go to Line Items and create line items for bidder Bigo Ads on each CloudX ad unit where BIGO Ads should compete.

• Use bidder Bigo Ads
• Match the line item to the correct ad format
• Repeat the setup for each ad unit where BIGO Ads should bid

Step 6. Finish app integration

Complete the integration and adapter setup for your platform:

• Android integration guide
• Android BIGO Ads Adapter page

In app code:

• Initialize CloudX with the CloudX app_key
• Load ads using CloudX ad unit identifiers
• Do not pass Bigo App IDs or Slot IDs into app code
• For Interstitial and Rewarded ads, call show() only after the ad is ready

Step 7. Test and validate

1. Register your device as a CloudX test device: open the app page, click the ⋮ menu, select Test devices, add the device, and turn on Test Traffic.
2. Optionally, map a development build to the test App ID and Slot IDs from the BIGO Ads platform documentation, which return test ads. Switch to your production IDs before release.
3. Build and run the app with the CloudX app_key and the correct CloudX ad unit identifiers.
4. Request an ad from each mapped ad unit.
5. Confirm that the ad loads and that BIGO Ads participates or wins where expected.

Troubleshooting

BIGO Ads is not bidding

Check the following first:

• Bigo Ads is enabled in the Bidders section
• The app has a valid Bigo App ID
• The ad unit has a valid Bigo Slot ID
• A Bigo Ads line item exists for the ad unit
• The app is approved on the BIGO Ads platform, and its app domain matches the developer website on the store listing
• Your app-ads.txt file includes the entries the BIGO Ads platform lists for your account

BIGO Ads bids but the ad does not render

Check the following:

• Your app is using the CloudX app_key, not a BIGO Ads ID
• Your app is loading the intended CloudX ad unit
• The slot belongs to the correct BIGO Ads app and format, and uses the Server Bidding auction type
• The BIGO Ads adapter is installed and the network security configuration from the Android BIGO Ads Adapter page is in place

The slot looks correct but loads still fail

The mobile adapter requires a valid Bigo Slot ID at load time. Re-check the ad-unit-level slot mapping in CloudX.

Mapping Reference