As part of the version update to Graph API v21, Meta is deprecating some metrics for Instagram. See also Meta's announcement of the changes.
Note this was originally scheduled for December 11th, but due to unforeseen issues, we need to reschedule this change to early January.
Note for data warehouse users
Due to the changes, we'll be updating the standard table group for this data to source. The STANDARD table group is renamed STANDARD_ARCHIVE_20250108 on January 8, 2025. All existing transfers using the standard table group will continue to reference the renamed version, but please note that the deprecated fields in this update will break the table group ACCOUNT and it will fail with an incompatibility error. Backfilling data after the sunset date will also overwrite data with empty values and should be avoided.
We highly recommend you either edit your custom table grouping to remove the deprecated fields, or switch as soon as possible to the new standard table group when it becomes available on January 8.
We'll then make available a new standard table group that removes the deprecated fields, as well as other improvements, optimizations, and new functionality. New transfers created after January 8, 2024 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, Redshift, or AlloyDB integrations listed in your storage destinations on the Supermetrics Hub.
For other destinations, such as the 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 will need to:
- 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 January 8, 2024. 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
The following fields will be deprecated from the Instagram Insights data source in January 8 2025 , and will no longer return results after that date. Including these fields in queries with certain other fields will break the query, so we recommend you remove the fields to prevent errors and issues.
- Video views
- Profile views
- Email contacts
- Phone call clicks
- Text message clicks
- Get directions clicks
- Website clicks
Please be aware that due to logic in the data source, including either/both the "Profile followers" and "Profile follows" metrics from the Account lifetime field group and the deprecated fields from the Account insights field group will cause incompatibility errors after January 8. You need to either remove the deprecated fields OR remove the Account lifetime group metrics from the query/transfer to fix the error.
There is currently no exact replacement field for the "Video views" metric. The "Reels plays" metric is the next closest metric, though we understand that it's not exactly the same thing. We'll update the data source as soon as Meta makes a replacement field available.
We’re here for you
If you have any questions or concerns about this change, contact our support team.
