Overview
The document outlines the requirements for embedding a portal page in Engagement Messenger.
Embedding a portal page on Engagement Messenger – Requirements & Considerations
Note - Requirements and considerations are related to the Configurable Cards feature introduced in v5.0.
Consider the following pre-requisites to embed the portal page in Engagement Messenger:
- Ensure the portal page is mobile responsive.
- In the portal page, do not include any additional navigation, sub-headers, or breadcrumbs to the page (or ensure they are not displayed when the page is embedded in Engagement Messenger). The EC header enables back navigation within Engagement Messenger.
- Avoid further navigations from the portal page. If you still want to navigate:
-
- Ensure that only portal page navigations are present.
- Stay on the current Engagement Messenger portal and do not navigate to other portals.
- Ensure that all non-portal navigations open in a new browser tab (target=”_blank”).
- Be careful when using window redirection on click of links on the embedded page (don’t over-ride parent window, this will cause issues with the Engagement Messenger header).
- Customers must use the $links-color variable for link colour.
- Verify the Page title of the embedded page is correct. Engagement Messenger considers the title from the dynamic page title and uses the portal page title as a fallback.
Example Screenshots
The screenshots show an example flow of how this might be leveraged. In this example, the embedded page is a catalog item.
