Review Speed and Approval Rate: How They Affect Traffic

Do review speed and approval rate affect your traffic?

Yes. Every task card on the offerwall shows users how soon they will be credited, which is your approval window, how many completions you approved and, once there is enough history, the share of completions you approved. Users compare these figures with the reward before they start, so a long window or a low approval rate makes your task look like a risk, while fast and fair reviews make it look like a safe choice.

The offerwall does not rank tasks by approval rate. It shows the highest reward first and sorts the rest by reward. Your reviewing affects something just as important: whether users pick your task once they see it, and whether they come back to it.

What users see about your task on the offerwall

When a user opens your task, the details box lists a few facts next to the reward. All of them come from your campaign settings and your review decisions:

The card itself can also carry a badge. Top marks the highest reward on the wall, Hot appears once a task has at least 10 approved completions, and New marks tasks approved by our team in the last 7 days. The card also shows a small “completed” count, and users can sort the wall by Most popular, which uses the same approved count.

Two details matter for the approval rate. Completions that are still waiting for review, rejected but open to a dispute, or in a dispute are not counted yet. And a rejection that a user wins in a dispute counts as approved, because it was.

Your approval window is the speed users see

The offerwall never shows how quickly you actually review. It shows the window you promised. A task that says “Within 3 days” looks slower than one that says “Within 1 hour”, even if you clear your queue every morning. If you review fast, a shorter window tells users so.

After sending proof, the user follows the completion in the History tab of the offerwall. It shows Pending review with a countdown until the review deadline. Approving early credits the user early, and a user who was credited quickly is more likely to come back to your tasks. How to pick the window itself is covered in Approval windows: how to choose one and review on time.

How slow reviews cost you completions

A long queue costs more than goodwill. Three things happen while completions wait:

• Users cannot repeat the task. While a user’s completion is waiting for review, rejected but still open to a dispute, or in a dispute, that user cannot send the same task again. They see “You already sent this offer. Check History for the result.” On a task with a frequency of every day or every hour, every hour in your queue is an hour of lost repeats.
• Money is held. The price of each undecided completion is set aside from your available balance. If what is left cannot cover the price for a user’s country, your task stops showing to that user. Holds on your balance, explained walks through the numbers.
• The budget fills up. If you set a total budget, held amounts count toward it together with what you already spent. A queue of undecided completions can hide a campaign that still has budget left. Campaign budgets and caps explained covers how the budget is counted.

What happens when the review window ends

A completion you have not approved or rejected when the window ends is approved automatically and charged to your balance, at the price for the user’s country. The user is credited, and the history of the completion says “Approved automatically because the review window ended”. From that moment you can no longer reject it: if you try, the dashboard tells you “The review window has ended, so this completion is approved automatically.”

Automatic approval protects users from advertisers who stopped checking, and it is the reason the Credited line on the wall can be trusted. For you, it means a missed review session is not a delay but a decision, made in the user’s favor.

How a high rejection rate shows up

Rejections that become final lower the share shown as approved, and they never add to your completed count or bring you closer to the Hot badge. Users cannot see your reasons for other people’s completions, but they see the result: a task that pays well but approves barely half of the work sent to it.

A low rate is rarely about bad users alone. When many completions are rejected for the same reason, the instructions or the proof requirement usually left room for guessing. Fix the campaign for future users with Write instructions that pass review, and give clear reasons for the rejections you do make, as shown in How to write rejection reasons users accept.

A review routine that keeps both numbers healthy

1. Choose a window you can beat. Set it a little longer than the gap between your review sessions, then shorten it once you never come close to the deadline.
2. Review at fixed times. The Completions page lists what is waiting, and the campaign page shows a Waiting for you count. Clear it every session, oldest first. How to approve or reject completions shows where each button is.
3. Answer disputes in the same session. The Disputes page has its own deadline. A dispute you answer quickly releases its hold sooner.
4. Cap the volume to your time. Hourly and daily caps keep the queue at a size you can review properly instead of rushing.
5. Read your own rate. The campaign page shows Approved and Rejected counts. If rejections climb, look for the common mistake and fix the instructions.
6. Approve honest work. If a user clearly did the task and the proof shows it, approve it even when the screenshot is not perfect. You would likely pay after a dispute anyway.

Frequently asked questions