OverviewAndroidiOSUnityReact NativeFlutterCLIAPIMCPDemandAd FormatsDashboardChangelog

Vrtcal (BETA)

Use this guide to enable Vrtcal bidding in CloudX.

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

Vrtcal 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 Vrtcal SDK or adapter to add to your app.

Overview

Vrtcal has no credentials or network mappings to configure in CloudX: no Vrtcal account ID, app ID, or placement ID. Enabling the bidder and adding line items is the entire CloudX setup.

Supported ad formats through CloudX

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

Native is not supported yet. Banner and MREC use banner creatives; Interstitial and Rewarded use video creatives.

Step 1. Confirm app-ads.txt requirements

Ask your CloudX account manager whether Vrtcal requires app-ads.txt entries for your publisher account before enabling live traffic. If entries are required, Vrtcal or CloudX will provide the current lines for your account.

Publish any supplied 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 Vrtcal in CloudX

Go to Bidders, select Vrtcal in the bidder list, and click Enable.

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

Step 3. Add Vrtcal line items

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

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

Step 4. Test and validate

Vrtcal does not provide a formal RTB test mode for CloudX. Use controlled live traffic after any required app-ads.txt updates are live.

  1. Use a physical device. Register it under Test Devices with Test traffic off and Debug Mode on for diagnostics.
  2. 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.
  3. Request ads from each Banner, MREC, Interstitial, and Rewarded ad unit where Vrtcal is enabled.
  4. Confirm that Vrtcal participates or wins where expected and that returned ads render correctly.
  5. Compare impressions and revenue with Vrtcal 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

Vrtcal is not listed

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

Vrtcal is not bidding

Check the following first:

  • Vrtcal is enabled under Bidders
  • A Vrtcal line item exists for the ad unit
  • The ad unit is Banner, MREC, Interstitial, or Rewarded (Native is not supported)
  • Any required app-ads.txt lines are published and the store listing points to that developer domain

Vrtcal 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 is on a current CloudX SDK version
  • The ad unit is configured as Banner, MREC, Interstitial, or Rewarded

Vrtcal 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 your CloudX account manager that any required Vrtcal app-ads.txt entries are present and current.
  • Allow time for buyers to re-crawl the updated file.
  • Validate with controlled live volume because Vrtcal does not provide RTB test demand through CloudX.