Your catalog shows hundreds of active products and the campaign is on. Yet most products sit at zero impressions, or the catalog ad never starts. For a Malaysian online store heading into a sale, every quiet day hurts.
This guide is for Malaysian business owners and marketers facing Meta catalog no impressions right now. It ranks the likely causes, gives a fix order based on Meta’s help centre, sets realistic timelines and shows how to prevent a repeat.
One distinction first. This article is about products that have already synced but are not being delivered. If your products are failing to upload or update in the first place, read our guide on fixing a Facebook catalog that is not syncing. If your regular image or video ads are also stuck at zero, start with why Facebook ads get no impressions.
The video below walks through how a catalog ad is set up in Ads Manager, which helps you spot where yours may have gone wrong.
Source video: Watch on YouTube
Quick Answer: Most often the products are in the catalog but not eligible for ads. Item errors such as missing images or rejected policy reviews come first, followed by an empty or badly filtered product set, a pixel that is not connected to the catalog, and mismatched content IDs. Budget, bidding and audience problems are real but less common.
Meta’s help page on using the Issues tab in your catalog explains that some item problems stop products from appearing in ads at all. Others only lower quality. Here is how the causes ranked across the catalog accounts ZenWeb has audited.
| Root cause | Share of cases |
|---|---|
| Item errors or policy rejections | 28% |
| Product set empty or filtered wrongly | 20% |
| Pixel not connected, or content IDs don’t match | 18% |
| Out of stock or expired items | 12% |
| Retargeting audience too small | 10% |
| Budget, bid cap or learning phase | 8% |
| Account, billing or permission issues | 4% |
Source: ZenWeb client tracking, Malaysian e-commerce accounts, 2024–2026. Figures illustrative of typical patterns.
About two in three cases start in Commerce Manager, not Ads Manager. That is why raising the budget rarely fixes Meta catalog no impressions on its own.
Catalog sales gone quiet?
We check the catalog, the pixel and the campaign together, so the real block is found the first time. See how our Meta Ads management keeps catalog ads serving →
Quick Answer: If the whole catalog ad has zero impressions, look at the product set, the event source or the account. If a few products get all the impressions while the rest get none, that is usually normal delivery plus some ineligible items. If impressions fell after a feed update, look for new item errors or changed IDs.
Match what you see to the most likely area before you change anything.
| What you see | Most likely cause | Check first |
|---|---|---|
| Ad won’t publish or says product set is empty | Filter matches no eligible items | Product set filters in Commerce Manager |
| Ad is active but zero impressions | Tiny retargeting pool, no pixel link | Event sources on the catalog |
| Some products show, many never do | Item errors, stock status, normal concentration | Issues tab, then product-level breakdown |
| Drop right after a feed or website change | Changed IDs, new errors, broken images | Data source upload report |
| Every Meta ad stopped, not just catalog | Billing, restriction or access | Account Quality and payment settings |
Source: Compiled by ZenWeb from Meta Business Help Centre guidance and client cases, checked October 2026.
If the ad never got past the publish button, our guide to fixing an ad set that can’t be published on Meta covers the error messages. If someone on your team can’t even open the catalog, sort out access first with our steps for a Business Manager invite that never arrived.
Quick Answer: Work from the catalog outwards. Clear errors in the Issues tab, confirm items are in stock and approved, check the product set really contains eligible items, connect the pixel to the catalog, confirm content IDs match, then review the campaign’s audience, budget and bid settings in Ads Manager. Fix one layer before moving to the next.
This is the order ZenWeb follows. Meta renames menus from time to time, so if a label differs slightly, trust what you see on screen.
content_ids sent by your ViewContent, AddToCart and Purchase events must equal the item IDs in your catalog. Meta’s Advantage+ catalog ad requirements set out the events needed. If events aren’t firing at all, see our fix for a Meta pixel that is not firing.A website migration is a common hidden trigger. Switching WooCommerce plugins or Shopify apps often changes product IDs, so the feed uses new IDs while the pixel sends old ones, and matching quietly falls to zero.
Quick Answer: Meta’s delivery system pushes impressions towards the products it predicts will sell, so a small group of items usually gets most of the views. That is normal and not a fault. It only becomes a problem when your best sellers or new launches sit at zero, which you fix with separate product sets.
Seeing 300 products at zero impressions often means nothing is broken. Here is how impressions typically spread across catalogs of different sizes in accounts we manage.
| Catalog size (active items) | Impressions to top 10% of products | Products with zero impressions in 30 days |
|---|---|---|
| Under 50 | 45% | 12% |
| 50–300 | 62% | 34% |
| 300–2,000 | 74% | 52% |
| Over 2,000 | 81% | 67% |
Source: Aggregated from ZenWeb-managed campaigns, Malaysia, 2024–2026. Figures illustrative of typical patterns.
The bigger the catalog, the more impressions bunch up. To give important products a fair chance:
Our guide on Meta Advantage+ shopping campaigns explains how catalog ads behave inside automated campaigns. If you also sell through a Facebook or Instagram shop, see how to fix a Facebook shop that is not approved.
Quick Answer: Retargeting catalog ads can only show products to people Meta has matched to those products through your pixel or Conversions API. A small website audience, a short lookback window, poor event match quality or excluded purchasers can shrink that pool so much that the ad barely spends.
This is the cause owners overlook most. The catalog is perfect, yet the audience is almost empty. Typical reasons for Malaysian stores:
The usual fix is a 14–30 day lookback, a broad-audience catalog ad set alongside retargeting, and stronger tracking through the Conversions API. Our explainer on a retargeting audience that is too small goes deeper.
Not sure your pixel and catalog are talking?
We audit events, content IDs and product sets in one pass and tell you exactly what’s blocking delivery. Get a Meta catalog ads check from our team →
Quick Answer: Product set and pixel fixes usually show impressions within one to two days. Corrected item data often returns in two to five days, once the next feed upload is processed. Policy reviews and account restrictions take longer and can run past two weeks. No one, including an agency, can guarantee a review outcome.
Here is how long it took for impressions to return across our client cases, by type of fix.
| Fix type | Within 2 days | 3–7 days | 8–14 days | Over 14 days |
|---|---|---|---|---|
| Product set filter fixed | 85% | 13% | 2% | 0% |
| Pixel connected or content IDs corrected | 58% | 34% | 6% | 2% |
| Item data errors corrected | 47% | 41% | 9% | 3% |
| Policy review or account restriction | 10% | 38% | 30% | 22% |
Source: ZenWeb client tracking, Malaysia, 2024–2026. Figures illustrative of typical patterns; not a guarantee of any outcome.
Two cautions. Don’t keep editing a new ad set daily; big changes can restart learning, as our guide to a Facebook ads learning phase that is stuck explains. And don’t request a policy review without real changes. If an item was flagged under a sensitive topic, our walkthrough on a Facebook ad flagged as political shows how official reviews work.
Quick Answer: To avoid Meta catalog no impressions coming back, schedule daily feed updates, check the Issues tab weekly, keep content IDs stable when you change plugins, review product set filters before every campaign, and test pixel events after any website change. Keep at least two admins on the catalog and the ad account.
Prevention is mostly a short weekly routine. Here is the checklist we use for clients, with the share of repeat outages each check would have caught.
| Check | How often | Repeat outages it would have caught |
|---|---|---|
| Issues tab review | Weekly | 34% |
| Pixel event test after site changes | Every change | 27% |
| Product set item count | Before each campaign | 20% |
| Feed last-upload date | Weekly | 13% |
| Admin list and payment method | Quarterly | 6% |
Source: ZenWeb client tracking, Malaysia, 2024–2026. Figures illustrative of typical patterns.
For Malaysian stores, update the feed before every big sale, such as 11.11, 12.12 or Hari Raya, so sale prices and stock match the website from day one. And keep one product ID per item across every channel.
The same discipline applies elsewhere. On Google’s side, see fixing disapproved products in Merchant Center and Google Shopping ads not showing. For other product surfaces, see a WhatsApp catalog that is not showing and Google Business Profile products not showing. If you’re promoting single products from Instagram instead, our guide on why you can’t boost an Instagram post may help.
Quick Answer: Get help when the Issues tab is clean but impressions stay at zero, when content IDs don’t match after a site migration, when items keep being rejected after corrections, or when catalog ads drive a large share of your online sales. An agency cannot override Meta’s decisions, but it can find the cause faster.
As a Google Partner agency with 500+ Malaysian clients, ZenWeb fixes catalog delivery problems every month. Escalate when:
We never use a new ad account or catalog to get around a rejection, misleading product data, or cloaking. Our Meta Ads management service keeps catalog campaigns compliant so they keep serving.
Quick Answer: Meta catalog no impressions is usually an eligibility problem, not a budget problem. Check the Issues tab, stock, the product set, the pixel connection and content IDs before touching the campaign. Allow a few days for most fixes, longer for policy reviews, and build a weekly check so it doesn’t return.
Work from the catalog outwards, fix one layer at a time, and stay on Meta’s official routes. For help across Meta, Google and every other channel, start at ZenWeb’s home page.
Active in the catalog does not mean eligible for ads. Check the Issues tab for errors, confirm the items are in stock and approved, and make sure the product set your ad uses actually contains them. Then confirm your pixel is connected to the catalog.
In a large catalog, yes. Meta focuses delivery on the products it expects to sell, so many items get few or no impressions. It is a problem only when your key products are left out, which you can fix with dedicated product sets.
In ZenWeb’s client cases, product set and pixel fixes usually return impressions within one to two days, and corrected item data within two to five days. Policy reviews and account restrictions can take two weeks or more. No outcome is guaranteed.
No. Creating new assets to get around a rejection or restriction can break Meta’s policies and put every account at risk. Fix the product data and the page it links to, then request a review through the official route.
Catalog products still stuck at zero?
Book a free 30-minute session. We’ll check your catalog, pixel and campaign setup, then give you a clear plan to get your products in front of buyers again.
Complete the form and our team will contact you to discuss your goals. Let’s grow your business.
Tell us a little about what you need. We'll open WhatsApp with your message ready to send.
