You have a campaign to launch and you see your facebook pixel not showing in ads manager. This happens when your dataset is not connected to your specific ad account in Meta Business Settings. It also happens when your user profile lacks the right permissions. You need to assign these assets manually before the pixel appears in your campaign setup.
Finding your facebook pixel not showing in ads manager is frustrating. The interface changes often. Meta recently moved pixels into a new category called datasets. If you look in the old pixel menu, you will find nothing. This guide shows you exactly where to click to fix the connection. We will check your account links, your user permissions, and your website code.
Connect your dataset to your ad account
This is the most common reason for a missing pixel. Meta requires you to explicitly link your data sources to your ad accounts. Creating a pixel does not automatically make it available for ads. You must tell Meta which ad account is allowed to use the data.
Go to Meta Business Settings. Look at the left menu. Find the Data Sources dropdown. Click on Datasets. Meta replaced the old Pixels menu with Datasets. If you click on Pixels, you will see a message telling you to go to Datasets.
Select your pixel from the list in the middle column. Look at the tabs across the top of the right hand column. Click the Connected Assets tab. If the list is empty, your ad account has no access to this data.
Click the Assign Assets button. A new window opens showing all your ad accounts. Check the box next to the ad account you want to use. Click Add.
Refresh your Ads Manager tab. Go back to your ad set. The pixel will now populate in the conversion setup dropdown. If you skip this step, the system physically cannot show the pixel in the ad set level.
This separation exists for security. Large companies have dozens of ad accounts and dozens of pixels. They need strict boundaries between divisions. Small businesses only have one of each, but they still have to follow the same connection rules.
Grant yourself user permissions
Sometimes the ad account has the pixel connected, but your personal user profile does not. You need explicit permission to view and manage the dataset. Meta operates on a two tier permission system. The business owns the asset, and the user needs a license to touch it.
Go back to Meta Business Settings. Click on Users in the left menu. Click on People. Find your name in the list and click it.
Look at the assigned assets on the right side of the screen. You should see a list of pages, ad accounts, and catalogs. If you do not see your pixel listed under datasets, you cannot use it.
Click the Add Assets button. Select Datasets from the left column of the popup window. Check the box next to your pixel in the middle column. Look at the right column and toggle the switch for Full Control. Click Save Changes.
This step is critical if you work in an agency or manage client accounts. The business owner must grant you these permissions. If they skip this step, you will face the issue of your facebook pixel not showing in ads manager.
If you are a freelancer, you might need to use the Partners tab instead of the People tab. The client goes to Business Settings, clicks Partners, and adds your Business Manager ID. They must then share the dataset asset with your partner ID. You then go into your own Business Settings and assign that shared dataset to your own name.
Check your website base code
Your pixel might be connected properly but failing to send data. If Meta receives no data, the pixel looks inactive. You need to confirm the code exists on your live website.
You can use a free pixel checker to scan your website URL and see exactly which pixel IDs are firing in under ten seconds. If the tool finds nothing, your base code is missing.
You or your developer must place the Meta pixel base code in the header of your website. It must load before any other tracking scripts. The code contains a function called fbq('init'). This function must run before any track calls.
If the tool finds a pixel, check the ID number. The ID on your website must exactly match the ID in your Meta Events Manager. A mismatched ID sends your traffic data to a different account. This happens often when people copy website templates or use old tag manager containers.
If you run an ecommerce store, you must also check your specific conversion events. The base code only tracks page views. You need separate event codes for adding to cart and checking out. You can read our guide on fixing a broken purchase event to sort out tracking failures at checkout.
Turn off your browser ad blockers
You might test your website and see no activity in the Meta Events Manager. This makes you think the pixel is broken. Often, the problem is your own browser.
Ad blockers stop the Meta pixel from firing. Privacy extensions stop tracking scripts by default. Browsers like Brave have built in shields that block the Meta base code.
When you visit your website with an ad blocker running, the pixel cannot send the page view event. Meta records nothing. Your Ads Manager shows no recent activity.
To confirm this is the cause, open a private browsing window with no extensions active. Visit your website. Click around a few pages.
Go back to Meta Events Manager. Look at the Test Events tab. You should see your page views appear in real time. The Test Events tab includes a View Details link for every action. Click this link to see exactly what data the browser sent to Meta.
You can also install the Meta Pixel Helper extension for Google Chrome. This tool sits in your browser toolbar. It lights up when it detects a pixel on the page. It shows you the pixel ID, the event names, and any load errors.
If you need more help with the testing tool, read our full guide on fixing the Meta pixel.
Select the right conversion objective
Ads Manager filters the available pixels based on your campaign objective. If you choose a traffic objective, Meta does not ask for a conversion pixel in the same way.
You must select the Sales or Leads objective to see the full conversion dataset options.
- Start a new campaign in Ads Manager.
- Choose Sales as your campaign objective.
- Move to the ad set level.
- Look for the Conversion location section.
- Choose Website.
- Set the Performance goal to Maximize number of conversions.
- Look at the Pixel dropdown menu.
Your connected dataset will appear here. If you select a custom event that has no recent data, Meta will show a yellow warning icon. This warning does not stop you from running the ad. It just means nobody has triggered that event recently.
You can also customise your reporting columns to show pixel data. Click the Columns dropdown in Ads Manager. Click Customise Columns. Search for your specific pixel events and add them to your report. The pixel will only appear for reporting if the ad set conversion objective is linked to that pixel event.
Check for duplicate tracking codes
Sometimes a website has two different Meta pixels installed. This causes massive confusion in Ads Manager. One pixel might be connected to your ad account, while the other belongs to an old agency.
If your website fires the wrong pixel first, Meta gets confused. You must remove all old tracking codes.
Log into your website content management system. Check your theme header file. Check your Google Tag Manager container. Check any dedicated tracking plugins.
Delete any Meta pixel code that does not match your current dataset ID. You only want one base code firing per page. Multiple base codes slow down your website and duplicate your event data.
According to tracking guides like SaveMyLeads, verifying your pixel base code is just the first step in a complete tracking setup. You have to keep your code clean.
Read the Test Events tab correctly
The Test Events tab in Events Manager is your main diagnostic tool. It shows you exactly what Meta receives from your website. If your facebook pixel not showing in ads manager is caused by a broken event, this tab reveals the error.
Open Events Manager and click on your dataset. Click the Test Events tab. Enter your website URL in the testing box and click Open Website.
Your website will open in a new tab. Click around the page. Add an item to your cart. Complete a test purchase.
Go back to the Test Events tab. You should see a list of actions appearing in chronological order. Each action has a View Details link.
Click View Details. A sidebar opens showing the raw data payload. You will see the event name, the timestamp, and the parameters.
Look for warnings highlighted in yellow or red. Meta flags events that miss required parameters. If your purchase event lacks a currency code or a value, Meta rejects it. A rejected event will not show up in Ads Manager reporting.
You must fix these parameter errors in your website code. Your developer needs to update the data layer to push the correct variables into the tracking script.
If the Test Events tab shows no activity at all, your browser is blocking the script or your base code is missing entirely. Go back to the earlier steps in this guide to fix the connection.
Verify the API and server connections
Browser tracking is no longer enough. Apple iOS updates and strict privacy settings block a large portion of standard pixel data. If your pixel relies entirely on the browser, your Ads Manager will underreport your results.
Meta recommends using the Conversions API alongside the browser pixel. This requires a server to send data directly to Meta.
Setting this up requires a developer. You cannot just click a button in Business Settings to make it work.
Your developer must configure a server side POST request to the Meta Graph API. This request must include the event name, the event time, the source URL, and a hashed user data string.
If the server payload misses the hashed user data, Meta will reject the event. The API response will show an error.
You can check your API connection in the Events Manager. Look at the data sources list. A healthy setup shows both Browser and Server as