Pixelflow
Tracking Setup Examples

How to Split Leads Based on a Form Answer

Split leads by form answer by redirecting each answer to a distinct URL and creating a page-load trigger for it. Your form tool must support conditional redirects based on an answer, and the redirect is set up in that tool — PixelFlow reads the destination URL, it doesn't change where your form sends people.

There are two correct ways to do it:

  • Redirect to a URL fragment per answer — send each answer to the same page with a different fragment (#warn vs #cold) and create a trigger for each.

  • Redirect to one URL with a dynamic query parameter — send every answer to the same URL with a different value (?value=500 vs ?value=100) and create one trigger that extracts the value.

Choose an approach

Both approaches track the same form. They differ in how many triggers you create and in how the answer reaches Meta.

Approach

How it works

Triggers

URL fragment per answer

Each answer loads the same page under a different URL (yoursite.com/thank-you#warn, yoursite.com/thank-you#cold)

One trigger per fragment

Dynamic query parameter

Every answer loads the same URL with a different value (yoursite.com/thank-you?value=500, yoursite.com/thank-you?value=100)

One trigger that extracts the value

Approach 1: Redirect each answer to a different URL fragment

With this approach each answer loads the same page, but the fragment after the path (#warn or #cold) makes the address a different URL to PixelFlow. You create one page-load trigger per fragment.

  1. Set your form's conditional redirect so one answer sends the visitor to yoursite.com/thank-you#warn and another sends them to yoursite.com/thank-you#cold. Both URLs load the same page.

  2. In your PixelFlow dashboard, click Track more events, choose the event, and select When a page loads.

  3. On Which page should trigger this event?, enter yoursite.com/thank-you#warn and click Create trigger.

  4. Repeat for yoursite.com/thank-you#cold.

Include the fragment in the trigger URL. Page-load triggers match with Starts With, so a trigger on ...#warn matches only visitors whose URL begins with #warn, and a trigger on ...#cold matches only #cold. Each fragment fires its own event. For the full page-load setup, see How to Trigger Events When a Page is Loaded.

Approach 2: Redirect every answer to one URL with a dynamic value

With this approach every answer loads the same URL, but the value in the query string differs per answer. One page-load trigger reads and extracts that value each time.

  1. Set your form's redirect to append the answer as a query parameter — for example ?value=500 for one answer and ?value=100 for another.

  2. In your PixelFlow dashboard, click Track more events, choose the event, and select When a page loads.

  3. On Which page should trigger this event?, paste a full example URL that includes the parameter, such as yoursite.com/thank-you?value=500.

  4. When PixelFlow detects the parameter, click Next to open Confirm what's in your URL.

  5. Map the value parameter to a Facebook field — such as Order value — and click Create trigger.

PixelFlow stores that mapping and extracts the value from each visitor's URL, so ?value=500 and ?value=100 are read dynamically without a separate trigger for each. For the full mapping walkthrough, see Extract Data from URLs When Using URL Triggers.

Verify and avoid duplicate events

Test every answer path end to end before you rely on the split, then confirm the event appears in the Realtime Event Monitor.

  • Submit the form once per answer and confirm the right event fires for each destination URL.

  • Revisit the confirmation URL to check that a refresh doesn't double-count the lead.

Block duplicate events is on by default for page-load triggers, so a refresh won't count the same conversion twice. Adjust the ignore window or turn blocking off under Event Blocking Rules.

What to do next

Was this helpful?
Was this helpful?