Google Ad Manager onboarding blocked by duplicate publisher account, but old account returns Error 500
Hi everyone,
We are running into a Google Ad Manager / publisher account issue and I’m trying to figure out the correct official Google support path.
We are onboarding a new Google Ad Manager child account under an MCM / parent publisher setup. During onboarding, Google says the account is not approved because we already have an existing Google publisher account.
The problem is that we cannot access the existing publisher / Ad Manager account. When we try to log in to Google Ad Manager, it returns Error 500, so we cannot close the old account or remove the duplicate account from the UI.
We also tried closing the related Google Payments profile, but Payments Center says there is still an active subscribed product/service listed as “AdSense”, so the payments profile cannot be closed either. It looks like the old publisher / AdSense payment service is still attached to the payments profile, but we cannot access the publisher account to unlink or close it.
My questions are:
Is there any official Google email address or support channel for Google Ad Manager / Publisher Support?
If there is no direct email, what is the correct official way to open a support case for this kind of issue?
Should this be handled by Google Ad Manager support, AdSense support, Google Payments support, or the MCM parent publisher?
Can Google support identify the linked Publisher ID / publisher account from a payments profile ID if we cannot access Ad Manager or AdSense?
Has anyone dealt with a duplicate publisher account block where the old Ad Manager account returns Error 500?
We do not want to post any sensitive details publicly, but we can provide Google support with the payment profile ID, login emails, company name, screenshots of the Error 500 page, the duplicate publisher account message, and the Payments Center message showing the active “AdSense” service.
Any advice on the correct official support route would be appreciated. We are mainly trying to find the right Google team or official contact method to resolve this.