MobileFuse

Use this guide to configure MobileFuse bidding in CloudX.

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

For platform-specific MobileFuse adapter requirements, see:

The MobileFuse adapter is available for Android and iOS, and for Unity through the CloudX Unity plugin. The current adapter requires CloudX Android SDK 4.2.0 or newer, CloudX iOS SDK 3.5.0 or newer, and iOS 15.0 or later. Native ads on iOS require CloudX iOS SDK 3.12.0 or newer.

Overview

Use the following values:

  • MobileFuse Publisher ID on the MobileFuse page under Bidders; this account-level value applies to all applications
  • MobileFuse Placement ID in CloudX ad-unit mapping
  • CloudX app_key and CloudX ad unit identifiers in app code

CloudX collects the MobileFuse bid token through the MobileFuse adapter, so you do not need to fetch or pass the token in your app code.

Supported ad formats:

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

Supported countries

MobileFuse buys inventory only in the United States and Canada, so CloudX requests MobileFuse bids only for users in those two countries.

Floors

MobileFuse does not bid when the floor is $30 or higher, so CloudX does not send MobileFuse those requests. Line items with a floor of $30 or higher get no MobileFuse demand.

Step 1. Complete MobileFuse onboarding and update app-ads.txt

Contact your MobileFuse account manager to sign an agreement before you enable MobileFuse in CloudX. If you do not have a MobileFuse contact, ask your CloudX account manager to coordinate the onboarding.

MobileFuse provides:

  • One Publisher ID for your publisher account. That same ID is reused across every app in the account.
  • A Placement ID for each app placement and ad format you want to monetize.

Publish the MobileFuse app-ads.txt lines for your Publisher ID. These are the lines CloudX requires for MobileFuse. The App-ads.txt page in your CloudX dashboard shows the full list for your file.

Loading the app-ads.txt lines…

Publish the lines at https://yourdomain.com/app-ads.txt, where yourdomain.com is the developer website listed in the App Store or Google Play. Keep the existing entries for CloudX and other networks.

Step 2. Enable MobileFuse in CloudX and add the Publisher ID

Go to Bidders, select MobileFuse, click Enable, then click Confirm.

On the same MobileFuse page, enter the MobileFuse Publisher ID supplied during onboarding and click Save. This value is required and applies to every app in the CloudX account.

If MobileFuse is disabled, CloudX will not request bids from MobileFuse even if your mappings are correct.

After enabling, you can also enter Placement IDs from this same page: search for an app, select it, enter the MobileFuse Placement ID for each ad unit under Placements, and click Save. You can also configure the same values from the ad-unit pages in the next step.

Step 3. Configure CloudX ad units

Go to Ad Units and add the MobileFuse mapping below for each eligible ad unit.

CloudX fieldValue to enterRequired
MobileFuse Placement IDThe numeric MobileFuse Placement ID for that ad unit and formatYes
  • Match each Placement ID to the CloudX ad-unit format.
  • Use the Placement IDs MobileFuse supplied for the intended app placements.

There are no app-level MobileFuse fields. For iOS apps, CloudX looks up the numeric App Store ID that MobileFuse requires from the app’s platform and bundle ID.

Step 4. Add MobileFuse line items

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

  • Target Banner, MREC, Interstitial, Rewarded, or Native ad units
  • Repeat the setup for each ad unit where MobileFuse should bid

Step 5. Finish app integration

Complete the integration and adapter setup for your platform:

In app code:

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

Step 6. Test and validate

MobileFuse returns test ads to CloudX test devices, so you can check every format before live traffic starts.

  1. Register your device as a CloudX test device: go to Dev Tools → Test Devices, add the device with the app in its scope, and turn on Test traffic.
  2. Test from the United States or Canada. CloudX does not request MobileFuse bids from other countries, including for test devices.
  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 MobileFuse wins with a test ad and that the ad renders.
  6. Turn off Test traffic and validate with live traffic from the United States or Canada.

No fill during a small live test can be normal and does not by itself indicate that the setup is broken.

Troubleshooting

MobileFuse is not bidding

Check the following first:

  • MobileFuse is enabled in the Bidders section
  • The required account-level MobileFuse Publisher ID is present
  • The ad unit has the correct numeric MobileFuse Placement ID, and the placement matches the ad-unit format
  • A MobileFuse line item exists for the ad unit
  • The user or test device is in the United States or Canada
  • The floor is below $30
  • The MobileFuse adapter is installed, so the CloudX SDK can collect the MobileFuse bid token
  • Your app-ads.txt file includes the MobileFuse lines from Step 1 with the correct Publisher ID
  • For iOS, the app is published on the App Store, so CloudX can look up the numeric App Store ID that MobileFuse requires

MobileFuse bids but the ad does not render

Check the following:

  • Your app is using the CloudX app_key, not a MobileFuse ID
  • Your app is loading the intended CloudX ad unit
  • The MobileFuse Placement ID belongs to the correct app placement and format
  • The MobileFuse adapter is installed and its platform requirements are complete
  • For Native ads on iOS, your app uses CloudX iOS SDK 3.12.0 or newer
  • Interstitial and Rewarded ads are shown only after they are ready

Demand is lower than expected

  • Confirm with MobileFuse that your Publisher ID, Placement IDs, and app-ads.txt lines are correct for your account.
  • Allow time for MobileFuse and its buyers to re-crawl the updated app-ads.txt file.
  • Validate with live traffic from the United States or Canada; test ads do not reflect live demand.

Mapping Reference

CloudX fieldInternal keyScope
MobileFuse Publisher IDpublisher_idAccount
MobileFuse Placement IDplacement_idAd unit

The numeric iOS App Store ID is looked up from the CloudX app’s platform and bundle ID. It is not a publisher-entered MobileFuse field.