Meta will be adding historical limitations which affect unique-count fields and hourly breakdowns, as well as removing 7-day view (7d_view) and 28-day view (28d_view) attribution windows. These changes will take effect on January 12, 2026. See Meta’s announcement of the changes.
This will impact the Facebook Ads data source Supermetrics provides, and requires that we change or sunset some of the fields and attribution windows that we support.
This article provides a comprehensive description of all updates and outlines to necessary steps to prevent potential issues.
Special note for data warehouse users
Standard table groups do not contain affected fields and by default are set to default attribution, and therefore will not be affected.
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 and attribution windows in the custom table, and they will start returning empty values after January 12.
Note that if you run a backfill after January 12 for such custom tables to fetch historical data, such as for year 2024, 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 fields or attribution windows that will lead to transfer failures after January 12. 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.
New historical limitations
From January 12, 2026, data will only be available for the previous 13 months for the following fields and breakdowns. A date range older than 13 months will return an error:
Field Name | Field ID |
|---|---|
Unique link clicks |
|
Unique outbound clicks |
|
Unique CTR (link click-through rate) |
|
Unique outbound CTR |
|
Unique clicks (all) |
|
Cost per unique link click |
|
Cost per unique outbound click |
|
Cost per unique click (all) |
|
Unique inline link clicks |
|
Hour (advert account time zone) |
|
Hour (viewer's time zone) |
|
Account timezone offset from UTC |
|
Deprecated conversion windows
The following conversion windows or attribution windows will be deprecated on January 12, 2026, and will no longer return results after that date:
28 d view
7 d view
28 d click + 28 d view
28 d click + 7 d view
7 d click + 28 d view
7 d click + 7 d view
1 d click + 28 d view
1 d click + 7 d view
7 d view first conversion
28 d view first conversion
Deprecated fields
The following fields will be deprecated on January 12, 2026, and will no longer return results after that date:
Field Name | Field ID |
|---|---|
Conversions within 7 days of view |
|
Conversion value within 7 days of view |
|
Conversions within 28 days of view |
|
Conversion value within 28 days of view |
|
We're here for you
If you have any questions or concerns about this change, contact our support team.