Partner Pricing
Turn rewards into a revenue engine
Scope cashback, deal, play, movement, or referral quests — or test a rewards layer against defined engagement and revenue baselines in your own app.
Acquire users who complete, not click: rewarded CPA campaigns with fraud screening and postback validation built in, so you pay for verified actions.
Published prices are planning inputs. Campaign funding, taxes, invalid-traffic adjustments, cancellation, refunds, support, service levels, data terms, and availability require checkout terms or a written agreement.
Advertiser Starter
Planning tier for scoped rewarded CPA campaigns. Placement, validation, reporting cadence, support, and market availability are confirmed at checkout or in a written order.
- Eligible CPA and offerwall placement, when configured
- Provider- and market-specific offer distribution
- Validation controls defined in campaign terms
- Reporting cadence defined in campaign terms
- Support channel defined at checkout
Growth Partner
Planning tier for a larger scoped campaign. Optimization, targeting, service ownership, dashboards, and support depend on the written order and configured deployment.
- Everything in Advertiser Starter
- Eligible movement, play, and sharing mechanics
- Configured targeting and experiment scope
- Service owner only when included in the order
- Dashboard and API scope confirmed before launch
- Support hours and response targets are contract-specific
Publisher Rewards Layer
Scope a rewards layer for an eligible app. Revenue share, funding, reward methods, validation, compliance responsibilities, and availability require a written pilot agreement.
- Configured earn placement (button, popup, or hub)
- Neutral points with eligible methods shown in-product
- Eligible offers and games via Agent Skills
- Provider and publisher responsibilities defined in writing
- Revenue terms defined in the pilot agreement
Enterprise
Request a scoped enterprise deployment. Account, reward, identity, service, infrastructure, and support commitments exist only when included in a signed order.
- Scoped points and reward-method design
- Connected accounts only when configured
- Provider coverage and settlement terms confirmed by market
- Identity and fraud responsibilities defined per deployment
- Service levels, SSO, and infrastructure only when contracted
- Engineering support only when included in the order
Agencies: any multi-brand pricing exists only in a signed order for isolated client Brand/App IDs. Memory is not shared automatically. Agency terms
Building an app or game? Publisher reward-layer terms are confirmed in the written pilot scope — see the developer docs
Provider coverage, payout methods, fraud controls, identity-verification requirements, campaign terms, support, and service levels are confirmed for each market and written agreement. No universal coverage or outcome is promised. Security & data handling details are on the partners page.
Memory continuity is available only for a connected deployment after per-App credentials, subject identity, consent, and the eligible event scope are configured. It is never automatic across accounts, brands, apps, or customers.
Not sure which plan fits?
Book a 20-minute demo and we will map the right rewarded mechanics to your goals — retention, revenue, or both.
Book a demo