Google today introduced three AI tools for AdMob, its mobile app advertising and monetization platform, setting out a schedule that runs from software that developers can install now to account-level agents that will not act on a publisher's behalf until later in 2027. The announcement, published on Google's Keyword blog under the Publisher Connections section and written by Naomi Ben-Ayoun, General Manager of AdMob, covers a Gemini-built assistant called Ask AdMob, a set of AdMob agent skills for AI coding assistants, and an AdMob server for the Model Context Protocol, the open standard that lets AI agents call outside software.
Only one of the three is available today. The agent skills can be installed now, according to Google. Ask AdMob enters testing "over the next few months", and the MCP server "is in early testing and will be expanding to more developers early next year." Beyond those three, the post promises "a much broader and more advanced wave of AI tools for app developers" throughout 2027.
In Short
Google is adding AI helpers to AdMob, its app advertising business: a chat assistant inside the account that looks for setup mistakes and revenue gaps, ready-made instructions that coding agents can use to add ads to an app, and a connection that will let those agents change AdMob settings directly. If you make money from ads in a mobile app or game, these tools are aimed at the work of configuring ad networks, floor prices and blocking rules, which Google says pulls teams away from building their products. Only the coding instructions are usable today; the assistant starts testing in the coming months, and Google says every change it suggests will need a person's approval before it is applied.
Three tools, three timelines
Ben-Ayoun frames the release around a familiar complaint. "Building a successful mobile app means balancing a great user experience with ads monetization," the post opens. "But manually managing ad setups, fixing integration errors, and auditing brand safety pulls your team's focus away from building." The three products are pitched at different layers of that work: Ask AdMob at the account, the agent skills at the app's code, and the MCP server at the connection between the two.
The table below sets out what the post and Google's developer documentation say about each, as of today.
| Tool | What it is, according to Google | Status today | Next step stated by Google | Human approval |
|---|---|---|---|---|
| Ask AdMob | "a conversational agent built with Gemini" that "will live directly in your AdMob account" | Not yet in testing | Testing "over the next few months"; features "to take action on your behalf later next year" | "reviewing and approving every recommendation before it's applied" |
| AdMob agent skills | "pre-built, tested playbooks" for AI agents to implement coding tasks | Available; six skills listed in the Android documentation, last updated November 13, 2026 | Not stated | Not stated |
| AdMob MCP server | Connects "your developer environments directly with AdMob" | "in early testing" | "expanding to more developers early next year" | "review and approve the updates before you push them to production" |
| Further AI tools | "a much broader and more advanced wave of AI tools for app developers" | Not released | "Throughout 2027" | Not stated |
The post does not name markets, languages, account eligibility or pricing for any of the three.
Ask AdMob: an assistant inside the account
Ask AdMob is the piece aimed at the widest group of AdMob users, because it sits in the web interface rather than in a developer's toolchain. The post describes it this way: "Trained on AdMob monetization best practices, it can help fix issues, find revenue opportunities, and protect your brand safety like an AdMob product expert." Google gives three examples of what it will do.
Finding setup problems
The first is diagnostic. "The troubleshooting hub will help you spot setup anomalies and SDK integration issues," the post says. "Ask AdMob has visibility into how ads are loading in your app so it can highlight recommendations to resolve issues impacting your revenue." Google does not describe what data that visibility draws on, beyond ad loading in the app, or how far back it looks.
Not every loading problem starts with a publisher's configuration, however. In August, rewarded video ads failed to play in Android apps for eight days, from August 20 to August 28, 2026, in an incident Google logged at its lowest severity tier and whose final update said mitigation covered most users rather than all of them. The post does not say whether Ask AdMob will report platform-side incidents of that kind or only problems in the publisher's own setup.
Bidders, mediation groups and floor prices
The second example reaches into revenue. "Ask AdMob uses peer benchmarks to recommend high-value SDK bidders with predicted revenue uplifts to add to your setup and help optimize your mediation groups," according to the post. Google also describes a check on configurations that publishers enter by hand for outside networks: "For example, Ask AdMob will automatically check your third-party network configuration to catch costly typos and floor price discrepancies before they impact your yield."
That is the territory of the mediation platform, the software layer that decides which of several ad networks gets to fill each ad request in an app. AdMob runs its own demand through the same mediation it offers to publishers, and its auction combines real-time bidders with waterfall lines that publishers configure network by network, each with its own floor price. In July 2025, Google added InMobi, ironSource and Unity as AdMob bidding partners and introduced bidding eCPM floors at the mediation-group level, alongside mediation A/B tests that could return recommendations in as little as three days.
The post does not explain what "peer benchmarks" are, which apps count as peers, how predicted revenue uplifts are calculated, or whether Google's own AdMob Network demand is assessed against the same benchmarks as third-party bidders. Those details matter, because the assistant recommending bidders belongs to the company that also sells demand inside the same auction.
Brand safety rules in plain language
The third example concerns brand safety, the controls that decide which ads an app will show. "Instead of manually managing blocklists, you can configure custom brand safety rules using simple, natural-language prompts in your AdMob UI," the post says. It does not show an example prompt, list which existing controls the rules map to, or say how a rule written in plain language is translated into the category, advertiser and URL blocks AdMob already offers.
This is a shift in approach from what Google described for its web publishing products a year ago. In November 2025, Google Ad Manager introduced an AI brand safety system that learned from publishers' manual decisions in Ad Review Center and, at that stage, surfaced unwanted ads for review rather than blocking them automatically. The same announcement added an AI help chatbot to the Ad Manager, AdMob and AdSense help centers. Ask AdMob's version starts from the publisher's written instruction rather than from past review decisions.
Testing first, action later
Google is explicit that none of this is live. "We'll begin testing these capabilities over the next few months and continue evolving Ask AdMob with more advanced features to take action on your behalf later next year," according to the post. The sentence that follows sets the control model: "As always, you remain in control, reviewing and approving every recommendation before it's applied."
There is a tension in the wording. The same post says Ask AdMob "will automatically check" third-party network configurations, which suggests the checks run without being asked, while changes still wait for approval. The post does not say how a recommendation is presented, whether approvals can be delegated to other users on an account, or whether a record of approved changes is kept.
Agent skills: six modules for coding assistants
The second product moves the work out of the AdMob dashboard and into the code editor. "Previously, setting up ad placements meant clicking through web dashboards, copying and pasting ad unit IDs, and managing ad configuration files outside your codebase," the post says. "AdMob agent skills give your AI agent pre-built, tested playbooks to implement coding tasks like, migrating to the Google Mobile Ads Next-Gen SDK, validating your SDK implementation, and implementing new ad formats in your app."
The post links to Google's developer site for the details. The Android documentation page, titled "Use agent skills" and last updated on November 13, 2026, describes the skills as self-contained modules of knowledge, instructions and workflows for the Google Mobile Ads (GMA) Next-Gen SDK. It has tabs for Android, iOS and Unity, and names AI assistants that support skills, including Antigravity, Claude Code, Codex and Cursor. Six skills are listed.
| Skill name | Purpose, according to Google's documentation |
|---|---|
| google-mobile-ads-get-started | Adds the GMA Next-Gen SDK to an app for the first time, sets the application ID and initializes the SDK |
| google-mobile-ads-banner | Implements banner ads, including large anchored adaptive and inline adaptive banners |
| google-mobile-ads-interstitial | Implements full-screen interstitial ads |
| google-mobile-ads-rewarded | Implements rewarded ads and reward callbacks |
| google-mobile-ads-android-migrate-to-next-gen | Migrates an Android app from the legacy Google Mobile Ads SDK to GMA Next-Gen |
| google-mobile-ads-validate | Validates an integration, runs pre-launch audits and checks for common implementation errors |
Some of this predates today's post. Google's Ads Developer blog introduced agent skills for its advertising and measurement developer products on June 24, 2026, including skills for the Google Mobile Ads SDK. And when Google made the Next-Gen SDK its preferred Android SDK in July, PPC Land reported that the migration aids already included an agent skill named google-mobile-ads-android-migrate-to-next-gen. Today's post gathers those skills under the AdMob brand and places them next to two products that are still in testing. It also names them inconsistently: the summary at the top of the post refers to "AdMob agent tools", while the body says "agent skills".
The SDK deadline behind the migration skill
The migration skill points at a deadline that already applies to every Android app using AdMob's older library. Google's deprecation page for the legacy Android SDK, updated today, describes that SDK as being in maintenance mode and recommends moving to GMA Next-Gen. Its timetable is below.
| Legacy Google Mobile Ads SDK (Android) | Released | Deprecation | Sunset | Status |
|---|---|---|---|---|
| v25.x.x | February 17, 2026 | June 30, 2027 | June 30, 2028 | Supported |
| v24.x.x | February 24, 2025 | June 30, 2027 | June 30, 2028 | Supported |
| v23.x.x | March 7, 2024 | February 17, 2026 | June 30, 2027 | Deprecated |
| v22.x.x | March 29, 2023 | February 24, 2025 | June 30, 2026 | Sunset |
According to Google's documentation, traffic from a sunset version risks automatic no-fill because ad serving stops. The Next-Gen SDK has its own schedule: version 1.x.x was released on April 14, 2026, with deprecation planned for the first quarter of 2028 and sunset for the second quarter of 2029, while the beta line released on July 17, 2025 is due to be deprecated in the first quarter of 2027. Google says exact Next-Gen sunset dates will be announced on its developer blog.
Google has published AI help for the older library as well. A separate documentation page, last updated September 11, 2026 and marked beta, covers integrating the legacy SDK with AI tools in Android Studio's Gemini, and states that it is not for the Next-Gen SDK.
The MCP server: read, write and manage
The third product is the one with the widest reach into accounts. "While agent skills can help you implement tasks today, we're also working on an AdMob MCP server to connect your developer environments directly with AdMob," according to the post. "Soon your AI agent will be able to read account data, write new ad units, and manage mediation settings. All you have to do is review and approve the updates before you push them to production. This is in early testing and will be expanding to more developers early next year."
Read access to account data would be useful on its own. The ability to create ad units and change mediation settings goes further: those are the objects that decide which networks compete for an app's inventory and at what price. PPC Land found no developer documentation for the AdMob server, or for Ask AdMob, on Google's developer site on the day of the announcement.
Google's earlier MCP work for advertisers moved more slowly on write access. The company released an open-source MCP server for the Google Ads API in October 2025 as a read-only tool with two functions. Its first write tools arrived only with version 0.0.6 on November 2, 2026, covering assets and labels, while campaigns, budgets, bids and keywords remained out of reach. The AdMob server, as described today, is meant to write ad units and mediation settings from the outset, although Google has not said which mediation settings are included or whether floors, network order and bidder lists are all in scope.
How the tools work, according to Google
According to Google's post and the linked documentation, the three tools work as follows.
- Ask AdMob sits in the AdMob account interface. It reviews how ads load in the app, flags setup anomalies and SDK integration issues in a troubleshooting hub, and checks third-party network configurations for typos and floor price discrepancies.
- Ask AdMob compares the account with peer benchmarks and recommends SDK bidders, with a predicted revenue uplift for each, along with changes to mediation groups.
- Brand safety rules are written as natural-language prompts in the AdMob interface, in place of manually maintained blocklists.
- Each recommendation is reviewed and approved by the publisher before it is applied. Features that take action on the publisher's behalf are scheduled for later in 2027.
- Agent skills are installed into a supported AI coding assistant. The Android documentation gives the command npx skills add google/skills/skills/ads, and npx skills update --all to update them. The full list sits in the ads folder of Google's skills repository on GitHub.
- The coding assistant then uses the relevant skill to add the SDK, implement banner, interstitial or rewarded formats, migrate an Android app from the legacy SDK, or validate an integration before launch.
- The MCP server, once available to a developer, connects the AI agent to the AdMob account so it can read account data, create ad units and manage mediation settings. The developer reviews and approves those updates before pushing them to production.
A same-day reminder of who controls mediation
The announcement lands on a day when mediation access was already in the news. Earlier today, Božo Janković, head of ad monetization at GameBiz Consulting, wrote on LinkedIn that AppLovin had stopped allowing publishers to create new zones for its ad network outside its own MAX mediation, a change he dated to the past four weeks. Under that account, AdMob users can still reach AppLovin demand through bidding but cannot add new AppLovin lines to a mediation waterfall. PPC Land found no public statement from AppLovin about the change.
The two developments sit at different ends of the same problem. Ask AdMob is designed to tidy and tune the mediation setup a publisher already has. Whether a given network can be added to that setup at all is decided by the networks themselves, and no recommendation engine inside AdMob changes that.
The "Ask" family grows
Ask AdMob follows a naming pattern Google has used across its advertising products this year. At Google Marketing Live on May 20, 2026, the company introduced Ask Advisor, a single AI agent for Google Ads, Google Analytics, Google Marketing Platform and Merchant Center, in beta for English-language accounts. That followed the Ads Advisor and Analytics Advisor rollouts to English-language accounts announced in November 2025, and on the publisher side, Google said in September that its AI help feature had reached 100% of English AdSense Help Center traffic, with a warning that answers may vary in accuracy.
Among Google's publisher platforms, Ad Manager moved first: in June 2026, Google introduced Ask Ad Manager, an AI agent for Ad Manager publishers. Today's post brings AdMob into the same pattern, with the most cautious timetable of the group: testing in the coming months, and action on a publisher's behalf only later in 2027.
Why this matters for app publishers and marketers
For app developers who live on ad revenue, the work Google describes is real. Mediation setups can accumulate many network lines, each with its own ID, floor and placement settings, and an error in one of them can cost revenue until someone notices it. Tools that read the whole configuration and flag mismatches address a genuine source of loss, and the decision to require approval for every change limits the damage a wrong recommendation can do.
The harder question is one of position. Can advice on which bidders to add be neutral when it comes from a platform that also sells demand in the same auction? AdMob is both the mediation layer and a demand source inside it, so recommendations on bidders and floors come from a party with a stake in the outcome. The post offers no methodology for its benchmarks or uplift predictions, which leaves publishers without a way to check them against their own data before approving changes.
For advertisers buying app inventory, the brand safety change may matter more over time. If blocking rules move from lists maintained by hand to instructions written in plain language, the rules that decide which ads appear in which apps will depend on how Google's model interprets a sentence. The post does not show that translation, and until Ask AdMob is in testing there is no public way to see it.
What the announcement does not say
The post gives no launch markets, languages, eligibility criteria or fees, and no definition of the peer benchmarks or predicted uplifts behind the bidder recommendations. It does not describe how natural-language brand safety rules map to AdMob's existing blocking controls, which mediation settings the MCP server will be able to change, or what data Ask AdMob's view of ad loading draws on. PPC Land found no developer documentation for Ask AdMob or the MCP server on the day of the announcement.
Key facts
- Source: "New Google AdMob AI tools help app creators build, fix, and grow faster", Google Keyword blog, Publisher Connections section, tagged AdMob
- Author: Naomi Ben-Ayoun, General Manager, AdMob
- Published: November 16, 2026, 17:00 UTC (page metadata)
- Source URL: https://blog.google/products/publisher-connections/new-google-admob-tools/
- Products: Ask AdMob (conversational agent built with Gemini); AdMob agent skills; AdMob MCP server
- Ask AdMob timing: testing "over the next few months"; features to "take action on your behalf later next year" (2027)
- MCP server timing: "in early testing", expanding "to more developers early next year" (2027)
- Further tools: "Throughout 2027"
- Agent skills documentation: "Use agent skills" (Android), last updated November 13, 2026, https://developers.google.com/admob/android/next-gen/agent-skills; tabs for Android, iOS and Unity
- Skills listed: google-mobile-ads-get-started, google-mobile-ads-banner, google-mobile-ads-interstitial, google-mobile-ads-rewarded, google-mobile-ads-android-migrate-to-next-gen, google-mobile-ads-validate
- Install command (per documentation): npx skills add google/skills/skills/ads
- Supported assistants named: Antigravity, Claude Code, Codex, Cursor
- Legacy Android SDK: v24 and v25 deprecated June 30, 2027, sunset June 30, 2028; v23 sunset June 30, 2027
- GMA Next-Gen SDK v1.x.x: released April 14, 2026; deprecation Q1 2028; sunset Q2 2029
- Approval model: "reviewing and approving every recommendation before it's applied"
Timeline
- July 2025 - Google adds InMobi, ironSource and Unity as AdMob bidding partners and introduces bidding eCPM floors at the mediation-group level
- July 17, 2025 - Google releases the beta of the Google Mobile Ads Next-Gen SDK, according to its developer documentation
- October 7, 2025 - Google releases an open-source, read-only MCP server for the Google Ads API
- November 2025 - Google Ad Manager introduces an AI brand safety system that learns from Ad Review Center decisions, and an AI help chatbot for the Ad Manager, AdMob and AdSense help centers
- November 2025 - Google says Ads Advisor and Analytics Advisor will reach all English-language accounts
- February 17, 2026 - Legacy Android SDK v25 released; v23 deprecated
- April 14, 2026 - GMA Next-Gen SDK v1.x.x released, according to Google's documentation
- May 20, 2026 - Google introduces Ask Advisor at Google Marketing Live
- June 2026 - Google introduces Ask Ad Manager, an AI agent for Ad Manager publishers
- June 24, 2026 - Google's Ads Developer blog introduces agent skills for its advertising and measurement developer products
- July 2026 - Google makes the Next-Gen SDK its preferred Android SDK and sets a 2028 sunset for the legacy SDK
- August 20 to 28, 2026 - AdMob rewarded video fails to play in Android apps for eight days
- September 3, 2026 - Google says its AI help feature covers 100% of English AdSense Help Center traffic
- November 2, 2026 - Google Ads MCP server version 0.0.6 adds four write tools for assets and labels
- November 13, 2026 - Google updates the AdMob "Use agent skills" documentation, listing six skills
- November 16, 2026 - Božo Janković reports on LinkedIn that AppLovin no longer allows new zones for its network outside MAX mediation
- November 16, 2026 - Google announces Ask AdMob, AdMob agent skills and the AdMob MCP server
- Next few months - Ask AdMob testing begins, according to Google
- Q1 2027 - Next-Gen SDK beta line scheduled for deprecation
- Early 2027 - AdMob MCP server scheduled to expand to more developers
- June 30, 2027 - Legacy Android SDK v24 and v25 scheduled for deprecation; v23 scheduled for sunset
- Later in 2027 - Ask AdMob features that take action on a publisher's behalf, according to Google
- June 30, 2028 - Legacy Android SDK v24 and v25 scheduled for sunset
Related PPC Land coverage
- Google forces Android developers off legacy Mobile Ads SDK by 2028 - The July 2026 change that made the Next-Gen SDK Google's preferred Android library, with the deprecation and sunset dates for the older SDK.
- Google's new Android SDK promises to double your mobile ad speed - Earlier coverage of the Next-Gen SDK's beta and Google's performance claims for it.
- Google launches major AdMob mediation updates with new bidding partners - New AdMob bidders, mediation-group bidding floors and mediation A/B tests from July 2025.
- Google left AdMob rewarded video broken for eight days on Android - The August 2026 rewarded video incident and how Google reported it.
- Google Ad Manager introduces AI tools for publisher brand safety and live CTV monetization - Google's November 2025 publisher AI release, including AI brand safety in Ad Manager and an AI help chatbot for AdMob.
- Google releases open source MCP server for Ads API integration - The read-only Google Ads MCP server Google released in October 2025.
- Google Ads MCP server gains 4 write tools, still can't change budgets - How Google's Ads MCP server added its first write tools in November 2026, and what it still cannot change.
- Google's Ask Advisor unifies ads, analytics, and commerce in one AI agent - The single AI agent for Google's advertiser products introduced at Google Marketing Live 2026.
- Google launches Ads and Analytics Advisors for all English accounts - The November 2025 expansion of Google's in-product advisors for advertisers.
- Google puts AI in front of 100% of English AdSense help traffic - The AI help rollout for AdSense publishers and its accuracy disclaimer.
Summary
Who: Google's AdMob, in a post by Naomi Ben-Ayoun, General Manager of AdMob, aimed at mobile app and game developers who earn revenue from in-app ads, and at the advertisers whose ads run in those apps.
What: Three AI tools. Ask AdMob, a Gemini-built assistant inside the AdMob account, will flag setup and SDK problems, recommend SDK bidders using peer benchmarks, check third-party network settings for typos and floor price discrepancies, and turn natural-language prompts into brand safety rules. AdMob agent skills, six modules listed in Google's documentation, let AI coding assistants add, migrate and validate the Google Mobile Ads Next-Gen SDK. An AdMob MCP server will let AI agents read account data, create ad units and manage mediation settings.
When: Announced today, November 16, 2026. The agent skills are available now; Ask AdMob testing starts over the next few months, with features that act on a publisher's behalf later in 2027; the MCP server is in early testing and expands to more developers early in 2027.
Where: In the AdMob web interface for Ask AdMob, in AI coding assistants such as Antigravity, Claude Code, Codex and Cursor for the agent skills, and in developer environments connected to AdMob for the MCP server. No markets or languages were given.
Why: Google says manual ad setup, integration fixes and brand safety audits take app teams away from building their products. Every recommendation and update will need a person's approval before it takes effect, according to Google.
Discussion