Thunder Monetize (BETA)

Use this guide to enable Thunder Monetize bidding in CloudX.

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

Thunder Monetize 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 Thunder Monetize SDK or adapter to add to your app. Thunder Monetize requires CloudX Android SDK 4.9.0 or newer and CloudX iOS SDK 3.8.0 or newer.

Thunder Monetize buys your inventory directly: you need your own agreement with Thunder Monetize, and Thunder Monetize pays you for the impressions it buys.

Overview

Thunder Monetize has no credentials or network mappings to configure in CloudX: no Thunder Monetize account ID, app ID, or placement ID. After onboarding, you add the Thunder Monetize app-ads.txt lines, enable the bidder, and add line items.

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 both Thunder Monetize vendors to the CMP’s vendor list: THUNDER MONETIZATION PTE. LTD. (IAB TCF vendor ID 1580) and HONGKONG THUNDER SOLUTION LIMITED (IAB TCF vendor ID 1579). After you add them, make sure your CMP asks existing users for consent again, so their consent strings include Thunder Monetize.

Step 1. Complete Thunder Monetize onboarding

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

Provide Thunder Monetize 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

Add the Thunder Monetize lines below to your app-ads.txt file. These are the lines CloudX requires for Thunder Monetize. 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 your CloudX DIRECT line and the existing entries for other networks, including any Thunder Monetize lines already in your file. If Thunder Monetize gives you app-ads.txt lines for your own account, add those as well.

Step 2. Enable Thunder Monetize in CloudX

Go to Bidders, select Thunder Monetize, click Enable, then click Confirm.

There is nothing to enter: Thunder Monetize has no account-level credentials, app mappings, or placement mappings in CloudX. If Thunder Monetize is disabled, CloudX will not request bids from Thunder Monetize for any of your inventory.

Step 3. Add Thunder Monetize line items

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

Use bidder Thunder Monetize
Target Banner, MREC, Interstitial, or Rewarded ad units
Repeat the setup for each ad unit where Thunder Monetize should bid

After the line items are live, tell your Thunder Monetize contact. Thunder Monetize reviews the first requests from your apps and then turns on its demand.

Step 4. Test and validate

Thunder Monetize does not provide a formal RTB test mode for CloudX. Use controlled live traffic after Thunder Monetize confirms that its demand is on for your apps.

Use a physical device. Register it under Test Devices with Test traffic off and Debug Mode on for diagnostics.
Build and run the app with the CloudX app_key and the correct CloudX ad unit identifiers. Do not start the SDK session in test mode.
Request ads from each Banner, MREC, Interstitial, and Rewarded ad unit where Thunder Monetize is enabled.
Confirm that Thunder Monetize participates or wins where expected and that returned ads render correctly.
Compare impressions and revenue with Thunder Monetize after traffic begins flowing.

With Test traffic on, registered devices receive test ads and their data is excluded from revenue reports. iOS Simulator sessions and SDK test-mode sessions remain test requests even with Test traffic off. Use live traffic for the ad and revenue checks above.

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

Troubleshooting

Thunder Monetize is not listed

Thunder Monetize is currently beta in CloudX. Contact your CloudX account manager to request access if it is not visible under Bidders.

Thunder Monetize is not bidding

Check the following first:

Thunder Monetize is enabled under Bidders
A Thunder Monetize line item exists for the ad unit
The ad unit is Banner, MREC, Interstitial, or Rewarded (Native and App Open are not supported)
Thunder Monetize has confirmed that the app is set up on its side
For iOS, the app is published on the App Store, so CloudX can send Thunder Monetize the app’s numeric App Store ID
For users where GDPR applies, your CMP includes Thunder Monetize (vendor IDs 1580 and 1579); see Consent for GDPR traffic

Thunder Monetize 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.9.0 or newer, or CloudX iOS SDK 3.8.0 or newer

Thunder Monetize 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 Thunder Monetize that every app you enabled is set up on its side.
Check the price floors on your Thunder Monetize line items. Thunder Monetize can only win when its bid clears the line item’s floor.
If GDPR traffic gets no Thunder Monetize bids, check that your CMP lists Thunder Monetize and that existing users have been asked for consent again.
Validate with controlled live volume because Thunder Monetize does not provide RTB test demand through CloudX.