Create an offer campaign

Open Advertiser → Offers → Campaign Studio → New campaign. The campaign begins as a DRAFT and cannot appear in publisher inventory until it passes review and is made LIVE.

The stepper labels are Goal, Experience, Rewards, and Delivery. Saving a draft does not waive review requirements. Use the template selector to prefill common patterns, then inspect every value: templates are examples, including their financial amounts.

1. Choose the owner and outcome

Select the advertiser profile that will own and fund the campaign. With one profile, the console can preselect it; with several, check the selection before saving. Choose a generic template or a custom conversion. Templates are editable starting points.

Choice	Use it when
Verified signup	A new account or registration must be confirmed
Purchase	A paid order or subscription must be verified
Install	An app install plus the required first action is confirmed
Engagement	A tutorial, level, or task is completed
Custom event	Your server verifies another measurable outcome
Multiple reward milestones	A user can earn at several separately verified stages

Use a single advertised platform: web, Android, or iOS. Add the actual website or store URL and package/property identifier. Campaign readiness requires a validated advertised asset. Managed partner campaigns and provider-managed tracking are administered separately; self-service advertisers use direct tracking.

2. Write the user experience

Provide an internal campaign name and a clear public title, benefit-led headline, description, button text, exact completion requirements, user instructions, and disclosure. State any purchase, subscription, eligibility, verification delay, or pending reward condition before the user starts. Add a support URL where available.

The destination, preview, support, icon, hero, and gallery URLs must use HTTPS. Direct S2S campaigns require {click_id} in the destination URL:

https://advertiser.example/join?rr_click_id={click_id}

Supported destination macros include {click_id}, {external_user_id}, {offerwall_user_id}, {country}, and {campaign_id}. Preserve the resolved click ID on your server; it is required for attribution. Test the destination with a development launch rather than replacing macros by hand.

Add a validated creative record for the advertised asset. A draft can be saved without every review prerequisite, but readiness requires at least one validated creative and a validated advertised asset. Current creative upload is development-only; see creative and review before assuming a production account can upload its own files.

3. Define milestones and financial terms

Every goal needs a user-facing name and a unique, stable Tracking event ID (externalGoalId). Send that exact value as goal_id in the postback. Enter gross advertiser revenue and publisher payout for each goal; the payout must not exceed gross revenue. Optional controls include pending minutes, completion window, repeatability, prerequisites, and availability windows. A prerequisite may only reference an earlier goal ID.

A multi-reward campaign should describe each step separately. For an install plus tutorial, for example, use distinct IDs such as install_verified and tutorial_complete; do not reuse one event ID for both outcomes. RapidoReach stores money in integer micros internally and snapshots financial terms per revision.

4. Set targeting and budget

Choose countries, offer surfaces, eligible traffic sources, platform-specific devices and versions, schedule, total budget, daily or monthly caps, and conversions per user. Country codes are two-letter ISO codes. Optional US state targeting applies when the US or worldwide traffic is eligible. Browser version filters apply to web campaigns; OS version filters apply to mobile campaigns. Leave advanced filters unset unless you can verify enough matching traffic remains.

See targeting and budget for field behavior and launch checks.

5. Save and review

Save the draft, open its Readiness panel, and resolve every reported reason. Set up a direct postback credential, confirm the click ID in the destination, and run an end-to-end development test. Then choose Submit for review. An administrator approves and launches an eligible campaign; advertiser owners can pause and later resume an approved campaign.

Editing creates a new immutable revision and returns the campaign to DRAFT. Existing clicks and conversions keep the financial terms captured when they started. Check the new revision, tracking, and readiness before resubmitting.

Next: Targeting and budget, assets and review, then S2S tracking.

Field-by-field decisions

Step	Control	Decision to make
Goal	Campaign owner	Choose the advertiser profile that owns and funds the offer. A normal advertiser sees only owned profiles.
Goal	Offer structure, objective, task type	Choose one verified conversion or separately rewarded milestones; match the task type to the user action. Publisher slots may exclude task types. Managed partner structures require administrator access.
Goal	Platform and property	Select one web, Android, or iOS property, enter the public store or website URL and matching identifier, then Validate property.
Goal	Campaign type and eligible sources	Choose CPI for install, CPA for action, or CPE for an engagement milestone. Leave sources unrestricted for compatible traffic or narrow them only when required.
Experience	Title, headline, CTA, description	Explain the reward and action before the user leaves the offerwall. Avoid an instant-reward promise when verification is pending.
Experience	Requirements, instructions, disclaimer, support	State every eligibility condition, purchase, subscription, verification delay, and deadline. Match the steps your server actually checks.
Experience	Destination and creative	Preserve {click_id} through redirects. Attach validated creative belonging to the advertised asset; inspect it at mobile width.
Rewards	Bid, budget, caps	Review USD bid and total budget; set daily, monthly, next-month, and per-user limits for the possible combined cost of multiple goals.
Rewards	Goal name and tracking event ID	Give each milestone a clear user-facing name and a stable unique ID sent as goal_id in callbacks.
Rewards	Gross revenue, payout, dependencies	Payout cannot exceed revenue. A prerequisite can reference only an earlier goal; align availability, completion, pending time, and repeatability with the actual task.
Delivery	Placement, country, schedule, device	A user must match both campaign rules and publisher slot policy. Optional US state, manufacturer, OS, and browser filters can sharply reduce supply.
Delivery	Tracking and security	Select an available certified tracking route, include {click_id} in the tracking link, and use an IP allowlist only when your callback egress addresses are stable.
Delivery	UTC day-parting and attribution	Convert local hours to UTC and set an attribution window long enough for the verified event. Disclose when real payment is required.

Optional ROAS targets for D1/D7/D14/D30/D60/D90 and the IAP/IAA ratio are planning KPIs; they do not prove a conversion. The worked examples show how to put these decisions together. The campaign API reference gives the server request fields and readiness response.