Google ads presentation

Google Ads Presentation

Turn an engagement or a quarter's results into a structured, client-ready deck outline that a slide generator can render. This skill does not draw slides; it produces the ordered argument - each slide with a title, a slide-type, the key data points, a one-line narrative, and the ask - so the story is right before a single pixel is rendered. It covers two modes: a proposal that sells an engagement, and a QBR that accounts for a period.

When to use

Reach for this skill when someone needs a Google Ads proposal or pitch deck, a client-ready slide outline, or a QBR/quarterly-review deck, or wants results and a plan turned into slides. If the request is to compute the numbers first (metrics, winners/losers, recommendations), run google-ads-reporting and feed its output here. This skill is the deliverable layer that sits on top of the report.

Workflow

1. Gather engagement inputs. Collect client, objective, budget, current results (spend, conversions, ROAS, CPA, period), targets, the proposed plan, and the ask. If a google-ads-reporting JSON exists, lift the totals, winners, losers, and recommendations from it directly.

2. Pick the mode. Use "proposal" to pitch a new or expanded engagement (objective -> baseline -> gaps -> plan -> impact -> ask). Use "qbr" to review a period with the 4-act arc (where we said we'd be -> where we are -> why the gap -> what next). See references/deck-structure.md for both slide orders.

3. Build the outline. Run python3 scripts/deck_outline_builder.py --demo to see the structure, then --data engagement.json --mode {proposal|qbr}. It emits structured JSON (consumable by a PptxGenJS renderer) by default, and a readable Markdown outline with --markdown. Each slide carries title, slide_type, data_points, narrative, and ask.

4. Tighten the narrative. Make every slide title a takeaway, not a topic, so each follows Headline -> Data -> Narrative -> Ask. Lead with the headline or objective; never bury a miss; make the ask specific and assign an owner. See references/narrative-frameworks.md.

5. Hand off to rendering. The outline JSON maps cleanly to slides: KPI dashboards become tables, projected impact and trends become charts, plans and gaps become numbered or two-column lists. references/pptxgenjs-recipes.md gives the PptxGenJS recipes, chart-styling notes, palette/typography guidance, the corruption pitfalls to avoid, and the required visual-QA loop. Build the renderer separately; this skill stops at the outline.

Inputs and data sources

The skill runs standalone on a hand-written engagement JSON or pasted numbers. No live connection is required.

Optional sources that enrich the deck:

• google-ads-reporting output (JSON) for the KPI dashboard, winners/losers, and recommendations - the most natural upstream.
• Google Ads API / UI for the raw current-period results and targets.
• Google Sheets as the place a client keeps targets and budget.

Outputs

• A structured deck outline in JSON: an ordered list of slides, each with title, slide_type, data_points, a narrative line, and the ask, plus design notes.
• The same outline as a readable Markdown document for quick review or sign-off.
• A clean handoff contract for a PptxGenJS (or any) slide renderer.

References

• references/deck-structure.md - the proposal vs QBR slide orders, the general rules, and how each slide type maps to a layout.
• references/narrative-frameworks.md - the Headline-Data-Narrative-Ask per-slide formula, the 4-act QBR arc, how to deliver bad news, and the specific-ask rule.
• references/pptxgenjs-recipes.md - a distilled how-to for rendering the outline to .pptx with PptxGenJS, including table/chart recipes, chart styling, palette and typography notes, corruption pitfalls, and the visual-QA loop (reference only; do not build the renderer here).