The notification feed is where you and your site visitors connect. It's the hub for all of your notification campaigns that you create in Wisp.

There are two ways your visitors can experience the notification feed depending on how you implement it: The Floating Feed and the Custom Feed.

Before exploring what makes the the floating and custom feeds different, let's consider what makes them the same.

The Red Notification Badge.

When a visitor has a notification waiting, the familiar red badge will appear at the location of the feed to draw them in. It's super effective; we're trained to click those red badges. Depending on how many unopened notifications are waiting, the red badge will display the corresponding number.

Another cool thing to note is that the feed isn't just updated when a page is loaded. Visitors can receive new notifications in real time, based on their activity as they browse. This is covered more in the section on audiences.

Feed Contents

Inside the feed, you'll always see the teaser: a short preview of the full notification campaign. Clicking on a teaser will reveal the next component of the campaign. We call this the message.

Unopened campaigns will be indicated in an obvious way. Opened campaigns will remain in the feed as an archive. The feed will become scrollable after a few notifications, so don't worry about a huge feed if you send a lot of notifications.

While there are opportunities for you to style and customize the appearance, those changes are aesthetic and independent of whether or not your feed uses the floating or custom setup.

We cover the appearance customizations in this section on settings.

Now let's take a look at the floating feed in greater detail and then move on to the custom feed.

Did this answer your question?