The Meta Pixel is JavaScript on your website that reports what visitors do, called events, to Meta, which uses them to measure results, build audiences and optimize delivery. Meta gives you three ways to track conversions with it. Standard events are the 17 actions Meta has predefined names for, such as Purchase and Lead. Custom events are actions you name yourself in code. Custom conversions are rules built in Events Manager on top of those events or your page URLs, with no new code. This guide covers all three, choosing the conversion event a campaign optimizes for and testing events before a new account spends.
What the Meta Pixel does, and how it fits with datasets and the Conversions API
Meta defines the pixel as a piece of code on your website that helps you measure the effectiveness of your advertising by understanding the actions people take there. It logs each action as an event, and Meta uses those events to show ads to people more likely to take an action you care about, build custom audiences such as recent visitors and measure results. By default, Meta's developer guide adds, it also tracks the URLs and domains visited and the devices visitors use.
Those events are organized into a dataset, which brings website, app, offline and business chat events together under one ID. A dataset linked to an existing pixel keeps the pixel's ID, and Meta says you can use a dataset ID as you would a pixel ID, for example to set up the pixel or the Conversions API. That is why newer screens, such as Datasets and pixels in Meta Business Suite settings, say dataset where older guides say pixel.
The Conversions API is the server-side route into the same dataset. Meta describes it as a direct connection from your server, website platform, app or CRM that is less affected than the pixel by browser loading errors, connectivity issues and ad blockers, and says its website events are used for the same types of optimization as pixel events. Meta recommends sending the same events through both, with a shared event ID so each action is counted once. Our Conversions API setup guide covers the server side and our Pixel and CAPI deduplication guide covers the event ID.
Base code and PageView: what loads on every page
Every pixel starts with base code from Events Manager that holds your pixel ID in two places. Meta recommends placing it between the opening and closing head tags of every page you track, where browsers and third-party code are less likely to block it. It loads the pixel's functions, initializes it with your ID and automatically tracks one PageView each time it loads, a call Meta recommends leaving intact. Create the pixel in Events Manager under Connect data, then Web, then add the code by hand, through a partner integration or with a tag manager; Meta's setup flow also offers to set up the Conversions API alongside it.
PageView only tells Meta that someone landed on a page carrying the base code. To confirm the install, load a page and check that PageView reaches Events Manager and the pixel's status turns Active. The pixel can also receive automatic events, actions it picks up from your site without extra code, which Meta deduplicates against events you set up yourself and recommends keeping on. One pixel can cover a whole website, and duplicate pixel code on a single page is one of the common setup errors Meta lists.
The 17 standard events and the parameters that matter
Standard events are actions with names Meta has predefined and supports across its ad products, used to log conversions, optimize for them and build audiences. You fire one with fbq('track') and the event name, either when a page loads, such as Purchase on an order confirmation page, or when a visitor acts, such as clicking a button. Names are case sensitive: Meta warns that tracking viewcontent instead of ViewContent creates a custom event called viewcontent. Meta's reference lists 17; the list below groups them by funnel stage.
Most parameters are optional, but two drive spend decisions. Meta's reference requires value and currency on Purchase, and its developer guide requires value for purchase events and any event used for value optimization, the Maximize value of conversions performance goal. Value must be a number of zero or more, with a decimal point and no letters, currency symbols or commas, and currency a three-letter code. Meta's standard Purchase code carries a placeholder of 0.00 US dollars, so replace it with the real order value or a dynamic one.
Other parameters serve specific products. Content IDs, contents and content type tie events to catalog items: for Advantage+ catalog ads, Meta's reference requires contents or content IDs on ViewContent, Search and Purchase, and contents on AddToCart. The num_items parameter goes with InitiateCheckout, search_string with Search and predicted_ltv, a subscriber's predicted lifetime value, with StartTrial and Subscribe.
- Browsing and discovery: ViewContent, Search, AddToWishlist, CustomizeProduct, FindLocation
- Cart and checkout: AddToCart, InitiateCheckout, AddPaymentInfo, Purchase
- Leads and contact: Lead, CompleteRegistration, Contact, Schedule, SubmitApplication
- Subscriptions and donations: StartTrial, Subscribe, Donate
- Not on the list: PageView, which the base code sends by itself
Custom events: tracking actions Meta has no name for
When none of the 17 fits, track a custom event with fbq('trackCustom') and a name you choose; Meta's example is ShareDiscount. Names must be strings of up to 50 characters. Custom events can carry the predefined parameters, value and currency included, plus your own custom properties; to build audiences from parameter data, Meta says key values must not contain spaces. Meta says custom events, like standard ones, help optimize for conversions and build audiences.
Each new custom event also needs a review. Meta asks you to review it in Events Manager, confirming that it comes from your business and follows the Meta Business Tools Terms, or blocking it. Confirmed custom events can be used with ads features such as campaigns, custom conversions and custom audiences, blocked ones cannot, and Meta requires the review before you can maximize value on one. The review sits in the dataset's Settings tab, under Data controls and Manage event blocking, and needs full control of the dataset.
Reporting is the other catch. Meta says Ads Manager shows standard events and custom conversions, while Ads Reporting adds custom events only if they were previously used to optimize delivery. To see a custom event as its own result in Ads Manager, build a custom conversion on it, and use a standard name whenever one fits.
Custom conversions: rules instead of code
A custom conversion is a rule applied to events you already send, built in Events Manager with no new code. Meta's example narrows all purchases to women's shoes over 40 US dollars. Rules can filter a standard event, a custom event or All URL traffic, which is based on PageView, so a site with only the base code can still count a thank-you page through a URL rule. You can use it as a performance goal, report on it and share it with other ad accounts or partners, who also need access to its dataset.
To build one, open Custom conversions in Events Manager, click Create custom conversion, name it, pick the data source and choose the conversion event; for All URL traffic or a custom event, Meta also asks for the closest standard event category to optimize toward. Then add URL or parameter rules. Several values within one parameter rule work as OR, while separate rules work as AND. Trigger the conversion once and check that its status reads Active.
Meta caps custom conversions at 100 per ad account, and its developer guide says product ID breakdowns and unique action counts are not supported for them in the Ads Insights API. They cannot optimize dynamic product ads, now Advantage+ catalog ads, though they can still measure them. Counts also differ by surface: Events Manager deduplicates custom conversion totals but not the Total events figure on its data sources page, and Ads Manager counts only conversions attributed to your ads.
- Prefer URL contains with the shortest unique part of the address
- Avoid URL equals unless the address never varies: UTM parameters, http instead of https or a trailing slash break it
- Use as few rules as possible; Meta says fewer rules mean a larger audience and more conversions
- Add a value, as a whole number, only if the underlying events carry none
- Repoint ad sets before deleting a custom conversion they optimize for; Meta says they keep delivering but may perform poorly
- Expect Meta to archive custom conversions that are inactive or not received for two years; restore one by recreating its rules
Picking the event your campaigns optimize for
The conversion event on an ad set tells Meta's delivery system what to find more of, so pick the most valuable action that happens often enough to learn from. Value is the first test: if sales are the goal, that usually means Purchase. Volume is the second: Meta says ad sets usually exit the learning phase after about 50 results in the week after their last significant edit, and flags those unlikely to get there as Learning limited.
Meta's fixes for Learning limited include combining ad sets, expanding the audience, raising the budget, bid or cost control and choosing an optimization event that occurs more often, its example being a move from purchases to add to cart. Treat that step up the funnel as temporary, and move back once volume allows. The Optimization events column in Ads Manager shows how many each ad set gets; our learning phase guide covers the mechanics.
Decide before launch, because Meta counts any change to the optimization event as a significant edit that sends an ad set back into learning. Use the same events and custom conversion rules in every ad account so results compare. If you optimize for value, send a value with every conversion: Meta says values work best when they reflect real differences in outcomes and are sent consistently, and its value optimization guidance lists the Conversions API as required alongside the pixel. For match quality, see our event match quality guide.
Testing events with Test Events and Meta Ads Data Advisor
Test before any ad set depends on an event. In Events Manager, open Data sources, select your dataset, click Test events, enter your website address and click Open website. Meta records website activity only while the Test events page stays open, and you can filter it by activity type, such as standard, custom or automatically logged pixel events, or by URL, parameters, errors and warnings. The tool also shows which web events were deduplicated, and server events have their own section.
Test activity stays in the tab for 24 hours or until you click Clear activity, but clearing it does not remove it from Events Manager, Ads Reporting or audience creation results. Meta also says data can take 30 minutes or more to reach your analytics after you set up an event, so verify in the test view meanwhile. Meta also says each standard event needs its own test conversion, such as adding an item to the cart to check AddToCart.
Meta Ads Data Advisor is the browser-side check: the new name for Meta Pixel Helper, a free Chrome and Edge extension that existing Pixel Helper installs update to automatically. A badge on its icon counts the pixel events fired on the page; no badge means no pixel. It flags broken events and missing parameters such as value or currency, its basic checks work without logging in, and Meta suggests it for testing a pixel whose ad account you cannot access. Meta notes that button clicks may go undetected and ad blockers must be off, and points to Test Events for in-depth troubleshooting.
Health, financial and other sensitive data: what Meta blocks
Meta's Business Tools Terms prohibit sharing health information, financial information and other sensitive data through the pixel and Meta's other business tools. The names and criteria of events, conversions and custom audiences must not reflect, imply or be based on prohibited information, which must also stay out of URL parameters, custom event names and custom data. Meta's examples include medical conditions, medications, credit scores, loan approvals and debt status.
Meta's developer guide dates more proactive restrictions to September 2, 2025: custom conversions suggesting specific health conditions, such as arthritis or diabetes, or financial status, such as credit score or high income, are flagged and cannot be used in new campaigns. A published campaign's custom conversion cannot be swapped, so Meta's fix for an active campaign is a new or duplicated campaign using an unaffected custom conversion. Flagged ones return is_unavailable as true in the API, and reviews can be requested in Ads Manager or Events Manager.
Meta can also block custom events it detects as carrying potentially prohibited information. You can request a review, but if Meta declines it, you cannot request another. Audit what your pages send, not only what you name: Meta warns that UTM parameters can carry prohibited data from the pages viewed, and that information should not be sent from pages where visitors log in and provide sensitive details, such as patient portals. Health advertisers should also read our health and wellness restrictions guide.
One dataset across many ad accounts, including agency ad accounts
A dataset created in your business portfolio, formerly Business Manager, belongs to that portfolio: Meta says it cannot be deleted or transferred to another portfolio, and each portfolio can create up to 100. So when a new, replacement or partner-shared ad account comes online, connect the dataset you already have instead of creating a fresh pixel, which would start with no event history and split one website's events across two IDs. Our pixel and dataset setup guide covers sharing across portfolios.
In Meta Business Suite, open Settings, then Data sources, then Datasets, click Add assets, select the ad accounts and click Add. You need full control of the portfolio, and the ad account must already be added to it; Meta lists getting shared access to another business's ad account as one way to add one. Custom conversions are capped per ad account, so keep each one's rules on file and share or rebuild them for every new account; the Marketing API can create them on each ad account's customconversions edge.
Agency ad accounts follow the same routine. Power Ads creates them in its own business portfolio and shares them into your Business Manager through partner access once you send your Business Manager ID or an admin invite link, with unlimited accounts and free replacements. Tracking stays with your team: Power Ads does not install pixels, configure events or run campaigns, so connecting the dataset, testing events and setting conversion events are your steps before any new or replacement account spends. Pricing is 4% deducted from each top-up, with no setup fee.
- Connect the existing dataset to the account
- Share or rebuild its custom conversions
- Confirm custom events are reviewed
- Fire each key event in Test Events
Key takeaways
- The Meta Pixel sends website events to a dataset from the browser; the Conversions API sends the same events from your server, and Meta recommends both, with a shared event ID so each action is counted once.
- Standard events are Meta's 17 predefined, case-sensitive names fired with fbq('track'); Purchase requires value and currency, and value optimization needs a value on every conversion.
- Custom events use fbq('trackCustom') and names of up to 50 characters, and each new one needs a review in Events Manager: confirmed events work with campaigns, custom conversions and audiences, blocked ones do not.
- Custom conversions are no-code rules on existing events or URLs, capped at 100 per ad account; since Meta began rolling out restrictions on September 2, 2025, ones that suggest health conditions or financial status can be flagged and kept out of new campaigns.
- Optimize for the most valuable event that reaches enough volume, and decide before launch: Meta treats any change to the optimization event as a significant edit that restarts learning.
- Connect your existing dataset to every new, replacement or partner-shared ad account and test its events in Test Events or Meta Ads Data Advisor, formerly Pixel Helper, before it spends.
FAQ
What is the Meta Pixel?
The Meta Pixel is a piece of JavaScript you add to your website that logs visitor actions, called events, and sends them to Meta. Meta uses them to measure ad results, build audiences such as recent visitors and optimize delivery toward people likely to act. Its base code tracks a PageView each time it loads, and the data lands in a dataset that the Conversions API can also feed from your server.
Is a Meta Pixel the same as a dataset?
Not quite. A dataset is the container in Events Manager that holds event data from your website, app, offline and business chat sources under one ID. The pixel is one way of sending website events into it, and the Conversions API is another. When a dataset is linked to an existing pixel, it keeps the pixel's ID, and Meta says you can use the dataset ID as you would the pixel ID, for example to set up the pixel or the Conversions API.
What is a conversion event in Facebook ads?
It is the action an ad set is told to get more of, such as Purchase, Lead or a custom conversion, chosen in the ad set's conversion settings. Set it up and test it before launch, then pick the most valuable event that happens often enough: Meta says ad sets usually exit the learning phase after about 50 results in the week after their last significant edit.
What is the difference between a custom event and a custom conversion?
A custom event is code: your site fires it with fbq('trackCustom') and a name of up to 50 characters, for an action no standard event describes. A custom conversion is a rule built in Events Manager on top of events you already send or your page URLs, such as purchases above a set value, with no new code. Ads Manager reports custom conversions, but not custom events on their own.
What happened to Meta Pixel Helper?
Meta renamed and expanded it. Meta Ads Data Advisor, formerly Meta Pixel Helper, is a free extension for Chrome and Edge, and existing Pixel Helper installs update to it automatically; if Chrome has switched the old install off, turn it back on from the extensions page. It still shows which pixel events fired on a page and flags issues such as broken events or missing value and currency, and it adds setup help such as connecting the pixel and Conversions API through Google Tag Manager.
Do I need a new pixel for every new ad account?
No. Meta says one pixel can cover your whole website, and a dataset in your business portfolio can be connected to many ad accounts from Business Suite settings, provided each account has been added to your portfolio, which includes accounts another business shares with yours, such as agency ad accounts. A new pixel would start without event history and split your data. Connect the existing dataset, share or rebuild your custom conversions and test events before the account spends.
Sources
- developers.facebook.com/documentation/meta-pixel/get-started
- developers.facebook.com/documentation/meta-pixel/reference
- developers.facebook.com/documentation/meta-pixel/implementation/conversion-tracking
- developers.facebook.com/documentation/meta-pixel/support/meta-ads-data-advisor
- facebook.com/business/help/742478679120153
- facebook.com/business/help/952192354843755
- facebook.com/business/help/402791146561655
- facebook.com/business/help/780705975381000
- facebook.com/business/help/964258670337005
- facebook.com/business/help/2375212726097833
- facebook.com/business/help/2040882565969969
- facebook.com/business/help/198406697184603
- facebook.com/business/help/2455915321411996
- facebook.com/business/help/361948878201809
- facebook.com/business/help/750785952855662
- facebook.com/business/help/2041148702652965
- facebook.com/business/help/392174274295227
- facebook.com/business/help/2254103654917599
- facebook.com/business/help/723326514751348
- facebook.com/business/help/462806641140703
- facebook.com/business/help/3313524248726315
- facebook.com/business/help/1700857106877546
- facebook.com/business/help/1624255387706033
- facebook.com/business/help/1292598407460746
- facebook.com/business/help/344247017987537
- facebook.com/business/help/642275438032995
- facebook.com/business/help/337196340694086
- facebook.com/business/help/296463804090290
- facebook.com/business/help/112167992830700
- facebook.com/business/help/269269737396981
- facebook.com/business/help/316478108955072
- facebook.com/business/help/314143995668266
- facebook.com/business/help/1556728331732865
- facebook.com/business/help/915885887059947
