Send web notifications with Connect Customer outbound campaigns
You can use Connect Customer outbound campaigns to deliver personalized notifications to website visitors through the Communications widget. Notifications are triggered by visitor activity that the web data tracker captures into Customer Profiles, such as scrolling past a portion of the page, viewing a product for an extended time, or adding an item to a cart. For an overview of how the web data tracker and web notification work together, see Web data tracker and web notification.
How web notification works
-
An event trigger fires when visitor behavior matches a rule you configured in your outbound campaigns campaign.
-
The campaign passes the visitor context to the web notification service, which calls the Customer Profiles API to resolve dynamic placeholders such as first name and recommended products.
-
The service delivers the notification to the visitor's browser over WebSocket and displays it in the Communications widget. The service records interaction events for analytics.
Prerequisites
-
An Connect Customer instance with the Communications widget configured and data collection enabled. For more information, see Capture website visitor activity with the web data tracker.
-
Customer Profiles enabled on the instance. For more information, see Enable Customer Profiles for your Connect Customer instance.
-
Connect Customer outbound campaigns enabled on the instance. For more information, see Enable outbound campaigns and Customer Profiles.
-
Upgrade your existing outbound campaigns configuration to enable this channel. For more information, see Set up Connect Customer outbound campaigns.
Step 1: Enable web notification on your Communications widget
-
Sign in to the Connect Customer admin website.
-
In the navigation menu, choose Channels, then choose Communications widgets.
-
Create a new widget or open an existing one for editing.
-
Under the Features section, enable Web notification.
-
Add the website domains where the widget will be embedded to the allowed domains list.
-
Save the widget and copy the widget snippet code for embedding on your website.
Step 2: Create a notification view
A view defines the visual layout and content of your notification. Use the notification template to design what visitors see.
-
In the navigation menu, choose UI Management, then choose Views.
-
Choose Create view and select the Notification template.
-
Design the notification content:
-
Title – Supports personalization, for example
Hi {FirstName}!. -
Message body – Can include product recommendations from Customer Profiles.
-
Action buttons – For example, Chat now or Learn more.
-
-
Publish the view.
For more information about views, see Views: UI templates to customize an agent's workspace in Connect Customer.
Step 3: Add a web notification service integration and personalize your view
To personalize notification content with Customer Profiles data, add a web notification service integration to your view. The integration connects the view to the Customer Profiles API so dynamic placeholders are resolved at delivery time.
-
Open your view in the view editor.
-
Choose the Integrations tab.
-
Choose Add integration.
-
Set the Integration name, for example
WNS. This name is how you reference profile attributes in your view content using the$.#INTEGRATION_NAMEsyntax. -
Set Integration type to Web notification service.
-
Choose Add integration to save.
After adding the integration, use dynamic placeholders in the view to personalize notifications with profile data. The following table shows the syntax patterns to use in the title or message body of a notification view.
Data type |
Syntax |
Example |
|---|---|---|
Customer profile attribute |
|
|
Recommendation (catalog item) |
|
|
Example notification content
Using an integration named WNS, a notification might look like the
following:
Title: Hi $.#WNS.Profile.FirstName! Still thinking about this? Message: We think you'll love $.#WNS.Recommendations[0].CatalogItem.Name. Click below to chat with an agent.
Tip
In the view editor, choose the Reference tab to see all available Customer Profiles attributes and recommendation catalog fields you can use as dynamic placeholders.
Note
When a notification is triggered, the web notification service calls the
BatchGetProfile and GetProfileRecommendations APIs in
Customer Profiles to fetch real-time profile data and resolve any dynamic placeholders before
delivering the notification to the visitor's browser.
Step 4: Create the campaign
Web notifications are delivered through outbound campaigns. Create a campaign that links to the widget you configured in Step 1 and the notification view you created in Step 2. For a full walkthrough including screenshots, see Create an outbound campaign using the console and Create an outbound campaign using event triggers.
(Optional) Link a recommender to enable AI-driven product suggestions in the notification. Recommenders are only available when you select the View notification type and the selected view has a Web Notification Service integration. For more information, see Predictive Insights (Preview).
Step 5: Initialize web notifications on your website
After embedding the Communications widget snippet on your website, initialize web
notifications by calling Notification.init() in your page
JavaScript. Call this method only after the visitor has granted appropriate consent
for personalized messaging.
await window.amazon_connect.Web.Notification.init();
Measure performance
Track delivery, engagement, chat conversion, and dismissal in the Connect Customer analytics dashboard under the outbound campaigns performance section.
Limitations
For limitations that apply to web notification, see Limitations.