Nothing moves on a click

Some networks count a conversion when a publisher reports it, or when a user lands on a thank-you page. We count it when the advertiser's own server tells us the event happened, with the click ID we gave it. The advertiser is the one who knows a real user signed up or paid, so they are the one who confirms it.

Advertisers can also report a conversion as pending while their own checks run, and confirm it later. Pending conversions are not credited to the user or the publisher until they are confirmed.

Refunds, chargebacks and fraud findings often take weeks to surface. For 30 days after a conversion, the advertiser can reverse it with the same postback and a reversed status. After that, it is final. Publishers' earnings become payable once the window has passed, which is why a payout never has to be clawed back in the usual case.

• The advertiser is not billed for it, or gets it back as a credit on the next invoice if it was already billed.
• The publisher gets a reversal postback to take the user's reward back. If the earnings were already paid out, they come off the next payout.
• Our team sees the reversal next to the publisher's other activity, which is often the first sign of a traffic problem.

Every click gets a unique ID tied to one publisher and one user. A postback for the same transaction, or for the same step on the same click, is ignored the second time, so retries and double-fires are never billed or paid twice.

Each click is checked against lists of datacenter, VPN and Tor addresses. We flag many user accounts clicking the same offer from one IP, conversions that arrive seconds after the click, and publisher accounts that sign in from the same address or share a payout account. Flags go to our team for review; they don't block anything automatically, so a real user on a VPN is not turned away, and a confirmed problem can be reversed.