Delivery Rules

When the SDK requests an ad for a unit, the server applies the checks below in order. If no campaign passes, the request returns empty and the reason is reported to the SDK.

• The unit must be active, the app verified, and the app key, bundle ID and platform must match the unit.
• There must be a campaign and creative approved by the publisher in this app for the unit's format.
• For banners, a creative of the requested size must exist.
• The campaign's country, platform and date targeting must match the request.
• A price must be set for the app and format.
• The campaign's total and daily budget and the advertiser's available balance must suffice.
• The device must not have reached the campaign's daily frequency cap.

Pricing

The price is fixed per app and format; it does not depend on country or an auction. Advertisers see their CPM in the catalog and publishers see the CPM they are paid in the dashboard. Price changes can be scheduled; the price in effect at impression time applies.

Budget and balance

Each impression records spend equal to one thousandth of the advertiser CPM. Spend is counted in real time and posted to the wallet every few minutes. When an advertiser's balance runs out, their campaigns in that currency stop receiving impressions without changing status and resume automatically after a top-up.

Country and device

• The country is determined from the user's connection. If it cannot be determined, country-targeted campaigns don't match.
• For frequency capping, the device is recognized by its advertising ID if the user allowed tracking, otherwise by an anonymous hash. Raw identifiers are not stored.