A weekly operating system for protecting a live test, controlling changes, pacing spend, and turning sales feedback into better campaign decisions.
What this page covers
Validate the complete lead path on launch day
Protect the first 14 days from reactive editing
Change one decision category at a time
Optimize for qualified business outcomes, not raw volume
Launch day: prove the system works
Before interpreting performance, verify that a real homeowner can travel from ad click to a correctly handled inquiry.
1
Inspect live delivery
Confirm the approved offer, service, destination URL, territory, schedule, budget limits, and available platform settings match the launch sheet.
2
Test every conversion path
Submit forms on mobile and desktop, tap phone links, place a test call, inspect confirmation states, and verify required consent and privacy language.
3
Follow the data
Confirm each test event appears in analytics and platform reporting where supported, carries the correct source, and creates or updates the expected CRM record.
4
Follow the lead
Make sure forms reach the assigned people, calls ring the intended queue, notifications arrive, and after-hours routing behaves as documented.
5
Confirm human coverage
Tell intake and sales the offer is live, provide qualification rules, identify the escalation owner, and verify phones are staffed for the advertised schedule.
Tracking is not complete until routing is complete
A platform event can fire perfectly while the customer’s email disappears into an unmonitored inbox. QA the business handoff, not just the tag.
The first 14 days: observe without freezing
Early data deserves attention, but a handful of events rarely supports sweeping conclusions.
Fourteen days is an operating window, not a universal statistical rule. A material tracking fault should be fixed immediately; a compliance concern should be paused immediately. Conversely, low activity alone may reflect limited inventory, account constraints, narrow eligibility, or normal variation. Document what is known and what remains uncertain before acting.
Use the period to establish a clean baseline. Annotate outages, holidays, storms, capacity changes, and offer interruptions. Without that context, the team may later credit or blame campaign edits for changes caused by the business itself.
Do
Protect customers, spend, and data integrity.
Check delivery, spend, links, events, phone routing, and form delivery every business day.
Read each available lead record and ask sales for a factual disposition.
Log every intervention with time, reason, old state, and new state.
Watch for repeated mismatch patterns without declaring a trend from one case.
Deliberately do not
Avoid edits driven by discomfort rather than evidence.
Rewrite the offer after one weak inquiry.
Expand geography simply because early spend is slow.
Cut the budget repeatedly throughout the day.
Change creative, destination, targeting inputs, and qualification rules together.
Call the campaign a winner from lead count before quality is known.
Run one disciplined weekly cycle
A regular review prevents both neglect and constant tinkering.
1
Reconcile delivery
Compare actual spend with the weekly plan, confirm campaign status and eligibility, and flag material under- or over-delivery.
2
Audit the funnel
Reconcile reported conversions with call records, form receipts, CRM entries, duplicates, spam, and missing source data.
3
Review lead quality
Group inquiries by qualification and loss reason, then inspect the underlying conversations rather than relying only on totals.
4
Check operations
Review answer rate, speed to first attempt, follow-up completion, appointment handling, territory declines, and current crew capacity.
5
Choose one change category
Select creative, context and eligibility inputs, geography, landing page, routing, or budget. Avoid changing several categories unless correcting an urgent fault.
6
Record the decision
Document the evidence, hypothesis, exact change, start date, expected signal, review date, and person responsible.
Know what you are allowed to change
The weekly rule is not “one tiny edit.” It is one coherent hypothesis. If repeated inquiries are outside the service area, a geography correction and matching copy clarification belong together. If qualified visitors abandon a long form, a landing-page test may include field reduction and revised supporting text. The change should answer one operational question.
Do not combine a new offer, larger territory, higher budget, different page, and revised intake script, then attribute the outcome to creative. That creates a new campaign with no useful comparison. Exceptions are failures that harm customers or violate approved limits: broken pages, incorrect claims, misrouting, policy issues, and uncontrolled spend should be addressed at once.
Keep a change log accessible to marketing, sales, and leadership. Memory is unreliable when several people can edit accounts or websites. The log makes reversals safer and stops the same failed idea from being rediscovered a month later.
Manage pacing without chasing the meter
Budget control is a weekly forecast tied to capacity, not an emotional response to each day’s spend.
Reforecast remaining spend using the actual run rate and known schedule, then compare it with the cap. If the platform’s controls or reporting behave differently than expected, state that uncertainty rather than assuming precise pacing is possible. Never spend into a fulfillment bottleneck just because budget remains.
When delivery is under plan
Verify campaign status, billing, approvals, schedule, eligibility, and tracking before changing strategy.
Check whether territory, offer, or available inventory is intentionally narrow.
Do not loosen qualification or expand into unprofitable ZIP codes merely to spend the budget.
Escalate unresolved platform limitations and revise the forecast honestly.
When delivery is over plan
Confirm the comparison period and whether delayed reporting is affecting the view.
Protect the approved total cap and verify any daily or campaign controls available.
Check whether operations can handle the resulting inquiry pace.
Reduce exposure deliberately; avoid repeated intraday changes that produce unstable management.
Build the lead-quality feedback loop
Every inquiry needs a source, owner, first-response timestamp, qualification status, appointment status, estimate outcome, sale outcome where available, and a concise loss reason. Marketing does not need private sales commentary; it needs consistent operational facts. Sales needs a short workflow that fits the CRM rather than a spreadsheet nobody maintains.
Hold a brief weekly review with one person empowered from each side. Read representative records: a qualified lead that sold, one that did not, a disqualified inquiry, and an unreachable contact. Ask whether the ad promise matched the conversation, whether the location and service were valid, whether response was timely, and whether the stated loss reason is supported.
Use count only as the top of the story. Ten inquiries with unknown dispositions reveal less than a smaller group with verified service fit, appointments, and outcomes. A low count can still expose useful message or routing issues; a high count can conceal spam, out-of-area demand, or calls abandoned on hold. Optimize toward qualified opportunities and economic outcomes as the data matures.
Pause, hold, or scale for a documented reason
Scaling is not a reward for a good-looking dashboard. Confirm that qualified opportunities become appointments and sold work at economics the business accepts, allowing for the sales-cycle delay. Increase in controlled steps and keep watching quality and capacity. Prior results do not guarantee that additional spend will behave the same way.
Pause
Stop for compliance concerns, materially inaccurate claims, broken conversion paths, spend beyond authorization, persistent misrouting, no fulfillment capacity, or evidence that the offer cannot be delivered.
Hold
Maintain the current setup when systems work, spend remains controlled, evidence is still thin, lead outcomes are pending, or a recent test has not had a fair observation window.
Scale carefully
Consider incremental expansion only when verified lead quality and downstream economics support it, operations have capacity, tracking is trusted, and the next budget step remains affordable.
Revise
Make a bounded change when repeated evidence identifies a correctable mismatch in message, territory, destination, routing, or campaign inputs.
Avoid the mistakes that kill a promising test
The familiar failure pattern is operational: the team changes multiple variables after a quiet day, judges performance before sales outcomes mature, misses calls during advertised hours, and follows forms slowly. Marketing then optimizes against incomplete data while sales concludes that the source is poor. None of this proves the channel could or could not work; it proves the test was not controlled.
Assign owners before problems occur. One person protects budget and change control, one owns tracking and routing, and one owns lead disposition and follow-up. Review unanswered calls and aging leads as urgently as ad settings. A relevant placement cannot compensate for a ringing phone nobody answers.
Finally, do not let novelty lower the standard applied to other paid media. Require accurate claims, documented access and platform limitations, sensible economics, clean measurement, and honest reporting. The channel is still developing, so disciplined operations (and comfort with uncertainty) matter more, not less.
What should I check on the day my ChatGPT ads go live?
Verify the live offer, geography, schedule, budget controls, destination, and available campaign settings against the approved plan. Then complete test calls and forms, follow events into reporting and the CRM, confirm notifications and routing, and make sure the people answering leads understand the offer.
Should I optimize the campaign during the first two weeks?
Monitor it closely and immediately correct tracking failures, inaccurate claims, routing errors, policy concerns, or uncontrolled spend. Avoid broad strategic edits based on a few early events; use the initial period to build a clean baseline and record lead dispositions, while recognizing that 14 days is an operating guideline rather than a universal evidence threshold.
How often should I change a live campaign?
Use a regular weekly review and make changes around one documented hypothesis at a time, unless an urgent customer, compliance, or budget issue requires immediate action. Record the evidence, exact change, expected signal, and review date so the team can understand what caused the next result.
What do I do if the campaign is spending too slowly or too quickly?
For under-delivery, first check status, billing, approvals, schedule, eligibility, inventory, and tracking rather than expanding into weak territory just to spend. For over-delivery, protect the authorized cap, account for reporting delay, verify available controls, and confirm the operation can handle the inquiry pace before maintaining exposure.
How can I tell whether the leads are actually good?
Track service need, location, contactability, qualification reason, appointment, estimate, sale, and loss reason in a consistent workflow. Review representative records with sales each week and judge the source by verified fit and downstream outcomes, not by raw call or form count alone.
Ready to turn ChatGPT conversations into booked jobs?
Claim your free strategy session today. We'll review your local market and outline a practical way to test ChatGPT advertising.
This runbook assumes the commercial choices are already signed off. If they are not, stop editing the live campaign and return to the pre-launch planning sequence. For a refresher on placement boundaries and platform uncertainty, use the channel overview.