In this article, we'll do a step-by-step guide on how to setup Watchtower and getting people using it!

To get setup, you need to create an instance. An instance simply represents a website, product, app or any website.

To get started with Watchtower, follow the next steps:

[Gif of the steps mentioned above]

Now you will be taken to the main Watchtower page where all your created instances will be listed.

To create an instance, you need to click on the New Instance in the top right corner. This will trigger the instance creation wizard which you will need to complete. To do this, you need to follow the next steps:

Your domain name typically represents the website, product, app or company name. ie. Effective Experiments, United States Postal Service, SpaceX etc

When specifying the domain URL, it's important to only add the index page of your website or app, no subpages should be included in the domain url. ie. https://effectiveexperiments.com, https://usps.com, https://spacex.com

When external users sign up to use Watchtower, either your wider team or an external client, they will need to enter an email they're using. You can control which emails can sign up to use a particular instance of watchtower. ie. gmail.com, outlook.com etc

Select the projects you want to include in this instance. This could be a single project or multiple projects spanning across a certain team or division.

Voilà, you have now create your first instance and you're one step closer to seeing real-time experiments on your website.

Watchtower looks for any Live experiments that are running or a particular page of your website. In order for Watchtower to find those experiments, you need to map the website URLs with the relevant Page Types/Categories

To start mapping URLs, you need to click on Add New URL. This will open the option for you to configure a new URL, you can follow the next steps

Select the Page Types/Categories you've created within your project. These Page Types will be linked to the experiments you've previously created and this will be used to map to certain URLs of your website, product or app. You can map as many page types to a URL as you want.

Choose the URL to link to the corresponding Page Type/Category you've selected. ie.

And... Done! You have now successfully mapped your website/product's URL and Effective Experiments will start checking for experiments matching this criteria

To see how this all works, you first need to download Watchtower. Once you have added this to your browser, you can login using your normal Effective Experiments login details.

Once you've logged in and Watchtower is active, you can start visiting the various pages you've specified within Watchtower. Once an experiment is found, you'll see the count indicator on the browser extension, indicating how many experiments have been found.

When you open the extension, you'll see all the experiments that are found on that particular page

Once an experiment is found, you can see the basic details and then you can click on one of the experiments in the list to be taken to a shared view with all the relevant details of that experiment.

If you don't see any badge on Watchtower, you can safely assume that this page has no experiments or it has not been configured yet.

If the particular domain you're visiting is not configured, Watchtower will tell you that. This means that you won't be able to see any live experiments on this domain. You will then need to either create an instance for this domain or visit a domain that has been configured.

Now that you have setup Watchtower and you've mapped your URLs, you can now have your team, or anyone external team member/client you want, to access Watchtower and see Live experiments running.

Your team can access Watchtower with 2 methods. You can see how both work below

This is for any user that does not have access or login detail to Effective Experiments. These users will rely on the token to login and check where experiments are running.

This is for users that do have access (login details) to Effective Experiments. These users won't be able to use a token. They will be required to use their emails to login to Watchtower.

Once you have everything setup and your team or external clients have downloaded the Watchtower browser extension, you can start to track & monitor overall engagement

Single Instance Engagement Stats are limited only to the users that made use of the public access token. This means that all these users are external users. To see who's been making use of the Watchtower Extension, you can follow the next steps:

You can also track the engagement of all the users that used their Effective Experiments emails to login to Watchtower. These engagement stats are not limited to a single instance, instead it's tracking their activity across all instances. You can find their engagement stats by following the next steps:

There are a few ways you can manage the overall access to an instance, either on an instance level or user level. See the details below:

If you don't want anyone to track experiments on one of your specified instances, you can switch off the entire instance. This means that no one will be able to see any live experiments when visiting Watchtower. This is useful as you don't need to delete your instance completely.

If some of your team members or clients have left and you don't want them to access Watchtower anymore, you can revoke individual user access. This means that these users won't be able to access any data when logging into Watchtower.

NB. You can only revoke access to external users. All internal users will keep having access until they're removed from the project or account