AdMob Dynamic Adapter

Step 1. Add AscendX AdMob Custom Adapter to Your Project

Android

repositories {
    maven { url "https://asia-southeast1-maven.pkg.dev/knorex-rtb/ascendx-sdk" }
}
dependencies {
    implementation 'com.knorex:ascendx-mobile-sdk-admob-custom-adapter:1.12.0'
}

iOS

target 'My-App' do
    pod 'AscendXAdMobAdapter', '~> 1.7.0' , :source => 'https://bitbucket.org/knorexteam/cocoapods-specs.git'
end

Step 2. Add AscendX to Your AdMob Mediation Waterfall

2.1 Add AscendX as a Custom Event in Your AdMob Dashboard

Follow the steps in AdMob official documentation to add a Custom Event to your mediation waterfall: Set up a custom event

iOS Adapter Class Name: TBU

Android Adapter Class Name: com.ascendxnow.mobile.admob.adapters.dynamic.AscendXMediationAdapter

2.2 Add AscendX to Your Mediation Group

1. Follow the steps in AdMob official documentation to add AscendX as a Custom Event to your mediation group: Add your custom event to a mediation group

2. Fill in the Required Fields to add mapping

   Mapping Name – Any value to help you identify the mapping

   Class Name – Select the appropriate adapter class name based on your target platform (iOS or Android)

   Network eCPM (optional) – A numeric eCPM value for this mapping (e.g., 2.0). It should match the "fp" value in the Custom Parameters and the eCPM you set on the AdMob line item. Setting Network eCPM helps AdMob detect and notify you of configuration mismatches.

   Example:

   • Network eCPM: 2.0

   • Custom Parameters: {"fp": 2.0}

   Notes:

   • Keep this value synchronized with your line-item eCPM to avoid mapping issues and missed bids.

   Parameter - Define eCPM floor, AscendX provided Account ID and Ad Unit ID by using the following key-value pairs

   Key	Value Type	Required	Description	Example
   fp	Double	Yes	eCPM floor price	2.0
   aid	String	Yes	AscendX provided Account ID	A1b2C3d4E5F6G7H8I9J0
   auid	String	Yes	AscendX provided Ad Unit ID	2fs3aFgs5st6
   fetch	Boolean	No	Whether to make a network request (default is false)	true

   By default (when fetch is omitted or set to false), AscendX will not perform a network request to the AscendX server. Instead, it will check for any locally cached bid response and use it if available.

   Example (fetch omitted — default is false, no network call):

   {"fp": 2.0, "auid": "2fs3aFgs5st6", "aid": "A1b2C3d4E5F6G7H8I9J0"}

   Example (explicit fetch set to false):

   {"fp": 10.0, "auid": "2fs3aFgs5st6", "aid": "A1b2C3d4E5F6G7H8I9J0", "fetch": false}

   Line items with fetch: true will request ads from the AscendX server and render if any qualified ad is returned.

   {"fp": 100.0, "auid": "2fs3aFgs5st6", "aid": "A1b2C3d4E5F6G7H8I9J0", "fetch": true}

Step 3. Verify your integration

To ensure proper integration, always start by configuring your AscendX ad units to serve test ads. This helps verify that everything is set up correctly before going live.

Ad Unit ID	Format	CPM Price	Custom Parameters
demo-waterfall-banner-ad	Banner	10.0	{"fp":10.0,"aid":"demo-account","auid":"demo-waterfall-banner-ad","fetch":true}
demo-waterfall-native-ad	Native	10.0	{"fp":10.0,"aid":"demo-account","auid":"demo-waterfall-native-ad","fetch":true}
demo-waterfall-interstitial-ad	Interstitial	50.0	{"fp":50.0,"aid":"demo-account","auid":"demo-waterfall-interstitial-ad","fetch":true}
demo-waterfall-rewarded-ad	Rewarded	50.0	{"fp":50.0,"aid":"demo-account","auid":"demo-waterfall-rewarded-ad","fetch":true}

ASX banner test ad

ASX Interstitial/Rewarded test ads

---

Best Practices: Dynamic Fetching Strategy

Dynamic Fetching allows AscendX to behave like a traditional waterfall adapter while maximizing fill rates through price granularity. With this setup, you can increase your opportunities to serve AscendX bids without adding latency to your stack.

How Dynamic Fetching Works

AscendX provides two behaviors depending on the configuration of each line item:

1. fetch: true

• Triggers a network request to AscendX.
• Retrieves and caches a fresh bid response.
• Acts similarly to a standard mediation adapter call.

2. fetch: false or omitted

• Does not initiate a new network request.
• Uses the locally cached bid from the most recent fetch: true line item.
• Enables instant checks with zero network overhead.

By combining these two modes, publishers can create a waterfall structure that is both efficient and flexible.

Recommended Setup Strategy

To maximize AscendX performance, we recommend creating multiple line items with different floor prices. This provides:

• Price granularity: Better alignment with AscendX's dynamic bid values.
• Higher fill rates: More line items → more opportunities to match bids.
• No additional latency: Non-fetch items read exclusively from cache.
• Retry points: Additional fetch: true line items allow AscendX to request again at lower floors if no qualified bid is cached.

A common approach is

1. Place a fetch: true item at your highest priority floor.
2. Add 2–3 non-fetch line items directly below it.
3. Add a second fetch: true item at a mid-lower floor.
4. Follow with additional non-fetch floors as needed.

Example Configuration:

Line Item	fetch	fp	Network eCPM	Behavior
ASX-2.0	true	2.0	2.0	Initiates a network request; fills or caches the returned bid
ASX-1.9	false	1.9	1.9	Uses cached bid if price >= 1.9
ASX-1.8	false	1.8	1.8	Uses cached bid if price >= 1.8
ASX-1.0	true	1.0	1.0	Second fetch point; requests a new bid if required
ASX-0.9	false	0.9	0.9	Uses cached bid if price >= 0.9
ASX-0.8	false	0.8	0.8	Uses cached bid if price >= 0.8

→ This structure ensures efficient waterfall progression without unnecessary network calls.

Key Benefits

1. Traditional waterfall behavior:

   Each fetch: true line item functions like a full adapter call, aligning with familiar mediation setups

2. Price granularity:

   Multiple floors increase the likelihood that AscendX's bid will qualify at one of your line items.

3. Zero Additional Latency:

   Non-fetch floor prices (fetch is omitted or set to false) rely solely on cached responses—no network calls, no waiting.

4. Controlled Retry Logic:

   Strategic placement of fetch: true at different price points provides multiple chances to fetch bids

5. Flexible and Transparent:

   Publishers retain full control over line item structure and behavior.