The Meta Pixel is a visit counter at your shop door. It records who entered, which shelf they paused at and whether they reached the till, so you can see it in the ads tools. In code you call the fbq function.
You get the base code from Events Manager and place it inside the head tag of every page. The developer docs explain that the head placement reduces the chance of browsers or third-party code blocking the pixel and raises the chance visitors are tracked before they leave. The base code calls fbq('init', pixelId) and sends a PageView automatically; keep that call intact. Standard events such as purchases and add-to-carts are called yourself, like fbq('track', 'Purchase', {value, currency}). Most tag managers also work.
To verify installation, check that PageView appears in Events Manager and that the Pixel Helper extension shows no errors. The pixel uses cookies to match visitors to Meta users, tracks URLs, domains and devices by default, and also collects button clicks and form field names (field values only through advanced matching or optional values).
Because it runs only inside the browser, blocking or early exits can drop events. That is why teams pair it with the server-side Conversions API.
When to use
Required for web conversion optimization and visitor audiences; confirm PageView and key events actually arrive after installing.