Impression Level Data

DT Exchange enables you to access detailed information for each impression through the impressions callback APIs. The information includes, for example, which demand source served the ad and its expected or exact revenue.

The following table describes Impression Level Data attributes.

Property Name	Description
advertiserDomain	A unique identifier for a set of campaigns for the same advertiser.
campaignId	A unique identifier that represents a Campaign.
creativeId	A unique identifier that represents the creative in the bid response. This can be useful when a particular creative causes user experience issues.
country	Identifier of the country of the ad impression (in ISO country code).
impressionId	A unique identifier for a specific impression.
demandSource	Identifies the demand source name of the buy-side/demand-side entity that purchased the impression: When mediated networks win an impression, the mediated network's name appears. When a DSP buying through the programmatic marketplace wins the impression, the DSP's name appears.
pricing	Object includes two properties about the impression's pricing, net payout value, and currency type.
Pricing.value	The impression's net payout value.
Pricing.currency	The impression's currency type.
video	Object includes two properties about the video: duration and skippable. The object is null for non-video impressions.
Video.skippable	An indication of whether the video is skippable or not. Possible values: true, false.
Video.duration	The duration of the video in seconds, for example, 15 seconds.

Receiving Per-Ad Impression Data

All unit controllers allow you to access the ImpressionData object through their callback APIs, using an Event Listener subclass with a suffix of WithImpressionData.

The example below showcases how you can access these data on a full screen placement integration

InneractiveAdViewUnitController

Java

InneractiveAdViewUnitController controller = 
    (InneractiveAdViewUnitController) bannerSpot.getSelectedUnitController();

controller.setEventsListener(
    new InneractiveAdViewEventsListenerWithImpressionData() {
        @Override
        public void onAdImpression(InneractiveAdSpot adSpot, ImpressionData impressionData) {
            Log.v("ImpressionData", impressionData.toString());
        }

        // … all other callbacks and methods
    }
);

InneractiveFullscreenUnitController

Java

InneractiveFullscreenUnitController fullscreenUnitController = 
    (InneractiveFullscreenUnitController) fullScreenSpot.getSelectedUnitController();

fullscreenUnitController.setEventsListener(
    new InneractiveFullscreenAdEventsListenerWithImpressionData() {
        
        @Override
        public void onAdImpression(InneractiveAdSpot adSpot, ImpressionData impressionData) {    
            Log.v("ImpressionData", impressionData.toString());
        }
        
        // … all other callbacks and methods

    }
);

Receiving Impression Data Globally

In addition to the per-ad callback, this listener also contains details about the relevant Placement ID (spot ID) and Unit ID.

Java

void OnGlobalImpressionDataListener.onImpression(
    String spotId, 
    String unitId, 
    ImpressionData impressionData
);

The static impression data listener holds a hard reference, which might cause memory leaks if you use it incorrectly.

DT recommends using the relevant InneractiveAdManager.clearImpressionDataListener() method when global ad impression data is no longer required.

Java

InneractiveAdManager.setImpressionDataListener(new OnGlobalImpressionDataListener() {
    @Override
    public void onImpression(String spotId, String unitId, ImpressionData impressionData) {
        Log.v("impressionStaticData", 
              "spotId: " + spotId + 
              ", unitId: " + unitId + 
              ", impressionData: " + impressionData);
    }
});