# Custom outcome

> People earn their reward for an outcome you define, confirmed by your system or by a reviewer. Private quests only.

Source: https://dashboard.adquest.io/docs/dashboard/quests/custom · Audience: Publishers · Section: Quests

## Set it up

1. Choose **Private** and your platform, then **Custom** under **Bring them back**, then **Use this quest**.
2. In the **Rules** section, write the **Outcome label**, such as Finish onboarding.
3. Under **Evidence type**, choose how it is proven, then fill in its field.
4. White Label platforms: under **How it starts**, choose **Starts on its own** or **User taps Start**. A quest that starts on its own is already running when the person opens your app, and the widget shows **Continue**.
5. With **User taps Start**, open **Time limit** and keep **No deadline** or choose **Set a deadline** (15 minutes to 30 days). When it passes, the try ends; starting again gives a new deadline. A quest that starts on its own has no time limit.
6. Fill in **Reward** and **Schedule**, read the instructions in the preview as a newcomer would, and choose **Publish Quest**.

| Evidence type | You fill in | What happens |
| --- | --- | --- |
| **URL callback** | **Callback URL**: an https address on your system. | AdQuest asks that address whether the person qualifies, and pays when it says yes. |
| **Manual review** | **Review instructions**: what people must send. | People send their proof and a reviewer approves or rejects it. |

## Before you publish

- For a URL callback, check with your developer that the address answers.
- For a manual review, make the instructions clear enough to judge each submission.

## What your developer does

For a URL callback, your developer builds the address that answers AdQuest. A manual review needs no code.

- [Custom outcome for developers](https://dashboard.adquest.io/docs/quest-evidence/custom): The callback request and the review flow.
