---
name: cross-channel-performance-reporting
description: Pulls performance across every connected channel onto one measurement basis, explains what changed and why, and prepares a client-ready report that a named approver releases. Use when the user asks for a monthly report, a performance summary, a client update, or cross-channel numbers.
metadata:
  version: "1.1.1"
---

# cross-channel-performance-reporting

> **Client-neutral reusable package.** No client names, tenant or workspace identifiers, account or
> resource IDs, customer records, credentials, or internal paths. All examples are synthetic.

| | |
|---|---|
| Live catalog name | Cross-Channel Performance Reporting |
| Live category | Agency Operations |
| Catalog entry | 4 |
| Internal capability ID | `CAP-AO-01` |
| Provider | Multiple advertising and analytics providers |
| Availability | Candidate; validate in the active Workspace |
| Deliverable type | `client_ready_guided_skill` |
| Validation status | Candidate; local package validation only |
| Version | 1.1.0 |


## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant
bindings for the required inputs below; this public package supplies no client facts or authority.
Consume `ask-ollie-authority-core` for authority, `outloop-access-fallback` for recovery and
resource verification, `email-lifecycle-core` for recipients, approvals and stored-copy delivery
verification, and the bootstrapper Runtime Contract for ownership, scheduling and completion.
These owners govern execution; this Skill does not implement a competing runtime.

Select the relevant expertise below for the requested outcome. Runtime governs combining Skills,
partial use and completing missing steps with other authorized capabilities. This Skill's domain
scope does not limit the Operator's wider authorized task. Preserve domain safety restrictions.
Verify findings against source evidence and read back any resulting artifact or authorized change.

## Business outcome

The client gets one honest number per question instead of three conflicting platform numbers, and nothing reaches them unapproved.

## Operating modes

Read · Analyze · Draft · Send with approval

## Prerequisites — what must be true before this runs

- Workspace Context (contacts, email formatting, performance marketing)
- An approved grant per channel in scope
- A declared measurement basis

## Required inputs

| Input | Source |
|---|---|
| Connected channels in scope | Workspace configuration |
| Declared measurement basis and source of truth | Required — see the basis rule |
| Reporting period and comparison period | Configuration |
| Recipients, and whether each is internal or client-side | Workspace Context — contacts |
| Language and formatting rules | Workspace Context — email formatting |
| Named approver | Configuration |

## Establish the basis before reporting a number

Platform-reported conversions, analytics conversions and the client's own revenue system will not agree.
Pick the basis first, say which one it is in the report, and show the others as a reconciliation delta. Reporting
a blended number with no stated basis is the single most common way an agency report becomes indefensible.

## Say what got worse

A report that only contains good news trains the reader to distrust it. Name what declined, what it cost, and
what is being done. Include a positive section too — but not instead.

## Action classification

| Action class | This workflow |
|---|---|
| Read | Spend, delivery, conversion and revenue data per channel; analytics and CRM outcomes where connected |
| Analyze | Basis reconciliation, period-over-period change attribution, channel contribution, anomaly detection |
| Draft | A client-ready report in the configured language, with an internal annex explaining the reconciliation |
| Send with approval | Prepares a draft. The send is a separate, explicitly approved action |
| Destructive | None |

## Approval and delivery

The Operator applies Authority Core and the active Workspace approval policy to any requested
mutation. Email Lifecycle owns recipient classification, sending and stored-copy verification.
The action table defines this capability's domain scope; it grants no permission by itself.

## Expected output

A client-ready report, an internal reconciliation annex, and a prepared draft addressed to the resolved recipients — held until released.

## Synthetic placeholders used in this package

These are illustrative only. Real values come from the client's own workspace configuration and are
never written back into this package.

| Placeholder | Meaning |
|---|---|
| `CHANNEL_PLACEHOLDER` | Connected channel |
| `PERIOD_PLACEHOLDER` | Reporting period |
| `APPROVER_PLACEHOLDER` | Named approver |