A Worked Example: Your First Ad Budget Over Seven Days

This is a worked example of a first ad budget, not a case study. Everything below is made up to show the process. The bakery, the numbers and the outcome are illustrative, and you should not read them as results or benchmarks. What is real is the platform behaviour I cite, which comes from the platforms' own help pages.

The point is to show what a first ad budget looks like day by day, so you can picture doing it. Lesson 4.6 gives you the actual routine: Spend your first $100 on ads the smart way.

A good first week is not about winning. It is about finishing with a clear record of what you tried and a decision about what to do next.

The imaginary first ad budget setup

Say you run a small bakery that takes custom cake orders. You want more enquiries from people in your town. You have a simple page with photos, a short description and an enquiry form. You have $100 to spend on a first test, and you decide on a seven day run.

Day 0: the plan, before you spend

You write the plan on one page.

• Cap: $100 total, which is about $14 a day. You will check spend daily and pause if the total is reached.
• Audience: people within a short drive of the bakery who are planning a birthday or event.
• Counted action: a cake enquiry form submission.
• Two ads: same photo of a finished birthday cake. Ad A opens with "Birthday coming up? Order your cake this week." Ad B opens with "Custom cakes, made to your design." Only the first line differs.
• Stop rule: if half the budget is gone and there are zero enquiries, check the page and the counting, then pause.

You also test the page on your phone and submit the form yourself to confirm the count goes up.

Day 1: launch and wait for review

You submit the ads. Meta's advertising standards say its review process typically completes within 24 hours, though it can take longer, and ads can be re-reviewed after going live. So the ads may not run straight away. You do not panic or edit. You check that the status moved from "in review" to active.

Day 2: check spend only

You open the dashboard to confirm spend is close to your daily figure and not racing ahead. On Google, a daily budget can be exceeded by up to double on a given day, so you look at the total, not just the daily figure. In this imaginary example, spend looks normal.

Day 3: first read

You look at four numbers: total spent, enquiries, cost per enquiry and which ad is ahead. Imagine there are two enquiries so far, both from Ad A. That is far too little to prove anything. You write "Ad A slightly ahead, too early" and change nothing. Meta's help centre says ad sets usually exit the learning phase after about 50 results in the week after the last significant edit, so with this few results you know the data is thin and the delivery is still settling.

Days 4 to 6: leave it alone

You resist the urge to add a third ad or to change the audience. A significant edit could restart learning, and you would lose clean data. You check spend once a day, and nothing else.

Day 7: the decision

You add up the week. Imagine you spent about $100, and got a handful of enquiries, most from Ad A. You then do your break-even sum. If a typical cake order is worth enough profit that a few enquiries could pay back the cost, the test is encouraging. If not, it is a warning.

You choose one of three:

• Stop if enquiries were few and the cost per enquiry was far above the profit from an order.
• Keep if the signal was positive but thin, and run another $100 on the same setup.
• Grow only if Ad A is clearly ahead and the cost leaves room for profit. Even then, raise spend gradually.

In this example, you pick "keep": same audience, Ad A as the control, and a new Ad B with a different image.

What the week taught, even without big numbers

Notice what the bakery learned without any dramatic outcome:

• Whether "this week" urgency or "custom design" drew more enquiries.
• How long ads took to start.
• That the enquiry form worked and was counted.
• Roughly what an enquiry costs, as a first estimate.

That last one is a rough guess, not a promise of what the next $100 will do.

The log entry

The bakery owner writes one line in a notes file:

Week 1. $100 cap. Local audience. Counted: cake enquiries. Ad A (urgency) vs Ad B (custom). A ahead on thin data. Decision: keep, test a new image against A. Next review: day 3.

What changes in your own case

Your business, offer and local market will differ, and so will your costs. A service business may count phone calls. An online shop may count purchases. A coach may count calendar bookings. Google Ads supports measuring conversion actions such as purchases, sign-ups and phone calls, so choose the one that fits.

If you want to see how others might frame their first test, the examples post lists twelve illustrative setups. For tracking the numbers, see the metrics guide.

Your seven day version

Copy the shape, not the numbers.

1. Day 0Write the cap, audience, counted action, two ads and stop rule.
2. Day 1Launch and allow time for review.
3. Day 2Check spend against your cap.
4. Day 3Read the first numbers. Change nothing unless something is broken.
5. Days 4 to 6Check spend daily. Do not edit.
6. Day 7Add up, do the break-even sum and choose stop, keep or grow.

Lesson 4.6, Spend your first $100 on ads the smart way, takes you through setting the $100 limit, building the one audience, two ad test, reading the first three days and deciding what the next $100 does.

Questions people ask

Are the bakery numbers real?

No. The bakery is invented and the figures are illustrative. Only the platform behaviour cited comes from official help pages.

Should I expect results like these?

No. Results depend on your offer, page, audience and market.

Why seven days?

It is long enough to see a pattern and short enough to limit risk. You can run it shorter or longer.

What if nothing happens in a week?

Check the page, the counting and the offer, then decide whether to stop or retest with a change.