Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Co-browse - retiring Firefly ( domain

Updated on September 5, 2022

This content applies only to Pega Cloud environments

Co-browse- Moving customers off from Firefly ( domain

What does this mean?

Pega Co-browse team is in the process of sunsetting old servers/domains run on a technology stack that cannot be updated to keep up with latest functionality and security requirements. Clients using Pega Co-browse product on Firefly domain must move to using the new domain, as the old firefly domain ( will be shut down in next 2 months, October 30, 2022


Domains to replace

  • to 
  • to 
  • to 
  • to 


Steps to move to domain 

  • Confirm if you are using firefly domain 
    • If the Co-browse server you are using has the domain name, for any of the environments (UAT/PROD).  If this is true, then you need to do the following steps mentioned below in order to move to domain. This is applicable for both standalone Co-browse or Integrated with Pega Customer Service. 


  • Move to new domain 
    • Standalone Co-browse 
      • Login to dashboard using domain. 
      • Replace the snippet everywhere in the website with the new snippet you get after login to the dashboard using domain. 
    • Integration with Customer Service 
      • Switch to app studio 
      • Under general settings in co-browse modify the server URL to domain 
      • If using 
  • Co-browse from phone: Login to the dashboard using domain. Replace the snippet everywhere with the new snippet you get after login to the dashboard using domain 
  • Co-browse from chat: Download the chat bot again, and replace the existing chatbot if using browse from chat 


If you have any issues related to moving to the new domain, reach out to your respective Pega account team.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us