Campaigns

Who it is for

A campaign is for a client who wants several testers on one release and will set the brief, eligibility, and compensation. It is not a monthly Company Plan and TestNexo does not operate it as a managed service.

What you submit

• The App and Build you want tested
• The testing objective
• Who should participate: devices, platforms, languages, or markets
• Tasks, evidence, and deliverables
• Compensation per tester and how many testers you need

How a campaign runs

1. Create your company account and add the App
2. Set the brief, eligibility, and compensation
3. Accept the campaign terms and fund it before recruiting starts
4. Eligible testers apply and you admit each one
5. Each tester accepts their own terms before work starts
6. Testers submit results
7. You review submissions
8. Tester compensation follows approval of that participant

What you control

You set the objective, the access method, admission, and whether a submission is acceptable.

What TestNexo provides

Discovery, the agreement record, messaging, payment coordination, moderation, and disputes. TestNexo does not operate the campaign for you.

Devices and access

Coverage comes from testers’ real devices, not an automated device farm. Private builds and links go to assigned participants. Google Play and Apple policies still apply if you distribute through those systems. TestNexo does not guarantee store approval.

Payment protection

You fund the campaign before testing begins. Tester rewards come from that funded work. Unused reward amounts and refunds are described on the Refund Policy. Read Payment Protection for the sequence.

How this differs from hiring one tester

Direct hiring is one agreement, one tester, and one submission. A campaign is a client-defined group around a release. Group testing uses this same campaign model.

Common questions

Company Plans do not include a campaign. You configure and fund each campaign. Testers do not need Tester Plus to apply.