Skip to content

Commit 23be956

Browse files
authored
Merge pull request #388 from dubinc/bounty-performance-update
Performance logic updated
2 parents 6ef9cc4 + ced5429 commit 23be956

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

help/article/program-bounties.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ When setting the logic for a performance bounty, you can choose from several opt
8585

8686
**Scope** determines how performance is tracked over a specific period.
8787

88-
- **New** - Tracks only performance generated after the bounty is created. For example, if you set a bounty that rewards partners after 10 leads, each partner must generate 10 new leads after the bounty goes live, regardless of how many leads they had before.
88+
- **New** - Tracks only performance generated after the bounty starts. For example, if you set a bounty that rewards partners after 10 leads, each partner must generate 10 new leads after the bounty goes live, regardless of how many leads they had before. For revenue-based bounties, only revenue from customers whose first sale happens after the bounty starts is counted.
8989
- **Lifetime** - Counts performance across the partner’s entire lifetime. For example, if you set a bounty that rewards after 10 leads, any partner who already has at least 10 leads will immediately qualify for the reward.
9090

9191
**Activity** determines which metric is tracked for the bounty. Revenue and commissions require a dollar amount to be set.

0 commit comments

Comments
 (0)