domains / families / business / analyze-performance

analyze-performance

combined

Weekly performance read across every channel we run: what worked, why, and what to make next, judged on the business's real number (store revenue, qualified pipeline, retained users), not platform claims. Use when: write my Monday report; how are my ads doing — which ad won?; are my ads actually making money (Meta says 4x ROAS but revenue is flat); why did sales drop this week; did the test win; is my tracking working; monthly numbers for the replan; anything on fire today. Not for acting on the recommendations (pausing, scaling, launching) — use run-paid-campaigns; not for replanning the budget — use plan-campaign. Use when investigating slow activities, waiting, handoff duration, bottlenecks or cumulative activity workload.

When not to use

• Applying any change (pausing, scaling, budgets, negatives) — run-paid-campaigns.
• Making the next creative — make-static-ads, make-content. Video ads: the goose-video skill.
• The monthly replan itself — plan-campaign (fed by this playbook).
• Fixing the pages it checks — not covered yet; the check here is read-only.
• Brand-search volume, share of voice, citations — research-market ("What people are saying"), improve-search-visibility (carried in when they exist).
• Standing alerts and watchers — not covered yet; the exception-only pulse covers the gap.
• The deep email flow audit — email-lifecycle; the organic content mix — run-organic-social.

Skill page

Conflict

The two skills share the name 'analyze-performance' but describe completely different procedures. The Microsoft skill is a technical playbook for Power Platform process intelligence, using specific MCP tools (get_bottleneck_analysis_v2, get_attribute_statistics) to analyze activity duration, handoffs, and bottlenecks. The GooseWorks skill is a marketing playbook for weekly performance reporting across ad channels, focusing on revenue, ROAS, and creative testing. They do not overlap in steps, tools, or domain logic; they are distinct workflows that happen to share a generic name.