VSLStats for Info Product Sellers
Info product launches live and die on the VSL. A $997 course, a $2,000 coaching program, a $47 ebook with a $297 upsell - the entire revenue engine is a video that either convinces someone to buy or doesn't. And yet most info product sellers can't tell you which 30-second segment of their VSL is causing the biggest drop-off, or how much revenue each viewer actually generates, or why their Meta pixel says they made $8,000 last week when Stripe says $14,000. This is the setup guide for tracking that actually answers those questions.
Info product VSLs need three things most video platforms don't provide: revenue attribution that ties each viewer to a purchase (so you know exactly what each VSL earns), retention analytics that show where the script loses people (so you can fix it), and server-side pixel forwarding that recovers the 30-50% of conversions browser pixels miss on long-form content.
What do info product sellers actually need from a VSL platform?
Info product sellers need revenue attribution per viewer, granular retention curves with timestamp-level resolution, server-side conversion tracking for Meta and Google ads, A/B testing that measures revenue per variant (not just views), and behavioral CTAs that fire at specific timestamps in the video.
The info product model has specific characteristics that change which VSL features matter most:
- High price points = high stakes per viewer. When a single sale is worth $497-$2,000, every viewer matters. You need to know exactly how much revenue each viewer generates, not just aggregate conversion rates. That's revenue attribution - the ability to trace a specific purchase back to a specific viewer session.
- Long-form content = long tracking windows. A 35-minute VSL means 35 minutes between the ad click and the purchase. That's 35 minutes for browser tracking to break. Server-side pixel forwarding isn't optional for info product VSLs running paid traffic - it's the only way to get accurate conversion data. (See: why your Meta pixel undercounts by 30-50%.)
- The script IS the product marketing. Unlike ecommerce where the product photo does the selling, info products sell through the VSL script. Which means retention curve analytics aren't a nice-to-have - they're the primary diagnostic tool for figuring out why a launch is underperforming.
- Launch cycles = testing cycles. Info product sellers typically launch in bursts - a new VSL, a new hook, a new offer structure. Each launch is a natural A/B test. You need to measure revenue per variant, not just engagement metrics, to know which version wins.
For info product sellers, the VSL isn't the marketing for the product - it IS the product's first impression, the sales team, and the closing mechanism, all in one video. Every minute of watch time is either building toward a sale or losing one.
How does VSLStats handle info product use cases?
VSLStats ties every viewer session to a revenue event, shows retention curves with second-level granularity, runs server-side conversion forwarding to Meta CAPI and GA4, and supports A/B testing that tracks revenue per variant. The Pro tier at $79/mo (annual) includes all of these.
Revenue attribution
When a viewer watches your VSL and buys, VSLStats connects the purchase to that specific viewer session. You see revenue per viewer, revenue per video, and revenue per traffic source. For info product sellers running multiple offers or upsell sequences, this means you can trace the entire customer journey from first VSL view through the final upsell acceptance.
Retention curve diagnostics
The retention curve is the most important diagnostic tool for info product VSLs. VSLStats gives you second-level granularity, so you can see exactly where viewers drop off - not just "between minutes 10 and 15" but "at 12:34 when the transition from problem to solution happens." The four metrics that matter for diagnosing a VSL all depend on retention data.
Server-side pixel forwarding
Info product VSLs are the single worst-affected category for pixel suppression. A $997 course VSL running 35 minutes on mobile traffic from Meta ads? You're losing 35-50% of your conversion data to ad blockers and iOS ATT. Server-side forwarding to Meta's Conversions API recovers those events so your algorithm actually knows which audiences are buying.
A/B testing with revenue tracking
Most VSL A/B testing tools measure engagement: which variant gets more views, better retention, higher play rate. But for a $997 info product, a variant with lower retention might generate more revenue if the viewers who stay are more qualified buyers. VSLStats A/B testing measures revenue per variant, which is the only metric that matters for deciding which version wins.
Which VSLStats tier makes sense for info product sellers?
Most info product sellers should start with Pro ($79/mo annual). It includes everything in the feature list above - revenue attribution, retention analytics, server-side forwarding, A/B testing, and AI captions. Starter ($29/mo annual) works for testing a first VSL, but lacks server-side forwarding and A/B testing.
| Feature | Starter ($29/mo) | Pro ($79/mo) |
|---|---|---|
| Retention curves | Yes | Yes |
| Revenue attribution | Basic | Full (per-viewer, per-source) |
| Server-side pixel forwarding | No | Yes (Meta CAPI, GA4, TikTok) |
| A/B testing | No | Yes (revenue per variant) |
| AI captions | No | Yes |
| Behavioral CTAs | Yes | Yes |
| HookBoost diagnostics | No | Yes |
| Videos | 10 | 50 |
The decision point is usually server-side forwarding. If you're spending more than $1,000/month on Meta ads driving traffic to a VSL, the pixel undercount problem is costing you more in misattributed conversions than the Pro upgrade costs. The math is clear.
Common info product use case scenarios
You're running $3,000-$10,000/week in Meta ads to a 40-minute VSL. Without server-side forwarding, Meta reports 12 sales when Stripe shows 21. Your campaign looks like a 1.2x ROAS when the real number is 2.1x. With VSLStats Pro, server-side CAPI forwarding recovers those missing conversions, and retention curve analytics show you the exact timestamp where the biggest viewer drop happens - so you know whether to fix the hook, the body, or the close.
The front-end VSL sells the ebook. A second VSL on the thank-you page sells the upsell. Revenue attribution across both videos tells you the real customer value: $47 × conversion rate + $297 × upsell take rate = actual revenue per viewer. Most sellers optimize the front-end VSL in isolation and never realize the upsell VSL is where they're leaving the most money.
Longer format (45-60 minutes), high price point, lower volume. Every viewer is worth significantly more, so retention diagnostics are critical. At $2,000 per sale and a 0.8% conversion rate, your RPV is $16 per viewer. A 5% improvement in midpoint retention - moving viewers past the "solution reveal" section - can shift conversion rate enough to add $2-3 per viewer in RPV. On 5,000 viewers per month, that's $10,000-$15,000 in additional annual revenue from one VSL section edit.
How info product sellers typically migrate to VSLStats
Migration takes 15-30 minutes per VSL: upload the video file, swap the embed code on your funnel page, configure your pixel IDs for server-side forwarding, and verify the tracking with a test purchase. No video re-encoding, no URL changes, no downtime.
The typical path:
- Start with your highest-spend VSL. The one with the most ad budget behind it benefits most from accurate tracking. Migrate that first.
- Upload and embed. Upload the video file to VSLStats. Copy the embed code and paste it into your ClickFunnels, GoHighLevel, Kajabi, or custom page. Remove the old player embed.
- Configure tracking. Add your Meta Pixel ID and CAPI access token for server-side forwarding. Add GA4 Measurement ID if you're running Google Ads. Set up the revenue webhook from Stripe.
- Verify with a test purchase. Run a $1 test transaction through the funnel. Confirm the conversion event appears in VSLStats, in Meta Events Manager, and in your ad account.
- Let it run for 7 days. Compare VSLStats-reported revenue attribution against Stripe's actual revenue. The gap should be under 15%. If it's larger, check the CAPI configuration.
Most info product sellers have 1-3 active VSLs at any time. The full migration is usually done in an afternoon.
Frequently asked questions
Track what your VSL actually earns
VSLStats Pro gives you revenue attribution, retention diagnostics, and server-side pixel forwarding. Try any plan for $1.
Start $1 Trial →