Mobile performance platform for CPA, CPI and CPL campaigns

Support outcome-based price models

Define the accepted event, the evidence required to accept it and when it becomes payable. Nexus offer settings include fixed-price or revenue-share terms, currency, advertiser and publisher payouts, event category and conversion-window controls. An event received from an advertiser is not automatically a settled publisher payment. Agree on pending, rejected and repeated-event handling before a source is approved.

• Offer identity, tracking destination and accepted event.
• Conversion window and pending/multiple-conversion policy.
• Advertiser payout, publisher payout, currency and reconciliation responsibility.

Apply offer and partner boundaries

Publisher access, traffic eligibility and caps are separate controls. Nexus exposes private offers, approval and terms requirements alongside geographic, device, carrier, SubID, domain and IP-range targeting. Daily and monthly limits can apply to clicks, conversions and revenue. A publisher who can see an offer is not thereby eligible for every traffic source, and an available cap does not override an offer’s conversion rules.

Illustrative postback: follow one event

In a fictional test, click demo-click-17 belongs to offer sample-install and publisher Cedar. The advertiser later reports event demo-event-42 as an installation. The integration test should verify the click-to-offer relationship, the agreed event, the conversion window and the resulting report state. These labels are illustrative records, not Nexus field names, endpoint parameters or a production API example. Use the actual partner contract to construct a request.

• Known click + accepted event + valid timing → check the configured acceptance or pending outcome.
• Unknown click or wrong offer → check the agreed rejection or investigation path.
• Same event delivered again → verify the agreed repeat-event behavior before counting it twice.

Test retries and conversion windows independently

A repeated delivery of one event is different from a second legitimate event on the same click. Document the event identifier, allowed event types and the intended multiple-conversion policy. Exercise an on-time event, an event outside the window, a delayed retry and a temporary endpoint failure. Authentication, acknowledgement, retry limits and duplicate handling are integration requirements to verify, not guarantees inferred from the presence of a postback URL.

Check the cap boundary before launch

For an illustrative test allocation of ten accepted events per day, prepare cases just below, at and above the agreed boundary. Confirm which status counts toward the cap, the timezone used for the reset and what happens to a late event or concurrent arrival. Ten is a fictional test value, not a recommended offer setting or included Nexus quota. Validate the implemented behavior with the configured offer and partner before routing production traffic.

Reconcile conversions with the commercial record

Use the same offer, publisher, period, currency and acceptance status on both sides. Nexus reports include valid/invalid conversions, advertiser and publisher payouts, profit and source details. Investigate a missing event by its click and event context before changing a payout. A useful handover records the sample cases, their expected outcomes, the reporting window and who resolves disagreements. No example in this guide is a customer result or an attribution guarantee.

Platform capacity is not the offer payout

An illustrative CPA configuration with 200,000 incoming clicks per day costs $1,000 per month, or $2,500 for the first full month including platform setup, with no optional add-ons. This is not a price per day, per conversion or a publisher payout. It is not a customer result or a promise of conversions.

• Purchased daily incoming-click capacity and an offer’s conversion cap are different limits. The ten-event example above explains an offer workflow, not the purchased platform capacity.
• Search uses daily searches, not CPA clicks. Do not convert either daily volume into a QPS entitlement.
• Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised.