Funnels

How Lead360 helps

Lead360 Funnels organizes multiple pages and actions into an ordered conversion journey. Each step can focus the visitor on one decision while forms, appointments, payments, and tracking connect the journey to live Lead360 records.

When to use this area

Use Funnels when the customer experience has a defined sequence such as discovery, qualification, booking, purchase, or confirmation.

Before you begin

• Define the purpose and success event for every step.
• Map links, forms, calendars, offers, consent, and tracking.
• Prepare a fallback path for ineligible, failed, or returning visitors.

What a Lead360 funnel is

A funnel is an ordered group of pages for one customer journey, such as ad landing page, offer details, form or booking, and confirmation. Each step has its own page and path, while the funnel keeps the flow, domain, and tracking together.

Choose how to start

1. Custom Funnel starts with an empty funnel and gives you full page control.
2. Use a Theme creates a designed starting point that you can revise.
3. Build with Ask360 helps generate page drafts from your audience, offer, style, required sections, and conversion goal when that workspace is available. Review every page before publishing.

Build the page journey

1. Define the audience, offer, traffic source, and one primary conversion.
2. Map the page order before writing copy: landing page, supporting pages, form, booking or checkout, then confirmation.
3. Open each step with Edit to build its sections and add the correct Lead360 form, survey, booking, or checkout experience.
4. Preview desktop and mobile, then test every step from the original traffic link.

Set redirects and submission flow

1. Use Flow on each funnel step to continue to the next step, send visitors to a selected funnel step, open an external URL, or use the redirect configured inside the submitted form or survey.
2. For a form or survey redirect, set the full post-submit destination in that form or survey builder, then choose Use the form or survey redirect on the funnel step.
3. Test successful submission, validation errors, repeat submission, and the final destination before sending traffic.

Add tracking and chat code

1. Use funnel-wide head code for trusted analytics, advertising pixels, verification tags, or scripts that the provider requires in the document head.
2. Use funnel-wide body code for an approved chat-widget embed or scripts that the provider requires after the body opens. Follow the provider placement instructions if its snippet specifies head or body.
3. Confirm consent requirements, avoid loading the same pixel or widget twice, verify event deduplication, and test performance and mobile behavior before publishing.

Use Ask360 for the right job

The Help button explains the funnel and prepares a page-by-page plan. To generate page drafts, open New Funnel and choose Build with Ask360. Ask360 should stay in the Funnels scope, request missing details, and show a review step before any server-granted live change.

Confirm the result

A completed Funnels workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.

• Complete the full journey on mobile and desktop.
• Test validation, back navigation, refresh, duplicate submission, and failure states.
• Confirm records, attribution, communication, and payment evidence in Lead360.

Troubleshooting

Visitors leave between steps

Review page speed, mobile layout, message continuity, required fields, broken links, and whether the next action is clear.

Conversion events are duplicated

Check repeated scripts, redirects, refresh behavior, tag manager rules, and server-side event handling.