"Book a Call" Funnel Setup Example

Use this guide to track a standard booked-call funnel in PixelFlow from the first visit to the completed booking. In most setups, the funnel is PageView → ViewContent → Schedule. The key decision is how you want to trigger the final booking event: through the Calendly integration or through a page-load URL Trigger on a confirmation page on your own domain.

How the funnel maps to events

1. PageView fires automatically when someone lands on your site.

2. ViewContent fires when they reach a key page such as your sales page, pricing page, or booking page.

3. Schedule fires when the person completes the booking.

This setup gives Meta a clear sequence: a visit, a high-intent page view, then a booked call.

Choose the right tracking method for the booking step

If you use Calendly and have a paid Calendly account, the integration is the simplest option. If you use Cal.com, TidyCal, or another calendar app, or if you're on a free Calendly plan, use a confirmation-page URL Trigger instead. If your booking tool redirects users to yourwebsite.com/booking-confirmed, a URL Trigger is the best option. If the final confirmation happens on an external domain, PixelFlow cannot fire a page-load event there.

Step 1: Let PageView track automatically

PageView is the default event for every site visit. Once PixelFlow is installed, you do not need to create a manual trigger for it.

This is your top-of-funnel signal. It tells Meta that someone visited your site before they reached the booking flow.

Step 2: Track ViewContent on the booking-intent page

Use ViewContent on the page that shows real booking intent. This is usually one of these:

• a service page

• a pricing page

• a sales page

• the page where your calendar is embedded

The cleanest way to do this is with a URL Trigger on the page path. PixelFlow matches URL triggers by prefix, so you can usually track the page with its base URL.

For example, you might trigger ViewContent on:

• /book-a-call

• /pricing

• /services

See How to Trigger Events When a Page is Loaded if you need the full page-load setup.

Step 3A: Use the Calendly integration for the booking event

Use this method when the booking itself happens in Calendly and you want PixelFlow to send the event from the Calendly booking source instead of relying on a page redirect.

1. Create a new tracking setup and choose Calendly Bookings & Events.

2. Use Connect Calendly to authorize your Calendly account.

3. In Select an event, choose Schedule.

4. Save the integration and book a test meeting.

With this setup, PixelFlow sends the booking data Calendly provides, including first name, last name, email, and booking time.

For the full integration walkthrough, see Trigger Events from Calendly Bookings.

Step 3B: Use a page-load trigger on a confirmation URL

Use this method when your booking flow ends on a dedicated confirmation page on your own domain, such as yourwebsite.com/booking-confirmed.

This is the best choice when:

• your booking platform supports redirects back to your site

• you want to use one tracked confirmation URL as the conversion step

• you want to extract booking details from the redirect URL

1. Create a confirmation page on your domain, such as /booking-confirmed.

2. Configure your booking tool to redirect people to that page after a successful booking.

3. In PixelFlow, create a URL Trigger for the base confirmation URL.

4. Select Schedule as the event.

5. Save the trigger and test a booking from start to finish.

This method works because PixelFlow is installed on your website. If the final confirmation page is on an external domain, PixelFlow cannot fire the page-load event there.

Calendly direct integration vs confirmation-page trigger

Use the Calendly integration when

• you have a paid Calendly account

• you want the event to come directly from Calendly via webhooks

• you do not want to depend on a redirect to your site

Use a confirmation-page URL Trigger when

• your booking flow redirects back to your own domain

• you want to extract invitee details from redirect parameters

• you want the booking milestone tied to a specific page in your funnel

• you are using a free Calendly plan and cannot use the webhook integration

Extract invitee email and phone from redirect parameters

If Calendly redirects the visitor to your confirmation page with booking details in the URL, PixelFlow can extract those parameters and map them to Meta fields.

Example redirect URL:

yourwebsite.com/[email protected]&invitee_phone=%2B15551234567&invitee_name=John+Doe&event_type_name=Discovery+Call

To set this up:

1. Create your URL Trigger for the base confirmation URL, such as yourwebsite.com/booking-confirmed.

2. Turn on Extract data from URL parameters.

3. Run a test booking and paste the full redirected URL into the example field in PixelFlow.

4. Review the detected parameters.

5. Map each parameter to the right Meta field.

Common mappings:

• invitee_email → Email

• invitee_phone → Phone

• invitee_name → Full name

• invitee_first_name → First name

• invitee_last_name → Last name

This improves event match quality because the booking event includes customer data from the redirect URL.

Cal.com parameters: If you use Cal.com instead of Calendly, the parameter names are different. Common Cal.com parameters include email, attendeeName, attendeeFirstName, attendeeLastName, and phone. The setup process is the same: enable "Forward parameters" in Cal.com's redirect settings, then map the detected parameters to Meta fields.

Prevent duplicate Schedule events

If you use a confirmation page trigger, protect it against duplicate fires. A visitor can refresh the page, bookmark it, or return to it later.

Use Event Blocking Rules on the confirmation page so the same person does not send multiple Schedule events from one booking.

This is especially important for booking confirmation pages because the URL often stays valid after the original conversion.

Example funnel setups

Example 1: Calendly integration funnel

1. PageView fires automatically on the landing page.

2. ViewContent fires on /book-a-call or another high-intent page.

3. Schedule fires through the Calendly integration when the booking is completed.

Example 2: Confirmation-page funnel with redirect parameters

1. PageView fires automatically on the first visit.

2. ViewContent fires on the booking page.

3. The booking tool redirects the visitor to /booking-confirmed.

4. Schedule fires from the confirmation-page URL Trigger.

5. PixelFlow extracts invitee_email and invitee_phone from the redirect URL and sends them with the event.

Verify the funnel before you optimize ads

Test the full journey in order.

1. Visit the first page and confirm PageView.

2. Go to the booking-intent page and confirm ViewContent.

3. Complete a test booking and confirm Schedule.

Check the result in PixelFlow first, then confirm it later in Meta Events Manager. Use Verify Setup with Realtime Event Monitor to inspect the event payload, and see Trigger Events from Calendars & Call Bookings for more redirect-based booking scenarios.