Digital Turbine

Datafly Signal reports attributed conversion actions to Digital Turbine (formerly Fyber / DT Offer Wall) using its Server-to-Server (S2S) tracking API. When a user completes a tracked action, Signal fires a real-time postback to Digital Turbine’s actions endpoint so the conversion is credited to the originating Digital Turbine campaign.

This is a mobile app-install / in-app action attribution integration. Conversions are matched by the campaign AppID plus the click token (the subid Digital Turbine appended to the original Click URL) and the device advertising ID (GAID on Android, IDFA on iOS). It is not a web pixel — events must carry mobile advertising identifiers.

Prerequisites

Before configuring Digital Turbine in Signal you need:

• An active Digital Turbine advertiser campaign created in the ACP Edge Console.
• Your campaign AppID (from the campaign details, or from your Digital Turbine account manager).
• The list of action IDs your campaign expects (each tracked action is defined per-campaign in ACP Edge — for example a tutorial-complete, registration, or purchase action).
• Your app’s Click URL flow must persist the click token that Digital Turbine appends, so Signal can return it as subid.

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

GET https://service.fyber.com/actions/v2?appid={appid}&action_id={action}&answer_received=0&subid={click_id}&ip={ip}&google_ad_id={gaid}

All fields travel in the URL query string. There is no request body. Signal injects appid from your config and always sends answer_received=0 (the required value for an attributed action). The endpoint returns HTTP 200 with an empty body on success; any other status indicates a malformed request.

Identity Signals

Digital Turbine matches each action postback to a click using these signals. Signal populates them automatically from the event:

Event Mapping

Only conversion actions route to Digital Turbine — pageviews and other non-conversion events are dropped. Each Signal event maps to a Digital Turbine action_id.

Default preset

Example: Conversion Event

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "ORD-001",
  total: 19.99,
  currency: "USD"
});

Digital Turbine postback sent by Signal:

GET https://service.fyber.com/actions/v2?appid=9ed9fdf1b5546748d56b4a01298a84fd&action_id=purchase&answer_received=0&subid=2fc13660-4509-f1a2-a0f1-61198a460826&ip=178.210.115.51&google_ad_id=38400000-8cf0-11bd-b23e-10b96e40000d&google_ad_id_limited_tracking_enabled=false

A 200 OK with an empty body confirms the action was accepted.

Testing

Troubleshooting