Integrating the companion into your web app

Learn how to integrate the tiq companion into your web app and see the differences between script integration and injection with the extension.

Need help on choosing how to integrate the companion? 🤨 Don't worry, we got you.

🚨 There are mainly two different ways of integrating the stagewise companion into your web-app.

You can either inject the companion via a script tag, which means you would have to change the source code and redeploy your web-application: <script defer src="https://gettiq.com/companion/tiq-companion.js" />
Or you can install the stagewise browser extension, which will inject the companion into the webpage on the fly

Choosing the right method completely depends on your needs.

The main difference to keep in mind is that:

while with an integration via extension, the companion will only show up to users that have installed the extension and are member of a project with the visited URL.
an integration via script tag will show the companion permanently to every user that visits your web-app.

Use cases for using the extension are:

you work in a company whose product is related to a web-app or online shop and you want to boost your in-house feedback- and issue-management 📈
you want to start a review on a web-app but are lacking access to the source code and deploy pipeline 🚫

Use cases for integration via script tag would be:

you work in a web agency and enter the feedback stage of a project where you just developed and deployed the first version 🎨
you want to engage beta users to leave feedback on your web-app or landing page 📝
Keep in mind that users will be shown the toolbar, but they need to have a stagewise account and be part of the project
Using the script tag allows users to interact with your stagewise sessions without having to install an additional browser extension.

If you still struggle to decide, just leave us a mail and we will develop the best fitting solution together. Don't hesitate.