"Lead Gen" Funnel Setup Example

Use this guide to map a typical lead funnel into PixelFlow so Meta receives the right events at each stage. In most cases, the journey starts with an automatic PageView, moves into ViewContent on key pages, and fires a Lead when someone submits a form or books a call.

How a standard lead funnel usually maps to events

A common setup looks like this:

1. PageView when someone lands on your site

2. ViewContent when they reach an important page such as a service page, product page, pricing page, or landing page

3. Lead when they submit a form, request a quote, join a waitlist, or book a call

Not every funnel uses every step. Some sites go straight from PageView to Lead. Others use multiple ViewContent pages before the conversion. The important part is assigning each milestone to the event that matches the real action.

Three ways to track leads in PixelFlow

There are three main ways to track leads in PixelFlow, from simplest to most advanced.

1. Use Visual Tagger on a form or button

Visual Tagger is the simplest setup for most lead funnels. Point and click on your form submit button or CTA button, then assign a Lead or Contact event.

This works best for simple single-step forms where every submission has the same value.

When the form is a good fit, PixelFlow can automatically find visible fields such as name, email, and phone and send that data with the event.

2. Use a direct integration for booking events

When the conversion happens in a connected platform, PixelFlow can trigger the event directly from the source.

• Calendly can send a Schedule event when a booking is completed

This is a strong option when you want the event to come from the source platform rather than from a browser page visit.

In the current setup, these integrations fire for activity in the connected account and are useful when you do not need to filter conversions by page flow.

3. Use page-load URL Triggers with query parameter extraction

This is the most flexible option when you want to control which leads are sent to Meta. Set up your form, booking flow, or funnel tool so qualified users land on a specific confirmation page. PixelFlow then fires the event only when that URL loads.

If the tool appends details such as email, phone, or name in the URL, PixelFlow can extract that data and send it with the event for stronger matching in Meta.

Use this method when you need to filter by lead quality, separate qualified from unqualified submissions, or pass data through the URL after a redirect.

Choose the right trigger method for each step

• Use Visual Tagger for most on-page actions.

• Use URL Triggers when the action ends on a unique page URL

• Use an integration when the conversion happens in Calendly.

PageView: the starting point of the funnel

PageView is the default event for every site visit. Once PixelFlow is installed, this event is sent automatically when someone lands on a page.

You do not need to create a manual trigger for PageView. Use it as the top-of-funnel signal that tells Meta a visit happened.

Typical use:

• homepage visits

• landing page visits

• blog or content entry pages

If your goal is to track a more meaningful step than a basic visit, add ViewContent on the key pages deeper in the funnel.

ViewContent: track visits to important funnel pages

ViewContent is useful when someone reaches a page that shows real buying intent or stronger interest than a simple visit. Common examples include product pages, service pages, pricing pages, webinar registration pages, and other high-intent landing pages.

Best ways to trigger ViewContent

1. URL Triggers for key page URLs or groups of URLs

2. Visual Tagger when you want to tag a specific section on the page also (it might contain price, product name etc.)

If the page URL is the milestone, use How to Trigger Events When a Page is Loaded. PixelFlow matches URL triggers by prefix, so a rule for one base path can also match deeper pages under that path.

Example uses:

• trigger ViewContent on /pricing

• trigger ViewContent on /services

• trigger ViewContent on a product page path such as /product

Lead: trigger the conversion when someone becomes a lead

Lead is the standard event for a successful lead action. In most funnels, this is the main conversion event.

Common lead actions include:

• submitting a contact form

• requesting a demo or quote

• joining a waitlist

• booking a call

• submitting an application

How to trigger Lead from forms

If the form lives on the page or inside a popup, start with Visual Tagger. PixelFlow can track the successful form submission and automatically find visible fields such as name and email.

If the form redirects to a unique success page such as /thank-you after submission, you can also use a URL Trigger on that page.

For a deeper form setup guide, see How to Trigger Events from Forms.

How to filter by lead quality using page routing

The most reliable way to send only qualified leads is to route different outcomes to different pages.

The pattern is simple:

• qualified leads land on a page such as /thank-you-qualified

• unqualified leads land on a different page such as /thank-you

Then create a PixelFlow URL Trigger only for the qualified page. If there is no trigger on the unqualified page, no lead event is sent from that route.

This approach works well when your form or booking tool supports conditional redirects. It is especially useful in multi-step forms, routing forms, and qualification funnels.

How to trigger Lead from bookings

If your lead is a booked call, PixelFlow’s Calendly integration is one option when the booking happens in Calendly. You can also use a URL Trigger if the booking flow ends on a unique confirmation page.

If you need to separate qualified and unqualified bookings, a redirect-based flow is usually easier to control than sending all bookings through one event source.

Examples for routing-based lead filtering

You can use the same pattern across different tools:

• Calendly routing forms: send qualified and unqualified leads to different destinations, then trigger only the qualified confirmation page

• Typeform or multi-step forms: use conditional logic so only qualified respondents reach the tracked thank-you page

• Other form tools with conditional redirects: point qualified users to one URL and everyone else to another

If the tool can append values to the redirect URL, pass fields such as name, email, and phone so PixelFlow can extract them on the confirmation page.

Why user data improves event quality

Sending a lead event is useful on its own, but the event becomes more valuable when PixelFlow can also send customer details that help Meta match the person to a real profile.

Fields such as email and phone are commonly used in lead flows. When those values are available from a form, redirect URL, or connected source, include them in the setup where possible.

If you use URL-based confirmations, query parameter extraction is the clearest way to enrich those events without adding a custom implementation.

Recommended setup examples

Example 1: simple lead generation funnel

1. PageView on the landing page happens automatically

2. ViewContent fires on the pricing or service page using a URL Trigger

3. Lead fires when the user submits the form using Visual Tagger

4. If the form redirects to /thank-you, you can use that page as the lead milestone instead

Example 2: qualified lead funnel with routing

1. PageView happens automatically on the landing page

2. ViewContent fires on the key offer or qualification page

3. The form uses conditional logic to route qualified users to /thank-you-qualified and everyone else to /thank-you

4. PixelFlow fires Lead only on /thank-you-qualified

5. If the redirect includes name, email, or phone in the URL, PixelFlow can extract that data on the qualified page

Example 3: booked-call funnel

1. PageView happens automatically

2. ViewContent fires on the booking page or sales page

3. Schedule fires from a booking flow when the user completes the booking

4. If you need qualification control, use separate confirmation pages and trigger only the qualified booking outcome

How to avoid common mistakes

• Do not use URL Triggers for forms that stay on the same page

• Do not include query parameters when entering the base URL for a page-load trigger

• Do not treat every page as ViewContent; reserve it for meaningful funnel pages

• Use duplicate blocking on reload-sensitive success pages

• Use manual tagging with CSS classes when you need richer form data

• Remove overlapping native Meta Pixel or plugin-based tracking if it would cause duplicate events alongside PixelFlow

Verify the funnel is working

After setup, confirm each event in PixelFlow before you start optimizing ads around it. Test the full journey from landing page to conversion, then verify the event appears in the Realtime Event Monitor.

• Check PageView on the first page visit

• Visit your key page and confirm ViewContent

• Submit the form or booking flow and confirm Lead or Schedule

Next, use Verify Setup with Realtime Event Monitor to confirm the final payloads, and see What Events Can PixelFlow Track? for the full standard event list.