Call Funnel

The VSL funnel end to end — traffic, the video, applications, bookings and cash. Counts are the same ones the Funnel Breakdown tab shows for VSL Funnel, on the same definitions. Showing 1–30 Sept.

1–30 Sept

Traffic and viewing

Unique page visitors514
VSL plays267
  • VSL play rate51.9%
Average watch time6m 55s
Viewers reaching the CTA35
  • CTA reach rate13.0%
Applications started64
  • CTA click-through rate— apps also arrive direct
  • more applications started than viewers reached the CTA — the application is also reached directly, not only from the video, so this ratio cannot isolate the CTA

Applications and bookings

Completed applications49
  • Application completion rate76.6%
  • Page-to-application rate9.5%
  • Qualification rate— no field yet
Calls booked27
  • Application-to-book rate55.1%
  • Page-to-booked-call rate5.3%
  • No qualification field exists on APPLICATIONS yet.

Sales and financial results

Calls held17
  • Show rate63.0%
Sales9
  • Close rate52.9%
Revenue generated$42,500
Cash collected$27,100
  • Average cash collected per sale$3,011
Cash per booked call$1,004
Cash per unique page visitor$52.72

VSL retention

Flip Lab VSL — Main (18 min) · 18:14 · all-time curve, not windowed — Wistia’s engagement endpoint takes no dates
25%50%75%100%CTA 14:050:004:349:0713:4118:14
540 viewers at the start70 still watching at the CTA (13%)6% reach the endsteepest drop around 14:00 (−5% in 10s)

Traffic-source performance

how each organic source performs through the whole funnel
SourceUnique page visitorsCompleted applicationsCalls bookedSalesCash collected
YouTube—431$2,500
Instagram—110—
Email—211$2,100
Direct—211$5,250
Other / Unknown—40216$17,250
Sources come from the UTM on the application itself. Unique page visitors per source needs the pageview stitched to the person who later applied — that join is not built, so the column is blank rather than filled from a different population.

Wiring faults on this funnel

1 booking is tagged to a different funnel than the application it came from
Credited here because the funnel is where the person entered — but the Booking Funnel cell disagrees, so any report reading that cell instead will disagree with this page.
Fix: Airtable → EVENTS → point the Calendly event at this funnel, or merge the two funnel rows.