Adverty

Revenue Data Integration to analytics system

 

To accurately track Lifetime Value (LTV) and Return on Ad Spend (ROAS), Adverty’s In-Play revenue can be piped into your centralized analytics or attribution system. Adverty  do not use standard mediation “Ad Unit IDs.” Instead, we identify revenue streams by their physical properties.

1. The Data Source: OnAdReady Callback

The primary hook for financial data in the Adverty SDK is the OnAdReady event. Unlike traditional banners, this event provides the bid value and the dimensions of the unit being filled.

  • Signature: void OnAdReady(double price, int width, int height)
  • Currency: Adverty programmatic bids are processed in USD.

2. Normalizing Data for Statistics Systems

Most tracking systems (Adjust, Firebase, AppsFlyer) require a string-based Ad Unit Name and a Currency Code to categorize revenue. Since the SDK does not pass these as strings, we generate them dynamically:

  • Generated Ad Unit ID: We concatenate the width and height (e.g., “adverty_1920x1080”). This ensures your statistics system can group revenue by formats.
  • Standardized Currency: We hardcode “USD” to ensure the ingestion engine validates the decimal value correctly.

3. Implementation Examples

Example A: Firebase Analytics (ILRD)

Firebase uses the OnAdReady event to calculate revenue metrics.

C#

// Inside the Adverty OnAdReady callback:

string adUnitId = $”adverty_{width}x{height}”;

 

Parameter[] adParameters = {

    new Parameter(“ad_platform”, “Adverty”),

    new Parameter(“ad_unit_name”, adUnitId),

    new Parameter(“value”, price),

    new Parameter(“currency”, “USD”)

};

FirebaseAnalytics.LogEvent(“ad_impression”, adParameters);

Example B: Adjust (Impression Level Revenue)

Adjust uses a dedicated AdjustAdRevenue object to attribute revenue back to specific user acquisition sources.

C#

// Inside the Adverty OnAdReady callback:

AdjustAdRevenue revenue = new AdjustAdRevenue(“adverty”);

revenue.setRevenue(price, “USD”);

revenue.setAdRevenueUnit($”adverty_{width}x{height}”);

 

Adjust.trackAdRevenue(revenue);

4. Integration Best Practices

  • Granularity: By using dimensions in the naming convention, your UA (User Acquisition) team can see which specific ad layouts provide the highest yield.
  • Verification: To verify the pipeline, use the Firebase DebugView or Adjust Sandbox. Note that during testing (Sandbox Mode), Adverty may return a price of 0.0.
  • Frequency: This event triggers every time an ad is successfully cached and priced for a specific placement, providing a near real-time stream of expected revenue.

 

  • iab
  • iab
  • Tag
  • IAB Europe