AdMob API (mediationReport.generate) returning manager account app data instead of MCM child publisher data

7 views
Skip to first unread message

Jay Cho

unread,
Mar 17, 2026, 10:48:46 PM (4 days ago) Mar 17
to AdMob API Developer Forum

Hello,


We are currently using the AdMob API to collect mediation report data, and we are experiencing an issue when querying data from MCM (Multiple Customer Management) child publisher accounts.


Environment

  • API: AdMob API v1

  • Method: accounts.mediationReport.generate

  • Authentication: OAuth2

Structure: Manager account with MCM child publishers


Issue Description


When requesting mediation reports using the child publisher account ID (pub-xxxxxxxx), the API does not return the mediation data of the child publisher.


Instead, the response contains data from apps connected to the manager account.


In other words:

  • The API request is made with a child publisher account ID

  • But the returned report contains apps belonging to the manager account


This behavior started recently and was not happening previously.

Dimensions 
DATE
AD_UNIT
MEDIATION_GROUP

Expected Behavior


When querying with a child publisher account ID, the API should return mediation report data for the child publisher’s apps.


Actual Behavior


The API returns mediation data for apps belonging to the manager account instead of the child publisher account.


Additional Notes

  • OAuth authentication is working correctly.

  • API calls are successful (no error response).

  • The returned data appears valid but corresponds to the wrong account.

  • The issue occurs only for MCM child accounts.


Question


Is there any known issue or recent change related to:

  • AdMob API and MCM accounts

  • mediationReport behavior for child publishers


Any guidance would be appreciated.


Thank you.

AdMob API Developer Forum

unread,
Mar 17, 2026, 10:54:22 PM (4 days ago) Mar 17
to AdMob API Developer Forum
Hello,

Thanks for reaching out.

Can you please check again now and confirm if the issue still persists?
Most probably, we had a auth related change that only impacted MCM use case. The issue should be resolved by now.

Thanks,
Reply all
Reply to author
Forward
0 new messages