Every AIUNIFY Funnels Landing Page can maintain a separate Thank You Page Builder experience in addition to its Main Page.
The Thank You Page can participate in the visitor journey after supported form-submission or payment-success actions, depending on how the Landing Page is configured.
It should therefore be reviewed as its own page rather than treated as an automatic copy of the Main Page.
The Thank You Page Builder route uses the Landing Page's code together with the Thank You Page page type.
AIUNIFY Funnels stores separate Builder data for the Thank You Page.
| Saved Area | Thank You Page Field |
| Components | Thank You Page Components |
| Styles | Thank You Page Styles |
| HTML | Thank You Page HTML |
| CSS | Thank You Page CSS |
This separation is why a change to the Thank You Page does not automatically rewrite the Main Page.
The Main Page has an additional script field used by supported payment-button behavior.
The Thank You Page update path saves its Components, Styles, HTML, and CSS, but it does not save that Main Page payment-component script field.
Do not assume that a payment button configuration placed on the Main Page is recreated automatically as Thank You Page script behavior.
When the Thank You Page is part of the configured visitor journey, use it to clearly communicate what should happen after the conversion action.
Depending on your campaign, useful visitor-facing content may include:
These are content recommendations. The actual next action is controlled by the Landing Page's configured form or payment behavior, which is covered in later chapters.
The same user Builder environment provides reusable Blocks for page construction.
You can add available Blocks to the Thank You Page and then customize the resulting page components.
Use Blocks to establish structure quickly, but review all copied text, images, links, calls to action, and visual styling for the specific post-conversion purpose.
The Thank You Page uses the same Builder tools for supported component editing:
| Style Manager | Adjust supported appearance properties for the selected component. |
| Layers | Navigate the structural hierarchy of page components. |
| Blocks | Add reusable page structures. |
| Settings | Work with the traits and properties exposed by the selected component. |
The Thank You Page can use Builder assets just as the Main Page can.
Uploaded images are managed through the user Builder's Asset Manager and stored in the authenticated user's storage area. Image-upload and asset-removal behavior is covered in Chapter 19.
The Builder loads and stores Thank You Page data through the Landing Page Builder storage endpoints.
Use the available Save control after important changes.
A successful Builder save can report:
Updated successfully
A failed update can report:
Updated failed
Select Main Page when you are ready to return to the primary Landing Page editing context.
Before switching pages after a significant Thank You Page editing session, allow the current Builder save process to complete.
Do not assume that every form submission or payment automatically sends a visitor to the built-in Thank You Page.
AIUNIFY Funnels includes configurable next-action behavior. A form can be configured to use the supported Thank You Page path or another configured action such as a redirect URL. Payment success behavior also has its own configuration.
Those workflows are addressed in Chapters 23 and 30.
The best way to validate the Thank You Page is to test the actual visitor workflow that is expected to reach it.
Before launching a campaign, confirm that the Thank You Page contains no leftover Template information or instructions that conflict with the current campaign.
Review:
The current Builder displays its mobile-editing warning when the browser width is 768 pixels or less.
Use a wider device to edit the Thank You Page, then test the public result on representative mobile devices or responsive browser widths.
Operating principle: Treat the Thank You Page as a separate conversion-stage experience. Save it independently and verify that the campaign's configured next action actually sends visitors where you intend.