LESSON 5 OF 8 / Paid media
Give automated ad campaigns a better definition of success
Review conversion quality, economics, creative and landing pages before increasing spend.
Your output: A campaign input checklist and a bounded test with a budget cap.
The campaign can optimize the wrong outcome
An inexpensive form submission is not automatically a good lead. If your primary signal includes spam, duplicate enquiries or people outside your service area, a campaign can look efficient while sales spends time on the wrong conversations.
Define your outcomes in stages: enquiry, qualified enquiry, booked conversation, acquired customer. Agree what qualifies and who records it. Audit the events before making bidding changes. Check duplicate fires, missing values, test submissions and whether the recorded action actually happened.
Work backward from contribution
Use a simple model before raising budgets. In an illustrative business, a customer produces $600 of contribution before acquisition cost, and the owner is willing to spend $150 to acquire one. If one in five qualified leads becomes a customer, the implied acquisition allowance is $30 per qualified lead. That is a planning assumption, not a promised campaign result.
Include agency fees, creative and software in your full economics. Distinguish media-only cost per lead from total cost per customer. Update the model if close rate, pricing, fulfillment cost or capacity changes. A channel is not scalable if the business cannot deliver the additional work profitably.
Connect sales outcomes when feasible
Google supports connecting downstream lead outcomes through enhanced conversions for leads and offline measurement. Its current documentation describes changes to supported upload routes, so verify the present setup instructions before implementation. A correctly configured connection still needs accurate source records and appropriate permissions.
When that connection is not ready, use a weekly reconciliation of campaign enquiries and sales outcomes. Be explicit about what the bidding system receives and what only appears in your internal review. Do not assume a dashboard automatically feeds qualification data back into the platform.
- Check the primary conversion action and remove inappropriate test signals.
- Agree qualification rules with sales.
- Review the actual search, audience and placement information available.
- Check the ad promise against the mobile landing page.
- Define the budget ceiling, observation window and stopping rule.
Test one useful change
Consider a test of a clearer service promise, a different proof point or a simpler next step. Keep the business outcome consistent. Changing bidding, audience, offer and page simultaneously makes interpretation harder.
Use qualified demand and customer outcomes alongside platform metrics. Report uncertainty when the sample is small or the buying cycle is long. An improvement in click-through rate may be encouraging, but it does not justify a profitability claim by itself. Keep human review of claims, spend and the customer experience.
Try it with your business
- Write the qualification rule and assign its owner.
- Calculate a provisional cost-per-customer ceiling from your actual economics.
- Audit one conversion path on mobile.
- Write a single-change experiment with a spend limit and review date.
Use the planning worksheet and save it as a PDF →
Use AI to help organize the work
Provide only material you are allowed to use. This prompt helps structure your evidence; it does not give the tool access to your analytics or verify facts on its own.
Review this anonymized campaign and sales summary. Check conversion definitions, duplicates, qualification, cost categories and sales lag. Calculate only what the supplied numbers support. Propose one bounded test with budget cap, primary business metric and a stop rule. Do not promise ROAS.
Measure: Cost per qualified enquiry and acquired customer, with a separate view of media and total acquisition costs.
Sources & further reading
Official references checked October 26, 2026. Product reporting and requirements can change.