AdMob custom events now expose their own class name
Update diagnostic matching rules before assuming a changed adapter label means a changed ad source.
A changed diagnostic label can look like a changed business entity when a reporting pipeline relies on exact strings. AdMob’s custom-event class-name change is a specific reason to inspect those mappings during an SDK upgrade.
Follow the label downstream
Ask whether adapter identity is used only for debugging or is also copied into internal reports, incident routing or QA assertions. Our recommendation is to capture a response from a known custom event and compare the value with the mapping expected by each consumer.
Do not merge newly named rows into an “unknown network” bucket without checking their origin. Equally, do not assume that two different custom event classes represent two independent commercial sources. The class is a technical identity; its business meaning comes from the integration configuration.
Preserve continuity without hiding the change
A useful migration table keeps the previous value, the new value, the associated integration and the date the new build shipped. This lets a reviewer distinguish a naming discontinuity from a delivery change. Keep raw source values available so that the mapping can be audited later.
No account data was inspected for this record. The documented change gives a narrow test case: request an ad through the intended custom event, inspect its response information and verify the downstream classification. Performance conclusions should wait until identity and measurement continuity are established.
The governing record is Android release notes — 25.5.0 custom events. This article checks the provider documentation; it does not inspect a studio account or certify a shipped build.
Inspect the evidence
Download the applicability and deadline record. The extraction separates documented facts from our analysis and unknowns.
| Field | Evidence or limit |
|---|---|
| Provider | |
| Effective or release date | 2026-09-17 |
| Applies to | Mediation with custom event ad sources on Android SDK 25.5.0 |
| Documented change | ResponseInfo.getAdapterClassName returns the custom event class name instead of the generic CustomEventAdapter name in this release. |
| Suggested owner | Ad diagnostics and data engineering |
| Next verification | Review string-based adapter mappings and preserve a before/after example. |
Further reading in the existing archive: Reading an MMP dashboard without fooling yourself; Attribution is an allocation rule, not a truth. These links provide background; this check does not independently verify their full contents.
