Fix the cohort and the follow-up window
Choose registrations attributed under the agreed rule, then allow the same follow-up time for each account. A group acquired yesterday cannot be compared fairly with one observed for a month. Mark immature cohorts provisional and retain the reporting cutoff.
Define the numerator too. A first successful payment, a commission-qualified acquisition and an account with any deposit are different events. Operator terms such as Arena’s demonstrate that qualification can depend on verification and territory as well as payment. Do not collapse them into one conversion flag.
Break the journey into states you can observe
Useful aggregate states include registered, verification pending, eligible, payment attempted, payment successful and commission qualified. Record unavailable states as unknown. Do not infer a payment decline from someone failing to deposit or infer fraud from a missing qualification.
The reporting owner should explain whether the funnel is sequential and deduplicated. A person can attempt payment more than once, so attempts may exceed people. Keep an account-level conversion rate separate from a transaction-level success rate.
Test for a product or message mismatch
Compare the creator’s approved message with the actual landing experience. Check product availability, language, device behaviour and the terms shown to the eligible audience. A creator may have explained one feature while the destination now emphasises another.
Inspect the permitted route without completing a real gambling transaction or bypassing access controls. If a payment route is unavailable, send that evidence to the operator. Do not ask a creator to persuade viewers to circumvent verification, location restrictions or financial limits.
Talk to us
Pick a 30-minute slot, or DM us on Telegram.
Need help applying this to your campaign? Tell us what you’re planning.
Pricing is scoped to your brief. We reply within one working day.
Reconcile a hypothetical gap
Suppose 200 attributed registrations have all had seven days of follow-up. Eighty reach the defined first-successful-payment event. The observed rate is 40%, not a market benchmark. An authorised aggregate state report shows many accounts still awaiting review and a smaller group encountering a technical error.
The actions differ. The operator resolves the error and explains legitimate review states. The campaign owner checks whether the brief accurately described eligibility. The creator is not told to increase pressure on non-depositors, and the team does not remove safeguards to improve the percentage.
| Observed state | Question | Responsible next step |
|---|---|---|
| Registration only | Has equal follow-up elapsed? | Wait or label the cohort immature |
| Review pending | Is this a legitimate eligibility process? | Ask the operator for authorised aggregate clarification |
| Technical error observed | Which approved route failed? | Repair and retest without bypassing restrictions |
| Payment successful, not qualified | Which contract condition differs? | Reconcile the event and payable definitions |
Choose a correction that answers the cause
Change the brief when the product explanation was wrong. Fix a technical route when evidence shows it failed. Allow time when the cohort is immature. Stop the promotion if a material eligibility issue remains. Keep each change dated so the next cohort can be interpreted honestly.
A useful follow-up report shows the original definition, corrected condition and equal observation window. Avoid promising that any one repair will produce a target rate. The goal is a truthful, functioning journey for eligible adults, not extracting deposits from every registration.
Use an explicit FTD definition before deciding where the funnel loses commission-qualified acquisitions.
Frequently asked questions
What is a good registration-to-FTD rate?
There is no responsible universal number for every product, market, offer and reporting rule. Compare matched mature cohorts and disclose the exact event definition.
Should verification be removed if conversion falls?
No. Required eligibility and responsible-gambling safeguards must remain. Diagnose errors without bypassing legitimate controls.
Results from campaigns our team has run
Web3 game · gaming creators, streams and events
Illuvium
6,550 new players and 24,000+ followers
Read the Illuvium caseCrypto exchange · KOLs on X, YouTube and TikTok
Binance
4,245 new users and more than $510M in trading volume, double the target
Read the Binance caseCrypto banking · influencers and growth
Swissmoney
32,000+ users onboarded and CPA cut 4x
Read the Swissmoney case
3betmedia launched in 2026; most of these campaigns ran before the name existed. See all 19 cases.
Sources and further reading
Primary references support the limited platform, product or rights facts above. Operational examples are hypothetical; this page does not provide legal approval or a performance guarantee.
