Publisher Integration Guide

Everything you need to start sending traffic and tracking conversions on the Komorebi Affiliate Network.

What is Komorebi Network?

Komorebi Media operates a cost-per-sale (CPS) affiliate network connecting publishers with financial product advertisers across Vietnam and Southeast Asia. When an end user completes a qualifying action — such as opening a bank account or applying for a loan — through your traffic, you earn a commission.

The platform tracks every click with a unique click_id, records conversions via a server-to-server postback, and provides real-time reporting in your publisher portal.

Getting an Account

Publisher accounts are created by the Komorebi Media team. To request access:

1. Contact your Komorebi account manager and provide your company name, traffic sources, and expected volume.
2. Once approved, you'll receive an email with a link to set your password.
3. Log in to the publisher portal, where you'll find your tracking links, earnings dashboard, and API key.

Tracking Links

Use these links in your campaigns. Each click is assigned a unique click_id that ties the eventual conversion back to your account.

Link Format

https://track.komorebimedia.com/track/{advertiser}?pub={your_username}

Example

For a publisher with username your_username promoting the advertiser your-advertiser:

https://track.komorebimedia.com/track/your-advertiser?pub=your_username

When a user clicks this link, they are immediately redirected to the advertiser's offer page with a unique click_id appended:

https://advertiser.example/landing?click_id=4a7f2e1c-...

Postback Setup

Conversions are tracked via a server-to-server (S2S) postback fired by the advertiser's mobile measurement partner (MMP) — typically AppsFlyer or Adjust — when a qualifying event occurs.

AppsFlyer Onboarding Walkthrough

Komorebi integrates with AppsFlyer as an Agency partner. Follow these steps in your AppsFlyer dashboard to grant Komorebi the access it needs and start sending attributed conversions. This mirrors AppsFlyer's exact permission and event-selection flow.

1. Add Komorebi as an Agency partner. In AppsFlyer, go to Configuration → Partner Marketplace (or Active Integrations → Add Partner), search for your agency/partner entry, and enable it for the app. If Komorebi is set up as a custom partner, use Configuration → Integrated Partners → Add a dedicated partner and enter the Komorebi partner ID supplied to you.
2. Set the attribution / click-through lookback window to match the value configured on the Komorebi advertiser (default 90 days). A mismatch causes valid postbacks to be rejected. See AppsFlyer Integration.
3. Configure the tracking link. Paste Komorebi's partner-link template into the partner's Attribution Link / Click-through URL. The template injects Komorebi's click_id into customer_user_id and maps af_siteid, af_sub1–5, and af_c_id.
4. Grant event postbacks. Open the partner's Integration → In-app events tab. Toggle "Send in-app events to this partner" on, then select "Events attributed to this partner only" (recommended) and map each in-app event (e.g. af_purchase, deposit_Trade_succeeded) you want Komorebi to receive. Map those names to the matching Komorebi event under AppsFlyer on the advertiser.
5. Configure the postback URL. For real-time postbacks, set the partner's Postback URL to Komorebi's endpoint: https://track.komorebimedia.com/postback/<slug>?click_id={click_id}&event={event_name}. For pull-based reconciliation, grant Komorebi Raw Data / Pull API access and an API token (entered in the advertiser's MMP section).
6. Grant raw-data access (for reconciliation). Under Configuration → Permissions, enable raw-data report access so Komorebi's MMP sync can pull the in-app-events export and reconcile each event against the originating click.
7. Verify. Use the postback test or your account manager's test tool to fire a sample conversion and confirm it appears as attributed in Komorebi.

HMAC Postback Signing

Komorebi supports optional per-advertiser HMAC-SHA256 signing on inbound postbacks. When a postback secret is configured for an advertiser, every postback must include a valid sig parameter or it is rejected (HTTP 403). Leave the secret blank to accept unsigned postbacks (backward compatible).

https://track.komorebimedia.com/postback/{advertiser}?click_id={click_id}&event={event}&payout={payout}&sig={hmac_sha256_hex}

AppsFlyer Integration

AppsFlyer conversions are reconciled by Komorebi's MMP sync: Komorebi pulls AppsFlyer's raw in-app-events export and matches each event back to the originating click. The match key is AppsFlyer's Customer User ID — so Komorebi's auto-generated click_id must be passed into AppsFlyer as the customer_user_id.

1. Drive traffic with your Komorebi tracking link — it appends a unique click_id to the redirect automatically.
2. Capture that click_id on the landing page (query parameter / deep link) and carry it into the app install flow.
3. In the AppsFlyer SDK, call setCustomerUserId(<click_id>) before logging events — or send customer_user_id=<click_id> on the server-to-server call — so AppsFlyer stores Komorebi's click_id against that user.
4. On each sync, Komorebi pulls the AppsFlyer in-app-events export and matches the Customer User ID column back to the click_id to approve or flag the conversion.

Adjust Integration

Adjust is push-based: unlike AppsFlyer, there is no CSV export and no pull sync. Adjust fires a server-to-server (S2S) postback to Komorebi in real time the moment a conversion is attributed, and the click_id is carried back via Adjust's {click_id} macro. Conversions are recorded the instant the postback arrives — no reconciliation pull is required.

To configure a custom postback in Adjust:

1. Log in to your Adjust dashboard and open the app.
2. Go to Settings → Partner Setup and click Add Partner.
3. Select Custom Partner and enter the postback URL below.
4. Map the click_id query parameter to Adjust's click ID placeholder {click_id}, and payout to {revenue}.
5. Configure the event tokens you want to track (e.g. install, purchase) and assign them to the event parameter.

https://track.komorebimedia.com/postback/{advertiser}?click_id={click_id}&payout={revenue}&event={event_token}

Supported Macros

REST API

Publishers can query their own performance data programmatically using the Komorebi REST API.

Authentication

All API requests must include your API key in the X-API-Key header. Your key is available in the publisher portal under the "API Access" section.

X-API-Key: kom_live_a1b2c3d4e5f6...

GET /api/v1/stats

Returns your current performance statistics: click volume, conversions by status, earnings by approval state, and a per-advertiser breakdown.

curl https://track.komorebimedia.com/api/v1/stats \
  -H "X-API-Key: kom_live_your_key_here"

{
  "publisher": "your-username",
  "status":    "active",
  "stats": {
    "clicks": 142,
    "conversions": {
      "total":    38,
      "approved": 31,
      "pending":  5,
      "rejected": 2
    },
    "earnings": {
      "approved":            465.00,
      "pending":             75.00,
      "this_month_approved": 120.00
    }
  },
  "by_advertiser": [
    {
      "advertiser":      "Your Advertiser",
      "advertiser_slug": "your-advertiser",
      "clicks":          98,
      "conversions":     26,
      "approved_payout": 390.00,
      "pending_payout":  60.00
    }
  ]
}

GET /api/v1/conversions

Returns conversion-level detail — one row per conversion — for programmatic reconciliation and optimization. Results are scoped to your account only, ordered newest-first, and paginated.

curl "https://track.komorebimedia.com/api/v1/conversions?limit=100&page=1&from=2026-07-01&to=2026-07-31" \
  -H "X-API-Key: kom_live_your_key_here"

{
  "publisher": "your_username",
  "paging": { "page": 1, "limit": 100, "total": 240, "total_pages": 3, "has_more": true },
  "conversions": [
    {
      "click_id": "…", "advertiser_slug": "tambadana", "event": "install",
      "status": "approved", "payout": 11.00, "currency": "USD",
      "sub_id": "yourSubId", "af_sub1": "yourSubId", "af_sub2": null,
      "rejection_reason": null, "timestamp": "2026-07-15 10:22:04"
    }
  ]
}

FAQ