In the ever-evolving digital advertising landscape, Waterfall Latency plays a pivotal role in successful ad monetization strategies. Recognizing its importance, we offer two specialized reports to aid in this domain: Placement Latency and Waterfall Latency. These reports are designed to provide clarity and actionable insights into latency issues, which are crucial for ad optimization.
What's in the Report?
Our Waterfall Latency Report is crafted to present latency data in the most straightforward manner. It helps identify potential opportunities for performance enhancements by providing a clear breakdown of latency metrics.
For full instructions on the functionality available to you with DT's Dynamic Reporting, click here.
Upon accessing the Waterfall Latency report, the default view provides:
- Placement average latency over the past seven days.
- Breakdown by App Name, Placement Name, and Instance Name.
Waterfall Latency Report Dimensions
The report includes several dimensions grouped as follows:
|Date and time of the report.
|The DT unique identifier for the app.
|The name of the app as written in the app settings.
|The version of the app.
|The DT unique identifier for the placement.
|The name of the placement as written in the placement settings.
Placement type describes the format and location of ads in your app according to the placement setting when it was created.
Placement types can be either:
|DT FairBid or DT Exchange.
|Demand Source Name
|Demand partners who bid in the auction.
|The operating system of the phone/device.
|The country from which the ad request was received.
Waterfall Latency Report Metrics
Metrics appear in the left pane under the dimensions. Set out below are the metrics:
Event means the number of times FairBid SDK has sent a request to each Ad Network's instance in a waterfall.
|Instance Fill rate
|The Rate means the number of times an instance gets Bids (Fills) on Instance Requests. The calculation is Bids (Fills) divided by Instance Requests.
A Fairbid SDK event means the number of times an ad was shown to a user.
This is not the same as Ad Impressions, as in some cases, ad networks do not count ads shown as valid Ad Impressions.
The average cost per thousand impressions on the SDK level (without possible adjustment from the ad network)
Calculated as: 1000 * Sum (Ad Network Revenue)/ Sum (Impressions)
|Instance Latency (sec.)
The average time it took to get a response (Bid, No Bid, Timeout) from the requested Ad Network's instance in a waterfall.