Considerations for the Enhanced Landing Page Experience

Keep these considerations in mind before you work with the enhanced landing page experience.

Available in: All Account Engagement Editions

Setting Up Enhanced Landing Pages

The enhanced landing page builder uses the same permissions and Digital Experiences integration as enhanced email. If the enhanced email experience is configured, your users can typically get started with landing pages right away.
Updates to landing page record layouts typically appear automatically. But if the Lightning record page or page layout for the landing page is customized, an admin must manually add new fields and tabs.

When you create an enhanced landing page, it must be associated with a connected campaign.
The landing page’s campaign must be associated with one business unit. The business unit assignment is required to publish the landing page. If you don’t have multiple business units, only Connected Campaigns settings define the relationship.
A connected campaign and a business unit have a one-to-one relationship that’s controlled in your connector settings. To assign a business unit, configure the record type settings and trigger a sync.
If you can’t find a field or tab on the landing page object, such as the Unpublish Redirect URL field, ask your admin to check for recent release updates. Some components must be added manually.

You can use Salesforce CMS in the Digital Experiences app as an image repository. You can also include absolute URL links to public images hosted by a third party. Salesforce Files aren’t supported.
When you design landing page content, it’s stored in an HTML field. The HTML field must not exceed 384 KB.
Active content, such as JavaScript or SVG files, isn’t supported in enhanced landing pages.
Landing pages are mobile-responsive. On screens smaller than 480 px wide, a landing page’s default width is 320 px.

The HTML component supports iframes. A placeholder for the iframe content appears on the builder canvas and record home. Iframed content is rendered only on the published landing page.
To make sure that your iframe is responsive when you publish your landing page, review the embed code.
- If your embed code is already responsive: Verify that the iframe tag includes a style attribute or a width attribute as a percentage. The builder doesn’t change the embed code.
- If your embed code isn’t responsive: Verify that the iframe tag includes the width and height attributes as pixels and doesn’t include a style attribute. The builder changes the embed code when it’s rendered, which make the iframe responsive.

You must publish a landing page to make it available online. When you edit a published landing page, the status updates to Published (With Changes) and must be published again before the edits appear online.
The public link on a landing page record shows your primary tracker domain. If you enter a vanity URL, the path works with any of your custom tracker domains.
You can use a vanity URL on one landing page at a time. If you delete a landing page record that uses a vanity URL, you can’t use that vanity URL again on another record. To reuse a vanity URL, clear it from a landing page record and publish the change. Then, you can add the vanity URL to a new record. If you no longer need the original landing page record, you can delete it.
When you publish an enhanced landing page, a related record is created in Account Engagement. This record tracks engagement activities and stores metrics, which are synced back to the main landing page record in Salesforce.
When you unpublish an enhanced landing page in Salesforce, the related record is archived in Account Engagement. If you republish the landing page, we unarchive the related record to retain previous metrics.

Most Account Engagement editions support up to 1,000 enhanced landing pages at one time. Published and unpublished enhanced landing pages count toward this number. Classic landing pages are unlimited.
Account Engagement Growth Edition supports 50 landing pages, counting any classic landing pages and published, enhanced landing pages.

Did this article solve your issue?

Let us know so we can improve!