As part of the work to migrate to Graph API v22, we will be making changes in support of the new Views metric for Instagram. This includes adding the Views metric itself and deprecating other fields that will no longer be supported. See also Meta's announcement of the changes.
This will impact the Supermetrics Instagram Insights data source and requires that we sunset 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.
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 is renamed STANDARD_ARCHIVE_20250325 on March 25, 2025. 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 March 25, 2025 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 March 25. 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 March 25 for such custom tables to fetch historical data, such as for year 2023, this might also overwrite your historical data for the affected fields with empty values. - Rename your custom tables in the Table Managerand 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 March 25. 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 March 25, 2025, and will no longer return results. While including these in queries won't break your queries, we recommend you update your queries to use the replacement fields to continue to get data.
- Media impressions → Use “Views” instead
- Reel plays → Use “Views” instead
- Reel replays → Use “Views” instead
- Reel initial plays → Use “Views” instead
- Carousel album impressions → Use “Views” instead
- Story impressions → Use “Story views” instead
- Profile impressions → Use “Profile views” instead when possible. Note the new field does not support date breakdowns
The “Views” and “Story views” metrics are already available in all destinations, so you can do the updates right away! The "Profile views" metric is coming very soon.
We're here for you
If you have any questions or concerns about this change, contact our support team.
