The position
Where Betitor stands, from what we can see
We walked the live product and took your own numbers from our conversation. Two kinds of figures appear in this document and they are labelled throughout: operator-reported (told to us, not yet verified in data) and indicative (ranges from our operating experience in this market, not a forecast).
| Fact | What we saw or were told | What it means for acquisition |
|---|---|---|
| Product | Turkish-first casino plus sportsbook: slots, live casino, originals (Plinko, Mines, Dice, Keno, Limbo), crash category, poker, Drops and Wins, special odds page | Complete enough to buy traffic for. Slots, crash and sport give three distinct verticals to match partners to |
| Welcome offer | 500% slot welcome bonus, plus 15% next-day cashback on losses | A strong headline for affiliate creative. Terms behind it need review before partners advertise it (Part 4) |
| Payments | Operator-reported: minimum deposit 250 TRY, minimum withdrawal 1,000 TRY, bank transfer (Havale); minimum can move in peak hours | A working local rail. Deposit floor is in the normal range for this market. Peak-hour changes must be flagged to us in advance, because they move conversion and partner disputes follow |
| Conversion | Operator-reported: 15 to 18% registration to deposit on Facebook traffic, on average | If it holds in player-level data, the funnel converts and this is a scale programme, not a repair programme. We verify it in Phase 0 from the raw export, per source |
| Domains | Traffic runs through a permanent entry domain that forwards to the current mirror | Correct setup for this market, and it puts one hard requirement on tracking: links and postbacks must survive a mirror change (Part 3) |
The headline read
The product is live, the local rail works, and the funnel converts by your own numbers. What is missing is what turns spend into a programme: partner supply under contract, a tagging spec that survives mirrors, cohort discipline, and reconciliation. That is exactly the service we run, and it means traffic can start weeks after tracking validates, not months.
The sequence
The sequence we propose
- Validate tracking first. Four parameters on every link, postbacks firing on registration and first deposit with the click ID echoed back, a test registration landing intact end to end. Days, not weeks, if the platform supports it.
- Baseline from your raw data. One player-level export gives us the real registration-to-deposit rate per source, deposit values, and repeat behaviour. Your 15 to 18% Facebook figure becomes a verified baseline, per partner.
- Pilot capped cohorts across two or three channels with partners from our network, every deal in writing on the ten points in Part 2. Your existing sources keep running; they migrate onto the same tagging spec in Phase 0 so their numbers become comparable, and nothing is switched off.
- Scale on day-14 reads, not on promises. Caps extend where cohort economics clear the bar; everything else stops at the cap.
Part 1
Supply for Turkey
Turkey is the market our operating experience comes from. The table below is what that experience says about each channel here: how it behaves, and what it typically costs on cost-per-acquisition terms. Ranges are indicative, observed across a portfolio of partners in this market; they are a starting expectation for negotiation, not a committed price, and every partner is priced individually against the vertical and the cap.
| Channel | Behaviour in this market | Indicative CPA | State |
|---|---|---|---|
| SEO | Cleanest traffic, longest tail, highest reactivation, lowest fraud incidence. Slow to start, then compounds. Watch concentration: a dominant SEO partner becomes a dependency | Often fixed monthly or hybrid rather than per-player | Sourced |
| Telegram | Quality close to SEO, fast to activate, large communities in this market | $70 to 110 | In network |
| Facebook, slots vertical | Volume workhorse. High variance, driven by a small number of large depositors; cohorts move heavily between day 4 and day 7, so the day-14 discipline is not optional | $85 to 110 | In network |
| ASO and APK | Predictable, low variance, deposits land 1 to 7 days after registration. Betitor needs an installable app or APK flow for this to open | Around $80 | In network Needs app |
| Streamers, crash and slots | Strong trust transfer onto originals and crash, which Betitor already leads with | Deal-specific | Sourced |
| UAC | Scales fast with clean tracking; needs an app and SDK-level attribution | $60 to 100 | Sourced Needs app |
| Paid search | In our experience the hardest channel to make work on CPA terms in this market. Tested last, at a small cap, never first | $60 to 100 | Sourced |
| Pop and push | Highest fraud incidence we have seen in this market. Only with full click-level tracking and a hold-by-default policy | Low | On request only |
Landings. Partner traffic lands on vertical-matched pages. Who produces them is agreed at onboarding: partners bring their own pre-landers where their channel uses them, and on-site landing pages are either produced by your team to our brief or added to our scope as an extension.
Vertical matching. Slots traffic lands on slots offers, crash traffic on the originals, sport traffic on special odds. A partner is signed for a named vertical and the landing follows it; mixed links that dump everything on the homepage are how conversion quietly dies.
Partner availability and volume are confirmed partner by partner at onboarding. This document commits the sourcing process and the operating discipline, not a traffic number.
Part 2
Deal and cap rules
Every partner deal fixes ten points in writing before a link is issued: rate and currency per market, vertical and traffic sources named, cap expressed in first-time depositors, the qualification rule in full, the attribution window (30 days registration to first deposit as standard), the tagging obligation, minimum payout with carry-forward, payment terms, clawback rights, and exclusions (incentivised traffic, brand bidding, self-referral, misleading creative).
Caps and extensions
- Every partner starts capped, regardless of reputation or referral.
- No cap extension before day 7. In this market, slots cohorts driven by large players reverse hard between day 4 and day 7.
- Day 14 is the decision point, on four signals: volume delivered, cost per player against the deal, cohort return trajectory, and the fraud screen.
- Caps are not more than doubled in one cycle unless you approve a larger step.
- Cohorts under roughly 15 depositors get an explicit low-confidence verdict.
- The day-14 bar is numeric and agreed at onboarding, written into the cohort sheet before the first link goes live. Our standard starting bar: cost per qualified player within the contracted rate, and the cohort deposit-return trajectory pointing at or above break-even on spend.
- High-value players are isolated in every read. Cohorts are shown with and without their largest depositor, because in the slots vertical a single account can carry or sink a pilot cohort, and a scale decision is never taken on the with-whale view alone.
Qualification, deposit floor
With a 250 TRY minimum deposit, the qualifying rule matters: a partner paid on any first deposit is paid on minimum-deposit players who never return. We set the qualifying threshold with you at onboarding, and one-and-done behaviour is reported per partner from day one, because in this market the share of depositors who never deposit again is the single number that separates good supply from volume supply. Self-excluded players and duplicate accounts are removed before payout, per the qualification rules signed in each deal.
Part 3
Tracking spec, mirror-proof
Nothing goes live untagged. Four parameters on every link: affiliate ID, market, campaign or sub-ID, click ID. All four persist to the player record, not only the click log, and we resolve by link ID, because one affiliate routinely runs several sub-teams on different terms.
The mirror requirement
Betitor already runs a permanent entry domain that forwards to the current mirror. The tracking spec has to respect that:
- All partner links point at the permanent entry domain, never at the current mirror. A link hard-coded to a mirror dies with the mirror, and its traffic becomes unattributable exactly when volume spikes.
- Parameters must survive the forward. The redirect has to carry the full query string onto the mirror. We test this with a live test link before any partner goes live, and again after every mirror change.
- Postbacks key on the click ID, not on the domain, so a mirror change never breaks partner-side measurement.
- Click IDs are captured server-side at landing and postbacks run server to server, not as pixels. Cookies do not survive a cross-domain forward; the query string and the player record do, which is why both are mandatory.
- A synthetic test link runs on a schedule: it fires a known click ID and confirms the postback returns intact, so an unannounced mirror change is caught within hours rather than at month end. Advance notice of planned changes stays as a courtesy on top, with same-day re-validation.
Postbacks
Postbacks fire on registration and on first deposit, with the click ID echoed back, and on repeat deposits where the platform supports it. Whether they fire in real time or batched, and what fields they can carry (deposit amount in particular), is one of the first platform questions we close in Phase 0, because partner-side optimisation quality depends on it.
Part 4
Quality, fraud, and the bonus surface
Standing screens, from day one
- A week-two IP and hosting audit on every spend cohort. Standing process, not triggered by suspicion. Hosting and datacentre IP concentration is the signature of routed traffic, and this market produces it regularly.
- Bot pattern detection: registrations that log in exactly once, at scale.
- Duplicate account detection across address and device; flagged on one signal, confirmed on a combination.
- Near-total conversion on a tiny cohort triggers an automatic hold, pending review. A hold is a review trigger, not a fraud finding; it resolves on the data.
- We do not assert fraud without evidence, and we do not drop a suspicion without data either. Held stays held until it resolves.
The bonus surface
A 500% headline plus 15% next-day cashback is strong affiliate creative, and it is also the first thing a bonus-abuse team looks at. Before partners advertise it, we review the terms behind it with you: rollover, game weighting (slots against originals against crash), maximum win, minimum qualifying deposit against the 250 TRY floor, and the cashback definition. Affiliate creative is then approved against those terms, so no partner advertises an offer the site does not honour; the mismatch between creative and terms is a leading cause of first-session abandonment and chargeback disputes.
Part 5
Phased launch
| Phase | Duration | What happens | Gate to the next phase |
|---|---|---|---|
| Phase 0: tracking and baseline | 1 to 2 weeks | Tagging spec implemented, test link validated end to end through the mirror forward, postback capability confirmed, first raw player-level export, baseline conversion per source verified against the operator-reported figures, bonus terms reviewed | Test registration lands with all four parameters; export delivers the agreed fields |
| Phase 1: pilot cohorts | Weeks 2 to 6 | Three to five partners from the network across two or three verticals (slots, crash, sport), every deal on the ten points, every cohort capped; initial caps indicatively 20 to 40 first-time depositors per partner. Day-7 reads, day-14 verdicts, first reconciliation cycle run in full | At least two cohorts clear the day-14 bar on cost and quality |
| Phase 2: scale | From week 6 | Caps extended on the partners that cleared the bar, new partners added on the same discipline, SEO and streamer supply activated for the compounding layer, ASO and UAC opened if an app or APK flow exists | Continuous: every extension justified by a cohort read |
Dates go on this table at onboarding; the gates do not move.
Part 6
Reporting and the shared BI platform
You get your own login to the same platform we run the programme from: totals, per-partner and per-cohort views with all three return metrics (deposit return on spend, net revenue return on spend, net margin on spend), attribution health, and holds with their evidence status. Refresh follows the data feed cadence. Weekly cohort status, day-14 verdicts per cohort, monthly reconciliation with statements, and a monthly narrative that says what moved, why, and what is blocked on which side.
The full service definition, workstream by workstream, is in the companion service document we have shared separately.
Part 7
What we need from Betitor
| Dependency | Why |
|---|---|
| Recurring player-level export: registration date, first deposit date and amount, every deposit, source and affiliate and link IDs, wagering and revenue fields, plus registration IP, login or active-days count, device identifier, and the self-exclusion flag | The baseline, every cohort verdict, the fraud screens and every reconciliation are computed from it. Without the IP, login and device fields the quality gate in Part 5 cannot be run |
| Tracking parameters and postbacks supported on the platform, with answers to: real-time or batched, click ID handling, which fields a postback can carry, and whether repeat-deposit events can fire | Phase 0 closes on these answers |
| Payment logs with a user key | A failed deposit must be traceable to partner and source, and peak-hour minimum changes must be visible in data |
| Bonus terms behind the public offers, and sign-off on the affiliate creative rules | Partners advertise only what the site honours |
| Advance notice of mirror changes | Test link re-validation the same day; unannounced changes orphan traffic |
| Named contacts in payments, platform and CRM, and timely approval of deals, caps and budgets | Timely approvals keep the day-14 cycle intact; a delayed decision is a delayed cohort |
Part 8
Commercial structure
Agreed separately, between principals. The programme above does not depend on which structure is chosen; the deal models we operate (flat CPA, tiered, hybrid, revenue share, spend deals, fixed monthly) are described in the companion service document, and the reporting shows each of them settled separately.
Open items for that conversation: service fee structure, partner payout funding and execution flow, the qualifying deposit threshold that payouts are built on, and the FX basis. Deposits run in TRY and partner rates are typically quoted in USD, so the reconciliation currency and the rate source (locked monthly or at settlement) are fixed in writing before the first cycle, not argued during it.