On forums, the loudest complaints are rarely “I cannot find programmes.” They are unpaid invoices, 60–90 day holds, conversions that vanish from the dashboard, and programmes that pause mid-promo. Vetting is how you avoid learning those lessons with real ad spend or a month of content work.
Why vetting beats chasing headline CPA
A £80 CPA with a 24-hour cookie, a 90-day validation hold, and broken click tracking is worse than a £25 CPA that pays Net-30 on clean S2S. Treat the listing as a shortlist, not a green light.
- Cashflow risk — long holds and high thresholds freeze money you need to reinvest.
- Attribution risk — short cookies and last-click coupon leakage erase credit you thought you earned.
- Ops risk — silent term cuts, paused programmes, and unresponsive support turn “pending” into “gone.”
Money terms (read these before the rate)
On the directory card and deal page, start with payout type and display value, then dig into the portal for the rest.
Payout type and what counts as a conversion
CPA, Recurring, RevShare, and Hybrid are not interchangeable. Confirm the payable event: signup, first payment, approved sale, FTD, or something narrower. Refund windows often sit behind the public rate. Hybrid deals need both parts written down.
Cookie (or attribution) window
Match the window to the sales cycle. B2B SaaS with a 45-day consideration path and a 7-day cookie is a structural mismatch, not a traffic problem. Short windows punish research content. Longer cookies help only if tracking survives the full path.
Hold period, min payout, and who pays you
Ask: when does “earned” become “in my bank”? Net-30 after a 30-day validation is not the same as Net-30 from conversion day. Direct programmes pay the brand; network programmes pay via the network’s schedule. High minimums trap small tests. The merchant’s payment status on the network matters as much as the CPA.
| Check | Good enough to test | Walk-away signal |
|---|---|---|
| Cookie vs niche | Covers a realistic buy cycle | Hours-long cookie on considered purchases |
| Validation / hold | Clear Net-30 / Net-45 you can fund | 90-day holds with no EPC clarity |
| Min payout | Reachable from a small test | Threshold you cannot hit for months |
| Payable event | Written and measurable | “At our discretion” with no examples |
Tracking and health
If clicks do not show in the portal, you are flying blind. Forum threads about “lost commissions” usually start with a dashboard that never matched the publisher’s own logs.
- Apply destination health — on PayoutDeals, green healthy only means the apply / join destination was checked and marked healthy after a real check. It is not the same as Verified.
- SubIDs / click IDs — confirm you can tag links so you can prove volume if support argues.
- Postback or pixel sanity — for paid traffic especially, know whether you get server-side confirmation or only a UI report.
- Shared join URLs — one broken network join page can affect many programmes; check the network profile too.
Before the first paid click: send yourself one test click. Confirm it appears in the portal (or your postback) in a timeframe the AM will stand behind. Screenshot it. Scale only after that.
Trust signals on the PayoutDeals listing
Badges are shorthand. Read them literally.
- Verified — an operator confirmed the programme or network looks genuinely open. Not automatic from a healthy URL check. Hidden when off.
- Featured — pinned for discovery, not a payout guarantee.
- New — listed in the last 7 days from our listing date, not the merchant’s launch date.
- Terms history — when present, shows when we recorded payout / cookie / network changes. Useful for spotting sudden cuts. Absent until there is a change worth showing.
- Sentiment % — only when we have an updated timestamp. Ignore empty / missing scores; we do not invent defaults.
- Health — healthy only after a check with status healthy. Dead / warning stay muted on purpose.
None of these replace reading the merchant’s current T&Cs in the network portal.
Rules you can break without knowing
Approvals and clawbacks often come from traffic-type rules, not “bad” content quality.
- Brand bidding / PPC on trademark terms
- Coupon, cashback, or toolbar / extension traffic
- Incentivised or loyalty placements
- Email / SMS without prior approval
- Geo or vertical restrictions that do not match your audience
- Mandatory disclosure and creative pre-approval
If the public listing is thin on rules, assume the portal PDF is the source of truth. Save a copy of the terms on the day you are approved.
Smoke-test before you scale
- One controlled click path — your device, your subID, one conversion event if you can ethically trigger a test (or at least a tracked landing).
- A small burst — enough volume to see EPC / CR direction, not enough to hurt if tracking fails.
- Support — one concrete question (cookie, hold, allowed traffic). Silence before you scale is data.
- Do not stake the niche on one merchant with no written SLA.
Red flags and a go / no-go scorecard
- Test clicks never appear; support blames “cookies” indefinitely
- Earnings show then reverse with no transaction-level reason
- Programme paused around peak promo windows with no notice
- Platform migration with missing stats / balances and silence
- Public rate far above peers with no clear payable event
- You cannot name who pays you (brand vs network) or when
| Scorecard item | Pass | Fail |
|---|---|---|
| Money terms understood | Cookie, hold, min, event written down | Only headline CPA known |
| Tracking smoke test | Click (and ideally conversion) visible | Dashboard blank after 24h |
| Rules match your channel | Traffic type allowed in writing | Guessing from forum lore |
| Support path | AM or ticket replied once | No human after approval |
| Directory signals | Health / terms / badges make sense | Dead apply URL or sudden term cut |
Rule of thumb: need four passes before meaningful budget. Two fails = keep browsing. One fail on tracking = stop traffic until fixed.