As part of the ongoing issues with the X Ads API, we were informed by X that they had already deprecated multiple sets of metrics to align with the Ad Manager UI. They are also still working to restore some functionality to the API, which means some fields don’t work at the moment.
To help keep you informed about these field deprecations and known broken functionality, we put this guide together and will update it as things evolve.
Please note that X did not communicate any of these changes in advance. There are no known public announcements and the X API documentation is still out-of-date with regards to the removed features. We are sorry about the abrupt updates, we’re trying to catch up with work X has already done.
Special note for data warehouse users
As the field deprecations have caused some functionality issues with the Standard table group, we will update it to a working version. The STANDARD table group will be renamed as STANDARD_ARCHIVE_20260507 on May 7, 2026.
All transfers using the standard table group will be available as a 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 will replace the deprecated fields with their new versions. New transfers created after May 7, 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, 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 have two options:
Keep the affected fields in the custom table, and they will start returning empty values after April 29. 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 April 29, 2026 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 combinations of fields that will lead to transfer failures after April 29, 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.
Known broken functionality
The following items are reporting elements or fields the X API team is still working to restore to service. We’ll remove these from the list in turn as X address’ them.
Segmentation
Some segmentation dimension have been restored. We confirmed the following work:
Gender
Country
Country code
Platform
Age
These are no longer in the API documentation and do not work - these will be deprecated:
App store category
Conversion tag
Event
Interests
Keyword
Language
Cities
Similar to follower
TV show
Region (will be replaced with DMA)
Reach related metrics
Currently any use of Total audience reach or Average frequency metrics will return no data.
We're currently discussing a resolution with X.
Restored functionality
More engagement metrics should be available
These metrics have been restored:
Replies
Engagements
Engagements (billed)
Cost per engagement (CPE)
Engagements rate (%)
Likes
Retweets
Follows
Qualified impressions
Mobile conversion metrics
All of these should be restored.
Deprecated metrics
The following fields do not function and will be deprecated on April 29, 2026, and will no longer return results after that date. While including these in queries won’t break your query, we recommend you remove the fields as they will no longer provide value.
In some cases, X noted they might bring some of these fields back. In those situations, we will re-add or reactivate the field at that time.
Field Name | Notes |
|---|---|
Video CTA clicks |
|
6s video views |
|
15s video views | Use Video views or View views 3s |
Media Engagements |
|
URL Clicks | Use Clicks instead |
Leads | Use Sign-ups, once it is working again |
Lead rate (%) |
|
Cost per lead |
|
Likes (paid+organic) | Use Likes |
Media views |
|
Media view rate |
|
Card engagements |
|
App clicks |
|
App click rate (%) |
|
Cost per app click (CPAC) |
|
Followers |
|
Follower rate (%) |
|
Cost per follower (CPF) |
|
Follows (promoted act) |
|
Follow rate (promoted act) |
|
Impressions (promoted act) |
|
Profile visits (promoted act) |
|
Tweet retweets | Use Retweets |
Impressions (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Qualified impressions (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Clicks (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Engagements (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Favorites (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Follows (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Replies (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Retweets (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
URL clicks (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Card engagements (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Media views (profile) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Impressions (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Qualified impressions (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Clicks (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Engagements (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Engagement rate (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
favorites (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Follows (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Replies (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Retweets (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
URL clicks (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Card engagements (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Media views (search) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Impressions (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Qualified impressions (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Clicks (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Engagements (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Engagement rate (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Favorites (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Follows (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Replies (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Retweets (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
URL clicks (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Media views (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Card engagements (timeline) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Media views (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Qualified impressions (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Card engagements (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Engagement rate (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Engagements (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Clicks (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Favorites (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Follows (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Impressions (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Replies (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Retweets (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
URL clicks (TPN) (deprecated) | Note that this field has been unsupported for some time. We're now properly marking it as deprecated. |
Additional planned changes
We have renamed “3s/100% video views” to “Video views 3s” to better align with the data source UI.
The Standard table group will be updated on May 7, 2026, as the included “Total likes” field is causing errors after the deprecation. We’ll remove all deprecated fields and add a few improvements to the table group on that date. The original version of the table group will be renamed STANDARD_ARCHIVE_20260507 and will still be available for existing transfers. However, due to the issue with the “Total likes” metric, we strongly recommend users migrate to the new version or create a custom table group to remove the problematic field.
We have renamed “Sign-ups” to “Lead” to better align with the data source UI.
We have added “DMA” as a replacement field for the deprecated Region dimension. Please note this only works for USA based accounts.
We’re here for you
If you have any questions or concerns about this change, contact our support team.