Library · Traffic · How to run this
RedTrack payout hold is not postback-fail rate
On one RedTrack pay cut, put parked payout $ over full payout ledger $. The quotient is hold %.
Pair: Payout-hold share on Traffic. Tracker twin: postback-fail rate. Marketplace twin: Digistore24 payout-hold.
What you type
Held payout $ — RedTrack dollars still parked / unpaid on that pay cut.
Total payout $ — Full RedTrack payout ledger dollars for that same pay cut (parked + released).
Hold % = parked ÷ full × 100. When hold % runs hot, open the RedTrack fraud / KYC hold for the affiliate who owns the park — never invent a hold chip.
What not to do
Do not invent hold %. Do not drop a Digistore or BuyGoods pay sheet into RedTrack fields. Do not treat failed postbacks as parked cash. Do not merge pay cuts when one affiliate owns the park.
Related: Traffic, postback-fail rate, click-ID coverage, Digistore24 payout-hold.
Procedure
- Type held payout $ and total payout $.
- Read hold %.
- Chase fraud / KYC holds when hold % is material.
Failure modes
- Inventing hold %.
- Dumping a Digistore or BuyGoods pay sheet into RedTrack fields.
- Treating failed postbacks as parked cash.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Payout-hold share %
- Held payout $ ÷ Total payout $ × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this postback-fail rate?
- Different RedTrack door. [Postback-fail rate](/manuals/redtrack-postback-fail-rate) is failed postbacks ÷ attempts. This page is parked payout $ on the pay ledger.
- Is this Digistore24 payout-hold share?
- Different marketplace ledger. [Payout-hold share](/manuals/digistore-payout-hold-share) reads Digistore24. Here you only read RedTrack parked payout $.
- What hold % should I invent?
- None. Take parked RedTrack payout $ and full RedTrack payout ledger $ from one pay cut.