Feed errors can derail your entire catalog advertising strategy. Products get rejected, campaigns stop delivering, and ROAS suffers— often before you even notice there's a problem.
This guide covers the most common catalog feed errors and how to diagnose and fix them quickly.
Understanding Feed Error Types
Meta classifies feed issues into different severity levels. Understanding these helps you prioritize your troubleshooting efforts.
Error Severity Levels
- Errors: Products rejected, won't show in ads. Fix immediately.
- Warnings: Products may show but with limited effectiveness. Address soon.
- Suggestions: Optimization opportunities. Address when possible.
Where to Find Feed Errors
- Commerce Manager and Diagnostics tab
- Catalog and Issues section
- Data Source upload history
- Event Manager for pixel-related issues
Required Field Errors
Missing required fields are the most common cause of product rejections. These must be present for every product.
Missing ID
- Error: "ID is required"
- Cause: Product has no unique identifier
- Fix: Ensure every product has unique id field
- Prevention: Validate feed before upload
Missing Title
- Error: "Title is required"
- Cause: Product missing title field
- Fix: Add descriptive title for all products
- Prevention: Include title in feed generation logic
Missing Image Link
Images are essential for catalog ads. For ecommerce creative best practices, quality images drive performance.
- Error: "Image link is required"
- Cause: No image_link field or empty value
- Fix: Add valid image URL for every product
- Prevention: Validate image URLs exist before upload
Format and Validation Errors
Invalid Price Format
- Error: "Price format is invalid"
- Cause: Missing currency code, wrong format
- Correct format: "29.99 USD" or with currency column
- Fix: Include ISO currency code with price value
Invalid Availability
- Error: "Availability value not recognized"
- Cause: Using non-standard availability values
- Valid values: in stock, out of stock, preorder, available for order, discontinued
- Fix: Map your availability values to Meta's accepted values
Invalid Condition
- Error: "Condition value not recognized"
- Cause: Using non-standard condition values
- Valid values: new, refurbished, used
- Fix: Use only accepted condition values
URL and Link Errors
Broken Product URLs
- Error: "Product link returns error"
- Cause: 404 errors, redirects, unreachable URLs
- Fix: Verify all product URLs resolve correctly
- Prevention: Implement URL validation in feed generation
Broken Image URLs
Image issues prevent products from displaying. For scaling catalog operations, image management is critical.
- Error: "Image could not be fetched"
- Cause: Image URL returns error or times out
- Fix: Test image URLs are accessible
- Check: CDN issues, authentication requirements, rate limiting
HTTP vs HTTPS
- Warning: "Insecure image link"
- Cause: Using HTTP instead of HTTPS
- Fix: Update all URLs to HTTPS
- Note: Meta may still fetch HTTP but prefers secure URLs
Image Specification Errors
Image Too Small
- Error: "Image does not meet minimum size"
- Requirement: Minimum 500x500 pixels
- Fix: Replace with larger image files
- Recommendation: Use 1024x1024 or larger
Invalid Image Format
- Error: "Image format not supported"
- Supported: JPG, PNG, GIF (static)
- Fix: Convert images to supported formats
- Note: WebP and AVIF not currently supported
Data Mismatch Errors
Price Mismatch
- Error: "Price in feed doesn't match landing page"
- Cause: Feed price differs from website price
- Fix: Sync feed with current website pricing
- Prevention: Implement real-time or frequent price updates
Availability Mismatch
- Error: "Availability doesn't match landing page"
- Cause: Feed shows in stock but page shows out of stock
- Fix: Update availability more frequently
- Prevention: Hourly or real-time inventory sync
Feed Processing Errors
Feed Upload Failed
- Error: "Could not fetch feed"
- Causes: Server timeout, authentication failure, network issues
- Fix: Check feed URL accessibility, server health
- Test: Manually fetch feed URL to verify
Malformed Feed File
For automated feed generation, proper formatting is essential.
- Error: "Feed parsing error"
- Causes: Invalid XML/CSV structure, encoding issues
- Fix: Validate feed structure before upload
- Tools: XML validators, CSV lint tools
Pixel-Catalog Matching Errors
Content ID Mismatch
- Error: "Pixel content_ids don't match catalog"
- Cause: Product IDs in pixel events don't match catalog IDs
- Fix: Ensure pixel fires with exact matching IDs
- Check: Leading zeros, case sensitivity, SKU vs product ID
Low Match Rate
- Warning: "Low event match quality"
- Cause: Many pixel events not matching catalog products
- Fix: Audit ID matching between pixel and feed
- Target: 90%+ match rate for optimal performance
Prevention Strategies
Feed Validation Before Upload
- Validate required fields are present
- Check URL accessibility for products and images
- Verify price and availability formatting
- Test image specifications
Monitoring and Alerts
- Set up Commerce Manager notifications
- Check diagnostics after each feed refresh
- Monitor product rejection counts
- Track catalog health score over time
How ROASPIG Helps
Troubleshooting feed errors across large catalogs requires automation. ROASPIG streamlines the process:
- Pre-Upload Validation: Catch errors before they reach Meta
- Real-Time Monitoring: Instant alerts when errors occur
- Automated Fixes: Common issues resolved automatically
- Historical Tracking: Monitor error trends over time
- Bulk Remediation: Fix multiple products with single actions
Conclusion
Feed errors are inevitable, but their impact doesn't have to be. With proper monitoring, quick diagnosis, and systematic prevention, you can maintain a healthy catalog that maximizes your advertising potential.
Establish a regular cadence for reviewing feed diagnostics—daily during high-volume periods, weekly at minimum. Address errors immediately, warnings within 24-48 hours, and suggestions during regular optimization cycles.
Frequently Asked Questions About Catalog Feed Errors
Navigate to Commerce Manager, select your catalog, and check the Diagnostics tab. You'll see errors, warnings, and suggestions organized by severity with affected product counts.
Check for subtle issues: invisible characters, encoding problems, trailing spaces in fields, or format inconsistencies. Use feed validation tools to identify hidden issues.
After fixing and re-uploading, allow 24-48 hours for Meta to reprocess your catalog. Products may start appearing sooner, but full reprocessing takes time.
Common causes include using SKU instead of product ID, case sensitivity differences, leading zeros being stripped, or variant IDs vs. parent product IDs. Audit both systems to ensure exact matching.
Fix errors first as they prevent products from showing. Then address warnings, which impact performance and optimization. Suggestions are optional but can improve results when implemented.