Iterable can send in-app messages to your website. These messages are called in-browser messages. To make it easy to display in-browser messages on your website, Iterable has a web SDK.
TIPS
- To learn more about in-browser messaging, read In-Browser Messaging Overview.
- For documentation about Iterable's web SDK, see its GitHub repository: https://github.com/Iterable/iterable-web-sdk.
# Description
Iterable's web SDK:
Can fetch HTML or JSON in-app messages from Iterable and display them on your website (or use the raw JSON in a custom message display or to trigger custom functionality).
Supports standard in-app message configurations like message priority, animations, expiration, background overlay, etc.
Can set custom margins and display intervals.
Can pause the display of in-browser messages, for situations where they shouldn't be shown. For example, you might not want to show in-browser messages when a user is viewing a shopping cart.
Can add an autogenerated close button to your in-browser messages.
Uses JWT-enabled Web API keys for authentication. Because of this, to use the web SDK, you'll need to set up a URL (on your servers) from which the SDK can fetch user-specific JWT tokens. To generate these tokens, use the JWT secret Iterable creates alongside your API key.
Checks for messages when its
getMessagesmethod is called, which can happen whenever you like (on page refresh, on button click, etc.). If the SDK fetches multiple messages, it will show them in sequence, at a configurable interval.Does not display in-browser messages configured for silent delivery.
Supports
action://anditerable://URLs (except in WebKit browsers, including Safari and other browsers on iOS), but notitbl://.Syncs message read state back to Iterable, so that users don't see the same message on multiple devices.
Tracks standard in-app message events such as In-App Open and In-App Click (except for In-App Delete events).
# Limitations
Some limitations to keep in mind:
Iterable's Web SDK does not provide an out-of-the-box mobile inbox implementation.
-
When displayed by Iterable's web SDK in a WebKit browser, in-browser messages have various limitations. This includes Safari, and other browsers on iOS such as Chrome.
Standard links embedded in in-browser messages work as expected.
iterable://andaction://links are not supported. Clicking them does not close the message or run the custom action. On Chrome for iPhone, tapping aniterable://dismisslink can show a prompt that the site is trying to open another application.These browsers prevent Iterable's web SDK from tracking events when users interact with in-browser messages, which affects your campaign metrics.
When a close button is configured, Iterable's web SDK shows that button and it dismisses the message. This includes Safari. On Chrome for iPhone and other iOS browsers that do not identify as Safari, it requires Web SDK 2.3.3 or later. Users can also close a message by clicking outside it, unless the message uses the full-screen layout. A full-screen message covers the area outside it, so use the close button to dismiss it.