Publishing takes your funnel from draft to live, making it accessible to real visitors. FunnelFox provides two environments — preview for testing and production for live traffic — ensuring you can test everything safely before going live.
Key concept: Published funnels are static and immutable. Once published, a funnel version works exactly the same way forever, giving you complete reliability and predictable behavior.

How Publishing Works

When you publish a funnel, FunnelFox builds static files that serve your visitors. This process:
  1. Creates a new version (v1, v2, v3…)
  2. Builds all pages and elements into optimized files
  3. Deploys instantly to your funnel URL
  4. Keeps the previous version running until the new one is ready

Instant Updates

Changes go live immediately after publishing completes. No waiting for propagation or cache clearing.

Zero Downtime

Active visitors continue on their current version. New visitors get the updated version seamlessly.

Preview Mode

Test everything before going live. Preview mode gives you a safe environment to validate your funnel with real interactions but without real consequences.

Preview URLs

All preview URLs follow this pattern:
https://app.funnelfox.com/preview/[funnel-id]
These URLs are:
  • Persistent: Save and bookmark them — they always show latest saved changes
  • Shareable: Send to teammates or clients for feedback
  • Device-friendly: Test on any device or browser
  • Always current: Automatically reflect your latest edits

What’s Different in Preview

FeaturePreview ModeProduction
URLapp.funnelfox.com/preview/…[project].fnlfx.com/…
PaymentsTest mode (no real charges)Real transactions
ProductsSandbox productsLive products
UsersMarked as preview profilesReal profiles
AnalyticsTracked normallyTracked normally
WebhooksCan use test endpointsProduction endpoints
Share preview links with stakeholders for approval before publishing. They’ll see exactly what the final funnel will look like.

Publishing to Production

Ready to go live? Click the Publish button in the editor to deploy your funnel to production.

What Happens When You Publish

  1. New version created: Each publish increments the version (v1 → v2 → v3)
  2. Static files built: Your funnel is compiled into optimized static files
  3. Instant deployment: New version replaces the old one immediately
  4. Active users protected: Visitors mid-funnel continue uninterrupted
Publishing is immediate and irreversible. There’s no built-in rollback — always test thoroughly in preview mode first.

Production URLs

Your funnel will be available at:
  • FunnelFox subdomain: [project-name].fnlfx.com/[funnel-alias]
  • Custom domain (if configured): yourdomain.com/[funnel-alias]
See Project Settings to configure custom domains.

When to Republish

Since funnels are static, certain changes require republishing to take effect:

Changes That Require Republishing

  • ✅ Visual Editor changes (elements, text, design)
  • ✅ Adding/removing pages or screens
  • ✅ Project settings (products, prices, integrations)
  • ✅ Payment provider configuration
  • ✅ Meta pixel or tracking changes
  • ✅ Starting an A/B test experiment
  • ✅ Custom domain configuration

Changes That Don’t Require Republishing

  • ❌ Viewing analytics data
  • ❌ User submissions and funnel data
  • ❌ Stopping an experiment (only starting requires republish)
Rule of thumb: If you changed something about how the funnel works or looks, you need to republish. If you’re just viewing data, you don’t.

Managing Versions

Each publish creates a new version number that increments automatically. While you can’t directly rollback to a previous published version, you can:
  1. Use History: The editor’s history feature lets you restore previous saves
  2. Republish: Make your changes and publish again to create a new version
  3. Track changes: Version numbers help you identify when changes went live

Best Practices

Before Publishing

1

Test in Preview

Complete the entire funnel flow in preview mode. Test all paths, buttons, and integrations.
2

Check Integrations

Verify payment providers, pixels, and webhooks are configured correctly for production.
3

Review on Devices

Test preview on mobile, tablet, and desktop to ensure responsive design.
4

Validate Copy

Double-check all text, prices, and legal disclaimers are accurate.

After Publishing

  • Monitor early traffic for unexpected behavior
  • Check analytics to verify tracking works
  • Test the production URL yourself (carefully with test data)
  • Document the version number and what changed

Troubleshooting

Next Steps