If you experience any issues after creating a UGC DPA feed in your Flowbox account, this guide helps you troubleshoot the most common problems that you may encounter.
Ideally, your generated UGC DPA feed has a 'Ready' status, with correct product coverage, and a valid feed URL under the 'Copy link' button.
The product coverage may be 100% or less depending on the settings of your UGC DPA feed and the number of collected posts that have products assigned to them.
When something fails during the generation of the UCG DPA feed, you may see one of the following error messages:
'Warning' status - Information missing
"Some of the products listed in the product feed file could not be imported due to missing information in their fields. Review the generated catalog and amend as required."
This error means that the UGC DPA link was generated successfully, but the original product feed URL that you provided for the UGC DPA feed as a base has some information missing.
You can still use the generated UGC DPA field when it has a 'Warning' status, but it may not work as expected because of the errors.
Please review this guide about product feeds to make sure that every required field is correct in your original product feed for each product.
'Failed' status - Product feed file not available
"The product feed file is not available. Contact your company’s technical team."
This error means that the UGC DPA feed was not generated because the original product feed URL that you provided for the UGC DPA feed as a base is not available.
Flowbox shows this error when our server is unable to fetch the file you provided or gets a bad response when fetching your file.
It may be for several reasons:
Your product feed URL is password-protected and you entered incorrect credentials when setting up the UGC DPA feed generation in Flowbox. Try to fill in the credentials again and check if it resolves the issue.
Your original product feed URL has changed or been removed. Check with your technical team the correct URL of the original product feed and make sure you use an available URL.
'Failed' status - Invalid file format
"The product feed file format is not compatible. Please amend the file format as per our requirements."
This error means that the UGC DPA feed was not generated because the original product feed URL that you provided for the UGC DPA feed as a base has an invalid file format.
Make sure that the original product feed is in XML or CSV format.
Please review this guide about product feeds to make sure that every field is correct in your original product feed.
'Failed' status - No catalog found
"Please import a product catalog in Visual Marketing."
This error means that you don't have any catalog imported in Flowbox. It is necessary to have a product catalog configured because when creating the UGC DPA feed, Flowbox needs to relate post images with product IDs.
Please review the 'Visual Marketing' > 'Catalog' menu and check if you have correctly set up your product catalog.
'Failed' status - Fields missing
"The product feed for this catalog is missing one or more of the required fields. Please amend the file."
This error means that the UGC DPA link was not generated, because the original product feed URL that you provided for the UGC DPA feed as a base has some required fields missing in all products. In other words, Flowbox was unable to parse all 'items' from your original product feed.
Please review this guide about product feeds to make sure that every required field is correct and available in your original product feed.
'Failed' status - Export failed
"An error occurred while generating the catalog export. Please contact CSM to create a technical support request."
This error means that the UGC DPA link was not generated because of an internal error in Flowbox.
Please contact your Customer Success Manager (CSM) to inform the Flowbox technical support team of the issue.
'Ready' status - But problems creating the DPA feed in Facebook
If you encounter issues while implementing UGC DPA in Facebook, we recommend you to check Facebook's official documentation where you may find the reason of your error:
Further details: Meta for Developers Reference - Catalog