MERCHANT OPERATING PROBLEM

Multi-store Google Asset Mapping Conflict

A company operates multiple stores but the wrong Google Ads, Merchant Center, GA4 or Search Console asset is associated with a store, causing mixed data or unsafe actions.

google_ads · gmc · ga4 · gsc · shopifyai_google_managerCAPABILITY WORKFLOW · NO STANDALONE APP
PROBLEM MAP

From operating symptom to executable capability

This mapping is the public knowledge layer behind YEEDOOR's app and agent architecture.

ProblemMulti-store Google Asset Mapping Conflict
AppNo standalone app published
CAPABILITY WORKFLOW · NO STANDALONE APP
Capabilitygoogle_ads.assets.discover · gmc.accounts.discover · ga4.assets.discover · gsc.assets.discover

What this looks like

  • Two stores appear under one company, but reporting or actions are being taken against the wrong Google Ads/GMC/GA4/GSC asset.
  • An agency or manager account sees many child assets and a merchant cannot tell which one belongs to which store.
  • Data from different storefronts is mixed, making store-level diagnosis or write actions unsafe.

What to inspect

  • The merchant store identity and canonical domain before inspecting Google assets.
  • Discovered Google Ads customers, Merchant Center accounts, GA4 properties and Search Console properties.
  • Existing store-to-asset bindings and whether they are explicit, inferred or still unresolved.

Operating response

  1. Treat store scope as a first-class object rather than assuming one company has one Google asset set.
  2. Discover assets under the authorized Google identity and map candidates to the correct store.
  3. Require explicit confirmation where multiple plausible assets exist before any write-capable workflow.
  4. Persist the binding so subsequent reads, diagnostics and actions remain store-scoped.
YEEDOOR coverage today: YEEDOOR has implemented asset discovery foundations across Google Ads, GMC, GA4 and GSC and uses store scope as a product-level concept. The mapping workflow is part of the Google operating architecture, not a separately published paid app today.