Ιστορικό διακοπών του Funnel

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

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.

This incident has been resolved.

We have observed that Display & Video 360 data sources that are configured to retrieve YouTube-related data, including data sources fetching custom reports that contain YouTube data, are currently struggling to import new data. From our investigation we believe this to be an issue with the DV360 API itself, as any report we attempt to generate that contains YouTube data ends up pending indefinitely. We have reached out to the DV360 support team with our findings, and we will continue to monitor affected data sources until the issue is resolved.

We have received confirmation from the Display & Video 360 team that there is an ongoing technical issue causing reports containing YouTube data to be significantly delayed. Their technical team is currently working on resolving the problem.

While we have not received any further correspondence from the DV360 team, we have observed that a majority of the data sources affected by this issue are now successfully managing to import new data. We will continue to monitor the connector for a while longer before considering this issue fully resolved.

We have received confirmation from the DV360 team that the issue has been resolved.

We are aware of this issue and in contact with Meta support. We have been receiving "Service temporarily unavailable" from the Facebook Ads API since the 16th of May. We will keep updating you on this status page. Thank you for your patience. /Funnel Team

We are continuing to investigate this issue.

We've identified that this issue specifically affects data sources configured with the Country breakdown. Sources without this breakdown are downloading normally. Workaround: If the Country breakdown is not essential for your reporting, you can connect a new data source without it applied to resume data imports. We are in contact with Meta regarding this issue and will provide another update as soon as we have more information.

We're actively working with Meta's engineering team to resolve this issue and will continue to provide updates as we learn more.

We are now seeing Facebook Ads data sources downloading normally again, including those configured with the Country breakdown. We have re-tested and can confirm that data is flowing as expected. We will continue to monitor the situation and provide further updates if anything changes. Thank you for your patience.

Facebook Ads data sources, including those with the Country breakdown, have continued to download as expected since our last update, and we have not seen any further "Service temporarily unavailable" errors from the Meta API. We are considering this incident resolved. If you experience any further issues, please reach out to support. Thank you for your patience

This incident has been resolved.

Due to mandatory security updates required by Salesforce, we recently enabled stricter token security controls across our Salesforce connectors (Marketing Cloud not affected) We are seeing an increased number of Salesforce sources reporting authentication errors ("No Access"). This is caused by existing refresh tokens being invalidated as part of the Salesforce security rollout. Affected sources need to be reconnected to generate a new valid token. We are also currently investigating issues with the reconnection flow that may prevent some users from completing the reconnect. We are working to unblock this with highest priority.

We have deployed a fix that resolves authentication errors for the majority of affected Salesforce sources. For most users: reconnecting your Salesforce data source through the Funnel UI will restore access and resume data collection. We recommend doing this if your source is currently showing "No Access." For a subset of users: we are aware that the reconnection flow is not completing successfully in some cases. We have identified this as a separate issue and are actively working to resolve it. No action is required from affected users at this time, we will provide an update as soon as a resolution is in place. We continue to monitor all Salesforce connections closely.

We are pleased to confirm that the Salesforce authentication errors have been fully resolved. All affected data sources should now be reconnected and downloading data as expected. Thank you for your patience on the matter.

Over the last week we see an increase in error rates in Funnels Data Studio Connector. These show up as 'Bandwidth quota exceeded' or as column mismatch error when loading data. This looks to be a widespread issue on Googles side affecting many different services. We are waiting for confirmation from Google and are looking at other ways to mitigate this issue.

Google has reported that the issue has been fixed and we have not seen any new errors in our logs. We will continue to monitor but we now consider this issue to be resolved.

We have observed an escalated number of failing import jobs for our Amazon Seller Central and Amazon Vendor Central connectors. Most data sources appear to be affected. We are currently investigating the cause of this issue.

We identified the issue and just deployed a fix. We are monitoring affected data sources to ensure everything works as expected.

This issue is resolved. Data sources that have experienced delays as a result of this incident will be up-to-date within a few hours.

We are currently investigating an issue causing data delays across several Facebook Ads data sources. Our requests are receiving "Internal Server Error" responses from the Meta API.

We've worked together with Meta to address the delays affecting Facebook Ads data sources and Facebook Ads data should be processing as expected without errors or gaps. Should you notice any issues, please don't hesitate to reach out.

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

We are continuing to work on a fix for this issue.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

We have continued investigating the remaining X Ads and X Organic report types affected by X's ad platform migration. This update reflects progress and current status across the outstanding areas. Location / Country segmentation We have confirmed with X that Location / Country is no longer supported in their ad platform. We are adding a clear error message for sources using this configuration so they no longer appear active without returning data. This is consistent with X's guidance that the supported segmentation types going forward are Age, Gender, Platforms, and Location / Metro Area. Age segmentation X has confirmed on their end that Age-segmented reports are operational. We have resumed downloads for most sources using this configuration. However, we are continuing to investigate a specific pattern where a small number of sources return incomplete data. We are working with X to confirm the expected behavior and expect to resolve this shortly. Platforms segmentation We are monitoring reports from some sources where Platforms-segmented data does not match expectations. Investigation is ongoing. We will update here once we have confirmed the scope and handling. Campaign-level budget optimization reports We are investigating a separate category of reports related to campaign-level budget optimization configuration. We have raised specific questions with X and are awaiting their response. Affected sources may continue to show incomplete or delayed data in the meantime. X Organic Tweet Activity X Organic Tweet Activity data is still not returning metrics. X provided a resolution timeline that has since passed without a fix landing. We continue to follow up with X actively and will post an update as soon as this is resolved. A lookback boundary remains in place at the start of April 2026. X's reporting APIs do not make migration-period data available for reliable re-fetching, so Funnel will not attempt to re-download data before this point. Historical data already collected in Funnel remains available. We will continue posting updates here as each area is confirmed resolved or stabilized.

There is an issue with Funnels Google Looker Studio Connector not responding and data is not loading in reports. We are currently investigating the cause.

Google has identified that some customers experience errors loading Community Connectors. They are working on mitigating the issue. We will monitor and update when we have new information from Google.

Google has informed us that: "The issue with Looker Studio has been resolved for all affected customers". Funnels Google Looker Studio Connector are now working as normal. We will continue to monitor the situation.

Everything working as normal, we consider this issue to be resolved.

We're aware of an issue where some customers are not seeing data after 2026-03-26 for their X Ads sources. We're currently investigating the cause.

We have made progress in our investigation into the data issues affecting X Ads sources. We have identified two separate issues contributing to the disruption, both not only limited to Funnel but confirmed across the broader X Ads API ecosystem: Intermittent errors when retrieving campaign data. This caused some downloads to fail entirely. Based on our monitoring, this issue has largely subsided. Incomplete or missing metrics for certain ad configurations, some X Ads sources are returning incomplete data for metrics such as impressions, clicks, and cost. This issue appears to still be ongoing and is not limited to Funnel. We are continuing to monitor both issues closely. Sources affected by the first issue has successfully been resolved. For the second issue, we are tracking the situation and will trigger re-syncs once complete data is available. We understand this impacts your reporting and continue to treat this with the highest priority.

After discussion with X, the discrepancies are due to a major overhaul of the X adstack between the period of 3.14 through 3.31. Still investigating when and if the reporting will be back to normal

Closing this issue, since its related to the larger issue around X new ad platform

We are currently experiencing delays in the sftp exports. We are investigating this issue and we will update as soon as we can.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We're aware of missing values for several Ad level fields for the TikTok connector, such as Ad status, Video ID, Ad landing page URL and more. We're currently investigating the cause.

A fix has been implemented and we're monitoring the results.

Postmortem: The issue was due to a change of download schedule for TikTok that resulted in long download cues. We have implemented observability and gardrails for this type of issue happen again

There is an active investigation into a spike in reports regarding missing data for archived or deleted Meta ads. While the system is designed to pull this historical content, a recent shift is currently obstructing these data sources. Root cause analysis is underway to determine the scale of this Meta limitation.

We are continuing to investigate this issue.

Closing incident since we 24 of March reverted the changes that resulted in that archived and deleted ads were not returned. After monitoring the update we are back to correct behavior.

_**What happened:**_ The root cause of the issue was threefold: on January 2nd, we updated the Facebook Ads API integration to better handle data sources struggling to download data on a low granularity with high complexity calls. A side effect of this change was that archived were not downloaded correctly. In February, while initially debugging the incident, the Facebook Ads endpoints did not return data that they had previously returned, leading us to escalate the issue with Meta. However, while awaiting a response from Meta, the endpoints changed behavior again - returning data as previously expected, something that increased the time to resolution. Finally, on March 10th another update aimed at increasing the efficiency and reliability of the Facebook Ads API integration to support customers with very large datasets had the side effect of removing all deleted ads from responses \(for most users this resulted in 30 days of missing deleted ads, but affected anyone with newly created sources or sources that requested a backfill during this period\). On March 23rd, we released a update which ensured archived and deleted ads are ingested correctly. _**What we are doing:**_ As a result of this incident, we are creating additional testing infrastructure to better cover more customer use cases for regression testing before releasing updates to the integrations. We are also implementing improved monitoring for API health so we will notice changes in 3rd Party Endpoints more reliably, minimizing the need for customer escalations. Furthermore, as a mid- to long-term mitigation we are also improving data health measures to detect irregularities on the data field level, that will further compound on these reliability gains. _**What you should do:**_ _If you notice discrepancies in your Facebook Ads data downloaded January 2 – March 22, please reach out and we will prioritize a backfill for your sources._

AppsFlyer - Inflated monetary values Monitoring - A recent update to our AppsFlyer connector caused a regression that greatly inflated monetary values, specifically Cost and Event Revenue, for any data that the connector retrieved between March 16th 10:05 AM and March 17th 12:04 AM (both times UTC). A fix has been deployed, and we believe that the majority of affected AppsFlyer data sources should self-heal within 24 hours. If your data source is still showing inflated values for these metrics after 24 hours, or if you want us to manually refresh your data source(s) to expedite the process of getting your data corrected, please reach out to our support team. We apologize for the inconvenience.

We have observed that some data sources are not self-healing as we previously anticipated, partially as a result of quota limit constraints that cause the re-fetching of affected data to take longer than expected. Moreover, we have identified that some data sources backfilled more historical data than we were previously aware of around the time the regression was introduced. We are currently working to locate these data sources to ensure that they are scheduled to re-import any data that has been affected by this issue.

We have now scheduled new backfills for all AppsFlyer data sources and date intervals that we believe to be affected by this issue. Due to quota limits, the process of re-fetching all this data may take a bit of time, but we hope that it will be completed over the weekend. We will check progress on Monday and update this incident accordingly.

We believe that most affected data sources should now have correct data once again. Some data sources that have a lot of data to re-fetch may still be in the process of backfilling historical data, so we will continue to monitor for a while longer. If you still notice any discrepancies related to inflated monetary values in your AppsFlyer data sources, please reach out to support and we will investigate accordingly.

We consider this issue to be resolved. Backfills for affected data sources should be completed successfully by now. If you observe any inflated monetary values in your AppsFlyer data sources, please reach out to support for investigation.

We are currently experiencing an interruption in TikTok data downloads. A recent change to our systems caused a higher volume of requests to the TikTok API which has caused us to temporarily exceed our API quota. Background: On March 3, we started seeing an increase in errors for TikTok downloads. We deployed a fix to accommodate this change; however, the resulting increase in request volume has triggered a secondary quota limitation. Next Steps: We are optimizing our retrieval process to lower the request count. We will provide an update as soon as downloads resume.

We deployed a fix over the weekend which allowed us to resume downloads again. As of March 8th, downloads are back to normal.

We have received reports of Trade Desk data sources and the imports of their most recent data being delayed. The team is currently investigating the issue and will provide further updates on the data delays as soon as we have them. We appreciate your patience while investigating the issue.

The issue affecting some Trade Desk data sources has been corrected. We identified that a recently added field in the connector impacted API performance, preventing some data imports from completing. The field has been removed, and delayed sources are now recovering. We are continuing to monitor to ensure stable data delivery.

All affected Trade Desk data sources have now fully recovered, and data imports are operating normally. The issue was caused by a recent connector update that impacted API performance. The update has been reverted, and we have validated that imports are completing as expected. We will continue to monitor performance closely to ensure ongoing stability.

We have observed that Display & Video 360 data sources that are configured to retrieve YouTube-related data, including data sources fetching custom reports that contain YouTube data, are currently struggling to import new data. From our investigation we believe this to be an issue with the DV360 API itself, as any report we attempt to generate that contains YouTube data ends up pending indefinitely. We are reaching out to the DV360 API support team with our findings to try to get the issue resolved.

After confirming that they were able to replicate the issue on their end, the DV360 team have now fixed the problem. Data sources in Funnel are now up-to-date and downloading new data without interruptions.

We’re currently aware of an issue where users are unable to connect data sources to Funnel. Our team is actively investigating the situation and working to identify the root cause. We’ll share updates here as soon as we have more information. Thank you for your patience.

We identified a small number of unhealthy instances and took immediate action to decommission and replace them with new, healthy instances. The issue is now fully resolved.

After confirmation from several customers normal operations have been restored. We apologize for the issue and thank you for your patience.

We are currently investigating an issue causing data delays across several Facebook Ads data sources. Our requests are receiving "Internal Server Error" responses from the Meta API. This has been escalated to Meta for investigation. As this is an upstream issue on their end, we are awaiting their feedback and will provide updates as they become available.

We are continuing to investigate the root cause of the recent data delays and are currently awaiting further technical feedback from Meta. To restore service in the meantime, we have deployed a temporary fix. While this allows data sources to resume downloading successfully, please note that a very small subset of ads will temporarily omit the bid_amount field. Most reporting delays have now been resolved and we will update when we have more information.

While the temporary fix is still in place and is allowing data sources to resume downloading data, we are also in the process of providing info to Meta. We are awaiting for Meta's technical feedback on the matter.

Closing issue since the correction made 6th of March. We still see a handful of sources not working with the correction due to the complexity. But this is handled as support issues

We are experiencing unusually long queue times for Funnel Exports. We’re sorry for the disruption. We are currently experiencing significant delays affecting exports that started on Jan 30, 2026, at 06:00 CET. Impact • Exports may be delayed or not delivered as expected. • This may impact your ability to move data from Funnel to your downstream destinations. We understand how critical exports are to your workflows, and we’re taking this issue very seriously. Our Product and Development teams are actively investigating and working to resolve this as quickly as possible.

We have identified the cause as a performance regression introduced in a deployment on Jan 29, 2026. While most exports were unaffected, a subset of exports starting this morning were severely impacted, which in turn caused delays for additional customers. We have reverted the change, and export processing is now recovering. Our teams are continuing to investigate to fully understand the issue and prevent a recurrence. We’re very sorry for the continued disruption.

Export queues have now returned to normal levels, and the system is operating as expected. We will continue to closely monitor the situation. We’re very sorry for the disruption this has caused.

Export queues have remained at normal levels, and exports have been processing as expected for the past four hours. We now consider this incident resolved. Our teams will continue with follow-up investigation to fully understand the root cause and ensure we prevent similar issues in the future. We’re very sorry for the disruption this caused and sincerely thank you for your patience while we worked to resolve the issue.