Revenue Integration Guide

Overview

DigiKube's bidder serves your JS tag template as the ad creative via OpenRTB. When the bidder wins an auction, your tag is returned with macros substituted (bid ID, subid, etc.). Your ad server should fire postback pixels at key events so DigiKube can optimize bids based on real revenue data.

How It Works

HTML Template & Macros

Your HTML template will be loaded like:

<script src="https://your-server.com/widget.js"></script>
<script>window.init({subid: 'camp001__US__mobile', bid: 'bid-abc123-imp1'});</script>

Available macros (configured per campaign in the creative):

Two template syntaxes: $${MACRO} for bid-time context (used in HTML templates and content field values). {{field}} for structured content fields (used in SSP output templates).

Click Redirect Tracking

DigiKube can wrap creative click URLs through a server-side redirect for accurate first-party click counting. Configure the mode per campaign under Tracking → Click Tracking.

Click Tracking Modes

Click Redirect Endpoint

When redirect mode is active, click URLs are automatically wrapped at bid time. The endpoint:

GET https://rtb.dkadx.com/click?b={bid_id}&url={encoded_destination_url}

The ${CLICK_URL} Macro

Use the ${CLICK_URL} macro in your HTML template to reference the creative's click URL. When the campaign's click tracking mode is redirect, this macro is automatically substituted with the wrapped redirect URL. Otherwise it resolves to the raw destination URL.

Example creative template:

<a href="${CLICK_URL}">
  <img src="https://cdn.example.com/banner.jpg">
</a>

Set the click URL in the creative settings. S2S campaigns: click URLs extracted from vendor responses are automatically wrapped when redirect mode is active — no template changes needed.

Postback Pixels

Fire these HTTP GET requests from your ad server (server-side). All endpoints return a 1x1 transparent GIF.

https://rtb.dkadx.com/pb/imp?b={bid_id}&v={estimated_rpc}

https://rtb.dkadx.com/pb/click?b={bid_id}&v={rpc_value}

https://rtb.dkadx.com/pb/conv?b={bid_id}&v={cpa_value}&ts={iso8601}

Parameters

SubID Format

The subid parameter encodes campaign dimensions for revenue reporting and bid optimization.

Examples:

Revenue Reports (Optional Calibration)

For maximum bid accuracy, configure a daily report endpoint per campaign. DigiKube polls your endpoint daily with ?date=YYYYMMDD and calibrates its eCPM model with final approved revenue figures.

Expected response format (JSON array):

[
  {
    "subid":        "69b6bd32__US__mobile",
    "revenue":      150.00,
    "clicks":       200,
    "impressions":  50000,
    "date":         "2026-03-16"
  }
]

Configure the report URL in the campaign settings. DigiKube reconciles approved revenue against postback estimates and adjusts bid shading accordingly.

Partner Stats API

Supply partners can query stats about their traffic via a dedicated API endpoint. Authentication uses the SSP endpoint_id as the API key.

GET https://stats.dkadx.com/api/stats?key={endpoint_id}&startDate=YYYY-MM-DD&endDate=YYYY-MM-DD&breakdown=DATE&metrics=BID_REQUESTS,BIDS,WINS,IMPRESSIONS,GROSS_REVENUE

Available Metrics:

Breakdown options: DATE (daily) or HOUR (hourly). Max date range: 31 days. Auth via query param key= or header Authorization: Bearer.

Native Ads

Structured creatives can serve both banner and native formats. The SSP defines output templates that render creative content into the required format. Templates use {{field}} for content fields and ${MACRO} for bid-time context.

Structured Content Fields

SSP Output Template Examples

Example 1: Simple native (title + click)

{"native":{"ver":"1.1","link":{"url":"{{click_url}}"},"assets":[{"id":1,"title":{"text":"{{title}}"}}]}}

Example 2: Full native (title + image + description + sponsored)

{"native":{"ver":"1.1","link":{"url":"{{click_url}}"},"assets":[{"id":1,"title":{"text":"{{title}}"}},{"id":2,"img":{"url":"{{image_url}}","w":300,"h":250}},{"id":3,"data":{"type":2,"value":"{{description}}"}},{"id":4,"data":{"type":1,"value":"{{sponsored_by}}"}}],"eventtrackers":[{"event":1,"method":1,"url":"https://your-tracker.com/imp?id=${BID_ID}"}]}}

Example 3: Banner from structured content

<div style="width:300px;height:250px;position:relative">
  <a href="{{click_url}}" target="_blank">
    <img src="{{image_url}}" width="300" height="250">
    <div style="position:absolute;bottom:0;background:rgba(0,0,0,0.7);color:#fff;padding:8px;width:100%;box-sizing:border-box">
      <strong>{{title}}</strong><br>
      <small>{{sponsored_by}} · {{cta}}</small>
    </div>
  </a>
</div>

Note: For native ads, impression tracking must use burl (server-side), not ADM pixel (cannot append HTML to JSON). Configure this in the SSP settings.

Testing Your Integration

curl "https://rtb.dkadx.com/pb/click?b=test-bid-001&v=0.50"