{
  "@type": "help_guide",
  "id": "performance-engine",
  "title": "Performance Engine",
  "kind": "engine",
  "summary": "The Performance Engine is the Performance section of the workspace: every report channel the client has connected (website, organic search, AI visibility, Google, LinkedIn and Meta ads, organic social, local, content, reputation, pipeline) and attribution. It pulls the data every night, measures it against the client's goals, and writes the weekly analysis that the Monday post carries.",
  "aliases": [
    "performance engine",
    "reporting engine",
    "reports engine",
    "set up reporting",
    "set up the performance engine",
    "performance setup"
  ],
  "engine": "performance",
  "agents": [],
  "related": [
    {
      "id": "onboarding",
      "page": "https://nexus.effiqs.com/help/onboarding"
    },
    {
      "id": "aeo-seo-engine",
      "page": "https://nexus.effiqs.com/help/aeo-seo-engine"
    },
    {
      "id": "paid-ads-engine",
      "page": "https://nexus.effiqs.com/help/paid-ads-engine"
    }
  ],
  "reviewed": "2026-10-31",
  "sections": [
    {
      "heading": "What it does",
      "key": "what-it-does",
      "markdown": "The Performance Engine is the Performance section of the workspace: every report channel the client has connected (website, organic search, AI visibility, Google, LinkedIn and Meta ads, organic social, local, content, reputation, pipeline) and attribution. It pulls the data every night, measures it against the client's goals, and writes the weekly analysis that the Monday post carries.\n\nIts optional modules each have their own guide: Search & AI visibility, Paid ads, Attribution, Reputation and the Pipeline report."
    },
    {
      "heading": "Set it up",
      "key": "set-it-up",
      "markdown": "**\"Show the performance engine setup.\"** shows what's done for the client and the next step. The same checklist is on Roadmap › Onboarding in the app.\n\n1. **At least one report source connected** — Connect Google (GA4 + Search Console), an ad account, Meta, Google Business Profile or HubSpot: each one adds its channel to the report.\n2. **Google Analytics 4** _(optional)_ — Same Google grant as Search Console; give the GA4 property id if it isn't detected.\n3. **Google Search Console** _(optional)_ — Grant access (or add the Google account your Nexus team gave you to the property). One grant covers GA4 too.\n4. **Goals the work is measured against** — Set at least one target (leads, pipeline, organic sessions…) with its period, so reports show pacing and actions get a priority.\n5. **Key pages and the form event** _(optional)_ — Name the pages that matter and the GA4 event the contact form sends, so the Website tab shows their sessions and conversion rate.\n6. **Report baseline** _(optional)_ — A fixed 'before' date (usually the start of the engagement) the report can compare with.\n7. **Client Slack channel** _(optional)_ — Pin the client's Slack channel: the Monday insights and alerts post there.\n8. **Weekly report digest** _(optional)_ — Turn on the weekly digest (Mondays) and, optionally, the monthly summary, in the client's channel or by email.\n9. **Report data syncing** _(optional)_ — Every connected source's nightly pull is current (a weekly source gets a week more). A failing one quotes its error.\n10. **Connections working** _(optional)_ — Every connection the client's agents use answered on its last check. A failing one says why; reconnect it with the connect tool it names.\n\n- ✋ Connecting Google, an ad account, Meta, Google Business Profile or HubSpot needs someone with access on the client's side. Each one adds its channel to the report.\n- ✋ Goals come from the client: **\"Set Acme's goal to 120 leads a month.\"** Without one, the report can't show pacing and action items can't be ranked by what the client is measured on.\n- Key pages and the form event make the Website tab useful: **\"Set Acme's key pages to /pricing, /demo and /contact.\"**"
    },
    {
      "heading": "Keep it running",
      "key": "keep-it-running",
      "markdown": "The keep-running steps check that what's set up still works: every source's nightly sync succeeded in the last three days, and every connection answered on its last check. A failing one shows the error as the source reported it. **\"Refresh the report data for Acme.\"** runs the sync again after a fix."
    },
    {
      "heading": "Prompts",
      "key": "prompts",
      "markdown": "- \"Show the performance engine setup.\"\n- \"Set Acme's goal to 120 leads a month.\"\n- \"Set Acme's key pages to /pricing, /demo and /contact.\"\n- \"Refresh the report data for Acme.\""
    }
  ],
  "prompts": [
    {
      "text": "Show the performance engine setup.",
      "tool": "read_engine_setup"
    },
    {
      "text": "Set Acme's goal to 120 leads a month.",
      "tool": "set_client_goal"
    },
    {
      "text": "Set Acme's key pages to /pricing, /demo and /contact.",
      "tool": "set_report_tracking"
    },
    {
      "text": "Refresh the report data for Acme.",
      "tool": "refresh_report_data"
    }
  ],
  "page": "https://nexus.effiqs.com/help/performance-engine",
  "markdown": "https://nexus.effiqs.com/help/performance-engine.md"
}