Meta Ads: how to set up a campaign and measure it properly
A Meta Ads campaign consists of a campaign, an ad set and an ad. Whether it pays off only becomes clear once enquiries and sales are measured cleanly. Here is how to go about it.

Meta Ads, meaning ads on Facebook and Instagram, are created in Meta Ads Manager: you choose an objective, set the audience, budget and placements in the ad set, and build the ad. That gets the campaign running, but it is far from running properly. You can only judge whether it pays off once it is clear which event counts as a result, and once that event reliably reaches Meta.
How is a Meta Ads campaign structured?
Meta Ads Manager works on three levels. At campaign level you choose the objective. In the ad set you set the audience, budget, schedule and placements, meaning whether the ad appears in the feed, in Stories or in Reels. At ad level you design the image or video, the text and the destination URL. Because budget and audience sit in the ad set, it is best to compare variants there rather than at campaign level.
There are six groups of objectives to choose from. They decide which behaviour Meta aims the ad at:
- Awareness: show the ad to as many people as possible
- Traffic: clicks to a website or profile
- Engagement: reactions, messages, video views
- Leads: contact details, through an instant form on Meta or a form on your website
- App promotion: installs and in-app actions
- Sales: purchases, including in an online shop
You then build the campaign in this order:
- At campaign level, choose the objective, for example Leads
- In the ad set, define where the result happens (website, instant form or messages) and which event counts
- Set the audience, budget, schedule and placements, and leave placements on automatic to begin with
- At ad level, create the image or video, the text and the destination URL with UTM parameters
- Check the preview for each placement and submit the campaign for review
Which objective fits: Leads or Sales?
Choose the objective that comes closest to your business. A trades business with a contact form needs Leads, an online shop needs Sales. The Traffic objective looks tempting because clicks are cheap. But Meta then shows the ad to people who click a lot, not to people who enquire or buy. If you want enquiries, you should have the campaign optimised for enquiries.
With the Leads objective there are two routes. With an instant form, the person stays in Facebook or Instagram, fills in the form there and Meta delivers you the data. That is convenient, but the enquiries are often less committed, and you cannot see what becomes of them unless you transfer the data to your CRM. On the route through your own website, you measure the Lead event with the Meta Pixel after the form has been submitted successfully. Then you can see the person’s path on the site and attribute the enquiry using UTM parameters.
→ Cookie banner with Consent Mode v2: compliant, with no monthly licence
What do you need to measure before the campaign starts?
Set up measurement before you spend any money. Meta only optimises for events that arrive, and an event that was never measured cannot be made up for later. How the pixel and the dataset fit together and how to read test events is explained in Meta Events Manager. This order has proved its worth:
- Create the dataset (pixel) in the business portfolio and connect it to the ad account
- Install the Meta Pixel through Google Tag Manager or your shop system
- Send the Lead event on a successful submission, or Purchase with value and currency
- Check a real run-through in Test events, with and without consent in the cookie banner
- Verify the domain in the business portfolio
- Optionally add the Conversions API and deduplicate with a shared event ID
Why do Meta Ads and Google Analytics 4 show different numbers?
Meta and Google Analytics 4 (GA4) count by different rules, so the numbers almost always differ. A difference is not proof of an error. It becomes a problem when you do not know the reasons and therefore trust the wrong number.
| Cause | What happens | How to check |
|---|---|---|
| Attribution window | Meta assigns results to an ad if they occur within a time window after a click or view. GA4 evaluates visits according to its own channel model. | Compare the ad set’s attribution setting with the GA4 attribution model |
| How views are counted | Meta can also attribute results to people who only saw the ad. GA4 only sees visits to your site. | Look at the click-based columns separately in Meta |
| Consent | Without consent in the cookie banner, pixels and tags in the EU send nothing. The gap differs from tool to tool. | Test run with consent and with rejection |
| Missing UTM parameters | GA4 does not know the visit came from the ad and records it as direct or social. | Open the ad’s destination URL in the preview |
| Ad blockers | The pixel in the browser is blocked, while a server event can still arrive. | Compare browser and server in Events Manager |
As a guide: Meta shows what Meta attributes to the ad. Your website analytics or your CRM shows what actually arrived as an enquiry or an order. In the end, the number from your own system is what counts. The Meta number helps you compare ads with one another.
→ Setting up Google Consent Mode v2 correctly: no warning in Tag Assistant
How long do you test, and how do you judge results?
Give a campaign time. Meta recommends planning the budget for at least seven days. During that time the system learns who to show the ad to. As a rule of thumb, Meta cites about 50 optimisation events per ad set after the last significant edit, and its training material mentions about 50 results per week. With only a few enquiries a week you will not reach that figure. The ad set then shows the status “Learning limited”. In that case it helps to run fewer ad sets instead of spreading the budget across many.
Do not judge by the cost per click, but by the cost per enquiry or per sale. The formula is: cost per enquiry equals spend divided by enquiries. Suppose you spend €300 in two weeks and get 12 enquiries, then one enquiry costs €25. If those 12 enquiries led to 4 jobs, one job costs €75. Whether that is good depends solely on your profit per job. For clean comparisons, Meta offers A/B tests in which exactly one variable is changed.
Example: a trades business with a contact form
A painting and decorating firm runs Meta ads for facade painting. It chooses the Leads objective with a form on its own website and measures the Lead event only on the thank-you page. The first days show lots of clicks but hardly any enquiries. A look at Events Manager reveals the reason: the event fired when the submit button was clicked, even for forms that had been filled in incorrectly. After the fix, the Meta number and the inbox agree, and the firm can see which ad brings in real enquiries.
Measurement errors like these often go unnoticed for weeks. In the free Trackum check, a real browser examines your site three times and shows findings with a fixed price to put them right, with no sign-up. Trackum sets up measurement for Meta, optionally with campaign data in every enquiry and a dashboard showing ROAS per campaign. Trackum does not plan or manage campaigns. All prices excl. VAT.
Frequently asked questions
Which campaign objective should I choose in Meta for enquiries?
For enquiries through a form on your website, the Leads objective fits, optimised for the Lead event, or the Sales objective if you can measure sales. The Traffic objective, by contrast, optimises for clicks. Meta then shows the ad to people who like to click, not necessarily to people who send an enquiry.
How long should a Meta campaign run at the very least?
On its page about advertising costs, Meta recommends planning the budget for at least seven days so that the system can evaluate performance. Change as little as possible about the audience, budget and ads during that time. Any major change can restart the learning phase of the ad set.
Do I need the Conversions API for Meta advertising?
It is not mandatory, and the Meta Pixel in the browser is enough to start with. The Conversions API additionally sends the same events from the server and partly makes up for losses caused by ad blockers and browser settings. You then need to prevent double counting with a shared event ID.
How can I tell which enquiry came from an ad?
Add UTM parameters to the ad’s destination URL and make sure they are kept all the way to the enquiry. Meta also adds the click ID fbclid. If you save these values with every enquiry, you can later also attribute sales to the ad.
Sources
- Meta: Ads Manager facebook.com
- Meta Business Help Centre: Meta ad pricing and budget facebook.com
- Meta Business Help Centre: Facebook attribution model facebook.com
- Meta Business Help Centre: About A/B tests facebook.com
- Meta for Developers: Conversions API developers.facebook.com
- Meta Business Help Centre: About the learning phase facebook.com
Read more
FeaturesCookie banner with Consent Mode v2: compliant, with no monthly licence
Reject on the first layer, settings per purpose, Consent Mode v2 with every consent type and a record of each choice. No monthly licence.
FeaturesSetting up Google Consent Mode v2 correctly: no warning in Tag Assistant
The most common warning in Tag Assistant says a tag read consent before a default was set. How to avoid it, and what else matters.
FeaturesMarketing dashboard with GA4 and Google Ads: every number on one page
Visitors, leads, orders, ad spend and ROAS per campaign on one page, compared with the previous period. One link, nothing to set up.
FeaturesRevenue from your CRM, shop and ERP in one dashboard: HubSpot, Shopify, Odoo and more
Google Analytics only sees what happens on the website. Orders by phone or email are missing. With a data connection, the real revenue from your system appears in the dashboard.
FeaturesWebsite leads with their source in your CRM: HubSpot, Pipedrive, Brevo, Salesforce or webhook
Where did the lead come from? The CRM handover writes source, campaign and click ID into the CRM with every enquiry, without a form plugin.
FeaturesOffline conversions: report sales from your CRM to Google Ads and Meta
Google Ads and Meta learn from what you report to them. If they only get form fills, they optimise for form fills. With offline conversions, they optimise for sales.