What is the Meta Pixel and how it tracks enquiries

The short answer: the Meta Pixel is a small snippet of JavaScript code you add to your website to see what visitors who came from your Facebook and Instagram ads do there [1]. Each action you want to count (a call, a sent form, a booked appointment) is called an event. The pixel reports it to Meta, so in Ads Manager you can see whether an ad brings customers, not just clicks [1]. If you run ads to your website without a pixel, you are paying without knowing what they bring you.

What the pixel does and what it doesn't

The pixel loads on your pages and waits. When someone does something you have marked as important, the code sends an event [1]. According to Meta, that data is used for three things [1]:

1. Measurement: how many enquiries and sales each ad brought in.
2. The path to a customer: at which step people give up before they write or call.
3. Audiences: you can show ads again to people who have already been on your website.

Here is what it doesn't do. The pixel only sees the website. The phone call itself happens outside it, so the pixel can count the tap on the Call button, but not whether the conversation took place. That is why it pays to ask new customers "how did you find us?", as explained in how to measure what your website brings you.

Meta also describes what the pixel collects: technical information about the browser, button clicks and the names of form fields, but not the values people type in, unless you choose to send them [1].

Which events to track: a table for small businesses

Meta has ready-made "standard" events [2]. You don't need all of them. For a salon, a garage, a restaurant or a clinic, three or four are usually enough:

One caveat: Meta says ViewContent tells you someone visited a page's address, but not what they saw or did there [2]. So don't count it as an enquiry.

Count the actions that lead to money: a call, a form, a booking. Visits are just the road there.

The clearer your buttons, the easier they are to count. If your website has no separate call button, start there: call-to-action buttons that bring customers.

Cookies and consent: the pixel doesn't start on its own

This is general information, not legal advice. The pixel uses cookies. According to the EU's Your Europe portal, a website must ask for your consent before placing a cookie that is not strictly necessary, explain what the data will be used for and let you withdraw your consent [4]. Advertising cookies are not strictly necessary.

Meta states plainly that each company is responsible for its own GDPR compliance [3]. So it provides a way to make the pixel wait: on every page it is paused first and starts only once the visitor presses "Accept" in the cookie banner [3]. If the person declines, no events are sent.

What this means for you: your reports will show fewer events than really happened, because some people decline cookies. That is normal. For personal data questions, talk to a lawyer or check your national data protection authority's guidance.

Pixel and Conversions API: do you need the second one?

The Conversions API is a connection that sends events to Meta not from the browser, but from your server, website platform or CRM [5]. Meta says that if you already have a pixel, you can switch on the Conversions API from Events Manager in one click, with no code and no setup fee [5]. When you use both, each event needs the same ID (eventID) so it isn't counted twice [2].

For a small website with a few enquiries a week, the pixel is usually a good enough start. The Conversions API makes sense once your ads run regularly and you want fuller data. The same consent rules apply to it.

Checklist: is your pixel working properly?

1. There is only one pixel, and it is on every page, not just the homepage.
2. The cookie banner holds the pixel back until the person agrees. Open the website in a new private window, decline and check that no events fire.
3. Events sit in the right places: Contact on the call button, Lead after a form is sent successfully (not when an empty form's button is pressed), Schedule after a confirmed booking.
4. Check with Meta Ads Data Advisor, the free extension for Chrome and Edge (formerly Meta Pixel Helper). It shows how many events fired on the page and whether there are errors [6].
5. Send yourself a test enquiry and see whether it shows up in Events Manager.
6. The website stays fast: every third-party script adds weight. If pages open slowly, see why your website is slow.

When you need a pixel and when you don't

If you only boost posts so more people see them, a pixel isn't essential. If you run a campaign aimed at enquiries or sales on your website, it is close to essential: without it there is no way to see which ads bring enquiries. And if you are still choosing where to advertise, read Facebook ads or Google Ads first.

And remember that the pixel only counts. If people come but don't get in touch, the problem is the page: how to turn website visitors into customers.

If you'd rather not think about events and campaigns, at Studio V1 we run Google and Facebook ads for a fixed monthly fee including VAT: €150 for Meta Ads (Facebook and Instagram) with a business page, one Motion Design video and one ad visual, €100 for Google Ads and €230 for both. You pay the ad budget straight to Meta and Google, with no commission to us, and you get a report every week. There is no minimum term. We don't promise a number of enquiries, but you will see what every euro brings.

References

1. Meta for Developers. "Meta Pixel." developers.facebook.com/docs/meta-pixel
2. Meta for Developers. "Meta Pixel API reference: Standard Events." developers.facebook.com/docs/meta-pixel/reference
3. Meta for Developers. "General Data Protection Regulation: Cookie Consent." developers.facebook.com/docs/meta-pixel
4. European Union, Your Europe. "Data protection and online privacy." europa.eu/youreurope
5. Meta for Developers. "Conversions API." developers.facebook.com/docs/marketing-api
6. Meta for Developers. "Meta Ads Data Advisor (formerly Meta Pixel Helper)." developers.facebook.com/docs/meta-pixel