Is TapClicks Down Right Now? Check if there is a current outage ongoing.

A subset of our customers connected to Simpli.fi are experiencing data delays due to a technical issue on our end. Impacted customers can see this by looking at "Connections with issues to be investigated by TapClicks" on the main tab of their Data Load Status dashboard and have received notifications via email already if they have configured these on the Notifications tab of the Data Load Status dashboard. Our team is actively working on resolving the issue and we will provide updates as they become available. We apologize for the inconvenience.

Update: All of Simpli.fi reporting services were restored starting around 7PM (CT) last evening and fetches for today have been completing without errors. If you are still experiencing issues with your Simpli.fi connection, please reach out to support@tapclicks.com Thank you

Impact: Data Delays for Simpli.fi-Connected Customers Monitoring We are currently observing intermittent connection issues between TapClicks and Simpli.fi, as reported by our partner at Simpli.fi. This is impacting customers whose data sources are connected to Simpli.fi via TapClicks. What you may experience: Delays in the availability of new data from Simpli.fi Historical data previously collected remains accessible and unaffected Simpli.fi has identified the issue and is actively working toward a resolution on their end. TapClicks will continue to monitor the situation closely and provide updates as we receive them. We appreciate your patience and understanding. The TapClicks Team

Impact: Data Delays for Simpli.fi-Connected CustomersMonitoringWe are currently observing intermittent connection issues between TapClicks and Simpli.fi, as reported by our partner at Simpli.fi. This is impacting customers whose data sources are connected to Simpli.fi via TapClicks.What you may experience:Delays in the availability of new data from Simpli.fiHistorical data previously collected remains accessible and unaffectedSimpli.fi has identified the issue and is actively working toward a resolution on their end. TapClicks will continue to monitor the situation closely and provide updates as we receive them.We appreciate your patience and understanding.The TapClicks Team

X Ads have restored their API over the weekend and after monitoring, we can confirm a majority of customers fetches have been successfully completing. We will close this incident as the connection now appears to be stable. If you are still facing issues with the X Ads connection, please reach out to support. Thank you, The TapClicks Team

Description: Tapclicks is currently experiencing an outage with the X (formerly Twitter) Ads Connector. This issue is due to an external service disruption on X Ads' side, which is impacting our ability to retrieve new advertising data via their API. Impact: New data from X Ads is currently unavailable in Tapclicks. Previously imported data remains intact and accessible. Next Steps: We are monitoring the situation and awaiting further updates from X. We will provide additional information as it becomes available. Thank you for your patience and understanding.

X Ads have restored their API over the weekend and after monitoring, we can confirm a majority of customers fetches have been successfully completing.We will close this incident as the connection now appears to be stable. If you are still facing issues with the X Ads connection, please reach out to support.Thank you,The TapClicks Team

Description:Tapclicks is currently experiencing an outage with the X (formerly Twitter) Ads Connector. This issue is due to an external service disruption on X Ads' side, which is impacting our ability to retrieve new advertising data via their API.Impact:New data from X Ads is currently unavailable in Tapclicks.Previously imported data remains intact and accessible.Next Steps:We are monitoring the situation and awaiting further updates from X. We will provide additional information as it becomes available.Thank you for your patience and understanding.

This incident has been resolved.

Fetches today continue to complete after close monitoring. We are marking the incident for fetch failures as resolved in the meantime. We are still in the process of working with the new metric fields as an enhancement separately.

Instagram has deprecated the "Impressions" field from the Professional API that was causing recent fetch issues. TapClicks has updated our system to discontinue requests for the impression metric to unblock data fetches for customers. Your historical impressions data that was previously stored within TapClicks will still be accessible in TapClicks but new impression data will no longer be supported by the Instagram API. We will be working on introducing new fields per Instagram's recent changes.

We are currently investigating an issue affecting the retrieval of recent metrics from the Instagram API. A recent change made by Instagram appears to be causing interruptions for some users attempting to access this data. Our team is actively working to adapt to the update. We will provide further updates as more information becomes available. Thank you for your patience and understanding.

This incident has been resolved.

Fetches today continue to complete after close monitoring. We are marking the incident for fetch failures as resolved in the meantime.We are still in the process of working with the new metric fields as an enhancement separately.

Instagram has deprecated the "Impressions" field from the Professional API that was causing recent fetch issues. TapClicks has updated our system to discontinue requests for the impression metric to unblock data fetches for customers. Your historical impressions data that was previously stored within TapClicks will still be accessible in TapClicks but new impression data will no longer be supported by the Instagram API.We will be working on introducing new fields per Instagram's recent changes.

We are currently investigating an issue affecting the retrieval of recent metrics from the Instagram API. A recent change made by Instagram appears to be causing interruptions for some users attempting to access this data.Our team is actively working to adapt to the update. We will provide further updates as more information becomes available.Thank you for your patience and understanding.

Update: After recent monitoring, we are no longer seeing fetch issues for conversions for our API fetches. If you are still encountering issues, please reach out to support@tapclicks.com. Thank you, The TapClicks Team

Update: The Trade Desk Fetches for today has been completing for a majority of our customer post communication with The Trade Desk Team. We are still in discussions with the TTD team and will continuing to monitor fetches. Thank you for your patience.

Issue Summary We are currently experiencing an issue with data ingestion from The Trade Desk connector. Specifically, some Conversions and Data Elements API reports have been disabled on The Trade Desk system side. The Trade Desk team is actively investigating the root cause. Impact This impacts users who are connected to The Trade Desk Connectors leveraging these specific reports. Please check the Data Load Status page to see whether your instance is affected. This impacts the ability to fetching new TTD data while previously stored data in TapClicks remains unaffected by this issue. Next Steps & ETA This issue is vendor-dependent. We've submitted an urgent request to The Trade Desk, who have acknowledged receipt and investigating on their end. We will share updates as soon as we receive more information from The Trade Desk team.

Google Ads services were successfully restored following a fix implemented on March 19th. After thorough monitoring, we can confirm that the intermittent Fetch issue has been resolved. If you continue to experience any problems with the Google Ads connector, please contact us at support@tapclicks.com. Thank you, The TapClicks Team

Incident Summary: We are currently investigating an issue affecting some of our customers who are connected to the Google Ads API. Due to recent changes made on Google's end, certain customers are experiencing difficulties with fetching data. Current Status: Our team is actively working with Google and collaborating closely with their team for a resolution. What’s Affected: Customers with active Google Ads API connections may experience intermittent data fetching failures or delays. Affected customers may notice incomplete or outdated data in their dashboards. Next Steps: We will continue to monitor the situation and keep you updated as we work with Google to resolve this issue. We are prioritizing this matter and will provide a follow-up once we have more information or once the issue has been resolved.

After carefully monitoring, all customers are stable with the fix done by the BigData provider yesterday. This incident is now resolved. Please reach out to support@tapclicks.com if you are still observing any issues. Thank you, The TapClicks Team

Update: Our BigData engine provider has implemented a fix on their end. Customers hosted on BigData servers are being restored, and we are seeing a significant improvement in dashboard performance. We will continue to closely monitor performance in collaboration with the provider to ensure stability moving forward.

We have identified that there is incident going on with one of our provider is impacting clients on the BigData package. We are working closely with the provider to get the service back ASAP. This is a global incident that was reported by the BigData data engine provider. This is impacting TapAnalytics and TapReport among other services. Customers not on BigData packages are not impacted.

UPDATE: The LinkedIn Team deployed a fix on their end last night and we are now seeing the fetches errors any longer this morning. If you are still having issues or observing issues with the LinkedIn Ads Connector, please let us know at support@tapclicks.com. Thank you, The TapClicks Team

Issue Summary We are currently experiencing a disruption in LinkedIn Ads data retrieval due to an ongoing issue on LinkedIn’s end. This problem affects all API users, including TapClicks, and is not specific to our platform. Impact New LinkedIn Ads data for today is currently stalled. Historical data previously stored in TapClicks remains unaffected and accessible. Current Status LinkedIn has acknowledged the issue and is actively working on a resolution as a priority. We are closely monitoring the situation and will provide updates as soon as more information becomes available. Next Steps We will update this page as soon as LinkedIn resolves the issue and data processing resumes. Thank you for your patience.

Emails Queued from yesterday has been sent. We have been monitoring the system and emails have been fully operational since. If you are still experiencing issues with emails from TapClicks, please feel free to reach out to support@tapclicks.com Thank you, The TapClicks Team

Our email provider has implemented a fix, and new email sends are now working as expected. We are still processing previously queued emails from earlier today. Our team is closely monitoring the situation to ensure all pending emails are delivered as soon as possible. We appreciate your patience and will provide further updates as needed. Thank you for your understanding

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

We are currently experiencing an issue with our email provider that has impacted the delivery of emails out of TapClicks. As a result, some scheduled reports may be delayed. Our team is actively working with the provider to resolve the issue and ensure that all emails are sent as soon as possible. Your reports and email communication outside of TapClicks are important to us and we are we are addressing as a priority. We apologize for any inconvenience and appreciate your patience. We will provide updates as more information becomes available. Thank you for your understanding.

Update: Performance has remained stable, with no new irregularities observed. We will continue collaborating with our partner to enhance systems and implement measures to prevent similar incidents in the future.

Update: Performance has returned to normal after the maintenance reboot conducted on Saturday. However, the root cause of the issue remains unclear, and we are continuing our monitoring and investigation. Further updates will be provided as we gather more information.

Monitoring: We are currently experiencing slower-than-usual performance across several services. The issue has been traced to an external DNS service provider experiencing disruptions. Our team has reported the issue to the provider and is actively monitoring their updates. Impact: Users may notice delays in loading pages, API responses, and other service-related interactions. This issue is affecting multiple regions and may cause intermittent slowdowns. Next Steps: We have reported the issue to the DNS provider. Our team is closely monitoring the situation for updates and resolution. Thank you for your patience as we work to resolve this issue.

Resolved We have identified and resolved the issue that caused some scheduled reports to be sent out as blank. Scheduled reports are now being generated and sent correctly. To avoid potential sending duplicate emails for customers, if you would like assistance resending any scheduled reports that were previously sent as blank, please contact us at support@tapclicks.com. Our team will gladly coordinate with you to resend the reports. Thank you for your patience as we worked to resolve this issue.

Identified: We are aware of an issue where some scheduled reports are being sent out as blank for some customers. Our team is actively working on a resolution. Impacted Services: Scheduled Reporting Impact Details: Some users may receive scheduled reports without content. We will resend emails with pdfs when ready. Dashboards are not impacted and users can export reports through the application still. We apologize for the inconvenience this is causing and are working on this as a priority. We will provide further updates as soon as we have additional information.

Summary: We have successfully resolved the issue identified with Simpli.fi reports generated between November 18th, 4:30 PM (CST) and November 22nd, 12:00 PM (CST). Resolution Details: TapClicks has ran a refetch of all impacted data from Simpli.fi. Reports for the affected timeframe now reflect Simpli.fi corrected data for the following data sets: New Ads Geo-Fences Audience/Segments What You Should Do: If you previously pulled reports during the affected timeframe, we recommend re-generating those reports to ensure accuracy. If you encounter any discrepancies, please contact our support team for further assistance. We appreciate your patience and understanding while we worked to resolve this issue.

Simpli.fi has notified us of a potential discrepancy in the API dataset that affected select reports between November 18th, 4:30 PM (CST) and November 22nd, 12:00 PM (CST). During this period, some reports may have yielded incomplete or missing data for the following data sets: New Ads Geo-Fences Audience/Segments This issue is specific to campaigns where new Ads, Geo-Fences, or Audiences/Segments were added during the affected timeframe AND reports were generated for these campaigns. Simpli.fi has taken action to correcting this dataset. TapClicks will proactively initiate a refetch of all impacted data from Simpli.fi to ensure accurate and complete reporting. What You Should Do: If you have concerns about specific campaigns or reports generated during the impact window, please feel free to reach out to our support team. We will update this notice once the refetch is completed. Thank you for your understanding and patience as we address this issue.

Resolution: YouTube has resolved the issue on their end, and API requests are now functioning as expected. Traffic Sources data is displaying correctly for all affected instances. Thank you for your patience while this was resolved. If you continue to experience any issues, please reach out to support@tapclicks.com.

Issue: We are experiencing a global issues with YouTube with an API error for ALL call requests containing insightTrafficSourceDetail dimension. Impact: Global Users with Traffic Sources data view enabled are impacted by this error. Historical data previously stored in TapClicks is unaffected but new data may be delayed due to this error. ETA The issue is Pending with the YouTube team. We've submitted a request on the YouTube issue tracker, and standing by to assist when updates are available by our friends at YouTube.

Issue: We have identified on October 3rd, 2024 a issue with Meta Facebook Ads where Spend data discrepancies are impacting customers connected to the Facebook Ads Instant Connector. Impact: Only Spend metrics are affected; all other metrics are operational as expected. Cause: Facebook is aware of this issue and is actively working to resolve it. Resolutions and action currently is waiting for the Facebook Ads team. For more details and to track Facebook's progress, you can view their open ticket here: Facebook Support Bug [https://developers.facebook.com/support/bugs/1264146567913934/]. We will continue to monitor the situation and provide updates as soon as more information becomes available. Thank you for your patience.

Issue: We have identified on October 3rd a issue with Meta Facebook Ads where Spend data discrepancies are impacting customers connected to the Facebook Ads Instant Connector. Impact: Only Spend metrics are affected; all other metrics are operational as expected. Cause: Facebook is aware of this issue and is actively working to resolve it. For more details and to track Facebook's progress, you can view their open ticket here: Facebook Support Bug [https://developers.facebook.com/support/bugs/1264146567913934/]. We will continue to monitor the situation and provide updates as soon as more information becomes available. Thank you for your patience.

Issue: We have identified on October 3rd, 2024 a issue with Meta Facebook Ads where Spend data discrepancies are impacting customers connected to the Facebook Ads Instant Connector.Impact: Only Spend metrics are affected; all other metrics are operational as expected.Cause: Facebook is aware of this issue and is actively working to resolve it. Resolutions and action currently is waiting for the Facebook Ads team.For more details and to track Facebook's progress, you can view their open ticket here: Facebook Support Bug [https://developers.facebook.com/support/bugs/1264146567913934/].We will continue to monitor the situation and provide updates as soon as more information becomes available.Thank you for your patience.

Summary: We recently resolved an issue that affected customers using TapAccess delivery types for Smart Connectors the morning of Oct 11th. Historical data was not impacted, but the issue prevented new data from being pulled beginning last night. Resolution: Our Engineering Team has applied a fix, and the system is now functioning correctly. New data is being pulled without any problems. Impact: Only customers using TapAccess delivery types were affected. No historical data was lost. Next Steps: We are currently evaluating additional safeguards to prevent similar issues in the future. If you encounter any further issues, please contact us at support@tapclicks.com. Thank you

Facebook Insights API issues for deprecated Metrics have been moved to resolved. Previous Fetches that have failed due to these metrics have been completing successfully for the past few days of monitoring. If you are experiencing new issues, please contact support@tapclicks.com. Thank you

Update: We have implemented updates to adjust for these API changes, and the daily data fetch for the majority of customers has been completing successfully today. We are continuing to monitor the system closely to ensure consistent performance. Historical Data: All previously stored data in TapClicks remains unaffected. New Data Fetches: The majority of daily fetches are now working as expected. Deprecated Metrics: Metrics that have been deprecated by Facebook are now labeled as such in TapClicks reports. Next Steps: If you are still experiencing connection issues with the Facebook Insights API, please reach out to our support team at support@tapclicks.com so we can assist you directly.

Description: We are currently experiencing global issues with the Facebook Insights API, impacting all users of this integration. Facebook has implemented changes to their API, including the deprecation of certain metrics as detailed in their changelog and blog posts: Facebook API Changelog: https://developers.facebook.com/docs/pages-api/changelog/ Facebook Insights Metrics Removal Blog: https://developers.facebook.com/blog/post/2024/06/17/page-insights-metrics-removal/ These changes may cause disruptions or missing data for new data being fetched via the TapClicks platform. Impact: Historical Data: Any historical data that has already been stored in TapClicks is unaffected and remains fully accessible. New Data Fetches: This issue is causing delays and potential gaps in new data being fetched via the Facebook Insights API, affecting daily data retrieval. TapClicks Response: We are actively working to deprecate the affected metrics from our API calls to bypass these errors. Moving forward, metrics that have been deprecated by Facebook by this change will be clearly labeled as such in your reports, ensuring transparency and accuracy. Current Status: We are investigating the full impact of these changes and working to update our system accordingly to reflect the changes. We expect to have this completed for 9/27. We are also monitoring Facebook’s updates to ensure minimal disruption going forward. Thank you for your patience and understanding

This incident has been resolved.

Update Summary: Basis has informed us that they have made a fix on their end. Recommendation: If you are still experiencing issues pulling new data, please re-authenticate your connection to the Basis BCI data source using the new credentials provided by the vendor. We will continue to monitor the connector but if you are still experiencing this issue, please reach out to support@tapclicks.com

Issue Summary: We are currently experiencing issues with accessing the Basis BCI Early Access. This issue is impacting customers connected to Connector when attempting to pull new data. However, please note that historical data currently stored on TapClicks remains unaffected. Current Status: We are actively communicating with Basis BCI Team to resolve this issue. We are closely monitoring the situation and will provide updates as soon as more information becomes available. Estimated Time to Resolution (ETA): The resolution timeline is currently dependent on details from our Partners at Basis. Basis BCI is working to address the problem, and we will update you as soon as we have a clearer ETA. We apologize for any inconvenience this may cause and appreciate your patience as we work through this issue.

Google has made updates on their end over the weekend and API calls have been completed for TapClicks Customers connected to Google Ads.

Issue: We are currently experiencing an issue due to an error with the Google Ads API. This error specifically affects the retrieval of data for the VIDEO data view. Impact: The error impacts all accounts connected to Google Ads API. While this issue is preventing the retrieval of new data for the VIDEO data view, please be assured that all previously stored historical data within TapClicks remains intact and unaffected. ETA: Resolution time is dependent on the provider (Google). We are closely monitoring the situation and will provide updates as more information becomes available. Next Steps: We are actively tracking this issue and have engaged with Google Ads API support. We apologize for any inconvenience this may cause and appreciate your patience as we work towards a resolution.

Update: Issue Resolved. Google Ads fetches have been completed successfully for TapClicks Customers after the fix from the Google Team. If you are still noticing issues with Google Ads data in TapClicks, please reach out to support@tapclicks.com

UPDATE: Google has made an update this morning and currently monitoring customers that may have been affected. (https://ads.google.com/status/publisher/incidents/Dgkp6kgKHeiuDaUXBa5Q) On TapClick's side, we are seeing new fetches complete as well and will continue to monitor today. Thank you for your patience

Update: TapClicks Customers are still impacted by the service disruption for Google Ads API. Our partners at Google are still working diligently on a resolution. You can reference their documented status updates here: https://ads.google.com/status/publisher/incidents/Dgkp6kgKHeiuDaUXBa5Q

We are experiencing an issue with the Google Ads API, specifically affecting the Google Ads shopping reports. This outage began on August 1, 2024, and impacts many of our clients. Here is Google's outage announcement: https://groups.google.com/g/adwords-api/c/a6VvepS3MQ0 Details from Google Ads Google Ads is actively investigating the issue. As of August 1 at approximately 2 PM EDT, the following reports are down and returning internal API errors: shopping_performance_view product_group_view asset_group_product_group_view Impact on TapClicks This impacts TapClicks Customers utilizing these reports in TapClicks: The 'Shopping Performance by Campaign (no Ad Group for Performance Max reporting)' and 'Shopping Performance by Ad Group (no Performance Max reporting)' reports correspond to the shopping_performance_view and are affected. Please stand by as we wait for our partners at Google to resolve the issue on their end and will take necessary action to refetch the data when it becomes available again.

Summary: We are writing to inform our valued customers that the current incident is being closed. The resolution of this issue is dependent on Facebook's engineering team, specifically regarding the exposure of the creative preview in their API. Details: While we await Facebook's updates, we have implemented an interim solution to assist you in the meantime. We have added the following fields to your reports: Desktop Preview URL: This field provides a clickable link to the desktop preview of your creative. Mobile Preview URL: This field provides a clickable link to the mobile preview of your creative. These new fields are currently available and can be used in your reports to access the creative previews. Next Steps: We will continue to monitor updates from Facebook's engineering team and will promptly inform you once the creative preview functionality is fully integrated into their API. We appreciate your patience and understanding.

As we continue to wait on Facebook Engineering, we have added the fields “Desktop Preview URL” and “Mobile Preview URL” that can be used in reports which serve as a clickable link to the preview.”

This issue is now affecting Facebook Ads mobile ad previews as well. These previews will render fine on dashboards if you enable the "Display preview as iframe ?" option in the "Styles" section of the widget edition window. However, they will often show an error in dashboard exports, or on dashboards directly if that option is not turned on. Details can be found on the public bug report with Facebook, which you can comment on if this is affecting you to help them prioritize the resolution of this issue: https://developers.facebook.com/support/bugs/146323590885933/

Hello! We are having a global issue with Facebook Ads. The issue is that we have vendor limitations to generate Desktop Previews. When exporting to pdf, Desktop previews don't show up on several instances for several clients. This issue is happening for the Desktop Preview metric of Facebook Ads → Ads Data View. This is affecting the automated reports. This issue has been reported to Facebook via the FB developers portal but they haven't come up with a solution yet. Ticket on FB portal: https://developers.facebook.com/support/bugs/146323590885933/ Several clients are being affected. If you are one of those clients, we would encourage you to comment on the Facebook ticket above, and reach out to your Facebook representative. Since this is a Vendor bug, we will need Facebook to fix this issue and with not much of a response from their end, we are looking for different ways and channels through which we can escalate this to achieve faster resolution from the Vendor. Thank you.

This incident has been resolved.

We have deployed a fix regarding the filter issue and future scheduled reports will filter as intended. If you would like us to help resend reports that went out today with updated data, please reach out to us by emailing support@tapclicks.com Thank you

Issue: We have identified a temporary issue affecting channel filters, which may have caused discrepancies in the scheduled reports sent out today. Impact: This issue impacts customers who use scheduled reports that include custom channels. ETA: Our engineers are actively working to resolve this issue. If you observe any discrepancies in your scheduled reports, please contact us at support@tapclicks.com and we will assist you in resending the reports with accurate information.

This incident has been resolved.

Connecting new Shopify accounts: Users who are looking to connect a new Shopify connection are currently unable to. TapClicks has been in contact with Shopify to update the connector version required. Existing connections users have established are still fetching data normally. If you are attempting to connect a new Shopify connection and hitting this issue, please reach out to support@tapclicks.com if you haven’t already done so

This incident has been resolved.

All delayed email attachments sent to smart connectors should now have been processed, and our team is actively monitoring.

We have identified an issue with delays processing attachments delivered via email to Smart Connectors. Our team is investigating and working on clearing that delay. We apologize for the inconvenience.

Update: Resolved We've resent scheduled reports that were impacted and have not observed any new errors. If you have reports actively scheduled and are still experiencing missing attachments, please report them to support@tapclicks.com

A fix has been implemented and we've been closely monitoring the scheduled reports feature. We have not observed any recurring issues since the update. If you have reports actively scheduled and are still experiencing missing attachments, please report them to support@tapclicks.com

Issue Summary: Scheduled reports are experiencing sporadic failures, with some reports missing PDF attachments. Impact: The issue potentially affects all customers leveraging scheduled reports. We recommend pausing your scheduled reports until a resolution to avoid incomplete sends. ETA: TapClicks Engineering team is actively addressing this as a high priority. Progress updates will be provided as they become available.

End of Day update: Customers Impacted by the previous TTD fetches errors have completed successfully. If you are still experiencing issues with the TDD instant on connector, please reach out to support@tapclicks.com.

UPDATE: Our Partners at The Trade Desk have notified TapClicks of a fix on their end. TapClicks has initiated a relaunch of our TTD fetches for impacted customers to retrieve TTD data that had the errors this morning. We will monitor the fetches and provide updates accordingly.

Issue: We observed an error returned by The Trade Desk Instant On connection for a service error on the API. Impact: This is impacting users of the TTD API and customers who are connected to the TTD instant on connector are impacted. Previously stored TTD data before this error is still available in TapClicks. Once TTD issues a fix, a refetch will occur to update new data. ETA: We have reached out to our partners at The Trade Desk and were informed that their Eng team is working on addressing the issue. We will provide additional updates when available.

Update: Fetches have been completed successfully and behaving as expected for the majority of customers. If you are still experiencing issues or have additional questions, please reach out to our support team at support@tapclicks.com. Thank you

Update: Our partners at Simpli.fi has made a fix on their end and TapClicks has relaunched our fetch to repull data from today's fetch.

Issue: Simpli.fi API is returning errors when TapClicks calls upon the Simpli.fi API. Impact: Simpli.fi API users who are requesting similar reports are impacted. Therefore, TapClicks Customers connected to the Simpli.fi Instant On connector are also impacted. Previously stored Simpli.fi data before this error is still available in TapClicks. Once Simpli.fi issues a fix, a refetch will occur to update new data. ETA: We have reached out to our Partners at Simpli.fi and they have identified the issue and working on a resolution.

Facebook has made a fix and after relaunching, Facebook Ads fetches from yesterday have been completed to include Targeting data. Facebook Ads fetches today are running as expected. Thank you

End of Day update: The majority of Facebook Ads fetches have been completing without the targeting data as expected. TapClicks will continue to monitor and keep our communication for a resolution with the Facebook team regarding the remaining targeting data.

TapClicks has implemented our solution to pull non-targeting data set while we wait for the Facebook team to fix the issue on their end. Many TapClicks customer Facebook Ads fetches are completing successfully without the targeting dataset. We will continue to monitor the Facebook Ads feed throughout the day. TapClicks will be continuing our communication for a resolution with the Facebook team regarding the targeting data.

Issue: Facebook Ads API is returning errors in their API when requesting the 'targeting' field. Impact: This is a Global issue for any platform that calls the Facebook Ads API. Facebook has a ticket open on their end to address the issue. TapClicks Customers who are connected to Facebook Ads are affected and Facebook Ads data for today (Jan 25th, 2024) may be incomplete. ETA: Dependent on Facebook to make a fix on their end. In the meantime, TapClicks will be working on a temporary solution to pull non-targeting data.

All Simpli.fi fetches fetches with the previous errors have been completed. New Simpli.fi fetches as of today are running as expected. Thank you for your patience.

Most customers' Simpli.fi fetches have been completed today but we are continuing to monitor Simpli.fi remaining fetches today. TapClicks will continue to communicate with Simpli.fi for a full resolution.

End-of-day update: Our partners at Simpli.fi have made additional updates on their end and TapClicks has relaunched a fetch to call the Simpli.fi API again. Most fetches have shown no new errors thus far but we will continue to monitor the issue accordingly. Thank you for your patience, The TapClicks Team

Simpli.fi has made some changes to its API to address the issue but is still returning errors. We are continuing communication to work with our partners for additional support on your behalf.

Issue: Simpli.fi connector fetch error due to the data formatting returned by the Simpli.fi API. Impact: Customers who are connected to the Simpli.fi connector. This is a Global issue that is impacting platforms utilizing Simpli.fi’s API. Customers who are impacted will have incomplete data from today’s (January 24, 2024) fetch. All your previously stored historical data before this error occurred is still available. We are reaching out to our Simpli.fi partners for a solution. ETA Dependent on Simpli.fi team. We will update customers as new updates become available

Update: This issue has been resolved now by Facebook. We have also removed the tags we previously put up for the 3 fields mentioned earlier (Total Reach, Reach Last 7 Days, Reach Last 28 Days.) Data is now coming in for all fields.

UPDATE: Facebook Insights fetches have been completing to pull data via API with the exception of the three impacted metrics, Total Reach, Reach Last 7 Days, and Reach Last 28 Days metrics. While we continue to wait for FB to address these metrics in their API, we have labeled these metrics in the TapClicks application as temporarily unavailable. If you have historical reach data that has been previously stored in TapClicks, the data is still available in TapClicks. However, the three FB Reach metrics will be empty for current data until the issue is addressed on Facebook's end.

Issue: Data Fetches are failing for Facebook Insights. The issue appears to be caused by the Total Reach, Reach Last 7 Days, and Reach Last 28 Days metrics. The issue has been reported to Facebook. Link to the bug reported on Facebook developer portal: https://developers.facebook.com/support/bugs/1386901288905292/ Impact: This only affects customers who are connected to the Facebook Insights Instant-on Connector. All other data sources are unimpacted by this error. ETA: (TBD by Facebook) In the meantime, our engineering team is working on a temporary solution that will allow fetches to complete to pull data for all fields except: Total Reach, Reach Last 7 Days, Reach Last 28 Days.

We have worked on the error with our partners at Spotify and the fetches have been completed successfully for all our clients. Regarding Assets data: Spotify Ads API V2 currently only supports audio assets that are created and uploaded by customers, and not created using Ad Studio's create new audio functionality. If you have additional questions on Spotify Ads API V2 changes, please feel free to reach out to your Spotify Ads representative. Thank you, TapClicks Team

We made the recommended fix from Spotify and today's fetches have been completed without an error response. However, Assets data is still not available/being returned by the API. We are currently engaging Spotify for additional details regarding Assets data. We will provide additional updates as they become available. Thank you for your patience.

Issue: Data Fetch failure for Spotify Ads API due to an API update. We have reached out to the vendor. Impact: This only affects customers who are connected to the Spotify Ads Instant-on Connector. All other data sources are unimpacted by this error. ETA: (TBD ) We will provide additional updates accordingly.

Marchex has made a fix on their end and API fetches have been completed.

Our friends at Marchex have identified the issue on their end and are currently working on a fix regarding a degradation of service potentially impacting Marchex Call Analytics and API. ETA: Marchex does not yet have an estimated time of completion but will provide additional updates once the issue is resolved.

Issue: The Marchex API is failing due to a Fetch Error response from the Marchex API. Impact: Customers who are connected to Marchex instant on connectors are impacted. Other Instant On connectors are not impacted by this specific Fetch error. ETA: (TBD) Dependent on Marchex. We have reached out and escalated the issue with our partners at Marchex to assist with their API.

The Amazon DSP API fetch incident has been resolved. If you have questions or are still experiencing issues please feel free to reach out to support@tapclicks.com Thank you, TapClicks Team

Amazon DSP Fetches are completed with the latest fix and will continue to monitor the instant on the connector. SuperAdmin users can view their fetch status on the data load status page within their TapClicks account.

Update: We have identified the cause is due to the dimension formatting within the API call. A fix has been developed and is currently in Review. We will provide additional updates as they become available. Thank you for your patience

Impact: Clients connected to Amazon DSP are having API connection issues with the Amazon DSP connector. We have reached out to Amazon to report this issue and are awaiting their response. All other connectors besides Amazon DSP are not impacted by this incident. We will provide additional updates as they become available by the Amazon DSP team. Please feel free to escalate with your Amazon DSP representative(s) for additional support if needed.

This incident has been resolved.

Centro Basis DSP has made a fix on their end and we have relaunched our fetches for impacted customers. Customers utilizing Centro Basis DSP Instant On connectors should see data once their fetch completes. You can monitor your feed via the Data Load status page within your account. If you are still experiencing issues, please reach out to support@tapclicks.com Thank you

Our partners at Centro Basis DSP have identified the issue source on their end and are working on a resolution with their engineering team. We will provide additional information as it becomes available from our friends at Centro Basis DSP.

Issue: The Centro Basis DSP API is not passing a required field, Account ID, and causing the Centro Basis DSP data fetch to fail. Impact: Customers that are connected to Centro Basis DSP instant on connectors are impacted by this missing field. Other Instant On connectors are not impacted by this Centro Basis DSP field requirement. ETA: (TBD) We have reached out and escalated the issue with our partners at Centro to assist with their API.

We have bulk updated existing channel filters for Data Source Name = "Google Analytics 4 (Early Access)" to filter by "Google Analytics 4" instead, so widgets who were using this channel filter will now behave as they did previously. We apologize for any inconvenience this may have caused.

We have identified that Google Analytics 4 is currently limited in filtering by the service name, Google Analytics 4. Issue: The instant on connector name was changed from "Google Analytics 4 (Early Access)" to "Google Analytics 4". Users utilizing filters referencing the original name may not be filtered as intended. Example: If you have a Custom Channel that contains "Google Analytics 4 (Early Access)" AND you have a filter on a widget for that channel for Include / Exclude Data Source Name = Google Analytics 4 (Early Access)", the filter will not reflect the GA4 data source at the moment. We are currently in the process of fixing this issue. TapAnalytics/Tapreports Platform is still operational

DBM and DBM- IO (Display & Video 360) API fetches are now successfully completing with an updated API version.

DBM and & DBM - IO API is experiencing API fetch delays. We are currently looking into the 3rd Party vendor's API and will provide additional updates as they become available.

Google has made a resolution to their incident. The incident began at 2023-04-25 07:29 and ended at 2023-04-25 09:55 (all times are US/Pacific)

As Google is working through its incident Customers may be experiencing intermittent issues with multiple parts of the platform. If users are experiencing intermittent issues when logging in via the Google oAuth option we recommend users log in via their TapClicks username and password in the meantime. Google Cloud has given an ETA of a resolution within the next 1-2 hours.

We have identified that Google has had intermittent issues with their API that is impacting data feeds for users. Google has posted on their status page regarding this issue here: https://status.cloud.google.com/incidents/gsr6HAk6oCUpNG4CAZ1H#FxgErUaBEZS6pEeX6yiz. We are closely monitoring the status for a resolution on Google's end and will update accordingly.

This incident has been resolved.

Twitter has restored TapClicks' access to the API. Data Fetches for all customers will be relaunched imminently and data for today will start flowing into the system.

Twitter data for today is not flowing into TapClicks dashboards. We have reached out to Twitter to re-establish data access. No historically loaded Twitter data in your dashboard will be affected. This does not impact Twitter Ads.

The data load process completed successfully on Friday, and then again on Saturday and Sunday, and scheduled reports have been resent for impacted customers. Our team is also implementing improved monitoring to better detect similar issues should they occur in the future. Sorry again for the inconvenience.

Some clients are experiencing data load delays due to an issue with our fetch infrastructure this morning. As a result of that issue, the data load progress reported in your Data Load Status dashboard may be inaccurate today. Some scheduled reports have also been sent with incomplete data earlier today. We will be re-sending these before the end of the day or once the daily data load for today is complete on your instance. Sorry for the inconvenience.

The majority of our customer's fetches from yesterday's relaunch has completed and scheduled reports have been sent out yesterday as planned. If you are still experiencing issues or have concerns, please reach out to support@tapclicks.com. Thank you, The TapClicks Team

We are currently monitoring our re-launched fetches and scheduled reports sends for our customers.

We've identified that customers may be experiencing fetch delays that can impact scheduled reports. Impact: All customers are impacted in some capacity Customers with faster fetches have already had their fetches complete Customers with longer fetches may experience longer fetch times All Customer scheduled reports will need to be re-initiated We are currently working on making the necessary updates and will provide additional updates when available.

The vast majority (99.9%+) of data loads for today have now completed. The remaining ones, generally dealing with larger volumes of data, are running and will complete once all data has been processed.

We have identified an issue that prevented our data load infrastructure to scale up as it should have for our daily data loads today, resulting in delays. We have addressed the issue and added additional resources to go through the queue. More than half of the delayed data loads have now completed, and we expect the remaining ones to complete within a few hours. For the majority of clients, scheduled reports (if any) go out after the daily data load completes, so these will be sent after that.

We are experiencing data load delays for several customers this morning. Our engineering and infrastructure teams are investigating and we will provide an update within 90 minutes. Sorry for the inconvenience.

After close monitoring of The Trade Desk connection, we are happy to see customer feeds continuing to complete successfully. If you have any additional questions or concerns, please feel free to reach out to support@tapclicks.com.

The Trade Desk feed has been completed successfully today. We are still awaiting updates from our Partners at The Trade desk and will continue to monitor the feed to see if any additional fetch issues persist. We will provide additional updates as they become available. Thank you for your patience.

We are currently investigating The Trade Desk connection fetch issue. We have escalated to our partners at The Trade Desk to help address the issue and will provide additional updates as they become available. If you are experiencing this issue with the Trade Desk, please feel free to reach out to your Trade Desk Representative as well to share your impact.

Our partners at Google have addressed their fix and all Google Ads fetches have been completed successfully. If you have additional concerns with your Google Ads fetches, please feel free to reach out to support@tapclicks.com.

Vendor API Issue: Google Ads data fetches have been failing for some of our clients. This is a global issue affecting all other data reporting solution providers as well. Google has acknowledged the issue and is actively working on a fix. We will closely monitor and work with our friends at Google to provide further updates as they become available.

PPT extracts should be stabilized now. If you encounter formatting issues with the PPT extracts please continue to report those through the support organization and we will address them on an individual basis. Thanks for your patience as we worked through these issues.

Thanks to everyone for your patience as we continue to work through font related issues on Report Studio. As you may appreciate, it is often tedious work to identify and fix all font conversion issues for the 16 fonts that Report Studio currently supports. We have addressed many of the glaring items but are continuing to test and correct less commonly encountered problems. We are keeping this status open until we are confident that we've comprehensively addressed the reported issues and ask that you please continue to report font related problems if they are encountered with support@tapclicks.com so we can get them addressed.

UPDATE: With tonight’s March Release, we plan to release a fix for users that are using Adobe API for PPTX exports along with the Century Gothic font in reports. We will continue to work on other fonts and will provide additional updates as they become available. If you have additional questions, please reach out to support@tapclicks.com.

UPDATE: The patch this evening will include an improvement for bold fonts in Report Studio PPTX exports as a part of today's patch. Bold font support is being added back for text widgets and for certain variables that are bolded in other widgets. NOTE: For the media widget bold text will (continue) appearing as normal text. However, we hope to add support in tomorrow's planned hotfix. After today's patch, there will continue to be some known issues with how certain fonts behave when using either the PPT export preliminary solution (ie. Adobe) or the original export solution. We continue to make progress in identifying and fixing the individual incompatibilities and will update here as we continue to make progress.

Update: We push a fix for the image preview issue that users experienced when trying to export either PDF or PPTX. If you continue to experience image preview issues after the fix, please raise the issue with support@tapclicks.com

Report Studio customers - We continue to work to resolve the several issues regarding the usage of PDF and PPT exports from Report Studio. High quality, attractive report exports from Report Studio continue to be our highest priority and we will post updates as we progress through the resolution. Update 2/24/2022 -- 1 - Editing - The ability to edit elements in PPT exports from Report Studio is limited until we complete the testing/integration of the preliminary solution against all our use cases. Account managers can enable our preliminary solution for clients who encounter this problem. Update 2/24/2022 -- 2 - Font Support with the above preliminary solution. Support for the below fonts is actively being addressed. There are still some spacing and font conversion issues in reports. We are continuing to make updates/changes as they become available and will update this section as items are resolved. Century Gothic Helvetica Lato Lucinda Grand Roboto Light, Regular, Black Playfair Display Black As of the 2/24 patch all Bolded text is being reverted to non-Bold to address the legibility of the characters. Reports should be more legible when Bold characters are used. We continue to work on resolution across all font types and to bring back Bold support. Update 2/24/2022 - RESOLVED - 3 - Font Support overall - There were some inconsistencies experienced between a Report Studio exported using the application vs a Report Studio generated using scheduled reports. PDFs and PPTs exported from the platform should now behave consistently between exports from the UI and the scheduled reports.

Report Studio customers - We are aware of several issues regarding the usage of PDF and PPT exports from Report Studio. These issues began earlier this month and create several negative effects, some which seem similar to each other. High quality, attractive report exports from Report Studio are our highest priority and the team is actively working on these various issues concurrently and involving any third party tools that are used in the process. Currently we are aware of several types of issues: 1 - Editing - The ability to edit elements in PPT exports from Report Studio is significantly limited. - If you are encountering this issue we have a preliminary solution and please reach out to your account manager for help addressing this. We will be introducing some changes in an upcoming release for all users to bring back the required editability 2 - Font Support with the above preliminary solution. - Currently users on the preliminary solution who are using the following fonts in their Report Studio reports may see spacing (kerning) and changes to styling when exporting PPT specifically. We will be addressing these as we finalize the preliminary solution for release. We will provide more information as we finalize the long term solution. Century Gothic Helvetica Lato Lucinda Grand Roboto Light, Regular, Black Playfair Display Black 3 - Font Support overall - There may be some inconsistencies experienced between a Report Studio exported using the application vs a Report Studio generated using scheduled reports. Our teams internally are working to correct this and ensure the highest quality and consistent reports are available from both downloaded and scheduled reports. This applies to both PDFs and PPTs exported from the platform and we will update once this is corrected.

We believe the issue with downloading PPT files from Report Studio has been resolved for most cases. However, we continue to work on the issue to resolve the handful of remaining cases. Additionally, we continue to work with the third party service to resolve the recent PPT layer/formatting issues.

Following a change by a third-party vendor, some TapClicks clients are currently experiencing issues with downloading PPT files from Report Studio as well as changes to the structure of layers in downloaded PPT files. TapClicks is working with the third-party vendor for resolution.

Thanks to our partners at StackAdapt, a fix was implemented on their end for all impacted customers. Mapping pages are loading as expected for customers. If you are still noticing a credentials error, you may need to refresh the mapping page.

We've connected with our partners at StackAdapt and they have helped reinstated a method to help address the error message for our mutual customers interim with a rate limit to avoid large spikes to the API. We are continuing to monitor this on our end and will work with StackAdapt to address customers with a higher volume of mappings to load. Thank you for your patience. The TapClicks Team

StackAdapt: For customers utilizing the StackAdapt connection, you may be experiencing a credentials error message when navigating to the mapping page. It appears that StackAdapt may have made a change causing this error that can prevent you from making new assignments. We are currently reaching out to our partners at StackAdapt to help address this error message. Please note that this error does not impact existing mappings assignments and the fetches for today are functioning as normal. If you are experiencing this and need assistance with making new assignments, please reach out to customercare@tapclicks.com.

We have an interim solution in place to fetch Simpli.fi data via the API with Simpli.fi's recommendation by querying the data at a later fetch time (9 AM EST) when there is less traffic. We will be closing this post as fetches have been completed successfully but will continue to partner with Simpli.fi for future enhancements to optimize the fetch schedules. If you continue to experience issues with your Simpli.fi data, please reach out to support@tapclicks.com.

We were provided some additional information from Simpli.fi about their reporting API updates. We have relaunched fetches for customers affected per Simpli.fi's recommendations and will continue to monitor the feed.

Simpli.fi is still investigating on their end regarding our connection to their API. Simpli.fi does not have an ETA on this but it’s actively being worked on and is a top priority for the Simpli.fi engineering department. We will post additional updates as they become available Thank you for your patience as we continue to work through this with our partners at Simpli.fi.

As we continue monitoring Simpli.fi fetches, we are still noticing some intermittent failures. We have reached out to Simpli.fi for additional feedback for further assistance with their API. We will post additional updates as they become available.

Simpli.fi has reverted some code changes on their end in regards to the suspected fetch timeouts. We are currently monitoring our fetches with the Simpli.fi API to see if the timeouts persist.

Our partner’s at Simpli.fi identified a deployment that went out on March 28th that is believed to be affecting the time it takes to return the API query results. Simpli.fi is currently in the process of addressing this on their end. We are currently awaiting further updates from the Simpli.fi team and will alert customers accordingly as information becomes available.

Some customers may be experiencing issues with their Simpli.fi data fetches for large datasets with the Simpli.fi API. Our Technical team is currently working with our Partner at Simpli.fi for a path forward of addressing the API calls as an enhancement request for large datasets. If you are experiencing issues pulling Simpli.fi data via API, please submit a ticket to support@tapclicks.com if you haven’t already done so.

This incident has been resolved.

We are happy to update that the migration error message has been resolved. For customers that are experiencing additional issues with Google Ads not related to the API migration error fetch message, please file new tickets accordingly with support@tapclicks.com. Thank you

Progress: Majority of customers with the migration fetch error messages have been completed and we are still monitoring remaining fetches. If you are experiencing unique Google Ads issues outside the migration script error message, please be sure to submit a ticket with support@tapclicks.com

Thank you to all customers for your patience so far as part of the Google Ad's API update. We are still currently monitoring the Google Ads API which is still taking some time.

We are currently monitoring API migration fetches to complete for customers connected to Google Ads. We are seeing progress in the fetches and will provide further updates as they become available.

Some clients may be experiencing fetch failures for Google Ads as part of Google Ad’s API updates. Our team is working diligently to fetch the data. If you are experiencing Google Ads fetch issues, please submit a ticket to support@tapclicks.com if you haven’t done so already. We will post a status update as it becomes available.

We have successfully been receiving Simpli.fi data with our most recent fetches from Simpli.fi. If you are still experiencing issues with your Simpli.fi data feed, please reach out to our support team, at support@tapclicks.com.

We have identified that customers utilizing the Simpli.fi connector may be experiencing some data connectivity issues. We have reached out to our partners at Simpli.fi and provided them with the information they need to investigate the issue further. If you are experiencing an issue with your Simpli.fi data, please feel free to also connect with your Simpli.fi representative regarding your usage of the Simpli.fi connection into TapClicks.

This incident has been resolved.

We have identified the software issue that resulted in scheduled reports with missing or empty attachments this morning: a recent update to our PDF generation tool caused problems on a fraction of our servers, resulting in blank PDF and PPT attachments. We have now addressed the issue. We have resent scheduled reports for several instances that were impacted by that. If you still have scheduled reports that you would like to have resent, please let our support team know. Thanks and sorry for the inconvenience.

Some clients have reported receiving scheduled reports with no attachments this morning. Our team is investigating and we'll provide an update once we've identified the cause of the issue.

The incident was closed by Google - https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh

Our infrastructure has been running normally for the last 60 minutes, but the Google incident is still open, so we are monitoring and waiting for them to close the incident at https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh before doing the same here.

Google posted an update. You can follow their incident status at https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh Note that some of our services are currently coming back online.

Some of our services are currently experiencing downtime due to a Google Cloud outage. Etsy, Spotify and Snowflake have also been reporting issues. We will provide updates as we get them from Google. Sorry for the inconvenience.

This was resolved by reverting the API version back to V1.

TapClicks has pushed the updated code and data is beginning to flow in for any instances that experienced interruptions. As a reminder, the previous Twitter V2 API that included Impressions, Clicks, and Video metrics on the Tweet level will render 0 until an alternative solution is coded and pushed. TapClicks will plan to reinstate these metrics in a future release, when a more scalable solution against the V2 API is scoped and executed. Thank you!

Customers leveraging Twitter data in their dashboards may have experienced a lag in data, particularly in regards to Tweet data. The issue stems from an API upgrade from the August release and the team is working to resolve the issue by reverting to the previous Twitter API Version. TapClicks will revert the API version back to V1 to ensure legacy KPIs are updated in the system and plan for an alternative solution for the Twitter V2 API upgrade in the future. Once reverted, any recently exposed Tweet KPIs around Impressions, Clicks, and Video performance will reflect "0" values. If you have any questions about this issue, please feel free to reach out to data-quality@tapclicks.com, customercare@tapclicks.com, or your Customer Success Manager.