CashoutGuard: fraud prevention for rewards, GPT, faucet, PTC and offerwall sites.

Offer completion speed: how fast is too fast on an offerwall

A game that takes real players three days to reach level 30 does not get finished in eleven minutes. Speed is one of the clearest fraud signals on an offerwall, and one of the easiest to measure if you log the right events. This guide shows how.

Short answer

Log the offer click and the conversion, measure the time between them and compare it with a baseline for that offer, never with a global number. A practical rule is to flag conversions that took less than half of the offer's 10th percentile time and review them before crediting.

Short survey
Real users take 5 to 15 minutes; under 30 seconds is almost certainly fraud.
App install and open
Real users take 2 to 10 minutes; a few seconds is almost certainly fraud.
Game level milestone
Real players take hours to days; minutes is almost certainly fraud.
Related signals
Conversions without a click, duplicate transaction IDs, conversion velocity and country changes.

Why speed gives fraud away

Every offer has a natural pace. A short survey takes a few minutes. An app install with registration takes five or ten. A game milestone can take days. Real users spread around that pace. Some are quick, some slow, but very few are dramatically faster than everyone else.

Fraud breaks that pattern. Bots, scripts, modded apps, reused survey answers and forged postbacks all produce conversions that arrive far sooner than a human could finish. Networks and advertisers know this. Time to install and time to event are among the first things they check before paying.

Measure click-to-conversion time

You cannot judge speed without a start time. The start is the moment the user opens the offer from your wall. The end is the moment the network postback arrives.

  1. Log every offer click with the user ID, the offer ID, the time and the IP country.
  2. Log every conversion with the same user ID and offer ID, the network transaction ID and the amount.
  3. Match them. For each conversion, find the most recent click by the same user on the same offer, within a sensible window such as 30 days.
  4. Store the difference in seconds. That number is your click-to-conversion time.
-- Click-to-conversion time per conversion
SELECT c.id, c.user_id, c.offer_id,
       TIMESTAMPDIFF(SECOND, k.created_at, c.created_at) AS seconds
FROM conversions c
JOIN offer_clicks k
  ON k.user_id = c.user_id AND k.offer_id = c.offer_id
 AND k.created_at = (
     SELECT MAX(created_at) FROM offer_clicks
     WHERE user_id = c.user_id AND offer_id = c.offer_id
       AND created_at <= c.created_at)
ORDER BY seconds ASC;

Build a baseline per offer

Once you have times, work out what normal looks like for each offer. The median tells you the typical pace. More useful for fraud is the fast end: the time that only the quickest 10 percent of users beat, the 10th percentile.

A practical rule: flag conversions that took less than half of that 10th percentile time. Even the fastest honest users rarely get there. Add a floor, such as 60 seconds, for offers with too little history to trust the baseline.

Offer typeTypical real timeSuspiciousAlmost certainly fraud
Short survey5 to 15 minutesUnder 2 minutesUnder 30 seconds
App install and open2 to 10 minutesUnder 1 minuteA few seconds
Install and register5 to 20 minutesUnder 2 minutesUnder 1 minute
Game level milestoneHours to daysUnder 1 hourMinutes
Trial or purchase offerMinutes to daysDepends on the offerSeconds after click

The numbers above are only a starting point. Your own data, per offer, will always be better. Recalculate baselines regularly, because offers change their requirements.

New offers and social tasks: what a fixed floor gets wrong

A floor is a guess, and it is easy to check how good the guess was: wait until the offer has enough completions to have a pace of its own, then look back at what the floor flagged before that. We did that on 30 days of three offerwall sites. Of the conversions the one-minute floor had flagged on offers that later learned their pace, 94 turned out to be within that pace. One did not, and it had come in under 20 seconds.

So while an offer is new, a conversion between 20 seconds and a minute after the click says little: weigh it lightly and let the other evidence on the account decide. Under 20 seconds is different, because almost nothing on an offerwall can be done that fast, and it keeps its full weight.

Social tasks break the floor completely. "Follow us on X", "like this post" or "join our Discord" take seconds, not minutes. In 14 days, 201 such conversions were flagged as too fast on three sites, done in 19 to 35 seconds, simply because no single site had enough completions to learn their pace. A task that is one follow, like or join needs a floor of about 10 seconds; anything that asks for an install, a level or a sign-up keeps the minute.

Signals that travel with speed

Conversions without a click

If a user gets paid for an offer they never opened from your wall, there is no start time at all. That can mean a forged or replayed postback, a user completing offers through another route, or a bug in your click logging. Check the logging first. Once you trust it, a paid conversion with no click is a strong signal.

Duplicate transaction IDs

Every network conversion has a transaction ID. The same ID arriving twice for the same offer means a replay or a duplicate. Store the IDs and ignore repeats, but also record them. A user who benefits from repeated IDs deserves a look.

Velocity

Many conversions from one account in a short time is its own warning, even if each one looks fine. Ten conversions in an hour is a lot for a real person doing real offers.

Country changes

An offer clicked from one country and converted from another is often a VPN or proxy switched on after the click. Combined with a fast conversion, it is a clear pattern.

How networks see fast conversions

Offerwall networks and advertisers look at the same data from their side. They see install time, event time and device data from the app. When your traffic shows many impossibly fast events, they reverse those conversions and may mark your site as low quality.

That matters beyond the single conversion. Networks can lower payouts, remove premium offers or pause a publisher with persistent speed problems. Catching fast conversions yourself, before the cashout, protects both your margin and your standing.

  • Share what you catch. Tell your account manager which offers attract fast fraud. They often have the same problem with other publishers.
  • Ask for reasons on reversals. Some networks can tell you when a reversal was for speed, which helps you tune your baselines.

Read the speed per offer and per publisher

One fast conversion says little; the shape of a whole offer or publisher says a lot. Group conversions by time since the click. Real users spread over the time a task takes, while bots and farms pile up under 30 seconds.

  • Per offer. A game that takes days should have almost nothing under ten minutes.
  • Per publisher. Users converting within seconds on many offers mean automated traffic.

CashoutGuard draws this for any offer or publisher you open from the Events page.

What to do with a fast conversion

  • Do not credit instantly when the conversion is under the threshold. Mark it pending.
  • Review the account at cashout. One fast conversion may be luck; a pattern is not.
  • Look at the cluster. Fast conversions on the same offer from linked accounts point to one operator.
  • Deduct if the network reverses, and let the balance go negative if needed.

Keep the evidence with each decision: the click time, the conversion time, the offer baseline at that moment and the IP country of both events. When a network questions a batch, you can answer with numbers. When a user appeals, you can show exactly why the conversion was held.

A worked example

Say an install-and-reach-level-10 game offer has a 10th percentile of 40 minutes across your users. Half of that is 20 minutes. A conversion that arrives 6 minutes after the click is well under the line, so it goes to review. A conversion at 25 minutes is fast but plausible, so it is credited. If the same account also shows three other fast conversions in the same hour, the pattern matters more than any single one.

How CashoutGuard automates it

Send CashoutGuard an offer_click event when a user opens an offer and a conversion event when the postback arrives, with the offer ID and transaction ID. It matches them and builds a baseline for each offer from your own traffic.

  • offer_completed_too_fast when the time is under half the fast end of that offer, with a minimum you can set yourself. Until an offer has its own pace, 20 to 59 seconds is only a light sign and under 20 seconds still counts in full; follow, like and join tasks get a 10-second floor.
  • conversion_without_click once your site sends click events.
  • duplicate_transaction for repeated transaction IDs.
  • conversion_velocity and click_conversion_country_mismatch for bursts and country switches.

The offer stats page shows each offer by name with its click-to-conversion speed, conversions without a click and earnings spikes, so you can see which offers attract fraud. Details are in the docs, and plans start free on the pricing page.

Frequently asked questions

What is a normal click-to-conversion time?

It depends entirely on the offer. Build a baseline per offer from your own users and compare each conversion with the fast end of that offer, not with a global number.

Can a real user complete an offer very fast?

Sometimes, especially on short surveys or if they already had the app. That is why one fast conversion should go to review, while a pattern across many offers or accounts is much stronger evidence.

Why do I see conversions without any click?

Either your click logging misses some paths, the postback was forged or replayed, or the user completed the offer outside your wall. Fix logging first, then treat the rest as suspicious.

Should I ignore duplicate transaction IDs?

Ignore them for crediting, but record them. A user who benefits from repeated IDs is worth reviewing.

Keep reading