Due to a recent service interruption, the Drift team has compiled a list of frequently asked questions (FAQs) to address concerns about the status of Drift's services and its impact on your website.

This document provides clarity on what to expect, how to manage your website's interaction with Drift, and the implications of the outage.

---

Q: Is there a vulnerability with the Drift JavaScript on my website? 

A: No, there is no vulnerability.

The current service interruption is not related to any security issue with the Drift JavaScript. Your website is safe to use the JavaScript snippet.

---

Q: Should I remove the Drift JavaScript from my website while the service is down? 

A: We recommend you keep the Drift JavaScript on your website. When the service is back online, your chat widget will be ready to go without any additional steps.

---

Q: Will the Drift JavaScript cause performance issues on my website while it's offline? 

A: No. The script is designed to fail to load immediately, so it will not cause any issues like render-blocking or other performance degradation.

---

Q: My team is seeing console errors related to Drift. Is this a problem? 

A: No, this is expected behavior.

The console errors you see are a result of the script failing to load, and they are not visible to your site visitors. This is an internal issue that does not affect the user experience.

---

Q: What if we have custom code that uses the Drift API?

A: If your team has any proprietary functions that use the Drift client-side API, we recommend you evaluate them to ensure they do not cause any execution failures or render-blocking issues while the service is offline.

---

Q: What will users see when they try to access app.drift.com URLs?

A: Users will likely see a system-level error, such as a 403 or 404 status code, because the CloudFront distribution that serves the website will be inaccessible. The system won't be able to show a user-facing error page because every part of the site, including static assets like images and CSS, will be blocked.

---

Q: Will other Drift-related links, such as Conversational Landing Pages (CLPs), Drift Links, profile links, and calendar links, also show this same error?

A: Yes, all of these links will also result in system-level errors. 

The underlying infrastructure for all these services will be inaccessible, leading to the same kind of 4xx errors. Drift Links specifically will also throw console errors and not function.

---

Q: What do we do with our live links like CLPs/Driftlinks/Drift Profiles/Calendar links in email signatures during the outage?

A: During the Drift downtime, these links will be non-functional. 

We recommend temporarily removing these links from use across all content sent outside the business (campaigns, emails, etc.) and from websites. 

For any links that are HREF or anchored on the website, we recommend temporarily pointing those references / anchors to forms that can be used to contact your company directly.

---

Q: Can you help us update our website links? 

A: While we cannot make changes directly to your website source code, we would be happy to work with your Web Development team to ensure that any questions they have about updating HREFs or anchored links.

---

Additional Resources

For the most current updates, subscribe to the Salesloft Trust Portal.