Campaign Studio
Keep a campaign's pages, calls to action and results together.
- Version
- 1.0.52
- Released
- 20 October 2026
- Requires
- Discovery Foundation, Form Builder, Insights, Layout Builder
- Licence
- Commercial
Price £39.00
Check access and installationOn this page
- Price and access
Review the price, licence and availability before deciding what to adopt.
- Your workflow
Read how the package is used and what your application needs to provide.
- Product captures
Review the available captures and see which part of the workflow each screen demonstrates.
- Capabilities
See which jobs this extension supports and which parts it adds to your site.
- Project fit
Decide what this removes from your workload and what your application still needs to supply.
- Installation
Check the setup steps before adding the package to a project.
- Release evidence
Review the available release, maintenance and package-review information.
Check your application before checkout
Use it in your project
Group landing pages around a specific conversion goal, then review which activity led to that result from the same admin workflow.
Picture it on your site
For a campaign launch, choose the result you want visitors to reach before grouping the landing pages. Review the journey from the entry page to that result and agree how the team will interpret activity. Campaign organisation helps keep the work focused; it does not replace the offer, creative work or judgement about the results.
Run and measure your next campaign
- Manage campaign pages and reusable calls to action.
- Record attributed conversions against campaign goals.
Is this right for your project?
Start with a useful campaign question
Choose the audience, action or measurement you actually need before adding another marketing workflow. A package is useful when it connects that task to the content and records your team already manages. Define what a successful result means and who checks it, rather than treating an enabled integration or a growing list of records as proof that the campaign is working.
Keep collection and interpretation separate
Verify the supported data flow with a small, recognisable example, then inspect where the result appears and how fresh it is. External services, consent choices and reporting windows can affect what you see. Your team remains responsible for those settings and for interpreting the result; the extension should make the workflow inspectable, not promise an improvement in sales or traffic.
You may ask Capell for a full refund within 14 days of purchase. Requests are assessed case by case against the recorded order, access and support history. This applies to live paid first-party packages; third-party author sales have separate terms. Read the Refund Policy
Your renewal price stays locked while you renew continuously, including during the grace period. After a full lapse, renewal uses the current list price.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Paid checkout adds access to the purchasing account after payment. Add a free package to your account, then review compatibility and site impact before installing it.
Explore the available extensions on the demo site.
Before you install
Run the commands below in your Capell application. Required dependencies are listed above. After installing a theme, select it for your site in Admin.
-
01
Require the package
composer require capell-app/campaign-studio -
02
Install the extension
php artisan capell:extension-install capell-app/campaign-studio
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.0.52 Oct 20, 2026
- Recent activity
- 18 approved releases in the last 12 months
Review evidence for this release
Tooling for building and publishing campaign landing pages, including a public conversion-tracking endpoint. The review found one medium-severity issue in how that endpoint establishes trust, plus two low-severity issues in error handling and site attribution.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.0.52
- Approval date
- Oct 19, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- A permission-check helper swallows unexpected errors without logging them, which can make a permissions misconfiguration harder to diagnose.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
10 releasesv1.0.52Oct 20, 2026v1.0.51Oct 17, 2026v1.0.48Oct 9, 2026v1.0.47Oct 8, 2026v1.0.46Oct 8, 2026v1.0.45Oct 7, 2026v1.0.44Oct 4, 2026v1.0.43Oct 1, 2026v1.0.42Sep 29, 2026v1.0.41Sep 23, 2026
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.