Contact monitoring – the principles of operation and the scope of collected data

The creation and monitoring of behavioural profiles is a thing of key importance in Marketing Automation. This functionality is a distinctive feature of marketing automation systems, its advantage over classic CRM and traditional systems for mass traffic analysis is what sets it apart.

Information on contact activity on the monitored website is obtained by SALESmanago from three basic sources:

  • tracking files (cookies)
  • visitor IP addresses
  • additional HTTP/HTTPS protocol data

What must be done in order to start tracking contacts 

Website monitoring can only start after a monitoring script is added into the code of every page on the website. The monitoring script can be found in SETTINGS -> INTEGRATION.

md
Every SALESmanago client has a unique monitoring code. If you want to monitor multiple websites, add the same monitoring code onto each one of them.

After adding the code wait for first corporate or identified visits – the code will then send this information to SALESmanago and it will be displayed on the dashboard. Depending on the volume of traffic on the website, it may take from a few minutes to several hours – if no visits have been recorded after that period of time, the code may have been added incorrectly. Learn more on how to paste the monitoring code.

This is all you need to do to make the code start collecting the behavioural data of your contacts. Advanced users will definitely appreciate some information on the script operation mode – it loads asynchronously so it will not slow down your website.

The first and most important source of information is common cookies.

Cookie – various types and collected data

Cookie file type Target Collected data If possible and how not to give permission
Smuuid Tracks anonymous visits; it is assigned to anyone who lands on the website Unique ID – cookie itself does not contain any information that enables to identify contacts and to recognize e.g. personal data of the website visitor. Connection to the contact card takes place in the SALESmanago system. Cookie automatically added by SALESmanago script – the only way possible not to give a permission is disabling cookies in a browser
Smclient Assigned to the identified and monitored contacts Cookie itself does not contain any information that enables to identify contacts and to recognize e.g. personal data of the website visitor. Connection to the contact card takes place in the SALESmanago system. Cookie automatically added by SALESmanago script – the only way possible not to give a permission is disabling cookies in a browser.
smform Handles contact forms and pop-ups Information about form and pop-up behavior- a number of visits, timestamp of the last visit, information about closing/minimizing pop-ups Cookie automatically added by SALESmanago script – the only way possible not to give a permission is disabling cookies in a browser.
smg Identifies a user Random ID in UUID format Cookie automatically added by SALESmanago script – the only way possible not to give a permission is disabling cookies in a browser.
smvr Stores information about visits (coded base64) Values coded by base64 Cookie automatically added by SALESmanago script – the only way possible not to give a permission is disabling cookies in a browser.
smwp Information about Web Push agreement forms True/false value Cookie automatically added by SALESmanago script – the only way possible not to give a permission is disabling cookies in a browser.
Smg Identifies a user- global ID for the whole system Random ID in UUID format Cookie automatically added by SALESmanago script – the only way possible not to give a permission is disabling cookies in a browser.
smrcrsaved Saves information if an ID was signed to SALESmanago (deprecated) True/false value Cookie automatically added by SALESmanago script – the only way possible not to give a permission is disabling cookies in a browser.
smOViewsPopCap Saves information about pop-up capping SM:X|, where X is replaced with a number Cookie automatically added by SALESmanago script – the only way possible not to give a permission is disabling cookies in a browser.

Additionally, we add the following parameters to the emails and links included in the mailings :

– smclient (id of a monitored contact),

– smconv (id of the mailing from the SALESmanago system),

– smlid (id of the link clicked by the contact),

– smpid (id of the product from dynamic emails sent from SALESmanago),

Apart from that, the UTM parameter is added as well.

Data obtained from IP addresses

The IP address a visitor uses to access the website is assigned to a particular country, province and town. This offers a high likelihood (not certainty – some connections are redirected between several addresses, which may generate misleading data) of the contact being identifiable by town or city if the contact has already been added to the database.

Additional data obtained from HTTP/HTTPS protocol

The request sent in an HTTP protocol contains other useful information on the contact – SALESmanago will read and add it to the behavioural profile of an identified user. Such information includes:

  • the browser and the operating system the contact used for visits,
  • details of an entry source – information sent through the so-called referer that identifies the original website, from which the user has been redirected to the monitored page,
  • information on searched phrases – unless the contact uses search engines in incognito mode, SALESmanago will receive key phrases the contact used to find your page. While using Google, the contact cannot be logged into their Gmail account, as the browser switches into the protected mode and information is not sent outside (similar limitations apply to Google Analytics users).
Submit your review
1
2
3
4
5
Submit
     
Cancel

Create your own review

Average rating:  
 0 reviews