CPA marketplace — a pay model for advertising and partner channels where a seller pays only for a recorded target action: a confirmed purchase, a lead or an installation. In the context of Kaspi.kz this means payment is made after the actual order placement or another agreed event.
How CPA works on a marketplace
The CPA mechanics are standard and include three elements: traffic source, tracking system and payment condition. In practice on Kaspi.kz it looks like this:
- Traffic source — internal Kaspi ad blocks, external partner sites, ad networks or arbitrage partners.
- Tracking — linking a click to an order via UTM tags, postback, API integration or a campaign number in the order.
- Payment condition — the specific action: an order paid, an item delivered, a confirmed return or a completed lead (for example, an installment application).
CPA payments are made after the condition is verified. For a marketplace it is important to agree the moment an action is recognized — buyer payment confirmation, changing the order status to "completed" or expiration of the return period.
Why a seller should use CPA: benefits and vulnerabilities
CPA is attractive because it converts advertising costs into variable expenses directly tied to sales. Specifically for Kaspi.kz sellers it provides the following advantages and risks:
- Pros:
- Profitability control: you pay only for real purchases, making ROI easy to calculate. Example: if the average order value is 9 000 KZT and CPA is 1 500 KZT, the margin remains clear immediately.
- Ability to scale sales with limited budget: you can start cooperation with partners without prepayment.
- Simplified accounting: advertising costs are tied to invoices for actual deals.
- Risks:
- Fraud and frod: fake orders, returns, repeated orders to inflate metrics. In practice sellers in Kazakhstan face returns of 5–12% in some categories.
- Payment delays: the marketplace or partner may lock payouts for 30–45 days while the return period expires.
- Reduced conversion with a poor product page: a CPA partner will bring traffic, but if the listing is not ready, purchases will be low and CPA becomes inefficient.
Concrete benchmarks and examples for Kaspi.kz sellers
Below are practical numbers and scenarios based on sellers' experience in Kazakhstan from 2022–2025. These are benchmarks, not absolutes.
- Typical CPA by categories (approximate ranges):
- Low‑price items (up to 3 000 KZT): ~150–500 KZT.
- Mid‑price goods (3 000–30 000 KZT): ~500–3 000 KZT.
- High‑price items (30 000–150 000 KZT): ~3 000–15 000 KZT.
- Electronics and white goods (higher ticket, higher risk): ~5 000–25 000 KZT depending on category and return rate.
- Leads and financial products (installment/credit leads): ~2 000–8 000 KZT per approved lead.
- CPA as a share of AOV or margin:
- Common guidance is to keep CPA within 10–30% of the average order value (AOV) or within 30–50% of gross margin per unit, depending on growth vs. profitability goals.
- Example calculation:
- Average order value: 9 000 KZT. Gross margin per unit: 3 000 KZT. If CPA = 1 500 KZT, remaining gross margin = 1 500 KZT before marketplace fees and logistics. If marketplace commission + logistics = 800 KZT, net contribution = 700 KZT.
- Use this to model breakeven CPA: breakeven CPA = gross margin − marketplace fees − required profit per unit.
Practical steps to set up CPA and prevent risks
- Agree the payment trigger and verification period in the contract: payment confirmation, order status change to "completed" or end of the return window (typical verification 7–14 days or longer for bulky items).
- Choose reliable tracking: prefer server‑to‑server postback with unique click_id and order_id, plus UTM tags for redundancy. Implement API integration where possible for automated reconciliation.
- Set clear exclusion rules: do not count cancelled orders, refunds, chargebacks or orders failing fraud checks.
- Run test orders and monitor postback delivery, duplicate events and timing mismatches. Verify that click_id persists across the buyer journey.
- Introduce staged payments or holdbacks for new or untrusted partners: initial period with partial payouts and manual checks, moving to full automation after stable performance.
- Implement anti‑fraud filters: IP/phone anomalies, address verification, velocity checks and blacklists. Coordinate with the marketplace security team to share signals.
- Agree reporting and reconciliation format: weekly/monthly statements with order_id, status change date, order amount and return flags; prefer automated CSV/JSON exports via API.
Typical seller mistakes and how to avoid them
- Poor product card or listings: low conversion despite traffic. Fix by improving photos, descriptions, specs and Buy Box competitiveness before scaling CPA.
- Wrong CPA level: setting CPA above the economics of the SKU. Start with tests on limited volumes and adjust.
- Ignoring returns and chargebacks: leads to overpayment. Exclude non‑confirmed orders and keep a verification window.
- Unreliable tracking setup: missing postbacks or wrong mapping. Implement server‑to‑server tracking and test thoroughly.
- Lack of dispute process: no agreed workflow for contested orders. Define escalation, evidence (order_id, timestamps, postback logs) and deadlines in the contract.
Conclusion
CPA on Kaspi.kz can be an effective channel to grow sales while keeping advertising spend performance‑linked — but success depends on correct tracking, clear contractual triggers, anti‑fraud measures and attention to product card quality. Use phased testing, automate reconciliations and monitor return rates to keep CPA campaigns profitable.
Часто задаваемые вопросы
- How do I agree the recognition moment and CPA payment with the Kaspi.kz marketplace?
- Specify the exact trigger in the contract: buyer payment confirmation, changing the order status to "completed" or the end of the return period. Parties should agree the verification window (for example, 7–14 days) and the documentary evidence procedure (a list of order_id and statuses). Payments are made per the agreed schedule after reconciliation and issuing acts/invoices.
- Which tracking methods are best to accurately link a click and an order for CPA?
- Server‑to‑server postback transferring a unique click_id and order_id is preferred; supplement with UTM tags and synchronized timestamps. Always run test orders and check for postback retries in case of data loss. API integration simplifies automated reconciliation and reduces disputed accruals.
- What measures will prevent CPA payouts for fraudulent or cancelled orders?
- Do not pay rewards until payment confirmation and the return period has expired; exclude orders with statuses "cancelled" and "returned." Implement verification rules: filter by anomalous IP/phone, check delivery address and match payment details. For unreliable partners, use payout holds and selective manual audits.
- How to correctly calculate a target CPA for a specific product on Kaspi.kz?
- Calculate CPA based on marginal contribution: target CPA should not exceed the gross margin per unit; commonly set CPA to 10–30% of average order value or 30–50% of margin depending on strategy. Include marketplace commissions, logistics and expected returns when building P&L. Test CPA levels on small volumes to find the working efficiency threshold.
- What documents and report format are needed for regular CPA reconciliation with partners?
- Agree on a weekly or monthly statement listing order_id, status change date, order amount and return markers; use reconciliation acts and electronic invoices. Automated CSV/JSON export via API speeds up processing and reduces errors. The report should also record confirmed orders count, cancellations and the final payable amount.