10.1 Landing Page Creation Workflow

AIUNIFY Funnels creates a new Landing Page from an existing active Template.

The normal user workflow begins in the Template Library or Template Preview rather than from a blank database record.

A typical creation sequence is:

  1. Open Create Landing Page.
  2. Browse or search the active Template Library.
  3. Preview the template.
  4. Select Use Template.
  5. Enter the new Landing Page Name.
  6. Select Save & Builder.

10.2 Required Creation Information

The creation form submits two important user/template values:

Value Requirement
Name Required. The server accepts a maximum of 255 characters.
Template ID Required. The Template Preview populates this value in a hidden field based on the template selected through Use Template.

10.3 Landing Page Name

The Name identifies the Landing Page inside your account and is displayed later in My Landing Pages.

Because My Landing Pages supports name-based search, choose an internal name that will remain understandable when your account contains many campaigns.

Keep the confirmed maximum length of 255 characters in mind.

10.4 Template Validation

The creation controller looks up the Template selected by the submitted Template ID.

If the Template cannot be found, the user is returned to the template library with:

Template id not found

If this occurs, return to the current Template Library and choose an available template again rather than attempting to reuse an obsolete or manually constructed Template identifier.

10.5 Automatic Subdomain Generation

Before validation, the Landing Page creation workflow automatically generates a subdomain value using a random string combined with the application's configured domain.

The generated value is used as the new Landing Page's initial subdomain.

The server validates that the generated subdomain:

  1. Matches the expected domain format.
  2. Is unique in the Landing Page table.
  3. Meets the configured minimum length requirement.

You are not expected to manually invent this initial random subdomain in the New Landing Page modal.

Subdomain and custom-domain management are covered in Chapter 22.

10.6 What Is Copied from the Template?

After locating the selected Template, AIUNIFY Funnels prepares the template content and style and uses it to create your own Landing Page.

The new Landing Page receives the Template's starting:

Landing Page Field Template Source
Main Page HTML Template content.
Main Page CSS Template style.
Thank You Page HTML Template Thank You Page content.
Thank You Page CSS Template Thank You Page style.
Template reference The selected Template ID.
Initial subdomain The newly generated subdomain for this Landing Page.

This creates a separate Landing Page record belonging to your authenticated user account.

10.7 Ownership of the New Landing Page

The server sets the new Landing Page's user_id to the authenticated user's ID.

This is why the resulting Landing Page appears in the user's My Landing Pages query.

10.8 Initial Integration Setting

The creation source initializes the Landing Page's mailing integration configuration with:

type: none

No external mailing integration is therefore automatically selected merely because a Landing Page was created.

Mailchimp, Acellemail, and Mailwizz configuration are covered later in this manual.

10.9 Initial Autoresponder Values

The new Landing Page is also initialized with empty autoresponder values for:

  1. Message Title
  2. Sender Name
  3. Sender Email
  4. Message Text

Creating the page therefore does not mean that a campaign autoresponder has already been configured.

10.10 Initial Font Setting

The confirmed creation source initializes:

fontCurrently = Open Sans

This provides the new Landing Page with an initial saved font setting that can later be managed through the Landing Page's Font configuration.

10.11 Save & Builder

The creation modal's primary action is:

Save & Builder

After the Landing Page is created successfully, the controller redirects directly to that new Landing Page's Builder using its generated Landing Page code.

This makes the Builder the next operational step after creation.

10.12 What Creation Does Not Automatically Complete

Creating the Landing Page establishes the page record and copies the Template's starting content. It does not mean that the campaign is ready for live traffic.

You should still review and configure the applicable:

  1. Main Page content.
  2. Thank You Page content.
  3. Responsive layouts.
  4. Publishing settings.
  5. Domain settings.
  6. Form next action.
  7. Autoresponder, if needed.
  8. Mailing integration, if needed.
  9. SEO and social-sharing information.
  10. Payment behavior, if the page sells a product or service.

10.13 Creation Errors

If server-side validation fails, the creation request returns to the previous workflow with the first validation error.

Confirmed creation validation includes:

  1. Name is required.
  2. Name must not exceed 255 characters.
  3. Template ID is required.
  4. The generated subdomain must satisfy the configured format, uniqueness, and minimum-length rules.

10.14 Recommended Post-Creation Sequence

  1. Create the Landing Page with Save & Builder.
  2. Confirm that the Builder opens for the newly created page.
  3. Edit the Main Page.
  4. Edit or review the Thank You Page.
  5. Test desktop, tablet, and mobile presentation.
  6. Open Landing Page Settings and configure the required campaign behavior.
  7. Test the complete visitor conversion path before promoting the page.

Operating principle: Save & Builder creates your Landing Page and moves you into customization. It is the beginning of the campaign-building process, not the end of it.

Write Your Comment