The Journey module is used to track visits on your website. This data is sent to your DI project. In this article, we will see how to configure your website and connect visitors, allowing you to collect data on your website's visitors.
→ Learn More on Journey
**Take note that there may be a delay of up to 24 hours before the statistics appear.
Step 1: Add the Website
Start by going to Configuration:
Click Create a Journey site. Then, enter a name for your site and specify at least one domain for the website you want to add tracking:
It is not necessary to put the "www.".
Adding a consent banner
If you want to display a banner so that visitors can either accept or refuse to have their visits tracked, check the option Wait for visitor's consent to start tracking.
This option will prevent the first visited page from being tracked, therefore giving visitors the time to read your cookie information banner and decide whether to accept or refuse it.
When this option is not enabled: all visited pages are tracked, starting with the first visited page.
When this option is enabled: behavioral tracking can only occur after the first visited page, depending on the visitor's consent response. If they accept cookies, all visited pages will be tracked, and if they deny it, no visited pages will be tracked. Know that if visitors ignore the consent request or do not reply to it, they will be deemed to have accepted that their visits be tracked.
*Take note that the display and creation of this banner is your entire responsibility. This banner should offer consent and explain how cookies are used on your site and what data protection options you offer.
|
Step 2: Add the Script
In the website configuration page, there is a script to integrate into your website. You must copy-paste the tracking code on each site page you wish to track in the <head> of the message, or right before the end tag of the body </body>.
Only pages that include this tracking code can be tracked and return results on the source of the visit and the number of visitors in Dialog Insight.
E-commerce indicators
If your site has an online store, you can add these extensions to track these indicators:
You will need to add scripts for the involved pages. By clicking Usage, you will have an example of the script and precisions on the extension.
The status will change when known visitors' data will start to come in (see next steps). Meanwhile, you can verify the visited pages history (data normally has a delay before it is displayed).
Step 3: Generate Known Visitors
Method 1: A link in an email
To generate data on known visitors in your project, you can share the link from your website by sending an email to contacts. Thus, contacts who visit your website by clicking this link in your email will become known visitors. When a contact clicks the link, parameters are injected in the URL using the Dialog Insight Tracking injection rule (→ Learn more on injection rules).
You must first activate the Dialog Insight Tracking rule by going to the Additional options:
In Link tracking, check the Dialog Insight Tracking rule:
Then, add the link to your website in an element from the email (for example in a button):
You could test the email by sending it to yourself (this test will count in your stats, including your visits).
→ See the Guide on Email Validation and Tests
Method 2: Login platform on the website
If you have data from logged-in users on your website and want to send this data to your DI project, you must add another script after the main Journey script.
If your primary key is the email
function OFSYS_Tracking_onload()
{
DI.Journey.Set("f_EMail", "bob@dialoginsight.com");
DI.Journey.Track();
}
If your primary key is the client number
function OFSYS_Tracking_onload()
{
DI.Journey.Set("f_ClientNumber", "14534234");
DI.Journey.Track();
}
Results
When visitors start visiting your website, the website status will change to
. The global stats for the project and for the website will start to come in your project analytics.
→ Learn more about Journey results
**Take note that there may be a delay of up to 24 hours before the statistics appear.