The LivePerson Tag. Technical Data Sheet. Document Version: 1.0. December 2012

(1)

Technical Data Sheet

The LivePerson Tag

Document Version:

1.0 December 2012

(2)

2

Technical Data Sheet The LivePerson Tag

Introduction

The LivePerson Tag enables you to implement innovative LivePerson products and

applications, and the ability to monitor your website traffic, without the need to continually retag your web pages. The tag consists of a small piece of code which should be embedded in each page of your website. This is to facilitate embedded content being dynamically

deployed to your site

Note: LivePerson strongly recommends that the LivePerson Tag is pasted on all web pages in your site,

directly after the opening <body> tag.

The LivePerson Tag replaces the LivePerson Monitor Code in order to provide more than just monitoring capabilities but can dynamically load other tags (knows as taglets) which can be called to the web page.

Benefits of the LivePerson Tag

Deploying the LivePerson Tag serves a number of benefits, some of which are listed below: ) Precision: Serves engagement content inline for better alignment between the

experience on your site and LivePerson's engagement application.

) Speed: Optimized geo-routing routes the visitor to the closest server for better page performance and higher availability.

) Control: Tag everywhere and control where and when engagement applications are activated on your site, based on the sites sectioning. There will avoid calls to IT to turn applications on and off.

) Flexibility: Tag once and automatically upgrade to any future LivePerson capability

without retagging your pages.

(3)

3

Accessing and Implementing the LivePerson Tag

There are a few options to implement the LivePerson Tag onto your website: ) Paste the LivePerson Tag on each page of your site. See the section “Manual

Implementation of the LivePerson Tag” on page3. (Recommended for customers with smaller websites).

) Use a link to the mtagconfig.js file and paste these links to the file within each page of your site. See the section “mtagconfig.js Implementation per Page” on page5.

) If your site uses a common header file you can paste a link to the mtagconfig.js file. This will automatically place the LivePerson Tag on all the pages of your site. See the section

“mtagconfig.js Implementation per Site” on page5.

Note: In all of these scenarios we strongly recommend that you paste the code directly after the opening

<body> tag.

Manual Implementation of the LivePerson Tag

The LivePerson Tag is accessed via LiveEngage.

To access and implement the LivePerson tag:

1 Log into LiveEngage. The home page is displayed.

2 Click the link Get it here from the LivePerson Tag area.

(4)

4

3 Copy the LivePerson Tag HTML code and paste the source code directly after the opening <body> tag in all of your web pages. As shown below. (You can click show here to open this explanatory window).

4 Click the OK button or Cancel to close the LivePerson Tag window.

(5)

5

mtagconfig.js Implementation per Page

Instead of pasting a block of code within each page of your site, you have the option to paste the LivePerson Tag code within the file mtagconfig.js and paste the line of code:

<script type="text/javascript" src=".../mtagconfig.js"></script> directly after the opening <body> tag in all the required web pages.

Note: When pasting the LivePerson Tag within the mtagconfig.js file you must omit the <script> tag. For a more detailed explanation, see “Complete LivePerson Tag” on page 7.

mtagconfig.js Implementation per Site

If your site uses a common header file you can paste a link to the mtagconfig.js file. This will automatically place the LivePerson Tag on all the pages of your site. You only need to paste the LivePerson Tag code within the file mtagconfig.js and paste the line of code:

Note: When pasting the LivePerson Tag within the mtagconfig.js file you must omit the <script> tag. For a more detailed explanation, see “Complete LivePerson Tag” on page 7.

Users with the Existing LivePerson Monitoring Code

For those who want to upgrade from the existing LivePerson Monitor Code to the LivePerson Tag and:

) have not made any alterations to the code, simply remove and replace the previous code

with the new code, as explained above.

) have made changes to the Monitor Code (either by you or with the aid of LivePerson),

please contact your Success Manager before replacing the code as they may be additional HTML code capabilities

(6)

6

Comparison of the Monitor Code and LivePerson Tag

This section gives a brief comparison of the manageability and performance of the Monitor Code and the new LivePerson Tag.

JavaScript Code Essentials

Technical Changes

When comparing the current Monitor Code and the new LivePerson Tag, the essential difference is that the current code contains JavaScript monitoring code only.

The new LivePerson Tag contains JavaScript code which has the capability to dynamically load other tags (knows as "taglets") which can be called to the web page. The existing Monitoring Code is one of these taglets. (Note that the content of the Monitor Code was not changed).

Advantages

The main advantage is that it allows LivePerson to remotely perform any changes required in the actual taglets without affecting the customer-side.

In the future LivePerson envisages that the customer will manage taglet allocation; allocating the most suitable taglets per web page.

Performance Related Issues

Technical Changes

) For optimum performance we strongly recommend the LivePerson Tag should be deployed on all pages directly after the opening <body> tag.

) LivePerson Tag is loaded asynchronously. ) Tag server is GEO distributed.

Advantages

Placing the LivePerson Tag at the initial section of the <body> does not slow page-load time on the clients' side. This is due to its' asynchronously load. In addition to that, taglets can be activated as soon as possible to the page, even before the page has completed loading. The tag server is GEO distributed, and therefore the service is performed from the closest server, optimizing the loading time.

(7)

7

Complete LivePerson Tag

Copy the LivePerson Tag HTML code and paste the source code directly after the opening <body> tag in all of your web pages.

Note: If you are pasting the LivePerson Tag within the mtagconfig.js file you must omit the <script> tag.

This is the text: <script type="text/javascript"> and </script> and is highlighted in blue. <script type="text/javascript"> window.lpTag={ site:'57746814', _v:'1.1',protocol:location.protocol,events:{bind:function(app,ev,fn){lpTag.def er(function(){lpTag.events.bind(app,ev,fn);});},trigger:function(app,ev,json){ lpTag.defer(function(){lpTag.events.trigger(app,ev,json);});}},defer:function( fn){this._defL=this._defL||[];this._defL.push(fn);},load:function(src,chr,id){ var t=this;setTimeout(function(){t._load(src,chr,id);},0);},_load:function(src,chr ,id){var url=src;if(!src){url=this.protocol+'// '+((this.ovr&&this.ovr.domain)?this.ovr.domain:'lptag.liveperson.net')+'/tag/ tag.js?site='+this.site;}var s=document.createElement('script');s.setAttribute('charset',chr?chr:'UTF-8');if(id){s.setAttribute('id',id);}s.setAttribute('src',url);document.getElem entsByTagName('head').item(0).appendChild(s);},init:function(){this._timing=th is._timing||{};this._timing.start=(new Date()).getTime();var that=this;if(window.attachEvent){window.attachEvent('onload',function(){that._ domReady('domReady');});}else{window.addEventListener('DOMContentLoaded',funct ion(){that._domReady('contReady');},false);window.addEventListener('load',func tion(){that._domReady('domReady');},false);}if(typeof(window._lptStop)=='undef ined'){this.load();}},_domReady:function(n){if(!this.isDom){this.isDom=true;th is.events.trigger('LPT','DOM_READY',{t:n});}this._timing[n]=(new Date()).getTime();} }; lpTag.init(); </script>

(8)

This document, materials or presentation, whether offered online or presented in hard copy ("LivePerson Informational Tools") is for informational purposes only. LIVEPERSON, INC. PROVIDES THESE LIVEPERSON INFORMATIONAL TOOLS "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

The LivePerson Informational Tools contain LivePerson proprietary and confidential materials. No part of the LivePerson Informational Tools may be modified, altered, reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), without the prior written permission of LivePerson, Inc., except as otherwise permitted by law. Prior to publication, reasonable effort was made to validate this information. The LivePerson Information Tools may include technical inaccuracies or typographical errors. Actual savings or results achieved may be different from those outlined in the LivePerson Informational Tools. The recipient shall not alter or remove any part of this statement.

Trademarks or service marks of LivePerson may not be used in any manner without LivePerson's express written consent. All other company and product names mentioned are used only for identification purposes and may be trademarks or registered trademarks of their respective companies.

LivePerson shall not be liable for any direct, indirect, incidental, special, consequential or exemplary damages, including but not limited to, damages for loss of profits, goodwill, use, data or other intangible losses resulting from the use or the inability to use the LivePerson Information Tools, including any information contained herein.

8

The LivePerson Tag. Technical Data Sheet. Document Version: 1.0. December 2012

Technical Data Sheet