# Landing Pages

Private Beta
Landing Page Delivery is currently available as a private beta. Contact your Treasure AI account representative for access.

Landing Page Delivery is the Treasure AI Engage Studio capability for hosting branded static websites on your custom subdomains. It gives marketers a governed way to publish campaign destinations while web operations teams retain control of DNS and the public domain. Use Landing Pages when you have a static website package to deploy for a promotion, event, or confirmation experience.

Landing Pages support the **Engage** stage of the Customer Intelligence Loop by giving your campaigns a public destination under your own brand.

## How Landing Page Delivery Works

Landing Page Delivery publishes a completed static website package through a custom subdomain that your organization configures in Engage Studio.

1. Prepare a static website package.
2. Configure a custom subdomain.
3. Create a landing page draft.
4. Upload the static ZIP package.
5. Publish the landing page.
6. Visitors open the HTTPS URL.
7. Update, unpublish, or delete the landing page.


A web or DNS administrator registers a subdomain and adds the DNS records generated by Engage Studio. After the subdomain is **Active**, a marketer creates a landing page, uploads its static files, and publishes it. The page is then available at `https://<subdomain>/<slug>` or, when no slug is set, at the root of the subdomain.

## What Landing Pages Support

Landing Page Delivery supports static HTML, CSS, JavaScript, images, fonts, and other allowlisted web assets uploaded in a ZIP package. Each landing page has a **Draft** or **Published** status.

| **Capability**  | **Behavior**  |
|  --- | --- |
| Custom subdomains | Register a branded subdomain, complete DNS setup, and publish after the subdomain becomes **Active**. |
| Static website packages | Upload a ZIP package containing allowlisted static files, including HTML, CSS, JavaScript, images, and fonts. |
| Page lifecycle | Create drafts, publish a verified package, upload changed content and republish it, unpublish the page, and then delete the draft. |
| No-code page builder | Landing Page Delivery does not currently include a no-code page builder. Create the website outside Engage Studio and upload the finished static package. |
| Native forms | Landing Page Delivery does not currently include native form processing. Use a third-party form service or custom JavaScript and HTML to handle form submissions. |
| Visitor tracking | Use the [Web SDK](/products/marketing-cloud/personalization-studio/web-sdk-integration) in the static package to track visitor behavior. |
| Personalization | Landing Page Delivery hosts static content. Use [Personalization Studio](/products/marketing-cloud/personalization-studio) or [Engage Studio In-Browser Messaging](/products/marketing-cloud/engage-studio/experiences/personalize-message-content) when an experience requires personalization. |


## Choose Your Starting Point

Landing Page Delivery separates responsibility for the public domain from responsibility for page content. Web and DNS administrators configure the custom subdomain and confirm its status. Marketers prepare the static package, create the landing page, and publish it after the domain becomes **Active**. Administrators grant the Campaign and Engage Domain permissions that control those actions.

- To prepare the static files for upload, see [Prepare a Static Website Package](/products/marketing-cloud/engage-studio/landing-pages/prepare-a-static-website-package).
- To register a branded web address and complete DNS setup, see [Configure Custom Subdomains](/products/marketing-cloud/engage-studio/landing-pages/custom-subdomains).
- To create, publish, update, or retire a campaign destination, see [Create and Publish Landing Pages](/products/marketing-cloud/engage-studio/landing-pages/creating-and-publishing).
- To confirm limits, permissions, and recovery steps, see [Specifications and Troubleshooting](/products/marketing-cloud/engage-studio/landing-pages/specifications-and-troubleshooting).


## Landing Page Lifecycle

Landing pages begin as **Draft**. Publishing copies the completed static package to the public URL and changes the status to **Published**. Uploading a revised package and publishing again serves the revised content at the same URL. Unpublishing returns the page to **Draft** and stops the URL from serving the page.

Published page settings
A landing page's URL slug is locked while the page is **Published**. Unpublishing returns the page to **Draft**, where you can edit the slug before publishing again. Its custom subdomain cannot change after the page has been published for the first time. To remove a published page, unpublish it before deleting it.

## Next Steps

Prepare a Static Website Package
Prepare a static ZIP package, verify its paths and files, and confirm that public content contains no secrets.

Configure Custom Subdomains
Register a branded subdomain, add DNS records, and confirm that it is ready for publication.

Create and Publish Landing Pages
Create a draft, upload a static website package, publish it, and manage the page lifecycle.

Specifications and Troubleshooting
Review package limits, supported files, permissions, related workflows, and recovery steps.