The worksheet turns the guide into an operating record. For each row, name the decision owner, evidence to inspect, acceptance rule, known limitation and failure response. Save it with the campaign record so another operator can understand the test without reconstructing it.
Outcome and acceptance rule
Define the business event before choosing dashboard metrics. Name the event, eligible population, exclusions, denominator, data source, time zone, currency, attribution scope and owner. Use “accepted lead” or “completed order” only when the business applies a consistent rule and can trace each record to the campaign.
Keep evidence exportable and readable by someone who did not configure the campaign. A short change log, versioned brief, source identifiers and reconciled outcomes often explain performance better than a screenshot. Mark unavailable dimensions so the report does not imply unsupported precision.
Audience and eligibility
For each audience signal, record why it relates to the offer, where data comes from, how long it remains valid and which exclusions apply. Separate prospecting, customers, retargeting and suppression groups where lawful and supported. Document overlap before comparing the groups.
Creative and landing-page continuity
List every approved claim, proof source, creative version, call to action and landing destination. Include material conditions and a person who can withdraw an outdated message. Match creative to placement while keeping the promise recognizable after the click.
Budget and failure case
Model conservative, expected and upside cases with explicit assumptions for eligible audience, media cost, response, acceptance, conversion delay and contribution. Add a failure case with maximum learning loss and a pause signal. These are planning scenarios, not FroggyAds forecasts or performance promises.
Source and cohort evidence
Preserve campaign, audience, source or placement, device, geography, creative and time identifiers when your reporting provides them. If a field is unavailable, mark the gap. Do not credit a publisher or format with an outcome unless the evidence supports that comparison.
Reconciliation across systems
Reconcile platform delivery, analytics events and business outcomes using a common time zone, currency and maturity window. Record counts, variance, known causes, unresolved amount and owner. Resolve discrepancies that could change the decision before using the totals to justify a larger budget.
Change log and experiment record
For every material edit, log the observed issue, hypothesis, exact change, start time, expected signal, minimum evidence, result and rollback decision. This preserves learning across agencies and internal handoffs and helps distinguish campaign changes from seasonal or operational shifts.
Scale and rollback conditions
Before expanding, confirm marginal economics, acceptable source or audience quality, understood frequency, sufficient creative coverage, operational capacity and a recoverable prior setup. If a condition is unknown, make that uncertainty explicit and keep the next step inside the approved test boundary.