This article covers the limitations, considerations, and workarounds for working with Facebook Ads data in Power My Analytics. For instructions on connecting your Facebook Ads account and creating reports, see the
Facebook Ads Data Connector User Guide.
General Limitations and Considerations
As of June 2026, Meta retired the Nielsen DMA (Designated Market Area) geographic breakdown and replaced it with Comscore Markets. Power My Analytics handles this automatically: the connector requests the new breakdown from Meta and continues to deliver it under the same DMA field, so your field names, warehouse columns, and dashboards are unchanged and no action is needed. Because the underlying numeric market codes differ between the two systems, reporting that relies on the numeric market code (rather than the market name) may see different code values. For details, see
Facebook Ads: DMA Breakdown Now Uses Meta's Comscore Markets.
Removed Configuration Options
The following configuration options have been removed from the Facebook Ads connector due to changes in Meta's API:
- action_attribution_windows: This configuration option is no longer available. Attribution is now managed at the ad set level within Facebook Ads Manager.
Historical Data Limitations for Specific Fields
Due to changes in Meta's Facebook Ads API, the following fields have limitations on how far back historical data can be retrieved via API requests:
| Field |
Historical Data Limitation |
| Fields starting with unique_actions |
13 months |
| Fields starting with cost_per_unique_action_type |
13 months |
| Hour of Day - Advertiser Time Zone |
13 months |
| Frequency Value |
6 months |
These limitations apply to new API calls only. If the data has already been cached in Power My Analytics' database through previous data syncs, PMA can provide historical data beyond these limitations.
Reach Reporting Limitations
As of June 10, 2025, reports that combine the Reach metric with breakdowns will have this report data limited to the last 13 months (394 days). This is due to a change in Meta's API. Reach data will only be available for the most recent 13 months when used with the following breakdowns:
- Action Target ID
- Action types/Action type with custom labels
- Age
- Applink Treatment
- Carousel Card ID
- Carousel Card Name
- Conversion Device
- Country
- Device Platform
- DMA
- DMA Code
- Gender
- Hour of Day - Advertiser Time Zone
- Hour of Day - Audience Time Zone
- Impression Device
- Place Page ID
- Placement
- Platform Position
- Publisher Platform
- Region
- Template URL
For more information, please see Meta's 2025 API Changelog.
Unavailable Data
The following data is not available through Meta's Facebook Ads API and cannot be reported through Power My Analytics:
- Purchase breakouts by device and publisher platform
- Offsite metrics
- Conversions by country
- Breakdowns by Objective
Report Custom Events
The Facebook Ads connector automatically includes any custom events you've configured in Facebook Ads. In Data Studio, if your custom events have not appeared as available fields in your report, reconnect the Facebook Ads data source from within Data Studio. The custom events fields should appear after reconnecting.
Replicating Custom Metrics
Custom metrics can be replicated with formulas in your report:

Create Breakdowns by Objective
Breakdowns by objective are available in Facebook Ads Manager but not in the API. You can use the following workaround:
- Create a filter on your table.
- Choose Include > Campaign ID (ad sets, campaign insights, campaigns, insights) > RegExp Match.

Report Result Rate
The Result Rate field is unavailable through Meta's Facebook API, so Power My Analytics cannot report total result rate for all KPIs. However, to report result rates for individual KPIs, please see our instructions at How to Report Result Rate in Facebook Ads.
Working with Ad Image Fields
Power My Analytics offers multiple image-related fields for Facebook Ads. Understanding their differences will help you choose the right field for your reports.
The Ad Creative Image field is recommended for most use cases. This field automatically displays the highest-quality image available:
- Uses the high-resolution Ad Image URL when available
- Falls back to the Thumbnail URL when Ad Image URL is not available
- Ensures your reports display an image for each ad (for Advantage+ Catalog dynamic ads, this will be a generic placeholder image; see Carousel Images for Advantage+ Catalog Ads below)
- For boosted Facebook Page posts, may repeat the same image (your Page's profile picture) across different ads; see Repeated Images for Boosted Page Posts below
Individual Image Fields
| Field |
Quality |
Availability |
Notes |
| Ad Image URL |
High |
Not always available |
Best quality; may not render for all ad types |
| Thumbnail URL |
Low |
Most ad types |
Lower resolution. For boosted Facebook Page posts, Meta returns the Page's profile picture instead of the post image, so this field can repeat the same image across ads (see Repeated Images for Boosted Page Posts below). For Advantage+ Catalog (dynamic product) ads, returns a generic placeholder image |
| Image Asset URL |
Medium |
Dynamic Creative only |
Live data; can only be used with Impressions, Clicks, Amount Spent, and Reach |
Carousel Images for Advantage+ Catalog Ads (Dynamic Product Ads)
If every carousel ad in your report shows the same generic image, your ads are most likely Advantage+ Catalog Ads. This is expected behavior caused by a limitation in Meta’s API.
Carousel ads created as Advantage+ Catalog Ads (also known as Dynamic Product Ads) do not return their carousel card images through Meta’s Marketing API. Meta builds these ads from your product catalog at the moment each ad is shown, selecting different products for different viewers. Because the images are chosen at display time, they are never stored as part of the ad creative, and the API provides only a generic placeholder thumbnail.
As a result, image fields such as Ad Creative Image, Ad Image URL, and Thumbnail URL will display the same placeholder image for these ads. This is a limitation of Meta’s API rather than a Power My Analytics issue, and it affects all marketing data connectors. Reconnecting your Facebook Ads data source will not change this behavior. Standard image ads and static carousel ads are not affected; their image fields work normally.
Because Meta chooses which products to show each viewer at the moment of impression, there is no way to match specific product images to specific ad creatives or performance metrics through the API. However, you can still get useful insight into these ads:
- Use the Product ID dimension to report performance by individual product.
- Reference product images directly from your own product catalog feed, which is the original source of the images in these ads.
- Use the Is Dynamic Creative field to help identify dynamic ads in your reports.
If you have questions about reporting on Advantage+ Catalog Ads, please submit a ticket and our support team will be happy to help.
Repeated Images for Boosted Page Posts
If the same image (often your Page's profile picture) repeats across different boosted-post ads, this is expected behavior caused by a limitation in Meta's API. You can recover the correct per-ad images by blending in Facebook Insights data.
When you boost a Facebook Page post, Meta's Marketing API does not provide a separate image for each ad. Instead, it returns your Page's profile picture as the Thumbnail URL, and the Ad Creative Image field falls back to that same picture. As a result, many different boosted-post ads show the same image in your report, even though the Hub displays the correct images. Ads built as new creatives (rather than boosted posts) are not affected.
Switching to the Thumbnail URL field does not fix this, because for boosted posts that field is the Page's profile picture. Reconnecting the data source does not change it either. This is a limitation of Meta's Marketing API and affects all marketing data connectors, including Supermetrics, Fivetran, and Funnel.io.
The correct post image is available in the Facebook Insights connector's Posts table, in the Full Picture field. Blend it into your Facebook Ads report:
- In your Hub, make sure the relevant Page is selected as an active account in the Facebook Insights connector.
- In your Data Studio report, blend your Facebook Ads data source with the Facebook Insights Posts data source (left outer join, with Facebook Ads on the left).
- Set the join key to Effective Object Story ID (Facebook Ads) = Post ID (Facebook Insights). Both use the same {pageID}_{postID} format.
- Use Full Picture (from Facebook Insights) as your image field.
Video Ad Thumbnail Fields
For video advertisements, the following thumbnail-related fields are available:
- Video Asset Thumbnail URL — Direct URL to the video thumbnail (Dynamic Creative breakdown)
- Video Asset Thumbnail Hash — Internal identifier for the thumbnail image
Limitations:
- Video thumbnail fields are part of the Dynamic Creative asset breakdowns and can only be used with the metrics Impressions, Clicks (All), Amount Spent, and Reach
- An image will only be returned for ads that include image or video creatives; non-visual ad types will not return images
- Meta's API does not provide a dedicated field to identify specific ad formats (Reels, Standard, Videos, etc.)
Troubleshooting
Follow the instructions in Troubleshooting Facebook Ads for information on issues that may affect the Facebook Ads connector.