Events & Conversion Reporting
Conversion reporting endpoints are prefixed with /track at https://track.adbnk.co.
track_id
track_id is an opaque string issued by the server. Use it exactly as received — don't parse or modify it.
Impressions and clicks are measured automatically by the ADBNK SDK. Use impression_url / click_url exactly as returned and don't call them yourself.
Landing-page macros
The landing-page URL supports macro substitution, written as {macro} or ; macro names are case-insensitive. On click, the platform replaces each macro with its real value, e.g. https://example.com/?cid={click_id}&camp={campaign_id}.
| Macro | Meaning |
|---|---|
click_id | ID of this click — required for conversion attribution: send it back unchanged when the conversion happens |
campaign_id / adgroup_id / ad_id / creative_id | Campaign, ad group, ad and creative IDs |
zone_id / site_id / site_domain | Zone ID, site ID, site domain |
country | Two-letter country code |
device | desktop / mobile / tablet |
os / browser | Operating system, browser |
timestamp / random | Unix timestamp, random number |
Values are URL-encoded; a macro with no value is replaced with an empty string; unknown {xxx} placeholders are left untouched.
Automatically appended parameters: on click, the platform appends adbnk_click_id, adbnk_zone_id, adbnk_campaign_id, adbnk_ad_id, adbnk_creative_id and adbnk_site_id to the destination URL. Parameters without a value are skipped, parameters already present in the URL are not duplicated, only http/https URLs are affected, and parameters are inserted before any #fragment. You can read the click ID and source information from these names directly; send adbnk_click_id back when reporting a conversion. For country, device and other details, add the macros above where you need them.
Conversion reporting
GET /track/conversion or POST /track/conversion
Reporting via the conversion tracker code is recommended; the legacy click_id method is also supported.
| Param | Type | Required | Description |
|---|---|---|---|
code / c | string | Yes* | Conversion tracker code tracking_code (recommended) |
click_id / clickid | string | No | Click ID, for attribution to a specific click |
value / payout | number | No | Conversion value; defaults to the tracker's configured default |
type | string | No | Only used when no code is sent (legacy mode), default conversion; ignored when a tracker code is present — the event type follows the tracker |
Without code, it's handled in legacy mode where click_id is required, otherwise it returns 400.
curl "https://track.adbnk.co/track/conversion?code=cvt_your_tracking_code&click_id=YOUR_SAVED_CLICK_ID&value=59.9"{ "code": 0, "msg": "OK", "conversion_id": 10086 }Conversion pixel
GET /track/conversion.gif
Reports a conversion silently as a pixel (returns a 1×1 GIF). The tracking code must be passed as c (code is not accepted here); click_id and value work as above, suitable for landing pages that can't make AJAX calls.
<img src="https://track.adbnk.co/track/conversion.gif?c=cvt_your_tracking_code" width="1" height="1" alt="" />S2S Postback
GET /track/postback or POST /track/postback
Server-to-server postback, with the same params as /track/conversion, suitable for an advertiser's server to actively post back when a conversion happens. The template the console generates:
https://track.adbnk.co/track/postback?c=cvt_your_tracking_code&click_id={click_id}&value={payout}See S2S Postback for responses and details.
Valid traffic and attribution
- Valid traffic: only valid traffic is billed; the settlement statement is final.
- Attribution: conversions are attributed via
click_idto the originating campaign, ad group and creative.
Conversion tracker management (advertiser)
Trackers are created and managed by advertisers at /api/advertiser/trackers (auth required):
| Method | Path | Description |
|---|---|---|
GET | /api/advertiser/trackers | Tracker list |
POST | /api/advertiser/trackers | Create a tracker |
GET | /api/advertiser/trackers/{id}/code | Get the tag/postback code |
POST | /api/advertiser/trackers/{id}/regenerate-code | Regenerate the code |
GET | /api/advertiser/trackers/{id}/conversions | Conversion details |
GET | /api/advertiser/trackers/{id}/stats | Conversion stats |
Create tracker (POST /api/advertiser/trackers) params:
| Param | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Tracker name |
type | string | No | Type, default PIXEL (also POSTBACK, etc.) |
event_type | string | No | Conversion event type, default CUSTOM |
conversion_value | number | No | Default conversion value |
attribution_window | int | No | Attribution window (days) |
postback_url | string | No | Postback URL |
pixel_code | string | No | Pixel code |
After creation, the system auto-generates a tracking_code, which is the code used when reporting.
Related reading: Conversion Tracking guide · Ad Request API