30.1 Payment Success Actions

AIUNIFY Funnels provides a Landing Page setting labeled:

Action after payment success

This setting determines the visitor destination used by the supported Landing Page payment workflow after a successful payment operation.

30.2 Payment Action Interface

The Settings screen describes the control with:

All the button payment in main pages when success will...

The confirmed choices are:

Go to default Thank You Page	Uses the Landing Page's default Thank You Page after successful payment.
Redirect to any URL	Uses the separately configured payment redirect URL after successful payment.

30.3 Go to Default Thank You Page

Select Go to default Thank You Page when the customer should remain within the Landing Page's built-in post-conversion experience.

The confirmed payment workflow uses the Landing Page's public URL together with its Thank You Page destination when this option is selected.

Before launch, open the Thank You Page in the Builder and make sure the content is appropriate for a completed payment.

30.4 Redirect to Any URL

Select Redirect to any URL when the customer should be sent to another web destination after successful payment.

When this option is selected, the interface exposes:

Redirect to:

Enter the intended complete destination URL and save the Landing Page Settings.

30.5 Payment Redirect Is Separate from Form Redirect

The Landing Page maintains separate controls for:

Action after form submission	Controls where a visitor goes after a normal form submission.
Action after payment success	Controls where a visitor goes after the supported payment-success workflow.

Changing one does not replace the other.

30.6 Review Payment Components Before Launch

The Landing Page Builder supports payment-related components associated with the application's Ecommerce workflow.

After changing a payment-success destination, test the actual payment flow used by the Landing Page rather than checking only whether the destination URL opens separately.

30.7 Testing the Thank You Page Payment Action

1. Open the Landing Page Settings.
2. Set Action after payment success to Go to default Thank You Page.
3. Save Settings.
4. Review the configured Product and payment component.
5. Run an appropriate controlled payment test.
6. Confirm the intended Thank You Page appears after the successful workflow.
7. Confirm the resulting Order information is recorded as expected.

30.8 Testing a Payment URL Redirect

1. Select Redirect to any URL.
2. Enter the destination in Redirect to:.
3. Save Settings.
4. Run a controlled payment test through the public Landing Page.
5. Confirm the successful payment reaches the exact intended destination.
6. Confirm the associated Order information is correct.

30.9 Custom Code Overview

Landing Page Settings also contain a Custom Code area labeled:

Insert Headers and Footers

The application explains:

Insert Headers and Footers lets you insert code like Google Analytics, custom CSS, Facebook Pixel, Chat, and more to your LandingPage site header and footer

30.10 Header Code

The Header field stores the Landing Page's custom_header content.

Use this area only when a trusted integration or customization specifically requires code to be added to the page header.

30.11 Footer Code

The Footer field stores the Landing Page's custom_footer content.

Use this area when trusted code is intended for the footer portion of the Landing Page output.

30.12 Common Uses Identified by the Interface

The application specifically identifies examples such as:

1. Google Analytics.
2. Custom CSS.
3. Facebook Pixel.
4. Chat code.
5. Other supported header or footer snippets required by a trusted service.

30.13 Custom Code Is Powerful

Header and Footer code becomes part of the Landing Page's public presentation. Incorrect HTML, CSS, or JavaScript can affect page appearance or behavior.

Only insert code from a source you trust and understand.

30.14 Do Not Put Private Credentials in Public Page Code

Do not place server passwords, private API credentials, database credentials, or other secrets into Landing Page Header or Footer code.

Public-page source can be inspected by visitors, so these fields should be treated as client-side page customization areas rather than secure credential storage.

30.15 Add One Integration at a Time

When possible, add or modify one custom-code integration at a time and test the public Landing Page afterward.

This makes it easier to identify which change caused a layout, tracking, chat, or script problem if one occurs.

30.16 Save and Verify Custom Code

1. Open Landing Page Settings.
2. Open Custom Code.
3. Place the trusted snippet into Header or Footer according to its installation instructions.
4. Save Settings.
5. Open the public Landing Page.
6. Verify the page still loads and displays correctly.
7. Verify the intended third-party function separately.
8. Check important Desktop and Mobile layouts after custom CSS or scripts are added.

30.17 Payment and Custom Code Changes Require Public Testing

Both payment-success behavior and custom Header/Footer code affect the public customer experience.

After changing either one, complete a public-page test instead of relying only on the saved Settings screen.

Operating principle: Configure the intended post-payment destination separately from ordinary form behavior, and treat Header/Footer code as public executable page customization that should be added carefully and tested immediately.