We are writing to inform our valued customers that the current incident is being closed. The resolution of this issue is dependent on Facebook's engineering team, specifically regarding the exposure of the creative preview in their API.
Details:
While we await Facebook's updates, we have implemented an interim solution to assist you in the meantime. We have added the following fields to your reports:
Desktop Preview URL: This field provides a clickable link to the desktop preview of your creative. Mobile Preview URL: This field provides a clickable link to the mobile preview of your creative. These new fields are currently available and can be used in your reports to access the creative previews.
Next Steps:
We will continue to monitor updates from Facebook's engineering team and will promptly inform you once the creative preview functionality is fully integrated into their API. We appreciate your patience and understanding.
Posted Jul 29, 2024 - 20:51 UTC
Monitoring
As we continue to wait on Facebook Engineering, we have added the fields “Desktop Preview URL” and “Mobile Preview URL” that can be used in reports which serve as a clickable link to the preview.”
Posted Feb 03, 2022 - 18:29 UTC
Identified
This issue is now affecting Facebook Ads mobile ad previews as well.
These previews will render fine on dashboards if you enable the "Display preview as iframe ?" option in the "Styles" section of the widget edition window.
However, they will often show an error in dashboard exports, or on dashboards directly if that option is not turned on.
We are having a global issue with Facebook Ads. The issue is that we have vendor limitations to generate Desktop Previews. When exporting to pdf, Desktop previews don't show up on several instances for several clients. This issue is happening for the Desktop Preview metric of Facebook Ads → Ads Data View. This is affecting the automated reports. This issue has been reported to Facebook via the FB developers portal but they haven't come up with a solution yet.
Several clients are being affected. If you are one of those clients, we would encourage you to comment on the Facebook ticket above, and reach out to your Facebook representative.
Since this is a Vendor bug, we will need Facebook to fix this issue and with not much of a response from their end, we are looking for different ways and channels through which we can escalate this to achieve faster resolution from the Vendor.