A Landing Page has a saved publishing state that determines whether it can be resolved through its configured public Landing Page domain.
The Landing Page model identifies published pages through its Publish state, while unpublished pages use the separate unpublished state.
Publishing should therefore be treated as a deliberate launch action rather than simply another design setting.
For public Landing Page traffic, AIUNIFY Funnels examines the host name used by the visitor.
The public-domain workflow can identify a Landing Page from either:
The public Landing Page lookup requires the matching Landing Page to be published.
The confirmed domain middleware does not simply locate any Landing Page with a matching domain. It applies the Landing Page's published scope before resolving the record.
If a matching published Landing Page cannot be found, the normal public lookup does not render that Landing Page.
Operating principle: A correct domain alone is not sufficient. The Landing Page must also be in the intended published state.
When a Landing Page uses the standard Sub domain mode, its saved subdomain identifies the public host associated with that page.
Use the Current domain value displayed in Landing Page Settings or the Domain column in My Landing Pages rather than manually guessing the public address.
When a Landing Page uses Custom domain mode, the configured custom domain becomes the host AIUNIFY Funnels attempts to match to that published page.
The external DNS configuration described in Chapter 22 must also be correct for visitors to reach the AIUNIFY Funnels server through that custom domain.
The confirmed application helper used by the current source builds the Landing Page's current URL from its saved domain type.
When Sub domain mode is selected, it uses the saved subdomain. When Custom domain mode is selected, it uses the saved custom domain.
The present source helper begins this generated value with http://. Users should therefore rely on the actual URL presented and served by the deployed system and verify the live browser result rather than manually constructing a different address from assumptions.
The published Main Page renders the Landing Page's saved public content and associated page configuration.
The public rendering workflow uses information that can include:
| Main Page content | The HTML and styling saved through the Landing Page Builder. |
| Landing Page font | The current font stored in Landing Page Settings. |
| SEO information | The saved SEO title, description, keywords, favicon, and related metadata. |
| Social information | The saved Social Title, Social Description, and Social Image. |
| Custom Header/Footer | Custom code saved through the Landing Page Custom Code settings. |
| Main Page scripts | Page script information used by supported form and ecommerce workflows. |
AIUNIFY Funnels also maintains separate Thank You Page content for each Landing Page.
The published Main Page prepares a Thank You Page URL from the current Landing Page domain followed by the application's Thank You Page path.
The Thank You Page is therefore part of the same Landing Page campaign and should be tested after any domain, publishing, design, or conversion-setting change.
The Main Page and Thank You Page have separate stored content and styling.
Changing one in the Builder does not mean the other has automatically been redesigned.
Before launching a campaign, open and review both pages.
The public Main Page and Thank You Page templates use the saved SEO and social-sharing values when rendering their page metadata.
This includes the SEO Title and Description as well as supported Open Graph and social-image information.
Complete these settings before promoting a page widely if search or social sharing is important to the campaign.
If a Favicon has been uploaded in Landing Page Settings, the public page can reference the saved Landing Page favicon from the page's storage location.
Use the application's recommended favicon size guidance and confirm that the icon displays properly in an actual browser tab.
Custom Header and Footer code configured in Chapter 30 is returned with the Landing Page's public page information.
Because this custom code can affect the live page, always test the public Landing Page immediately after changing tracking code, chat scripts, custom CSS, pixels, or other snippets.
When a visitor submits a supported Landing Page form, AIUNIFY Funnels processes that submission against the Landing Page identified by its unique Landing Page code.
This connects the public form submission to the correct campaign record and ultimately to the Leads workspace.
If the Main Page contains supported payment components, the page's saved payment configuration and associated Product information participate in the public checkout workflow.
Payment functionality should be tested independently from ordinary form submission because payment-success actions and form-submission actions are separate Landing Page settings.
A Builder view or template preview is not the same as visiting the actual published Landing Page through its live domain.
The live-domain test validates additional behavior such as:
Operating principle: Publish only after the complete public visitor journey has been tested through the Landing Page's actual configured domain.