Verified against ChatGPT · 2026-08-09
Build a paid-campaign calendar sequenced around real fatigue signals, not a fixed weekly slot
Schedules creative refreshes, budget shifts, and campaign launches around actual performance-decay signals for each channel, instead of a generic content calendar that assigns a new post or ad every Monday regardless of whether last week's creative is still working.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Build a paid-campaign calendar for the period below. Every scheduled action must be triggered by a stated performance or timing signal — not placed on a fixed cadence just because a calendar needs entries in every week. CAMPAIGNS RUNNING OR PLANNED Meta ads for the fall product line (ongoing), Google Search brand campaign (always-on), planned LinkedIn campaign for a new webinar series. CREATIVE FATIGUE HISTORY Meta creative historically shows CTR decline starting around day 10-12 of a given ad set; Google Search brand terms rarely fatigue since they're intent-driven. BUDGET REVIEW CADENCE Budget reviewed every other Friday with the finance lead. KEY BUSINESS DATES TO BUILD AROUND New product line ships Oct 1; no new campaign launches want to overlap with the Oct 1 week's operational load. For each campaign, schedule the creative refresh based on the fatigue pattern in creative_fatigue_history rather than an arbitrary fixed interval — if history shows this channel's creative typically fatigues (CTR decline of a certain magnitude) around a known point, schedule the refresh check just before that point, and say so explicitly rather than defaulting to a round-number cadence like "every 2 weeks" that isn't actually tied to this channel's real decay pattern. Do not schedule a budget review on the same day as a creative refresh unless there's a specific reason to bundle them — reviewing budget and refreshing creative are different decisions that get made worse when rushed together under one calendar slot. Build key_business_dates into the calendar as hard anchors the rest of the schedule must work around, not as an afterthought layered on top — if a launch or refresh would otherwise land in the same week as a key business date, move it, and say which way you moved it and why. If two campaigns would compete for the same audience's attention in the same week without a stated reason for that overlap, flag it explicitly rather than let a busy week for one audience pass silently. OUTPUT FORMAT A week-by-week calendar table: Week | Campaign | Action (launch / refresh check / budget review / pause) | Trigger reason for that timing. Below the table, list any key business date that forced a scheduling move, and any audience-overlap conflict you flagged between two campaigns.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
A calendar assembled by pattern-matching to "marketing calendar" templates in GPT-5.1's training data defaults to a fixed cadence — new post every Monday, refresh every two weeks — because that's the shape most calendar examples take online, and it has nothing to do with when this specific channel's creative actually stops working; a Meta ad set that fatigues at day 10 sitting untouched until a generic 2-week mark has already been bleeding efficiency for several days before the calendar even prompts a look. Requiring every scheduled action to cite the specific fatigue or timing signal that triggered it forces the model to actually use the creative_fatigue_history input rather than defaulting to round numbers, which is the entire value of giving it channel-specific decay data in the first place — a calendar that ignores that data isn't meaningfully different from one built with no input data at all. Separating budget review from creative refresh into distinct triggers matters because they're genuinely different decisions with different information needs — a budget reallocation call made in the same rushed slot as a creative swap tends to under-consider one or the other, and collapsing them onto the same day is a false efficiency that a naive calendar-generation pass won't flag on its own. Treating key business dates as hard anchors the schedule must move around, rather than optional context, addresses a common real failure where a campaign refresh lands during a week the team's attention is already consumed by an unrelated operational event like a product launch, and nobody actually executes the refresh on time because the calendar never accounted for competing bandwidth.
What you get back
Week of Sept 22: Meta fall product line — refresh check (trigger: approaching day-10 fatigue point based on history, want fresh creative in queue before CTR decline starts, not after). Week of Oct 1: no new campaign launches scheduled this week — moved the planned LinkedIn webinar campaign launch to Oct 8 to avoid competing with the Oct 1 product line ship date for internal attention. Flagged overlap: Meta fall campaign and the LinkedIn webinar campaign both target the same warm-audience segment in week of Oct 8 with no stated reason for the overlap — confirm this is intentional before both go live.
Verified against
ChatGPT GPT-5.1 · 2026-08-09
Changelog
- 2026-08-09 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
