OverviewAndroidiOSUnityReact NativeFlutterCLIAPIMCPDemandAd FormatsDashboardChangelog

Smadex

Use this guide to configure Smadex bidding in CloudX.

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

Smadex is a server-side bidder: CloudX requests bids on the server and renders winning creatives with the CloudX SDK’s built-in renderer. There is no Smadex SDK or adapter to add to your app. Smadex requires CloudX Android SDK 4.1.4 or newer and CloudX iOS SDK 3.6.0 or newer.

Overview

Unlike SDK-based networks, Smadex has no credentials to configure: no account ID, no app ID, and no placement IDs. After onboarding, enabling the bidder and adding line items is the entire CloudX setup.

Smadex buys your inventory directly: you need your own agreement with Smadex, and Smadex pays you for the impressions it buys. Smadex also buys through CloudX Exchange, which needs no agreement with Smadex and no setup on this page.

Supported ad formats:

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

Native and App Open are not supported.

If your app collects consent through an IAB TCF consent management platform (CMP), add Smadex (IAB TCF vendor ID 161) to the CMP’s vendor list. Smadex does not bid on requests whose consent string does not include vendor 161. After you add Smadex, make sure your CMP asks existing users for consent again, so their consent strings include it.

Step 1. Complete Smadex onboarding

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

Provide Smadex with the apps you plan to enable:

  • Android package names, such as com.example.app
  • Numeric App Store IDs for iOS apps, such as 6448392061

Smadex does not need its own app-ads.txt entries. Keep your CloudX DIRECT line in place; see app-ads.txt.

Step 2. Enable Smadex in CloudX

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

There is nothing to enter: Smadex has no account-level credentials. If Smadex is disabled, CloudX will not request bids from Smadex for any of your inventory.

Step 3. Add Smadex line items

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

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

Step 4. Test and validate

Use controlled live traffic after Smadex confirms your apps.

  1. Add your device as a CloudX test device so you can inspect CloudX behavior during validation.
  2. Build and run the app with the CloudX app_key and the correct CloudX ad unit identifiers.
  3. Request ads from each Banner, MREC, Interstitial, and Rewarded ad unit where Smadex is enabled.
  4. Confirm that Smadex participates or wins where expected and that returned ads render correctly.
  5. Compare impressions and revenue with Smadex after traffic begins flowing.

CloudX test-device configuration helps you validate your integration, but it does not make Smadex return test ads. No fill during a small test can be normal and does not by itself indicate that the setup is broken.

Troubleshooting

Smadex is not bidding

Check the following first:

  • Smadex is enabled in the Bidders section
  • A Smadex line item exists for the ad unit
  • The ad unit is Banner, MREC, Interstitial, or Rewarded (Native and App Open are not supported)
  • Smadex has confirmed that the app is set up on its side
  • The user is in a country Smadex serves; on line items with country targeting, the Bidders picker shows whether Smadex is eligible
  • For iOS, the app is published on the App Store, so CloudX can look up the numeric App Store ID that Smadex requires
  • For users where GDPR applies, your CMP includes Smadex (vendor ID 161); see Consent for GDPR traffic

Smadex bids but the ad does not render

Check the following:

  • Your app is using the CloudX app_key and loading the intended CloudX ad unit
  • Your app uses CloudX Android SDK 4.1.4 or newer, or CloudX iOS SDK 3.6.0 or newer

Smadex creatives render through the CloudX SDK’s built-in renderer. If a specific creative fails consistently, contact CloudX support with the app, ad unit, and approximate time of the failure.

Demand is lower than expected

  • Confirm with Smadex that every app you enabled is set up on its side.
  • If GDPR traffic gets no Smadex bids, check that your CMP lists Smadex and that existing users have been asked for consent again.
  • Validate with controlled live volume because CloudX test devices do not receive Smadex test demand.