Download the PHP package clicktrail/laravel without Composer

On this page you can find all versions of the php package clicktrail/laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of clicktrail/laravel

Informations about the package laravel

中文

**clicktrail/laravel** See which campaign, keyword, click ID and landing page created each form submission and conversion in any Laravel 10/11 app.

CI Latest Version on Packagist

Index

Why

Most tracking packages store what a page showed. ClickTrail proves which campaign created the lead or sale. This package is a thin adapter over clicktrail/php-sdk: the SDK owns parse/classify/merge/serialize; Laravel owns capture middleware, consent-gated session persistence, queued delivery, Blade output, and artisan diagnostics.

Installation

Package auto-discovery registers the service provider and the ClickTrail facade. Publish the config and fill CLICKTRAIL_SITE_ID and CLICKTRAIL_ENDPOINT in .env:

Quick start

clicktrail() is the main entry point (a ClickTrail facade also exists).

A direct visit afterwards changes nothing: first touch stays, stored last touch persists. That is the SDK's merge law, tested, not promised.

Blade output

Queued delivery

Events are never sent during the request. Dispatch the delivery job from your own triggers:

The job uses the BatchClient, so bind a PSR-18 client as Psr\Http\Client\ClientInterface plus PSR-17 request/stream factories before dispatching. Queue connection and queue name come from clicktrail.queue_connection / clicktrail.queue.

Failed events and replay

After all retries fail, payloads are stored verbatim in the clicktrail_failed_events table (clicktrail.persist_failed_events, default true). Diagnose, then replay through the same helper:

Consent

ClickTrail is a consent consumer, not a CMP. Implement ClickTrail\Laravel\Consent\ConsentResolverInterface with your CMP adapter and bind it, or set clicktrail.consent_resolver to its class name. Until then the shipped NullConsentResolver returns an unknown snapshot, which is treated as denied everywhere: no identifiers are persisted and no events are delivered. Setting clicktrail.consent_required to false declares this use needs no CMP gating.

First-party proxy (optional)

With CLICKTRAIL_FIRST_PARTY_PROXY=true the provider registers POST /clicktrail/collect. It minimally validates the batch payload shape and re-queues delivery through your own infrastructure.

Diagnostics

Checks config presence, endpoint reachability (TCP-level flag), and consent resolver resolution.

Webhook signatures

Verify ClickTrail webhook callbacks with HMAC-SHA256 constant-time comparison:

How it differs

Package What it does Boundary
combindma/laravel-trail Stores UTMs/referrers in cookies ClickTrail proves which campaign created the lead or sale: deterministic first/last-touch merge laws validated by golden fixtures shared with our WordPress and GTM engines, consent-gated persistence, batched delivery with idempotency keys
DirectoryTree/Metrics Counts anonymous events Complementary: ClickTrail connects campaigns to identities and revenue

See ../docs/COMPETITOR-NOTES.md for the full analysis.

Testing

CI lints all files and runs both stages on PHP 8.1–8.3 (.github/workflows/ci.yml).

License

MIT. Copyright (c) 2026 Vizuh OÜ

All versions of laravel with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
illuminate/support Version ^10.0|^11.0
illuminate/http Version ^10.0|^11.0
illuminate/config Version ^10.0|^11.0
clicktrail/php-sdk Version dev-main
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package clicktrail/laravel contains the following files

Loading the files please wait ...