Appearance
Fresh 2026
Version 25.0
Graph API
Released February 18, 2026 | Available until TBD | Blog post
Insights
Will apply to all versions when v26.0 is released.
When v26.0 is released later this year, page reach, page post reach, video impressions, and story impressions metrics listed below will be deprecated. Once deprecated, these metrics will return an error if requested using any API version.
Alternative metrics are listed in parenthesis. If a metric has no alternative, data that the metric would normally return will no longer be available upon deprecation.
Page Insights API
Removing the following Page Insights API metrics:
page_impressions_unique(usepage_total_media_view_uniqueto get total unique views on a page's media, andpage_media_viewto get breakdowns between paid and organic reach on a page's media)page_impressions_paid_uniquepage_impressions_viral_uniquepage_impressions_nonviral_uniquepage_posts_impressionspage_posts_impressions_uniquepage_posts_impressions_paidpage_posts_impressions_paid_uniquepage_posts_impressions_organic_uniquepage_posts_served_impressions_organic_uniquepage_posts_impressions_viralpage_posts_impressions_viral_uniquepage_posts_impressions_nonviralpage_posts_impressions_nonviral_uniquepage_video_views_unique
Post Insights API
Removing the following Post Insights API metrics:
post_impressions_unique(usepost_total_media_view_uniqueto get total unique views on a page post media, andpost_media_viewto get breakdowns between paid and organic reach on a page post's media)post_impressions_paid_uniquepost_impressions_fan_uniquepost_impressions_organic_uniquepost_impressions_viral_uniquepost_impressions_nonviral_uniquepost_impressions_nonviral_uniquepost_video_views_organic_uniquepost_video_views_paid_uniquepost_video_views_unique
Video Insights API
Removing the following Video Insights API metrics:
post_impressions_uniquetotal_video_impressionstotal_video_impressions_uniquetotal_video_impressions_paid_uniquetotal_video_impressions_paidtotal_video_impressions_organic_uniquetotal_video_impressions_organictotal_video_impressions_viral_uniquetotal_video_impressions_viraltotal_video_impressions_fan_uniquetotal_video_impressions_fantotal_video_impressions_fan_paid_uniquetotal_video_impressions_fan_paidtotal_video_views_organic_uniquetotal_video_views_paid_uniquetotal_video_views_unique
Stories Insights API
Removing the following Stories Insights API metrics:
PAGE_STORY_IMPRESSIONS_BY_STORY_ID(useSTORY_MEDIA_VIEWto get breakdowns between paid and organic reach on a story's media)PAGE_STORY_IMPRESSIONS_BY_STORY_ID_UNIQUE(useSTORY_TOTAL_MEDIA_VIEW_UNIQUEto get total unique views on a story's media)
Node metadata
Applies to v25.0+. Will apply to all versions May 19, 2026.
The metadata query parameter (metadata=1) is deprecated and will no longer return metadata about supported fields for the targeted node. Use the Graph API Explorer or API references instead.
Webhooks mTLS
The current Webhooks mTLS certificate is signed by the DigiCert root CA. Because DigiCert is deprecating the use of the Client Authentication EKU, the certificate cannot be renewed when the root CA expires on April 15, 2025.
Consequently, starting March 31, 2026, Meta will sign a new Webhooks mTLS certificate using a different Certificate Authority (CA), owned by Meta. It will maintain the same common name (client.webhooks.fbclientcerts.com) as the current certificate.
If your servers are configured to require and verify the Webhooks mTLS certificate, you must trust the new Meta CA. Failure to update your trust store by March 31, 2026, will result in TLS handshake failures, and your servers will stop receiving all webhooks events.
To ensure a seamless transition, download the new meta-outbound-api-ca-2025-12.pem root certificate and add it to your trust store as soon as possible. You can do this while the current certificate is active. Do not wait until the deadline, or you risk an interruption to webhook receipt and delivery.
Marketing API
February 18, 2026 | Available until TBD | Blog post
Advantage+ Campaigns
Advantage+ Shopping Campaigns and Advantage+ App Campaigns deprecation
Applies to v25.0+. Will apply to all versions May 19, 2026.
Creation, duplication, and updates to Advantage+ shopping campaigns and Advantage+ app campaigns is no longer allowed.
Refer to the Advantage+ Campaigns documentation to learn how to migrate your campaigns to Advantage+ campaigns or continue to create new campaigns using the Advantage+ structure.
The following endpoints are affected:
POST /{ad-account-id}/campaignsPOST /{campaign-id}/copies
Insights
Asynchronous Jobs
Applies to v25.0+.
The following new default fields will be returned when an asynchronous ad report fails:
error_code: The error codeerror_message: A message corresponding to theerror_codeerror_subcode: The specific subcode for the errorerror_user_title: A user-friendly title for the error subcodeerror_user_msg: A user-friendly message detailing the error subcode
For any developers with access to the error_code field, the type will be changed from uint to int.
See Insights API Asynchronous Jobs and Ads Insights API Error Codes for more information.
The following endpoints are affected:
GET /{ad-report-run-id}
``
``