21.1 Landing Page Settings

Each AIUNIFY Funnels Landing Page has its own Settings workspace. This workspace controls page-level configuration that is separate from the visual Main Page and Thank You Page content maintained in the Builder.

Use Landing Page Settings after the visual page has been created whenever you need to change publishing, domain, form, autoresponder, integration, font, SEO, social-sharing, payment-success, or custom-code configuration.

21.2 Opening Settings

  1. Open Landing Pages → My Landing Pages.
  2. Locate the Landing Page you want to configure.
  3. Select Setting for that Landing Page.
  4. Review the available Settings sections before making changes.

The authenticated Settings workflow resolves the Landing Page through the signed-in user's Landing Page records and its unique Landing Page code.

21.3 General Settings

The confirmed interface includes a section labeled General Settings.

Its primary user controls include:

Name The saved name used to identify the Landing Page in the user's workspace.
Publish Controls whether the Landing Page's saved publish state is enabled.
Favicon Allows an image to be associated with the Landing Page for browser-tab presentation.

21.4 Landing Page Name

The Landing Page Name is required when the Settings form is saved.

Use a name that makes the campaign easy to recognize in My Landing Pages, especially when several pages use similar Templates or offers.

Changing the Name does not by itself replace the Main Page or Thank You Page Builder content.

21.5 Publish

The General Settings area contains a Publish switch.

AIUNIFY Funnels stores this as the Landing Page's publish state.

When the Publish control is submitted as enabled, the Settings update stores the publish value as enabled. When the control is not enabled, the update stores the publish value as disabled.

21.6 Published and Not Publish Indicators

After saving, return to My Landing Pages to review the Landing Page's saved publish status.

The interface uses:

Published The Landing Page's publish flag is enabled.
Not publish The Landing Page's publish flag is disabled.

These are the application's current interface labels.

21.7 Publishing and Domain Configuration Are Separate

The Publish setting and Domain configuration are separate controls.

A Landing Page can have a generated subdomain or a custom-domain value while its Publish setting remains disabled.

Likewise, enabling Publish does not by itself prove that a custom domain's external DNS configuration is complete.

Important: Before distributing a Landing Page URL, verify both the intended Publish state and the intended Domain configuration.

21.8 Favicon

The General Settings interface provides a Favicon image upload control.

The application displays the guidance:

Image will be displayed in browser tabs (best size 32 x 32)

If the Landing Page already has a favicon, the Settings screen can display the currently stored image.

21.9 What Happens When a New Favicon Is Saved

When a new favicon file is submitted through Landing Page Settings, AIUNIFY Funnels stores the file in that Landing Page's page-storage directory and names the stored file using favicon with the uploaded file's extension.

After changing the favicon, open the public Landing Page in a browser and confirm that the intended browser-tab image appears.

21.10 Save Settings Deliberately

Landing Page Settings contain several different campaign controls on one Settings screen. Before saving, review the sections that already contain configuration so an unrelated campaign setting is not changed unintentionally.

Important configuration can include:

  1. Domain mode and domain values
  2. Form submission next action
  3. Autoresponder
  4. Mailing integration
  5. Current Font
  6. SEO and social-sharing information
  7. Payment-success next action
  8. Custom header and footer code

21.11 Recommended Publishing Workflow

  1. Finish the required Main Page edits.
  2. Finish the required Thank You Page edits.
  3. Open Landing Page Settings.
  4. Confirm the Landing Page Name.
  5. Confirm Domain configuration.
  6. Review form and payment next actions.
  7. Review autoresponder and mailing integrations when used.
  8. Review SEO, social-sharing information, and favicon.
  9. Enable Publish when the page is ready for its intended public workflow.
  10. Save the Settings.
  11. Return to My Landing Pages and verify the saved status.
  12. Open and test the public Landing Page.

21.12 Publishing Does Not Replace Testing

A saved Published status confirms the application's publish flag. It does not independently prove that every button, form, redirect, mailing integration, custom domain, or payment workflow is correct.

Perform a complete visitor-path test after publishing and after any major Settings change.

Operating principle: Use General Settings to control the Landing Page identity and publish state, then verify the actual public experience rather than relying only on the saved status indicator.

Write Your Comment