Monitoring - Facebook appears to have implemented a fix on their side. We've had recent reports of users successfully connecting their Facebook and Instagram data sources, and new connections should now be working. We'll continue to monitor the situation but believe the issue should be resolved at this point in time.
Jun 12, 2026 - 18:17 CEST
Jun 12, 2026 - 18:17 CEST
Investigating - There's an issue currently originating from Meta, which affects their services. Once the issue is resolved on Meta's side, the connection of new Facebook and Instagram sources will be possible again.
Feel free to follow along and monitor the progress of the incident on Facebook's official status page here: https://metastatus.com/ads-manager
Jun 12, 2026 - 16:15 CEST
Feel free to follow along and monitor the progress of the incident on Facebook's official status page here: https://metastatus.com/ads-manager
Jun 12, 2026 - 16:15 CEST
Update - We have deployed additional X Ads connector changes to reflect the reporting capabilities we have now confirmed after X’s ad platform migration.
As part of this update, several segmentation types that no longer return reliable data from X have been removed for new data source configurations. Existing sources using these configurations will now show a clear error message instead of continuing to appear active while returning no new data. This helps prevent silent gaps in reporting and makes it clearer when a source configuration can no longer be supported for new data.
The affected segmentation configurations are Audience, Keyword, Location / Region, Location / Postal Code, and Similar to Followers of User. Historical data already collected in Funnel remains available.
We are continuing to investigate some remaining X Ads report types where X’s reporting API still returns empty or incomplete data even though the configuration is expected to be supported. This currently includes Age-segmented reports, some reports related to ad group-level budget optimization, and Media Creative reports. These sources may continue to show delayed, empty, or incomplete data while we verify the behavior and determine the correct handling.
Location / Country remains under investigation separately. We are seeing mixed behavior where some sources return current data while others do not, so we are continuing to monitor this before making further changes.
A lookback boundary remains in place at the start of April 2026. X’s current reporting APIs do not make the earlier migration-period data available for reliable re-fetching, so Funnel will not attempt to re-download data before this boundary. Historical data that was already collected in Funnel remains available.
We are also seeing continued issues with the X Organic Tweet Activity report. The report request is accepted by X, but the completed report does not return tweet activity metrics, so affected sources may return no new data. X Organic User Insights is not affected by this specific issue. We are working with X to confirm the expected behavior and path forward.
We will continue posting updates here as we confirm which remaining configurations can reliably download data and which are no longer supported by X.
Jun 09, 2026 - 09:28 CEST
As part of this update, several segmentation types that no longer return reliable data from X have been removed for new data source configurations. Existing sources using these configurations will now show a clear error message instead of continuing to appear active while returning no new data. This helps prevent silent gaps in reporting and makes it clearer when a source configuration can no longer be supported for new data.
The affected segmentation configurations are Audience, Keyword, Location / Region, Location / Postal Code, and Similar to Followers of User. Historical data already collected in Funnel remains available.
We are continuing to investigate some remaining X Ads report types where X’s reporting API still returns empty or incomplete data even though the configuration is expected to be supported. This currently includes Age-segmented reports, some reports related to ad group-level budget optimization, and Media Creative reports. These sources may continue to show delayed, empty, or incomplete data while we verify the behavior and determine the correct handling.
Location / Country remains under investigation separately. We are seeing mixed behavior where some sources return current data while others do not, so we are continuing to monitor this before making further changes.
A lookback boundary remains in place at the start of April 2026. X’s current reporting APIs do not make the earlier migration-period data available for reliable re-fetching, so Funnel will not attempt to re-download data before this boundary. Historical data that was already collected in Funnel remains available.
We are also seeing continued issues with the X Organic Tweet Activity report. The report request is accepted by X, but the completed report does not return tweet activity metrics, so affected sources may return no new data. X Organic User Insights is not affected by this specific issue. We are working with X to confirm the expected behavior and path forward.
We will continue posting updates here as we confirm which remaining configurations can reliably download data and which are no longer supported by X.
Jun 09, 2026 - 09:28 CEST
Update - We have deployed connector changes earlier this week based on the reporting capabilities currently available from X following their ad platform migration.
These changes have restored downloads for many X Ads data sources that were previously delayed. We are continuing to monitor the resumed downloads closely to verify that data is complete and aligned with the selected report configurations.
As previously communicated, X has removed support for some reporting capabilities. This means that Web custom conversion metrics based on individual conversion events, for example fields named after a specific event such as “Purchase | example.com”, will no longer receive new data. Historical data for those fields remains available in Funnel. Standard conversion metrics that are still returned by X are not affected by this specific change.
We are still investigating remaining cases where X Ads reports return empty or incomplete data even when the data source configuration is expected to be supported. This includes some segmented reports and reports related to campaigns using ad group-level budget optimization. These cases may continue to show delayed, empty, or incomplete data while we verify the behavior and determine the correct handling.
To protect data quality, we have also set a lookback boundary at the start of April 2026. X’s current reporting APIs no longer make the earlier migration-period data available for reliable re-fetching, so Funnel will not attempt to re-download data before this boundary. Historical data that was already collected in Funnel remains available.
We will continue posting updates here as we confirm which remaining configurations can reliably download data and which are no longer supported by X.
Jun 04, 2026 - 14:37 CEST
These changes have restored downloads for many X Ads data sources that were previously delayed. We are continuing to monitor the resumed downloads closely to verify that data is complete and aligned with the selected report configurations.
As previously communicated, X has removed support for some reporting capabilities. This means that Web custom conversion metrics based on individual conversion events, for example fields named after a specific event such as “Purchase | example.com”, will no longer receive new data. Historical data for those fields remains available in Funnel. Standard conversion metrics that are still returned by X are not affected by this specific change.
We are still investigating remaining cases where X Ads reports return empty or incomplete data even when the data source configuration is expected to be supported. This includes some segmented reports and reports related to campaigns using ad group-level budget optimization. These cases may continue to show delayed, empty, or incomplete data while we verify the behavior and determine the correct handling.
To protect data quality, we have also set a lookback boundary at the start of April 2026. X’s current reporting APIs no longer make the earlier migration-period data available for reliable re-fetching, so Funnel will not attempt to re-download data before this boundary. Historical data that was already collected in Funnel remains available.
We will continue posting updates here as we confirm which remaining configurations can reliably download data and which are no longer supported by X.
Jun 04, 2026 - 14:37 CEST
Update - Update — June 3 ETA, connector changes from X's new API guidelines
We have received written confirmation from X on which reporting capabilities remain available following their ad stack migration. We are now updating the connector accordingly. We expect most data sources to resume downloading from June 3, 2026.
What is changing:
Sources using segmentation types that X has permanently discontinued will be set to an Error state. You will see a red error indicator on those data sources in Funnel, with a message explaining that the configuration is no longer supported by X's API. No further data will be downloaded for those sources.
The affected configuration summaries (visible under the source name in Funnel) are any source with one of the following Configuration Summary:
| Audience
| Location / Country
| Location / Region
| Location / Postal Code
| Keyword
| Similar to Followers of User
This applies across all report levels (Campaign, Ad Group, Promoted Tweet).
If you have sources with these configurations, you can keep them for historic data. But they will not download new data going forward.
Also changing: The Web custom conversion metrics — fields named after your specific conversion events (e.g. "Purchase | yoursite.com") — will no longer receive new data, as X has removed the underlying reporting capability. Historical data already in Funnel remains accessible. All other conversion metrics (total web purchases, site visits, website leads, etc.) are unaffected.
What resumes working after the changes: All other X Ads configurations, including non-segmented reports and sources segmented by Age, Gender, Platform, and Location / Metro.
We are closing the related status page [X Ads - Missing data since 26 March] and will continue posting updates here.
May 28, 2026 - 16:16 CEST
We have received written confirmation from X on which reporting capabilities remain available following their ad stack migration. We are now updating the connector accordingly. We expect most data sources to resume downloading from June 3, 2026.
What is changing:
Sources using segmentation types that X has permanently discontinued will be set to an Error state. You will see a red error indicator on those data sources in Funnel, with a message explaining that the configuration is no longer supported by X's API. No further data will be downloaded for those sources.
The affected configuration summaries (visible under the source name in Funnel) are any source with one of the following Configuration Summary:
| Audience
| Location / Country
| Location / Region
| Location / Postal Code
| Keyword
| Similar to Followers of User
This applies across all report levels (Campaign, Ad Group, Promoted Tweet).
If you have sources with these configurations, you can keep them for historic data. But they will not download new data going forward.
Also changing: The Web custom conversion metrics — fields named after your specific conversion events (e.g. "Purchase | yoursite.com") — will no longer receive new data, as X has removed the underlying reporting capability. Historical data already in Funnel remains accessible. All other conversion metrics (total web purchases, site visits, website leads, etc.) are unaffected.
What resumes working after the changes: All other X Ads configurations, including non-segmented reports and sources segmented by Age, Gender, Platform, and Location / Metro.
We are closing the related status page [X Ads - Missing data since 26 March] and will continue posting updates here.
May 28, 2026 - 16:16 CEST
Update - We are still working with X on this issue, but there has not been any progress since our last update.
We will keep posting in this Status Page to keep you informed on the situation.
May 22, 2026 - 12:25 CEST
We will keep posting in this Status Page to keep you informed on the situation.
May 22, 2026 - 12:25 CEST
Update - We are continuing to monitor the ongoing issue affecting X Ads and X Organic data sources. This remains a top priority for our team. The root cause lies on X’s side and we are in ongoing contact with them. We do not have any new updates to share at this time, but will post here as soon as we do.
We appreciate your patience and understanding on the matter and will share updates with you here as soon as we have more information to share.
May 13, 2026 - 18:38 CEST
We appreciate your patience and understanding on the matter and will share updates with you here as soon as we have more information to share.
May 13, 2026 - 18:38 CEST
Update - We are still working on this issue, and can see some issues being corrected on the X APIs. However, we are still unable to get all breakdowns needed to provide correct data for reporting. We have unblocked the sources to see what combination of settings have incorrect data.
This means that some data sources might look like they are working. But they show up with no data. We are investigating if which combinations are truly no data and which ones are due to X returning no data incorrectly.
We are actively working together with X to sort this out.
May 07, 2026 - 15:54 CEST
This means that some data sources might look like they are working. But they show up with no data. We are investigating if which combinations are truly no data and which ones are due to X returning no data incorrectly.
We are actively working together with X to sort this out.
May 07, 2026 - 15:54 CEST
Update - We’re still holding the X connectors in blocked state until reporting data is verified end-to-end. The time zone alignment issue and server errors are unchanged since our last update. We’re actively following up with X and will post the next update by [today + 4 days], or sooner if anything material changes.
Apr 30, 2026 - 15:31 CEST
Apr 30, 2026 - 15:31 CEST
Update - We continue to hold the X (Twitter) Ads connector in a blocked state while we verify reporting data end-to-end.
In addition to the time zone alignment issue we described previously (which X is working to correct), we are now also seeing intermittent server errors from the reporting paths we use, including responses that fail when requesting certain breakdowns of the data. We are in contact with X to confirm whether this is related to the ongoing corrections to reporting.
We will not enable the connector for general use until we are confident the data in Funnel is complete and correct for your reports. The next update will be posted by 2 days once we have more from X, or sooner if the situation changes materially.
Apr 27, 2026 - 15:42 CEST
In addition to the time zone alignment issue we described previously (which X is working to correct), we are now also seeing intermittent server errors from the reporting paths we use, including responses that fail when requesting certain breakdowns of the data. We are in contact with X to confirm whether this is related to the ongoing corrections to reporting.
We will not enable the connector for general use until we are confident the data in Funnel is complete and correct for your reports. The next update will be posted by 2 days once we have more from X, or sooner if the situation changes materially.
Apr 27, 2026 - 15:42 CEST
Update - We’ve identified an issue in how X’s API returns data in relation to time zones, which can affect how performance metrics line up to dates in your reports. We’re working with X, who have acknowledged the issue and are working on a correction. We’re keeping the X connector in a blocked state until we’ve verified that the data we receive matches what we expect for accurate reporting. We expect to share a further update by the end of the week
Apr 22, 2026 - 14:57 CEST
Apr 22, 2026 - 14:57 CEST
Update - We have made further progress with X on restoring downloads, but we are still validating that the data fully matches your reporting periods and is safe to rely on. Until that is confirmed, we are not writing new data for the affected X Ads and X Organic configurations, so we do not replace existing correct figures with values that may be misaligned.
X has confirmed they are treating the underlying platform issues as a high priority. We remain in close contact with them and will post the next update when we can either confirm reliable delivery or share a clearer timeline.
Apr 19, 2026 - 23:29 CEST
X has confirmed they are treating the underlying platform issues as a high priority. We remain in close contact with them and will post the next update when we can either confirm reliable delivery or share a clearer timeline.
Apr 19, 2026 - 23:29 CEST
Update - In collaboration with X we now got a bit further in finding ways to get the X Ads and X organic connectors up and working. However we are still validating if the workaround produces valid data, and can be scaled. The focus is currently on getting X ads working first, and X organic secondly.
Apr 17, 2026 - 17:34 CEST
Apr 17, 2026 - 17:34 CEST
Update - During conversation with X dev team, the issues are known and they are working on it with highest prio. However, no ETA when it can be solved.
Apr 16, 2026 - 19:06 CEST
Apr 16, 2026 - 19:06 CEST
Update - We are continuing to work on a fix for this issue.
Apr 13, 2026 - 15:06 CEST
Apr 13, 2026 - 15:06 CEST
Identified - We have identified an issue where X endpoints we are using for specific reports are not returning data.
Our hypothesis is that this is due to the major update on X Ad platform.
Sources with the issue:
X Ads
- All configuration except Campaign Non-Agg
X Organic
- Tweet Activity (User insights is working)
The issue has been reported by multiple other vendors.
The issues started 2026-04-10.
We are working on findings ways around the issue.
See also related Status page X Ads - Missing data since 26 March https://status.funnel.io/incidents/dsyj3s7hzrzf
Apr 11, 2026 - 13:33 CEST
Our hypothesis is that this is due to the major update on X Ad platform.
Sources with the issue:
X Ads
- All configuration except Campaign Non-Agg
X Organic
- Tweet Activity (User insights is working)
The issue has been reported by multiple other vendors.
The issues started 2026-04-10.
We are working on findings ways around the issue.
See also related Status page X Ads - Missing data since 26 March https://status.funnel.io/incidents/dsyj3s7hzrzf
Apr 11, 2026 - 13:33 CEST
About This Site
This is the status page for Funnel. It is used for announcing technical issues and posting updates as issues are diagnosed and resolved.
It was put in place in November 2019, which means you will not find information about prior issues.
Funnel
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance