Android端能否将Admob Ad ID存入变量并支持动态切换？

Absolutely, this approach is technically feasible—but there are critical technical and policy hoops you’ll need to jump through to make it work without running into issues. Let’s break this down:

Technical Implementation #

Most major ad platforms (like Google AdMob, Ad Manager) support dynamic ad unit ID configuration—you don’t have to hardcode IDs in your AndroidManifest.xml or build files. Instead, you can pass the user-inputted ID directly when initializing your ad objects.

For example, here’s how you’d set a dynamic Ad Unit ID for a Banner ad in Kotlin:

// Get the user's input from an EditText
val userProvidedAdUnitId = binding.etAdUnitId.text.toString().trim()

// Validate the ID format first (e.g., AdMob IDs follow ca-app-pub-XXXXXXXXXXXXXXXX/YYYYYYYYYY)
if (isValidAdUnitId(userProvidedAdUnitId)) {
    val adView = AdView(requireContext())
    adView.adUnitId = userProvidedAdUnitId
    adView.adSize = AdSize.BANNER
    
    // Add the AdView to your layout and load the ad
    binding.adContainer.addView(adView)
    adView.loadAd(AdRequest.Builder().build())
} else {
    Toast.makeText(requireContext(), "Invalid Ad Unit ID format", Toast.LENGTH_SHORT).show()
}

// Helper function to validate ID format
private fun isValidAdUnitId(id: String): Boolean {
    return id.matches(Regex("ca-app-pub-\\d+/\\d+")) // Adjust regex for your target ad platform
}

Key technical notes:

• Input validation: Always validate the format of the user’s input to avoid unnecessary ad load failures or errors. Each ad platform has a specific ID format—make sure your regex matches it.
• Ad state handling: Implement ad load callbacks (AdListener) to notify users if the ad loads successfully, fails, or is clicked. This improves UX and helps debug issues.
• Permissions: Don’t forget to include required permissions (like INTERNET and ACCESS_NETWORK_STATE) in your AndroidManifest.xml—these are mandatory for ad networks to function, regardless of how you set the ad unit ID.

Critical Policy Considerations #

This is where things get tricky. Most ad platforms strictly prohibit allowing users to input arbitrary third-party Ad Unit IDs in public apps. Here’s why:

• Platforms like Google AdMob require all ad units used in your app to be registered under your own developer account. Allowing random users to plug in their own IDs could lead to ad fraud, unauthorized ad serving, or violation of content policies (e.g., inappropriate ads being served through your app).
• Violating these policies can result in your ad account being suspended, your app being removed from the Google Play Store, or legal action in severe cases.

That said, there are exceptions:

• If your app is a developer tool (e.g., for testing ad implementations) and is only used by trusted users or distributed privately, some platforms may allow this (but always check their official policies first).
• If you’re building the app for your own internal testing (switching between your own ad units), this is completely allowed and common practice.

Final Verdict #

Technically, yes—you can absolutely build this feature. But before releasing it to the public, read your target ad platform’s program policies carefully to avoid getting your account or app banned. For internal testing or private developer tools, it’s a solid approach. For public consumer apps, this is almost certainly against platform rules.

内容的提问来源于stack exchange，提问作者Oddy