Skip to main content
Capell home
Live demo
Beta

Referers

See which external sources are sending people to your site.

Version
1.0.0-beta.12
Released
20 October 2026
Licence
Free
A genuine Referers product screenshot. Open the workflow gallery for its full description.
Review referral sources, successful page requests and their share for the selected site and reporting period.
Beta

Check compatibility before using this Beta extension

Beta does not mean production-ready. Review compatibility, support, site impact, and likely upgrade work before enabling it.

Check your application before checkout

Usage

Use it in your project

Review aggregate counts for configured referral sources. Reports keep daily and lifetime totals without storing raw referral URLs or individual request identifiers.

Picture it on your site

For a campaign using a few known referral sources, agree which aggregate totals help answer the business question. Compare daily and lifetime figures without expecting a person-by-person journey. The package deliberately avoids raw referral URLs and individual request identifiers, so choose it for source-level reporting rather than detailed visitor tracking.

1 capture

Included

Run and measure your next campaign

  • Compare site-scoped referral source counts.
  • Read cached reports and a dashboard summary.

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.

Licence Free
Install now
Review site impact

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.

Open the live demo

Explore the available extensions on the demo site.

Installation impact

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.

  1. 01

    Require the package

    composer require capell-app/referer
  2. 02

    Install the extension

    php artisan capell:extension-install capell-app/referer
Release and review evidence
Maintenance

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.0-beta.12 Oct 20, 2026
Recent activity
8 approved releases in the last 12 months
Capell reviewed

Review evidence for this release

Privacy-preserving aggregate referral reporting package reviewed with no defects found; it deliberately never stores raw referrer URLs, only classifies them in-memory into a bounded source key before discarding the header, and aggregate counters cannot be used to fingerprint individual visitors.

Review reduces risk, but it is not a permanent security guarantee.

Automated checks passed
AI-assisted analysis completed
Human sign-off completed
Reviewed version
1.0.0-beta.12
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

  • Cache-hit measurement requires an extension hook before frontend cache short-circuiting, deferred per the package's own contribution-traceability notes. Cross-package integration was not exercised by this per-package review; the local suites used SQLite, and live browser flows and server-database behaviour were not exercised.

Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.

Changelog

Release notes and maintenance evidence

Total downloads
0
Last downloaded
No downloads yet

Version history

8 releases
  1. v1.0.0-beta.12
    Oct 20, 2026
  2. v1.0.0-beta.11
    Oct 17, 2026
  3. v1.0.0-beta.10
    Oct 9, 2026
  4. v1.0.0-beta.9
    Oct 9, 2026
  5. v1.0.0-beta.8
    Oct 8, 2026
  6. v1.0.0-beta.7
    Oct 8, 2026
  7. v1.0.0-beta.6
    Oct 7, 2026
  8. v1.0.0-beta.5
    Oct 4, 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.

Referers screenshot gallery

Referrers report showing populated referral aggregates in Capell Admin