Multi-channel

Aggregate Performance Reporting

Composes SEO, GA4, Google Ads, and Meta Ads reporting drafts into one internal aggregate performance report when a task asks for a combined channel view.

All Skills Architecture Map

Status

Live dev deployed

Current hosted implementation state.

Trigger Surface

Asana task

Created or updated in Jessie Intake and assigned to Jessie.

Delivery

HTML artifact

Attached to the source task or linked as a stable artifact.

Approval

Review required

No client-facing or external-system action without human approval.

Consultant Prompt

Live dev deployed

Example Asana request

Jessie, create an aggregated April report for Plunkett including SEO, Google Ads and Meta.

Routes before single-channel skills when the request contains aggregate/combined report wording and at least two reporting channels.

Default Inference

Named month shorthand such as "April report" resolves to that month in the current year when it has already passed.
Infers prior month as the comparison period.
Infers Plunkett Homes and consultant/internal audience when unambiguous.
Requests clarification instead of selecting a single channel when the requested channel set is ambiguous.

Data Sources

SEO reporting draft and supporting evidence.
GA4 reporting draft and supporting evidence.
Google Ads reporting draft and supporting evidence.
Meta Ads reporting draft and supporting evidence.
Shared Asana task context and consultant follow-up comments.

Output Contract

One internal aggregate performance HTML report attached to the source Asana task.
Channel sections for SEO, Google Ads, and Meta Ads when requested and available.
Cross-channel caveats and review-required action list.

Guardrails

No channel-specific work is invented when a provider fails; the report carries a data-quality note.
No client-facing rollup publishing until a later approved rollup workflow exists.
No account, website, tracking, or external-system changes.

Current System Context

Recent changes

Added after an aggregate April Plunkett request initially routed to SEO only.
Domain parser test covers the exact aggregate wording.
Workflow execution test covers an aggregate artifact containing SEO, Google Ads, and Meta.
Dev Worker deployed as 8337026c-7e16-446d-a54b-db5eededd97c with the clarification loop guard.

Prompt Source

Hosted runner prompt contract

---
name: aggregate-performance-reporting
description: Use when a Jessie-assigned Asana task asks for an aggregate, combined, or rollup marketing performance report across at least two supported reporting channels.
---

# Aggregate Performance Reporting

Route aggregate wording before single-channel skill matching. Require at least two reporting channels such as SEO, Google Ads, and Meta Ads. Infer safe Plunkett defaults only when brand, channel set, audience, period, and approval gates are clear.

Compose existing channel report drafts into one deterministic internal HTML artifact. Do not claim hard attribution across channels. Preserve each channel's source caveats and approval gates. If any channel fails or is unavailable, keep the aggregate report review-required and state the missing evidence plainly.

Do not publish a client-facing rollup, change ad accounts, change websites, change tracking, create tasks, or create credentials without explicit approval.

Related Docs

2 references

Aggregate Performance Reporting And Clarification Loop Guard decisions/aggregate-performance-reporting-and-clarification-loop-guard.md
Team Agent Work Intake docs/runbooks/team-agent-work-intake.md