Let's imagine a site with 4 different pages.
Wanting to activate, using Predictive Engagement, the Web Messenger (WM) on 2 of these pages, I configure 2 segments and the related Action Maps.
For clarity, let's say that page1 and page3 are the pages with this action map and page2 and page4 those without.
Experience tells me that, by configuring the WM for this site with "Hide until triggered by business logic" I get the following results (generally speaking):
Scenario 1:
user on page2 - no Launcher Icon (LI), then
on page3 - LI active then
on page4 - LI (of page3) active then
on page1 - LI (of page3) active.
Scenario 2:
user on page1 - LI active, then
on page2 - LI active (of page1)
on page3 - LI active (of page1)
How can I prevent a possible launcher icon from always being presented on pages where there is no Action Map?
How can I prevent the first launcher icon displayed from overriding subsequent ones (relating to different pages/different action maps)?
Clicking on the "X" of the icon (possibly before changing pages) is not good because it removes the instance of the icon and therefore, if you return to the page where the chat was expected, this action map is not executed again.
Even the use of events and commands related to Web Messaging does not seem to be very useful.
Any suggestions? Thank you very much!
Hi @Vincenzo_Mercolino I understand the "what" you are trying to achieve, but can you clarify the "why"?
In your example, if a conversation was to start on any other page where action maps is triggered (page1/page3), would you not want that conversation to persist as user navigates on page2/page4? Even if it's just for the initial offer, why would you not want to show that offer on all pages where Messenger Deployment is configured?
If we were to auto-dismiss the existing offer when moving back to page2/page4, that would be interpreted as offer-rejected/ignored in terms of funnel, would you agree?
Hi Angelo! First of all, thank you for your prompt reply.
Probably, talking about web messenger, I made you confused about the topic.
Actually the focus is the launcher icon and not the web messenger. The topic I'm discussing with a customer is whether there is a way to avoid that, on urls where there are no Action Maps configured, a launcher' text-icon relating to the immediately preceding page (with an appropriate action map triggered) still appears.
It is also clear to the customer that, once the icon is clicked and a conversation is activated via Web Messenger, this conversation is maintained throughout the customer's web journey, as you have also underlined.
I hope I have better clarified the schematization I presented earlier.