# Frequently asked questions

<!-- WARNING: THIS FILE WAS AUTOGENERATED! DO NOT EDIT! -->

This section provides answers to common questions about using the ZVA bot.

## A bot is set to trigger on the left in an embedded campaign. Why does it open on the right side?

When the invitation is in embedded mode, you can use parameters to define the location of the bot when introducing the `liveSDK` tag, as shown in this example:

```html
<script src="xxx" data-apikey="your_apikey" data-window-position="left">
```

## Why does a page continue to display _Connecting_ and the subsequent dialog pop-ups don't appear as expected?

If the ZVA process ends and needs to transition to another SDK process and remains stuck on "connecting" for a long time, you should check whether the APIs of the other SDK are functioning correctly. Note that this issue typically happens when routing to a third-party CRM, such as switching from ZVA to Zendesk.

## Why does ZVA SDK not work with certain ad blockers plugins?

The ZVA SDK is effective for most ad blockers on Google Chrome. However, some situations exist where the ZVA SDK could be blocked. For example, deploying the ZVA SDK through Google Tag Manager(GTM) could result in the ZVA SDK not loading properly due to blocking GTM under the default filtering rules of the UBlock Origin plugin.

## While navigating between pages while the widget is open, the widget can receive an event from the Zendesk websocket that triggers _Help center_ to display in the widget. Why?

If the button at the bottom of the widget reads, _Chat with us_, you can return to the chat and receive messages from an agent. If it reads, _Leave us a message_, you cannot easily return to the chat or receive agent messages. In either state, the chat becomes inactive. When you minimize the Zendesk widget, it triggers ZVA to completely hide the Zendesk widget and display the ZVA engagement window.

To prevent this behavior, disable _Help Center_ on the Zendesk widget so it ignores help center triggers from the Zendesk websocket. Now the widget remains in chat mode and forces the chat to remain active.

![](/img/zva-disable-helpcenter.png)