Create and configure Proactive Chat Campaigns to engage with your visitors on web pages where Glad App is available. Once configured, you can leverage Proactive Chat to greet your visitors with a custom message and invite them to chat with an Agent.
Under the Proactive Conversations category, click Proactive Chat. The Proactive Chat page will show you a list of current campaigns you have, both active and inactive.
Click Create Campaign.
From the Create a Campaign page, enter the following information:
Name – Enter a name for the Campaign. This is the same name that will appear in the Conversation Timeline. Make sure it’s a name that makes it easy to identify the Campaign. See Agent Experience for Proactive Chat for more information.
Description – Enter a description for the Campaign. This is the same description that appears in the Conversation Timeline. Ensure it’s descriptive enough to give Agents enough context on what the Campaign is for. See Agent Experience for Proactive Chat for more information.
Order – Enter the order of priority for the Campaign. “1” is the highest priority. If there is another Campaign with all of its Triggers met first, it will display first.
Next, you must set up the Campaign Trigger(s) and Actions.
Triggers – Select the Conditions that a Campaign must meet before a Proactive Chat Campaign is displayed to visitors. See Proactive Chat ‘Order’ and ‘Trigger’ Overview to learn more about the Triggers.
By default, Proactive Chat Campaigns apply to all pages where Glad App is embedded unless a URL is specified.
If using URL as a Trigger, do not include the URL protocol (i.e., https://, www.) or commas as part of the URL.
Actions – Determines what happens if Trigger(s) are met.
Greeting– The first message or greeting displayed to the visitor when the Proactive Chat Campaign is launched.
Indicate if you want the Campaign to follow your current chat throttling setting and if you want to skip onboarding.
Ignore chat throttling – A Campaign will follow the chat throttling (auto or manual) thresholds currently set up for a Glad App instance by default. Check this box if you want to ignore the chat throttling rules for a Glad App instance. The Campaign will still respect your Glad App business hour settings. Proceed with caution, as disregarding your chat wait times could mean visitors may need to be queued and may sometimes have longer than desired wait times.
If you don’t check this box and set up a Campaign, you can use the “Estimated Wait Time” Trigger, which will only allow a Proactive Chat Campaign to engage if the estimated wait time is less than the threshold you configured.
Skip onboarding – If onboarding is activated on your Glad App instance, checking this box skips the onboarding process (i.e., asking for the visitor’s name and email address) and immediately starts a chat session.
If you check this box, Gladly won’t identify if the visitor is a known Customer and will create a blank Customer Profile.
Click Save. Next, you can preview what the Campaign would look like.
Tip – Multiple Glad App instances
Campaigns apply to all Glad App instances. Use Campaign URL Trigger to target which Glad App instance you want the Campaign to appear in.
Next, you can preview what a Campaign greeting would look like to a visitor when shown through the Glad App preview feature. From there, click the Preview Glad App With Proactive Chat checkbox to preview what a Campaign would look like to a website visitor.
Once a Campaign is saved and you know what it would look like to a visitor, you can create a Rule to route chat requests from a Campaign to a specific Inbox. By default, without a Rule configured to route chats from a Campaign, the visitor will be routed to the Inbox that Glad App (chat) is linked to in the Entry Point settings page.
Next, double-check your Glad App Display Rules. Proactive Chat Campaigns work with Glad App Display Rules to determine which pages the Campaign appears on, and keep in mind that Campaign Triggers could override Glad App Display Rules. For example, Campaign Triggers will ignore the Glad App Display Rules if a Campaign is set to appear on a specific URL, but Glad App Display Rules have an exception to hide the Glad App on the same URL.
Test a Campaign before it’s made live on your website #
Feature Availability
The Campaign preview feature is not yet available but is coming soon. In the meantime, test your Campaign with the workaround below.
If you want to launch a Campaign on the URL (e.g., retale.com/new-products), add ?=[your test name] at the end of the URL in your Campaign (i.e., retale.com/new-products?=TESTNOV2020). The text after the ?= can be anything, but it should be unique so your regular Customers don’t inadvertently see the Campaign.
Once you’ve saved your Campaign, you can test it by navigating to retale.com/new-products?=TESTNOV2020 on your browser. Once you have confirmed everything is working correctly, remove ?=TESTNOV2020 from the URL Trigger. Continue to tweak your Campaign until it looks just right. After that, remove the addition you made to the end of your URL Trigger in your Campaign, click Save, and your Campaign should work as configured.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__cf_bm
29 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_wpfuuid
1 year 1 month 4 days
This cookie is used by the WPForms WordPress plugin. The cookie is used to allows the paid version of the plugin to connect entries by the same user and is used for some additional features like the Form Abandonment addon.
BIGipServer*
session
Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
PHPSESSID
session
This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
li_gc
5 months 27 days
Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
1 year 1 month 4 days
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gd_session
4 hours
This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.
_gd_visitor
1 year 1 month 4 days
This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.
_sp_id.*
1 year 1 month 4 days
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
_sp_ses.*
30 minutes
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
AnalyticsSyncHistory
1 month
Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.
mf_user
3 months
Mouseflow sets this cookie to identify whether a visitor is new or returning.
vuid
1 year 1 month 4 days
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_mkto_trk
1 year 1 month 4 days
This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
li_sugr
3 months
LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.