AIUNIFY Funnels provides a dedicated Domain Settings area for choosing the public domain value associated with a Landing Page.
The Settings screen displays the Landing Page's Current domain and provides a Domain Type control.
The confirmed Domain Type choices are:
| Sub domain | Uses the Landing Page's subdomain value. |
| Custom your domain | Uses a custom domain entered for the Landing Page. |
The selected Domain Type determines which domain input is active in the Settings interface.
A new Landing Page receives a generated subdomain during the normal Template creation workflow.
The initial value is created using a random string together with the application's configured primary domain.
This provides a Landing Page-specific domain value without requiring the user to supply a separate custom domain during initial creation.
When Sub domain is selected, the subdomain field is enabled and the interface displays:
You can customize subdomain
The subdomain submitted through Settings must satisfy the application's domain-format validation and must not duplicate another Landing Page's saved subdomain.
Use the complete domain format expected by the Settings field rather than entering an arbitrary label that does not form a valid domain value.
Select Custom your domain when the Landing Page should use a custom domain rather than its subdomain value.
The custom-domain field uses the placeholder:
Enter your custom domain
The submitted custom-domain value must satisfy the application's domain-format validation and must be unique among Landing Page custom-domain values.
The Domain Settings validation is designed for domain values rather than a complete campaign URL containing additional paths or page parameters.
Enter the domain required by the field and use Landing Page content, buttons, redirects, and other supported controls for visitor destinations that include more specific paths.
When custom-domain mode is selected, AIUNIFY Funnels displays DNS information that should be added at the provider managing that domain's DNS settings.
The interface states:
Add records below in your domain provider's DNS settings
The DNS table contains the columns:
| TYPE | The DNS record type required by the displayed configuration. |
| HOST | The host/name value for the DNS record. |
| VALUE | The target value to which the DNS record should point. |
| TTL | The TTL value displayed by AIUNIFY Funnels for that DNS record. |
Do not substitute guessed DNS targets for the values shown in the Landing Page Settings screen.
Use the TYPE, HOST, VALUE, and TTL information displayed by the system for the current installation.
DNS management itself is performed with the external provider responsible for the selected domain.
The Domain Settings screen displays the Landing Page's Current domain according to its selected domain mode.
When subdomain mode is active, the saved subdomain is used. When custom-domain mode is active, the saved custom-domain value is used.
My Landing Pages uses the same basic distinction when presenting the Landing Page's Domain column.
Domain configuration and the Publish control are separate.
A valid domain value does not automatically enable publishing, and enabling Publish does not automatically complete external custom-domain DNS configuration.
Before sending traffic, verify both.
If a submitted domain does not satisfy the required domain format, the Settings form will not accept it.
Subdomains and custom domains are also checked for uniqueness so the same saved domain value cannot simply be assigned to multiple Landing Page records through the normal Settings workflow.
If a subdomain does not contain the domain structure expected by the application, the system can return a message beginning with:
Subdomain must have
followed by the required application-domain value.
If the Landing Page should return to its subdomain, select Sub domain, verify the saved subdomain value, save the Settings, and retest the public Landing Page.
Do not assume a previously distributed custom-domain URL will automatically represent the newly selected subdomain configuration.
A cloned Landing Page receives a new generated subdomain and its custom-domain value is cleared by the clone workflow.
Always review Domain Settings after cloning before distributing the new Landing Page.
Operating principle: Treat the domain as part of the Landing Page's operating configuration. Save the correct mode, follow the displayed DNS instructions for custom domains, and verify the actual public URL before sending traffic.