Web advertising needs a reliable connection between the originating ad, the customer and a verified payment. Adapted from Xiaowei’s October 6, 2026 article, this guide uses a paid image-processing website to explain Simple KUMA click tracking, server-side postbacks and order deduplication.
The original headline mentions saving $50,000. That figure is not a verified saving in this guide. Actual economics depend on traffic, existing fees and engineering costs. Free software still requires hosting, a domain, backups and maintenance, and a Web tracking example does not establish that it can replace an app MMP.
What belongs in the tracker?
Simple KUMA can handle self-hosted Web click and conversion tracking, campaign management and basic reporting. The author also built a custom TikTok relay; that implementation should not be mistaken for a capability automatically enabled by installing the tracker. Your backend must still connect users and orders, verify payments and handle retries. Check the official guide against your installed version.
Connect an ad click to a verified order
- A visitor clicks an ad and reaches the website through the tracking entry point.
- The tracker creates a KUMA click_id. The website retains applicable, genuine source identifiers and associates the visit with the business user.
- When creating an order, persist its attribution association in server-side records rather than relying exclusively on cookies.
- The backend validates the payment notification and checks the order, amount, currency and payment status.
- Only after confirming payment, record the purchase with a stable event identifier and send the appropriate postbacks.
The flow is ad click → tracker → website → order → backend payment confirmation → recorded conversion → channel delivery. Loading a thank-you page is not proof of a successful payment.
Keep three identifier layers separate
| Identifier | Purpose |
|---|---|
| ttclid, fbc and fbp | Support applicable channel click or browser matching; their roles differ |
| KUMA click_id | Connect a tracked visit with signup and order activity |
| order_id, txid and event_id | Identify a transaction or event for deduplication and retries |
A KUMA click_id must not impersonate a ttclid. Do not fabricate browser identifiers or substitute the server’s information for the visitor’s. Use genuinely collected data with the necessary permission.
One order stays one purchase, even after ten retries
Suppose a visit has click ID K_DEMO_01. Order O_DEMO_01 produces event webimg:purchase:O_DEMO_01. A second purchase uses order O_DEMO_02 and its own event ID. Retrying the first order ten times must keep its original event ID.
The example payment is 19.90 USD. Read the real amount and currency from backend order records, not browser input. One click can lead to several genuine purchases, so deduplicating solely by click_id would lose legitimate repeat orders. Make processing idempotent by order and event type, then map txid, event_id and event keys according to your installed version. Consult the official postback reference for the actual recording rules.
Check browser events, tracker records and channel delivery
In this implementation, verified backend payments determine whether a purchase happened. If Meta Pixel and CAPI report the same Purchase, align the event name and stable event ID. Other channels require their own field mappings. A conversion in KUMA does not prove Meta or TikTok accepted it. Keep inbound and outbound delivery results and preserve the original event ID on retries.
Test before scaling
- Use a real test click to connect signup, an order and payment.
- Replay a payment notification and reload the thank-you page; neither should create another purchase.
- Place two paid orders from the same source and verify two separate purchase events.
- Failed or unverified payments must not generate successful purchases.
- Reconcile backend orders, tracker records and channel responses before increasing spend.
Compare total operating costs before replacing a tool. Do not risk a large advertising budget on an untested tracking flow just to save subscription fees. Read our attribution discrepancy guide, ad funnel diagnostics and advertising tutorials. Adapted from Xiaowei’s original article.
FAQ
Can Simple KUMA fully replace AppsFlyer or Adjust?
This Web example does not establish that. Compare your app attribution, SDK, privacy framework, channel support and service requirements first.
Does a free tracker guarantee $50,000 in savings?
No. The original headline is not a verified saving here. Include hosting, development and maintenance when comparing costs.
Can one click_id have more than one purchase?
Yes. Give separate orders distinct transaction or event identifiers, retain the identifier on retries, and configure conversion recording for your version.
Why not rely only on a thank-you page?
The page can be refreshed, blocked or interrupted. Verify payment notifications and the order’s amount, currency and status on the backend.