Verve

Use this guide to configure Verve bidding in CloudX.

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

For platform-specific Verve adapter requirements, see:

The Verve 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 and CloudX iOS SDK 3.5.0 or newer.

Overview

Use the following values:

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

CloudX collects the Verve bid token through the Verve 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

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

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

Verve sends you an onboarding document with:

  • A Publisher ID for your publisher account (also called the app token). The same Publisher ID is used for every app in the account.
  • The Verve app-ads.txt lines for your account.

Create Zone IDs with the Verve account management team. You need a Zone ID for each app and ad format you want to monetize.

Publish every app-ads.txt line in your Verve onboarding document. CloudX checks for at least the line below. 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 Verve in CloudX and add the Publisher ID

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

On the same Verve page, enter your Publisher ID in Verve Publisher ID and click Save. This value is required and applies to every app in the CloudX account.

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

After enabling, you can also enter Zone IDs from this same page: search for an app, select it, enter the Verve Zone 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 Verve mapping below for each eligible ad unit.

CloudX fieldValue to enterRequired
Verve Zone IDThe Verve Zone ID for that app and ad formatYes
  • Match each Zone ID to the CloudX ad-unit format.
  • Use the Zone IDs you created with the Verve account management team for that app.

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

Step 4. Add Verve line items

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

  • Target Banner, MREC, Interstitial, Rewarded, or Native ad units
  • Repeat the setup for each ad unit where Verve 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 Verve Publisher IDs or Zone IDs into app code
  • For Interstitial and Rewarded ads, call show() only after the ad is ready

Step 6. Test and validate

Verve 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. Build and run the app with the CloudX app_key and the correct CloudX ad unit identifiers.
  3. Request an ad from each mapped ad unit.
  4. Confirm that Verve wins with a test ad and that the ad renders.
  5. Turn off Test traffic and validate with live traffic.

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

Troubleshooting

Verve is not bidding

Check the following first:

  • Verve is enabled in the Bidders section
  • The required account-level Verve Publisher ID is present
  • The ad unit has the correct Verve Zone ID, and the zone matches the ad-unit format
  • A Verve line item exists for the ad unit
  • The Verve adapter is installed, so the CloudX SDK can collect the Verve bid token
  • Your app-ads.txt file includes the Verve lines from your onboarding document
  • For iOS, the app is published on the App Store, so CloudX can look up the numeric App Store ID that Verve requires

Verve bids but the ad does not render

Check the following:

  • Your app is using the CloudX app_key, not a Verve ID
  • Your app is loading the intended CloudX ad unit
  • The Verve Zone ID belongs to the correct app and format
  • The Verve adapter is installed and its platform requirements are complete
  • Interstitial and Rewarded ads are shown only after they are ready

Demand is lower than expected

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

Mapping Reference

CloudX fieldInternal keyScope
Verve Publisher IDpublisher_idAccount
Verve Zone IDzone_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 Verve field.