The common mistake: “Google is connected, so we are done.”
A Google identity may have access to many assets. One login can see a Google Ads manager account with many client accounts, several GA4 properties and one or more Merchant Center accounts. Authorization answers who may access Google; it does not automatically answer which asset belongs to this store.
A safer relationship model
├── Shopify Store A
│ ├── Merchant Center A
│ ├── Google Ads Client Account A
│ └── GA4 Property A
│
└── Shopify Store B
├── Merchant Center B
├── Google Ads Client Account B
└── GA4 Property B
The mapping should be stored as business configuration, not reconstructed by guessing on every request.
Manager accounts are not the same as the advertising account you operate
A Google Ads manager account can link and manage multiple Google Ads accounts. Google describes this as a hierarchy that can include individual accounts and other manager accounts. For store-level reporting or campaign actions, the system still needs to resolve the relevant client account inside that hierarchy.
Recommended mapping workflow
- Resolve the authenticated merchant and selected store.
- Load the merchant's authorized Google identity.
- Discover accessible Google Ads accounts, Merchant Center accounts and GA4 properties.
- Present or infer candidate assets using safe evidence such as known domains and existing configuration.
- Persist the confirmed Store → Asset relationships.
- Require every later read or write call to carry the store scope.
- Reject an action if the requested Google asset does not match the store's stored relationship.
Why this matters for AI agents
An AI model may correctly decide that a campaign budget should be reviewed but still cause a serious operating error if the tool executes against the wrong client account. Tool quality therefore depends on identity resolution and scope enforcement as much as on the model's recommendation.
What YEEDOOR uses this model for
YEEDOOR's merchant workspace treats store scope as context that follows reads, analysis and supported actions. The same pattern applies beyond Google: multiple Shopify stores, Amazon sellers, eBay sellers and other marketplace connections should not collapse into one global credential bucket.