Read mature paid campaign results for the weekly campaign workflow. Compare spend and outcomes with allowable costs, account for attribution windows and data coverage, and produce an evidence table and ad scorecard to inform later decisions. This is a step within a larger playbook.
Step of the run-paid-campaigns playbook: reads each platform's last mature results window against the allowable cost, as evidence for the week's moves. Run run-paid-campaigns instead; not for direct use.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Load: ../run-paid-campaigns/references/reading-results.md.
Inputs: the volume regime; meta_read view: performance (a 14-day and a 3-day window, ranked by spend) for Goose ads, when Meta is chosen and GooseWorks is connected (local mode: the connector's date-range reads, ../run-paid-campaigns/references/local-mode.md); the marketer's exports for non-Goose Meta and other platforms; analyze-performance's weekly read (blended MER, new-customer CAC, store-joined CPA per angle, its kill/scale/hold calls); decisions.md (edits inside the window); the brief's test plan and targets.
Do:
Set the window for the regime (high-volume: 14-day minus the immature last 3 days; low-volume: 14–28 days matured past the qualified lag; app: 7–14 days past postback delay); same attribution setting as last week. Trends from trailing totals are approximate — say so.
State coverage: share of spend visible per platform; what is not visible (frequency, learning status, CPM unless exported).
Per ad set / ad, sorted by spend: spend, results, cost per result vs allowable, CTR trend over 3 weeks, conversions (n) and its noise band (±1/√n), learning (events/week vs ~50), and any edit inside the window. Traffic tests: CTR, cost per LPV, UTM store CVR.
Join to the blended read: does store-joined data agree with the platform? If not, the store-joined number decides and the disagreement is stated.
Mark each object: readable winner · readable loser · near-threshold · too early · broken.
Build the per-ad scorecard (../run-paid-campaigns/references/run-memory.md § End): top 10 by spend plus all others, each row against its row in the last run record.
Output: the evidence table the moves are drafted from, with confidence per row, and the scorecard. No moves yet.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
The supplied material contains only placeholder text for the skill’s purpose, inputs, steps, and completion criteria. It does not provide enough information to describe a task or result reliably.
Research supported advertising angles using buyer context, current product facts, customer language, and observed ads. Turn the evidence into static ad, video, or copy ideas, matching video concepts to available recipes. Scores rank ideas for testing; they do not predict results.
Analyze campaign data from Google, Meta, and LinkedIn to find strong and wasteful spend. The skill checks funnel performance and test results, then recommends which campaigns to pause, scale, or test and how to shift budget across channels.
Compare ad spend and signups with downstream outcomes to calculate the cost of each qualified lead. The skill checks tracking coverage, accounts for how long leads need to mature, and groups creatives into actionable categories with confidence notes.
Prepare the intake for a Meta ad campaign by reviewing available brand information first, stating reasonable assumptions, and asking only questions whose answers could affect budget, claims, or legal exposure. It records stable brand facts, a campaign brief, and what was asked versus assumed.
Review ad copy, image text, visuals, and people against platform and brand category rules. It suggests honest fixes and needed disclosures, then flags issues requiring human or legal review, with a separate result for each ad and platform.