As part of the work to align the funtionality of the Facebook Page Insights API with that of the Facebook app and Meta Business Suite, Meta will again be deprecating a number of metrics, primarily unique impression and 3-second video view-related metrics. See also Meta’s announcement of the changes.
This will impact the Facebook Insights data source by Supermetrics and requires that we sunset or change some of the fields we support based on these upcoming deprecations.
This article contains a full description of all the updates and what you need to do to prevent any possible issues.
Some fields have been replaced, this article details the replacement fields where applicable.
Special note for data warehouse users
As the changes are affecting what we consider to be core fields, we’ll be updating the standard table group for this data source. The STANDARD table group will be renamed as STANDARD_ARCHIVE_20260630 on June 30, 2026. All transfers using the standard table group will continue to work as the renamed version, but please note that any deprecated fields from this round of changes or previous ones will return empty values. Backfilling data after the sunset date will also overwrite data with empty values and should be avoided. We’ll then make available a new standard table group that replaces the deprecated fields with their new versions. New transfers created after June 30, 2026 will use the new standard table group instead.
Keep in mind that removing fields from your custom tables can lead to that field being removed from your tables in the data warehouse, in particular, if you're using our BigQuery, Snowflake, Azure Synapse, Azure SQL DB, or AlloyDB integrations listed in your storage destinations on the Supermetrics Hub.
For other destinations, such as our direct BigQuery integration on Google Cloud, AWS S3, Google Cloud Storage, Azure Storage, and SFTP, only shards and files are overwritten for the dates you're backfilling and transferring daily within your refresh window.
If you want to preserve the historical data of those fields in your destination, you have two options:
Keep the affected fields in the custom table, and they will start returning empty values after June 30, 2026. If there are replacement fields available, you can add them to the custom table and continue using your custom table as before in your reports.
Note that if you run a backfill after June 30, 2026 for such custom tables to fetch historical data, such as for year 2025, this might also overwrite your historical data for the affected fields with empty values.
Rename your custom tables in the Table Manager and make the necessary changes to the custom table according to the information in this article in case your custom table contains combinations of fields that will lead to transfer failures after June 30, 2026. Renaming custom tables in the Table Manager will lead to new tables or files being generated in your destination.
If any of your reporting is dependent on the affected custom tables, you'll either need to point the reports to the new tables, or combine the data of the new tables with the tables that contain your historical data (using SQL, ETL tool, or by combining the data inside a BI tool), so that your reports contain both the historical and the latest data.
Note that you need to rename the custom tables, not the table group. Renaming the table group won't have any impact on the transfer, and this scenario would lead to you losing data for the fields you removed or replaced in your custom tables.
Deprecated fields with replacements
The following fields will be deprecated on June 30, 2026, and will no longer return results. We recommend you update your queries to use the replacements to continue to get data.
Field name - Field ID | Replacement | Notes |
|---|---|---|
Total reach - | Page media views - | This metric cannot be used when splitting by post-level dimensions. For this use |
Post reach (Total reach + a post dimension) | Post views unique - | |
Unique view views - | Page media views unique - | This metric cannot be used when splitting by postel-level dimensions. For this use |
Unique video views (Unique video views + a post dimension) | Post views unique - |
The replacement fields were already added in late April 2026 and are ready to use now.
Deprecated fields with no replacements
Thw following fields will be deprecated on June 30, 2026 and will no longer results after that date.
Field name | Field ID | Notes |
|---|---|---|
Total reach (28 day) |
| Data warehouse only, older table groups may have this still |
Total reach (7 day) |
| |
% of reach from paid |
|
|
% of reach from viral |
|
|
% of reach from non-viral |
|
|
Viral reach amplification % |
|
|
Non-viral reach amplification % |
|
|
Paid reach |
|
|
Post paid reach |
| This is “Paid reach” + a post dimension |
Viral reach |
|
|
Post viral reach |
| This is “Viral reach” + a post dimension |
Non-viral reach |
|
|
Post non-viral reach |
| This is “Non-viral reach” + a post dimension |
Total impressions of posts |
|
|
Total reach of posts |
|
|
Paid impressions of posts |
|
|
Paid reach of posts |
|
|
Viral impressions of posts |
|
|
Viral reach of posts |
|
|
Non-viral impressions of posts |
|
|
Non-viral reach of post |
|
|
Unique video views |
|
|
Unique video views |
|
|
Unique video views |
| This is “Unique video views” + a post dimension or video dimension |
Unique watch 30s rate |
|
|
Unique watch 30s rate |
|
|
Unique watch 30s rate |
| This is “Unique video watch rate” + a post dimension or video dimension |
Reels reach |
|
|
% of reach from organic |
|
|
Post reach (page likers [fans] only) |
|
|
Post organic reach |
|
|
We’re here for you
If you have any questions or concerns about this change, contact our support team.