MoEngage enables users to navigate to a specific app screen, using three different methods: Navigate to screen, DeepLink, and Rich Landing. You can integrate widgets(like texts, images, or buttons) with URLs that, when clicked, send users to other sections of the app or a different app seamlessly.
In this article, we will learn how to configure Navigate to screen, DeepLink, and Rich Landing into your In-app widgets and how they work independently.
Where can you find them?
library_add_check |
Prerequisites Ensure that you're present in Step 2 of creating an In-app campaign. To learn more, see Create In-App Campaign. |
Follow the steps below to find Navigate to screen, DeepLink, and Rich landing in your In-app campaign:
- Once you've chosen a template in the Content section, select a widget for navigation.
- Scroll down to the Actions section and then click + Actions.
- Select Navigation from the dropdown.
- Select one of the three radio buttons depending on your requirements:
- Navigate to screen
- DeepLink
- Rich Landing
-
Select the target screen or enter the target URL.
- Click Next.
Types of Navigation
This action navigates to a specific screen within the app when the user clicks the widget. It is used to guide users to different sections or features of the app seamlessly.
- Specify the target screen within your app from the dropdown.
Deep linking allows users to be directed to a specific screen within your app, another app, or an external website. For example, you can use it to open a website URL in the browser or redirect users to the Play Store if they haven’t downloaded the app. DeepLinks can open external applications, unlike the "Navigate to screen" action which only works within the app.
- Enter the desired URL or DeepLink.
Handling DeepLinks for Native Frameworks
Android
- Create a DeepLink and add it to the manifest file. Refer to the Android documentation.
- Ensure the links are added to the manifest, otherwise, it will open the browser instead of the app screen.
- After following the above steps, add the DeepLink to the input box while creating the campaign.
iOS
- Add the URL scheme (not the entire URL) in the build settings within the Info.plist file.
- After following the above steps, add the DeepLink to the input box while creating the campaign.
Handling DeepLinks for Hybrid Frameworks (e.g., Flutter)
MoEngage SDK does not handle in-app redirections by default for hybrid frameworks, unlike push notifications. Except for Rich Landing pages, you must implement in-app click callback methods.
- Implement in-app click callback methods in your root/app widget.
- Call the moengage_plugin.initialise() method after registering for callbacks.
- In these callbacks, handle the redirection for DeepLink or screen-based redirection.
Refer to the detailed callback documentation for further guidance.
By following these steps, you can effectively configure and manage different navigation actions within the MoEngage dashboard, ensuring a smooth and engaging user experience.
Reference articles:
Rich Landing pages are displayed within the app's web view. This keeps the user within the app while viewing web content, providing a seamless user experience. Use Rich Landing to open a webpage in-app and not externally.
- Enter the HTTPS URL to be displayed.
info Info
Ensure the URL is HTTPS, as HTTP URLs are not supported for Rich Landing pages.
Difference between Rich Landing and DeepLink
Aspect | Rich Landing | DeepLink |
---|---|---|
Content Display | Within the app’s web view |
Within the app or externally (browser, other apps) |
User Experience |
Keeps the user within the app |
Can take the user out of the app |
Use Case |
Displaying web content seamlessly within the app |
Directing to specific screens, external websites, or other apps |
Technical Requirements |
Requires HTTPS URLs |
Requires configuration of URL schemes and intent filters |
Advantages |
User retention, seamless transition |
Versatility, broader reach |
Examples |
Product detail pages, survey forms, promotional content |
Redirect to app sections, open websites, redirect to app stores |