paid-performance-report

$npx mdskill add Significant-Gravitas/skills-catalog/paid-performance-report

Use this for a weekly, monthly, or quarterly look at paid results.

SKILL.md

.github/skills/paid-performance-reportView on GitHub ↗
---
name: "paid-performance-report"
description: "Report paid results for a period with sources, changes, causes, and open questions."
triggers: ["ads report", "PPC report", "paid performance", "monthly ads summary", "ROAS report"]
version: "1"
---

# Paid performance report

Use this for a weekly, monthly, or quarterly look at paid results.

## Headline numbers

State the period, accounts, currency, attribution setting, and the source of
each figure. Give spend, conversions, cost per conversion, and revenue or
return where tracked, against the prior period and the target. Keep
platform-reported results apart from what the analytics tool or CRM shows,
and give the gap.

## What changed and why

For each large change, show the campaigns, terms, or audiences behind it.
List possible causes with the evidence for each: budget changes, new ads,
tracking breaks, seasonality, competitor activity, or page changes. Say
plainly when the cause is unknown. Note any days with broken or partial
tracking.

## Next actions

Close with:

- the two or three changes worth making, each with its owner;
- tests running and when each can be read;
- open questions for the business, such as lead quality or sales outcome;
- data the next report needs.

Do not share the report outside the team or change campaigns yourself. Never
invent results or benchmarks, fill tracking gaps with estimates, or promise a
return.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.