Common Mistakes in Referral Program Descriptions
Why Tasks Fail — and How to Fix Them
Avoid vague reward wording and hidden conditions.
They reduce trust, lower conversion, and increase the number of disputed tickets.
Below are the most common mistakes that directly hurt task performance and create problems for both advertisers and performers.
❌ 1. Vague Description of the Expected Result
Bad Example
“Register and get paid.”
What’s Wrong
This wording is too unclear.
It does not explain:
- what exactly counts as completion;
- which result must be achieved;
- how the result will be checked;
- what proof must be submitted.
As a result, performers may complete the task differently, and disputes may appear during moderation.
Better Examples
“Create an account and reach the ‘Account Created’ page.”
“Confirm your email and show the success page.”
“Register through the link, log in to your account, and submit a screenshot of the dashboard.”
❌ 2. Hidden Conditions
The Problem
The performer finds out about additional requirements only after completing the task.
For example:
- “You also had to confirm your phone number.”
- “You also had to complete one more step.”
- “You also had to open a specific section.”
- “You also had to wait for manual approval.”
What Happens
Hidden conditions lead to:
- mass rejections;
- complaints;
- disputes;
- lower trust;
- fewer performers willing to take the task.
How to Fix It
All conditions must be clearly stated in the task description from the start.
If phone confirmation, email confirmation, profile completion, or any additional step is required, it must be written before the performer begins the task.
❌ 3. Unclear Reward Conditions
Bad Examples
“Payment after review.”
“Reward depends on quality.”
“We may reject without explanation.”
Why This Is a Problem
Such wording creates uncertainty.
The performer does not understand:
- how much they will receive;
- when the reward will be credited;
- what can lead to rejection;
- how the review will be handled.
This reduces motivation and lowers the number of completed tasks.
How to Fix It
Use clear and predictable reward rules:
- fixed payment for an accepted result;
- clear conditions for reward accrual;
- transparent reasons for rejection;
- understandable review logic.
A performer should know what to do, what to submit, and what result will be paid.
❌ 4. No Acceptance Criteria
If you do not specify acceptance criteria, every performer will interpret the task differently.
Missing Criteria May Include
- what must be visible on the screenshot;
- which steps are mandatory;
- which page should be reached;
- what result is considered valid;
- what information must not be hidden;
- which proof format is accepted.
Result
No clear criteria usually leads to:
- chaos;
- inconsistent reports;
- high rejection rates;
- disputes;
- support tickets;
- slower moderation.
How to Fix It
Describe exactly what will be accepted.
For example:
“Submit a screenshot where the account email and the success page are visible.”
“Proof must show that the email has been confirmed.”
“Reports without the final success page will be rejected.”
❌ 5. Overly Complicated Task Flow
The Mistake
The task contains:
- too many steps;
- a long instruction;
- a complicated user path;
- unclear transitions between pages;
- several actions that are hard to verify.
What Happens
When the task is too complicated:
- conversion drops;
- completion speed decreases;
- the cost per result increases;
- performers abandon the task;
- the number of errors grows.
How to Fix It
Simplify the task to the minimum working scenario.
Remove everything that is not essential.
A good task should be easy to understand, easy to complete, and easy to verify.
❌ 6. Requesting Unnecessary Data
Dangerous Requirements
Avoid asking performers for:
- passport data;
- identity documents;
- phone access;
- bank card data;
- verification codes;
- passwords;
- personal account access;
- sensitive personal information.
Possible Consequences
Such requirements may lead to:
- performer refusal;
- complaints;
- task blocking;
- legal risks;
- reputational damage;
- additional moderation checks.
Correct Approach
Use only safe and minimal requirements.
Ask only for the proof that is necessary to verify the task result.
Do not request documents, banking data, passwords, codes, or other sensitive information.
❌ 7. Unstable or Broken Links
Common Link Problems
- redirects;
- broken pages;
- loading errors;
- region restrictions;
- expired links;
- links that open different pages for different users;
- mobile/desktop mismatch.
What Happens
If the link does not work correctly:
- performers cannot complete the task;
- trust decreases;
- rejection rates increase;
- support tickets grow;
- the campaign loses speed.
How to Fix It
Use direct, stable links.
Before launching the task, check the link:
- on desktop;
- on mobile;
- in different browsers;
- without being logged in;
- from the performer’s expected region, if relevant.
❌ 8. Contradictions in the Description
Example
At the beginning of the task, one condition is stated.
Later in the description, another condition appears.
Or:
The instruction says one thing, but the real website flow works differently.
Result
Performers complete the task “as they understood it,” which leads to:
- inconsistent reports;
- rejected completions;
- complaints;
- disputes;
- lower trust.
How to Fix It
Review the task before publishing.
Make sure that:
- all steps match the real website flow;
- the reward conditions are consistent;
- the proof requirements do not contradict each other;
- the final result is described in one clear way.
❌ 9. No Prohibited Methods Listed
If you do not specify what is not allowed, some performers may start looking for shortcuts.
What Should Be Prohibited
You should clearly state that performers cannot use:
- bots;
- scripts;
- fake accounts;
- multi-accounting;
- proxies or VPNs, if prohibited by the task;
- another person’s data;
- fake screenshots;
- repeated completions;
- any method that violates the platform rules or third-party service rules.
Result
Without restrictions, you may get:
- fraud;
- low-quality completions;
- suspicious reports;
- disputes;
- task blocking.
How to Fix It
Add a clear “Do Not Use” section to the task description.
This helps reduce abuse and makes moderation easier.
❌ 10. Slow Review
The Problem
This is not a text mistake, but it directly affects task performance.
If tasks are reviewed too slowly:
- performers lose interest;
- task completion speed drops;
- fewer people choose the task;
- trust decreases;
- disputes become more likely.
How to Fix It
Review reports faster whenever possible.
If review takes time, explain it in the task description.
For example:
“Reports are usually reviewed within 24 hours.”
“Manual review may take up to 48 hours.”
Clear expectations reduce frustration.
🚨 11. Risky Wording
Strictly Prohibited Wording
Do not use task descriptions such as:
- “boost reviews”;
- “increase the rating”;
- “install the app to improve ranking”;
- “bypass restrictions”;
- “create multiple accounts”;
- “leave a positive review”;
- “hide that this is a paid action.”
Such tasks may be blocked and may create legal or platform-related risks.
Correct Approach
Use safe, transparent, and rule-compliant wording.
If you are not sure whether the task is allowed, contact support before publishing it.
⚙️ 12. No Structure in the Description
A Bad Description Looks Like This
- one long block of text;
- no steps;
- no logic;
- no separate proof requirements;
- no clear result;
- no rejection criteria.
This makes the task hard to understand and hard to moderate.
A Good Description Includes
- what to do;
- how to do it;
- what proof to submit;
- what will be accepted;
- what is prohibited;
- how long review may take.
Recommended Structure
Use this format:
- Goal of the task
- Step-by-step instruction
- What to submit as proof
- Acceptance criteria
- Prohibited actions
- Review time
- Reward conditions
📊 Final Summary
Most problems do not happen because of performers.
They happen because the task description is unclear.
A good task description includes:
- a clear result;
- transparent conditions;
- simple instructions;
- fair reward;
- stable link;
- clear proof requirements;
- predictable moderation rules.
When all of this is in place, conversion improves, rejection rates decrease, and disputes become rare.
A strong task description does not just explain the task.
It protects your campaign from confusion, fraud, and unnecessary support tickets.
