Custom branding no longer working after switching to grouped connections

Embedded Wallets (Web3Auth)
2

Hi Diego — thanks for the clear report. I’m sorry you’re seeing this after the migration; I’ll help get it escalated. I pulled the key details you gave and added what we still need to investigate further.

Summary of what you reported

  • SDK: MetaMask Embedded Wallets (Web3Auth)
  • Platform / environments: Web — staging and production (both affected)
  • Recent change: Upgraded to Growth plan and migrated users to a grouped Google / Email auth connector
  • Symptoms: Custom branding (logo) no longer appears in emails — shows Web3Auth logo instead. Default language set to Spanish but emails/UI show Portuguese translations.
  • Attempts to contact support: Reached out twice via dashboard, no response yet

Missing / unclear items we’ll need to escalate
(please only share what you’re comfortable with; these help the support team reproduce and fix the issue)

  • SDK version number (from package.json / package-lock / yarn.lock) — important to know which Web3Auth / Embedded SDK you’re running
  • The clientId / projectId you’re using for staging and prod (or confirm whether the same clientId is used across both)
  • Initialization snippet for the Embedded Wallet / Web3Auth (the code where you construct Web3Auth / EmbeddedWallet and pass UI/branding or locale options)
  • Whether you’re using custom email templates in Web3Auth (or relying on default templates)
  • Screenshot of the email you received showing the Web3Auth logo (helps confirm which template/logo is being used)
  • Screenshot of your branding settings in the Web3Auth / MetaMask portal (so the team can confirm the assets and which project they belong to)
  • Any support ticket ID(s) you created from the dashboard (so we can correlate prior outreach)
  • Browser console logs / network logs from a session where the wrong language/logo appears (if possible)

Quick checks you can try right now

  • Confirm the clientId/project you configured in your app is the same project in the portal where you uploaded the custom branding (migration could have created a new project)
  • Confirm branding assets are uploaded to the correct project/environment in the portal
  • Clear app/browser cache or open an incognito window to rule out cached assets/templates
  • Confirm you’re explicitly passing the locale (language) param in your Web3Auth / Embedded init (ensure it’s set to ‘es’ / ‘es-ES’ as appropriate, and not ‘pt’)
  • Verify whether grouped-connector creation changed the project linkage (grouping can sometimes create or reference different connections)

Helpful docs

Next steps from my side

  • If you can paste the SDK version + the init snippet + one screenshot of the email and one screenshot of the portal branding, I’ll escalate this to the support team immediately and include these details so they can investigate the branding/template mapping and locale behavior.

Thanks again for flagging this, Diego — once you share the items above I’ll make sure the team gets all details and follows up. If you already have a dashboard support ticket ID, drop it here and I’ll reference it.

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. MetaMask Developer Office Hours