Why this matters
On Meta the objective is the instruction the delivery system optimises against, and it cannot be changed once the campaign is published. Pick Traffic for a goal that is really about bookings and the system will find people who click, report a lovely cost per click and fill no tables.
This exercise applies two readings. The Meta campaign objectives guide gives you the objectives, the optimisation goals beneath them and the rule for matching them to a business goal: choose the event closest to the outcome that still happens often enough to learn from. The complete guide to how Meta Ads works explains why: the auction ranks ads partly on the predicted rate of the action you asked for. If the price of impressions is hazy, the glossary entry on cost per thousand impressions is a short refresher.
The café and its goals
Dicebox Café is a fictional board game café in a market town, with bookable game nights, a tiny online shop and a private room for parties. The pixel is installed on the website, the booking system and the shop. The owner has written down everything they want from "doing Facebook and Instagram".
Dicebox Café: the owner's goal list
| Goal | What happens now | How often it happens |
|---|---|---|
| A. Let people within about five miles know the café has moved to bigger premises | Nothing yet; the move is in six weeks | Not applicable |
| B. Fill Thursday game nights, booked and paid online at £8 a seat | Purchase event fires on the booking confirmation | About 25 bookings a week |
| C. Sell more games through the online shop | Purchase event fires on the order page | About 3 orders a week; add to cart about 40 a week |
| D. Get enquiries for private parties (birthdays, office socials) | People message the café's Instagram and Facebook accounts | About 4 conversations a week, roughly half become bookings |
| E. Grow the email list for the monthly events newsletter | Sign-up form on the site fires a complete registration event | About 30 sign-ups a week |
| F. Appear higher when people search Google Maps for a board game café | The Google Business Profile has few photos and old opening hours | Not applicable |
| G. "Get more likes on our posts" | Posts get a handful of likes each | Not applicable |
- Monthly Meta budget: £600, to be split by the owner later.
- The owner checks Instagram likes daily and the till weekly.
Matching goals to objectives
Work from the business outcome down, never from the metric the owner likes to watch. For each goal ask: what outcome does the business pay for, which objective names it, and which event is closest to it while still happening often enough to learn from? Where the true event is too rare, use the guide's step-up compromise: optimise for the next event up the FunnelModel of the customer journey stages., watch whether it still tracks the outcome, and move back down when volume allows. Asking the system to find buyers means a higher CPMCost per 1,000 impressions. than asking it to find clickers; cost per result is the comparison that matters.
Task
- For goals A to E, write the campaign objective you would choose and the optimisation goal or conversion event beneath it.
- For each of those goals, write one sentence describing the people the delivery system will look for as a result of your choice.
- For goal C, decide whether the purchase event happens often enough to optimise on. If not, say what you would optimise for instead and what you would watch.
- Decide which goal should not be a Meta campaign at all, and say where it belongs.
- Decide what to do with goal G, and write the sentence you would say to the owner.
- Say which goals could share a campaign and which need their own.
Worked answer
Goal A: Awareness, optimised for reach, with a frequency cap. The move is news, not an offer. The system looks for as many distinct local people as the budget allows, and the cap limits repeats. Measure ReachUnique people who saw an ad. against the local population, then whether bookings rise after the move.
Goal B: Sales, website conversion location, optimised for purchase. Seat bookings are paid online and the event fires reliably, so the system learns from the real outcome and looks for likely bookers, not tappers.
Goal C: Sales, but stepped up the funnel for now. Shop purchases are too rare to learn from. Optimise for add to cart as a bridge and compare cost per add to cart with cost per order each week; if they stop moving together, the proxy has drifted. Holding this campaign until game nights run well is also defensible.
Goal D: Leads with a messaging conversion location, optimised for conversations. Party enquiries already arrive as messages. The system looks for people likely to start a chat, and a reply flow asking date, group size and occasion turns conversations into qualified leads.
Goal E: Leads, website conversion location, optimised for complete registration. The sign-up event fires often enough, and the system looks for likely subscribers.
Goal F: not a Meta campaign. Maps visibility depends on the Google Business Profile, which no Meta objective touches.
Goal G: reframe it. People who like posts readily are not the people who book tables. Tell the owner: "Likes are cheap to buy and do not pay the rent; let's judge Meta on bookings and party enquiries, and let likes rise from better posts."
Shared or separate. Each objective is its own campaign. Goals B and C share Sales but need different events and budgets, so separate campaigns stop the shop draining game night money. Goals D and E share Leads but need separate ad sets for their different events and conversion locations.
Common mistakes
- Traffic for bookings. The system finds clickers; the café wanted seated customers.
- Engagement because likes are visible. The objective follows the dashboard, not the till.
- Optimising the shop for purchase anyway. Too few events and the ad set never stops learning.
When you are confident with these choices, try the auctions, objectives and structure checkpoint, or return to the beginner Meta Ads level to see the module in order.
