Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Statamic Funnels

Statamic Funnels Laravel Package

goldnead/statamic-funnels

goldnead/statamic-funnels is a Statamic addon for building and managing marketing funnels. Define multi-step journeys, connect landing pages and conversions, and review funnel performance from the control panel. A lightweight Laravel package for teams running funnel-driven campaigns in Statamic.

View on GitHub
Deep Wiki
Context7

Funnels for Statamic: a path a visitor walks. Pages, forms, offers and payments in one flow, drawn on the automations canvas.

Frequently asked questions about Statamic Funnels
What is goldnead/statamic-funnels?
goldnead/statamic-funnels is a Statamic addon for defining and tracking conversion funnels directly in the Control Panel. You model each stage of a customer journey, connect entry and conversion events to pages, and review conversion rates and step-by-step drop-off. A lightweight middleware records visits and completions automatically, and dashboard widgets surface the results without leaving Statamic.
How do I install Statamic Funnels?
Install it as a Composer package in your Statamic application, then confirm your lockfile resolves cleanly. Adoption is essentially a Composer bump: the material available describes no migration step and no required config key. Recent releases rebuild the Control Panel bundle against goldnead/statamic-flow-canvas, so check that dependency resolves before you deploy.
Do I need to run migrations or publish the config file after installing?
No database migration is called out for the addon, and the Control Panel integration works after install. A publishable config file exists for storage and tracking options, which you only need to publish if you want to override the defaults. Confirm the current requirements against the repository before rolling out to production.
How does funnel tracking work and is there a performance cost?
Tracking is handled by a lightweight middleware that records visits and completions automatically, so you do not write custom event code per funnel step. Control Panel assets ship prebuilt, so no Node toolchain is introduced into your application. As with any middleware, test the overhead under your own traffic patterns before enabling it site-wide.
Can I define multi-step funnels with custom entry and conversion events?
Yes. Funnels are multi-step with configurable entry and conversion events, so you can connect landing pages to the completions you care about. Each funnel is defined in the Control Panel rather than in application code, which keeps campaign changes out of your deploys.
What reports and widgets does the Control Panel provide?
The Control Panel shows conversion rates and step-by-step drop-off for each funnel, plus dashboard widgets and reports. That lets you see where visitors exit and which pages drive completions. Reporting stays inside Statamic, so you do not need a separate analytics dashboard for the basics.
Which Laravel and Statamic versions does this addon support?
The available material does not include a compatibility matrix, so check the composer.json constraints on Packagist and the repository README for supported Laravel and Statamic versions. Treat version support as something to verify for your specific application rather than assume. This matters most if you are running an older Statamic major version.
Does it require other addons such as statamic-flow-canvas?
Yes, at least in recent releases. Version 1.25.1 declares goldnead/statamic-flow-canvas ^1.6.1 as a dependency and rebuilds the Control Panel bundle against it. If your lockfile or another addon pins flow-canvas below 1.6.1, composer update will block the upgrade, which is a visible but deploy-blocking failure. The addon also integrates with statamic-brand-context for Control Panel navigation, so plan both constraints together.
Will upgrading break my custom Control Panel styling or dark mode?
This is the main upgrade risk to check. Canvas components moved from ambient Tailwind utility classes to plain, package-scoped CSS, so any custom styling that targeted the old utility class names on those components will stop applying. The release notes do not confirm dark mode or custom Control Panel theme coverage, so do a visual pass in staging before upgrading production.
Do I need to republish assets after updating the addon?
The release note only says the Control Panel bundle is rebuilt; it does not state whether published asset filenames changed or whether a vendor:publish step is required. Run the upgrade in staging first and check whether your published assets need republishing. If in doubt, re-run the addon's publish command and confirm the Control Panel renders as expected.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console