Skip to main content
Version: v2

Offer targeting and budget

Targeting determines which publisher sessions can see and launch an offer. Set the broadest audience that is genuinely eligible for the advertised action; each additional rule can reduce available inventory.

Geography, platform, and placement​

  • Countries: add two-letter country codes. A country is required for review. Check legal and service availability before selecting a market.
  • Advertised platform: choose exactly one of web, Android, or iOS. The selected store or website asset must be validated.
  • Placements: choose where the offer may appear, such as an offerwall, app inbox, or web landing surface. Publisher ad-slot policy can further exclude a campaign.
  • Traffic sources: restrict Android, iOS, or desktop supply only when needed. A blank traffic-source selection allows compatible sources.
  • Device and software rules: mobile campaigns may use device type, manufacturer, and OS version; web campaigns may use browser version. A minimum version above a maximum version is invalid.
  • US states: use only when targeting the US or worldwide traffic. An empty state list does not add a state restriction.

Publisher slot country policy, campaign status, the schedule, cap availability, consent, and SDK capability all affect final eligibility. A campaign that is LIVE can still have no matching inventory.

Diagnose an empty feed​

Check the intended user from the outside in: is the campaign LIVE and within schedule; is budget reserved and every relevant cap open; does the user match country, advertised platform, traffic source, device, OS or browser range, and any state or manufacturer rule; does the publisher placement and ad slot permit the task type and surface; and is offer delivery enabled for that environment? Asset validation or campaign approval alone does not prove that a particular placement can show the offer. Use a matching development session and the offer feed response to find the failed boundary.

Schedule and spend​

Enter a positive total budget and optional start/end dates. The end must be after the start. Daily, monthly, and next-month conversion caps limit the number of outcomes; a per-user cap limits repeated conversions. Optional UTC day-parting restricts delivery to defined windows. Review the timezone when scheduling around a local launch.

Both survey and offer campaigns use the advertiser's shared balance. At launch, the service reserves available budget; insufficient available funds or an exhausted budget prevents new delivery. Compare the budget with the gross revenue of all possible goals, particularly in multi-reward campaigns. Pausing or ending releases unused reserved budget under the campaign ledger rules, while existing audited conversions remain recorded.

For a two-goal offer, estimate the upper bound as eligible users multiplied by the sum of both goals' gross revenue. Compare it with the total budget and conversion caps. This is a planning estimate: read actual reservation, acceptance, pending events, reversals, and pacing from the campaign ledger and reports. UTC day-parting uses minute ranges within selected UTC days; convert local launch hours before saving.

Before submission​

Check the Readiness panel for a positive budget, countries, goal, validated asset and creative, certified tracking partner, and required tracking credential. Test at least one matching country and platform, a no-fill case, and a user who should be excluded. See submit and operate for status and reports.