Integrate chat system at the trade fair stand

NOTICE: Chat tools are not expo-IP's own modules. Chat tools come from third parties and can be integrated into the expo-IP system by the user. Please note that we do NOT provide support for the use of third-party products. For questions regarding the use of the chat tool you are embedding on expo-IP, please contact the provider of the product.

Chat setting across fairs

If an overall chat (Fair->Tab General -> Option: Show this service chat on all stands) has been defined, NO individual chat can be displayed on a stand.

CHAT - Insert embed code

Fügen Sie den Embed-Code des von Ihnen ausgewählten Chat Systems in das dafür vorgesehenen Feld im expo-IP CMS ein.

JavaScript

Via JavaScript you have access to the visitor data(available variables). If the used chat system offers a JavaScript API that can populate and display visitor data within the chat system, you can use it to automatically transfer the visitor data from the expo-IP system to the chat system.

JavaScript - Examples

Die folgenden Beispiele wurden im Februar 2023 auf Basis der zu dieser Zeit gültigen Java Script APIs der jeweiligen Hersteller (Dritt-Produkte) erstellt und getestet. Sollte sich das von Ihnen gewählte und eingesetzte CHAT-System nicht mehr wie beschrieben verhalten, hat der Hersteller des Chat-Systems seine API oder Funktionalitäten verändert. In diesem Fall wenden Sie sich bitte direkt an den Hersteller des Chat-Systems. EXPO-IP GmbH kann KEINEN Support für Fremdprodukte übernehmen.

 

Our examples apply to the following chat systems:

• • 123.chat
  • ZoHo SalesIQ
  • tawk.to
  • Crisp chat
  • RumbleTalk

Example 123.chat

In this example the expo-IP visitor name and its company name should be transferred to the chat system. The company name was stored in the custom field with ID 64.

Original EmbedCode:

<script src=“https://livechat.123.chat/embedded/0bc6e09f-c2b1-9889-a694-d9093276e462.js“ async></script>

Supplemented EmbedCode:

<script>
var g_we_child = null;
window[„custom123chat“] = (we_child) => {
g_we_child = we_child;
g_we_child.load(sendExpoUserData);
};

function sendExpoUserData() {
if (g_we_child != null && g_we_child.document.we_wsConn != null && g_we_child.document.we_wsConn.readyState) {
setTimeout(()=>{
g_we_child.wsSend(„SetInfo“, {„Key“: „email“, „Value“: expo.user.email});
g_we_child.wsSend(„SetInfo“, {„Key“: „name“, „Value“: expo.user.userName+ “ “ + expo.user.customField[64].value});
}, 300);
} else {
setTimeout(sendExpoUserData, 300);
}
}
</script>

<script src=“https://livechat.123.chat/embedded/0bc6e09f-c2b1-9889-a694-d9093276e462.js“ async></script>

Example ZoHo SalesIQ

In this example the expo-IP visitor name and its company name should be transferred to the chat system. The company name was stored in the custom field with ID 64.

Original EmbedCode:

<script type=“text/javascript“ id=“zsiqchat“>var $zoho=$zoho || {};$zoho.salesiq = $zoho.salesiq || {widgetcode: „b2a99ecc2a580a9bd1c14a4ed7g33913b60d5f0e5a363aad2cfe466309aea812“, values:{},ready:function(){}};var d=document;s=d.createElement(„script“);s.type=“text/javascript“;s.id=“zsiqscript“;s.defer=true;s.src=“https://salesiq.zoho.eu/widget?plugin_source=wordpress“;t=d.getElementsByTagName(„script“)[0];t.parentNode.insertBefore(s,t);</script>

Supplemented EmbedCode:

<script type=“text/javascript“ id=“zsiqchat“>var $zoho=$zoho || {};$zoho.salesiq = $zoho.salesiq || {widgetcode: „b2a99ecc2a580a9bd1c14a4ed7g33913b60d5f0e5a363aad2cfe466309aea812“, values:{},ready:function(){}};var d=document;s=d.createElement(„script“);s.type=“text/javascript“;s.id=“zsiqscript“;s.defer=true;s.src=“https://salesiq.zoho.eu/widget?plugin_source=wordpress“;t=d.getElementsByTagName(„script“)[0];t.parentNode.insertBefore(s,t);</script>

<script>
$zoho.salesiq.ready=function()
{
$zoho.salesiq.visitor.name(expo.user.userName + expo.user.customField[64].value);
$zoho.salesiq.visitor.email(expo.user.email);
}
</script>

Example tawk.to

In this example the expo-IP visitor name and its company name should be transferred to the chat system. The company name was stored in the custom field with ID 64.

Original EmbedCode:

<!–Start of Tawk.to Script–>
<script type=“text/javascript“>
var Tawk_API=Tawk_API||{}, Tawk_LoadStart=new Date();
(function(){
var s1=document.createElement(„script“),s0=document.getElementsByTagName(„script“)[0];
s1.async=true;
s1.src=’https://embed.tawk.to/581a0020e808d60cd077360c/default‘;
s1.charset=’UTF-8′;
s1.setAttribute(‚crossorigin‘,’*‘);
s0.parentNode.insertBefore(s1,s0);
})();
</script>
<!–End of Tawk.to Script–>

Supplemented EmbedCode:

<!–Start of http://tawk.to/ Script–>
<script type=“text/javascript“>
var Tawk_API=Tawk_API||{}, Tawk_LoadStart=new Date();

expo.user.userName = expo.user.userName +" " + expo.user.customField[64].value;

Tawk_API.visitor = {
name : expo.user.userName,
email : expo.user.email
};

(function(){
var s1=document.createElement(„script“),s0=document.getElementsByTagName(„script“)[0];
s1.async=true;
s1.src=’https://embed.tawk.to/581a0020e808d60cd077360c/default‘;
s1.charset=’UTF-8′;
s1.setAttribute(‚crossorigin‘,’*‘);
s0.parentNode.insertBefore(s1,s0);
})();
</script>
<!–End of http://tawk.to/ Script–>

Crisp Chat example

Also in this example the expo-IP visitor name and its company name should be transferred to the chat system. The company name was stored in the custom field with ID 64.

Original EmbedCode:

<script type=“text/javascript“>
window.$crisp=[];
window.CRISP_WEBSITE_ID=“04180900-8d98-4ffb-9082-4f85895ed2c1″;
(function(){d=document;s=d.createElement(„script“);s.src=“https://client.crisp.chat/l.js“;s.async=1;d.getElementsByTagName(„head“)[0].appendChild(s);})();</script>

Supplemented EmbedCode:

<script type=“text/javascript“>
window.$crisp=[];
$crisp.push([„set“, „user:nickname“, expo.user.userName + expo.user.customField[64].value]);
$crisp.push([„set“, „user:email“, expo.user.email]);
window.CRISP_WEBSITE_ID=“04180900-8d98-4ffb-9082-4f85895ed2c1″;
(function(){d=document;s=d.createElement(„script“);s.src=“https://client.crisp.chat/l.js“;s.async=1;d.getElementsByTagName(„head“)[0].appendChild(s);})();
</script>

Example RumbleTalk

With RumbleTalk, the invention is a bit more complex. First the EmbeddCode for the "floating" display is created and copied at Rumble talk. This code is supplemented by further JavaScrip program lines.

Also in this example the expo-IP visitor name and its company name should be transferred to the chat system. The company name was stored in the custom field with ID 64.

Original EmbedCode:

<div id=“rt-76de8b2a6ecd0974abadd7fe51f8bf7c“ data-floating=“true“ data-side=“right“ data-width=“700″ data-height=“500″ data-user-counter=“14,23″ data-message-counter=“0,60″></div> <script src=“https://rumbletalk.com/client/?jnI6-WJE„></script>

Supplemented EmbedCode:

<div id=“rt-76de8b2a6ecd0974abadd7fe51f8bf7c“ data-floating=“true“ data-side=“right“ data-width=“700″ data-height=“500″ data-user-counter=“14,23″ data-message-counter=“0,60″></div> <script src=“https://rumbletalk.com/client/?jnI6-WJE„></script>

<script>
let rumbletalk_hash = ‚jnI6-WJE‚;
(function(g, v, w, d, s, a, b) {
w[‚rumbleTalkMessageQueueName‘] = g;
w[g] = w[g] ||
function() {
(w[g].q = w[g].q || []).push(arguments)
};
a = d.createElement(s);
b = d.getElementsByTagName(s)[0];
a.async = 1;
a.src = ‚https://d1pfint8izqszg.cloudfront.net/api/‘ + v + ‚/sdk.js‘;
b.parentNode.insertBefore(a, b);
})(‚rtmq‘, ‚v1.0.2′, window, document, ’script‘);
var s = document.createElement(„script“);
s.type = „text/javascript“;
s.src = „https://www.rumbletalk.com/client/?“ + rumbletalk_hash ;
// Use any selector
$(„head“).append(s);
if (!expo.config.isGuest && expo.user.username !== null) {
rtmq(„login“, {
hash: rumbletalk_hash,
username: expo.user.userName + expo.user.customField[64].value,
});
}
</script>

RumbleTalk - Feature

Rumble Talk can be covered by expo-IP elements in some situations (e.g. widgets, such as Youtube and Vimeo widgets, among others. To ensure that this does not happen, the following should be set as Custom CSS:

 

Fair -> General -> Custom CSS/JS

 

</style>

div.rumbletalk-floating {
z-index:1010 !important;
}

</style>