# Hosted Pages

Hosted Pages is the Mobile In-App Messaging experience that displays a URL-based web page full-screen inside a mobile app. Use it for interactive campaign content such as coupons, stamp cards, lotteries, surveys, and forms that need more space than a Modal or Banner.

A Hosted Pages experience is a transient in-app experience. It is not a persistent Content Card or Inbox item, and it is different from Engage Studio's standalone Landing Page Delivery capability.

Beta
Hosted Pages is currently part of the beta Mobile In-App Messaging capability. The message payload, SDK APIs, and distribution model may change before general availability.

## When to Use Hosted Pages

Use Hosted Pages when the campaign content needs a full-screen surface or interactive web behavior.

| Use case | Why Hosted Pages fits |
|  --- | --- |
| Coupon or offer page | Provides space for offer details, terms, and actions. |
| Stamp card or loyalty experience | Supports interactive content hosted at a URL. |
| Lottery or gamification | Provides a full-screen surface for a multi-step experience. |
| Survey or form | Gives the form enough space for fields and validation. |
| Personalized campaign page | Lets the hosted page read the profile context provided by the app. |


## Configure Hosted Pages in Engage Studio

Create a Mobile In-App Message and select **Hosted Pages** as the message type. In the creation dialog, choose **Show a Hosted Page** to use a URL that is hosted separately from the drag-and-drop editor.

Create In-App Message dialog showing the Show a Hosted Page option for a Hosted Pages experience
### Target the Audience

Configure the campaign's target audience with the linked Parent Segment, Realtime Personalization, and Personalization Section.

### Enter the Hosted Pages URL

Enter the URL that the mobile app should display. The SDK opens it in the Hosted Pages experience when the campaign matches.

### Preview and Test

Before launching, test the following items:

- The URL loads on the target iOS and Android devices.
- The page provides a visible way to leave the experience.
- Deep links and web links behave as expected.
- The page renders correctly in portrait and landscape orientations.
- Profile values appear only where the campaign intends to use them.
- The page does not expose credentials or other sensitive values.


### Launch and Pause

Click **Launch** to make the Hosted Pages available through the linked Personalization Section. Click **Pause** to stop delivery. The app receives no new campaign offer after the message is paused and the updated Personalization configuration has propagated.

For hosted page and native Bridge requirements, see [Hosted Pages WebView and Bridge Integration](/products/marketing-cloud/engage-studio/channels/mobile-inapp/rich-landing-integration).

## How Hosted Pages Is Displayed

Hosted Pages follows this delivery flow:

1. A customer reaches a tracked screen or performs a tracked action.
2. The app sends the event through the Engage Mobile SDK.
3. Realtime Personalization evaluates the audience and delivery conditions.
4. The response contains a Hosted Pages URL when a campaign matches.
5. The Engage Mobile SDK opens the URL in an SDK-owned full-screen WebView.
6. The page uses the available bridge and context to interact with the app.


The SDK does not display anything when no campaign matches. This is a normal result, not an error.

## App Integration

For hosted page requirements, WebView context, Bridge actions, security, and native SDK responsibilities, see [Hosted Pages WebView and Bridge Integration](/products/marketing-cloud/engage-studio/channels/mobile-inapp/rich-landing-integration).

## Hosted Pages vs. Other Experiences

| Experience | Persistence | Content source | Display |
|  --- | --- | --- | --- |
| Modal | Transient | Engage Studio HTML | Centered overlay |
| Banner | Transient | Engage Studio HTML | Top or bottom banner |
| Hosted Pages | Transient | Hosted URL | Full-screen WebView |
| Content Card / Inbox | Persistent | Card or feed content | App-owned feed or inbox |
| Landing Page Delivery | URL-dependent | Standalone hosted page | Web or channel destination |


For troubleshooting, see [Mobile In-App Troubleshooting](/products/marketing-cloud/engage-studio/channels/mobile-inapp/troubleshooting).

## Related Documentation

- [Mobile In-App Messaging](/products/marketing-cloud/engage-studio/channels/mobile-inapp)
- [iOS SDK Integration](/products/marketing-cloud/engage-studio/channels/mobile-inapp/developer-guide-ios)
- [Android SDK Integration](/products/marketing-cloud/engage-studio/channels/mobile-inapp/developer-guide-android)
- [Mobile Push Campaign](/products/marketing-cloud/engage-studio/channels/mobile-push)