How to implement the deployment tag on my website?

What is a deployment Tag ?

The deployment Tag allows you to correctly trigger and display your surveys on your website, according to the rules you have previously defined (in particular via scenarios of your website deployment type).

It also allows you to capture information about the visitor's behavior that is necessary to evaluate the conditions under which your surveys are displayed (such as visited pages, time spent, visitor information etc..). 

It is intended to trigger your surveys at the best time during a visit to your website.

Where Can I find the Tag ?

You will find your Deployment tag in the Menu >> "Settings". 

Then "Deployment tag" in Deployments category.

Note: Make sure you have created your Domains before configuring your trigger tags (otherwise you will not be able to do so).

The MyFeelBack Javascript tag controls the display of questionnaires according to the rules you have defined in your website deployments and captures information on the visitor's behaviour (pages views, time spent, information on the visitor, etc.), which is necessary to evaluate the display conditions of your questionnaires.

We advise you to involve a developer from your technical team to integrate the code.

It is recommended to use a tag management system for its installation.

 

Tag example

<script type='text/javascript'>
window._Mfb_useCookie : true;
window._Mfb_ud = {

var1 : undefined,
var2 : undefined,
varN : undefined,
_context : {

lang : undefined,
privacyMode : false,
_page : {

url : location.pathname,
storageDuration : 30
// remove this if not used
pageProperties : {

property1 : undefined,
property2 : undefined

}

}

}

};
(function() {

var mfb = document.createElement('script');
mfb.type = 'text/javascript';
mfb.charset = 'UTF-8';
mfb.async = true;
mfb.id = 'MFBActor';
mfb.src = 'https://actorssl-5637.kxcdn.com/actor/XXXXXXX/action';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(mfb, s);

})();
</script>

Installation on a standard website

Integrate the code from your account settings on all the pages of the site corresponding to the domain name associated with the tag. It must be placed just before the closing of the body tag.

During the integration of the code, "undefined" must be dynamically valued via the system of variables of the site or of the dataLayer for each defined variable.

For each page of the site, a Javascript resource is downloaded asynchronously. When this resource is loaded, the trigger rules are automatically evaluated.

Integration on a Single Page Application (SPA)

Integrate the code from your account settings, to the main page of the application corresponding to the domain name associated with the tag. It must be placed just before the closing of the body tag.

During the integration of the code, "undefined" must be dynamically valued via the system of variables of the site or the dataLayer for each defined variable.

When the application is loaded, a javascript resource is downloaded asynchronously. When this resource is loaded, the trigger rules are automatically evaluated.

To activate the evaluation of the trigger rules when the screen or context changes, it is necessary to update the properties of the _Mfb_ud variable and then to launch the evaluation by calling a javascript function made available by the tag.

1. Update of _Mfb_ud variable

<script type='text/javascript'>

window._Mfb_ud = {

var1 : undefined, 

var2 : undefined, 

varN : undefined,

_context : {

lang : undefined,

privacyMode : false,

_page : {

url : location.pathname,

storageDuration : 30

// remove this if not used

pageProperties : { 

property1 : undefined, 

property2 : undefined

}

}

}

};

</script>

2. Evaluation of trigger rules

    <script type='text/javascript'>

    if(typeof MFB !== 'undefined') {

    MFB.start() ;

    }

    </script>

    Better understand the content of my tag

    If you're curious to know a little more, here's an example of a trigger tag (not to be tried on your site):

    <script type='text/javascript'>

    window._Mfb_useCookie : true;

    window._Mfb_ud = {

    var1 : undefined, 

    var2 : undefined, 

    varN : undefined,

    _context : {

    lang : undefined,

    privacyMode : false,

    _page : {

    url : location.pathname,

    storageDuration : 30

    // remove this if not used

    pageProperties : { 

    property1 : undefined, 

    property2 : undefined

    }

    }

    }

    };

    (function() {

    var mfb = document.createElement('script');

    mfb.type = 'text/javascript';

    mfb.charset = 'UTF-8';

    mfb.async = true;

    mfb.id = 'MFBActor';

    mfb.src = 'https://actorssl-5637.kxcdn.com/actor/XXXXXXX/action';

    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(mfb, s);

    })();

    </script>

     

    Site variables and attributes

    window._Mfb_ud = {

    var1 : undefined, 

    var2 : undefined, 

    varN : undefined,

     

    When the code is integrated, the properties (var1, var2, in the example etc.) defined as "undefined" at the first level of the object_Mfb_ud must be dynamically valued via the site's variable system or the dataLayer. 

    These properties will be used to define the rules for displaying the questionnaires and are associated with the respondents' answers if they are declared as attributes within the solution.

    Their name is defined during integration and must correspond to the system name declared in the solution if it is an attribute.

    This information can be used in the "Attributes" or "Site Variable" conditions.

    Language management

    lang : undefined, // You can force the language of the survey.

    This block allows you to manage the translation if you have translated your campaign into several languages. If you leave this content undefined the language will be the one defined in the deployment, the browser language or the original language of the questionnaire.

    The "undefined" placeholder must then be replaced by the language code in ISO 639-1 format, for example "nl", followed if necessary by the country code in ISO 3166-1 format, for example "nl-BE".

    Browsing history management

    _page : {

    url : location.pathname,

    storageDuration : 30

    // remove this if not used

    pageProperties : { 

    property1 : undefined, 

    property2 : undefined

    }

    }

    This block allows you to configure the collection of the browsing history of visitors on which triggering rules can be based. 

    • url : url of the visited pages. By default, the tag uses the standard javascript function to value this property. It is possible to value it with a specific variable of your datalayer if the management of your pages is specific.
    • storageDuration : storage time in days - value accepted from 0 to 30. This is the duration, expressed in number of days, of the visitor's browsing history. 30 being the maximum value accepted.
      You can set the parameter to 0 to store nothing in this key if you do not base any triggering on a browsing history (previous visits).
    • pageProperties : If necessary, you can add specific properties for each page. These properties will be kept in the history. Trigger rules on the browsing history can be based on these properties. This object can be removed if it is not used.

    This information can be used in the "Number of visits" or "Page visited" conditions or in the case of a scope on the browsing history.

    Sharing information between 2 sub-domains

    window._Mfb_useCookie : true;

    By default, the tag shares certain information, on which the triggering conditions are based, between the sub-domains that may make up the same site via a cookie.

    If the path on your site is composed of the same domain (same sub-domain), this cookie is not necessary. You can deactivate its use by setting this parameter to "false".

    window._Mfb_useCookie : false;

    Privacy mode

    privacyMode : false

    This allows the operation of the tracers used by the tag to be adapted according to the Internet user's consent to the use of cookies.

    If the privacyMode is activated, the information stored by the tracers cannot be read during subsequent visits by the user to the website, except for the technical information that is essential for the proper functioning of the device (such as the management of the request).
    This parameter is deactivated by default.

    To activate it you can set it to "true".

    privacyMode : true

     

    If the privacyMode parameter is activated, the browsing history is no longer kept (StorageDuration:0) and the sharing of information between two subdomains is deactivated (window._Mfb_useCookie: false).

    Thus, scenarios with trigger conditions based on browsing history (Page visited on a history and Number of visitors since N days) will not trigger a questionnaire.

    Want to start? Click here