Integration

AppHarbr ad-quality connector for CloudX iOS SDK. Runs AppHarbr ad-quality protection on CloudX ads with no publisher glue code.

Connectors pass data between the CloudX SDK and another product. The AppHarbr connector runs AppHarbr ad-quality protection on the ads CloudX loads. When AppHarbr blocks an ad, CloudX does not show it. Add the dependency and protection is automatic — the connector registers itself with the CloudX SDK at load time.

Installation

CocoaPods

pod 'CloudXAppHarbrConnector', '~> 1.38.3.0'

pod install --repo-update

No code changes are required. The connector never initializes AppHarbr; it uses your existing AppHarbr setup and API key.

Swift Package Manager

Add the package in Xcode (File > Add Package Dependencies) and add the CloudXAppHarbrConnector product to your app target:

https://github.com/cloudx-io/cloudx-ios-swift-package-connector-appharbr

• Latest package version: 1380300.0.0
• Add -ObjC to Other Linker Flags on your app target, so the connector registers itself at load time.

Manual registration

The pod sets -ObjC on your target so the connector’s +load runs in the host app and it self-registers. If your build does not link with -ObjC, register it once before or after initializing the CloudX SDK:

#import <CloudXAppHarbrConnector/CloudXAppHarbrConnector.h>

CloudXAppHarbrConnectorRegister();

import CloudXAppHarbrConnector

CloudXAppHarbrConnectorRegister()

Requirements

• iOS 13 or newer.
• CloudXCore 3.11.0 or newer.
• Your app already integrates and initializes the AppHarbr SDK with your own AppHarbr API key. The connector never bundles or initializes AppHarbr; CocoaPods dedupes the dependency against your app’s existing AppHarbrSDK, so your runtime version is the one used.
• A supported AppHarbr SDK version: AppHarbrSDK 1.38.3 or newer.

What gets analyzed

The connector sends each ad CloudX loads to AppHarbr for analysis before your app is told the ad loaded. If AppHarbr allows the ad, it loads as usual. If AppHarbr blocks the ad, CloudX does not show it, and your app receives a normal load failure.

If a banner or MREC is blocked after it is already on screen, your app receives didFailToLoadAd and CloudX refreshes the slot with a new ad.

If AppHarbr is not ready, or cannot analyze an ad, the ad is shown. Protection fails open and never blocks a load on its own.

Known limitations

• Ads from CloudX demand, which the CloudX SDK renders itself, are not analyzed yet. AppHarbr is adding support for them.
• Mintegral native ads are not analyzed yet. A future CloudX release adds them.
• Moloco native ads are not analyzed until a future AppHarbr SDK release.

Ads that are not analyzed load and show as usual.

Compatibility

Support

For support, contact support@cloudx.io