YEEDOOR PROBLEM LIBRARY

Start with the merchant problem, not the software category.

Each problem below is mapped to an operating role, a solution context, an app or app lifecycle state, and real capability references. The library is intentionally small: YEEDOOR publishes problems when there is enough operating evidence to explain them usefully.

11 initial operating problemsRole → Solution → App → CapabilityNo keyword doorway pages
CURRENT LIBRARY

Problems connected to the current product roadmap

Live coverage and in-development coverage are labeled separately so the knowledge layer does not overstate product availability.

CAPABILITY WORKFLOW · NO STANDALONE APP

Performance Max Underperformance

A Performance Max campaign spends without producing the expected ecommerce return, while feed quality, conversion measurement and campaign signals make the root cause difficult to isolate.

Operating role: ai_ads_manager · ai_google_manager · ai_feed_manager
Mapped app: No standalone app published
Platforms: google_ads · gmc · ga4 · shopify

Understand the problem →
KNOWLEDGE GRAPH

Why the mapping matters

A merchant usually starts with a symptom, not an app name. YEEDOOR connects the symptom to who should own it, what solution pattern applies, which app packages the workflow, and which underlying provider capabilities are actually available.

Problem → AI operating role → solution context → app → provider capability → merchant-approved action → verification