Facebook Dynamic Product Ads track individual users’ behavior to create custom ad experiences. It is literally automating efforts to handle the difficult parts of setup and optimization.
Advertizers may use Dynamic Facebook Ads for non-eCommerce campaigns as well. As long as they have a properly prepared “product” feed they can use these dynamic campaigns for any kind of strategy. Facebook Dynamic Product Ads may yield really fantastic results at a low cost.
Although advertising with Facebook is often easy, things might get tricky. It can be frustrating to discover how much trial, errors and learning are involved.
e-Retailers all know the irritation that comes with having feed rejected by Facebook. It slows down your sales efforts and creates problems with your workflow.
The good news is we know what are the most common feed errors. We decided to give you a sneak peek into how to avoid and troubleshoot those issues.
Give yourself a minute and check our round-up of the most often feed mistakes in Facebook Dynamic Product Ads. Acknowledge how to fix them and bring excellent results into your campaigns.
Common Feed Errors
Image size too small
One of the last things you want is for your product ad to appear pixelated or sloppy. While having a smaller image might not completely disqualify your items, it will affect your feed’s performance and it won’t look good in the ads.
Each channel has its own strict product image sizes and requirements. That makes easy for errors to occur.
It’s important to note that Facebook’s recommended resolution for all images is 600x600 pixels. Any smaller than that and your image starts to look bad.
How to overcome this issue:
→ first, double-check both the channel requirements and recommendations
→ In your mapping section make sure you have selected the biggest image from the source possible.
PRO TIP for Shopify users
→ sometimes, even though you may choose image_large_1 from your Shopify source, this warning might still occur (!)
To prevent this make sure to use your biggest image possible and apply this hack:
Missing required fields: Property missing
Facebook has both - required and optional data fields. Make sure they are all mapped correctly. And before starting mapping remember to prepare data accordingly.
How to overcome this issue:
Follow the rules listed below and you will surely map all the columns in a proper and valid way.
→ remember to add the correct image links in the image_link column.
→ Make sure links begin with http:// or https://.
→ Make sure that links are correct and aren't broken.
Most catalog types require product IDs, but the column name varies depending on the kind of inventory you have. You determine your item IDs, and they won't show up in your ads.
→ enter item IDs in the correct column on your feed
→ don't use capital letters to differentiate between product IDs.
→ use SKUs as your product IDs if you can.
→ use a different product ID for each item.
→ include prices in the price column.
→ format prices correctly. Use a 3-digit ISO currency code such as USD or EUR
→ Make sure the prices are accurate and match the prices on your website.
→ Don't include shipping or other additional fees in the price.
→ Don't use auction prices or fluctuating prices.
Every item in the catalog must include a link to a website landing page that people can click on to learn more about the product.
→ add the correct links in the link column.
→ make sure that links begin with http:// or https://.
→ make sure that links are correct and aren't broken
→ link to pages that are optimized for mobile.
→ descriptions must be under 5,000 characters.
→ provide accurate information in the description column.
→ Don't enter links in the description column.
→ Descriptions can't be in all capital letters.
→ limit names and titles to 150 characters.
→ provide a name or title that's relevant and specific to each item.
→ include keywords such as brand names, product areas or attributes.
→ avoid all capital letters.
→ include the condition in product titles whenever you can.
→ proofread names and titles for spelling and grammar.
→ keep track of stock levels
→ Regularly update the availability column
→ filter out the unavailable products
Wrong GTIN codes: Property GTIN is incorrectly formated
A GTIN code (Global Trade Item Number) is a unique bar code that identifies your product.
The code will vary in the following countries:
- In North America it’s commonly known as a UPC number and has 12-digits
- In Europe it’s commonly known as an EAN number and has 13 digits
- In Japan it’s commonly known as a JAN number and has either 8 or 13 digits
- An ISBN code is reserved for books and has 13 digits
It’s very important to have the correct codes mapped in your feed so spend a little extra time when setting up your feed and make sure you have the correct codes matched to all your products.
The only time you won’t be required to add a GTIN code is if your feed includes custom-made products.
How to avoid the error?
→ If your products are missing GTIN codes, your feed will also be rejected.
→ The quickest way to check this is to download your feed in a csv file and do a quick
→ If you can't find the GTIN, you can always contact the product's manufacturer to ask for it.
→ If you’d like more information on GTIN codes, read our blog post: Finding GTIN’s for your products
Sometimes it may seem challenging when utilizing values to optimize your feeds. But if you apply incorrect values, your feed won’t make any sense and it will get rejected.
A common mistake many e-retailers make when mapping their feeds is to list custom labels individually as opposed to having them grouped together.
For example, all price variations should be grouped in 1 custom label, while promotional items should all be grouped in another.
How to fix the issue?
You may have several different price ranges, but you will group them all into 1 custom label by creating rules that separate them from one another
DataFeedWatch offers 11 ways (besides regular expressions) that you can use to edit and optimize your data feeds, as shown in the image below:
An error that we have picked up time and time again in Facebook feeds is the missing currency.
While Google accepts feeds with or without the price currency, Facebook insists on it so you need to remember to include this.
For example, instead of 15.00, you need to specify 15.00 USD. With our nifty DataFeedWatch tool, you can add your currency as your suffix in your field mapping area’
Facebook also offers a valuable Product Feed Debug Tool that allows you to paste your feed up and get it validated for errors and warnings.
Missing Google categories
What on earth do the Google categories have to do with Facebook anyway, you may ask?
Well, Facebook uses Google taxonomy to categorize items, and although this field is optional in Datafeedwatch, if not mapped it will give you warnings in the Business Facebook account.
How to avoid this error?
Fact is, it’s always good to categorize your items properly to increase their visibility. If your own feed is already mapped to Google’s categories, simply connect your input field google_product_category to the optional output feed google_product_category that you will create.
However, if you have already mapped all your Google sub-categories in your Google feed, you can save yourself a lot of time by utilizing the “Copy From” functionality in DataFeedWatch to copy it across to your Facebook feed.
If you still have to map all categories from scratch and your input field doesn’t contain this, then you can simply connect easily with our Google pre-mapped sub-sub-categories, as follows:
Facebook’s Dynamic Product Ads are huge and full of potential. We hope that with provided troubleshooters on the most common error you will no longer struglle when running DPA .
All tips are based on our own experience. So we asure that by paying attention to these common errors and applying the solutions, your feeds will not be rejected again.
Don’t waste any downtime while trying to figure out what the problem is with your feed and why Facebook is rejecting it.