Native

Set up standalone native, native-in-banner, and native-in-MREC, and see which networks support each

You can sell native demand in three ways. Pick your case first. The setup differs for each one.

You wantCloudX ad unitNetwork placement to createCloudX bidderCreative types
Standalone native: native ads in your own layoutNativeNativeThe network, for example MetaImage and video
Native-in-banner: native demand in a 320x50 banner slotBannerNative (for Meta: Native Banner)The network’s Native bidder, for example Meta NativeImage only
Native-in-MREC: native demand in a 300x250 MREC slotMRECNativeThe network’s Native bidder, for example Meta NativeImage and video

Native-in-banner and native-in-MREC need no new app code. They serve through the Banner or MREC ad unit you already load. Your network adapter must meet the minimum version.

Set up native-in-banner and native-in-MREC

Native-in-banner and native-in-MREC add a second bidder to your Banner or MREC ad unit. It competes in the same auction as the network’s regular banner bidder, and the higher bid wins.

Check your adapter version

Find each network in the network setup reference. Update the adapter in your app if it is older than the minimum. An older adapter can win the auction but cannot render the ad, so the slot stays empty.

Create native placements in the network dashboard

Create one native placement for each slot size. Use the placement type in the network setup reference.

  • For a 320x50 Banner, select image only in the network dashboard. Never select video. A 320x50 slot cannot play video, so CloudX drops video bids and you lose that fill.
  • For a 300x250 MREC, select image and video. Video plays in MREC slots and brings more demand.

Keep the two sizes in separate placements, so each one keeps its own setting.

Enable the Native bidder

Go to Bidders. Enable the network’s Native bidder, for example Meta Native. It is a separate entry from the regular network, for example Meta, and it is off by default.

If the Native bidder is not listed in Bidders, ask your CloudX account manager to enable it for your account.

If it asks for account-level or app-level IDs, enter the same values you use for the regular network.

Map the native placement ID

Go to Ad Units and open the Banner or MREC ad unit. Under Network mapping, find the row for the Native bidder, for example Meta Native. Enter the native placement ID from step 2.

The Native row is separate from the regular row. Do not copy the banner placement ID into it.

Add the Native bidder to line items

In Manual mode, add the Native bidder to the line items on that Banner or MREC ad unit. Without a line item, CloudX does not request bids from it.

Under Dynamic Pricing, line items are optional. The Native bidder bids unless you add it to Excluded bidders.

To confirm it works, filter reporting by the Native bidder, for example Meta Native, and look for requests and impressions.

Set up standalone native

Standalone native uses a Native ad unit and renders the ad in your own layout.

  1. In the network dashboard, create a Native placement. Image and video are both fine. For Meta, a Native Banner placement also works on iOS; see Meta has two native placement types.
  2. In CloudX, map that placement ID to the regular network row on the Native ad unit, for example Meta. Do not use the Native bidder.
  3. In Manual mode, add the regular network bidder to the ad unit’s line items. Under Dynamic Pricing, make sure it is not in Excluded bidders.
  4. In your layout, bind a visible media container. Some networks count an impression only when their media view is on screen.

For layout and code, see the Android, iOS, and React Native Native pages.

Meta has two native placement types

Meta is the only network with a separate Native Banner placement type in addition to Native. A Native Banner ad has an icon, title, text, and call to action, with no media view. Every other network has one Native placement type, which you use for all three cases.

Meta placement typeNative-in-banner (320x50)Native-in-MREC (300x250)Standalone native
Native Banner✓—✓ iOS only
Native—✓✓

For standalone native with a Native Banner placement, your layout needs no media view. Bind the icon view instead; Meta counts the impression only when the icon is on screen.

Network setup reference

Each network has its own placement types and minimum adapter version. Use this table for steps 1 and 2 above.

Network320x50 Banner placement300x250 MREC placementStandalone native placementMinimum Android adapterMinimum iOS
Meta Audience NetworkNative BannerNativeNative6.21.0.2SDK 3.4.0
MolocoNative, image onlyNative, image and videoNative4.9.0.1, or 3.12.1.0 for Moloco SDK 3.12SDK 3.4.0
MintegralNative (Custom Rendering), image onlyNative (Custom Rendering)Native (Custom Rendering)17.1.81.1, with SDK 4.2.0Adapter 8.1.7.1
PangleNative, image onlyNativeNative8.3.0.4.2, with SDK 4.3.0SDK 3.5.0
InMobiNative, image onlyNative, image and videoNative11.3.0.0SDK 3.4.5
Digital TurbineNative, image onlyNativeNative8.4.7.1SDK 3.5.0
VerveNative, image onlyNativeNative3.8.1.1SDK 3.5.0
VungleNative, image onlyNativeNativeTemporarily disabledSDK 3.4.0

Meta. Use a Native Banner placement for native-in-banner and a Native placement for native-in-MREC. See Meta has two native placement types.

Mintegral. Always create native placements with Custom Rendering. Placements set to Auto Rendering do not serve. In the Native bidder’s row, enter both the Mintegral placement ID and its paired Ad Unit ID.

Vungle. Native-in-banner and native-in-MREC are temporarily disabled on Android. Vungle Native ad units work on both platforms. See the Vungle Android known issues.

Standalone native only. TaurusX, MobileFuse, Magnite, and AdMob estimated support standalone native. They do not support native-in-banner or native-in-MREC.

Troubleshooting

The Native bidder gets no requests

Check these in order:

  1. The app runs an adapter at or above the minimum version.
  2. The Native bidder is enabled in Bidders. If it is not listed there, ask your CloudX account manager to enable it.
  3. The Banner or MREC ad unit has a placement ID in the Native bidder’s row.
  4. In Manual mode, the Native bidder is on that ad unit’s line items. Under Dynamic Pricing, it is not in Excluded bidders.
  5. For Vungle on Android, native-in-banner and native-in-MREC are temporarily disabled.
The Native bidder wins but shows no impressions or revenue
  • Meta: check the placement type. Use a Meta Native Banner placement for 320x50 Banner, and a Meta Native placement for MREC.
  • Mintegral: the placement must use Custom Rendering, not Auto Rendering.
  • Standalone native: bind a visible media container in your layout.
  • Any network: an adapter below the minimum version can win but not render.
Native fill on 320x50 dropped

Check that the 320x50 native placement is set to image only. CloudX drops native video bids for 320x50 slots.

Can I reuse my banner placement ID?

No. The Native bidder needs a native placement from the network. The regular row keeps your banner or MREC placement.

Does this work in Unity, Flutter, and React Native apps?

Yes. Native-in-banner and native-in-MREC serve through the Banner and MREC APIs on every platform. Only the Android and iOS adapter versions matter.

Supported networks

Android

NetworkStandalone nativeNative-in-bannerNative-in-MREC
Digital Turbine✓✓✓
InMobi✓✓✓
Magnite✓——
Meta Audience Network✓✓✓
Mintegral✓✓✓
MobileFuse✓——
Moloco✓✓✓
Pangle✓✓✓
TaurusX✓——
Verve✓✓✓
Vungle✓——
AdMob estimated (BETA) †✓——

iOS

NetworkStandalone nativeNative-in-bannerNative-in-MREC
Digital Turbine✓✓✓
InMobi✓✓✓
Magnite✓——
Meta Audience Network✓✓✓
Mintegral✓✓✓
MobileFuse✓——
Moloco✓✓✓
Pangle✓✓✓
TaurusX✓——
Verve✓✓✓
Vungle✓✓✓
AdMob estimated (BETA) †✓——