Set up and install the Meta Pixel: the clear guide
Meta’s help article “Set up and install the Meta Pixel” only loads with JavaScript. Here are the steps in plain words, with Meta’s pages on what the pixel does, setup best practices and the test events tool, from Meta’s help center as read on October 9, 2026.
On this page · 8 sections
The Meta Pixel is a piece of code you put on your website so Meta can log the actions people take there, such as adding to cart or buying, and measure what your ads produce. Setting it up takes two steps: create the pixel in Events Manager and add its base code to your site, then set up the events you want to measure. In Events Manager, you click Connect data, select Web, name your pixel and click Create pixel. Meta then checks your website for a partner integration, such as a shop platform, and offers Get guidance, which it recommends, or Do it yourself. You can install the pixel alone or with the Conversions API, which Meta also recommends. To check it works, visit a page with the pixel: the page view event should appear in Events Manager and the status should switch to Active. The test events tool shows events live.
TL;DR
- The Meta Pixel is code on your website that logs actions, called events, so Meta can measure your ads.
- Two steps: create the pixel and add its base code, then set up events like purchases.
- Start in Events Manager: Connect data, Web, Connect, name it, Create pixel.
- Check it with the page view event, the test events tool and the Diagnostics tab.
- Adwize does not install your pixel. It reads the results your Meta account reports each day.
What is the Meta Pixel?
The Meta Pixel is a piece of code you place on your website. It logs when someone takes an action there, which Meta calls an event, such as adding an item to the cart or making a purchase. Meta uses those events to measure how effective your ads are on Facebook and Instagram.
Meta lists three uses. Showing your ads to the right people, including people who visited a page or took an action. Driving more sales with automatic bidding toward people likely to act. And measuring what happens after people see your ads.
You see those events in your pixel’s dataset in Events Manager. In Ads Manager, you can turn them into custom audiences or use them for retargeting ads.
What do you need before you install it?
Meta names two requirements. You need a business website or app. And if you install the pixel manually with code, you or your developer must be able to update your website’s code, or the tag manager you use. If you go through a partner integration, the partner handles the code.
Setup comes in two steps. First, create the pixel in Events Manager and put its base code on your site, through a partner integration if one exists, or by hand. Second, set up events for the actions you want to measure, through a partner, the point-and-click event setup tool, or code.
Meta guides you through the options during setup. If you choose manual setup, plan for some developer time.
How do you create and install the Meta Pixel?
Go to Meta Events Manager, click Connect data, select Web and click Connect. Enter a name for your pixel and click Create pixel: this creates a new pixel ID, visible in Events Manager. If you have a website, enter its URL and click Check, so Meta can look for an easy partner integration.
If Meta finds a partner integration, click Next and follow the steps on your partner’s website. If not, click Next. Without a website, tick I don’t have a website and continue. Then choose Get guidance, which Meta recommends and which hands you onscreen recommendations, or Do it yourself if you already know your setup.
With Do it yourself, pick Conversions API and Meta Pixel, or Meta Pixel only. For the pixel alone, choose Install code manually or Check for partner, or click Email instructions to send the steps to your developer.
- Events Manager: Connect data, then Web
- Name your pixel, click Create pixel
- Enter your URL and click Check
- Choose Get guidance or Do it yourself
- Pixel only, or Pixel with Conversions API
Should you add the Conversions API too?
Meta recommends it. If you share events with the pixel, Meta suggests also using the Conversions API, which works alongside the pixel to improve the performance and measurement of your campaigns. Its best practices page calls sending the same events through both a redundant setup, and suggests it for purchases, checkouts and contacts.
The reason Meta gives: the Conversions API can share website events the pixel may miss because of network issues or page loading errors.
During setup, Meta offers three ways to add it: a partner integration, a Meta-enabled web-only Conversions API, or manual setup with personalized instructions. Our Meta Conversions API guide covers it in detail, so this page sticks to the pixel.
How do you set up events without errors?
Events are the actions the pixel logs. Meta’s best practices start with the base code: if you installed it by hand, everything between the script tags must match your pixel base code exactly. If you used a tag manager, troubleshoot there, because the code will not show on the page itself.
Order matters. Your page’s own code comes first, then the pixel base code, then the standard event code, such as add to cart. Spelling matters too: event names are case sensitive. Meta’s example is fbq('track', 'viewcontent') instead of ViewContent, which creates a custom event named viewcontent rather than the standard one.
Example. A shop adds the Purchase event to its thank-you page but types purchase in lowercase. Events Manager then shows a custom event called purchase, and the standard Purchase stays empty. Fixing the capital letter puts it back.
- Your page code
- = first
- Pixel base code
- = second
- Standard event code
- = third
- viewcontent instead of ViewContent
- = a custom event, not the standard one
How do you check that your pixel works?
Start simple. Visit a page where the full base code is installed. The page view event is part of the base code, so if the pixel works it sends that event to Meta. It then appears on your pixel’s page in Events Manager, and the pixel status changes to Active.
Then use the test events tool. In Events Manager, click Data sources, select your pixel and click Test events. For website events, enter your URL, click Open website and browse: your actions appear live, and you can filter by event type, URL or errors. Activity is only recorded while the test events page is open, and test data stays 24 hours unless you clear it.
Two more checks. The Diagnostics tab in Events Manager flags setup problems and suggests fixes. If you cannot access the ad account that owns the pixel, Meta suggests installing Meta Ads Data Advisor, which shows in a pop-up which pixel and events loaded on a page. Meta adds that data can take 30 minutes or more to appear in your analytics.
| Tool | Where | What it shows |
|---|---|---|
| Page view event | Your pixel’s page in Events Manager | Event received, status Active |
| Test events tool | Events Manager, Data sources, Test events | Your events live, with errors |
| Diagnostics tab | Events Manager | Setup problems and suggested fixes |
| Meta Ads Data Advisor | Browser pop-up on your page | Pixel and events found on the page |
Which rules apply to the pixel?
Meta asks you not to share prohibited information through the pixel or its other business tools. That includes health, financial and children’s data, and anything its terms, policies or the law do not allow. Meta advises reviewing your event names, parameters and URLs regularly, and asking legal counsel if unsure.
Meta’s Business Tools Terms also forbid placing the pixel tied to your ad account on websites you do not own, unless you have permission.
One pixel can cover your whole website, across all its pages. Meta notes there can be reasons for two, for example when two agencies each run ads for your business and each sets up its own pixel.
Where does Adwize fit with your pixel?
Adwize does not install your pixel, does not edit your website and does not set up events. You install the pixel once, with Events Manager, a partner integration or a developer. Adwize then works with the results your Meta ad account reports, inside your own account. See the Report page.
Each day, Adwize reads those results, says in one sentence what changed, and proposes a change that waits for your approval. Nothing launches, changes or spends without your yes. See the Optimize page.
Adwize works with Meta ads only, on Facebook and Instagram.
Frequently asked questions
Do I need a developer to install the Meta Pixel?
Not always. A partner integration can set it up through your site platform. Meta says manual setup with code may need a developer, and Events Manager offers an Email instructions option to send the steps to one.
How do I know my Meta Pixel is working?
Visit a page with the base code. The page view event should appear on your pixel’s page in Events Manager and the status should be Active. The test events tool shows your events live.
Why does my event show up as a custom event?
Event names are case sensitive. Meta’s example: writing viewcontent instead of ViewContent creates a custom event named viewcontent. Match the standard spelling exactly.
Should I use the Meta Pixel and the Conversions API together?
Meta recommends it. The Conversions API can share events the pixel misses because of network issues or page loading errors. Our Conversions API guide explains the setup options.
Can Adwize install my Meta Pixel?
No. Adwize does not edit your website or set up events. You install the pixel in Meta; Adwize then reads the results your ad account reports and proposes changes for your approval.
Sources
- Meta Business Help Center, Set up and install the Meta PixelAccessed 10/09/2026
- Meta Business Help Center, About Meta PixelAccessed 10/09/2026
- Meta Business Help Center, Best practices for Meta Pixel setupAccessed 10/09/2026
- Meta Business Help Center, Test events tool: verify app and web browser events for MetaAccessed 10/09/2026
