Digibid Attribution Conversion Postback Integration Guide (S2S)

Version: v2 (2026-08)

No on-page code required · Your server reports conversion events directly

Server-to-Server GET / POST click_id attribution

Receiving Endpoints

Americas / Brazil (default)

https://cb-use.digibid.com/tracking

Asia-Pacific

https://cb-apac.digibid.com/tracking

1. How It Works

When digibid serves an impression/click, it appends a unique, encrypted click ID to your landing URL via click_id. Your system captures and stores this value; when a conversion happens, your server sends a postback to the digibid cb-use postback server, carrying the click_id + event type, and digibid decrypts the click_id to complete attribution.

How Digibid S2S conversion postback works: (1) digibid serves the ad and injects click_id into the landing URL; (2) your landing page captures and stores click_id mapped to the user; (3) the user converts (registration / first deposit / deposit); (4) your server sends the postback: GET cb-use…/tracking?click_id=…&type=N; (5) cb-use.digibid.com receives it, decrypts click_id, attributes the conversion and writes it to reporting. click_id is encrypted ciphertext (the core attribution key) and must be passed through as-is; the postback is sent server-side, so no on-page code is needed. — Figure 1 · S2S conversion postback flow (inject → capture & store → conversion → server postback → cb-use receives & attributes)

digibid serves the ad — click_id is injected into the landing URL.
Your landing page — captures and stores click_id ↔ user.
User converts — registration / first deposit / deposit.
Your server sends the postback — GET cb-use…/tracking?click_id=…&type=N
cb-use.digibid.com receives it — decrypts click_id · attributes · writes to reporting.

click_id is encrypted ciphertext (the core attribution key) and must be passed through as-is; the postback is sent from your server, so no code needs to be installed on the page.

2. Step 1: Capture and Store click_id from the Landing URL

digibid injects click_id into the landing URL when serving, for example:

Landing URLhttps://yoursite.com/?click_id=${click_id}

When booking the landing_url in the digibid UI, you must include the click_id macro. The parameter name is provided by you (it does not have to be click_id).

Screenshot of the Ad Details form in the Digibid console: the Landing URL field contains a URL carrying the click_id macro, in the form https://…?click_id=${click_id} — Digibid UI · the Landing URL under Ad Details must carry the `${click_id}` macro

Note: click_id is encrypted ciphertext and the core attribution key. Pass it through as-is: do not modify / truncate / reuse / re-encode it.

3. Step 2: Send the Postback on Conversion (Postback API)

Once a conversion is confirmed, your server sends a request to the postback server (GET is sufficient, same endpoint as the pixel; POST is also supported):

RequestGET https://cb-use.digibid.com/tracking?click_id=<click_id>&type=&did=&ua=&ip=&adv_app_bundle=

Parameters:

Postback request parameters
Parameter	Required	Description
`click_id`	Recommended	The encrypted click ID carried on the landing URL — the core attribution key; pass it through as-is. If attribution fails, still post back all events, with click_id empty or omitted.
`type`	Yes	Event code (see Section 4): `8` install / `12` registration / `13` deposit / `18` login / `19` first deposit / `17` reject
`event_id`	Recommended	Unique event ID on your side; it must stay the same when the same real event is retried.
`did`	Recommended	Device id, android id or ifa
`ua`	Recommended	User Agent (url encode)
`ip`	Recommended	IP address of the end user
`adv_app_bundle`	Recommended	App bundle and related info of the advertised app; please include adv_app_bundle on every request. Custom field, max length 256.
`uid`	Recommended	The end user's registration id in your system
`purchase`	Required for deposits	Amount (when `type=13/19`), e.g. `9.9`.
`currency`	Optional	ISO 4217 currency code, default `USD`, e.g. `BRL` for Brazil; only reported together with an amount.
`_`	Optional	Cache-busting random value (e.g. a timestamp). Add it when the same user posts back the same kind of event multiple times, to make sure every request actually arrives.

Success response: HTTP 200 means the event was received.

4. Event Types (type codes)

digibid uses numeric type codes for each layer of the conversion funnel (a different event is simply a different code — no need for goal=2/3 style layering as in some networks); the English / Chinese aliases in the table below are also accepted.

Event types and type codes
Event	type	Aliases (also accepted)
Install / open	8	`install` / `open`
Registration	12	`register` / 注册
Login	18	`login` / 登录
First deposit (FTD)	19	`firstpurchase` / 首充
Deposit (cumulative, total deposits)	13	`purchase` / `recharge` / 充值 / 总充值
Install rejected	17	`reject` / 拒绝安装

5. Example Requests

HTTP# Install / open
GET https://cb-use.digibid.com/tracking?event_id=e123&click_id=<click_id>&type=8&adv_app_bundle=com.test.app&ip=1.1.1.1&did=ffc225f9-8ec7-45bc-90f0-c973398a4d1c&ua=Dalvik%2F2.1.0+%28Linux%3B+U%3B+Android+13%3B+Pixel+7+Build%2FTQ3A.230901.001%29

# Registration
GET https://cb-use.digibid.com/tracking?event_id=e123&click_id=<click_id>&type=12&adv_app_bundle=com.test.app&ip=1.1.1.1&did=ffc225f9-8ec7-45bc-90f0-c973398a4d1c&ua=Dalvik%2F2.1.0+%28Linux%3B+U%3B+Android+13%3B+Pixel+7+Build%2FTQ3A.230901.001%29

# Login
GET https://cb-use.digibid.com/tracking?event_id=e123&click_id=<click_id>&type=18&adv_app_bundle=com.test.app&ip=1.1.1.1&did=ffc225f9-8ec7-45bc-90f0-c973398a4d1c&ua=Dalvik%2F2.1.0+%28Linux%3B+U%3B+Android+13%3B+Pixel+7+Build%2FTQ3A.230901.001%29

# First deposit succeeded (with amount + currency)
GET https://cb-use.digibid.com/tracking?event_id=e123&click_id=<click_id>&type=19&purchase=9.9&currency=BRL&adv_app_bundle=com.test.app&ip=1.1.1.1&did=ffc225f9-8ec7-45bc-90f0-c973398a4d1c&ua=Dalvik%2F2.1.0+%28Linux%3B+U%3B+Android+13%3B+Pixel+7+Build%2FTQ3A.230901.001%29

# Deposit succeeded (cumulative)
GET https://cb-use.digibid.com/tracking?event_id=e123&click_id=<click_id>&type=13&purchase=99.9&currency=BRL&adv_app_bundle=com.test.app&ip=1.1.1.1&did=ffc225f9-8ec7-45bc-90f0-c973398a4d1c&ua=Dalvik%2F2.1.0+%28Linux%3B+U%3B+Android+13%3B+Pixel+7+Build%2FTQ3A.230901.001%29

Requirements:

Send only after the MMP, SDK or your server has confirmed success;
Pass click_id through as-is — do not truncate, decrypt, or re-encode its content;

Success response: HTTP 200 means the event was received.

6. Key Requirements / Notes

click_id: conversions without a valid click_id cannot be attributed. If attribution fails, please still post back the event; click_id may be empty or omitted.
Set adv_app_bundle to the bundle of the app; including adv_app_bundle on every request is recommended.
Deposits / first deposits must carry purchase (+ optional currency); for a first deposit, post back both type=19 and type=13.