Adding a website
The first time you log in to the dashboard you will be prompted to Add a website. Follow the instructions and remember to choose https:// if you use secure connections (SSL).
If you do not get this popup follow this link to see how this is done.
As an account owner (or a user with user management rights), you have the possibility to invite users to two different levels and with different rights (view/edit/user management) at that level.
If you are invited/invite to an account, all websites and projects in that account are also shared with the same right level as the account. Read how to invite a user on account level here.
If you are invited to a website you get access to all projects on that website. Read how to invite a user on website level here.
Fetching the implementation script
You need to add a website to be able to fetch the implementation script that you need to add to your website to link it with Symplify. This will make it possible to create projects and run them on your website.
After you added the website you can fetch the implementation script and add it to your website. Remember that this script contains a unique ID that is connected to the website so if you add multiple websites you need to fetch the script for each one and add the script with the correct ID to each website.
Select if you want to add jQuery or not
Set Audience mode
Script execution mode
Select Google Analytics integration
By default, Symplify will automatically send events to the Google Analytics property installed on your website. If you do not want that you can go to website settings and turn this off (My websites -> click website -> Edit website -> Tracking -> uncheck "Enable Google Analytics sync"). You can later turn this on for specific projects in the settings for each project.
Notice that if you have multiple GA properties implemented on your website we will by default send to all of these. If you do not want this you need to specify which one you want us to send the events to.
GA4 implemented via GTM?
If you have implemented GA4 via GTM you need to set up a custom Trigger and Event for us to be able to send to your GA4 property. See how to set this up.
If it will take some time before your developers/platform provider will be able to add the implementation script to your website you can still use our tool in the meantime by installing our Chrome extension. With this installed you are able to create and edit projects as if the implementation script was on your website. This can be a good way to test out the tool and also to create projects so that they are already ready to go live when the implementation script is added to your website.
Note: You won't be able to go live and collect data with any projects before the implementation script is on your website. The projects you make can only be edited/previewed on computers that have the extension installed.
Check if the script is implemented correctly
If you have added the implementation script on your website you can test that it is implemented correctly by creating a project and see if you can open up an editor for that project. If you click the project you've created and choose Edit in the menu an Editor should open up. If this does not happen or if you get the "Install SiteGainer Chrome extension" popup (see image below) there might be something wrong with the script installation.
To test this further please try to open up a preview of the project instead. You do this by clicking the project and selecting Preview. If you can open a preview and get the preview bar at the bottom the script is implemented on the website.
If the script is implemented with Google Tag Manager (GTM) our script control (that runs when you try to open an editor) fails. This does however not mean you can't use the tool, you can prevent our script control in order to use the editor.
If you do not get the preview bar at the bottom of the preview you can try more ways to check if the script is installed correctly on your website.
NOTE: that we do not recommend adding the script with tag managers because of the negative effect on performance. Do not implement the script with Google Tag Manager, this will make the script load after your website is loaded, making any changes you do also appear after your website is loaded, which might cause "flickering".
Read more about how to prevent flickering if you've added the script in <head>.
Create your first project
Creating projects in Symplify is easy and you will go through the same steps no matter what type of project you create so you will recognize these steps after creating your first. The steps below are for an A/B test but is mostly the same for all types of projects.
- Create project
- Edit project - Make your changes in the editor
- Set audience to target only the visitors that visit the page where your changes happen.
- Test your audience - this is important not only because you do not want your changes to be executed on pages that you don't want them to but also you do not want to track visitors that never see your changes.
- Set goals/KPI's
- Test goals
- Preview project - make sure that your changes look good on all devices/browsers (that your target with your audience).
- Activate project - start serving the project to your visitors and collect data.
- Pause (stop) project - when enough data has been collected and you have a statistically correct result
- Check result - check your primary goal/KPI to see if the variation is a success.
- Convert to personalization - if you have busy developers and there will be a while before you can implement a winning variation you can convert this to a Personalization and let us host this for you in the meantime. Converting a winning variation to a Personalization will duplicate the variation (and audience settings) in your A/B test and serve this for 100% of the traffic on your website. You can now find this under Personalizations.
Note: Remember to pause the personalization before your developers implement the changes on the website, otherwise they will be served the changes from us and it will be hard for them to tell what's what and what to implement.